Nokia 8DG09603CAAATQZZA Issue 4 PDF

1850 Transport Service Switch
(TSS-320, TSS-320H and TSS-

160)
Release 5.1 (ETSI)
TL1 User Provisioning Guide
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.
Release 5.1 (ETSI)

September 2017
2 8DG09603CAAATQZZA Issue 4
1850 TSS-320/TSS-320H/TSS-160
Contents
About this document..........................................................................................................................................21
1 Line Command User's Interface Introduction ...........................................................................................29

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
2 Getting started..............................................................................................................................................49
2.1 Overview ...........................................................................................................................................49
2.2 TL1 and CLI sessions .......................................................................................................................49
3 Task Index List (IXL) ....................................................................................................................................57

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
Release 5.1 (ETSI)

September 2017
Issue 4 8DG09603CAAATQZZA 3
1850 TSS-320/TSS-320H/TSS-160
3.20 IXL-19: Enhanced Shelf Equipment Functions .................................................................................66
4 Nontrouble Procedure (NTP).......................................................................................................................67

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.23 PW Termination Management (Case of VPLS) .................................................................................97
4.24 Tunnel Protection Management (Label swap and Tunnel not Terminated) .......................................98
4.25 VCG Deprovisioning........................................................................................................................100
4.26 VCG Provisioning............................................................................................................................100
4.27 VPLS Deprovisioning ......................................................................................................................102
4.28 VPLS Provisioning ..........................................................................................................................102
4.29 UGW Protection Provisioning..........................................................................................................104
5 Control Plane Functions............................................................................................................................107

5.1 Overview .........................................................................................................................................107
5.2 Administer T-MPLS Control Plane Global Parameters....................................................................110
5.3 Administer Control Plane - Control Routing Port .............................................................................111
5.4 Administer Control Plane - IP Route................................................................................................115
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
5.5 Administer Control Plane - Tranport Port ........................................................................................119

5.6 Administer Control Plane - OSPF routing .......................................................................................122
5.7 Administer CP Tunnels - Make Before Break..................................................................................125
5.8 Administer Control Plane Hoplist ....................................................................................................129
6 Detailed Level Procedure ..........................................................................................................................135

6.1 Overview .........................................................................................................................................135
6.2 Add New User to System ................................................................................................................138
6.3 Administer ASAP.............................................................................................................................139
6.4 Administer Duplex Switching Equipment Protection Group ............................................................143
6.5 Administer Duplex Switching ATM Protection Group ......................................................................147
6.6 Administer Database Backup..........................................................................................................150
6.7 Administer Database Restore ........................................................................................................152
6.8 Administer Ethernet Facility ...........................................................................................................155
6.9 Administer Equipment Optical Connection......................................................................................161
6.10 Administer Line Optical Connection Management ..........................................................................163
6.11 Administer PassThrough Optical Connection Management ...........................................................167
6.12 Administer Cascade Optical Connection Management...................................................................171
6.13 Administer ADD/DROP Optical Connection Management ..............................................................175
6.14 Administer GBE10 Loopback ..........................................................................................................179
6.15 Administer GBE Loopback ..............................................................................................................183
6.16 Administer L2 Encapsulation Profile ...............................................................................................186
6.17 Administer MAC FILE COLLECTION..............................................................................................190
6.18 Administer MAU Facility ..................................................................................................................193
6.19 Administer MAU Loopback..............................................................................................................195
6.20 Administer Network Interface ..........................................................................................................199
6.21 Administer NE IP Route ..................................................................................................................200
6.22 Administer NE IP Tunnel .................................................................................................................203
6.23 Administer Network Time Protocol (NTP) .......................................................................................207
6.24 Administer STMn Neighbor Discovery ............................................................................................211
6.25 Administer ODU2 Facility ................................................................................................................212
6.26 Administer OTU2 Facility ................................................................................................................218
6.27 Administer Path Protected Cross-Connection.................................................................................224
6.28 Administer Per Hop Behaviour Profile (PHBprofile) ........................................................................227
6.29 Administer Radius server ................................................................................................................229
6.30 Administer Security Log File ...........................................................................................................232
6.31 Administer STMn Facility ................................................................................................................235
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
6.32 Administer STM-n Facility Protection Group ...................................................................................237

6.33 Administer STMn Loopback ...........................................................................................................241
6.34 Administer STMn MS-SPRING .......................................................................................................245
6.35 Administer System Configuration....................................................................................................253
6.36 Administer System Timing/BITS......................................................................................................255
6.37 Administer Clock references - Synchronization ..............................................................................258
6.38 Administer Users with Security Administrator Privileges.................................................................263
6.39 Administer VC Cross-Connection ...................................................................................................267
6.40 Administer VCG Facility ..................................................................................................................277
6.41 Auto Discovery Function .................................................................................................................284
6.42 Boundary TOD Card administration ................................................................................................285
6.43 Change Facility Service State .........................................................................................................293
6.44 Change User Password ..................................................................................................................294
6.45 Convert a Cross-Connection...........................................................................................................296
6.46 Delete User from System ................................................................................................................308
6.47 Deprovision Equipment ...................................................................................................................308
6.48 Disable/Enable User Account..........................................................................................................314
6.49 Display Alarms ................................................................................................................................319
6.50 Display MPLS interface parameters................................................................................................328
6.51 Display Status and Conditions ........................................................................................................329
6.52 Edit User Profile ..............................................................................................................................337
6.53 Housekeeping Alarms Management ...............................................................................................341
6.54 Housekeeping Controls Management.............................................................................................345
6.55 Initialize System Processors ...........................................................................................................348
6.56 LCAS Monitoring .............................................................................................................................351
6.57 Log Into System ..............................................................................................................................354
6.58 Log Out of System ..........................................................................................................................355
6.59 Master TOD Card Management ......................................................................................................357
6.60 Optical Intrusion Overview ..............................................................................................................363
6.61 Optical Intrusion Adminstration .......................................................................................................364
6.62 Perform Audible Alarm Cutoff ..........................................................................................................366
6.63 Perform Module Protection Switch or Copy Switch.........................................................................367
6.64 Perform Remote Database Backup ................................................................................................369
6.65 Perform Remote Database Restore................................................................................................375
6.66 Port segregation Management........................................................................................................382
6.67 Provision Equipment .......................................................................................................................385
6.68 Radius server authentication ordering ............................................................................................390
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
6.69 Remove/Restore Equipment ...........................................................................................................393

6.70 Report Performance Monitoring (PM) Data.....................................................................................397
6.71 Retrieve and Change Site Identifier ................................................................................................400
6.72 Retrieve Module Remote Inventory Information..............................................................................402
6.73 Retrieve Section Trace....................................................................................................................404
6.74 Retrieve System Configuration .......................................................................................................406
6.75 Retrieve TL1 Command Syntax ......................................................................................................409
6.76 Retrieve User Session Information .................................................................................................410
6.77 Retrieve/Provision IP Address of NE...............................................................................................414
6.78 Security Defaults Administration .....................................................................................................417
6.79 Set Performance Monitoring (PM) Mode.........................................................................................419
6.80 Set Performance Monitoring (PM) Threshold Levels ......................................................................421
6.81 Slave TOD Card Management ........................................................................................................424
6.82 Set System Date and Time .............................................................................................................430
6.83 Set System-Wide User Security Parameters ..................................................................................432
6.84 Switch STMn Line to Protection ......................................................................................................434
6.85 Switch VCn Line to Protection.........................................................................................................437
6.86 System Access Control (intrusion alarm) ........................................................................................439
6.87 Users with Security Administrator Privileges Overview...................................................................441
6.88 Virtual Concatenation Path Check ..................................................................................................442
6.89 Modify Equipment Management for Data units ...............................................................................444
7 S320H Shelf Detailed Level Procedure ....................................................................................................451

7.1 Overview .........................................................................................................................................451
7.2 Provision Equipment (S320H).........................................................................................................451
7.3 Administer S320H module ..............................................................................................................455
8 TMPLS/MPLS-TP Detailed Level Procedure ............................................................................................463

8.1 Overview .........................................................................................................................................463
8.2 Administer MPLS-TP Loopback OAM tool .....................................................................................464
8.3 Administer MPLS-TP Connectivity verification Loopback OAM tool ..............................................471
8.4 Administer MPLS-TP Diagnostic Loopback OAM tool ...................................................................479
8.5 Administer MPLS-TP Discovery Loopback OAM tool ....................................................................486
8.6 Administer (T-MPLS/MPLS-TP) DM tool ........................................................................................491
8.7 Administer T-MPLS Facility Protection Group .................................................................................497
8.8 Administer T-MPLS Global Network Parameters ............................................................................502
8.9 Administer T-MPLS/ MPLS-TP Node configuration.........................................................................504
8.10 Administer T-MPLS OAM (T-MPLS Tunnel protection) ...................................................................507
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
8.11 Administer T-MPLS Pseudo Wire....................................................................................................510

8.12 Administer T-MPLS Pseudo Wire Segment ....................................................................................514
8.13 Administer T-MPLS Pseudo Wire Segment Cross-Connection.......................................................517
8.14 Administer T-MPLS Traffic Descriptor .............................................................................................521
8.15 Administer T-MPLS Tunnel .............................................................................................................524
8.16 Administer TMPLS Tunnels Group..................................................................................................528
8.17 Administer T-MPLS Tunnel Segment ..............................................................................................531
8.18 Administer T-MPLS Tunnel Segment Cross-Connection ................................................................535
8.19 Proactive DM ..................................................................................................................................538
8.20 Proactive LM (Synthetic Loss Measurement) .................................................................................543
8.21 Report Performance Monitoring (PM) Data for T-MPLS..................................................................550
8.22 Set Performance Monitoring (PM) Data for T-MPLS .......................................................................552
9 1662 Drop Shelf Detailed Level Procedure ..............................................................................................555

9.1 Overview .........................................................................................................................................555
9.2 1662SMC Drop Shelf Overview ......................................................................................................555
9.3 1662SMC drop shelf management .................................................................................................559
9.4 Administer 1662 Subshelf E1 cards ................................................................................................561
9.5 1662 Subshelf Facilities Overview ..................................................................................................564
9.6 1662 Subshelf Facilities Administration...........................................................................................565
9.7 Database backup and restore from remote file server on 1662 subshelf........................................569
9.8 1662 subshelf PM Administration (E1) ............................................................................................571
9.9 1662 subshelf PM Administration (STM4).......................................................................................573
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
10.14 LAG Management ..........................................................................................................................602

10.15 VLAN protocol profile Management ...............................................................................................605
10.16 VPLS Instance Management ..........................................................................................................608
A Software Reference Guide.........................................................................................................................611

A.1 Introduction......................................................................................................................................611
A.2 Access Identifiers ............................................................................................................................611
A.3 States ..............................................................................................................................................627
A.4 Codes..............................................................................................................................................629
A.5 Security ...........................................................................................................................................652
A.6 Performance Monitoring..................................................................................................................656
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
Table 32 CCT usage rules depending on TUSegment DIR parameter ...........................................................535

Table 33 CrsTuSeg allowed when FROM=TO ................................................................................................535
Table 34 T-MPLS PM counters foreseen for PWSEG and TUSEG ................................................................553
Table 35 Primary Equipment Values ...............................................................................................................627
Table 36 Secondary Equipment Values (TL1 3.0)...........................................................................................628
Table 37 1850 TSS-320, TSS-320H and TSS-160 Equipment Condition Types ............................................629
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type Codes...................634
Table 39 Transient Condition Type Codes ......................................................................................................646
Table 40 Notification Codes ............................................................................................................................646
Table 41 Service Affect Codes ........................................................................................................................647
Table 42 Response (Error) Codes ..................................................................................................................647
Table 43 Command Parser Error Codes.........................................................................................................651
Table 44 Number of Registers for Each PM Parameter Monitored.................................................................657
Table 45 GBE PM Parameters........................................................................................................................659
Table 46 OTU2 PM Parameters......................................................................................................................660
Table 47 ODU2 PM Parameters .....................................................................................................................660
Table 48 10GBE PM Parameters....................................................................................................................661
Table 49 10GFC PM Parameters....................................................................................................................661
Table 50 STM-n (n = 1, 4, 16, 64) PM Parameters .........................................................................................661
Table 51 VC4n (n = 4C, 16C, 64C) PM Parameters .......................................................................................662
Table 52 LOVCn (n = 3, 12) PM Parameters ..................................................................................................663
Table 53 MAU PM Parameters .......................................................................................................................665
Table 54 User Command Privilege Defaults ...................................................................................................665
Table 55 SFPs and the XFPs ProvisionedType allowed per IOC Card...........................................................681
Table 56 1850 TSS-160 Supported Modules ..................................................................................................686
Table 57 1850 TSS-320 Supported Modules ..................................................................................................687
Table 58 Supported SFP/XFP Optics Modules - Line Side .............................................................................690
Table 59 Supported SFP/XFP Optics Modules - Client Side...........................................................................692
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
Figure 32 MEP/MIP configuration for loopback connectivity verification..........................................................472

Figure 33 Diagnostic loopback.........................................................................................................................479
Figure 34 Discovery loopback - target = MEP .................................................................................................486
Figure 35 Discovery loopback - target = MIP...................................................................................................487
Figure 36 Fig1. Link Aggregation concept .......................................................................................................603
Figure 37 1850 TSS-160 Shelf Slot Locations .................................................................................................687
Figure 38 1850 TSS-320 Shelf Slot Locations .................................................................................................690
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
List of procedures
2.2 TL1 and CLI sessions ..............................................................................................................................49
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.23 PW Termination Management (Case of VPLS) .......................................................................................97
4.24 Tunnel Protection Management (Label swap and Tunnel not Terminated)..............................................98
4.25 VCG Deprovisioning ..............................................................................................................................100
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
4.26 VCG Provisioning ..................................................................................................................................100
4.27 VPLS Deprovisioning.............................................................................................................................102
4.28 VPLS Provisioning .................................................................................................................................102
4.29 UGW Protection Provisioning ................................................................................................................104
5.2 Administer T-MPLS Control Plane Global Parameters ..........................................................................110
5.3 Administer Control Plane - Control Routing Port....................................................................................111
5.4 Administer Control Plane - IP Route ......................................................................................................115
5.5 Administer Control Plane - Tranport Port ...............................................................................................119
5.6 Administer Control Plane - OSPF routing ..............................................................................................122
5.7 Administer CP Tunnels - Make Before Break ........................................................................................125
5.8 Administer Control Plane Hoplist ...........................................................................................................129
6.2 Add New User to System.......................................................................................................................138
6.3 Administer ASAP ...................................................................................................................................139
6.4 Administer Duplex Switching Equipment Protection Group...................................................................143
6.5 Administer Duplex Switching ATM Protection Group.............................................................................147
6.6 Administer Database Backup ................................................................................................................150
6.7 Administer Database Restore ...............................................................................................................152
6.8 Administer Ethernet Facility ..................................................................................................................155
6.10 Administer Line Optical Connection Management.................................................................................163
6.11 Administer PassThrough Optical Connection Management ..................................................................167
6.12 Administer Cascade Optical Connection Management .........................................................................171
6.13 Administer ADD/DROP Optical Connection Management.....................................................................175
6.14 Administer GBE10 Loopback.................................................................................................................179
6.15 Administer GBE Loopback.....................................................................................................................183
6.16 Administer L2 Encapsulation Profile ......................................................................................................186
6.17 Administer MAC FILE COLLECTION ....................................................................................................190
6.18 Administer MAU Facility.........................................................................................................................193
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
6.19 Administer MAU Loopback ....................................................................................................................195
6.20 Administer Network Interface.................................................................................................................199
6.21 Administer NE IP Route.........................................................................................................................200
6.22 Administer NE IP Tunnel........................................................................................................................203
6.23 Administer Network Time Protocol (NTP) ..............................................................................................207
6.24 Administer STMn Neighbor Discovery ...................................................................................................211
6.25 Administer ODU2 Facility.......................................................................................................................212
6.26 Administer OTU2 Facility .......................................................................................................................218
6.27 Administer Path Protected Cross-Connection .......................................................................................224
6.28 Administer Per Hop Behaviour Profile (PHBprofile)...............................................................................227
6.29 Administer Radius server.......................................................................................................................229
6.30 Administer Security Log File ..................................................................................................................232
6.31 Administer STMn Facility .......................................................................................................................235
6.32 Administer STM-n Facility Protection Group..........................................................................................237
6.33 Administer STMn Loopback ..................................................................................................................241
6.34 Administer STMn MS-SPRING..............................................................................................................245
6.35 Administer System Configuration ..........................................................................................................253
6.36 Administer System Timing/BITS ............................................................................................................255
6.37 Administer Clock references - Synchronization .....................................................................................258
6.38 Administer Users with Security Administrator Privileges .......................................................................263
6.39 Administer VC Cross-Connection ..........................................................................................................267
6.40 Administer VCG Facility.........................................................................................................................277
6.41 Auto Discovery Function........................................................................................................................284
6.42 Boundary TOD Card administration.......................................................................................................285
6.43 Change Facility Service State................................................................................................................293
6.44 Change User Password.........................................................................................................................294
6.45 Convert a Cross-Connection .................................................................................................................296
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
6.46 Delete User from System.......................................................................................................................308
6.47 Deprovision Equipment..........................................................................................................................308
6.48 Disable/Enable User Account ................................................................................................................314
6.49 Display Alarms .......................................................................................................................................319
6.50 Display MPLS interface parameters ......................................................................................................328
6.51 Display Status and Conditions...............................................................................................................329
6.52 Edit User Profile.....................................................................................................................................337
6.53 Housekeeping Alarms Management......................................................................................................341
6.54 Housekeeping Controls Management ...................................................................................................345
6.55 Initialize System Processors..................................................................................................................348
6.56 LCAS Monitoring....................................................................................................................................351
6.57 Log Into System.....................................................................................................................................354
6.58 Log Out of System .................................................................................................................................355
6.59 Master TOD Card Management ............................................................................................................357
6.61 Optical Intrusion Adminstration ..............................................................................................................364
6.62 Perform Audible Alarm Cutoff ................................................................................................................366
6.63 Perform Module Protection Switch or Copy Switch ...............................................................................367
6.64 Perform Remote Database Backup .......................................................................................................369
6.65 Perform Remote Database Restore ......................................................................................................375
6.66 Port segregation Management ..............................................................................................................382
6.67 Provision Equipment..............................................................................................................................385
6.68 Radius server authentication ordering ...................................................................................................390
6.69 Remove/Restore Equipment..................................................................................................................393
6.70 Report Performance Monitoring (PM) Data ...........................................................................................397
6.71 Retrieve and Change Site Identifier.......................................................................................................400
6.72 Retrieve Module Remote Inventory Information ....................................................................................402
6.73 Retrieve Section Trace ..........................................................................................................................404
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
6.74 Retrieve System Configuration ..............................................................................................................406
6.75 Retrieve TL1 Command Syntax.............................................................................................................409
6.76 Retrieve User Session Information ........................................................................................................410
6.77 Retrieve/Provision IP Address of NE .....................................................................................................414
6.78 Security Defaults Administration ............................................................................................................417
6.79 Set Performance Monitoring (PM) Mode ...............................................................................................419
6.80 Set Performance Monitoring (PM) Threshold Levels.............................................................................421
6.81 Slave TOD Card Management ..............................................................................................................424
6.82 Set System Date and Time ....................................................................................................................430
6.83 Set System-Wide User Security Parameters.........................................................................................432
6.84 Switch STMn Line to Protection.............................................................................................................434
6.85 Switch VCn Line to Protection ...............................................................................................................437
6.86 System Access Control (intrusion alarm)...............................................................................................439
6.88 Virtual Concatenation Path Check.........................................................................................................442
6.89 Modify Equipment Management for Data units......................................................................................444
7.2 Provision Equipment (S320H) ...............................................................................................................451
7.3 Administer S320H module .....................................................................................................................455
8.2 Administer MPLS-TP Loopback OAM tool ............................................................................................464
8.3 Administer MPLS-TP Connectivity verification Loopback OAM tool .....................................................471
8.4 Administer MPLS-TP Diagnostic Loopback OAM tool ..........................................................................479
8.5 Administer MPLS-TP Discovery Loopback OAM tool ...........................................................................486
8.6 Administer (T-MPLS/MPLS-TP) DM tool ..............................................................................................491
8.7 Administer T-MPLS Facility Protection Group .......................................................................................497
8.8 Administer T-MPLS Global Network Parameters...................................................................................502
8.9 Administer T-MPLS/ MPLS-TP Node configuration ...............................................................................504
8.10 Administer T-MPLS OAM (T-MPLS Tunnel protection)..........................................................................507
8.11 Administer T-MPLS Pseudo Wire ..........................................................................................................510
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
8.12 Administer T-MPLS Pseudo Wire Segment...........................................................................................514
8.13 Administer T-MPLS Pseudo Wire Segment Cross-Connection .............................................................517
8.14 Administer T-MPLS Traffic Descriptor....................................................................................................521
8.15 Administer T-MPLS Tunnel ....................................................................................................................524
8.16 Administer TMPLS Tunnels Group ........................................................................................................528
8.17 Administer T-MPLS Tunnel Segment.....................................................................................................531
8.18 Administer T-MPLS Tunnel Segment Cross-Connection.......................................................................535
8.19 Proactive DM ........................................................................................................................................538
8.20 Proactive LM (Synthetic Loss Measurement) ........................................................................................543
8.21 Report Performance Monitoring (PM) Data for T-MPLS ........................................................................550
8.22 Set Performance Monitoring (PM) Data for T-MPLS .............................................................................552
9.3 1662SMC drop shelf management ........................................................................................................559
9.4 Administer 1662 Subshelf E1 cards.......................................................................................................561
9.6 1662 Subshelf Facilities Administration .................................................................................................565
9.7 Database backup and restore from remote file server on 1662 subshelf ..............................................569
9.8 1662 subshelf PM Administration (E1)...................................................................................................571
9.9 1662 subshelf PM Administration (STM4) .............................................................................................573
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
10.12 General Interface Management .............................................................................................................599
10.13 L2 control frames management (in Provider Bridge) .............................................................................600
10.14 LAG Management .................................................................................................................................602
10.15 VLAN protocol profile Management ......................................................................................................605
10.16 VPLS Instance Management .................................................................................................................608
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
About this document

Purpose
This document provides the information and procedures necessary to install, self-test and turn up
the 1850 Transport Service Switch TSS-320, TSS-320H and TSS-160 (1850 TSS-320, TSS-320H
and TSS-160) system.
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.
This information product is intended for the following users:

• Technicians
• Network providers
• Operators
• Maintenance personnel
How to use this document

Each chapter of this guide treats a specific aspect of the system and can be regarded as an
independent description. This ensures that readers can inform themselves according to their special
needs. Before you start reading the manual, it is therefore necessary to assess which aspects or
chapters will cover the individual area of interest.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
Table 1 Chapter contents
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
Table 1 Chapter contents (continued)
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
Adhere to the following safety precautions:

• Electrostatic discharge (ESD)
You must be properly grounded when making contact with the 1850 Transport Service Switch
TSS-320, TSS-320H and TSS-160 frame and handling circuit packs, disk drives, and tapes.
Wrist strap ground cords should be routinely tested for the minimum 1-megohm resistance.
• Plug-in storage
Circuit packs should be stored in static-safe packaging or in a grounded cabinet.
For additional safety precautions, please see the 1850 Transport Service Switch (TSS-320, TSS-
320H and TSS-160) Release 5.1 Safety Guide, 8DG09603GAAATQZZA.
Admonishments
To avoid hazardous conditions, observe the following admonishments:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
DANGER
Optional Content
Possibility of personal injury.
Optional Content added above. Please modify as needed.
WARNING
Optional Content
Possibility of equipment damage.
NOTICE
Optional Content
Possibility of service interruption.
Packaging collection and recovery requirements

Countries, states, localities, or other jurisdictions may require that systems be established for the
return and/or collection of packaging waste from the consumer, or other end user, or from the waste
stream. Additionally, reuse, recovery, and/or recycling targets for the return and/or collection of the
packaging waste may be established.
For more information regarding collection and recovery of packaging and packaging waste within
specific jurisdictions, please contact the Nokia Field Services/Installation - Environmental Health
and Safety organization.
For installations not performed by Nokia, please contact the Nokia Customer Support Center at:
Technical Support Services, Nokia

• Within the United States: 1 (866) 582-3688, prompt 1
• From all other countries: +1 (630) 224 4672, prompt 2
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
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)
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
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).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Line Command User's Interface Introduction
1 Line Command User's Interface Introduction
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.2 Writing Conventions

Boldface characters indicate commands or parameters that must be entered or keys that must be
pressed. Enter input parameters exactly as shown in the examples.
1.1.3 Related Documentation

For additional system information, refer to the “About this document” on “About this document”
1.1.4 Document Types

The documentation contains all instructions needed to perform a task.
This manual consists of the following types of documents:

• Task Index List (IXL)
IXLs group procedures by function. Each IXL lists procedures alphabetically by name and refers
the user to the appropriate procedure number.
• Nontrouble Procedure (NTP)
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.
• Detailed Level Procedure (DLP)
DLPs 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.
• CLI Procedure (CLIP)
CLIPs contain detailed steps and supporting information required to complete a task. When a
CLIP is referenced from another part of the manual, perform the CLIP, then return to the point
where the CLIP was referenced. Generally CLIP are to be used during DLPs execution.
Release 5.1 (ETSI)

September 2017
Overview 1850 TSS-320/TSS-320H/TSS-160
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Structure of safety statements
TL1 and CLI overview
1.2 Structure of safety statements

1.2.1 Overview
This topic describes the components of safety statements that appear in this document.
1.2.2 General structure

Safety statements include the following structural elements:
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]
Item Structure element Purpose

1 Safety alert symbol Indicates the potential for personal injury
(optional)
2 Safety symbol Indicates hazard type (optional)
3 Signal word Indicates the severity of the hazard
4 Hazard type Describes the source of the risk of damage or
injury
5 Safety message Consequences if protective measures fail
6 Avoidance message Protective measures to take to avoid the hazard
7 Identifier The reference ID of the safety statement
(optional)
Release 5.1 (ETSI)

September 2017
TL1 Command Structure and Syntax 1850 TSS-320/TSS-320H/TSS-160
1.2.3 Signal words

The signal words identify the hazard severity levels as follows:
Signal word Meaning

DANGER Indicates an extremely hazardous situation which, if not avoided, will
result in death or serious injury.
WARNING Indicates a hazardous situation which, if not avoided, could result in
death or serious injury.
CAUTION Indicates a hazardous situation which, if not avoided, could result in
minor or moderate injury.
NOTICE Indicates a hazardous situation not related to personal injury.
1.3 TL1 Command Structure and Syntax

1.3.1
Command syntax refers to rules that govern Transaction Language 1 (TL1) command element
arrangement; that is, how elements are delimited or separated using special characters and
punctuation.
For the system to understand a command entered in Direct mode, the precise command structure
and syntax must be entered.
A complete TL1 command consists of the following elements:

• Command code: specifies an action the command performs and the object or nature of that
action.
• Input parameters: directs a command to the appropriate processing environment or supplies the
data required to execute the command. Parameters can be either required or optional depending
on the command.
• Special characters and punctuation: identify command elements, separate each element, and
end each command.
1.3.2 Command Code

The command code contains up to three elements: a verb and one or two verb modifiers. A hyphen
separates each element of a command. Command codes are usually abbreviations of the meaning
of the command.
An example of a command code is ENT-CRS-STS1. In this example, the first element, ENT, is a
verb that specifies the action Enter. Up to two modifiers can follow; these modifiers refer to data,
such as a database in the system, an internal software subsystem, or a physical entity (such as an
equipment or circuit type). In this case, the first modifier is CRS for cross-connection, which is the
type of action. The second modifier is STS1, which is the object of the cross-connection.
ENT-CRS-STS1 connects an incoming STS-1 circuit to an outgoing STS-1 circuit in the switching
environment. The command code, however, does not specify which circuits to connect. Input
parameters supply the additional information needed to execute the command.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 TL1 Command Structure and Syntax
1.3.3 Input Parameters
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.
Release 5.1 (ETSI)

September 2017
TL1 Command Structure and Syntax 1850 TSS-320/TSS-320H/TSS-160
• 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.
1.3.4 Special Characters

TL1 uses characters that have special meanings depending on where the characters appear or how
they are used. Refer to table 2-A for the characters used with commands, parameters, and output
messages.
Table 2 TL1 Special Characters
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 TL1 Command Structure and Syntax
Table 2 TL1 Special Characters (continued)
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.
1.3.5 Ranging and Grouping

The AID parameter of specific commands lets ranging and grouping generate a range of AID
values, a list of AID values, or a combination of both.
The string &&- (double ampersand and hyphen) specifies a range of AID values (&&-ranging), while
&- (single ampersand and hyphen) specifies a list of AID values (&-grouping).
The &&-ranging supports numeric ranging on multiple arguments of a compound AID parameter
(the information units in the AID). The range must fully define the first AID value (for example,
OC48STS1-1-3-1-1-2-3), while the range argument must end with the numeric argument of the
last AID value in the range (with the preceding hyphen after the ampersands; for example, &&-3,
&&-10, and so on). The expanded range of AIDs always includes the first and last AID values of the
sequential series specified by the range. AID formats cannot be combined for different entity types
(that is, an STS-1 AID format and an OC-48 AID format) when specifying &&-ranging.
An example of STS-1 &&-ranging is: OC48STS1-1-3-2-1-2-1&&-3. This is understood by the
system as OC48STS1-1-3-2-1-2-1, OC48STS1-1-3-2-1-2-2, and
OC48STS1-1-3-2-1-2-3.
Ranged sequences increment by N, and the system default is N=1. To change the value of N, enter
.++.N after the range. For example, OC48-1-3-2-1&&-5.++.2 is understood by the system as
OC48-1-3-2-1, OC48-1-3-2-3, and OC48-1-3-2-5. The range ends at the highest value less
than or equal to the end value; OC48-1-3-2-1&&-6.++.2 is also understood as
OC48-1-3-2-1, OC48-1-3-2-3, and OC48-1-3-2-5.
Release 5.1 (ETSI)

September 2017
TL1 System Messages 1850 TSS-320/TSS-320H/TSS-160
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.
1.3.6 Executing a Command in Direct Mode
To execute a command in Direct mode, perform the following steps:

1. Enter command code and at least all required parameters. Use precise syntax. The system will
not execute a command that is entered with any syntax mistakes.
2. Press ; (semicolon) or Return.
The system processes the command and displays a successful response message if the
command executed properly. The next command may be entered at the next prompt.
End of steps
1.4 TL1 System Messages

1.4.1
When the system processes a command, it returns a specific type of message to indicate the status
of the request. These message types include: successful and unsuccessful response messages,
in-progress messages, and alarm messages.
1.4.2 Response Messages

When a command is entered, the system processes it and then returns either a successful
response message if the command executed properly or an unsuccessful response message if the
command failed. The system records all command transactions, successful and unsuccessful, in
the system's Audit Log.
For more information on the Audit Log, refer to the Appendix A, “Software Reference Guide” in the
back of this manual.
Successful response messages have the following general content and format:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 TL1 System Messages
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:
ALU-1850 2006-06-17 15:10:04

M 32 COMPLD
/* RTRV-HDR */
;
Unsuccessful response messages have the following general content and format:
Release 5.1 (ETSI)

September 2017
TL1 System Messages 1850 TSS-320/TSS-320H/TSS-160
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:
ALU-1850 2006-06-17 15:10:04

M 23 DENY
IDNV
/* Data Not Valid */
;
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 CLI Command Structure and Syntax
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 are a few common reasons why commands fail:

• User command privileges are invalid for the command entered.
• Command format, syntax, or parameter data is incorrect.
• Command is invalid.
• Equipment is in an invalid state for the command.
1.4.3 In-Progress Messages

If the system does not complete a command within 2 seconds, it automatically generates an in-
progress message to acknowledge that the command is being processed. In-progress messages
do not interrupt other output responses.
1.4.4 Alarm Messages

Alarm notifications are sent to active login sessions (with alarm output subscription level) in
standard TL1 format.
An example:
ALU-1850 2006-06-17 15:10:04

*C 17 REPT ALM EQPT
"8XSO-1-1-3:CR,IMPROPRMVL,SA,06-17,15-10-04,NEND"
;
1.5 CLI Command Structure and Syntax

1.5.1
The resource naming format implementation has to be designed open to meet different format
requirements.
It has to be taken into account that each naming format can use own specific symbols for "AND
operation", "range interval", "list elements separation".
This Handbook considers only one naming format which is coherent with the operator label
specification document and uses ampersand ( & ), hyphen ( - ), comma ( , ) for respectively "AND
operation", "range interval", "list elements separation".
1.5.2 List of defined indexes
The following indexes are defined for indicating specific resources inside CLI commands:
1. ace_index An integer value indicating an element of an ACL.
Release 5.1 (ETSI)

September 2017
CLI Command Structure and Syntax 1850 TSS-320/TSS-320H/TSS-160
2. aceorder_number An integer value, indicating the ordering position of execution of an Access

Control Element in an ACL.
3. adminkey_value An integer value in the range [1 ... 124].
4. admitted_fractional_rate An integer value, indicating in Kbit/s the threshold value of the
admitted bandwidth on the interface; it is used for triggering PAUSE frames generation.
5. bridge_forward_delay The Bridge Forward Delay used by STP to transition Root and
Designated Ports to Forwarding; an integer value, measured in 0.01seconds, in the range [400
... 3000] with default value=1500.
6. bridge_hello_time The interval between periodic transmissions of Configuration Message
by Designated Ports; an integer value, measured in 0.01seconds, in the range [100 ... 200] with
default value=200.
7. bridge_max_age The maximum age of the information transmitted by the Bridge when it is
the Root Bridge; an integer value, measured in 0.01seconds, in the range [600 ... 4000] with
default value=2000.
8. bridge_pri Writable portion of the bridge identifier (the first 2 byte of 8 byte); an integer value
in the range [0 ... 61440] with granularity 4096 and default value=32768.
9. cbs_value An integer number, in the range [0 ... 64 MB] with 1 byte granularity.
10. cir_value An integer number, in the range [3 kbit/s ... port line rate] with 1 kbit/s granularity.
11. classifier_id An integer number, indicating the specific ETS InFlow classifier.
12. confseverity, confseveritynsa The configured severity or severity "non-service
affecting" in the set: critical, major, minor, warning, indeterminate and cleared.
13. ctrl_frame_32bits It identifies the control frame types for managing their passing through
or discarding and it has the following syntax:
[customerbpdu] [providerbpdu] [slowprot] [802.1x] [providergvrp]
[customergmrp] [customergarp] [bridgemgt] [reserved]
This parameter selects to which control frame types the command {pass | drop} applies.
If no optional parameter is present, it means all control frames.
Inside the MIB, this information is mapped in a 32 bits string in which each bit (located in
position 0 ... 31 with 0 being most significant bit) indicates if the frame type represented by this
bit (0 ... 31) is discarded (bit=0) or passed (bit=1). Data frame have to be always passed. Bit
mapping is defined in the Table 3, “Bit Mapping” (p. 44).
14. directorypath The directory of the server in which the SW to be downloaded is stored. It
has the form disk/folder/sub-folder/.../sub-folder where the last sub-folder contains the software
package.
15. domain_name The domain name in the set: 'eqpt', 'ts' and 'pm'.
16. dscp An integer value in the set [0 ... 63], indicating the DSCP value (or the lower bound of
a DSCP range).
17. dscp_set An expression using integer values in the range [0 ... 63], and specific symbols for
representing set of DSCP value ranges which are associated to "green" in that color profile.
For instance, 12-15&55 means that the DSCP values 12, 13, 14, 15 and 55 are associated to
'green' in that color profile.
Release 5.1 (ETSI)

September 2017
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.
Release 5.1 (ETSI)

September 2017
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.
Release 5.1 (ETSI)

September 2017
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.
Release 5.1 (ETSI)

September 2017
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].
1.5.3 List of indexes defined by user
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.
Table 3 Bit Mapping
Protocol Description MAC Address Bit

Data Frames -- 0
Customer BPDU (STP, RSTP, MSTP) 01-80-C2-00-00-00 1
Provider BPDU (STP, RSTP, MSTP) 01-80-C2-00-00-08 2
Slow Protocols 01-80-C2-00-00-02 3
802.1X PAE 01-80-C2-00-00-03 4
Reserved for future MAC applications 01-80-C2-00-00-04 5
Reserved for future MAC applications 01-80-C2-00-00-05 6
Reserved for future bridge applications 01-80-C2-00-00-06 7
Reserved for future bridge applications 01-80-C2-00-00-0A 10
Reserved for future Provider bridge operations 01-80-C2-00-00-0B 11
Release 5.1 (ETSI)

September 2017
Table 3 Bit Mapping (continued)
Protocol Description MAC Address Bit

Reserved for future Provider bridge operations 01-80-C2-00-00-0C 12
Provider GVRP 01-80-C2-00-00-0D 13
Reserved for future Customer bridge operations 01-80-C2-00-00-0E 14
Reserved for future Customer bridge operations 01-80-C2-00-00-0F 15
Bridge Management 01-80-C2-00-00-10 16
Customer GMRP 01-80-C2-00-00-20 17
Customer GARP 01-80-C2-00-00-21 18
Reserved for future GARP applications 01-80-C2-00-00-22 to 19 to
01-80-C2-00-00-2F 32
Table 4 Alarm and cause relationship
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
Release 5.1 (ETSI)

September 2017
Conventions used in CLI command definition 1850 TSS-320/TSS-320H/TSS-160
Table 4 Alarm and cause relationship (continued)
Alarm pcause
LOF lof
CSF csf
EXM extensionheadermismatch
UPM userpayloadmismatch
URU uru
UAT uat
TCA tca
1.6 Conventions used in CLI command definition

1.6.1
The following conventions are used in CLI command definition.

1. Several commands require operator to define a user label. The node must assure that user
labels for a specified resource are unambiguous.
2. Operator can define user labels containing blank characters. In this case, the string must be in
inverted commas (e.g. ext point in 2 user label "physical LOS housekeeping").
3. The ASAP configuration commands require operator to enter the ASAP user label instead of the
ASAP index, for simplicity sake.
4. In some commands, the bridge port is referenced by the bridge port number.
5. When an optional value in a command is not provided by the operator, the corresponding
currently configured value remains unchanged (if no value had been previously configured the
default value applies). In the commands where a different behavior is applied, it is explicitly
stated.
6. The CLI command is atomic. If any command parameter setting fails, the entire command is
rejected.
7. For commands, which set parameters that are modifiable only when a certain resource is
administratively disabled, it is required to check if this condition is satisfied and, if not, to reject
the command advising properly the operator.
8. If a CLI command fails, the error code currently defined for the corresponding management
function failure has to be reported to the operator.
9. Any parameter, that is retrievable by a show command but that is not significant in a specific
scenario in which the command has been applied, is neglected in the show report.
10. The show command must support the optional more parameter at the end of the command for
showing information by 24rows pages. For simplicity sake, [more] is not repeated in all show
commands along the document.
11. Some commands requires a confirmation for allowing operator an after-editing verification.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Answers to CLI commands
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.
1.6.2 Considerations about functionalities supported by CLI
Not supported functionalities
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.
CLI does not cover also the following management functions:

• Support Domain:
− Condition of Configuration Mode
− Inhibit/Allow Logging
1.7 Answers to CLI commands

1.7.1
The following examples are referred to some answers from the equipment when a CLI command is
forwarded and are relevant or to correct/wrong commands or to incomplete commands.
Note: Some CLI commands do not get answers.
>> message: successful completed command ||
>> message: waiting - command in progress

>> error: timeout rot executed command
Release 5.1 (ETSI)

September 2017
Answers to CLI commands 1850 TSS-320/TSS-320H/TSS-160
>> warning: already present value for AdminStatus of rlsrls16d1p1

>> error: bad command
>> error: missing parameter
>> error: invalid parameter number
Error: Out of range. Valid range: dynamic, blocked, forwarding
>> error: db writing error for Stp BridgeHelloTime

>> message: partially completed command
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Getting started
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 TL1 and CLI sessions

2.2.1 Purpose
Purpose of this paragraph is to describe procedures needed to activate the command console in
order to use the TL1 and CLI commands.
2.2.2 Tools
For the these procedures the following tools are necessary:
Table 5 Necessary tools
Item description Feature P/N or suggested

ETH cable LAN cable (RJ45 male both side) 8DG 08351 AAAA
Figure 1 LAN cable
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.
Release 5.1 (ETSI)

September 2017
TL1 and CLI sessions 1850 TSS-320/TSS-320H/TSS-160
Figure 2 Connection to the interface
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:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 TL1 and CLI sessions
Figure 3 CMD console selection
3
Press OK button to activate the command console as shown in the following picture:
Figure 4 CMD console activation
Release 5.1 (ETSI)

September 2017
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:
Figure 5 Telnet session activation
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:
Release 5.1 (ETSI)

September 2017
Figure 6 Telnet console
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:
Figure 7 Logging the system
Release 5.1 (ETSI)

September 2017
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:
Figure 8 Successful login answer
8
Now it is possible to enter a command, e.g. with the RTRV-EQPT::ALL; the relevant response
is the following:
Release 5.1 (ETSI)

September 2017
Figure 9 Command response example
Release 5.1 (ETSI)

September 2017
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Task Index List (IXL)
3 Task Index List (IXL)
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
Release 5.1 (ETSI)

September 2017
IXL-1: User Administration 1850 TSS-320/TSS-320H/TSS-160
3.2 IXL-1: User Administration

3.2.1 Overview
Refer to Table 6, “Common User Administration Functions” (p. 57) to identify a common user
administration function and the corresponding procedure.
Table 6 Common User Administration Functions
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)
3.3 IXL-2: Equipment Functions

3.3.1 Overview
Refer to Table 7, “Equipment Functions” (p. 58) to identify an equipment function and the
corresponding procedure.
Table 7 Equipment Functions
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)
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 IXL-3: Equipment Provisioning and Deprovisioning
Table 7 Equipment Functions (continued)
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)
3.4 IXL-3: Equipment Provisioning and Deprovisioning

3.4.1 Overview
Refer to Table 8, “Equipment Provisioning and Deprovisioning” (p. 59) to identify an equipment
provisioning or deprovisioning function and the corresponding procedure.
Table 8 Equipment Provisioning and Deprovisioning
FUNCTION
6.47 “Deprovision Equipment” (p. 308)
6.67 “Provision Equipment” (p. 385)
6.72 “Retrieve Module Remote Inventory Information” (p. 402)
3.5 IXL-4: System Information Reports

3.5.1 Overview
Refer to Table 9, “System Information Reports” (p. 59) to identify a system information report and
the corresponding procedure for retrieval of the report.
Table 9 System Information Reports
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)
Release 5.1 (ETSI)

September 2017
IXL-5: System Administration 1850 TSS-320/TSS-320H/TSS-160
Table 9 System Information Reports (continued)
FUNCTION
6.75 “Retrieve TL1 Command Syntax” (p. 409)
6.76 “Retrieve User Session Information” (p. 410)
3.6 IXL-5: System Administration

3.6.1 Overview
Refer to Table 10, “System Administration” (p. 60) to identify a system administration function and
the corresponding procedure.
Table 10 System Administration
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)
6.82 “Set System Date and Time” (p. 430)
3.7 IXL-6: VCG Functions

3.7.1 Overview
Refer to Table 11, “VCG Functions” (p. 61) to identify an VCG function and the corresponding
procedure.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 IXL-7: T-MPLS/MPLS-TP Functions
Table 11 VCG Functions
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)
3.8 IXL-7: T-MPLS/MPLS-TP Functions

3.8.1 Overview
Refer to Table 12, “T-MPLS Functions” (p. 61) to identify a T-MPLS/MPLS-TP function and the
Table 12 T-MPLS Functions
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)
6.50 “Display MPLS interface parameters” (p. 328)
8.6 “Administer (T-MPLS/MPLS-TP) DM tool ” (p. 491)
Release 5.1 (ETSI)

September 2017
IXL-8: VC & LOVC Functions 1850 TSS-320/TSS-320H/TSS-160
Table 12 T-MPLS Functions (continued)
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)
3.9 IXL-8: VC & LOVC Functions

3.9.1 Overview
Refer to Table 13, “VC & LOVC Functions” (p. 62) to identify an VC & LOVC function and the
Table 13 VC & LOVC Functions
FUNCTION
6.39 “Administer VC Cross-Connection” (p. 267)
6.45 “Convert a Cross-Connection” (p. 296)
3.10 IXL-9: SDH Functions

3.10.1 Overview
Refer to Table 14, “SDH Functions” (p. 62) to identify an SDH function and the corresponding
procedure.
Table 14 SDH Functions
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)
3.11 IXL-10: ODU Functions

3.11.1 Overview
Refer to Table 15, “ODU Functions” (p. 63) to identify an ODU function and the corresponding
procedure.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 IXL-11: OTU Functions
Table 15 ODU Functions
FUNCTION
6.25 “Administer ODU2 Facility” (p. 212)
4.17 “ODU2 Deprovisioning” (p. 92)
4.18 “ODU2 Provisioning” (p. 93)
3.12 IXL-11: OTU Functions

3.12.1 Overview
Refer to Table 16, “OTU Functions” (p. 63) to identify an OTU function and the corresponding
procedure.
Table 16 OTU Functions
FUNCTION
6.26 “Administer OTU2 Facility” (p. 218)
4.19 “OTU2 Deprovisioning” (p. 94)
4.20 “OTU2 Provisioning” (p. 94)
3.13 IXL-12: Ethernet Functions

3.13.1 Overview
Refer to Table 17, “Ethernet Functions” (p. 63) to identify an Ethernet function and the
Table 17 Ethernet Functions
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)
Release 5.1 (ETSI)

September 2017
IXL-13: Maintenance Operation 1850 TSS-320/TSS-320H/TSS-160
3.14 IXL-13: Maintenance Operation

3.14.1 Overview
Refer to Table 18, “ Maintenance Operation Functions” (p. 63) to identify a maintenance operation
and the corresponding procedure.
Table 18 Maintenance Operation Functions
FUNCTION
6.45 “Convert a Cross-Connection” (p. 296)
3.15 IXL-14: Control Plane Functions

3.15.1 Overview
Refer to Table 19, “Control Plane Functions” (p. 64)to identify a TMPLS Control Plane function and
the corresponding procedure..
Table 19 Control Plane Functions
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)
3.16 IXL-15: WDM Functions

3.16.1 Overview
Refer to Table 20, “WDM Functions” (p. 64)to identify a WDM functions and the corresponding
procedure.
Table 20 WDM Functions
FUNCTION
6.10 “Administer Line Optical Connection Management” (p. 163)
6.11 “ Administer PassThrough Optical Connection Management” (p. 167)
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 IXL-16: ATM Functions
Table 20 WDM Functions (continued)
FUNCTION
6.12 “ Administer Cascade Optical Connection Management” (p. 171)
6.13 “ Administer ADD/DROP Optical Connection Management” (p. 175)
3.17 IXL-16: ATM Functions

3.17.1 Overview
Refer to Table 21, “ATM Functions” (p. 65)to identify ATM functions and the corresponding
procedure.
Table 21 ATM Functions
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)
3.18 IXL-17:Security Functions

3.18.1 Overview
Refer to Table 22, “ Security Functions” (p. 65) to identify a security operations and the
Table 22 Security Functions
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)
Release 5.1 (ETSI)

September 2017
IXL-18: 1662 Drop Shelf Equipment Functions 1850 TSS-320/TSS-320H/TSS-160
3.19 IXL-18: 1662 Drop Shelf Equipment Functions

3.19.1 Overview
Refer to Table 23, “1662 Drop Shelf Equipment Functions” (p. 65) to identify a 1662 drop shelf
equipment function and the corresponding procedure.
Table 23 1662 Drop Shelf Equipment Functions
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)
3.20 IXL-19: Enhanced Shelf Equipment Functions

3.20.1 Overview
Refer to Table 24, “S320 Shelf Equipment Functions” (p. 66) to identify an enhanced shelf
equipment function and the corresponding procedure.
Table 24 S320 Shelf Equipment Functions
FUNCTION
7.2 “Provision Equipment (S320H)” (p. 451)
7.3 “Administer S320H module” (p. 455)
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Nontrouble Procedure (NTP)
4 Nontrouble Procedure (NTP)
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
Release 5.1 (ETSI)

September 2017
ATM Protection Provisioning 1850 TSS-320/TSS-320H/TSS-160
4.23 PW Termination Management (Case of VPLS) 97

4.24 Tunnel Protection Management (Label swap and Tunnel not Terminated) 98
4.25 VCG Deprovisioning 100
4.26 VCG Provisioning 100
4.27 VPLS Deprovisioning 102
4.28 VPLS Provisioning 102
4.29 UGW Protection Provisioning 104
4.2 ATM Protection Provisioning

4.2.1 Purpose
This procedure provides an ATM facility (and protection) provisioning example.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 ATM Protection Provisioning
4.2.3 General
Figure 10 Functional architecture of the Multiservice ATM Collector card
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:
SDH board e SFP creation:

• ENT-EQPT::8XSO-1-1-35:1:::PROVISIONEDTYPE=8PSO:;
• ENT-EQPT::SFP-1-1-35-1:1:::PROVISIONEDTYPE=SS-11:;
ATM board provisioning:

• ENT-EQPT::PP10AD-1-1-19:1:::PROVISIONEDTYPE=PP10GATM:;
Release 5.1 (ETSI)

September 2017
ATM Protection Provisioning 1850 TSS-320/TSS-320H/TSS-160
This command creates 32 ATM interfaces (one side TDM and the other side SNMP)
DATA board and SFP provisioning:

• ENT-EQPT::PP1GE-1-1-5:1:::PROVISIONEDTYPE=PP1GE:;
• ENT-EQPT::SFP-1-1-5-1:1:::PROVISIONEDTYPE=ANY-DATAS:;
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).
Note: On CLI side enter:

Interface show
The result of this command is something like: r1sr1sl5d0p1 atm (37)
For details refer to 8DG09603EAAATQZZA 1850 Transport Service Switch (TSS-320,
TSS-320H and TSS-160) Release 5.1 Command Line Interface Guide.
4
Create the PW, for details see 4.22 “PW Termination Management (Case of point-to-point)”
(p. 96).
Example:
CLI side create and activate the mpls port:

• interface position r1sr1sl5d0p1 localeth portservice mpls
• interface position r1sr1sl5d0p1 localeth activate
TL1 side create and activate Tunnel, Traffic descriptor, PW:

• ENT-TMPLS-TUSEG:::::MPLSIF-1-1-5-1,TERMINATION,BIDIR:INLABEL=5000,
OUTLABEL=5000,MEP=ENABLE,MEG-ID=WRK,MEP-ID=1,EXPMEP-ID=2,CVRX=
ENABLE,CVTX=ENABLE,CVPERIOD=3.33ms,CVPHB=EF;
• ENT-TMPLS-TD::::::CIR=1000000,PIR=1000000,CBS=1280000,PBS=1280000;
• ED-TMPLS-TUNNEL::TUNNEL-1-1-1-1-0-0-0-0-0-0-0-0::::TD-ID=MPLSTD-1,
STATUS=ON;
• ENT-TMPLS-PWSEG:::::TUSEG-1-1-1,TERMINATION,BIDIR:INLABEL=100,
OUTLABEL=100;
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Basic Control Plane TL1 Provisioning sequence
• 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:
atmflowunidir activate ATM_PW port1 r1sr1sl19d0p1 pw 1

inflowclassifier vpi 10 vci 20 trafficdescriptor GUA
6
Create the PW on ATM cross-connection, for details refer to 8DG09603EAAATQZZA
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 Basic Control Plane TL1 Provisioning sequence

4.3.1 Purpose
This procedure provides TL1 instructions and sequence to provision Basic Control Plane.
Release 5.1 (ETSI)

September 2017
Basic Control Plane TL1 Provisioning sequence 1850 TSS-320/TSS-320H/TSS-160
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.
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).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Bicast&Merge provisioning
• 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 Bicast&Merge provisioning

4.4.1 Purpose
This procedure provides instructions and sequence to provision BICAST&MERGE functionality.
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.
Via CLI side:

• Verify the ETS ports presence, see 10.12 “General Interface Management” (p. 599).
• 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).
Release 5.1 (ETSI)

September 2017
CP Provisioning 1850 TSS-320/TSS-320H/TSS-160
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).
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 CP Provisioning
All ports involved in the CP link should have MPLS interface.

The control plane signaling should be in band in fiber.
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.
The conditions for CP option are the followings:

• All involved ports must work at the same rate.
• All involved ports must have the same configurations, regarding AutoNegotiation and Flow
Control.
• All links must be point-to-point.
• All involved interfaces must work in full-duplex modality.
• All involved ports could be Local or Remote ports.
• Ports (local and far sides) must be of the same type. The control plane signaling could be: in
band in fiber, out band in fiber , out fiber.
4.5.4 Procedures
1
TL1 side:
Provision board and unit.
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).
Release 5.1 (ETSI)

September 2017
Ethernet Deprovisioning 1850 TSS-320/TSS-320H/TSS-160
• 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 Ethernet Deprovisioning

4.6.1 Purpose
This procedure provides instructions and sequence to deprovision an Ethernet facility.
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 Ethernet Provisioning

4.7.1 Purpose
This procedure provides instructions and sequence to provision an Ethernet facility.
4.7.2 Prerequisites
The node should be equipped with one of the following boards:
• 8XSO
• 10GSO
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 In Fiber In Band for Control Plan Provisioning
• 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.
Note: If the facility provisioning mode of this NE is automatic, i.e., PROVMODE=

AUTOEQ-AUTOFC, then this TL1 commands 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)). Automatically entered facilities are created with default
provisioning, with AINS active. Provisioning changes may be made to an automatically
entered ethernet facility using the TL1 edit commands.
4.7.4 Procedures
1
Provision board.
2
Provision Ethernet facility.
For details, refer to 6.8 “Administer Ethernet Facility ” (p. 155).
END OF STEPS
4.8 In Fiber In Band for Control Plan Provisioning

4.8.1 Purpose
This procedure provides instructions and sequence to create In Fiber In Band for Control plane.
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:
Release 5.1 (ETSI)

September 2017
LAG Deprovisioning 1850 TSS-320/TSS-320H/TSS-160
• VLAN basedIn Fiber In Band Management Interface;

• MPLS label basedIn Fiber In Band Management Interface
4.8.4 Procedures
1
Provision board and unit.
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 LAG Deprovisioning

4.9.1 Purpose
This procedure provides instructions and sequence to deprovision an LAG facility.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 LAG Provisioning
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 LAG Provisioning

4.10.1 Purpose
This procedure provides instructions and sequence to provision an LAG facility.
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.
The conditions for Link Aggregation option are the followings:

• All involved ports must work at the same rate.
• All involved ports must have the same configurations, regarding AutoNegotiation and Flow
Control.
• All aggregated links must be point-to-point (Multicast is not allowed).
• All involved interfaces must work in full-duplex modality.
• All involved ports must be Local (Remote ports are not allowed).
Release 5.1 (ETSI)

September 2017
LAG Provisioning 1850 TSS-320/TSS-320H/TSS-160
• 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.
The benefits of Link Aggregation feature are:

• Bandwidth limitation overcoming.
• Load balancing (the traffic is distributed over the constituting links).
• Reliability increasing (in case that a link of the aggregate fails, its traffic will be automatically
distributed over the other links of the aggregate).
4.10.4 Procedure
1
Provision board and the module.
Verify CLI side conditions for Link Aggregation:

• that the ETS ports created in the step before is present see 10.12 “General Interface
Management” (p. 599)
• Verify all ports that will belong to LAG have same mau configuration see 10.10 “ Ethernet
Port management (over MAU)” (p. 595) and 10.2 “ Administer Autonegotation” (p. 577)
• Create the LAG see 10.14 “ LAG Management ” (p. 602)
• Activate LAG see 10.14 “ LAG Management ” (p. 602), i.e. enable LAG administrative status
• Attach ports to the LAG see 10.14 “ LAG Management ” (p. 602)
• If necessary, modify LAG parameters see 10.14 “ LAG Management ” (p. 602)
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 LER Tunnel Management (Tunnel Terminated)
• 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 LER Tunnel Management (Tunnel Terminated)

4.11.1 Purpose
This procedure provides instructions and sequence to provision an LER Tunnel (i.e. tunnel
terminated).
4.11.3 General
4.11.4 Procedure
1
Via TL1:
Via CLI side:

• 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 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
Release 5.1 (ETSI)

September 2017
LSR Tunnel Management (Label swap and Tunnel not Terminated) 1850 TSS-320/TSS-320H/TSS-160
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.3 General
4.12.4 Procedure
1
Via TL1:
Via CLI side:

(p. 595).
Via TL1:
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).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 NE Secure mode configuration
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 NE Secure mode configuration

4.13.1 Purpose
This procedure provides instructions and sequence to configure the NE in SECURE mode.
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.3 Before you begin

The procedure described below can be performed only by a SECU-admin user. To create a SECU-
admin user please refer to 6.38 “Administer Users with Security Administrator Privileges” (p. 263).
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
Release 5.1 (ETSI)

September 2017
NE Unsecure mode configuration 1850 TSS-320/TSS-320H/TSS-160
use SFTP to transfer files to/from the NE.
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 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.
Note: SNMPv3 is supported on port 161.
Note: Telnet connections using (3082/3083/1123) ports are denied.
END OF STEPS
4.14 NE Unsecure mode configuration

4.14.1 Purpose
This procedure provides instructions and sequence to configure the NE in UNSECURE mode.
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).

The NE needs to be connected to the Network Management System.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 SSH keys configuration
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 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: SNMPv1 and v2 are supported on port 161.
Note: Connections to ports 6084, 6085 and 6086 are available also in unsecure mode
END OF STEPS
4.15 SSH keys configuration

4.15.1 Purpose
This procedure provides instructions and sequence to generate and install a new pair of SSH keys
(public and private) for the NE.
Release 5.1 (ETSI)

September 2017
SSH keys configuration 1850 TSS-320/TSS-320H/TSS-160
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.

The NE needs to be connected to the Network Management System.
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.
Note: SSH Keys should be periodically updated according to a centralized policy.

Result: REPTÊVT^SECU with CONDTYPE=SSHKEY is sent when INIT-SSH-KEY is
successfully completed.
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ÊVT^SECU with CONDTYPE=OSSSHKEY is sent when COPY-RFILE-SECU
with FROM=LOCSSHKEY and TO=RFSSSHKEY is successfully completed.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 SSH keys configuration
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ÊVT^SECU with CONDTYPE=OSSSHKEY shall be sent when
COPY-RFILE-SECU with FROM=RFSSSHKEY and TO=LOCSSHKEY is successfully
completed.
END OF STEPS
Release 5.1 (ETSI)

September 2017
SSL keys configuration 1850 TSS-320/TSS-320H/TSS-160
4.15.5
Figure 11 SSH key management
4.16 SSL keys configuration

4.16.1 Purpose
This procedure performs the NE certificate provisioning for either an initial installation or an update.
NE SSL certificates generation and installation is initiated by 1350 OMS EML administrator and only
applies in the case where the NMS is configured to act as a certificate authority (CA) for the
managed network elements.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 SSL keys configuration
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.

The NE needs to be connected to the Network Management System where NMS is a root CA
owning a self-signed CA certificate.
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.
Note: SSL certificates should be periodically updated according to a centralized policy. It

is expected that NMS should generate them with an expiration age of 10 years but they
should be periodically updated.
Result: The NE generates a new SSL key pair (public and private) and then sends a
notification warning to all network administrators, through REPTÊVT^SECU with
CONDTYPE=SSLKEY is sent when INIT-SSL-KEY is successfully completed. and a new
Release 5.1 (ETSI)

September 2017
SSL keys configuration 1850 TSS-320/TSS-320H/TSS-160
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ÊVT^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ÊVT^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ÊVT^SECU with CONDTYPE=SSLCSR is sent when COPY-RFILE-SECU
with FROM=LOCCSRPEM and TO=RFSCSRPEM is successfully completed.
REPTÊVT^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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 SSL keys configuration
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ÊVT^SECU with CONDTYPE=SSLCERT is sent when COPY-RFILE-SECU
with FROM=RFSX509PEM and TO=LOCX509PEM is successfully completed.
REPTÊVT^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ÊVT^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
Release 5.1 (ETSI)

September 2017
ODU2 Deprovisioning 1850 TSS-320/TSS-320H/TSS-160
4.16.5
Figure 12 SSL key management
4.17 ODU2 Deprovisioning

4.17.1 Purpose
This procedure provides instructions and sequence to deprovision an ODU2 facility.
None
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 ODU2 Provisioning
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.
END OF STEPS
4.18 ODU2 Provisioning

4.18.1 Purpose
This procedure provides instructions and sequence to provision an ODU2 facility.
The node shall be equipped with one of the following modules:

• DWLA10X
• OTU-2
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.
Release 5.1 (ETSI)

September 2017
OTU2 Deprovisioning 1850 TSS-320/TSS-320H/TSS-160
END OF STEPS
4.19 OTU2 Deprovisioning

4.19.1 Purpose
This procedure provides the instructions and sequence to deprovision an OTU2 facility.
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.
END OF STEPS
4.20 OTU2 Provisioning

4.20.1 Purpose
This procedure provides instructions and sequence to provision an OTS facility.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 PW Stitching Management (Case of label swap)
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.
END OF STEPS
4.21 PW Stitching Management (Case of label swap)

4.21.1 Purpose
This procedure provides instructions and sequence to provision a PW terminated segment.
4.21.3 General
None.
4.21.4 Procedure
1
Via TL1:
Via CLI side:

(p. 595).
Release 5.1 (ETSI)

September 2017
PW Termination Management (Case of point-to-point) 1850 TSS-320/TSS-320H/TSS-160
Via TL1:
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 PW Termination Management (Case of point-to-point)

4.22.1 Purpose
4.22.3 General
None.
4.22.4 Procedure
1
Via TL1:
Via CLI side:

Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 PW Termination Management (Case of VPLS)
(p. 595).
Via TL1:
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 “
END OF STEPS
4.23 PW Termination Management (Case of VPLS)

4.23.1 Purpose
4.23.3 General
None.
4.23.4 Procedure
1
Via TL1:
Release 5.1 (ETSI)

September 2017
Tunnel Protection Management (Label swap and Tunnel not Terminated) 1850 TSS-320/TSS-320H/TSS-160
Via CLI side:

(p. 595).
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 “
END OF STEPS
4.24 Tunnel Protection Management (Label swap and Tunnel not

Terminated)
4.24.1 Purpose
This procedure provides instructions and sequence to provision an Tunnel Protection (in Release
4.0) only Tunnel Protection is performed.
In Release 4.0 Tunnel termination is needed.
4.24.3
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Tunnel Protection Management (Label swap and Tunnel not Terminated)
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.
Two cases are supported:

• delete FFP “keeping main” (the PWs remain associated to main tunnel);
• delete FFP “keeping spare” (the system automatically moves the supported PWs from main to
spare).
4.24.5 Procedure
1
Via TL1:
Via CLI side:

(p. 595).
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
Release 5.1 (ETSI)

September 2017
VCG Deprovisioning 1850 TSS-320/TSS-320H/TSS-160
4.25 VCG Deprovisioning

4.25.1 Purpose
This procedure provides instructions and sequence to deprovision an VCG facility.
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).
3
Deactivate the ETS port CLI side.
4
Deprovision VCG facility.
For details, refer to 6.40 “Administer VCG Facility” (p. 277).
END OF STEPS
4.26 VCG Provisioning

4.26.1 Purpose
This procedure provides instructions and sequence to provision an VCG facility.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 VCG Provisioning

• PP10AD
• 10XANY.
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
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 VCG activation execute the following steps:

1. Provision the Virtual Concatenation Path Check.
For details, refer to 6.88 “Virtual Concatenation Path Check” (p. 442).
2. Enable LCAS if necessary.
Release 5.1 (ETSI)

September 2017
VPLS Deprovisioning 1850 TSS-320/TSS-320H/TSS-160
For details, refer to 6.40 “Administer VCG Facility” (p. 277) and 6.56 “LCAS Monitoring”
(p. 351).
END OF STEPS
4.27 VPLS Deprovisioning

4.27.1 Purpose
This procedure provides instructions and sequence to deprovision an VPLS service.
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-
2
Delete VPLS Instance.
For details, refer to 10.16 “VPLS Instance Management” (p. 608).
END OF STEPS
4.28 VPLS Provisioning

4.28.1 Purpose
This procedure provides instructions and sequence to provision an VPLS service.

• PP10GE
• PP1GE.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 VPLS Provisioning
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).
A VPLS Service allows:

• remote LAN segments to behave as one single LAN via “end to end” connectivity (irrespective
from higher layer protocols) between 2 remote Ethernet stations;
• Ethernet services to exploit “carrier class” MPLS capabilities, relying on both MPLS “connection
oriented” behavior and MPLS QoS capabilities.
4.28.4 Procedure
1
2
Change ports involved in VPLS in MPLS ones.
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)
Release 5.1 (ETSI)

September 2017
UGW Protection Provisioning 1850 TSS-320/TSS-320H/TSS-160
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).
END OF STEPS
4.29 UGW Protection Provisioning

4.29.1 Purpose
This procedure provides an UGW facility (and protection) provisioning example.
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: Current release supports E1 TDM client only
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 UGW Protection Provisioning
4.29.4 Procedures
1
Provision boards and modules. No module provisioning for the UGW board.
Example:
SDH board e SFP creation:

• ENT-EQPT::8XSO-1-1-35:1:::PROVISIONEDTYPE=8PSO:;
• ENT-EQPT::SFP-1-1-35-1:1:::PROVISIONEDTYPE=SS-11:;
UGW board provisioning:

• ENT-EQPT::PPUGW-1-1-19::::PROVISIONEDTYPE=PP2G5UGW:;
DATA board and SFP provisioning:

• ENT-EQPT::PP1GE-1-1-5:1:::PROVISIONEDTYPE=PP1GE:;
• ENT-EQPT::SFP-1-1-5-1:1:::PROVISIONEDTYPE=ANY-DATAS:;
2
TDM side: create the VC4 cross-connection, i.e. between the AUn and the VCn..
Example: Example with TDM card STM16 (AU4 range: 1 - 16):ENT-CRS-VC4::
STM16AU4-1-1-12-2-1,UGMVC4-1-1-17-2;
Note: Inside each UGW VC4, there will be automatically 63 elements
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.
Note: On CLI side enter:

Interface show
For details refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
4
Create the PW, for details see 4.22 “PW Termination Management (Case of point-to-point)”
(p. 96).
Example:
CLI side create and activate the mpls port:

• interface position r1sr1sl5d0p1 localeth portservice mpls
Release 5.1 (ETSI)

September 2017
UGW Protection Provisioning 1850 TSS-320/TSS-320H/TSS-160
• interface position r1sr1sl5d0p1 localeth activate
TL1 side create and activate Tunnel, Traffic descriptor, PW:

• ENT-TMPLS-TUSEG:::::MPLSIF-1-1-5-1,TERMINATION,BIDIR:INLABEL=5000,
OUTLABEL=5000,MEP=ENABLE,MEG-ID=WRK,MEP-ID=1,EXPMEP-ID=2,CVRX=
ENABLE,CVTX=ENABLE,CVPERIOD=3.33ms,CVPHB=EF;
• ED-TMPLS-TUNNEL::TUNNEL-1-1-1-1-0-0-0-0-0-0-0-0::::TD-ID=MPLSTD-1,
STATUS=ON;
• ENT-TMPLS-PWSEG:::::TUSEG-1-1-1,TERMINATION,BIDIR:INLABEL=100,
OUTLABEL=100;
• ED-TMPLS-PW::PW-1-1-1::::TD-ID=MPLSTD-2,STATUS=ON;
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Control Plane Functions
5 Control Plane Functions
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
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
• CLI commands used in this procedure, refer to the 1850 Transport Service Switch (TSS-320,
TSS-320H and TSS-160) Release 5.1 Command Line Interface Guide
5.1.2 Overview
CP ROUTE is a CP session that can manage different Data Plane services (CP instances), in
GMPLS routing environment.
Data plane service can be identified by the following CP instance:

• TDM
• TDM for OTH
• TDM for SDH/SONET
TDM instance involves management of SONET/SDH transport network , while T-MPLS is oriented
to data service application (MPLS encapsulation of Ethernet, ATM, IP packets).
CP ROUTE defines global parameters of the network , Control Channel configuration and routing
management, according to the used interface type (I-NNI or E-NNI).
Moreover all database elements stored in the LSR for the relevant routing protocol can be
achieved.
CP ROUTE implemented features can be split in the following categories:

• Global parameter definition
• Control Channel configuration and management
• Static routing management
• Routing interfaces management
Release 5.1 (ETSI)

September 2017
• Routing database reporting
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
5.1.3 Control Plane network

Control Plane is, in a general meaning, the GMPLS implementation function to manage and
consolidate different technologies on Data Plane (network services).
A GMPLS instance is a network service managed by CP. It can be of different type (TDM, T-MPLS,
DWDM, etc.)
GMPLS instances are running on a Signaling Communication Network (SCN) that is in charge to
support GMPLS functionalities (routing and signaling) of GMPLS entities (known as GMPLS
Controllers).
SCN is a Layer -3 network and is defined independently from MCN (Management Communication
Network), assigned to a Network Manager.
SCN is built over IP Control Channel (IPCC) network, through point-to-point communication links
between GMPLS Controllers via Control Channel termination ports.
5.1.4 E-NNI configuration

In CP TDM instance, network environment where CP ROUTE operates, is the E-NNI scenario, as
defined from ITUT-T recommendation G.8080, under ASON network architecture concept.
A complex network can be partitioned into different subnetworks, each of them will be
homogeneous in terms of transport technologies, vendor, management/control approach
(administrative control).
This architectural partitioning is called Control Domain (CD) partitioning.
This application scenario is associated to SONET/SDH transport as TDM layer for interconnection
between domains.
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
5.1.5 Global network setting

Operator should provide global configuration of network assigned to CP control in terms of:
• Node IP Address (or Node Identifier)
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Overview
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.1 Overview 107

5.2 Administer T-MPLS Control Plane Global Parameters 110
5.3 Administer Control Plane - Control Routing Port 111
5.4 Administer Control Plane - IP Route 115
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Control Plane Global Parameters 1850 TSS-320/TSS-320H/TSS-160
5.5 Administer Control Plane - Tranport Port 119

5.6 Administer Control Plane - OSPF routing 122
5.7 Administer CP Tunnels - Make Before Break 125
5.8 Administer Control Plane Hoplist 129
5.2 Administer T-MPLS Control Plane Global Parameters

5.2.1 Purpose
This procedure provides the instructions to retrieve information on, and change global network
parameters assigned to Control Plane (CP) for T-MPLS handling.
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.
These are concerning the setting of :

• Node IP address,
• OSPF Area Identifiers
• auto configuration mode
• IP static routes leaked into routing protocols and event notification to CP.
Note that assignment of Node IP address results in activation of the relevant OSPF loopback
interface, located on the OSPF backbone default area (0.0.0.0). If the entry for ED-CP-GLOBAL
command is only for a change of the OSPF default area , this can be done before the node IP
address is set.
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] ;
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane - Control Routing 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).
3
Modify Control Plane parameters
Enter ED-TMPLS-CPGLOBAL::::::[IPADDR=][,OSPFAREAIDDFLT=][,AUTOC
ONFIG=][,ADVERTISE=][,CP-PORTEVNT=][,CP-ROUTPROTEVNT=][,CP-SIGNEVNT=
];
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 Administer Control Plane - Control Routing Port

5.3.1 Purpose
This procedure provides the instructions to retrieve information on, create, modify and delete a
Control Channel port configuration.
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.
Control Channel configuration is based on the following set of parameters:

• Topology and port configuration
• Control Channel port type
Release 5.1 (ETSI)

September 2017
Administer Control Plane - Control Routing Port 1850 TSS-320/TSS-320H/TSS-160
• Data parameter configuration (MTU, encapsulation

• ARP set mode (T-MPLS only)
• Administrative status
CP performs all the provisioning via the ENT-CP-COM TL1 command.
The ENT-CP-COM command is used to create In Fiber- Out Of Band (IF-OOB) or Out of Fiber -Out
Of-Band (OF-OOB) Control Channel port configuration, used for routing purpose, under CP
management.
In T-MPLS instance, Control Channel can be created over MPLS interfaces in In Fiber- In Band (IF-
IB) configuration . For Out of-Fiber -Out of Band (OF-OOB) topology , T-MPLS Control Channel can
be provisioned with virtual tunnel by IP over IP or GRE encapsulation.(TIPIP-n / TGRE-n ).
In T-MPLS IF-IB configuration, operator can set the ARP mode (enable/disable) for MPLS interfaces
over GbE (local MPLS interface)
Operator can modify the following provisioned parameters via ED-CP-COM:

• MTU size of exchanged data packets
• ARP set mode and configuration (T-MPLS only)
Control channel (CC) can be created numbered or unnumbered.
For numbered CC IPADDR and MASK should be provided.
The ED-CP-COM command allows the operator to modify the MTU value parameter and
admnistrative status of control channel. set-up configuration, used for routing purpose, under CP
management.
This command allows to change setting of the ARP protocol (Address Resolution Protocol) in MPLS
interfaces, together with ARP timeout (aging time of ARP table entries) and flushing of the ARP
table (deleting all ARP entries).
The DLT-CP-COM command deletes the previously defined control channel termination port, used
for routing purpose, under CP management.
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.
2
Retrieve Control Channel Termination Port information
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane - Control Routing Port
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
3
Examine output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
Release 5.1 (ETSI)

September 2017
Administer Control Plane - Control Routing Port 1850 TSS-320/TSS-320H/TSS-160
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>:: IPADDR=<value>,MASK=<value>, PORTCLASS=<value>,

ENCAPS-REMOTE-ID=<value>, AREA=<value>,ARP=<value>, ARPTIMEOUT=
<value>, STATUS=<value>, OPER-STATUS=<value>" cr lf
[
"<AID>::ARP-IPADDR=<value>, ARP-MACADDR=<value>"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...
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane - IP Route
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..
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..
10
END OF STEPS
5.4 Administer Control Plane - IP Route

5.4.1 Purpose
This procedure provides the instructions to retrieve information on, create and delete a new static
IP route in the IP routing table, by CP.
I.e. CP will provide routing management in terms of static IP routes added or removed from the IP
routing table of a local node.
Release 5.1 (ETSI)

September 2017
Administer Control Plane - IP Route 1850 TSS-320/TSS-320H/TSS-160
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).
5.4.3 Routing management

Static route is achieved through TL1 command referred to the AID of control channel physical
termination ports (OC-n/STM-n, LAN, IPIP or GRE encapsulation)
CP can also retrieves all or specific IP routes from the routing table of the local node, with its source
attributes (static or dynamic).
If advertise mode is set in CP global parameter configuration, all IP static entries of a local node are
leaked into routing protocol (OSPF) as AS external LSA and flooded into the network.
5.4.4 Static routing configuration

Operator configures, from CP, IP static route to add in the IP routing table of the local node, through
access to the control channel termination port
An IP route is a route to the destination IP address through a network interface , that is defined as
the "next hop" in the routing table.
Static route provisoning is performed via the ENT-CP-RT TL1 command.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane - IP Route
• 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
2
Retrieve Control Plane IP Route information
Enter RTRV-CP-RT:::::[DESTADDR],[MASK];
3
(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
Release 5.1 (ETSI)

September 2017
Administer Control Plane - IP Route 1850 TSS-320/TSS-320H/TSS-160
− TGRE-{10-300000} for Virtual Link using GRE encapsulation for TMPLS

• 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}.
• NEXTHOP = Entry required if AID is LAN-1, else None. Next hop address, it is the IP address
of the next interface in the route (in the format nnn-nnn-nnn-nnn). The target NE shall be
directly connected to this interface. 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 0’s or all 1’s. The
NEXTHOP address must be in the address range of the IP subnet configured on the
Customer LAN interface. If this parameter is given, the route is via the USI Ethernet interface.
Possible values: {1- 99, 101-126,128-223} - {0-255} -{0-255} - {0-255}.
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}.
8
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane - Tranport Port
5.5 Administer Control Plane - Tranport Port

5.5.1 Purpose
This procedure provides the instructions to retrieve information on, create, modify and delete a
Control Plane TE Link.
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.

In TMPLS, autodiscovery of remote-peer is NOT supported.
The User can define max 1000 CP Transport ports. The User can define max 100 Bundle links.
The User can define max 100 component ports in the same Bundle link.
The user can define max 16 numbers Shared Risk Link Group (max 16 SRLG) using grouping
and/or ranging addressing.
The System shall not permit to define a Bundle link inside another Bundle link.
Release 5.1 (ETSI)

September 2017
Administer Control Plane - Tranport Port 1850 TSS-320/TSS-320H/TSS-160
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.
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
3
(p. 107).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane - Tranport Port
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.
Release 5.1 (ETSI)

September 2017
Administer Control Plane - OSPF routing 1850 TSS-320/TSS-320H/TSS-160
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.
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.
7
END OF STEPS
5.6 Administer Control Plane - OSPF routing

5.6.1 Purpose
Use this procedure to modify/retrieve parameters associated to OSPF, to retrieve all attributes of a
neighbor OSPF router port, to retrieve the report of routing information exchanged within the AS
where OSPF is running as common routing protocol.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane - OSPF routing
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)
• 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.

Before changing the parameters associated to OSPF check that:
• the OSPF interface has been provisioned.
• the OSPFAREA-ID parameter is not set with OSPF interface enabled i.e. IFSTATUS should be
OFF.
• the OSPF neighbor interface IP Address ( NEIGHBOR value), matches local OSPF interface
subnet mask.
5.6.5 Procedure
1
Select action:
1. To modify the OSPF interface parameters, go to Step 2
Release 5.1 (ETSI)

September 2017
Administer Control Plane - OSPF routing 1850 TSS-320/TSS-320H/TSS-160
To retrieve the parameters associated with OSPF , go Step 3
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer CP Tunnels - Make Before Break
• TGRE-{10-300000} - Virtual Link using GRE encapsulation for TMPLS.
END OF STEPS
5.7 Administer CP Tunnels - Make Before Break

5.7.1 Purpose
This procedure should be used to edit tunnels created by Control Plane, to replace a LSP tunnel
previously created by Control Plane.
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

Before performing this command:
• Tunnel specified by AID must be present
Release 5.1 (ETSI)

September 2017
Administer CP Tunnels - Make Before Break 1850 TSS-320/TSS-320H/TSS-160
• TD-ID must be previously created

• HOPLIST-ID should be previously created.
• at Board-Level the maximum resource number for NNI in egress direction should not be reached
The tunnel created by make-before-break has:

• the (Tunnel Index, Ingress LER, Egress LER) of the replaced Tunnel
• the Tunnel Instance different from the replaced Tunnel.
where AID = TUNNEL-{1-7}-{1-9}-{1-10000}-{0-65535}-{0-255}-…-{0-255}
i.e. AID = TUNNEL-{1-7}-{1-9}-{Tunnel Index}-{Tunnel Instance}-{Ingress
LER}-…-{Egress LER}
• Same SRC-ADDR and DEST-ADDR of the replaced Tunnel
• Path and bandwidth depends on the entered value for related parameters
• After moving traffic to the new created one (PW are moved to new tunnel), the old tunnel is
removed
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:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer CP Tunnels - Make Before Break
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
Release 5.1 (ETSI)

September 2017
Administer CP Tunnels - Make Before Break 1850 TSS-320/TSS-320H/TSS-160
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,
This parameter can be edited:

• if ACD=CP and only if ROLE=HEAD
• if there is a PW with PW STATUS = ON referencing this TUNNEL, this parameter can't be set
to OFF;
VT-HEAD, VT-TAIL editable in HEAD, TAIL and TRANSIT nodes only allowed to be changed
for Tunnels where STATUS = OFF
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane Hoplist
5.8 Administer Control Plane Hoplist

5.8.1 Purpose
This procedure provides the instructions to retrieve information on, create, modify and delete an
"Hoplist" entry in Control Plane hop list table to be used by CP connections for T-MPLS instance.
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
Release 5.1 (ETSI)

September 2017
Administer Control Plane Hoplist 1850 TSS-320/TSS-320H/TSS-160
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.
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}.
3
Examine output for provisioning information, as detailed in the relevant command guide, refer to
“Command details” (p. 107).
Release 5.1 (ETSI)

September 2017
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}.
Release 5.1 (ETSI)

September 2017
• 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 [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.
6
Delete T-MPLS Control Plane Hoplist
Release 5.1 (ETSI)

September 2017
Enter DLT-CPTMPLS-HOPLIST::HOPLIST-ID::::[PATH-INDEX=][,HOP-IND EX=];
where:
• HOPLIST-ID =Hoplist Identifier selected by user to remove.. The HOPLIST-ID must be
unique in the system. Possible values: {1-2147483647}.
7
END OF STEPS
Release 5.1 (ETSI)

September 2017
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Detailed Level Procedure
6 Detailed Level Procedure
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
Important! 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
• CLI commands used in this procedure, refer to the 1850 Transport Service Switch (TSS-
320, TSS-320H and TSS-160) Release 5.1 Command Line Interface Guide
The Appendix A, “Software Reference Guide” in the back of this manual may also be used as
reference.
6.1.3 Contents
6.1 Overview 135

6.2 Add New User to System 138
6.3 Administer ASAP 139
6.4 Administer Duplex Switching Equipment Protection Group 143
6.5 Administer Duplex Switching ATM Protection Group 147
6.6 Administer Database Backup 150
6.7 Administer Database Restore 152
6.8 Administer Ethernet Facility 155
6.9 Administer Equipment Optical Connection 161
6.10 Administer Line Optical Connection Management 163
6.11 Administer PassThrough Optical Connection Management 167
6.12 Administer Cascade Optical Connection Management 171
6.13 Administer ADD/DROP Optical Connection Management 175
6.14 Administer GBE10 Loopback 179
Release 5.1 (ETSI)

September 2017
6.15 Administer GBE Loopback 183

6.16 Administer L2 Encapsulation Profile 186
6.17 Administer MAC FILE COLLECTION 190
6.18 Administer MAU Facility 193
6.19 Administer MAU Loopback 195
6.20 Administer Network Interface 199
6.21 Administer NE IP Route 200
6.22 Administer NE IP Tunnel 203
6.23 Administer Network Time Protocol (NTP) 207
6.24 Administer STMn Neighbor Discovery 211
6.25 Administer ODU2 Facility 212
6.26 Administer OTU2 Facility 218
6.27 Administer Path Protected Cross-Connection 224
6.28 Administer Per Hop Behaviour Profile (PHBprofile) 227
6.29 Administer Radius server 229
6.30 Administer Security Log File 232
6.31 Administer STMn Facility 235
6.32 Administer STM-n Facility Protection Group 237
6.33 Administer STMn Loopback 241
6.34 Administer STMn MS-SPRING 245
6.35 Administer System Configuration 253
6.36 Administer System Timing/BITS 255
6.37 Administer Clock references - Synchronization 258
6.38 Administer Users with Security Administrator Privileges 263
6.39 Administer VC Cross-Connection 267
6.40 Administer VCG Facility 277
6.41 Auto Discovery Function 284
6.42 Boundary TOD Card administration 285
6.43 Change Facility Service State 293
6.44 Change User Password 294
6.45 Convert a Cross-Connection 296
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Overview
6.46 Delete User from System 308

6.47 Deprovision Equipment 308
6.48 Disable/Enable User Account 314
6.49 Display Alarms 319
6.50 Display MPLS interface parameters 328
6.51 Display Status and Conditions 329
6.52 Edit User Profile 337
6.53 Housekeeping Alarms Management 341
6.54 Housekeeping Controls Management 345
6.55 Initialize System Processors 348
6.56 LCAS Monitoring 351
6.57 Log Into System 354
6.58 Log Out of System 355
6.59 Master TOD Card Management 357
6.60 Optical Intrusion Overview 363
6.61 Optical Intrusion Adminstration 364
6.62 Perform Audible Alarm Cutoff 366
6.63 Perform Module Protection Switch or Copy Switch 367
6.64 Perform Remote Database Backup 369
6.65 Perform Remote Database Restore 375
6.66 Port segregation Management 382
6.67 Provision Equipment 385
6.68 Radius server authentication ordering 390
6.69 Remove/Restore Equipment 393
6.70 Report Performance Monitoring (PM) Data 397
6.71 Retrieve and Change Site Identifier 400
6.72 Retrieve Module Remote Inventory Information 402
6.73 Retrieve Section Trace 404
6.74 Retrieve System Configuration 406
6.75 Retrieve TL1 Command Syntax 409
6.76 Retrieve User Session Information 410
Release 5.1 (ETSI)

September 2017
Add New User to System 1850 TSS-320/TSS-320H/TSS-160
6.77 Retrieve/Provision IP Address of NE 414

6.78 Security Defaults Administration 417
6.79 Set Performance Monitoring (PM) Mode 419
6.80 Set Performance Monitoring (PM) Threshold Levels 421
6.81 Slave TOD Card Management 424
6.82 Set System Date and Time 430
6.83 Set System-Wide User Security Parameters 432
6.84 Switch STMn Line to Protection 434
6.85 Switch VCn Line to Protection 437
6.86 System Access Control (intrusion alarm) 439
6.87 Users with Security Administrator Privileges Overview 441
6.88 Virtual Concatenation Path Check 442
6.89 Modify Equipment Management for Data units 444
6.2 Add New User to System

6.2.1 Purpose
This procedure provides the instructions to create a new user's profile in the system.
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.
A user profile consists of:

• UID—User identifier
• PID—Password identification
• UAP—Command authorization privilege
• PAGE—Password age
• PCND—Number of days to change expired passwords
• PCNN—Number of times allowed to log in after password expiration
• POINT—Password obsolescence interval
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer ASAP
• UOUT—Maximum allowed inactivity period without login
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)}.
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
END OF STEPS
6.3 Administer ASAP

6.3.1 Purpose
This procedure provides the instructions to retrieve information on, create, modify and delete an
Alarm Severity Assigned Profile (ASAP) instance for a given profile type.
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.
Release 5.1 (ETSI)

September 2017
Administer ASAP 1850 TSS-320/TSS-320H/TSS-160
The command can be issued only by users with appropriate privileges.

When successfully completed, the response message shall return the AID of the created ASAP. The
AID is assigned by the NE with a sequence index number starting from 2, because indexes 0 and 1
are respectively used for the nul and factory default ASAP, for each ASAP type.
This RTRV-ASAP-PROF command retrieves information about an Alarm Severity Assigned Profile
(ASAP) instance for a given profile type.
This command can be used also to retrieve information about all Alarm Severity Assigned Profile
(ASAP) instances for ALL profile types in one shot.
This command can be used also to retrieve information about all ASAP instances of a given profile
type (ASAPTYPE) in one shot.
The system-defined ASAPs cannot be deleted.
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.
2
Retrieve ASAP information
Enter RTRV-ASAP-PROF:::::[ASAPTYPE]:[USERLABEL=];
3
(p. 107).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer ASAP
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
Release 5.1 (ETSI)

September 2017
Administer ASAP 1850 TSS-320/TSS-320H/TSS-160
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-
8
Go to Step 1.
9
Replace OLD ASAP with the NEW ASAP
Enter ED-ASAP-ASSIGN:[TID]:[OLDASAPAID],[NEWASAPAID]:[CTAG]:::
[OLDUSERLABE L=],[NEWUSERLABEL=];
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=];
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Duplex Switching Equipment Protection Group
11
END OF STEPS
6.4 Administer Duplex Switching Equipment Protection Group

6.4.1 Purpose
This procedure provides the instructions to retrieve information on, create, switch and delete a
duplex switching equipment protection group out of two unprotected equipment entities.
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).
This command applies to 1:1 protected modules only:

• Main Shelf: EC320, MT320, PP10AD/ATM, PP/UGW
• Drop Shelf: MTSynth
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
• PPUGW with PROVISIONEDTYPE=PP2G5UGW
• P42E1 with PROVISIONEDTYPE=PE1A or PE1B
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.
Release 5.1 (ETSI)

September 2017
Administer Duplex Switching Equipment Protection Group 1850 TSS-320/TSS-320H/TSS-160

In order for a SW-DX-EQPT command to execute, the standby module has to be provisioned and
physically equipped.
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:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Duplex Switching Equipment Protection Group
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
Possible values:
− 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.
Note: Equipment entities specified by the AID1 or AID2 parameter should:

• have same PROVISIONEDTYPE,
• not be already involved in a duplex switching protection group.
• 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.
Besides, the equipment entity specified by the AID2 parameter should not be in SDEE
state. I.e. The command is denied if the protecting entity is supporting "in Service"
facilities.
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.
Release 5.1 (ETSI)

September 2017
Administer Duplex Switching Equipment Protection Group 1850 TSS-320/TSS-320H/TSS-160
Important! It is not recommended to perform a forced protection switch without

assistance from Nokia CTAC.
5
Duplex switching equipment protection group Deletion
Enter:
DLT-DX-EQPT::AID1,AID2::::[CMDMDE=];
where:
Possible values:
− 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
Possible values:
− 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:
Possible values are

• PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Duplex Switching ATM Protection Group
• PPUGW-{1-7}-{1-9}-{2-9,12-19}- Universal GateWay Card Packet Module 2e5G

• P42E1-{1-7}-{1-9}-{1-6} - 1646DS 42XE1/T1 Card.
END OF STEPS
6.5 Administer Duplex Switching ATM Protection Group

6.5.1 Purpose
This procedure provides the instructions to retrieve information on, create, switch and delete a
duplex switching ATM protection group out of two unprotected ATM entities.
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-
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-
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.

In order for a SW-DX-EQPT command to execute, the standby module has to be provisioned and
physically equipped.
Release 5.1 (ETSI)

September 2017
Administer Duplex Switching ATM Protection Group 1850 TSS-320/TSS-320H/TSS-160
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
To perform a MANUAL switch enter:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Duplex Switching ATM Protection Group
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.

Example: SW-DX-EQPT::PP10AD-1-1-6;
SW-DX-EQPT::PP10AD-1-1-6:::FRCD;
5
Duplex switching ATM protection group Deletion
Enter:
DLT-DX-EQPT::AID1,AID2::::[CMDMDE=];
where:
Possible values:
− P42E1-{1-7}-{1-9}-{1,3,5} - 1646DS 42XE1, protected module
Possible values:
− P42E1-{1-7}-{1-9}-{2,4,6} - 1646DS 42XE1, protecting module
• CMDMDE = Command Mode, identifies the Command Execution Mode.
Possible values:
− NORM
− FRCD.
Release 5.1 (ETSI)

September 2017
Administer Database Backup 1850 TSS-320/TSS-320H/TSS-160
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:
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:
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 Administer Database Backup

6.6.1 Purpose
This procedure provides instructions to backup the primary database to the secondary database.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Database Backup
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:
Release 5.1 (ETSI)

September 2017
Administer Database Restore 1850 TSS-320/TSS-320H/TSS-160
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
END OF STEPS
6.7 Administer Database Restore

6.7.1 Purpose
This procedure provides instructions to restore the system database with database information
previously backed up to the standby database.
6.7.2 Prerequisites
None.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Database Restore
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
(p. 107).
Release 5.1 (ETSI)

September 2017
Administer Database Restore 1850 TSS-320/TSS-320H/TSS-160
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Ethernet Facility
4
Did RESTORE-DB command complete?
If no, go to Step 5.
5
Contact Nokia for assistance .
6
END OF STEPS
6.8 Administer Ethernet Facility

6.8.1 Purpose
This procedure provides the instructions to provision, deprovision and modify a specified GBE or
GBE10 client signal facility.
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.
Release 5.1 (ETSI)

September 2017
Administer Ethernet Facility 1850 TSS-320/TSS-320H/TSS-160
When an <ETH> is in an OOS-MA, OOS-AUMA, or OOS-AU,AINS state, no <ETH> transmission

condition types or performance monitoring threshold crossing alerts are autonomously reported for
the <ETH>, but <ETH> alarm conditions are monitored and performance monitoring data is
collected for the <ETH> port.
The ED-<ETH> command is used to set parameters related to the encapsulation mode previously
provisioned using the ENT-<ETH> command.
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)
• PP10GESY: Data port module with sync capability (GBE)
• DWLA10X: Optical Transponder (client port) for GBE10
• PP10GESY: Data port module with sync capability for GBE10
Note: The management of facilities on PP1GE, PP1GESY, PP1GEX20, PP10GE,

PP10GESY, PP1GEX2 modules is limited to the S1TRANS and TCDLY parameters. All other
facility management on these modules is accomplished via SNMP S1TRANS and TCDLY are
not supported on 10XANY and DWLA10X module ports.
RTRV-<ETH> can be used to view the parameters.
DLT-GBE will be denied if the SDEE SST is set.
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
Release 5.1 (ETSI)

September 2017
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).
Release 5.1 (ETSI)

September 2017
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
Ensure that port is in valid state for provisioning (OOS-MA).
5
Deprovision GBE or GBE10 client signal facility
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).
Release 5.1 (ETSI)

September 2017
• 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.
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
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,
Release 5.1 (ETSI)

September 2017
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Equipment Optical Connection
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
END OF STEPS
6.9 Administer Equipment Optical Connection

6.9.1 General
ENT-EQPT_OCONN command allows the operator declaring the cable configuration, regardless of
whether the equipment is physically installed in system or not.
This command configures bidirectional optical connections.
According to the possible DWDM configurations on the Node, the optical connections have been
distinghished in four classes. Each class has a FROM and a TO; FROM and TO are logically and
physically equivalent since connections are bidirectional and can be ex-changed.
Class 1: LINE, this 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.
Class 2: PASSTHROUGH, this connection class configures the passthrough between MUX
channels. In case of line terminal configuration, this optical connection is not present.
Class 3: 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.
Release 5.1 (ETSI)

September 2017
Administer Equipment Optical Connection 1850 TSS-320/TSS-320H/TSS-160
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),
omsoch(M1W/M2W)
CSD&ADDRP (Note) ots(M1), oms(M1), 16 omsoch(M1), 1
omsochif(M1/M2)
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Line Optical Connection Management
INPUT CONN CLASS Facility to be provisioned

PT&ADDRP (Note) ots(ME), oms(ME), omsband(ME), ots(MW),
omsoch(MW), 1 omsochif(ME/MW)
LINE&CSD&PT (Note) ots(L1E), oms(M1E), omsband(M1E),
omsoch(M1W/M2W)
LINE&CSD&ADDRP (Note) ots(L1), oms(M1), 16 omsoch(M1), 1
omsochif(M1/M2)
LINE&PT&ADDRP (Note) ots(LE), oms(ME), omsband(ME), ots(MW),
omsoch(MW), 1 omsochif(ME/MW)
CSD&PT&ADDRP (Note) ots(M1E), oms(M1E), omsband(M1E),
omsoch(M1W/M2W), 1 omsochif(M1E/M2E/
M1W/M2W)
LINE&PT&CSD&ADDRP (Note) ots(L1E), oms(M1E), omsband(M1E),
omsoch(M1W/M2W), 1 omsochif(M1E/M2E/
M1W/M2W)
Note: such provisioning is the result of separate ENT-EQPT-OCONN issue, one for each
optical class specified in the column.
6.10 Administer Line Optical Connection Management

6.10.1 Purpose
Use this procedure to configure, modify, remove and restore line bidirectional optical connections.
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.

DWDM facility configurations on the Node should be already present (OMS, OMSBAND, OMSCH,
OTS), i.e. OMDX8 cards and their facilities should configured.
Release 5.1 (ETSI)

September 2017
Administer Line Optical Connection Management 1850 TSS-320/TSS-320H/TSS-160
Cascade connection can not be set up if a Line connection is in place for MUX on L2 band; and
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Line Optical Connection Management
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
Value Description
multiplexer
LNTO = Access Identifier identifying the TO connector to be cabled. AID can identify one
Value Description
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
Retrieve all facilities created in the step before:

• RTRV-OMS::AID::::[PARMS=];
where:
AID = OMS Access Identifier, specifies the selected OMS facility to which the command is
directed.
• 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
• RTRV-OTS::AID::::[PARMS=];
Release 5.1 (ETSI)

September 2017
Administer Line Optical Connection Management 1850 TSS-320/TSS-320H/TSS-160
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.
To remove OMDX8 facilities enter:

• RMV-OMS::AID:::[MODE];
where:
AID = Access Identifier, specifies the facility.
i.e. AID value is OMS-{1-7}-{1-9}-{6-9,12-15}-1 (OMS Facility on an OMDX8100 L1 or L2).
• RMV-OMSBAND::AID:::[MODE];
where:
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:::[MODE];
where:
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).
• RMV-OTS::AID:::[MODE];
where:
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)
Note: MODE values are FRCD Forced, NORM Normal.

Executing this command causes a state transition for the specified facility from: IS to
OOS-MA
5
Restore an OMDX8 Facility
The RESTORE command causes the specified facility to be placed in an IS or OOS-AU state.
To restore OMDX8 facilities enter:

• RST-OMS::AID;
where:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer PassThrough Optical Connection Management

• RST-OMSBAND::AID;
where:
OMDX8100 L1 or L2)
• RMV-OMSOCH::AID;
where:
OMDX8100 L1 or L2).
• RST-OTS::AID;
where:
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.11 Administer PassThrough Optical Connection Management

6.11.1 Purpose
Use this procedure to configure, modify, remove and restore PASSTHROUGH bidirectional optical
connections.
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.

OTS), i.e. OMDX8 cards and their facilities should configured.
To configure the passthrough between MUX channels the latter should have same frequency (L1/
L2).
Release 5.1 (ETSI)

September 2017
Administer PassThrough Optical Connection Management 1850 TSS-320/TSS-320H/TSS-160
Cascade connection can not be set up if a Passthrough connection is already in place.
6.11.4 Procedure
1
Enter:
where:
Value Description
ALL
1POTU2
Value Description
ALL
multiplexer
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
29-36}-L1 module
29-36}-1 module
2
Enter:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer PassThrough Optical Connection Management
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
-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
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}

where:
directed.
where:
where:
where:
Release 5.1 (ETSI)

September 2017
Administer PassThrough Optical Connection Management 1850 TSS-320/TSS-320H/TSS-160
directed.
4

where:
where:
OMDX8100 L1 or L2)
where:
OMDX8100 L1 or L2).
where:
or L2)

OOS-MA
5

• RST-OMS::AID;
where:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Cascade Optical Connection Management
where:
OMDX8100 L1 or L2)
where:
OMDX8100 L1 or L2).
• RST-OTS::AID;
where:
or L2)
• OOS-MA to IS
END OF STEPS
6.12 Administer Cascade Optical Connection Management

6.12.1 Purpose
Use this procedure to configure, modify, remove and restore cascade bidirectional optical
connections.
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.
Release 5.1 (ETSI)

September 2017
Administer Cascade Optical Connection Management 1850 TSS-320/TSS-320H/TSS-160

OTS), i.e. OMDX8(both L1 and L2 types should be present) cards and their facilities should
configured.
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
connection.
6.12.4 Procedure
1
Enter:
where:
Value Description
ALL
1POTU2
Value Description
ALL
multiplexer
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Cascade Optical Connection Management
Value Description
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
29-36}-L1 module
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
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

where:
directed.
where:
Release 5.1 (ETSI)

September 2017
Administer Cascade Optical Connection Management 1850 TSS-320/TSS-320H/TSS-160
where:
where:
directed.
4

where:
where:
OMDX8100 L1 or L2)
where:
OMDX8100 L1 or L2).
where:
or L2)

OOS-MA
5
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer ADD/DROP Optical Connection Management

• RST-OMS::AID;
where:
where:
OMDX8100 L1 or L2)
where:
OMDX8100 L1 or L2).
• RST-OTS::AID;
where:
or L2)
• OOS-MA to IS
END OF STEPS
6.13 Administer ADD/DROP Optical Connection Management

6.13.1 Purpose
Use this procedure to configure, modify, remove and restore add/drop bidirectional optical
connections.
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.
Release 5.1 (ETSI)

September 2017
Administer ADD/DROP Optical Connection Management 1850 TSS-320/TSS-320H/TSS-160

DWDM facility configurations on the Node should be already present , i.e. OMDX8/DWLA10X/
OT2TDM cards and their facilities should configured.
6.13.4 Procedure
1
Enter:
Value Description
ALL
1POTU2
Value Description
ALL
multiplexer
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
29-36}-L1 module
29-36}-1 module
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer ADD/DROP Optical Connection Management
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
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
29-36}-L1 module
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
29-36}-L1 module
29-36}-1 module
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
EXTERNAL

where:
directed.
Release 5.1 (ETSI)

September 2017
Administer ADD/DROP Optical Connection Management 1850 TSS-320/TSS-320H/TSS-160
where:
where:
where:
directed.
4

where:
where:
OMDX8100 L1 or L2)
where:
OMDX8100 L1 or L2).
where:
or L2)

OOS-MA
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer GBE10 Loopback
5

• RST-OMS::AID;
where:
where:
OMDX8100 L1 or L2)
where:
OMDX8100 L1 or L2).
• RST-OTS::AID;
where:
or L2)
• OOS-MA to IS
END OF STEPS
6.14 Administer GBE10 Loopback

6.14.1 Purpose
This procedure provides the instructions to administer GBE10 loopbacks.
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).
Release 5.1 (ETSI)

September 2017
Administer GBE10 Loopback 1850 TSS-320/TSS-320H/TSS-160
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

Performing loopbacks interrupts traffic.
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.
4
Retrieve Loopback Information
Select RTRV-LPBK-GBE10::[AID];
where:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer GBE10 Loopback
AID=GBE10 access identifier
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:
Possible values are:

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:

• 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).
Release 5.1 (ETSI)

September 2017
Administer GBE10 Loopback 1850 TSS-320/TSS-320H/TSS-160
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.

• FACILITY Specifies a loopback at the receive side (from the network) to the transmit side (to
the network) of the specified facility.
• TERMINAL Specifies a loopback where the signal that is about to be transmitted is connected
to the associated incoming receiver.
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
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}
Note: To execute a RLS-LPBK-GBE10, the specified GBE10 must have a PST,SST of

OOS-AUMA,LPBK or OOS-MA,LPBK.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer GBE Loopback
17
Enter ED-GBE10::AID:::::IS; to place the facility back in service.
where:
AID=Access identifier of GBE10 facility.
18
END OF STEPS
6.15 Administer GBE Loopback

6.15.1 Purpose
This procedure provides the instructions to administer GBE loopbacks.
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
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.
Release 5.1 (ETSI)

September 2017
Administer GBE Loopback 1850 TSS-320/TSS-320H/TSS-160
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.
4
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
6
Go to Step 3.
7
Establish Loopback
Enter RTRV-GBE::AID; to retrieve the current PST and SST of the GBE facility.
where:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer GBE Loopback
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
Enter ED-GBE::AID:::::OOS;
where:
AID=Access identifier of GBE facility.
11
Enter OPR-LPBK-GBE10::AID:::[LOCN],,,[LPBKTYPE];
where:
Near End.

12
Go to Step 3.
13
Enter RTRV-LPBK-GBE::[AID]; to verify the GBE facility is in loopback status.
where:
Release 5.1 (ETSI)

September 2017
Administer L2 Encapsulation Profile 1850 TSS-320/TSS-320H/TSS-160
14
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}
17
Enter ED-GBE::AID:::::IS; to place the facility back in service.
where:
18
END OF STEPS
6.16 Administer L2 Encapsulation Profile

6.16.1 Purpose
This procedure provides the instructions to retrieve information on, create, modify and delete a L2
Encapsulation Profile user defined.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer L2 Encapsulation Profile
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.
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
(p. 107).
Release 5.1 (ETSI)

September 2017
Administer L2 Encapsulation Profile 1850 TSS-320/TSS-320H/TSS-160
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>:: MAC-DA=<value>,TAG=<value>[, VLAN-ID=<value>]

[,PRIORITY=<value>] [,DE=<value>],INUSE=<value>"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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer L2 Encapsulation Profile
• 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.
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.
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
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.
Delete L2 Encapsulation Profile
Release 5.1 (ETSI)

September 2017
Administer MAC FILE COLLECTION 1850 TSS-320/TSS-320H/TSS-160
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
END OF STEPS
6.17 Administer MAC FILE COLLECTION

6.17.1 Purpose
This procedure provides the instructions to initiate NE globally the preparation of the MAC File
Collection and retrieve this file.
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.
Four (4) possible cases shall be supported:

• If both SLOTAID and PORTAID are entered, then the command shall start the collection of all the
learned triplets MAC/port/vsi by the TCAM on board of the entered SLOTAID, where "port" shall
be equal to PORTAID. NOTE: PORTAID can also refer to a different slot than SLOTAID.
• If only SLOTAID is entered, then the command shall start the collection of all the learned triplets
MAC/port/vsi by the TCAM on board of the entered SLOTAID, where "port" shall indicate all the
equipped ports.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer MAC FILE COLLECTION
• 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.
Current state of the MAC File process could be:

• EMPTY: No MAC File is available.
If there are no collected MAC file available the NE starts with the EMPTY MAC file state. This
could be e.g. after the first start of the NE.
• READY: The MAC File is available. Once the MAC file was successfully created, it is
compressed via gzip and the state READY is entered. In this state a MAC file is available (only
in gzip format), which can be either retrieved via COPY-RFILE. A COPY-RFILE command would
be accepted in the READY state, which starts the MAC file transfer from the NE to the
management system.
• INPREP: The MAC File is currently in the process of preparation.
The MAC file will be started by the STA-MACGLB command. After acceptance of this command
the INPREP - files in preparation will be entered. Old file will be no longer available.
While in INPREP state a new start of the file cannot be done. A COPY-RFILE command would
be not accepted in the INPREP state, which starts the file transfer from the NE to the
management system for the MAC file.
• FTRUNNING: File Transfer is currently running.
The FTRUNNING state would be entered with the COPY-RFILE command requesting the MAC
file transfer between the NE and the management system. No other file transfer for MAC file can
be started in this state. The state will be left by canceling the file transfer by CANC-COPY-FILE
or when the file transfer is completed.
After the file transfer the MAC file is still available and the READY state will be entered again.
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.
Release 5.1 (ETSI)

September 2017
Administer MAC FILE COLLECTION 1850 TSS-320/TSS-320H/TSS-160
To retrieve the gzip MAC File Collection, go to Step 8.
2
Retrieve MAC File Collection process Status
Enter RTRV-MACGLB-STATUS;
Result: MACADDCOLLECTIONSTATE Values could be: {EMPTY, READY, INPREP,
FTRUNNING}.
I.e.Current state of the MAC File process.

• EMPTY No MAC File is available.
• READY The MAC File is available. The user could retrieve the gzip file produced go to Step
8
• INPREP The MAC File is currently in the process of preparation.
• FTRUNNING File Transfer is currently running.
3
Examine output (i.e. MACADDCOLLECTIONSTATE value) before starting MAC File Collection.
4
Is the MACADDCOLLECTIONSTATE = empty?
If yes go to Step 7.
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];
8
Retrieve the gzip MAC File Collection
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer MAU Facility
Verify the MAC File Collection is complete (i.e. MACADDCOLLECTIONSTATE equal to

READY).
Enter:
COPY-RFILE::FROM,TO::::LOCATION=;
FROM=LOCMACGLB, i.e Specifies the entity to be transferred.
TO=RFSMACGLB, i.e. Specifies the entity that gets created as the result of the command
completion.
LOCATION=
ftp ://[<userid>[:<password>]@]<ftphost>[:<port>]/<url-path>
Location indicates the source/destination of the files on an RFS to be transferred.
END OF STEPS
6.18 Administer MAU Facility

6.18.1 Purpose
This procedure provides the instructions to modify a MAU (Medium Access Unit). A MAU (Medium
Access Unit) represents the physical layer termination for a sub-set of Ethernet ports.
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.
The following Ethernet ports are covered:

• electrical 10/100/1000 BaseT port
• optical 100 FX port
This command manages MAU port facilities on the following modules:

• 10XANY 10 by Any port module
Release 5.1 (ETSI)

September 2017
Administer MAU Facility 1850 TSS-320/TSS-320H/TSS-160
• PP1GESY Data port module with sync capability

• PP1GE Data port module (10 port)
The management of facilities on PP1GE, PP1GESY, PP1GEX20 modules is limited to the
S1TRANS and TCDLY parameters. All other facility management on these modules is
accomplished via SNMP S1TRANS and TCDLY are not supported on 10XANY module ports.
Executing an ED-MAU command causes the following primary state transitions for the specified
MAU. Secondary states associated with the MAU after the command is executed depend upon
events detected by the system.
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
4
Modify MAU facility parameters
5
Enter ED-MAU::AID::::[AINSTH=][,PMODE=][,AINSCRIT=][,PSTCORR=][,CMDMDE=]
[,FLOWCONT=][,NEGOTN=][,CSF=][,SSF=][,ALMPROF=][,TCAPROF=][,S1TRANS=]
[,TCDLY=]:[PST][,SST];
where: AID = MAU facility. Possible values:

• MAU-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1-10}MAU port on a 10xAny module
• MAU-{1-7}-{1-9}-{2-9,12-19}-{1-10}MAU Port on Packet Module PP1GE or PP1GESY
• MAU-{1-7}-{1-9}-{2-9,12-19}-{1-20}MAU Port on Packet Module PP1GEX20
S1TRANS = {ACT, PRC, SSUL, SSUT, SEC, DUS, NONE}.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer MAU Loopback
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.
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
END OF STEPS
6.19 Administer MAU Loopback

6.19.1 Purpose
This procedure provides the instructions to administer MAU loopbacks.
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
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.
Release 5.1 (ETSI)

September 2017
Administer MAU Loopback 1850 TSS-320/TSS-320H/TSS-160
To execute a near-end or far-end RLS-LPBK-MAU, the specified MAU must have a PST of IS.
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.
4
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
6
Go to Step 3.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer MAU Loopback
7
Establish Loopback
Enter RTRV-MAU::AID; to retrieve the current PST and SST of the MAU facility.
where:

• ALL
• MAU-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1-10} MAU port on a 10xAny module
• MAU-{1-7}-{1-9}-{2-9,12-19}-{1-20} MAU Port on Packet Module PP1GEX20.
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
Enter ED-MAU::AID:::::OOS;
where:

• MAU-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1-10} (MAU port on a 10xAny module)
• MAU-{1-7}-{1-9}-{2-9,12-19}-{1-20} (MAU Port on Packet Module PP1GEX20)
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}.
Near End.

Release 5.1 (ETSI)

September 2017
Administer MAU Loopback 1850 TSS-320/TSS-320H/TSS-160
12
Go to Step 3.
13
Enter RTRV-LPBK-MAU::[AID]; to verify the MAU facility is in loopback status.
where:
AID=MAU Access Identifier
14
15
Go to Step 3.
16
Release Loopback
Enter RLS-LPBK-MAU::AID:::[LOCN],,,[LPBKTYPE]; to release the MAU loopback.
where:
LOCN={NEND}
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:
18
Go to Step 3.
19
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Network Interface
6.20 Administer Network Interface

6.20.1 Purpose
This procedure provides the instructions to retrieve, provision and delete a network interface on a
specified DCC channel on an optical port for data communication purposes.
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
Release 5.1 (ETSI)

September 2017
Administer NE IP Route 1850 TSS-320/TSS-320H/TSS-160
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= ];
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=];
5
Modify Network Interface
Enter ED-NETIF::AID::::[DCCCHNL=][,IP=][,INTISIS=][,L2SIDE=][,OSI=][,
OSIAREA=];
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 Administer NE IP Route

6.21.1 Purpose
This procedure provides the instructions to provision/deprovision a new static IP route in the IP
routing table.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer NE IP Route
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,
Release 5.1 (ETSI)

September 2017
Administer NE IP Route 1850 TSS-320/TSS-320H/TSS-160
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<AID>:<DESTADDR>, <MASK>, [<NEXTHOP>], [<DCCCHNL>], <METRIC>,

<METRICTYPE>, <STATUS>, <ADVERTISE>" 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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer NE IP Tunnel
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}.
7
END OF STEPS
6.22 Administer NE IP Tunnel

6.22.1 Purpose
This procedure provides the instructions to provision/deprovision an IP tunnel instance on the NE.
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.
Release 5.1 (ETSI)

September 2017
Administer NE IP Tunnel 1850 TSS-320/TSS-320H/TSS-160
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer NE IP Tunnel
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<AID>::REMOTENSAP=<value>, ENCAPTYP=<value> " 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.
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).
Release 5.1 (ETSI)

September 2017
Administer NE IP Tunnel 1850 TSS-320/TSS-320H/TSS-160
6
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<AID>::REMOTENSAP=<value>, ENCAPTYP=<value> " 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
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Network Time Protocol (NTP)
6.23 Administer Network Time Protocol (NTP)

6.23.1 Purpose
This procedure provides the instructions to retrieve the NTP server IP address, provision NTP
servers, and delete NTP servers. It also provides instructions to enable NTP, modify NTP
parameters, and disable NTP.
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.
The NE supports the following time-of-day synchronization modes:

• Non-synchronized, free-running mode—NTP is not enabled, and the NE is not synchronized to
an NTP server and is instead using its own internal clock as a source.
• Synchronized mode—The NE is using the NTP protocol to synchronize to an NTP server. The
NE is polling the NTP server and periodically making corrections to its internal clock so as to
maintain the same clock time as the NTP server.
• Non-synchronized, holdover mode—NTP is enabled and the NE has lost NTP server
connectivity and is using the last known clock update to synchronize its clock.
The RTRV-NTP command is used to retrieve the current time-of-day synchronization mode.
Up to 10 NTP servers can be provisioned. An NTP server can be designated as a preferred server
among equally usable and qualified servers. In the case where more than one server is determined
to be the optimum server, the server with the preferred attribute is selected. The ENT-NTP-ADDR
command is used to provision NTP servers.
The RTRV-NTP-ADDR command is used to retrieve the attributes and service states of all
designated NTP servers.
Changing the date and time of the system could result in partial or incomplete PM data.
If NTP is disabled (via ED-NTP) after having been synchronized to an NTP server, the NE internal
clock will adopt the last value of the NTP server time as its set time and will continue to calculate
time stamps using the provisioned offset.
Release 5.1 (ETSI)

September 2017
Administer Network Time Protocol (NTP) 1850 TSS-320/TSS-320H/TSS-160
6.23.4 Procedure
1
Enter RTRV-NTP;
2
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"::NTP=<value>, OFFSET=<value>, CLKMODE=<value>" 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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Network Time Protocol (NTP)
4
Retrieve NTP Server IP Addresses
Enter RTRV-NTP-ADDR;
5
(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.
Release 5.1 (ETSI)

September 2017
Administer Network Time Protocol (NTP) 1850 TSS-320/TSS-320H/TSS-160
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 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
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer STMn Neighbor Discovery
18
Disable NTP
Enter ED-NTP::::::NTP=DISABLE;
19
END OF STEPS
6.24 Administer STMn Neighbor Discovery

6.24.1 Purpose
Use this procedure to create and retrieve a list of the immediate STMn neighbor(s) of the specified
AID(s).
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.

ED-IP-ADDR must be entered before procedure execution.
Release 5.1 (ETSI)

September 2017
Administer ODU2 Facility 1850 TSS-320/TSS-320H/TSS-160
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 Administer ODU2 Facility

6.25.1 Purpose
The ODU2 object entity is automatically created on the line side by the system when the OTU-2
board is inserted and provisioned.
Verify the board is in appropriate slot (02 to 09 - 12 to 19 - 21 to 28 - 29 to 36).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer ODU2 Facility
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
Release 5.1 (ETSI)

September 2017
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
where: AID = Access Identifier, specifies an access Identifier to the OT client or line port.
Possible values:
• ALL
Release 5.1 (ETSI)

September 2017

DWLA10X module
OT2TDM module
7
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]
;
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.
Release 5.1 (ETSI)

September 2017
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
where: AID = Access Identifier, specifies an access Identifier to the OT (client or line) port.
Possible values:
• ALL
DWLA10X module
OT2TDM module
11
Release 5.1 (ETSI)

September 2017
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]
;
12
Enter ED-ODU2::AID::::[,ALMPROF=][,TCAPROF=]:[PST],[SST];
Possible values:
• ALL
DWLA10X module
OT2TDM module
Release 5.1 (ETSI)

September 2017
Administer OTU2 Facility 1850 TSS-320/TSS-320H/TSS-160
13
END OF STEPS
6.26 Administer OTU2 Facility

6.26.1 Purpose
This procedure provides the instructions to provision/deprovision/modify a specified OTM0.2 client
signal facility.
The OTU2 object entity is automatically created on the line side by the system when the OTU-2 is
inserted and provisioned
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer OTU2 Facility
2
Retrieve OTU2 facility information
Enter RTRV-OTU2::AID;
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
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
Release 5.1 (ETSI)

September 2017
Ensure that port is in valid state for provisioning (OOS-MA,UAS).
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.
6
Deprovision OTU2 facility
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
Release 5.1 (ETSI)

September 2017
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>::[AINSTH=<value>][, AINSTIMER=<value>] [,FECTYPE=<value>][,

[
/*
<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
- OTU2, OC192, STM-64, 10GE, 10GFC
Release 5.1 (ETSI)

September 2017
10
Enter RST-OTU2::AID;
where:
• AID=Access Identifier, specifies an access Identifier to the OT client port (client AID).
Possible values:
DWLA10X module
- OTU2, OC192, STM-64, 10GE, 10GFC
11
Modify OTU2 facility
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
Release 5.1 (ETSI)

September 2017
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>::[AINSTH=<value>][, AINSTIMER=<value>] [,FECTYPE=<value>][,

[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
13
Enter ED-OTU2::AID::::[AINSTH=][,FECTYPE=][,ALMPROF=] [,TCAPROF=][,
OTU2CHNL=]:[PST],[SST];
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 )
Release 5.1 (ETSI)

September 2017
Administer Path Protected Cross-Connection 1850 TSS-320/TSS-320H/TSS-160
14
END OF STEPS
6.27 Administer Path Protected Cross-Connection

6.27.1 Purpose
This procedure provides the instructions to retrieve information on, create, modify, and delete a path
protected cross-connection entity and establishes a one-way (unidirectional) or two-way
(bidirectional) SNCP cross connection between the specified rate facilities.
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.
There are two options for the cross-connect type (CCT):

• 1WAYSNCP: Identifies One-way SNCP cross-connection (unidirectional SNCP cross-
connection)
• 2WAYSNCP: identifies Two-way SNCP cross-connection (bidirectional SNCP cross-connection)
There are two options for the Protection Type (PTYPE):

• SNCI: Identifies SubNetwork Connection Protection with Inherent monitoring
• SNCN: Identifies SubNetwork Connection Protection with Non-intrusive monitoring
The RTRV-CRS-VCn and RTRV-CRSPROT-VCn commands retrieve the connection path,
connection type, and circuit ID for a one-way or two-way protected or unprotected cross-
connection.
The DLT-CRS-VCn and DLT-CRSPROT-VCn/STSn commands delete 1-way or 2-way cross-
connections previously set up between the specified VCn to VCn facilities.
The ED-CRS-VCn and ED-CRSPROT-VCn commands are used to edit the AUn level cross-
connect connection attributes that have been previously provisioned with the ENT-CRS-VCn or
ENT-CRSPROT-VCn commands.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Path Protected Cross-Connection
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.
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:
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
Release 5.1 (ETSI)

September 2017
Administer Path Protected Cross-Connection 1850 TSS-320/TSS-320H/TSS-160
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-
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:
FROMPED = AID of connection point.
TO = AID of connection point.
connection.
7
Delete Protected Cross-Connections
DLT-CRSPROT-<rate>::FROMPED,FROMPING,TO:::[CCT];
where:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Per Hop Behaviour Profile (PHBprofile)
rate
Values are:
FROMPED = AID of connection point.
TO = AID of connection point;
connection.
8
Go to Step 1.
9
END OF STEPS
6.28 Administer Per Hop Behaviour Profile (PHBprofile)

6.28.1 Purpose
This procedure provides the instructions to create, modify and delete a Per Hop Behaviour Profile
user defined.
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;
Release 5.1 (ETSI)

September 2017
Administer Per Hop Behaviour Profile (PHBprofile) 1850 TSS-320/TSS-320H/TSS-160
Queue types (either Strict Priority queue or Weighted Fair Queue).
Figure 13 PSC set and related CIR,PIR,CBS and PBS relationship
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
(p. 107).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Radius server
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
Note: The PHB Profile can't be edited if used/referenced by a TUSegment and/or

PWSegment.
Enter ED-PHB-PROF::AID:::[EXP0],[EXP1],[EXP2],[EXP3], [EXP4],[EXP5],
[EXP6],[EXP7];
END OF STEPS
6.29 Administer Radius server

6.29.1 Purpose
Use this procedure to add, modify, retrieve and delete RADIUS server attributes.
Release 5.1 (ETSI)

September 2017
Administer Radius server 1850 TSS-320/TSS-320H/TSS-160
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.
Figure 14 RADIUS general scenario
The NAS role is covered by the NE.

The Figure shows the messages exchange between the user, the NE and the RADIUS server, for
the three possible cases of authentication and authorization.
When the RADIUS server receives an access request, it searches a database of users to find the
user whose name matches the request. If the username is found and the password is correct, the
RADIUS server returns a RADIUS packet, Access-Accept, otherwise an Access-Reject.
The access request contains the userID, the user password and the NSA address. The user
password shall be encrypted by a shared key (between the NE and the RADIUS server). This
shared key is called “shared secret”.
Note: The NE supports provisioning of up to 2 RADIUS Servers.

The ENT-RADIUS-SERVER command is used to configure the RADIUS server attributes so that
the client can communicate with a server for authentication.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Radius server
Access Level: admin.
A server profile consists of:

• the RADIUS server identifier,
• the RADIUS server's status,
• the RADIUS server's IP address,
• the RADIUS server's specific port number,
• shared secret key between the NE and the RADIUS server.
The ED-RADIUS-SERVER command is used to change/modify the RADIUS server attributes which
are provisioned through ENT-RADIUS-SERVER command.

Make sure that an alarms free 1850-TSS320 system with LAN port on MT320 needs to be
connected to PC. NE needs to be connected to the Network Management System and RADIUS
server.
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;
Release 5.1 (ETSI)

September 2017
Administer Security Log File 1850 TSS-320/TSS-320H/TSS-160
3
To modify the Radius Server attributes enter:
ED-RADIUS-SERVER:::::SERVERNUM,[STATUS]:[IPADDR=][,PORT=][,SECRET=];
The SERVERNUM is a valid server number to provision the server, values:

• RAD1: RAD1 is first server name
• RAD2: RAD2 is the second server name.
4
Check server parameters have been modified correctly entering:
RTRV-RADIUS-SERVER;
5
Examine the output.
6
Is the RADIUS server status Enable?
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 Administer Security Log File

6.30.1 Purpose
This procedure provides the instructions to retrieve all output response messages generated by the
system and to provision the security log file parameters.
Retrieving the security log file and provisioning security log file parameters can only be performed
by administrators with security privileges.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Security Log File
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.
The following parameter options are available:

• EIUA—Records logins, logoffs, invalid user authentication attempts and the alarms/alerts
generated due to the invalid authentication attempts. Commands creating log events of this type
are: ACT-USER, INTRUSION events.
• EUSP—Records the details of the changes made in a user's security profiles and attributes.
Commands creating log events of this type are: ENT-USER-SECU, ED-USER-SECU, ED-PID,
DLT-USER-SECU, ALW-USER-SECU, INH-USER-SECU.
• ESCC—Records the details of changes made in the NE/NS security configuration. Commands
creating log events of this type are: SET-ATTR-SECUDFLT, SET-ATTR-SECULOG, ED-CMD-
SECU.
• ECMR—Records creation and modification of NE/NS resources performed via standard
operations and maintenance procedures. This does not address creations and modifications
carried offline. Commands creating log events of this type are all the commands not mentioned
in the lists above, having Y in the security field of the command security table. Refer to .
• ALL—Records all events.
The UPSLG parameter specifies the maximum size, in 1 Megabyte blocks, of the security log file's
disk buffer.
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.
Release 5.1 (ETSI)

September 2017
Administer Security Log File 1850 TSS-320/TSS-320H/TSS-160
2
Provision Security Log Parameters
Enter RTRV-ATTR-SECULOG; to retrieve current security log parameter values.
3
(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=];
5
Enter RTRV-ATTR-SECULOG; to verify changes.
6
Go to Step 9.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer STMn Facility
7
Retrieve Security Log File
Enter RTRV-AUDIT-SECULOG:::::["FRDATM","TODATM"],[UID];
8
Observe output.
9
END OF STEPS
6.31 Administer STMn Facility

6.31.1 Purpose
This procedure provides the instructions to provision/deprovision/modify an STM-1, STM-4, STM-
16, or STM-64 facility.
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
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?
Release 5.1 (ETSI)

September 2017
Administer STMn Facility 1850 TSS-320/TSS-320H/TSS-160
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
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;
The following payload structure (in terms of AUG-Ns) is set:

1. 1.AUG-4, 1.AUG-1: AU4
2. 1.AUG-4, 2.AUG-1: AU4
3. 1.AUG-4, 3.AUG-1: AU4
4. 1. AUG-4, 4.AUG-1: AU4
5. 2. AUG-4: AU4-4C
6. 3. AUG-4: AU4-4C
7. 4.AUG-4, 1.AUG-1: AU4
8. 4.AUG-4, 2.AUG-1: AU4
9. 4.AUG-4, 3.AUG-1 : AU4
10. 4. AUG-4, 4.AUG-1:AU4
If the operator wants only to change a sub-part of the payload structure, he still needs to
specify the complete payload structure for the whole port bandwidth. If in the previous
example the payload of the 3. AUG4 shall be changed from AU44c to 4xAU4, then the
following command needs to be issued:
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;
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer STM-n Facility Protection Group
5
END OF STEPS
6.32 Administer STM-n Facility Protection Group

6.32.1 Purpose
This procedure provides the instructions to retrieve information on, provision, modify, and
deprovision STM-n facility protection groups.
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.
Release 5.1 (ETSI)

September 2017
Administer STM-n Facility Protection Group 1850 TSS-320/TSS-320H/TSS-160
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.
− STM16 for FFP with STM16 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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer STM-n Facility Protection Group
− FFPSTM16-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7} 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
3
(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
Release 5.1 (ETSI)

September 2017
Administer STM-n Facility Protection Group 1850 TSS-320/TSS-320H/TSS-160
Enter ENT-FFP-<STMn>::[AID]::::PTYPE=[,RVRTV=][,RVRTTIM=] [,HLDFFTTIM=]

[,WKG=][,PROTN=][,PSDIRN=][,PROTOCOL=][,EAST=][,WEST=] [,NODEID=][,
NODEDESCR=];
where:
• <STMn> = rate of the facility protection group used as command modifier. Possible values
• AID = Access identifier of the FFP. Possible values previously described.
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
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
10
Go to Step 1.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer STMn Loopback
11
END OF STEPS
6.33 Administer STMn Loopback

6.33.1 Purpose
This procedure provides the instructions to administer STM1, STM4, STM16, or STM64 loopbacks.
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).
Figure 15 Facility Loopback
Release 5.1 (ETSI)

September 2017
Administer STMn Loopback 1850 TSS-320/TSS-320H/TSS-160
Figure 16 Terminal Loopback
6.33.4 Steps
NOTICE

Performing loopbacks may interrupt service if a protection line or protecting path is not
available.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer STMn Loopback
4
Select RTRV-LPBK-STMn::[AID];
where:
STMn=Optical facility type (STM1, STM4, STM16, or STM64).
5
6
Go to Step 3.
7
Establish Loopback
Enter RTRV-STMn::AID; to retrieve current PST and SST of facility.
where:
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
Enter ED-STMn::AID:::::OOS;
where:
STMn = STM1, STM4, STM16, STM64
11
Enter
Release 5.1 (ETSI)

September 2017
Administer STMn Loopback 1850 TSS-320/TSS-320H/TSS-160
OPR-LPBK-STMn::AID:::[LOCN],,,[LPBKTYPE]:[LPBKCONSACT=];
where:
• STMn = The rate of the loopback used as command modifier.
STM1 for a STM-1 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
Enter RTRV-LPBK-STMn::[AID]; to verify the STMn facility is in loopback status.
where:
14
15
Go to Step 3.
16
Release Loopback
Enter RLS-LPBK-STMn::AID:::[LOCN],,,[LPBKTYPE];
where:
LOCN=NEND
LPBKTYPE={TERMINAL, FACILITY}
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer STMn MS-SPRING
17
Enter ED-STMn::AID:::::IS; to place the facility back in service.
where:
18
Go to Step 3.
19
END OF STEPS
6.34 Administer STMn MS-SPRING

6.34.1 Purpose
This procedure provides the instructions to retrieve information on, provision, and deprovision a
Bidirectional Line Switched Ring (MS-SPRING) in which two fiber facilities are used to transport
traffic between nodes of a ring. The two MS-SPRING facilities interface with an STMn MS-SPRING.
Add/drop traffic at the 1850 Transport Service Switch TSS-320, TSS-320H and TSS-160ring node is
connected to other facilities through the 1850 TSS-320, TSS-320H and TSS-160matrix.
It also provides instructions to modify a MS-SPRING ring map, squelch map, or node ID.
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.
Features of the MS-SPRING are as follows:

• One to 20 MS-SPRING STMn STM16 rings within the same 1850 TSS-320, TSS-320H and
TSS-160 node and up to 4 MS-SPRING STM64 rings.
Release 5.1 (ETSI)

September 2017
Administer STMn MS-SPRING 1850 TSS-320/TSS-320H/TSS-160
• 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.
6.34.4
1
Select action.
To provision STMn MS-SPRING Node, go to Step 2.
Release 5.1 (ETSI)

September 2017
To modify MS-SPRING ring map, go to Step 12.

To modify MS-SPRING squelch map, go to Step 22.
To modify MS-SPRING node ID, go to Step 27.
To deprovision STMn MS-SPRING facilities, go to Step 36.
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
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
LLMODE=[,OSI=][,OSIAREA=][,CHNLUSEDBY= ];;
where:
AID=Protected (west) STM-16 or STM-64 access identifier
Release 5.1 (ETSI)

September 2017
LLMODE=LAPD protocol to be supported on the Layer 2
7
Repeat Step 6 for protecting (east) STM-16 or STM-64.
8
Go to Step 9.
9
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:
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}
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
Release 5.1 (ETSI)

September 2017
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=West STMn facility access identifier
17
Enter ED-RINGMAP::AID::::RINGMAP=;
where:
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:
Release 5.1 (ETSI)

September 2017
19
Enter RLS-PROTNSW-<STMn>:[TID]:AID:[CTAG]::LOP-S:WEST;
where:
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)
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?
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.
Release 5.1 (ETSI)

September 2017
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?
27
Modify MS-SPRING Node ID
where:
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:
30
Enter OPR-PROTNSW-<STMn>::AID:::LOP-S:EAST;
where:
31
Enter ED-FFP-STMn::AID::::,NODEID=;
where:
Release 5.1 (ETSI)

September 2017
NODEID=New value of node identifier (0-15)

AID=FFPSTM16/64 facility protection group access identifier
32
Enter RLS-PROTNSW--<STMn>::AID:::LOP-S:WEST;
where:
33
Enter RLS-PROTNSW--<STMn>::AID:::LOP-S:EAST;
where:
34
Enter RTRV-FFP-STMn::[AID]; to verify new node ID value.
where:
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
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
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer System Configuration
6.35 Administer System Configuration

6.35.1 Purpose
The procedure allows the setting of an NE level parameter able to manage the Region context of
NE Application.
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).
Release 5.1 (ETSI)

September 2017
Administer System Configuration 1850 TSS-320/TSS-320H/TSS-160
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]
;
An example output is shown below:
1850TEST 08-05-16 10:33:39

M P00017 COMPLD
"::NODETYPE=UNVRSL320"
"ACTSW:1850TSS-320,,R03.00.15,05-02-20,320::COMPLETE,"
/* RTRV-PRMTR-NE::: [Pad567] (2) */
;
3
Enter SET-PRMTR-NE::::::[REGION=][,PROVMODE=][,USERLABEL=];
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer System Timing/BITS
4
END OF STEPS
6.36 Administer System Timing/BITS

6.36.1 Purpose
This procedure provides the instructions to retrieve, edit, remove, and restore Building Integrated
Timing Source (BITS) timing and to switch system clock synchronization from one reference to the
other.
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 supported clock modes (operational states of a clock) follows:

• Locked mode (normal mode)—Steady state. The SETG generated clock signal is controlled by
the selected external timing reference determined by the T0 selection process
• Holdover mode—Steady state. The operating condition of a clock that has lost its references and
is using data previously acquired (when it was operating in the normal mode) to control its output
signal.
• Free-running mode—Temporary operating mode. The operating condition when the output signal
is totally internally controlled with no influence of a present or previous reference.
The RTRV-BITS command retrieves the provisioning of one or more ports dedicated to BITS
facilities for clock synchronization purposes.
Release 5.1 (ETSI)

September 2017
Administer System Timing/BITS 1850 TSS-320/TSS-320H/TSS-160
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.
Note: Use of Internal timing is not recommended for network traffic.

The OPR-SYNCNSW command controls the timing references used by CRG.
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer System Timing/BITS
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.
Default value depends on provisioned node type in the following way:

• NORM - for node working in SONET mode.
Release 5.1 (ETSI)

September 2017
Administer Clock references - Synchronization 1850 TSS-320/TSS-320H/TSS-160
• FRCD - for node working in SDH mode.

Example:
• In the following ETSI example, the one BITS is provisioned to have a FMT of 2MHZ.
ED-BITS::BITS-1-1-1::::FMT=2MHZ;
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
END OF STEPS
6.37 Administer Clock references - Synchronization

6.37.1 Purpose
This procedure provides the instructions to retrieve, edit, remove, and restore system clock
synchronization from one reference to the other.
6.37.2 General
The ED-SYNCN command modifies the provisioning for the following entities:
• system timing
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Clock references - Synchronization
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
Release 5.1 (ETSI)

September 2017
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Clock references - Synchronization
− 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
5
Edit clock reference parameters
Verify that the newly assigned port of a timing reference:

• is not in the state OOS-MA
• has been provisioned.
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.

• AUTO quality level value is derived from incoming SSM.
This is the default value for :2 Mbit with SSM BIT; STMn port; and for the Ethernet port.
• PRC ETSI quality level value is fixed to PRC (Primary Reference Clock, specified in ITU-T
Rec. G.811)
• SSUL ETSI quality level value is fixed to SSUL (Synchronization Supply Unit - Local node,
specified in ITU-T Rec. G.812)
• SSUT ETSI quality level value is fixed to SSUT (Synchronization Supply Unit -Transfer node,
specified in ITU-T Rec. G.812)
Release 5.1 (ETSI)

September 2017
• 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

• EXTREF-{1-7}-{1-9}-{0,1} (Timing Reference of a Shelf for an External Timing Input Port).
System Timing).
CMDMDE = Command Execution Mode. Values are: FRCD Forced or NORM Normal
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Users with Security Administrator Privileges
6.38 Administer Users with Security Administrator Privileges

6.38.1 Purpose
This procedure describes authorized users creation, modification, deletion and how these users
manage system security resources.
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.
Release 5.1 (ETSI)

September 2017
Administer Users with Security Administrator Privileges 1850 TSS-320/TSS-320H/TSS-160
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.

Login to the NE with ADMIN User (default password).
On first login to NE with the created user in a different session with ACT-USER command User is
prompted to change password.
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Users with Security Administrator Privileges
Login to the NE with ADMIN User (default password).
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.)
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:
Release 5.1 (ETSI)

September 2017
Administer Users with Security Administrator Privileges 1850 TSS-320/TSS-320H/TSS-160
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:
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer VC Cross-Connection
From ADMIN session enable the user with Security Administrator Privileges (for ex.: USER01).
Enter
ALW-USER-SECU:::::UID;
where:
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:
12
Delete user with Security Administrator Privileges
Enter:
DLT-USER-SECU::UID;
where:
Note: All users can be deleted except default users.
END OF STEPS
6.39 Administer VC Cross-Connection

6.39.1 Purpose
This procedure provides the instructions to create/delete/modify a cross-connection entity and
establishes a one-way (unidirectional), two-way (bidirectional) cross connection between the
This command is used for ETSI.
Release 5.1 (ETSI)

September 2017
Administer VC Cross-Connection 1850 TSS-320/TSS-320H/TSS-160
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.
Figure 17 1WAY cross-connection
Figure 18 2WAY cross-connection
Release 5.1 (ETSI)

September 2017
Figure 19 1WAY multicast cross-connection build from single 1WAY cross-connections
Figure 20 1WAY loopback through cross-connect matrix
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.
Release 5.1 (ETSI)

September 2017
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.
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)
Release 5.1 (ETSI)

September 2017
− VCGVC4-{1-7}-{1-9}-{2-9,12-19}-{1-64}- {1-64} for VC4 within a logical VCG on a

Multiservice Packet Card
− VCGLOVC3-{1-7}-{1-9}-{2-9,12-19}-{1-24}-{1-24} for LO VC3 within a logical VCG on a
− 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
− MVC4TU3-{1-7}-{1-9}-{21,22,35,36}-{1-64}-{1-3} for TU3 embedded within a Modifiable
VC4
− 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
STM64
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
2G5PSO or 10xANY
2G5SO or a 10xANY
− VCGVC4-{1-7}-{1-9}-{2-9,12-19,21-36}-{ 1-10}-{1-7} for VC4 within a VCG on a 10xAny
module
Modifiable VC4
VC4
− STM1AU4-{1-7}-{1-9}-{7}-{1}-1 for AU4 embedded within STM1 on Sub-module on SCC of
1646DS
Release 5.1 (ETSI)

September 2017
− STM16AU4-{1-7}-{1-9}-{7}-{1}-{1-16} for AU4 within STM16 on Sub-module on SCC of

1646DS
− STM4AU4-{1-7}-{1-9}-{7}-{1}-{1-4} for STM4AU4 on Sub-module on SCC of 1646DS
− MVC4-{1-7}-{1-9}-{7}-{1-16} for MVC4 on SCC card on 1646 Drop shelf
− 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
− MVC4TU3-{1-7}-{1-9}-{7}-{1-16}-{1-3} for TU3 within a MVC4 on SCC card on 1646 Drop
shelf
− PDHLOVC12-{1-7}-{2}-{8-10, 11-13}-{1-63} for VC12 with E1 client on the PDH Access
shelf E1 Port Module
3
(p. 107).
Release 5.1 (ETSI)

September 2017
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:
2G5SO or a 10xANY
Release 5.1 (ETSI)

September 2017

− LOPOOL-{1-7}-{1-9}-1 for Lower order pool for all LOA cards within a shelf
− 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)
Possible values for VC44C rate:
− STM64AU44C-{1-7}-{1-9}-{2-9,12-19,21 -36}-1-{1,5,9,13,17,21,25,29,33,37,41,4
within an STM64
2G5PSO or 10xANY
STM64
Possible values for LOVC12 rate:
Modifiable VC4
− 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
1646 shelf.
Possible values for LOVC3 rate:
VC4
shelf
• 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 for FROM field.
Release 5.1 (ETSI)

September 2017
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
Release 5.1 (ETSI)

September 2017
Enter ED-CRS-<rate>::FROM,TO:::[CCT]:[CKTID=];
where:
• <rate> = crossconnection rate on which the command acts. Possible values: VC4, VC44C,
of cross-connection) facility of the cross-connection. Possible values as referred in Step 5.
connection) facility of the cross-connection. Possible values as referred in Step 5.
11
Go to Step 1.
12
NOTICE
Optional Content
Possibility of service interruption. Deleting an active cross-connection always affects service.
Delete Cross-Connection
Enter DLT-CRS-<rate>::FROM,TO:::[CCT];
where:
of cross-connection) facility of the cross-connection. Possible values as referred in Step 5.
connection) facility of the cross-connection. Possible values as referred in Step 5.
13
Go to Step 1.
14
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer VCG Facility
6.40 Administer VCG Facility

6.40.1 Purpose
This procedure provides the instructions to provision/deprovision/modify a Virtual Concatenation
Group.
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.
Release 5.1 (ETSI)

September 2017
Administer VCG Facility 1850 TSS-320/TSS-320H/TSS-160
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
Release 5.1 (ETSI)

September 2017
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
[
/*
*/ 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:
Release 5.1 (ETSI)

September 2017
− 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)
• MAXMBR = Maximum Number of Members. The number of members of the type given in
VCGTYPE to be assigned as the initial number of members to the VCG being provisioned.
Indicates the Maximum number of members in the VCG that are available for carrying traffic.
Possible values: {1-192}
• VCGTYPE= The type of VCG. Defines if the VCG contains STS1, VC4, LOVC3 or LOVC12.
Possible values:
− VC4 (the VCG is populated with VC4 members)
− LOVC3 (the VCG is populated with Low Order VC3 members, SDH Hierarchy)
− LOVC12 (the VCG is populated with VC12 members).
Example: In the following example, VCG number 32 on the Multiservice Collector module in
slot 5 is provisioned with 10 VC4s members. The VCGVC4-1-1-5-32-1 is given a sequence
number of 0, VCGVC4-1-1-5-2-32-2 is given a sequence number of 1 so on and the VCGVC4-
1-1-5-32-10 is given a sequence number of 9.
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
module
• MAUVCG-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} for VCG on a MAU port on a 10xAny module
12xVC4 )
Release 5.1 (ETSI)

September 2017

24xVC4)
• ALL for all AID
6
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
/*
*/ 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.
Release 5.1 (ETSI)

September 2017
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
• ALL for all AID
module
• GBEVCG-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} for VCG on a GBE port on a 10xAny module
12xVC4 )
24xVC4)
10
Release 5.1 (ETSI)

September 2017
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
/*
*/ cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
Possibility of service interruption. If this command is issued on a VCG without LCAS,

that is already carrying traffic and LCAS is enabled, then the traffic will be disrupted for
the time that the LCAS on both nodes is established.
11
Enter ED-VCG::AID::::[MAXMBR=][,HLDOFFTIME=][,LCASENABLE=][,RSQACKTOUT=]
[,SDMODE=][,CSFPROP=][,CSFTYPE=][,ALMPROF=][,MODE=]:[PST];
module
Release 5.1 (ETSI)

September 2017
Auto Discovery Function 1850 TSS-320/TSS-320H/TSS-160
• GBEVCG-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} for VCG on a GBE port on a 10xAny module

12xVC4 )
24xVC4)
12
END OF STEPS
6.41 Auto Discovery Function

6.41.1 Purpose
This procedure allows the operator to enable oe 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.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Boundary TOD Card administration
3
Enter ED-NE-DSCV:::::ENABLED= ;
where: ENABLED =NE Autodiscovery mechanism is enabled or disabled. Possible values:

• N No. NE Autodiscovery mechanism is disabled.
• Y Yes. NE Autodiscovery mechanism is enabled.
Default value: N.
4
END OF STEPS
6.42 Boundary TOD Card administration

6.42.1 Purpose
This procedure should be used for TOD card management in boundary mode.
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.
Release 5.1 (ETSI)

September 2017
Boundary TOD Card administration 1850 TSS-320/TSS-320H/TSS-160
Figure 21 Boundary clock schema
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.
Release 5.1 (ETSI)

September 2017
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:
The following resources are enabled:

• 1 PPS-IN port
• 1 PPS-OUT port
• 1 PTP slave port.
• 1 PTPMaster port
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
Release 5.1 (ETSI)

September 2017
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.
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.
Release 5.1 (ETSI)

September 2017
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];
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)
Release 5.1 (ETSI)

September 2017
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:
Release 5.1 (ETSI)

September 2017
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
Release 5.1 (ETSI)

September 2017
Note: The steps below should be done using the SNMP or CLI commands.
First the user should:

• in case of PTP logical Slave/Master port as Provider Bridge UNI:
de-registration of PTP logical Slave port from Static S-VLAN Member Set;
• in case of PTP logical Slave/Master port as VPLS UNI:
de-registration of PTP logical Slave port from VPLS Instance UNI/IWI Static Egress Ports
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:
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:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Change Facility Service State
DLT-EQPT::AID;
where:
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 Change Facility Service State

6.43.1 Purpose
This procedure provides instructions to retrieve or change the service state for a facility.
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
Release 5.1 (ETSI)

September 2017
Change User Password 1850 TSS-320/TSS-320H/TSS-160
Enter RMV-x::AID;
where:
5
Go to Step 7.
6
Restore Facility
Enter RST-x::AID:::SWTCHCMD;
where:
7
END OF STEPS
6.44 Change User Password

6.44.1 Purpose
This procedure provides the instructions to change a user's login Password Identifier (PID).
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Change User Password
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.
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
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.
Release 5.1 (ETSI)

September 2017
Convert a Cross-Connection 1850 TSS-320/TSS-320H/TSS-160
5
END OF STEPS
6.45 Convert a Cross-Connection

6.45.1 Purpose
This procedure provides the instructions to:

• join unidirectional cross connections to one bidirectional cross connection.
• split a bidirectional cross connection into unidirectional cross connections.
• add a protection leg to a cross connection.
• removes a protection leg from a cross connection.
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.
Following join conversions are supported:

• Join to 2WAY see Figure 22, “Conversion of 1WAY <--> 2WAY cross connection” (p. 297)
The CKTID parameter of the new 2WAY cross connection will be taken over from the 1WAY
cross connection addressed by the TO parameter if not provided. Addressed by TO means: input
parameter TO of CNVT-CCJ-<rate> is equal TO of the cross connection.
• Join to 2WAYSNCP see Figure 23, “Conversion of 1WAYSNCP <--> 2WAYSNCP cross
connection” (p. 298)
All parameters of the protection switch will be not changed and taken over to from the
1WAYSNCP cross connection to the 2WAYSNCP cross connection. The protection switch state
remains unchanged by the join operation. The role of FROMPED and FROMPING will be not
changed.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Convert a Cross-Connection
The CKTID of the new 2WAYSNCP cross connection will be taken over from the previous
1WAYSNCP cross connection if not provided.
Figure 22 Conversion of 1WAY <--> 2WAY cross connection
Release 5.1 (ETSI)

September 2017
Figure 23 Conversion of 1WAYSNCP <--> 2WAYSNCP cross connection
Add and remove leg

The CNVT-CCTPR-<rate> command adds a protection leg to a cross connection.
The CNVT-CCTU-<rate> command removes a protection leg from a cross connection.
Following conversions are supported:

• 1WAY <--> 1WAYSNCP see Figure 24, “Conversion of 1WAY <--> 1WAYSNCP - adding/
removing a protection leg” (p. 299)
The command does not support the exchange of the FROMPED / FROMPING role of an existing
path protection cross connection.
The cross connection to be modified will be addressed by the TO parameter. (called original
cross connection)
The CKTID will be taken over from the already existing cross connection if not provided.
Release 5.1 (ETSI)

September 2017
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)
Figure 24 Conversion of 1WAY <--> 1WAYSNCP - adding/removing a protection leg
Release 5.1 (ETSI)

September 2017
Figure 25 Conversion of 2WAYSNCP <--> 2WAY - adding/removing a protection leg
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.
2
Join unidirectional cross connections to one bidirectional cross connection
where:
cross connects in the system. Possible values are described in 6.39 “Administer VC Cross-
Connection” (p. 267).
Release 5.1 (ETSI)

September 2017
3
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
[,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:
• 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).
Release 5.1 (ETSI)

September 2017
5
Go to Step 1.
6
Split a bidirectional cross connection into unidirectional cross connections
where:
7
(p. 107).
Release 5.1 (ETSI)

September 2017
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 CNVT-CCS-<rate>::TO::::[CKTID=];
where:
• 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).
9
Go to Step 1.
10
Add a protection leg to a cross connection
Release 5.1 (ETSI)

September 2017
where:
11
(p. 107).
Release 5.1 (ETSI)

September 2017
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
12
Enter CNVT-CCTPR-<rate>::TO::::NEWFROMPED=,NEWFROMPING= [,RVRTV=][,
RVRTTIM=][,HLDFFTIM=][,PTYPE=];
where:
• 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.
Release 5.1 (ETSI)

September 2017
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).
13
Go to Step 1.
14
Remove a protection leg to a cross connection
where:
15
(p. 107).
Release 5.1 (ETSI)

September 2017
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
16
Enter CNVT-CCTU-<rate>::TO::::NEWFROM=;
where:
• 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-
17
Go to Step 1.
Release 5.1 (ETSI)

September 2017
Delete User from System 1850 TSS-320/TSS-320H/TSS-160
18
END OF STEPS
6.46 Delete User from System

6.46.1 Purpose
This procedure provides the instructions to delete a user's profile for a specified User Identifier
(UID).
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
part of the UID: % (percent sign), + (plus sign), # (pound sign), and _ (under score).
2
END OF STEPS
6.47 Deprovision Equipment

6.47.1 Purpose
This procedure provides instructions to deprovision modules in the system.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Deprovision Equipment
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.
Table 25 Procedures Required Before Deprovisioning Modules
Delete Cross Delete Conference

Port Type Deprovisioning port
Connections Connections
VCG X X X
LAG X X X
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
Release 5.1 (ETSI)

September 2017
Deprovision Equipment 1850 TSS-320/TSS-320H/TSS-160
− CWDM Optical Transponder (2.5G) with Optical Protection

− CWDM OADM 4ch w/o OSC coupler
− CWDM OADM 4ch w OSC coupler
− CWDM Mux/Demux 8ch w/o OSC coupler
− CWDM Mux/Demux 8ch with OSC coupler
− DWDM Mux/Demux 8 channels L1 band without S-band input/output
• SFP and XFP modules:
− XFP on 10GSO modules
− SFP on 2G5SO modules
− SFP on 8XSO modules
− SFP on 10XANY modules
− Electrical SFP 10/100/1000
− 100FX SFP
− CWDM SFP STM-16 Short haul
− CWDM SFP STM-16 Long haul
− DWDM XFP STM-64 Long haul
• Shelf Types:
− UNVRSL320 (Generic 320 type shelf)
− UNVRSL160 (Generic 160 type shelf)
Default equipment (EC320, MT320/MT160, PSF, FAN, and TBUS) are autoprovisioned and cannot
be deleted separately. I/O equipment can only be deleted if all supported facilities are deprovisioned
first.
When a board or a circuit pack is deleted, all related XFP/SFPs are also deleted (if present).
Upon successful completion of the DLT-EQPT command, the system clears all condition types
associated with the specified equipment entity.
The specified equipment must be in the Out-Of-Service-Management (OOS-MA) or Out-of-Service-
Autonomous Management (OOS-AUMA) service state for DLT-EQPT to execute.
RTRV-EQPT retrieves the Primary Service State (PST) and the Secondary Service State (SST) of
the specified equipment AID.
ED-EQPT modifies provisioning parameters for the specified equipment AID.
RMV-EQPT puts the specified equipment into the OOS-MA and/or OOA-AUMA service states.
Traffic should always be switched away from the module before executing the RMV-EQPT
command.
Release 5.1 (ETSI)

September 2017
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.
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
Release 5.1 (ETSI)

September 2017
Deprovision Equipment 1850 TSS-320/TSS-320H/TSS-160
5
Enter DLT-EQPT::AID;
decribed in Step 2
6
Go to Step 20.
7
For DATA boards
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
9
decribed in Step 7
10
decribed in Step 7
11
Go to Step 20.
Release 5.1 (ETSI)

September 2017
12
For WDM board
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
14
decribed in Step 12
15
decribed in Step 12
16
Go to Step 20.
Release 5.1 (ETSI)

September 2017
Disable/Enable User Account 1850 TSS-320/TSS-320H/TSS-160
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.
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.
For XFP/SFP Module
Read the following WARNING.
20
END OF STEPS
6.48 Disable/Enable User Account

6.48.1 Purpose
This procedure provides the instructions to disable (inhibit) existing users in order to prohibit access
to the system. This procedure also provides instructions to reenable user accounts.
The user must have administrator privileges to enable/disable a user account.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Disable/Enable 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];
3
Observe output. Verify STATE=ACTIVE, as detailed in the relevant command guide, refer to
Release 5.1 (ETSI)

September 2017
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
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).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Disable/Enable User Account
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
(
<value>" cr lf)+
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
7
Go to Step 13.
8
Enable User Account
9
Observe output. Verify STATE=SUSPENDED, as detailed in the relevant command guide, refer
Release 5.1 (ETSI)

September 2017
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
(
<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
where: UID=User Identifier of user just enabled
12
Observe output. Verify STATE=ACTIVE, as detailed in the relevant command guide, refer to
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Display Alarms
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
(
<value>" cr lf)+
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
13
END OF STEPS
6.49 Display Alarms

6.49.1 Purpose
This procedure provides the instructions to view the current status of any existing, reported alarm
conditions in the system, or any alarm conditions matching a specified combination of position-
defined input parameters.
None.
Release 5.1 (ETSI)

September 2017
Display Alarms 1850 TSS-320/TSS-320H/TSS-160
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.
3
(p. 107).
Release 5.1 (ETSI)

September 2017
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.
Possible values:
• 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
Release 5.1 (ETSI)

September 2017
• FAN320-{1-7}-{1-9}-{40,41} for FAN equipment

• 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
• MDL-{1-7}-{1-9}-{1-39} for Generic Module AID
• MDL-{1-7}-{1-9} for Generic Shelf AID
• MDL-{1-7}-{1-9}-{1-39}-{1-10} for Generic PIM/SFP AID
• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for SFP on 8XSO modules
• XFP-{1-7}-{1-9}-{2-9,12-19,21-36}-1 for XFP on 10GSO modules
• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 OTU2 Line port, OT2TDM or DWLA10X
module
• TBUS-{1-7}-{1-9}-{42,43} for ISPB Termination Bus
• 10XANY-{1-7}-{1-9}-{2-9,12-19,21-36} for 10XANY Card
• OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} for G.709 OTU 10GB Card - Provisioned Type =
1POTU2
• 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
• 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
• SFP-{1-7}-{1-9}-{2-9,12-19}-{1-10} for SFP on PP10 modules
• XFP-{1-7}-{1-9}-{2-9,12-19}-1 for XFP on PP10GE modules
• SHELF-{1-7}-{1-9} for Shelf
• MDL-{1-7}-{1-9}-{7,8}-{1} for Generic 1646DS Sub-module AID
• MDL-{1-7}-{1-9}-{1-11} for Generic 1646DS Module AID
• SCC-{1-7}-{1-9}-{7,8} for 1646DS SCC Card
• SERV-{1-7}-{1-9}-{1-6} for 1646DS Service Card
• PWR-{1-7}-{1-9}-{9-10} for 1646DS Power Unit
• FAN-{1-7}-{1-9}-{11} for 1646DS FAN Unit
• P42E1-{1-7}-{1-9}-{1-6} for 1646DS 42XE1/T1 Card
• ALL for all AID
Release 5.1 (ETSI)

September 2017
6
(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
Release 5.1 (ETSI)

September 2017
9
(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
Enter RTRV-ALM-x::AID:::[NTFCNCDE],[CONDTYPE],[SRVEFF],[LOCN], [DIRN]; to

retrieve the current status of all alarms or conditions, where the possible values for the relevant
AID = Facility Access Identifier, are the following:
• ALL for all AID
• x= GBE
− GBE-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} for GBE port on a 10xAny module
• x = GBE10
- OTU2, OC192, STM-64, 10GE, 10GFC.
Release 5.1 (ETSI)

September 2017
• x= LOVCN
Values valid for: LOVC12 command modifier
Modifiable VC4
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
− MVC4TU3-{1-7}-{1-9}-{21,22,35,36}-{1- 64}-{1-3} for TU3 embedded within a Modifiable
VC4.
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
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
- OTU2, OC192, STM-64, 10GE
− STM1-{1-7}-{1-9}-{7,8}-{1} for STM1 on Sub-module on SCC of 1646DS
Release 5.1 (ETSI)

September 2017
• 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
− STM4AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-{1-4} for AU4 embedded within an STM4
2G5SO or a 10xANY
− STM64AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-1-{1-64} for AU4 embedded within an STM64
− 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
− 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
Release 5.1 (ETSI)

September 2017
− STM64AU464C-{1-7}-{1-9}-{2-9,12-19,21-36}-1-1 for AU4-64c embedded within an

STM64
- OTU2, STM-64, 10GE , 10GFC
− STM4AU4-{1-7}-{1-9}-{7}-{1}-{1-4} for STM4AU4 on Sub-module on SCC of 1646DS
− STM16AU4-{1-7}-{1-9}-{7}-{1}-{1-16} for AU4 within STM16 on Sub-module on SCC of
1646DS
− MVC4-{1-7}-{1-9}-{7}-{1-16} for MVC4 on SCC card on 1646 Drop shelf
12
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
<LOCN>,<DIRN>,[<MONVAL>],[<THLEV>],[<TMPER>]" cr lf]*
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
Note: The x = OGPOTRT, TUSEG, VCG don't have [<MONVAL>],[<THLEV>],

[<TMPER>] fields.
Note: The x = TIMING don't has <LOCN>,<DIRN>,[<MONVAL>],[<THLEV>],

[<TMPER>] fields.
Release 5.1 (ETSI)

September 2017
Display MPLS interface parameters 1850 TSS-320/TSS-320H/TSS-160
13
Go to Step 14.
14
END OF STEPS
6.50 Display MPLS interface parameters

6.50.1 Purpose
This procedure provides the instructions to view the MPLS Interface parameters.
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
2
(p. 107).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Display Status and Conditions
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
END OF STEPS
6.51 Display Status and Conditions

6.51.1 Purpose
This procedure provides the instructions to view 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.
None.
Release 5.1 (ETSI)

September 2017
Display Status and Conditions 1850 TSS-320/TSS-320H/TSS-160
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.
Output is given for:

• Each equipment entity with standing conditions grouped by equipment type 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.
• All common (no specific entity) standing conditions in ascending order by date and time of
occurrence.
• Each facility entity with standing conditions grouped by facility type 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.
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.
3
(p. 107).
Release 5.1 (ETSI)

September 2017
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 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.
Release 5.1 (ETSI)

September 2017
6
(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
Release 5.1 (ETSI)

September 2017
9
(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
Release 5.1 (ETSI)

September 2017
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.
12
(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]
;
Note: The x = OGPOTRT, TUSEG, VCG don't have [<MONVAL>],[<THLEV>],

[<TMPER>] fields.
Note: The x = TIMING don't has <LOCN>,<DIRN>,[<MONVAL>],[<THLEV>],

[<TMPER>] fields.
Release 5.1 (ETSI)

September 2017
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
− 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)
15
(p. 107).
Release 5.1 (ETSI)

September 2017
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.
18
(p. 107).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Edit User Profile
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
19
END OF STEPS
6.52 Edit User Profile

6.52.1 Purpose
This procedure provides the instructions to edit a current user's profile.
To create a new user profile, refer to 6.2 “Add New User to System” (p. 138).
The user must have administrator privileges to edit a user profile.
Release 5.1 (ETSI)

September 2017
Edit User Profile 1850 TSS-320/TSS-320H/TSS-160
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.
A user profile consists of:

• UID—User identifier
• PID—Password identification
• UAP—Command authorization privilege
• PAGE—Password age
• PCND—Number of days to change expired passwords
• PCNN—Number of times allowed to log in after password expiration
• POINT—Password obsolescence interval
• UOUT—Maximum allowed inactivity period without login
6.52.4 Procedure
1
2
(p. 107).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Edit User Profile
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
(
<value>" cr lf)+
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
Enter RTRV-STATUS;
4
(p. 107).
Release 5.1 (ETSI)

September 2017
Edit User Profile 1850 TSS-320/TSS-320H/TSS-160
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.
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).
7
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Housekeeping Alarms Management
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
END OF STEPS
6.53 Housekeeping Alarms Management

6.53.1 Purpose
This procedure provides the instructions to retrieve information on, set, operate and release the
housekeeping alarms and controls.
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.
Input Alarm sensors have the following characteristics:

• Single ended with a common reference
• Alarm sensor inputs shall indicate a LOW state when the customer driving circuitry has an
impedance less than 470 Ohms. Driver applied voltage if any must be greater than -4v. Driver
circuit must be able to supply at lease 2mA minimum. A closed relay contact shall sufficient to
cause a Low indication by the HKP alarms sensors.
• Alarm sensor inputs shall indicate a HIGH state when the customer driving circuitry has an
impedance greater than 100K ohms. An open relay contact shall sufficient to cause a HIGH
indication by the HKP alarms sensors.
Release 5.1 (ETSI)

September 2017
Housekeeping Alarms Management 1850 TSS-320/TSS-320H/TSS-160
Table 26 Housekeeping input characteristics
Polarity Environment Condition Physical signal

Detected
ALOW yes 0
AHIGH yes 1
ALOW no 1
AHIGH no 0

EC320 board must be provisioned.
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Housekeeping Alarms Management
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:
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:
− MJ major alarm
− MN minor alarm
− NA Not Alarmed
− NR Not Reported
Release 5.1 (ETSI)

September 2017
Housekeeping Alarms Management 1850 TSS-320/TSS-320H/TSS-160
SET-ATTR-ENV.
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:
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:
− MJ major alarm
− MN minor alarm
− NA Not Alarmed
− NR Not Reported
SET-ATTR-ENV.
• 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:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Housekeeping Controls Management
SET-ATTR-ENV::AID:::[NTFCNCDE],[ALMTYPE],[ALMMSG],[POLARITY];
where:
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 Housekeeping Controls Management

6.54.1 Purpose
Use this procedure to configure the mode of operations for the control point output which can be
MANUAL (operation by TL1 command) or AUTOMATIC (operation based on alarm condition).
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.
Release 5.1 (ETSI)

September 2017
Housekeeping Controls Management 1850 TSS-320/TSS-320H/TSS-160
RLS-EXT-CONT instructs an NE to release an external control, such as a relay deactivation. The

control is released continuously, and can be operated by using the OPR-EXT-CONT command.
The RTRV-ATTR-CONT instructs an NE to retrieve the attributes of an external control. The
command can be used to audit the result of a SET-ATTR-CONT command.
The RTRV-EXT-CONT instructs an NE to send the control state of an external control. The
command can be used to audit the result of an OPR-EXT-CONT or a RLS-EXT-CONT command.
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Housekeeping Controls Management
POLARITY = Polarity. Determine when the external control is active.
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.
Command Guide.
5
Operate housekeeping control
The user can de/activate output external-control points.
Enter:
OPR-EXT-CONT::AID;
where:
6
Release housekeeping control
Enter:
RLS-EXT-CONT::AID;
where:
END OF STEPS
Release 5.1 (ETSI)

September 2017
Initialize System Processors 1850 TSS-320/TSS-320H/TSS-160
6.55 Initialize System Processors

6.55.1 Purpose
This procedure provides the instructions to reset processor-based modules provisioned and
installed in the system.
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..
Two possible "full reset" of the NE are defined:

• normal full reset of the NE is not traffic affecting, it implies cold restart of EC320 followed by cold
restart of MT320/MT160, no reloading of IOCs FPGA. MODE= FRCD and PHASE=COLD are
necessary.
• power-on full reset of the NE is traffic affecting, it consists of cold restart of EC320, power-on
restart of MT320/MT160 and cold restart of IOCs if present. MODE= FRCD and
PHASE=POWER-ON are necessary.
If an entity is providing service, COLD and POWER-ON restarts are allowed only if the FRCD mode
is specified.
The matrix, clock processor, and shelf controller cannot be reset separately.
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)
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Initialize System Processors
• 10XANY 10GB 10xGBE Card

• MultiService Adaptation Card (Packet Module 10G)
• Packet Module 10x1GbEthernet (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 Mux/Demux 8ch w/o OSC coupler
• CWDM Mux/Demux 8ch with OSC coupler
• DWDM Mux/Demux 8 channels L1 band without S-band input/output
Shelf Types
• UNVRSL320 (Generic 320 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
Release 5.1 (ETSI)

September 2017
Initialize System Processors 1850 TSS-320/TSS-320H/TSS-160
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
• 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).
3
Go to Step 5.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 LCAS Monitoring
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
END OF STEPS
6.56 LCAS Monitoring

6.56.1 Purpose
This procedure provides the instructions to monitor the Link Capacity Adjustment Scheme (LCAS)
protocol.
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.
Release 5.1 (ETSI)

September 2017
LCAS Monitoring 1850 TSS-320/TSS-320H/TSS-160
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
• MAUVCG-{1-7}-{1-9}-{2-9,12-19,21-36}- {1-10} for VCG on a MAU port on a 10xAny module)
12xVC4 )
24xVC4)
2
Examine output as detailed in the relevant command guide, refer to “Command details”
(p. 107).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 LCAS Monitoring
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>::WRKTXCHNUM=<value>, WRKRXCHNUM=<value>, MSTCHREF=<value>,

CHFRDIFFDLY=<value>,RSACKTX=<value>, RSACKRX=<value>" cr lf
[
"<CHNUM>::CTRLPKTTX=<value>, CTRLPKTRX=<value>, SQNUMTX=<value>,

SQNUMRX=<value>, CHNSTATETX=<value>,
CHNSTATERX=<value>,DIFFDLYRX=<value>" cr lf]+
[
/*
*/ cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
END OF STEPS
Release 5.1 (ETSI)

September 2017
Log Into System 1850 TSS-320/TSS-320H/TSS-160
6.57 Log Into System

6.57.1 Purpose
This procedure provides the instructions to establish a session with the network element (NE) and
to log in a specific user to the 1850 TSS-320, TSS-320H and TSS-160.
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Log Out of System
values for HOSTIP are {0-255}-{0-255}-{0-255}-{0-255}. This parameter is optionally passed

to NE by ZIC application in order to provide to the NE the needed information for correct LOG
and reporting.
2
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
END OF STEPS
6.58 Log Out of System

6.58.1 Purpose
This procedure provides the instructions to terminate a session with the system and to log out a
specific user.
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,
Release 5.1 (ETSI)

September 2017
Log Out of System 1850 TSS-320/TSS-320H/TSS-160
The CANC-USER-SECU 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 specified user.
Only the security administrator can log-off any other user. Other users, besides the security
administrator, cannot log-off another user.
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
(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
(under score).
5
Observe output.
6
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Master TOD Card Management
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.
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
END OF STEPS
6.59 Master TOD Card Management

6.59.1 Purpose
This procedure should be used for TOD card management in Master mode.
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.
Release 5.1 (ETSI)

September 2017
Master TOD Card Management 1850 TSS-320/TSS-320H/TSS-160
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.

Before provisioning insert TOD card. The card is auto-provisioned if NE is in AutoProvision mode.
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:
• CKMODE=MASTER means that the PP1588 card is configured in Master Clock
Configuration.
Result:

• 1 PPS-IN port
• 1 PPS-OUT port
• 1 PTP Slave port
3
Check the card InService state.
Enter:
RTRV-PTPMASTER::[AID];
Release 5.1 (ETSI)

September 2017
where:
AID = PTPMASTER-{1-7}-{1-9}-{2-9, 12-19, 21-36}-1
4
Select action:
manage PTP Master port facility, go to Step 10
5
provisioned:
where:
PPSIN Access Identifier, specifies the input port receiving the PPS signal
synchronization. The delay is due to the length of the cable on the link. The length
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];
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.
Release 5.1 (ETSI)

September 2017
8
provisioned
where:
synchronization. The delay is due to the length of the cable on the link. The length
values can be provisioned as well for compensating excessive delays provisioned at the
other side transmitter. The unit of measure is nanosecond.
9
Enter:
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.
Release 5.1 (ETSI)

September 2017
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
Provide phase distribution from ToD signal info or from the input PPS interface.
12
Enter:
where:
Values are:
Phase)
Values are:
reference
13
To configure PTP clock and ports refer to the 1850 Transport Service Switch (TSS-320, TSS-
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
Release 5.1 (ETSI)

September 2017
TOD Card deletion

• in case of PTP logical Master port as Provider Bridge UNI:
de-registration of PTP logical Master port from Static S-VLAN Member Set
• in case of PTP logical Master port as VPLS UNI:
de-registration of PTP logical Master port from VPLS Instance UNI/IWI Static Egress Ports
15
guide.
16
17
18
The PTP logical Master port must be disabled at SNMP side. Please refer to the CLI command
guide.
19
Enter:
RMV-EQPT::AID;
or
ED-EQPT::AID:OOS;
where:
20
Enter:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Optical Intrusion Overview
DLT-EQPT::AID;
where:
END OF STEPS
6.60 Optical Intrusion Overview

6.60.1 General
A procedure to monitor the status of STM-64 line has been defined, with a warning alarm in case of
Rx power falling below or raising above a configured threshold in order to identify intrusion in the
optical line.
The mechanism shall be applicable to UNI/NNI interfaces.
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.
6.60.2 Alarm Raising and Clearing details

• Alarm is inhibited during LOS condition.
When LOS alarm is raised the following behaviour applies:
− The LOS alarm hides possible intrusion alarm already raised.
− The value of the measured Input Power BEFORE the LOS is maintained as reference for the
comparison of the delta for the first available sampling after LOS clearing.
• Alarm shall raise if Delta Power > CONFIGURED THRESHOLD
• Default alarm severity shall be MAJOR
• Reset of the reference power for comparison is performed also when the “optical intrusion
monitoring” is disabled
Definition of a new standing condition associated to STM64 condition Class:

• The new condition is OPT-INTRUSION, Optical Intrusion alarm
• New condition applies as standing condition, which can be manually cleared or automatically
cleared at time out expiration (default value equal to 24 h).
• The default ASAP severity is MAJ instead of WR.
Release 5.1 (ETSI)

September 2017
Optical Intrusion Adminstration 1850 TSS-320/TSS-320H/TSS-160
6.60.3 New alarm definition
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 Optical Intrusion Adminstration

6.61.1 Purpose
Use this procedure to enable/disable the mechanism for intrusion detection and configure the
threshold to trigger the alarm.
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Optical Intrusion Adminstration
For the control of the optical intrusion detection, enter:

ED-STM64::AID::::[,OIDET=][,OITHR=];
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
Release 5.1 (ETSI)

September 2017
Perform Audible Alarm Cutoff 1850 TSS-320/TSS-320H/TSS-160
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 Perform Audible Alarm Cutoff

6.62.1 Purpose
This procedure provides the instructions to cut off the office audible alarm indications without
changing the local alarm reporting.
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
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Perform Module Protection Switch or Copy Switch
6.63 Perform Module Protection Switch or Copy Switch

6.63.1 Purpose
This procedure provides instructions to perform manual protection switch for all 1:2 protected
boards (LOA10G) and to perform a copy switch for redundant equipment (MT320s/MT160s).
The procedure is used to perform "Forced Switch to Protection" or "Manual Switch to Protection"
operation for a working module. The specified working module is switched to the associated
protection module.
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
Release 5.1 (ETSI)

September 2017
Perform Module Protection Switch or Copy Switch 1850 TSS-320/TSS-320H/TSS-160
Enter SW-TOPROTN-EQPT::AID:::[MODE]
Possible values:

3
Go to Step 7.
4
Switch LOA10G to Working
Enter SW-TOWKG-EQPT::AID:::[MODE];
Possible values:

5
Go to Step 7.
6
Enter SW-DX-EQPT::AID:::[MODE];
Possible values:

Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Perform Remote Database Backup
7
END OF STEPS
6.64 Perform Remote Database Backup

6.64.1 Purpose
This procedure provides the instructions to create a database backup, copy those database files to
a Remote File Server Database (RFSDB), and to cancel an in-progress file transfer.
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
The process of performing a remote database backup consists of two phases:

• Create a backup file on the NE.
• Send that backup file to a remote storage location.
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.
Release 5.1 (ETSI)

September 2017
Perform Remote Database Backup 1850 TSS-320/TSS-320H/TSS-160
Figure 26 Database Types
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
Release 5.1 (ETSI)

September 2017
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).
Release 5.1 (ETSI)

September 2017
Figure 27 Database Backup and File Transfer to RFS
6.64.4 Procedure
1
Select action.
To perform remote database backup, go to Step 2.
Release 5.1 (ETSI)

September 2017
To cancel database file transfer, go to Step 6.
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
Release 5.1 (ETSI)

September 2017
for the parameters FROM and TO.
FROM TO
STBYDB RFSDB
RFSDB STBYDB
RFSSW STBYSW
LOCPMGLB RFSPMGLB
RFSSCRIPT LOCSCRIPT
LOCFILE RFSFILE
LOCMACGLB RFSMACGLB
• LOCATION= Location indicates the source/destination of the files on an RFS to be

transferred. 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.
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..
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Perform Remote Database Restore
7
END OF STEPS
6.65 Perform Remote Database Restore

6.65.1 Purpose
This procedure provides instructions to restore backed up provisioning data (configuration files)
from a remote file server to a 1850 TSS-320, TSS-320H and TSS-160.
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 process of performing a remote database restore consists of two phases:

• Copy a backup file from a remote location to the target NE.
• Restart the NE with the downloaded database.
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.
Release 5.1 (ETSI)

September 2017
Perform Remote Database Restore 1850 TSS-320/TSS-320H/TSS-160
Figure 28 Database Types
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
Release 5.1 (ETSI)

September 2017
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.
Release 5.1 (ETSI)

September 2017
Figure 29 Database Transfer and Restore from RFS to NE
Release 5.1 (ETSI)

September 2017
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
(p. 107).
Release 5.1 (ETSI)

September 2017
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
[
/*
*/ 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
Release 5.1 (ETSI)

September 2017
for the parameters FROM and TO.
FROM TO
STBYDB RFSDB
RFSDB STBYDB
RFSSW STBYSW
LOCPMGLB RFSPMGLB
RFSSCRIPT LOCSCRIPT
LOCFILE RFSFILE
LOCMACGLB RFSMACGLB
• LOCATION= Location indicates the source/destination of the files on an RFS to be

transferred. 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.
4
Wait for command completion message.
5
Enter RESTORE-DB::::::[CMDMDE=];
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
Release 5.1 (ETSI)

September 2017
Port segregation Management 1850 TSS-320/TSS-320H/TSS-160
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
END OF STEPS
6.66 Port segregation Management

6.66.1 Purpose
Use this procedure to avoid remote NE’s (RNE) inter-communication via ingress ports, for
management purposes.
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:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Port segregation Management
Figure 30 Port segregation scenario
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.

Port Segregation is enabled/disabled via TL1 command (SET-ATTRSECUDFLT) with NE in
SECURE mode. By default this feature is disabled (i.e. no check & filtering is applied by the system
on RNEs IP addresses).
Note: Port Segregation must not be enabled if the “port segregation list” is empty, since it will
make the NE unreachable.
Release 5.1 (ETSI)

September 2017
Port segregation Management 1850 TSS-320/TSS-320H/TSS-160
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).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Provision Equipment
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 Provision Equipment

6.67.1 Purpose
This procedure provides instructions to provision shelves, boards/circuit packs and modules in the
system.
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.
The following equipment is mandatory and is automatically pre-provisioned/created in the system:

• Main shelf
• EC320
• MT320/160
• PSF320
• FAN
• TBUS
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
• 10GSO (OC-192/STM-64) Evolution card
• 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)
Release 5.1 (ETSI)

September 2017
Provision Equipment 1850 TSS-320/TSS-320H/TSS-160
• 63 E1 Protection Card
• G.709 OTU 10GB Card with XFP
• ANYFC 10GB 10 x FC-2/FC-4
• MultiService Adaptation Card for ATM (Packet Module 10G)
• Universal GateWay UGW Adaptation Card (Packet Module 10G)
• Packet Module 20x1GbEthernet
• Packet Module 2x10GbEthernet
• XFP on 10GSO modules
• SFP on 2G5SO modules
• SFP on 8XSO modules
• SFP on 10XANY modules
• 1000BASE-BX20 (Upstream and Downstream)
• FE 100BASE-BX20 (Upstream and Downstream)
• OC-48/STM-16 40km BiDi (Upstream and Downstream)
Release 5.1 (ETSI)

September 2017

Shelf Types
• UNVRSL160C (19” 160 type shelf)
The following features apply to related modules:

• A module can be provisioned with its related module not provisioned, except for XFP/SFP.
• To provision an XFP/SFP, the corresponding IOC must be provisioned. For details see Appendix
B, “Equipment Entities”.
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.
The SS-Bit parameter configures the SS-Bit SDH overhead transmit value that is SS10 (if the
REGION parameter is ETSI).
Once equipment is provisioned, ED-EQPT can be used to alter parameters.
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
Release 5.1 (ETSI)

September 2017
Provision Equipment 1850 TSS-320/TSS-320H/TSS-160
Enter ENT-EQPT::SHELF-{1-7}-{1-9}::::[PROVISIONEDTYPE=] [,AINSMODE=][,

SHELFNUM=][,SHELFROLE=][,APTMODE=][,VOAMODE=] [,APSD1=][,APSD2=][,
OPWRL1=][,OPWRL2=][,VOA=][,EOLSPAN=][,N1=][,PCH1=][,IT=][,LAMBDASET=]
[,ALMPROF=][,CLNTSEL=][,OPWRLOT2=][,SSBIT=]:[PST];
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
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)
This command fails if:

• the first ENT command received is not the one related to AID Assignment to the Main Shelf
Release 5.1 (ETSI)

September 2017
• 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).
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?
Release 5.1 (ETSI)

September 2017
Radius server authentication ordering 1850 TSS-320/TSS-320H/TSS-160
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=][,
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.
12
END OF STEPS
6.68 Radius server authentication ordering

6.68.1 Purpose
Use this procedure to configure and retrieve the Radius authentication order.
6.68.2 General
The NE supports the following general RADIUS attributes configuration:

• Timeout: This is the timeout (in seconds) for the NE to wait for a response from the RADIUS
server.The failure is declared after the timeout is elapsed. The supported value range for timeout
is 1 to 1000. The default value is 5.
• Retries: This is the number of attempts that the NE will try to contact the specified RADIUS
server that has failed to respond during the previous request(s). If there is no response from the
server after the specified tries then the NE will try to contact the second RADIUS server if one is
provisioned (status: “Enabled”). The retries range is 0 to 100 with default value 3.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Radius server authentication ordering
The following TL1 commands are used to configure and retrieve RADIUS Timeout and Retries:
SET-RADIUS-AUTH RTRV-RADIUS-AUTH
The NE supports the following authentication ordering behavior options:

• LOCAL: Authentication is based on the local NE's security database.
• RADIUS: Authentication first attempt is however based on the local NE's security database: if the
userID in not found there, then the authentication is based on the RADIUS server's database.
NOTE: this way the NE can always guarantee NMS access, which is based on a local NE
userID.
The following TL1 commands are used to configure and retrieve the authentication order: SET-
RADIUS-AUTH /RTRV-RADIUS-AUTH
The SET-RADIUS-AUTH command sets the authentication parameters which are used during
access to the RADIUS servers. This command shall be allowed to a security administrator only.
Authentication parameter profile consists of:

• the authentication order,
• the timeout,
• the number of retries.
The above attributes shall be configured and retrieved by a user with appropriate administrative
privilege.

NE needs to be connected to the Network Management System and RADIUS server.
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).
Release 5.1 (ETSI)

September 2017
Radius server authentication ordering 1850 TSS-320/TSS-320H/TSS-160
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=];
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Remove/Restore Equipment
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=];
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 Remove/Restore Equipment

6.69.1 Purpose
This procedure provides instructions to remove modules from service and to restore modules to
service. Them was been previously provisioned as described in 6.67 “Provision Equipment”
(p. 385).
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
Release 5.1 (ETSI)

September 2017
Remove/Restore Equipment 1850 TSS-320/TSS-320H/TSS-160
• FAN
• 8 Port (STM-1)/(STM-4) card
• SFP on 8 port (STM-1)/(STM-4) modules (8XSO)
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Remove/Restore Equipment
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
where:
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
Release 5.1 (ETSI)

September 2017
Remove/Restore Equipment 1850 TSS-320/TSS-320H/TSS-160
− 10XANY-{1-7}-{1-9}-{2-9,12-19,21-36} for 10XANY Card

− XFP-{1-7}-{1-9}-{2-9,12-19,21-36}-1 for XFP on 10GSO modules
− SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4} for SFP on 2G5SO or on CWLA modules
− SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for SFP on 8XSO modules
− SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} for SFP on 10XANY modules
− 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
− SFP-{1-7}-{1-9}-{2-9,12-19}-{1-10} for SFP on PP10 modules
− XFP-{1-7}-{1-9}-{2-9,12-19}-1 for XFP on PP10GE modules
3
What is PST of module to remove?
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?
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).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Report Performance Monitoring (PM) Data
7
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 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
END OF STEPS
6.70 Report Performance Monitoring (PM) Data

6.70.1 Purpose
This procedure provides the instructions to report Performance Monitoring (PM) data and initialize
(reset) the collection register for GBE10, GBE, GFC10, ODU2, OTU2, MAU, and SDH facilities.
Release 5.1 (ETSI)

September 2017
Report Performance Monitoring (PM) Data 1850 TSS-320/TSS-320H/TSS-160
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.
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,
• AID=Access Identifier, identifies the entity access identifier. Only valid sdhFacility / AID
combinations are allowed, all other shall be rejected.
3
Examine output for PM information, as detailed in the relevant command guide, refer to
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Report Performance Monitoring (PM) Data
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:
• AID=Access Identifier, identifies the entity access identifier. Possible values: refer to
A.2 “Access Identifiers” (p. 611) according to the facility.
6
Go to Step 1.
Release 5.1 (ETSI)

September 2017
Retrieve and Change Site Identifier 1850 TSS-320/TSS-320H/TSS-160
7
END OF STEPS
6.71 Retrieve and Change Site Identifier

6.71.1 Purpose
This procedure provides instructions to retrieve or change the unique identifier for the NE.
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).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Retrieve and Change Site Identifier
cr lf lf
< SID >

<YY-MM-DD>
<HH:MM:SS> cr lf
M
<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.
Release 5.1 (ETSI)

September 2017
Retrieve Module Remote Inventory Information 1850 TSS-320/TSS-320H/TSS-160
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
END OF STEPS
6.72 Retrieve Module Remote Inventory Information

6.72.1 Purpose
This procedure provides instructions to retrieve module remote inventory information.
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Retrieve Module Remote Inventory Information

• POW320-{1-7}-{1-9}-{37,39} for Power Supply Filter TSS-320
• FAN320-{1-7}-{1-9}-{40,41} for FAN equipment
• 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
• MDL-{1-7}-{1-9} for Generic Shelf AID
• MDL-{1-7}-{1-9}-{1-39} for Generic Module AID
• MDL-{1-7}-{1-9}-{1-39}-{1-10} for Generic PIM/SFP AID
• XFP-{1-7}-{1-9}-{2-9,12-19,21-36}-1 for XFP on 10GSO modules
• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4} for SFP on 2G5SO or on CWLA modules
• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for SFP on 8XSO modules
• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} for SFP on 10XANY modules
• TBUS-{1-7}-{1-9}-{42,43} for ISPB Termination Bus
• 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
• SFP-{1-7}-{1-9}-{2-9,12-19}-{1-10} for SFP on PP10 modules
• XFP-{1-7}-{1-9}-{2-9,12-19}-1 for XFP on PP10GE modules
2
(p. 107).
Release 5.1 (ETSI)

September 2017
Retrieve Section Trace 1850 TSS-320/TSS-320H/TSS-160
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
END OF STEPS
6.73 Retrieve Section Trace

6.73.1 Purpose
This procedure provides instructions to retrieve the contents of the Section Trace message.
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Retrieve Section Trace
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
2
(p. 107).
Release 5.1 (ETSI)

September 2017
Retrieve System Configuration 1850 TSS-320/TSS-320H/TSS-160
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<AID>::TRC= /"<value>/",INCTRC=/"<value>/" [,EXPECTEDTRC=/"<value>

/"]" cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
END OF STEPS
6.74 Retrieve System Configuration

6.74.1 Purpose
This procedure provides the instructions to retrieve general system level and global system
configuration information.
None.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Retrieve System Configuration
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
(p. 107).
Release 5.1 (ETSI)

September 2017
Retrieve System Configuration 1850 TSS-320/TSS-320H/TSS-160
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:
1850TEST 08-05-16 10:33:39

M C0001 COMPLD
"::NODETYPE=UNVRSL320"
"ACTSW:1850TSS-320,,R03.00.15,05-02-20,320::COMPLETE"
/* RTRV-PRMTR-NE [Pad567] (2) */
;
4
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Retrieve TL1 Command Syntax
6.75 Retrieve TL1 Command Syntax

6.75.1 Purpose
This procedure provides the instructions to retrieve the syntax of a TL1 command, including a
description of the command parameters.
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
Release 5.1 (ETSI)

September 2017
Retrieve User Session Information 1850 TSS-320/TSS-320H/TSS-160
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
/* INPUT-FORMAT */ cr lf
[
/* INPUT-PARAMETER = <allowed values> */ cr lf]*

cr lf
/*
<Command
Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf
;
3
END OF STEPS
6.76 Retrieve User Session Information

6.76.1 Purpose
This procedure provides instructions to retrieve user session information.
None.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Retrieve User Session Information
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
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
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
(p. 107).
Release 5.1 (ETSI)

September 2017
Retrieve User Session Information 1850 TSS-320/TSS-320H/TSS-160
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
(
<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
part of the UID: % (percent sign), + (plus sign), # (pound sign), and _ (under score).
6
(p. 107).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Retrieve User Session Information
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
<value>" cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
7
Enter RTRV-STATUS;
8
(p. 107).
Release 5.1 (ETSI)

September 2017
Retrieve/Provision IP Address of NE 1850 TSS-320/TSS-320H/TSS-160
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
END OF STEPS
6.77 Retrieve/Provision IP Address of NE

6.77.1 Purpose
This procedure provides the instructions to retrieve and provision the IP address of the NE.
None
6.77.3 General
The NE has one provisionable IP address for all external IP communications via ethernet, local
LAN, and DCC.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Retrieve/Provision IP Address of NE
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.
The following port numbers are used:

• port 3082 (raw encoding)
• port 3083 (telnet encoding)
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.
2
Retrieve IP Address of NE
Enter RTRV-IP-ADDR;
3
(p. 107).
Release 5.1 (ETSI)

September 2017
Retrieve/Provision IP Address of NE 1850 TSS-320/TSS-320H/TSS-160
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;
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Security Defaults Administration
7
Observe output and verify change was made.
8
Go to Step 1.
9
END OF STEPS
6.78 Security Defaults Administration

6.78.1 Purpose
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.
Release 5.1 (ETSI)

September 2017
Security Defaults Administration 1850 TSS-320/TSS-320H/TSS-160
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.
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,
Output parameters related to security information are as follows:

• PAGE={0-999}
• PCND={0-999}
• PCNN={0-999}
• POINT={0-999}
• MININTVL=0-60
• MXINV=0-15
• TMOUT=0-999
• UOUT={0-999}
• KAMINTVL=0-240
3
To modify system-wide provisioned values, enter:
SET-ATTRSECUDFLT::::::[PAGE=][,PCND=][,PCNN=][,POINT=][,MININTVL=][,
MXINV=][,TMOUT=][,UOUT=][,KAMINTVL=][,MAXSESSION=][,SECACC=][,ICMP=][,
DHCP=] [,PHYSPORTS=];
Command Guide.
4
Observe the changes entering the retrieve command.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Set Performance Monitoring (PM) Mode
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=];
END OF STEPS
6.79 Set Performance Monitoring (PM) Mode

6.79.1 Purpose
This procedure provides the instructions to set or change Performance Monitoring (PM) mode for
specified GBE10, GBE, ODU2, OTU2, MAU, SDH FACILITY ports. The PM mode controls the data
collection for specific types of PM data (section, line, path, or all applicable locations).
None.
6.79.3 General
Each facility will support following PMSTATE:

• ON PM collection is enabled: current data are available and counting, history data are available,
current data and history data are retrievable.
• OFF PM is enabled and not counting: current data are available and not counting, history data
are available but always 0 if the whole period OFF, current data and history data are retrievable.
• DISABLED PM is disabled: current data and history data are not available and retrievable.
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.
Release 5.1 (ETSI)

September 2017
Set Performance Monitoring (PM) Mode 1850 TSS-320/TSS-320H/TSS-160
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:
• AID=Access Identifier, identifies the entity access identifier. Possible values:
- 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
- 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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Set Performance Monitoring (PM) Threshold Levels
− STM64AU416C-{1-7}-{1-9}-{2-9,12-19,21-36}-1-{1,17,33,49} for an AU4-16c embedded

within an STM64
− STM16AU416C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-1 for an AU4-16c in an STM16 on
a 2G5PSO or 10xANY
− STM64AU464C-{1-7}-{1-9}-{2-9,12-19,21-36}-1-1 for an AU4-64c embedded within an
STM64
− VCGLOVC12-{1-7}-{1-9}-{2-9,12-19}-{1-124}-{1-63} for a 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 a TU12 embedded within
a Modifiable VC4
− VCGLOVC3-{1-7}-{1-9}-{2-9,12-19}-{1-24}-{1-24} for a LO VC3 within a logical VCG on a
− MVC4TU3-{1-7}-{1-9}-{21,22,35,36}-{1-64}-{1-3} for a TU3 embedded within a Modifiable
VC4
- OTU2,, STM-64, 10GE , 10GFC
• LOCN=Location where PM data is to be enabled or disabled. Possible values:
− NEND Near End registers
− FEND Far End registers
− BIDIR Bidirectional registers
− ALL Near End, Far End and Bidirectionsl registers.
• MODETYPE=PM mode type to be enabled or disabled. Possible values:
− ALL PM for all applicable parameters is configured
− P PM for Path parameters is configured.
− S PM for RS parameters is configured
− L PM for MS parameters is configured
It varies for facility type.
4
END OF STEPS
6.80 Set Performance Monitoring (PM) Threshold Levels

6.80.1 Purpose
This procedure provides the instructions to set Performance Monitoring (PM) threshold levels for
DWDM, ETSI SDH, Packet profile types.
None.
Release 5.1 (ETSI)

September 2017
Set Performance Monitoring (PM) Threshold Levels 1850 TSS-320/TSS-320H/TSS-160
6.80.3 General
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.
2
(p. 107).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Set Performance Monitoring (PM) Threshold Levels
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)
Release 5.1 (ETSI)

September 2017
Slave TOD Card Management 1850 TSS-320/TSS-320H/TSS-160
− {E1} ETSI (PDH profile types)

− {GBE, MAU, TUSEG} (Packet 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
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: Entry is required if USERLABEL hasn't been entered
Note: The user label assigned to a TCA profile instance required if TCA-AID hasn't been
entered.
7
END OF STEPS
6.81 Slave TOD Card Management

6.81.1 Purpose
This procedure should be used for TOD card management in Slave mode.
6.81.2 General
Each slave clock has the following characteristics:

• It belongs to one clock domain, which might have multiple master capable clocks.
• It will have 1588 Slave logical port via which it synchronizes local clock with the master.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Slave TOD Card Management
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:
• CKMODE=SLAVE means that the PP1588 card is configured in Slave Clock Configuration.
Result:

• 1 PPS-IN port
• 1 PPS-OUT port
• 1 PTP slave port.
Note: PPS-IN, PPS-OUT and PTPSlave can be selected as input for CRU and for
internal Phase Distributor.
3
Select action:
Release 5.1 (ETSI)

September 2017

4
provisioned:
where:
I.e PPSIN Access Identifier, specifies the input port receiving the PPS signal
Note: In addition PPS-IN can be selected as input for CRU and for internal Phase
Distributor.
5
Enter:
RTRV-PPSIN::[AID];
system.
6
provisioned
where:
Release 5.1 (ETSI)

September 2017
Note: PPS-OUT is automatically locked to internal T0 and to the internal Phase

Distributor.
7
Enter:
the system.
8
Enter:
RTRV-PTPSLAVE:[TID]:[AID]:[CTAG];
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
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:
Release 5.1 (ETSI)

September 2017
where:
Values are:
Phase)
Values are:
reference
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

• in case of PTP logical Slave port as Provider Bridge UNI:
de-registration of PTP logical Slave port from Static S-VLAN Member Set;
• in case of PTP logical Slave port as VPLS UNI:
de-registration of PTP logical Slave port from VPLS Instance UNI/IWI Static Egress Ports
Release 5.1 (ETSI)

September 2017
13
guide.
14
15
16
The PTP logical slave port must be disabled at SNMP side. Please refer to the CLI command
guide.
17
Enter:
RMV-EQPT::AID;
or
ED-EQPT::AID:OOS;
where:
18
Enter:
DLT-EQPT::AID;
where:
END OF STEPS
Release 5.1 (ETSI)

September 2017
Set System Date and Time 1850 TSS-320/TSS-320H/TSS-160
6.82 Set System Date and Time

6.82.1 Purpose
This procedure provides the instructions to retrieve and change the system date and time.
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).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Set System Date and Time
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?
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
END OF STEPS
Release 5.1 (ETSI)

September 2017
Set System-Wide User Security Parameters 1850 TSS-320/TSS-320H/TSS-160
6.83 Set System-Wide User Security Parameters

6.83.1 Purpose
This procedure provides the instructions to retrieve and change the system-wide value for the user
security parameters related to the password aging (PAGE, PCNN, PCND, POINT), the minimum
interval between consecutive failed login attempts (MININTVL), the maximum number of failed login
attempts (MXINV), the input inactivity timeout (TMOUT), the user inactivity without login (UOUT),
the timeout value for the generation of the KEEP ALIVE MESSAGE autonomous message
(KAMINTVL), and the maximum number of sessions allowed for users that are able to change their
password (MAXSESSION).
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
(p. 107).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Set System-Wide User Security Parameters
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?
5
Set Default Security Parameters
Enter SET-ATTR-SECUDFLT::::::[PAGE=][,PCND=][,PCNN=][,POINT=]
[,MININTVL=][,MXINV=][,TMOUT=][,UOUT=][,KAMINTVL=] [,MAXSESSION=];
Release 5.1 (ETSI)

September 2017
Switch STMn Line to Protection 1850 TSS-320/TSS-320H/TSS-160
6
END OF STEPS
6.84 Switch STMn Line to Protection

6.84.1 Purpose
This procedure provides the instructions to initiate and release an STMn line switch to protection.
This procedure is used for MS-SPRING and MSP 1+1 configurations.
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Switch STMn Line to Protection
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.
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.
2
Retrieve Information on STMn Facilities and FFP
Enter RTRV-STMn::[AID];
where:
3
Examine output. Note states and other pertinent information.
4
where:
STMn=Optical facility type STM1, STM4, STM16, or STM64).
Release 5.1 (ETSI)

September 2017
Switch STMn Line to Protection 1850 TSS-320/TSS-320H/TSS-160
AID=STMn Facility Protection Group Access Identifier
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:
SWTCHCMD={FRCD, LOCKOUT, MAN} for Linear protections
Note: SWTCHCMD could be MAN only if no alarms are present.

SWTCHCMD={LOW-R, FRCD, FRCD-R, LOCKOUT, LOP-S, MAN, MAN-R} for MS-SPRING
protections
8
Go to Step 1.
9
Release STMn Protection Switch
Enter RLS-PROTNSW-STMn::AID;
where:
10
Go to Step 1.
11
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Switch VCn Line to Protection
6.85 Switch VCn Line to Protection

6.85.1 Purpose
This procedure provides the instructions to initiate and release an VC-n line switch to protection.
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.
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
2
Retrieve Information on VC-n Facilities
Enter RTRV-VCn::[AID];
where:
VCn/STSn=Facility type{VC4, VC44C, VC416C, VC464C, LOVC12, LOVC3)
Release 5.1 (ETSI)

September 2017
Switch VCn Line to Protection 1850 TSS-320/TSS-320H/TSS-160
AID=VCn/STSn facility access identifier
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 System Access Control (intrusion alarm)
11
Go to Step 1.
12
END OF STEPS
6.86 System Access Control (intrusion alarm)

6.86.1 Purpose
Use this procedure to configure the INTRUSION alarm for an userID.
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.
Release 5.1 (ETSI)

September 2017
System Access Control (intrusion alarm) 1850 TSS-320/TSS-320H/TSS-160
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.
To clear INTRUSION alarm for an UID:

• delete UID (secu admin performs this operation when he considers the INTRUSION a real
attack), go to Step 7
• re-allow UID (secu admin performs this operation when he considers the INTRUSION a
simple mistake by a valid UID), go to Step 8
7
Enter:
DLT-USER-SECU::UID;
where.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Users with Security Administrator Privileges Overview

Result: The NE clears the INTRUSION alarm for that UID.
8
Enter:
ALW-USER-SECU:::::UID;
where.
Result: The NE clears the INTRUSION alarm for that UID.
END OF STEPS
6.87 Users with Security Administrator Privileges Overview

6.87.1 Overview
In this release new procedure have been described to:

• Define and assign user privileges
• Add and delete user IDs
• Disable/enable users
• Initialize and reset login passwords
• Set the system’s and user's aging threshold for login passwords
• Remove a lockout or change the system’s lockout timer value
• Set the system’s inactivity timer value
• Manage system security logging processes
• List any user-id or session, and have the option to terminate it.
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.
Release 5.1 (ETSI)

September 2017
Virtual Concatenation Path Check 1850 TSS-320/TSS-320H/TSS-160
• Set command privilege partitioning.
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.
A “user profile” consists of:

• the user identifier (UID),
• the user’s password identification (PID),
• the user’s command authorization privilege (UAP),
• the user’s password age (PAGE),
• the numbers of days allowed to the user to change the password after the password expiration
(PCND),
• the number of logins allowed to the user to change the password after the password expiration
(PCNN),
• the user’s password obsolescence interval (POINT),
• the user’s maximum allowed inactivity period without login (UOUT),
6.88 Virtual Concatenation Path Check

6.88.1 Purpose
This procedure provides the instructions to enable or disable the traffic through the Virtual
Concatenation paths of the addressed VCG.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Virtual Concatenation Path Check
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.
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.
Release 5.1 (ETSI)

September 2017
Modify Equipment Management for Data units 1850 TSS-320/TSS-320H/TSS-160
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
/*
*/ cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
3
END OF STEPS
6.89 Modify Equipment Management for Data units

6.89.1 Purpose
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).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Modify Equipment Management for Data units
• 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.
Table 27 Supported features in the modified AIDs
AID to be modified Allowed new AID Not supported Description

features in the new
AID
PP10GEX2 PP10GE6 T-MPLS In case of presence
PP10GE10 of TUSEG with
OAM-TYPE =
T-MPLS
PWOAM In case of PWSEG
with MEP = ENABLE
Section OAM In case of MPLSIF
with MEP = ENABLE
NNI ring In case of PORT that
are Ring NNI
Access ring In case of UNI PORT
crossconnected to an
Ring NNI
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)
Release 5.1 (ETSI)

September 2017
• 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
Perform the following steps:
1
Enter RTRV-EQPT::ALL;
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:
− 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)
Release 5.1 (ETSI)

September 2017
− PP10GE6-{1-7}-{1-9}-{3,5,7,9,13,15,17,19} ENH (Packet Module 6x10Gb)

• NEWPROVISIONED TYPE = The Nokia mnemonic stored in the Remote Inventory EPROM
for the given equipment.
− PP1GEX20 UNIV Packet Module 20x1GbEthernet (Packet Module 20G)
− PP1GE20E UNIV Packet Module 20x1GbEthernet Evolution (20G)
− PP10GE2E UNIV Packet Module 2x10GbEthernet Evolution (20G)
− PP10GE6 ENH Packet Module 6x10GbEthernet (Packet Module 60G)
− PP10GE10 ENH Packet Module 10x10GbEthernet (Packet Module 100G)
Result:
This command fails under the following conditions:

• An Equipment Entity is addressed in a Shelf that has a PROVISIONEDTYPE equal to
UNVRSL160, and its slot-level AID number is either between 2 and 9 or between 21 and 28
• The addressed AID is a PP1GE and the NEWAID and /or the NEWPROVISIONEDTYPE are
not related to a Packet Module 20x1GbEthernet
• The addressed AID is a PP10GE and the NEWAID and /or the NEWPROVISIONEDTYPE
are not related to a Packet Module 2x10GbEthernet
• The equipment entity is not provisioned
• The command is input for an AID which is different from the one provisioned in the
corresponding slot
• The entity is not in OOS-[AU]MA state
• The command is entered to change the AID/PROVISIONEDTYPE of an Equipment AID but
they are not allowed to be hosted in that Shelf (eg. because of the <320Shelf> tag set on it)
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.
Release 5.1 (ETSI)

September 2017
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
END OF STEPS
6.89.4 Modify 20G to 20G V1 and V2 (Legacy to Enhanced)
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).
Release 5.1 (ETSI)

September 2017
6.89.7 Procedure
Perform the following steps:
1
To retrieve the compatible cards, enter RTRV-COMPATIBLE:[TID]:AID:[CTAG];
where:
• PP1GEX20-{1-7}-{1-9}-{2-9,12-19} (Packet Module 20x1Gb)
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:
− 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.
− PP1GE20E Packet Module 20x1GbEthernet Evolution (20G)
− PP10GE2E Packet Module 2x10GbEthernet Evolution (20G)
Command Guide
3
Enter RTRV-EQPT::ALL; and verify that the AID and PROVISIONEDTYPE match the new
card.
4
END OF STEPS
Release 5.1 (ETSI)

September 2017
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 S320H Shelf Detailed Level Procedure
7 S320H Shelf Detailed Level Procedure
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.1 Overview 451

7.2 Provision Equipment (S320H) 451
7.3 Administer S320H module 455
7.2 Provision Equipment (S320H)

7.2.1 Purpose
This procedure provides instructions to provision “enhanced shelf” shelves, boards/circuit packs
and modules in the system.
7.2.2 Prerequisites
The Enhanced Shelf version is S320H (ENH Shelf 320). Mandatory equipment shall be
automatically provisioned whether present or not.
The following equipment is mandatory and is automatically pre-provisioned/created in the system:

• For the Main shelf:
• dual MXEC320
• PSF320H
• FAN320H
• TBUS
• Mandatory Card HKPCNTC
Release 5.1 (ETSI)

September 2017
Provision Equipment (S320H) 1850 TSS-320/TSS-320H/TSS-160
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;
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Provision Equipment (S320H)
Enter ENT-EQPT::SHELF-{1-7}-{1-9}::::[PROVISIONEDTYPE=] [,AINSMODE=][,

SHELFNUM=][,SHELFROLE=][,LAMBDASET=][,ALMPROF=][,CLNTSEL=][,OPWRLOT2=]
[,SSBIT=]:[PST];
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
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)
This command fails when:

• the first ENT command received is not the one related to AID Assignment to the Main Shelf
• the first ENT command received is the one related to AID Assignment to the Main Shelf, but
at least one of the paramters 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
6
Go to Step 7.
7
Unit provision
Verify the unit is in appropriate slot. Refer to the figures below:
Release 5.1 (ETSI)

September 2017
Provision Equipment (S320H) 1850 TSS-320/TSS-320H/TSS-160
Figure 31 S320H enhanced shelf (operator view)
8
SHELFROLE=][,LAMBDASET=][,ALMPROF=][,CLNTSEL=][,OPWRLOT2=][,SSBIT=]:
[PST];
where:
values: refer to B.3 “AIDs” (p. 692) or to “Command details” (p. 107).
given equipment.
For possible values please refer to B.4 “Provisioned Types” (p. 693).
For Card's administration details please refer to 7.3 “Administer S320H module” (p. 455).
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer S320H module
9
Is the board provided with an XFP or SFP module?
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=][,
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).
12
END OF STEPS
7.3 Administer S320H module

7.3.1 Purpose
This procedure provides instructions to provision “enhanced shelf” boards/circuit packs and
modules in the system.
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
Release 5.1 (ETSI)

September 2017
Administer S320H module 1850 TSS-320/TSS-320H/TSS-160
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.

Main shelf must be already present and provisioned.
If a Shelf is entered, the mandatory cards will be autocreated and creation notifications are sent.
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.
Release 5.1 (ETSI)

September 2017
• To modify boards, go to Step 9.
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
SHELFROLE=][,LAMBDASET=][,ALMPROF=][,CLNTSEL=][,OPWRLOT2=][,SSBIT=]:
[PST];
where:
values see “Procedure” (p. 457).
given equipment.
For possible values please refer to “Procedure” (p. 457).
AID Provisioned Type Description

ETSI 63 x E1 Port
[ETSI] E1M-{1-7}-{2}-{7-14} [ETSI] P63E1
Module
ETSI 63 x E1 Access
[ETSI] A63E1A
[ETSI] E1ACC-{1-7}-{2}-{3-5,16- Module 75ohm unb
18} ETSI 63 x E1 Access
[ETSI] A63E1B
Module 120ohm bal
ETSI 63 x E1 Access
[ETSI] E1PR-{1-7}-{2}-{2,19} [ETSI] LSPROT
Protection Module
10G Synchronous
1P10GSO
10GSO-{1-7}-{1-9}-{2-9,12-19, Optical
21-36} 10G Synchronous
1P10GSOE
Optical Evolution
Release 5.1 (ETSI)

September 2017

2G5SO-{1-7}-{1-9}-{2-9,12-19, 4x2.5G Synchronous
4P2G5SO
21-36} Optical
8XSO-{1-7}-{1-9}-{2-9,12-19,21- 8 x Synchronous
8PSO
36} Optical
MRSOE-{1-7}-{1-9}-{2-9,12-19, SDX/SONET Multirate
MRSOE
21-36} Card
OT2TDM-{1-7}-{1-9}-{2-9,12-19,
1POTU2 G.709 OTU 10GB Card
21-36}
OT2TDMXB-{1-7}-{1-9}-{2-9,12- G.709 OTU 10GB Card
1POTU2XB
19,21-36} - XFP based
10XANY-{1-7}-{1-9}-{2-9,12-19,
10XANY 10GB 10 x GBE/Sonet
21-36}
PRE-{1-7}-{1-9}-{2-9,12-19,21- Optical Pre-Amplifer
PRE10G
36} 10G
BOOST-{1-7}-{1-9}-{2-9,12-19,
BOOST10G Optical Booster 10G
21-36}
DWDM Optical
DWLA10X-{1-7}-{1-9}-{2-9,12-
DWLA10X Transponder with
19,21-36}
Colored XFPs
MultiService Adaptation
PP10AD-{1-7}-{1-9}-{2-9,12-19} PP10MS Card (Packet Module
10G)
ETSI MultiService
Adaptation Card for
PP10AD-{1-7}-{1-9}-{2-9,12-19} [ETSI] PP10GATM
ATM (Packet Module
10G)
ETSI UGW Adaptation
PPUGW-{1-7}-{1-9}-{2-9,12-19} [ETSI] PP2G5UGW Card - Packet Module
2.5G
Packet Module
PP1GEX20-{1-7}-{1-9}-{2-9,12-
PP1GE20E 20x1GbEthernet
19}
Evolution (20G)
PP10GE2E Packet
PP10GEX2-{1-7}-{1-9}-{2-9,12- Module
PP10GE2E
19} 2x10GbEthernet
Evolution (20G)
Release 5.1 (ETSI)

September 2017

Time Of Day - TOD
PTP-{1-7}-{1-9}-{2-9,12-19,21-
PP1588 Card
36}
PTP Packet Processor
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).
Example: The following command performs logical removal for the module 10GSO-1-1-5.
ED-EQPT:: 10GSO-1-1-5:::::OOS;
10
Remove board
Release 5.1 (ETSI)

September 2017
To place in the out-of-service management service state specified equipment enter:
RTRV-EQPT::AID;
where:
Note: See also Step 9.
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.
Note: A forced removal may result in an interruption of traffic.

Enter:
RMV-EQPT::AID:::FRCD;
15
Enter:
RMV-EQPT::AID:::NORM;
16
Go to Step 1.
17
Restore board
Release 5.1 (ETSI)

September 2017
Enter:
RTRV-EQPT::AID;
where:
Note: See also Step 9.
18
Observe output.
19
To place in the IS or OOS-AU primary state specified equipment, enter
RST-EQPT::AID:::[MODE];
where:
• 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
Release 5.1 (ETSI)

September 2017
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 TMPLS/MPLS-TP Detailed Level Procedure
8 TMPLS/MPLS-TP Detailed Level Procedure
8.1 Overview
8.1.1 Purpose
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.1 Overview 463

8.2 Administer MPLS-TP Loopback OAM tool 464
8.3 Administer MPLS-TP Connectivity verification Loopback OAM tool 471
8.4 Administer MPLS-TP Diagnostic Loopback OAM tool 479
8.5 Administer MPLS-TP Discovery Loopback OAM tool 486
8.6 Administer (T-MPLS/MPLS-TP) DM tool 491
8.7 Administer T-MPLS Facility Protection Group 497
8.8 Administer T-MPLS Global Network Parameters 502
8.9 Administer T-MPLS/ MPLS-TP Node configuration 504
8.10 Administer T-MPLS OAM (T-MPLS Tunnel protection) 507
8.11 Administer T-MPLS Pseudo Wire 510
8.12 Administer T-MPLS Pseudo Wire Segment 514
8.13 Administer T-MPLS Pseudo Wire Segment Cross-Connection 517
8.14 Administer T-MPLS Traffic Descriptor 521
8.15 Administer T-MPLS Tunnel 524
8.16 Administer TMPLS Tunnels Group 528
8.17 Administer T-MPLS Tunnel Segment 531
8.18 Administer T-MPLS Tunnel Segment Cross-Connection 535
8.19 Proactive DM 538
8.20 Proactive LM (Synthetic Loss Measurement) 543
8.21 Report Performance Monitoring (PM) Data for T-MPLS 550
8.22 Set Performance Monitoring (PM) Data for T-MPLS 552
Release 5.1 (ETSI)

September 2017
Administer MPLS-TP Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160
8.2 Administer MPLS-TP Loopback OAM tool

8.2.1 Purpose
This procedure provides the instructions to configure, dis/enable, change, delete the MPLS-TP
Loopback OAM tool.
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
• Start Date & TIME, and End Date & TIME, or Number of LBM frames to be sent Activation of
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Loopback OAM tool
bidirectional connectivity verification (this can be done only if the source MEP and the target
MIP have been configured with all expected parameters).
configure Test-Type.
8.2.3 TL1 Commands

The ENT-TMPLS-ODLB command creates On Demand OAM LB (Loop Back) tools.
When the Operator wants START/STOP LB-Tool will use SET-TMPLS-ODOAM command
specifying TOOL parameter proper value.
The TMPLS facility involved in Loopback must be Bidirectional, Terminated and with MEP enabled.
The TMPLS facility involved in Loopback must have OAM-TYPE=MPLS_TP.
If the parameters TARGET-MEPID=NOTARGET and TARGET-MIPID=NOTARGET and
DISCOVERY=NODISCOVERY then this command will be refused.
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.
Check before performing MPLS-TP Loopback OAM tool that:

• at Node-Level the number of started LB-Tools does not exceed the allowed maximum number.
• 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
Release 5.1 (ETSI)

September 2017
• 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.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
Release 5.1 (ETSI)

September 2017
• 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
Release 5.1 (ETSI)

September 2017
− STOP The tool stops sending/receiving packets
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 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
Release 5.1 (ETSI)

September 2017
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:
where:
8
Examine output.
9
Enter:
DLT-TMPLS-ODLB]:AID;
where:
10
To retrieve the DM data
Enter:
where:
TERM-AID = AID of the Terminated TMPLS facility where the LB-Tool has been configured.
Result:
Some OUTPUT PARAMETERS are:

• NE-LB-TOOLS = Reports LB-Tool info at Node Level.
• LB-TOOL-STATE = Reports LB-Tool state
• TARGET-MEPID = The MEP Identifier of peer MEP where MPLS-TP LBM is destinated for.
Release 5.1 (ETSI)

September 2017
• SEND-PKT-NUM = Number of LBM packets to send or already sent

• DISCOVERY = This parameter reports if the ingress or egress MIP has to be addressed in
the discovery case.
11
Retrieve LB tool measurement results
Enter:
where:
12
Examine output.
If YES, Step 13.
13
Enter:
RTRV-TMPLS-ODLBOUTPUT::AID;
where:
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:
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Connectivity verification Loopback OAM tool
8.3 Administer MPLS-TP Connectivity verification Loopback OAM tool

8.3.1 Purpose
This procedure provides the instructions to administer Connectivity verification loopback (TARGET
= MEP/MIP).
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
• 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).
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
• 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).
configure Test-Type.
Release 5.1 (ETSI)

September 2017
Administer MPLS-TP Connectivity verification Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160
Figure 32 MEP/MIP configuration for loopback connectivity verification

MEP=ENABLE.
Release 5.1 (ETSI)

September 2017
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=]
Release 5.1 (ETSI)

September 2017
[,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:
Remember: It is required that the TUSEG involved must have:
− DIR = BIDIR
− MEP = enable
Release 5.1 (ETSI)

September 2017
− TYPE=TERMINATED
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;
tool from a TUSEG.
7
Connectivity verification loopback (TARGET = MIP)
Enter:
ENT-TMPLS-ODLB::AID::::[,SRC-ID=][,TTL=][,TARGET-MIPID=][,DISCOVERY=];
where:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
• 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.
{ENABLE, DISABLE}
tool from a TUSEG.
Release 5.1 (ETSI)

September 2017
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:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
{ENABLE, DISABLE}
• 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)
• 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
enter:
Release 5.1 (ETSI)

September 2017
[,TARGET-MIPID=][,DISCOVERY=][,TEST-TLV=][,TEST-TYPE=];
where:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
{ENABLE, DISABLE}
• PKT-LENGTH = 105 – 1500 (Default = 105).
Restrictions: If TEST-TLV = ENABLE and SRC-ID = ENABLE and TEST-TYPE = 0, 2 then
PKT-LENGTH ≥ 105
• TEST-TLV = ENABLE.
• 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
enter:
Release 5.1 (ETSI)

September 2017
where:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
{ENABLE, DISABLE}
Restrictions: If TEST-TLV = ENABLE and SRC-ID = ENABLE and TEST-TYPE = 1, 3 then
PKT-LENGTH ≥ 109
Where:
1 = Null signal (all-zeros) with CRC-32.
3 = PRBS 2-31-1 with CRC-32.
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Diagnostic Loopback OAM tool
8.4 Administer MPLS-TP Diagnostic Loopback OAM tool

8.4.1 Purpose
This procedure provides the instructions to configure, dis/enable, change, delete the MPLS-TP
Diagnostic Loopback OAM tool.
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.
Figure 33 Diagnostic loopback

Release 5.1 (ETSI)

September 2017
Administer MPLS-TP Diagnostic Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160
MEP=ENABLE.
8.4.4 Procedure
1
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:
Release 5.1 (ETSI)

September 2017
4
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:
• DIR = BIDIR
• MEP=ENABLE
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)
Release 5.1 (ETSI)

September 2017
Enter:
where:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not
{ENABLE, DISABLE}
tool from a TUSEG.
7
Diagnostic loopback (TARGET = MIP)
Enter:
ENT-TMPLS-ODLB::AID::::[,SRC-ID=][,TTL=][,TARGET-MIPID=][,DISCOVERY=];
where:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
Release 5.1 (ETSI)

September 2017
{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)
tool from a TUSEG.
8
Diagnostic loopback - No test TLV
enter:
[,TARGET-MIPID=][,DISCOVERY=][,TEST-TLV=];
where:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
{ENABLE, DISABLE}
• PKT-LENGTH = 45, 48 – 1500(Default = 45).
Restrictions: If TEST-TLV = DISABLE and SRC-ID = DISABLE then PKT-LENGTH ≥ 45 and
≠ (46, 47)
Release 5.1 (ETSI)

September 2017
• TEST-TLV = DISABLE.
9
Diagnostic loopback - Test TLV without CRC
enter:
where:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
{ENABLE, DISABLE}.
Restrictions: If TEST-TLV = ENABLE and SRC-ID = DISABLE and TEST-TYPE = 0, 2 then
PKT-LENGTH ≥ 49
Where:
0 = Null signal (all-zeros) without CRC-32.
Release 5.1 (ETSI)

September 2017
2 = PRBS 2-31-1 without CRC-32.
10
Diagnostic Loop - Test TLV with CRC enabled
enter:
where:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
{ENABLE, DISABLE}
• PKT-LENGTH = 101, 104 – 1500 (Default = 101).
Restrictions: If TEST-TLV = ENABLE and SRC-ID = DISABLE and TEST-TYPE = 1, 3 then
PKT-LENGTH ≥ 53
Where:
1 = Null signal (all-zeros) with CRC-32.
Release 5.1 (ETSI)

September 2017
Administer MPLS-TP Discovery Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160
3 = PRBS 2-31-1 with CRC-32.
END OF STEPS
8.5 Administer MPLS-TP Discovery Loopback OAM tool

8.5.1 Purpose
This procedure provides the instructions to perform the MPLS-TP Discovery Loopback OAM tool.
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.
Figure 34 Discovery loopback - target = MEP
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Discovery Loopback OAM tool
Figure 35 Discovery loopback - target = MIP
8.5.3 DISCOVERY sequence

N Loopback instances are created with the required value for TTL and DISCOVERY = ingress /
egress -> ODLBS-i AID are generated.
Ranging addressing value for TTL and DISCOVERY can be used in the ENT-TMPLS-ODLB
command.
The SET command is used for starting/stopping the sending of LBM packets.
Then the required number of LBM packets for each Loopback instance is sent, considering in the
generation of the LBM packet the pre-established range of TransID for the Loopback instances
The received LBR packets are addressed to the associated Loopback instance considering the
value of the TransID, so the type of DISCOVERY (ingress/egress) associated to the ODLBS-i AID
can be retrieved; received TTL and REPLY ID can be retrieved from the LBR packets.
Distance of the MIP/MEP can be calculated using the received value for TTL DISTANCE = 255 –
received TTL + 1

Release 5.1 (ETSI)

September 2017
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
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:
4
BIDIR, MEP=ENABLE.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Discovery Loopback OAM tool
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:
• DIR = BIDIR
• MEP=ENABLE
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:
where:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
Release 5.1 (ETSI)

September 2017
• 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.
{ENABLE, DISABLE}
• DISCOVERY = INGRESS EGRESS. It indicates if the ingress or egress MIP has to be
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:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
• 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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer (T-MPLS/MPLS-TP) DM tool
{ENABLE, DISABLE}
• 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
• DISCOVERY = INGRESS, EGRESS. It indicates if the ingress or egress MIP has to be
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 Administer (T-MPLS/MPLS-TP) DM tool

8.6.1 Purpose
This procedure provides the instructions to configure, dis/enable, change, delete the DM tool.
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).
Release 5.1 (ETSI)

September 2017
Administer (T-MPLS/MPLS-TP) DM tool 1850 TSS-320/TSS-320H/TSS-160
• 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.
The specific behavior of this command is related to ENT-TMPLS-<tool> commands.

• Enable OAM tools. OAM packets will be sent towards the peer MEP point and process packets
received.
• Stop OAM tools. OAM Tool doesn't send Packets.
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).
Release 5.1 (ETSI)

September 2017
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.
Release 5.1 (ETSI)

September 2017
• To retrieve the DM data, see Step 6.
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”
Release 5.1 (ETSI)

September 2017
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.
RTRV-TMPLS-OD2WAYDM command).
• SEND-PKT-NUM = Number of DMM packets to send.
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.
RTRV-TMPLS-OD2WAYDM command).
• START-TIME = This parameter is used to establish when Sender DM-Tool starts to send
Release 5.1 (ETSI)

September 2017
DMM packets. The format is START-TIME=YY-MM-DD-hh-mm-ss. Warning: SEND-PKT-

NUM parameter has priority on this parameter.
RTRV-TMPLS-OD2WAYDM command). This parameter can't be entered together with
SEND-PKT-NUM parameter. If START-TIME is antecedent to "Current System Date-Time"
then command will be refused.
• END-TIME = This parameter is used to establish when Sender DM-Tool stops to send
packets. The format is END-TIME=YY-MM-DD-hh-mm-ss. Warning: SEND-PKT-NUM
parameter has priority on this parameter Let be QT-SEC=(END-TIME)-(START-TIME)(sec.)
and FREQ=(1/PERIOD)(pkt/sec) then QT-SEC * FREQ can't be greater than 10.000 pkt.
RTRV-TMPLS-OD2WAYDM command). This parameter can't be entered together with
SEND-PKT-NUM parameter. If END-TIME is antecedent or equal to START-TIME then the
command will be refused
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Facility Protection Group
TERM-AID= DM-PHB= DM-TOOL-STATE= PERIOD= END-PKT-NUM= PKT-LENGTH=

START-TIME= END-TIME=
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 Administer T-MPLS Facility Protection Group

8.7.1 Purpose
This procedure provides the instructions to retrieve information, create, and delete a facility
protection group.
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.
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Facility Protection Group 1850 TSS-320/TSS-320H/TSS-160
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.

Before entering the ENT-FFP-TMPLS verify that:
• the both WRK/PROT Tunnels of this FFP don't have STATUS=OFF
• one of the specified tunnel segment which shall become member of the new FFP is not already
a member of another FFP protection group
• one of the specified tunnel which shall become member of the new FFP is not already a member
of a TMPLS GROUP created previously with the ENT-TMPLS-GROUP
Release 5.1 (ETSI)

September 2017
• the Tunnel used as TUNNEL-WKG/TUNNEL-PROTN is not referenced by a TUSEG with ADD-

GROUP = TRUE
• MEP is already defined for WKG tunnel and MEP is already defined for PROTN tunnel
(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
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
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-
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Facility Protection Group 1850 TSS-320/TSS-320H/TSS-160
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.
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.
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
Release 5.1 (ETSI)

September 2017
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.
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:
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Global Network Parameters 1850 TSS-320/TSS-320H/TSS-160
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
END OF STEPS
8.8 Administer T-MPLS Global Network Parameters

8.8.1 Purpose
This procedure provides the instructions to retrieve information, and modify global network
parameters assigned to T-MPLS, such as range for CV Period into OAM CV frames, range for user-
defined PHB profiles and granularity of T-MPLS PM counters.
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.
2
Enter RTRV-TMPLS-GLOBAL:::;
3
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Global Network Parameters
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"::OAM-CVPERIOD-SEL=<value>, PHB-RANGE-SEL=<value> "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=];
6
Go to Step 1.
7
END OF STEPS
Release 5.1 (ETSI)

September 2017
Administer T-MPLS/ MPLS-TP Node configuration 1850 TSS-320/TSS-320H/TSS-160
8.9 Administer T-MPLS/ MPLS-TP Node configuration

8.9.1 Purpose
This procedure provides the instructions

• to generate, receive and process T-MPLS and MPLS OAM packets at node level
• perform T-MPLS to MPLS-TP migration.
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.4 OAM generation

There is a configurable parameter for NE OAM-TYPE-SEL= T-MPLS, MPLS_TP.
This is the default value for the OAM supported by Tunnels created since the change of the value of
this NE parameter.
It is possible to change the OAM selection with Tunnel granularity, allowing for single Tunnel a
different value from the default node selection.
8.9.5 OAM reception and processing

There is a configurable parameter for NE OAM-RX-DETECT = TYPE-SEL, BOTH.
This parameter provides the possibility to select between the reception and processing of both
T-MPLS and MPLS-TP OAM tools or of only the OAM tools configured for generation at Tunnel
level.
By default the behaviour that allows to receive and to process both T-MPLS and MPLS-TP is
selected. A change of this configuration affects all the already created Tunnel Termination.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS/ MPLS-TP Node configuration
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.
2
Enter RTRV-TMPLS-GLOBAL:::;
3
Release 5.1 (ETSI)

September 2017
Administer T-MPLS/ MPLS-TP Node configuration 1850 TSS-320/TSS-320H/TSS-160
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"::OAM-CVPERIOD-SEL=<value>, PHB-RANGE-SEL=<value> "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.
BOTH T-MPLS and MPLS_TP. I.e. the receiver MEP accepts both “OAM T-MPLS packets”
and “MPLS_TP OAM packets”.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS OAM (T-MPLS Tunnel protection)
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.
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
END OF STEPS
8.10 Administer T-MPLS OAM (T-MPLS Tunnel protection)

8.10.1 Purpose
This procedure provides the instructions to enable T-MPLS Tunnel protection (bidirectional case,
but could be extended to unidirectional tunnels).
Release 5.1 (ETSI)

September 2017
Administer T-MPLS OAM (T-MPLS Tunnel protection) 1850 TSS-320/TSS-320H/TSS-160
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS OAM (T-MPLS Tunnel protection)
8.10.4 Procedure
1
Bidirectional tunnels in the Protection Group creation
Create two TUSegments Main and Spare on the first NE:

• ENT-TMPLS-TUSEG:::::MPLSIF-x-x-x-x,TERMINATION,BIDIR:INLABEL=main_
inlabel,OUTLABEL=main_outlabel,MEP=ENABLE,MEG-ID=main_megid,MEP-ID=
main_mep_id,EXPMEP-ID=main_expmep_id,CVRX=ENABLE,CVTX=ENABLE,
CVPERIOD=main_cvperiod;
• ENT-TMPLS-TUSEG:::::MPLSIF-y-y-y-y,TERMINATION,BIDIR:INLABEL=spare_
inlabel,OUTLABEL=spare_outlabel,MEP=ENABLE,MEG-ID=spare_megid,
MEP-ID=spare_mep_id,EXPMEP-ID=spare_expmep_id,CVRX=ENABLE,CVTX=
ENABLE,CVPERIOD=spare_cv_period
where:
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 = 13 ASCII chars string. It must be unique in the system
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.
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.
CVRX= ENABLE, DISABLE. Enabling/disabling capability to detect the Loss Of Continuity
(LOC) alarm, associated to Sink TUSegment Termination.
CVTX= ENABLE, DISABLE. Enabling/disabling transmission of CV packets, associated to
Source TUSegment Term.
CVPERIOD= (3.33ms,10ms,100ms,1s,10s,20ms,50ms,1m,10m). Period (1/Frequency) of CV
packet transmission.
2
On the far end NE repeat Step 1, i.e.:
create two TUSegments (Main and Spare) exchanging parameters, i.e.

• ENT-TMPLS-TUSEG:::::MPLSIF-x-x-x-x,TERMINATION,BIDIR:INLABEL=main_
outlabel,OUTLABEL=main_inlabel,MEP=ENABLE,MEG-ID=main_megid,MEP-ID=
main_expmep_id,EXPMEP-ID=main_mep_id,CVRX=ENABLE,CVTX=ENABLE,
CVPERIOD=main_cvperiod;
• ENT-TMPLS-TUSEG:::::MPLSIF-y-y-y-y,TERMINATION,BIDIR:INLABEL=spare_
outlabel,OUTLABEL=spare_inlabel,MEP=ENABLE,MEG-ID=spare_megid,
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Pseudo Wire 1850 TSS-320/TSS-320H/TSS-160
MEP-ID=spare_expmep_id,EXPMEP-ID=spare_mep_id,CVRX=ENABLE,CVTX=
ENABLE,CVPERIOD=spare_cv_period
Note: If errors occur some alarms would araise.
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 Administer T-MPLS Pseudo Wire

8.11.1 Purpose
This procedure provides the instructions to retrieve information, create, and delete a Pseudo Wire
to be used on 1850 TSS-320, TSS-320H and TSS-160 product.
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
The Pseudo Wire (PW) can be:

• Terminated
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Pseudo Wire
• Stitched (= swapped) in case of Multi-Segment PW
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).
In case of PW stitching (label swap):

• two segments are created by ENT-TMPLS-PWSEG (each of them creates internally a pwEntry)
with the option "swap".
• ENT-TMPLS-CRSPWSEG command is used to connect the two PW.
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.
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Pseudo Wire 1850 TSS-320/TSS-320H/TSS-160
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer 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.
6
Go to Step 1.
NOTICE
Equipment damage hazard

Possibility of service interruption. Editing port parameters of a traffic bearing port can adversely
affect service.
Modify T-MPLS Pseudo Wire
Enter ED-TMPLS-PW::AID::::[,DESCR=][,TD-ID=][,STATUS=] [,VT-HEAD=][,
VT-TAIL=];
where: AID = AID of PW that defines PW AID. Possible values: PW-{1-7}-{1-9}-{1-64000} in the
Rack, Shelf, PW index, format.
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).
9
Does Pseudo Wire Termination associated to VPLS?
If yes, erase services and VPLS facility (For details, refer to 8DG09603EAAATQZZA —
Line Interface Guide
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Pseudo Wire Segment 1850 TSS-320/TSS-320H/TSS-160
10
Does Pseudo Wire involved in PW swapping?
If yes, see 8.13 “Administer T-MPLS Pseudo Wire Segment Cross-Connection” (p. 517).
11
Delete T-MPLS Pseudo Wire Segment
Does Pseudo Wire Segment is active?
If yes, see WARNING.
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.
Note: A pseudowire could be deleted only if its STATUS = OFF.

Result: After this command, all the corresponding PWSEG and CRSPWSEG are deleted.
13
END OF STEPS
8.12 Administer T-MPLS Pseudo Wire Segment

8.12.1 Purpose
This procedure provides the instructions to retrieve information, create, and delete a PWSegment to
be used on 1850 TSS-320, TSS-320H and TSS-160 product.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Pseudo Wire Segment
The RTRV-TMPLS-PWSEG command retrieves the provisioned parameters for MPLS

PWSegments.
The ED-TMPLS-PWSEG command edits MPLS PWSegment parameters.
Table 28 PST usage rules depending on PWSegment current PST value
PWSEG PST PWSEG current PST

entered IS OOS-AU OOS-MA OOS-AUMA
IS Denied Denied IS OOS-AU
OOS OOS-MA OOS-AUMA Denied Denied

PWSegments.
The DLT-TMPLS-PWSEG command deletes the provisioned Swapped T-MPLS PWSegment entity.
Terminated PWSegment can be automatically deleted using DLT-TMPLS-PW command.
For Termination PWSegment, the command will be refused because on PWSegment there is still
the PW automatically generated (see ENT-TMPLS-PWSEG).
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.
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.
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Pseudo Wire Segment 1850 TSS-320/TSS-320H/TSS-160
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
"<AID>: <PORT>, <TYPE>, <DIR>[ ,

<USERNAME>]:[L2ENCAPPROF-AID=<value>,]INLABEL=<value>, OUTLABEL=
<value>, PHBPROF-AID=<value>, ACD=<value>[,CW=<value>]:<PST>"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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Pseudo Wire Segment Cross-Connection
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}.
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?
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
END OF STEPS
8.13 Administer T-MPLS Pseudo Wire Segment Cross-Connection

8.13.1 Purpose
This procedure provides the instructions to retrieve information, create, and delete a cross-connect
entity and establishes a one-way, two-way cross-connection between the specified PWSegments.
None.
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Pseudo Wire Segment Cross-Connection 1850 TSS-320/TSS-320H/TSS-160
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).
Table 29 CCT usage rules depending on PWSegment DIR parameter
FROM PWSegment DIR TO PWSegment DIR CCT value allowed

BIDIR BIDIR 2WAY
BIDIR BIDIR 1WAY
BIDIR UNIDIROUT 1WAY
BIDIR UNIDIRIN CRS not allowed
UNIDIRIN BIDIR 1WAY
UNIDIRIN UNIDIROUT 1WAY
UNIDIRIN UNIDIRIN CRS not allowed
UNIDIROUT BIDIR CRS not allowed
UNIDIROUT UNIDIROUT CRS not allowed
UNIDIROUT UNIDIRIN CRS not allowed
From⇒To
Table 30 CrsPwSeg allowed when FROM=TO
PWSegment DIR FROM = TO

UNIDIRIN CRS not allowed
UNIDIROUT CRS not allowed
BIDIR CCT=1WAY
8.13.4 Procedure
1
Select action.
To retrieve T-MPLS Pseudo Wire Segment Cross-Connection information, go to Step 2.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Pseudo Wire Segment Cross-Connection
To create T-MPLS Pseudo Wire Segment Cross-Connection, go to Step 5.

To modify T-MPLS Pseudo Wire Segment Cross-Connection parameters, go to Step 7.
To delete T-MPLS Pseudo Wire Segment Cross-Connection, go to Step 10.
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.
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Pseudo Wire Segment Cross-Connection 1850 TSS-320/TSS-320H/TSS-160
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}.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Traffic Descriptor
Delete T-MPLS Pseudo Wire Segment Cross-Connection

Please refer to 8.11 “Administer T-MPLS Pseudo Wire” (p. 510) procedure to delete the
Pseudo Wire cross connection
10
END OF STEPS
8.14 Administer T-MPLS Traffic Descriptor

8.14.1 Purpose
This procedure provides the instructions to retrieve information, create, and delete a TD (Traffic
Descriptor) also called MPLS Tunnel Resource Descriptor.
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.
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Traffic Descriptor 1850 TSS-320/TSS-320H/TSS-160
To delete T-MPLS Traffic Descriptor, go to Step 10.

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
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Traffic Descriptor
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
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.
Modify T-MPLS Traffic Descriptor parameters
Enter ED-TMPLS-TD::AID::::[CIR=][,CBS=][,PIR=][,PBS=];
MPLSTD-{1-10000}.
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Tunnel 1850 TSS-320/TSS-320H/TSS-160
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
Delete T-MPLS Traffic Descriptor
Does Traffic Descriptor in use?
10
Enter DLT-TMPLS-TD::AID:;
MPLSTD-{1-10000}.
11
END OF STEPS
8.15 Administer T-MPLS Tunnel

8.15.1 Purpose
This procedure provides the instructions to retrieve information, create, and delete an LSP tunnel
between source and destination point.
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))
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Tunnel
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.
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
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Tunnel 1850 TSS-320/TSS-320H/TSS-160
3
Examine output for provisioning information on tunnel, as detailed in the relevant command
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}.
for INNI connections

• SRC-ADDR = Source Node IP Address as originating point of the LSP Tunnel. It is the IP
address of the Ingress LER, used in TUNNEL AID output parameter. Possible values: {1-99,
101-126,128-223} - {0-255} - {0-255} - {1-254}.
• DEST-ADDR = Destination Node IP Address as target point of the LSP Tunnel. It is the IP
address of the Egress LER, used in TUNNEL AID output parameter. Possible values: {1-99,
101-126,128-223} - {0-255} - {0-255} - {1-254}.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Tunnel
6
Go to Step 1.
NOTICE
Optional Content
affect service.
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.
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.
Delete T-MPLS Tunnel
Does tunnel has active or protected?
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.
Release 5.1 (ETSI)

September 2017
Administer TMPLS Tunnels Group 1850 TSS-320/TSS-320H/TSS-160
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.
10
END OF STEPS
8.16 Administer TMPLS Tunnels Group

8.16.1 Purpose
The procedure explains how to create/configure/delete 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.
This procedure provides the instructions to setup the bicast&merge functionality (specifically
developed to allow the "Single Node Ring Closure" in the TSS-320 / TSS-40 IWI scenarios).
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer TMPLS Tunnels Group
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.
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".
Release 5.1 (ETSI)

September 2017
Administer TMPLS Tunnels Group 1850 TSS-320/TSS-320H/TSS-160
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
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
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Tunnel Segment
8.17 Administer T-MPLS Tunnel Segment

8.17.1 Purpose
This procedure provides the instructions to retrieve information, create, and delete a Tunnel
Segment to be used on 1850 TSS-320, TSS-320H and TSS-160 product.
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.
Table 31 PST usage rules depending on TUSegment current PST value
TUSEG PST TUSEG current PST

entered IS OOS-AU OOS-MA OOS-AUMA
IS Denied Denied IS OOS-AU
OOS OOS-MA OOS-AUMA Denied Denied

TUSegments.
The DLT-TMPLS-TUSEG command deletes the provisioned Swapped T-MPLS TUSegment entity.
(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.
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Tunnel Segment 1850 TSS-320/TSS-320H/TSS-160
To modify T-MPLS Tunnel Segment, go to Step 7.

To delete T-MPLS Tunnel Segment, go to Step 10.
To end this procedur Step 11.
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.
3
Examine output for provisioning information on Tunnel Wire Segment, as detailed in the
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=]
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Tunnel Segment
[,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.
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
affect service.
The System shall not permit to edit parameters of a TUSegment:

• involved in a cross-connection.
• referenced by a PWSegment (see PORT parameter in 8.12 “Administer T-MPLS Pseudo
Wire Segment” (p. 514) ).
Modify T-MPLS Tunnel Segment
Enter ED-TMPLS-TUSEG::AID:::[DIR],[USERNAME]:[L2ENCAPPROF-AID=][,
INLABEL=][,OUTLABEL=][,PHBPROF-AID=][,OAMPHB-AID=][,MEP=][,MEG-ID=][,
MEP-ID=][,EXPMEP-ID=][,CVRX=][,CVTX=][,CVPERIOD=][,CVPHB=][,ALMPROF=]
[,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: AID = Access IDentifier, specifies an access to the TUSegment facility. Possible values:
TUSEG-{1-7}-{1-9}-{1-20000}.
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Tunnel Segment 1850 TSS-320/TSS-320H/TSS-160
8
Go to Step 1.
WARNING
Optional Content
The System does't permit to delete a TUSegment involved in:

• a cross-connection (see 8.13 “Administer T-MPLS Pseudo Wire Segment Cross-Connection”
(p. 517) )
• referenced by a PWSegment (see PORT parameter in 8.12 “Administer T-MPLS Pseudo
Wire Segment” (p. 514) ).
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.
For Termination TUSegment, the command will be refused because on TUSegment there is still
the TUNNEL automatically generated (ref. to Step 5).
Delete T-MPLS Tunnel Segment
Does Tunnel Segment involved in a cross-connection or referenced to PWSegment?
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
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Tunnel Segment Cross-Connection
8.18 Administer T-MPLS Tunnel Segment Cross-Connection

8.18.1 Purpose
This procedure provides the instructions to retrieve information, create, and deletea cross-connect
entity and establishes a one-way, two-way cross-connection between the specified TUSegments.
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).
Table 32 CCT usage rules depending on TUSegment DIR parameter
FROM TUSegment DIR TO TUSegment DIR CCT value allowed

BIDIR BIDIR 2WAY
BIDIR BIDIR 1WAY
BIDIR UNIDIROUT 1WAY
BIDIR UNIDIRIN CRS not allowed
UNIDIRIN BIDIR 1WAY
UNIDIRIN UNIDIROUT 1WAY
UNIDIRIN UNIDIRIN CRS not allowed
UNIDIROUT BIDIR CRS not allowed
UNIDIROUT UNIDIROUT CRS not allowed
UNIDIROUT UNIDIRIN CRS not allowed
From⇒To
Table 33 CrsTuSeg allowed when FROM=TO
TUSegment DIR FROM = TO

UNIDIRIN CRS not allowed
Release 5.1 (ETSI)

September 2017
Administer T-MPLS Tunnel Segment Cross-Connection 1850 TSS-320/TSS-320H/TSS-160
Table 33 CrsTuSeg allowed when FROM=TO (continued)
TUSegment DIR FROM = TO

UNIDIROUT CRS not allowed
BIDIR CCT=1WAY
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.
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;
ALU-01 03-07-19 09:08:33 M TS002 COMPLD

TUSEG-1-1-10, TUSEG-1-1-20:1WAY
4
Go to Step 1.
5
Create T-MPLS Tunnel Segment Cross-Connection
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer 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}.
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.
Release 5.1 (ETSI)

September 2017
Proactive DM 1850 TSS-320/TSS-320H/TSS-160
WARNING
Optional Content
This command will be refused when:

• the Tunnel is active (see 8.15 “Administer T-MPLS Tunnel” (p. 524) ),
• the tunnel is protected.
After this command, all the corresponding TUSEG and CRSTUSEG are deleted.
Delete T-MPLS Tunnel Segment Cross-Connection
Please refer to 8.15 “Administer T-MPLS Tunnel” (p. 524) procedure to delete the Tunnel cross
connection.
10
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:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Proactive DM
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
(p. 504).

Terminated Tunnels can be created with Proactive DM enabled or can be created without DM
options enabled and then edited to enable the Proactive DM.
To create a terminated tunnel refer to 4.11 “ LER Tunnel Management (Tunnel Terminated)” (p. 81).
DM tool based counters:
At TUSEG creation default value for PM collection is DISABLED, i.e. DM tool based PM counters
are not available for that facility
In order to create the PM counters the SET-TMPLSPM-<tool> command should be entered:
PM collection is enabled and begins counting (PMSTATE = ON) if related tool (PRODM) is enabled.
When PRODM is disabled also collection is stopped and counter resources are released (PM not
retrievable)
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.
Release 5.1 (ETSI)

September 2017
3
(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.
Note: STATUS indicates the Tunnel administrative status.

• ON: The Tunnel is committed to carrying traffic.
• OFF: The Tunnel is not committed to carrying traffic.
Restrictions: If there is a PW referencing this TUNNEL, this parameter can't be OFF if
PW STATUS = ON If the Tunnel is part of a “Tunnel Group” created with ENT-TMPLS-
GROUP command, then this parameter can't be OFF.
If STATUS=ON and ACD=LOCAL and TD-ID parameter is not edited then the
command will be refused.
If STATUS=ON and ACD=LOCAL and OUTLABEL of correspondent TUSEG is not
entered then the command will be refused.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Proactive DM
• ,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
• CVPERIOD{0.1ms,0.5ms,1ms,3.33ms,10ms,20ms, 50ms,100ms,1s,10s,1m,10m}. Period
(1/Frequency) of CV packet transmission
• OAM-TYPE = OAM Packets type. Values are: T-MPLS MPLS_TP.
• PRODM = {ENABLE/DISABLE}. Enabling/disabling proactive delay measurement over
TUSEG.
Restrictions: ENABLE value can't be used if TYPE=SWAP.
If ENABLE MEP parameter must be ENABLE. ENABLE value can't be used if DIR≠BIDIR.
If the number of DM Tools enabled at Board-Level exceeds the allowed maximum number,
the command shall be denied.
• PRODM-PHB one of the PHB in the PHB-PROF for that entities; not possible to have more
than one on-demand or proactive DM for an entity with the same PHB;
• PRODM-PERIOD = {1s,10s,1m,10m}Period (1/Frequency) of DMM/DMR packet transmission
• PRODM-LENGTH = {0,41-1500}
The packet length of DMM frame transmitted. PRODM-PKT-LENGTH=0 means a random
length between 41 and 1500 byte.
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
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}.

7
To enable/freeze/disable the PM data collection for the facility
Release 5.1 (ETSI)

September 2017
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
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)
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Proactive LM (Synthetic Loss Measurement)
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
END OF STEPS
8.20 Proactive LM (Synthetic Loss Measurement)

8.20.1 Purpose
This procedure provides the instructions to configure, enable/disable the Proactive SLM tool at
TUSEG level on the 1850 TSS-320, TSS-320H and TSS-160 product.
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
Release 5.1 (ETSI)

September 2017
Proactive LM (Synthetic Loss Measurement) 1850 TSS-320/TSS-320H/TSS-160
A Proactive SLM tool can be created on bidirectional MEP only.
It is not possible to:

• disable a MEP if SLM tool has been enabled on it.
• to delete a Tunnel if Proactive SLM OAM tool has been created on MEP associated to the
TUSEG related to that Tunnel. It is necessary to disable the tool and then it is possible to delete
the Tunnel.
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
8.20.3 CCM / SLM periods

It is not possible to enable the only Continuity Check tool if CVPERIOD value is 0.1 ms or 0.5 ms or
1 ms, but SLM and CC tools must be enabled together (PROSLMCV = ENABLE).
In this cases the dLOC is detected anyway in 10 ms time interval, as for CVPERIOD = 3.33 ms.
It is not possible to enable the Synthetic LM if CVPERIOD value is 1s, 20 ms, 50 ms, 10 s, 1 min or
10 min.
(p. 504).

Terminated Tunnels can be created with Proactive LM (SLM) enabled or can be created without
SLM options enabled and then edited to enable the Proactive LM (SLM).
To create a terminated tunnel refer to 4.11 “ LER Tunnel Management (Tunnel Terminated)” (p. 81).
DM tool based counters:
At TUSEG creation default value for PM collection is DISABLED, i.e. SLM tool based PM counters
are not available for that facility
In order to create the PM counters the SET-TMPLSPM-<tool> command should be entered:
PM collection is enabled and begins counting (PMSTATE = ON) if related tool (PROLM) is enabled.
When PROlM is disabled also collection is stopped and counter resources are released (PM not
retrievable)
Release 5.1 (ETSI)

September 2017
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
(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-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.
Release 5.1 (ETSI)

September 2017
6
Enable/disable the SLM functionality
Enter:
RTRV-TMPLS-TUSEG::[AID]:::[USERNAME];
7
(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}.

Restrictions: If there is a PW referencing this TUNNEL, this parameter can't be OFF if
PW STATUS = ON If the Tunnel is part of a “Tunnel Group” created with ENT-TMPLS-
GROUP command, then this parameter can't be OFF.
If STATUS=ON and ACD=LOCAL and TD-ID parameter is not edited then the
command will be refused.
If STATUS=ON and ACD=LOCAL and OUTLABEL of correspondent TUSEG is not
entered then the command will be refused.
9
Configure the SLM on the terminated tunnel, enter:
ED-TMPLS-TUSEG::AID:::: [,MEP=][,MEG-ID= ][,MEP-ID=][,EXPMEP-ID=][,

CVPERIOD=][,PROSLMCVTX=][,PROSLMCVRX=][,PROLM-PLP =][,
PROLM-SD-CROSSTH=][,PROLM-SD-CLEARTH=] [,TCAPROF=][,RDI-SD=];
where:
• AID = TUSEG-{1-7}-{1-9}-{1-20000}. Access IDentifier, specifies an access to the
TUSegment facility.
• MEP = ENABLE, DISABLE.
Release 5.1 (ETSI)

September 2017
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
• 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.
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
Release 5.1 (ETSI)

September 2017
• in order to activate the SLM and associated CV functionality the recommended

sequence for avoiding spurious alarm is similar to the one used for CV functionality:
first enable PROSLMCVTX only in one of the two peer MEPs, then enable both
PROSLMCVTX and PROSLMCVRX in the other MEP, at the end enable also
PROSLMCVRX in the first mentioned MEP.
If the CV function was previous active, it is necessary first to disable it and then to
enable the SLMCV function
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}.

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.
Release 5.1 (ETSI)

September 2017
When PMSTATE changes from ON to DISABLED, counters are not retrievable because
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
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)
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.
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:
Release 5.1 (ETSI)

September 2017
Report Performance Monitoring (PM) Data for T-MPLS 1850 TSS-320/TSS-320H/TSS-160
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
END OF STEPS
8.21 Report Performance Monitoring (PM) Data for T-MPLS

8.21.1 Purpose
This procedure provides the instructions to report Performance Monitoring (PM) data and initialize
(reset) the collection register for the near-end side pertaining to the specified segment.
The System supports only the initial value 0 to be set in the cleared counters.
8.21.3 General
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.
2
Retrieve PM Data
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Report Performance Monitoring (PM) Data for T-MPLS
Enter RTRV-TMPLSPM-<SEG>::AID::::[MONTYPE=][,MONLEV=] [,TMPER=][,

MONDAT=][,MONTM=][,NUMMIN=][,NUMDAY=];
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)
3
Examine output for PM information, as detailed in the relevant command guide, refer to
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.
Release 5.1 (ETSI)

September 2017
Set Performance Monitoring (PM) Data for T-MPLS 1850 TSS-320/TSS-320H/TSS-160
5
Initialize PM Data Collection Register
Enter INIT-TMPLSPM-<SEG>::AID::::[MONTYPE=][,TMPER=];
where:
segment)
• AID = Access Identifier, identifies the entity access identifier. Possible value:
6
Go to Step 1.
7
END OF STEPS
8.22 Set Performance Monitoring (PM) Data for T-MPLS

8.22.1 Purpose
This procedure provides the instructions to enable/freeze/disable Performance Monitoring (PM)
data collection for the PseudoWire or Tunnel Segment facility.
None.
8.22.3 General
The SET-TMPLSPM-<SEG> command enables/freezes/disables the PM data collection for the
PseudoWire or Tunnel Segment facility.
Executing SET-TMPLSPM-<SEG> command with PMSTATE to:

• ON the PM data collection starts with all counters cleared (0 value).
• DISABLED the PM data collection is stopped and the User can't retrieve PM data because all
counters resource are released.
• OFF the PM data collection is stopped nevertheless the User can retrieve history PM data.
When <SEG> facility is deleted then data collection is automatically stopped and counters resource
are released.
In the following table are reported all the counters foreseen for <SEG> facility.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Set Performance Monitoring (PM) Data for T-MPLS
Table 34 T-MPLS PM counters foreseen for PWSEG and TUSEG
MPLS MonType DESCRIPTION DIRN

MINB MPLS Input Number of Bytes RCV
MONB MPLS Output Number of Bytes TRMT
MINP MPLS Input Number of Packets RCV
MONP MPLS Output Number of Packets TRMT
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.
Release 5.1 (ETSI)

September 2017
Set Performance Monitoring (PM) Data for T-MPLS 1850 TSS-320/TSS-320H/TSS-160
3
Enter SET-TMPLSPM-<SEG>::AID:::[PMSTATE]:[TMPER=];
where:
segment)
• AID = Access Identifier, identifies the entity access identifier. Possible value:
4
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 1662 Drop Shelf Detailed Level Procedure
9 1662 Drop Shelf Detailed Level Procedure
9.1 Overview
9.1.1 Purpose
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
9.1 Overview 555

9.2 1662SMC Drop Shelf Overview 555
9.3 1662SMC drop shelf management 559
9.4 Administer 1662 Subshelf E1 cards 561
9.5 1662 Subshelf Facilities Overview 564
9.6 1662 Subshelf Facilities Administration 565
9.7 Database backup and restore from remote file server on 1662 subshelf 569
9.8 1662 subshelf PM Administration (E1) 571
9.9 1662 subshelf PM Administration (STM4) 573
9.2 1662SMC Drop Shelf Overview

9.2.1 General
It is possible to manage 1662SMC shelf as drop shelf of TSS-320 R.4.0 in order to have integrated
PDH access available on TSS-320 in particular for UGW (Universal Gateway) access.
Providing the E1 physical access for UGW CES functionalities means a full inter-work between
1662SMC E1 and UGW E1.
In the 1850TSS-320 the E1 access has been integrated by managing a 1662SMC drop shelf (with
the physical interfaces) and collecting the VC-12 inside the main shelf using STM-4 connections.
Limitation: only single 1662SMC drop shelf is managed by 1850TSS-320.
9.2.2 Control Management

The 1662SMC shelf is connected to 1850TSS-320 shelf with an internal LAN in order to provide
management access from main shelf to drop shelf.
Release 5.1 (ETSI)

September 2017
1662SMC Drop Shelf Overview 1850 TSS-320/TSS-320H/TSS-160
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
Note: No DCC access is provided for 1662SMC drop shelf.

No specific IP address is provided for 1662SMC drop shelf.
9.2.3 1662SMC shelf equipping rules
1662SMC drop shelf is equipped with:

• common parts:
− 2xCONGI cards are foreseen (for providing dual power).
CONGI card with 2 LAN interfaces is used.
• 2xCompact ADM-4:
− Only Compact ADM-4 is supported.
− Each Compact ADM-4 is equipped with 2xSTM-4 Optical Drawer
• Up to 8 63xE1 ports (organized in two fixed 3:1 EPS groups)
• Up to 6 63xE1 access (75ohm or 120ohm)
• Up to 2 LSPROT access card (for EPS protection)
• FAN tray
Limitation: no plug&play available for cards equipped in the drop shelf.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 1662SMC Drop Shelf Overview
9.2.4 1850TSS equipping rules

The connection between 1850TSS-320 main shelf and 1662SMC drop shelf is provided with STM-4
lines.
Standard 8xSTM-1/4 card is equipped in the main shelf without a fixed position in order to carry E1/
VC-12 from 1662SMC access to TSS-320 central matrix.
The STM-4 access to the Main Shelf is also supported by a proper Port inside a 10XANY card or
inside a MultiRate <8xSTM-1/4 | 4xSTM-16> card.
Connection capability inside Drop shelf is fixed, and is activated on Equipment provisioning basis.
Limitation: 1662SMC is applicable only to ETSI region.
Release 5.1 (ETSI)

September 2017
1662SMC Drop Shelf Overview 1850 TSS-320/TSS-320H/TSS-160
9.2.5 Shelf creation

As a precondition, the REGION parameter should be equal to ETSI then the Drop Shelf should be
created by the ENT-EQPT command.
The following items cannot be Autoprovisioned

• Synth4(a+b)
• Congi(a+b)
• FanBox
• OpticalModule
So, the modules described above shall be automatically pre-provisioned at the Drop-Shelf creation
and shall be deleted only on the Drop-Shelf deletion
9.2.6 Network Management Interface

Overview of the provisioning sequence and of the TL1 commands impacted by 1662SMC drop shelf
management below the new AIDs:
New shelf:
• Drop Shelf AID: SHELF-1-2
• Drop Shelf ProvisionedType75ohm access: PDHACCSSHLF
• Drop Shelf ProvisionedType120ohm access: PDHACCSSHLF120
New cards in 1662SMC:

• Synth4 AID: MTSYNTH4-1-2-{6,15}
• Synth4 ProvisionedType: SYNTH4V2
• Congi AID: CONGI-1-2-{1,20}
• Congi ProvisionedType: CONGISL
• FAN box AID: FANDSHLF-1-2-21
• FAN box ProvisionedType: SRFANV2
• 63E1 port module AID: E1M-1-2-{7-14}
• 63E1 port module ProvisionedType: P63E1
• 63E1 acc module AID: E1ACC-1-2-{ 3-5,16-18 }
• 63E1 75ohm acc module ProvisionedType: A63E1A
• 63E1 120ohm acc module ProvisionedType: A63E1B
• 63E1 prot module AID: (+) E1PR-1-2-{2,19}
• 63E1 prot module ProvisionedType: LSPROT
• Optical Mod synth4 AID: OPTMOD-1-2-{6,15}-{1,2}
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 1662SMC drop shelf management
• Optical Mod synth4 ProvisionedType: OPTMODSS41
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 1662SMC drop shelf management

9.3.1 Purpose
This procedure provides instructions and sequence to de/provision and modify the 1662SMC drop
shelf.
9.3.2 General
The Drop shelf should be provisioned using the ENT-EQPT command.
The following meaningful parameters should be set on Drop Shelf creation:

• AID: SHELF-1-2
• PROVISIONEDTYPE: PDHACCSSHLF/PDHACCSSHLF120
• SHELFROLE: NOMAIN
• SHELFNUM is meaningless for PDHACCSSHLF(120).
The Drop Shelf is deprovisioned using the DLT-EQPT command.
The ED-EQPT command is allowed on Drop Shelf only for changing the Primary State and the
pointed ASAP Profile of an item.
RMV-EQPT and RST-EQPT commands can be used.
The RTRV-ALLOWED command addressed to a (provisioned) Drop Shelf will output a sequence of
rows, one for each PROVISIONEDTYPE value located in the immediate Lower level AID that is
Unprovisioned.
The RTRV-EQPT 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.
The RTRV-RI 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.
Release 5.1 (ETSI)

September 2017
1662SMC drop shelf management 1850 TSS-320/TSS-320H/TSS-160
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.

Provision 1850 TSS320 in AUTOEQ-AUTOFC mode with REGION=ETSI
The Drop shelf is not be provisioned automatically.
Cards autoprovisioned with the Drop shelf creation are:

• SYNTH4
• CONGI
• FAN
• OPTICAL Module.
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 .
Note: If TSS320 is provisioned as REGION=ANSI the provision command is denied.
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer 1662 Subshelf E1 cards
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
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
9.4 Administer 1662 Subshelf E1 cards

9.4.1 Purpose
Use this procedure to administer the following cards:
• 63 E1 Port Card
Release 5.1 (ETSI)

September 2017
Administer 1662 Subshelf E1 cards 1850 TSS-320/TSS-320H/TSS-160
• 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.
3
E1 port module E1M deletion
Note: The specified equipment entity must be in an OOS-[AU]MA state.

Enter:
DLT-EQPT::AID;
where:
• AID = E1M-{1-7}-{2}-{7-14} ETSI (63 E1 Multiplexer Card).
4
E1 protection module E1PR creation
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer 1662 Subshelf E1 cards
Enter:
[PST];
where:
• AID = E1PR-{1-7}-{2}-{2,19} ETSI (63 E1 EPS Card)
• PROVISIONEDTYPE = LSPROT - ETSI 63 x E1 Access Protection Module
5
E1 protection module E1PR deletion

Enter:
DLT-EQPT::AID;
where:
• AID = E1PR-{1-7}-{2}-{2,19} ETSI (63 E1 EPS Card)
6
E1 access module E1ACC creation
Enter:
[PST];
where:
• AID = E1ACC-{1-7}-{2}-{3-5,16-18} ETSI (63 E1 Access Card)
• PROVISIONEDTYPE = A63E1A/A63E1B: i.e. ETSI 63 x E1 Access Module 75ohm unb/
ETSI 63 x E1 Access Module 120ohm bal
7
E1 access module E1ACC deletion

Enter:
Release 5.1 (ETSI)

September 2017
1662 Subshelf Facilities Overview 1850 TSS-320/TSS-320H/TSS-160
DLT-EQPT::AID;
where:
• AID = E1ACC-{1-7}-{2}-{3-5,16-18} ETSI (63 E1 Access Card)
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).
On creation of a couple E1M-E1ACC, the following Facilities and Connections areautocreated:

• 63 E1s are autocreated. i.e.AIDs = E1-1-2-{8-10,11-13}-{1-63}.
• 63 x PDHLOVC12 are autocreated i.e PDHLOVC12-1-2-{8-10,11-13}-{1-63}
• A fixed Cross Connection between these 63xPDHLOVC12 and 63xMVC4TU12
I.e. 63 2WAY CRS MVC4TU12 to PDHLOVC12 are autocreated.
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
9.5 1662 Subshelf Facilities Overview

9.5.1 General
On the 1662 subshelf facilities, cross connection and FFP groups are AUTOCREATED during the
1662 provisioning.
The following facility types are auto created:

• 4 STM4 facilities on the SYNTH, (i.e STM4-{1-7}-2-{6,15}-{1-2})
• 2 STM4 FFP groups (i.e FFPSTM4-{1-7}-2-15-{1-2}).
• 8 STM4AU4 facilities (i.e. STM4AU4-{1-7}-2-6-{1-2}-{1-4}).
• 6 MVC4 facilities(i.e. MVC4-{1-7}-2-6-{1-6}).
• 63 MVC4TU12 are created on each of the 6 MVC4 facilties(i.e. MVC4TU12-{1-7}-2-6-{1-6}-{1-3}-
{1-7}-{1-3}).
• 2WAY crossconnection is created from each of the 6 MVC4 facilities to its corresponding
STM4AU4 facility, i.e. six 2-WAY crossconnections are created.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 1662 Subshelf Facilities Administration
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.
The following PTF rates are supported:

• VC4 PTF LOVC3:
• VC4: lower order (LO) VC3 PTF
• LOVC12: lower order (LO) VC12 PTF
9.6 1662 Subshelf Facilities Administration

9.6.1 Purpose
Use this procedure to administer the AUTOCREATED 1662 subshelf facilities.
Below the list of TL1 commands available for the 1662 subshelf facilities.
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
Release 5.1 (ETSI)

September 2017
1662 Subshelf Facilities Administration 1850 TSS-320/TSS-320H/TSS-160
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;
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 1662 Subshelf Facilities Administration
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.

• MVC4-{1-7}-{2}-{6}-{1-6} ETSI (MVC4 on an SYNTH4 on 1662 PDH Access shelf)
• PDHLOVC12-{1-7}-{2}-{8-10, 11-13}-{1-63} ETSI (VC12 with E1 client on the PDH Access
shelf E1 Port Module)
• MVC4-{1-7}-{1-9}-{7}-{1-16} - MVC4 on SCC card on 1646 Drop shelf
• PDHLOVC12-{1-7}-{2}-{8-10, 11-13}-{1-63} - VC12 with E1 client on the PDH Access shelf
E1 Port Module
• PDHLOVC12-{1-7}-{1-9}-{1-6}-{1-42} - VC12 with E1 client on the PDH Port Module of 1646
shelf
7
Enter:
RTRV-PTF::AID::::PTFTYPE=,PTFRATE=[,PARMS=][,TRCFMT=];
AID = PTF Access Identifier, specifies the PTF facility.

• MVC4-{1-7}-{2}-{6}-{1-6} ETSI (MVC4 on an SYNTH4 on 1662 PDH Access shelf)
• PDHLOVC12-{1-7}-{2}-{8-10, 11-13}-{1-63} ETSI (VC12 with E1 client on the PDH Access
shelf E1 Port Module)
Result: Ouput retrievable parameters are: AINSTIMER, MGRACD., PTFTYPE, PTFRATE,
CAPLIST.
8
Manage 1662 subshelf TU12 facilities
(i.e.:RTRV-TU12 , ED-TU12),
Enter:
ED-TU12::AID::::[AINSTH=][,ALMPROF=][,CMDMDE=]:[PST],[SST];
where:
Release 5.1 (ETSI)

September 2017
1662 Subshelf Facilities Administration 1850 TSS-320/TSS-320H/TSS-160
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).
MVC4TU12-{1-7}-{1-9}-{7}-{1-16}-{1-3}- {1-7}-{1-3} - TU12 within a MVC4 on SCC card on 1646
Drop shelf.
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
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Database backup and restore from remote file server on 1662 subshelf
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.

This procedure is done on the TSS320, when the TSS320 database backup and restore procedure
is done it includes also the 1662 Dropshelf database backup and restore.
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.
Release 5.1 (ETSI)

September 2017
Database backup and restore from remote file server on 1662 subshelf 1850 TSS-320/TSS-320H/TSS-160
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.
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 1662 subshelf PM Administration (E1)
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 1662 subshelf PM Administration (E1)

9.8.1 Purpose
Use this procedure to administer PM data collection for the E1 facility on the 1662 subshelf.
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.

Bidirectional PM will be considered as PM in receive directionality (DIRN = RCV)
The RTRV-PM-E1 command retrieves the current and/or historical 15-minute and/or 1-day PM data
corresponding to the PM data collection register(s) selected for the specified facility.
If AID=ALL is specified, all the (enabled) PM for the facility residing in the NE should be returned,
which matches the other input parameter criteria.
For each monitored parameter, the current and/or up to thirty-two (32) 15-minute historical PM
Release 5.1 (ETSI)

September 2017
1662 subshelf PM Administration (E1) 1850 TSS-320/TSS-320H/TSS-160

Provision Drop shelf and provision E1 card.
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
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:
LOCN = Location specifies the location where PM data collection is to be enabled or disabled.

• NEND Near End registers
• FEND Far End registers
• BIDIR Bidirectional registers
• ALL Near End, Far End and Bidirectionsl registers
MODETYPE = Mode Type, specifies the PM mode type 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:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 1662 subshelf PM Administration (STM4)
RTRV-PM-E1::AID:::[MONTYPE],[MONLEV],[LOCN],[DIRN],[TMPER],[MONDAT],
[MONTM],[NUM15MIN],[NUM1DAY];
where:
5
To enable both 15-min and 1-day PM.
Repeat Step 2 with the following settings:

• TMPER = 15-minute or 1-day (24 hour).
Note: PM collection register is to be enabled/disabled.

15-MIN 15 minutes registers, only valid for LOCN not equal BIDIR
1-DAY 24 hour registers BOTH 15 minutes and 24 hour registers
END OF STEPS
9.9 1662 subshelf PM Administration (STM4)

9.9.1 Purpose
Use this procedure to administer PM data collection for the STM4 facility on the 1662 subshelf.
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.

Bidirectional PM will be considered as PM in receive directionality (DIRN = RCV)
The RTRV-PM-STM4 command retrieves the current and/or historical 15-minute and/or 1-day PM
data corresponding to the PM data collection register(s) selected for the specified facility.
For each monitored parameter, the current and/or up to thirty-two (32) 15-minute historical PM
Release 5.1 (ETSI)

September 2017
1662 subshelf PM Administration (STM4) 1850 TSS-320/TSS-320H/TSS-160
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.

• NEND Near End registers
• FEND Far End registers
• BIDIR Bidirectional registers
• ALL Near End, Far End and Bidirectionsl registers
MODETYPE = Mode Type, specifies the PM mode type 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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 1662 subshelf PM Administration (STM4)
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.
Repeat Step 2 with the following settings:

• TMPER = 15-minute or 1-day (24 hour) or Both.
Note: PM collection register is to be enabled/disabled.

15-MIN 15 minutes registers, only valid for LOCN not equal BIDIR
1-DAY 24 hour registers.
BOTH 15 minutes and 24 hour registers
END OF STEPS
Release 5.1 (ETSI)

September 2017
1662 subshelf PM Administration (STM4) 1850 TSS-320/TSS-320H/TSS-160
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 CLI Procedures
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
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
10.14 LAG Management 602
10.15 VLAN protocol profile Management 605
10.16 VPLS Instance Management 608
10.2 Administer Autonegotation

10.2.1 Purpose
This procedure provides instructions and sequence to enable, disable and restart autonegotation on
the mau interface.
Release 5.1 (ETSI)

September 2017
Administer Autonegotation 1850 TSS-320/TSS-320H/TSS-160
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.
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
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
This command reports:

• Whether or not the autonegotation is enabled on the mau.
• The current status of the autonegotation process autonegotation capabilities supported by
mau.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Autonegotation
• autonegotation capabilities advertised by mau.

• The autonegotation capabilities advertised by the remote end: reported capabilities are
considered.
• meaningful only after the autonegotation has been completed.
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.
This command sets the autonegotation capability to be advertised, i.e.:

• the mau type (default value = default mau type)
• the PAUSE frame handling capability
Each possible value corresponds to a defined combination of capability bits from 8 to 11:
− 0000 for no pause
− 1100 for asymmectric pause[default value]
− 1111 for asymmetric and symmectric pause
6
END OF STEPS
Release 5.1 (ETSI)

September 2017
Administer Ethernet Flow Classifier 1850 TSS-320/TSS-320H/TSS-160
10.3 Administer Ethernet Flow Classifier

10.3.1 Purpose
This procedure is aimed to be used as a guideline for a set of instructions to configure, activate,
delete or modify an Ethernet Flow Classifier.
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
Classification of incoming customer traffic requires up to 4 basic input parameters:

• NE incoming, i.e. local/remote Ethernet interface or LAG Interface; and/or
• EtherType; and/or
• Outer VLANID (either single or range value) with optional additional classification parameters
consisting of:
− Inner VLANID (either single or range value); and/or
− Inner VLAN Priority bits (Inner VLAN PRI, either single or range value); and/or
• one of the two parameters below:
− Outer VLAN Priority bits (Outer VLAN PRI, either single or range value)
− IP-DSCP (either single or range value) values.
Output parameters from Ethernet Classifier:

• Unicast ETS Flow ID or
• Multicast ETS Flow ID.
For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1
Command Line Interface Guide.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Ethernet Flow Classifier
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:
FlowLabelKey classId InFlow UserLabel

Classifier Status
====================================================
@1.1.1 1 '2B1_REG_cvid100_svid10' active
(1)
@2.2.2 2 '2B4_BE_cvid200r_svid20' active
(1)
@3.3.3 3 '16B1_GUA_untag_svid30' active
(1)
4
Remove ETS InFlow classifier
Enter
Release 5.1 (ETSI)

September 2017
Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow 1850 TSS-320/TSS-320H/TSS-160
inflowclassifier remove classifierid

where:
classifierid is the classId number in the output shown in figure xx, i.e. an integer number,
indicating the specific ETS InFlow classifier
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 Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional

flow
10.4.1 Purpose
This procedure is aimed to be used as a guideline for a set of instructions to create, configure,
activate and delete an ETS to Provider Bridge ETS/PW/VPLS bidirectional flow.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow
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.
Release 5.1 (ETSI)

September 2017
Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow 1850 TSS-320/TSS-320H/TSS-160
• 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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer ETS-to-ETS bidirectional (port to port configuration)
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 Administer ETS-to-ETS bidirectional (port to port configuration)

10.5.1 Purpose
activate and delete an ETS to ETS bidirectional Transparent Mapping (port to port configuration).
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
flow show [flowuserlabel] [port {naming | lagnumber}][flowtype { pb | pw

| vpls | atm}]
to retrieve
• the specified flow or all configured flows (if no flow optional parameter is not specified) or for all
Release 5.1 (ETSI)

September 2017
Administer ETS-to-ETS bidirectional (port to port configuration) 1850 TSS-320/TSS-320H/TSS-160
flows with a specified service type (pb, pw, vpls,atm);

• of a certain port or all ports (if no flow optional parameter is not specified) the following
information;
− the flow user label;
− the flow index;
− the flow type (i.e. provider bridge bridirectional, provider bridge unidirectional ingressing,
provider bridge unidirectional egressing, port to port).
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer In Fiber In Band for Control Plan
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 Administer In Fiber In Band for Control Plan

10.6.1 Purpose
This procedure provides instructions and sequence to create In-Fiber/In-Band for Control plane.
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
“In Fiber In-Band” Management Interface is requested to support below features:

• Logical In Fiber In-Band Management Interface inherits same IfIndex of associated (Ethernet/
LAG or MPLS) interface on Data Plane, requiring no “on per port basis” specific configuration
over those “on per port basis” SNMP entries (e.g. ifEntry), shared between Data and
Management Planes;
• The administrative and operational status of “In fiber-In Band” management plane interface is at
all decoupled respect to corresponding underlying Interface at Data Plane: “In Fiber In-band”
Management Interface is allowed to be provisioned also over a underlying Interface supporting
no data traffic;
• PPP protocol, stacked over underlying either Ethernet/LAG or MPLS Interface (see above Figure
1), is allowed to be disabled (Default value: enabled) from Management Operator;
• L3 protocol for Management Interface Plane, irrespective of underlying either Ethernet or MPLS
Interface, is only IP: the packets received on “In Fiber In Band” Management Interface will be
extracted and forwarded (based on IP protocol) to upper layer IP protocol module;
Release 5.1 (ETSI)

September 2017
Administer In Fiber In Band for Control Plan 1850 TSS-320/TSS-320H/TSS-160
• 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}]
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Administer Traffic Descriptor
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 Administer Traffic Descriptor

10.7.1 Purpose
activate and delete a traffic descriptor.
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.
Release 5.1 (ETSI)

September 2017
Administer Traffic Descriptor 1850 TSS-320/TSS-320H/TSS-160
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:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Color Profile Management
trafficdescriptor config trafficdescriptoruserlabel cir cirvalue {pir

pirvalue | eir eirvalue} cbs cbsvalue {pbs pbsvalue | ebs ebsvalue}
[admittedmcrate admittedmcrate] [admittedunknrate admittedunknrate]
[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}].
Configures an ETS traffic descriptor without changing assigned Traffic Descriptor type.
Note: SNMP parameters are set according to MEF definition via the relations:
PIR=CIR+EIR, PBS= EBS.
END OF STEPS
10.8 Color Profile Management

10.8.1 Purpose
activate and delete a color profile.
10.8.3 General
ETS Policing is requested to support below different modes:

• Color-blind
• Color-aware
• Disabled.
Disabled ETS Policing assumes:

• incoming ETS Traffic, characterized from an already assigned “colored PHB”(Ethernet
Forwarding Class, DP) has been previously both “policed” and “pre-colored”;
• incoming ETS Traffic, characterized from an already assigned “colored PHB” (Ethernet
Forwarding Class, DP), has been associated to a NULL Traffic Descriptor.
“Color-Blind mode” ETS Policing (in the color-blind mode all the MEF and IETF policing algorithms
have the same behavior) assumes that incoming ETS Traffic to be uncolored;
“Color-Aware mode” ETS Policing can be implemented in three different modes:

• according to RFC2698
• according to MEF without the coupling flag
• according to MEF with the coupling flag.
Release 5.1 (ETSI)

September 2017
Color Profile Management 1850 TSS-320/TSS-320H/TSS-160
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.
ETS Flow Meter/Policer. for incoming Ethernet traffic

• relying on Dual Rate Token Bucket algorithm, verifies the compliance of ETS Flow with ETS
Traffic Descriptors
• ensures the use of network resources within the limits of agreed Traffic Descriptor and performs
those reactive actions over marked packets.
Each color profile considers either PRI or DSCP values, and associates to each of them a drop
precedence [green(g) and/or yellow(y) and/or red(r)].
The creation command has different options:

• allg (all values are associated to “green”)
• ally (all values are associated to “yellow”)
• allr (all values are associated to “red”);
• DSCP default (the default association scheme is used).
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Ethernet Physical management
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 Ethernet Physical management

10.9.1 Purpose
This procedure provides instructions manage the MAU interface type.
• 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.
General MAU information retrieved:

• mau and operational status
• jack type: jack connector type and jabber status: it can be {other | no jabber | jabbering}. It is
meaningful only for 10BaseT
• possible mau types and mau defaut type
• autoneg supplied
• optical channel type (B&W or Colored) and optical wavelength
• optical channel spacing
• ASAP pointer
Release 5.1 (ETSI)

September 2017
Ethernet Physical management 1850 TSS-320/TSS-320H/TSS-160
• interface alarm status

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:
END OF STEPS
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Ethernet Port management (over MAU)
10.10 Ethernet Port management (over MAU)

10.10.1 Purpose
This procedure provides instructions and sequence to manage a Ethernet local port.

• PP10GE
• PP1GE.
and also its unit should be provisioned.
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;
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:
This command retrieves the following Ethernet port information:

• the administrative/operative status
• the system time at which the port has entered the current operational state
Release 5.1 (ETSI)

September 2017
Ethernet Port management (over MAU) 1850 TSS-320/TSS-320H/TSS-160
• the interface type and the line rate

• the available bandwidth and the interface maximum MTU/MRU
• the interface mode
• the Ethernet local MAC address (if local Mac address is unavailable, it is set to
00:00:00:00:00:00)
• if the interface has a physical connector
• the handling of the incoming errored Ethernet frames
• the Ethernet port client layer
• the automatically assigned bridge port number
• the PAUSE frame handling capability to be applied when autonegotiation is disabled
• the admitted fractional rate
• the encapsulation method used by the local Ethernet entity (e.g. ethernetV2, llc-snap)
• the ASAP associated to the Ethernet port Scope
go to Step 1
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}
Note: The operation is rejected If ifAdminStatus is set to “up” value.
5
Configure Ethernet local port maximum MTU/MRU
Enter interface position namingsetlist localeth maxmtu mtuvalue
where:
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Ethernet Port management (over GFP)
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 Ethernet Port management (over GFP)

10.11.1 Purpose
This procedure provides instructions and sequence to manage a Ethernet remote port on GFP
port..

• PP10GE
• PP1GE.
and also its unit should be provisioned.
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;
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
Release 5.1 (ETSI)

September 2017
Ethernet Port management (over GFP) 1850 TSS-320/TSS-320H/TSS-160
Configure Ethernet remote port type, go to Step 4

Configure Ethernet remote port maximum MTU/MRU, go to Step 5
Configure some Ethernet remote port parameters using a single command, go to Step 6
2
Retrieve Ethernet remote port information
Enter interface position namingsetlist remoteeth show ethinfo
where:
This command retrieves the following Ethernet remote port information:

• the administrative/operative status
• the system time at which the port has entered the current operational state
• the interface type and the line rate
• the available bandwidth and the interface maximum MTU/MRU
• the interface mode
• the Ethernet local MAC address (if local Mac address is unavailable, it is set to
00:00:00:00:00:00)
• if the interface has a physical connector
• the handling of the incoming errored Ethernet frames
• the Ethernet port client layer and the automatically assigned bridge port number
Go to Step 1.
3
Activate/Deactivate Ethernet remote port
Enter interface position namingsetlist remoteeth {activate | deactivate}
where:
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 General Interface Management
Enterinterface position namingsetlist remoteeth portservice {ets |

bridge | mpls | iw}
5
Configure Ethernet remote port maximum MTU/MRU
Enter interface position namingsetlist remoteeth maxmtu mtu_value
where:
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 General Interface Management

10.12.1 Purpose
This procedure provides instructions and sequence to retrieve configured interfaces information.
None.
10.12.3 General
Below the list of the configured interfaces information retrievable:
• the administrative status
• the interface type
• 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).
Release 5.1 (ETSI)

September 2017
L2 control frames management (in Provider Bridge) 1850 TSS-320/TSS-320H/TSS-160
10.12.4 Procedure
To retrieve the following information:

• administrative status
• operational status
• the traffic rate to which transmission is limited
• the ingress port admitted flooding rate
Enter:
interface trafficshow [namingsetlist]
where:
parameters, the system will show all configured interfaces values.
To retrieve the following information:

• the administrative status
• the interface type
• ETS Service Type and ETS Service Status
Enter interface show [namingsetlist]
where:
END OF STEPS
10.13 L2 control frames management (in Provider Bridge)

10.13.1 Purpose
This procedure provides instructions and sequence to manage L2 control frames (passed or
discarded) received at a certain Ethernet port or a LAG Port configured as ETS port.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 L2 control frames management (in Provider Bridge)
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).
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:
Release 5.1 (ETSI)

September 2017
LAG Management 1850 TSS-320/TSS-320H/TSS-160
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 LAG Management

10.14.1 Purpose
This procedure is aimed to be used as a guideline for a set of instructions for Link Aggregation
management. .
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 LAG Management
Figure 36 Fig1. Link Aggregation concept
Traffic is shared among Aggregated Links belonging to an Aggregated system, by means of a

proprietary algorithm (“hashing” function). Basic principle of the algorithm is that a set of ordered
frames from two end-point users (end stations), also known as “Conversation” can transit on only
one link . Therefore, load balancing is not taken for grant , because of statistical distribution of traffic
over link aggregation interface. Furthermore, an Aggregated Link can carry out more that one
Conservation.
Inherent protection mechanism ensures that, in case of failure of one or more links , traffic is
redistributed over the remainders. Re-routing is performed by frame distribution algorithm.
It must be remarked that switched traffic has impact over all other conversations carried by
aggregated links, due to new computation of hashing function. Therefore, traffic is not hitless for all
the conversation set.
Default LAG size is 8.
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.
Release 5.1 (ETSI)

September 2017
LAG Management 1850 TSS-320/TSS-320H/TSS-160
To show all Link Aggregation groups go to Step 7.
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.
This command changes:

• either enabled/disabled LACP in case of not active Link Aggregation Group;
• either enabled/disabled Link Aggregation Group administrative status;
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 VLAN protocol profile Management
• or some parameters for a active Link Aggregation Group.
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 VLAN protocol profile Management

10.15.1 Purpose
This procedure is aimed to be used as a guideline for a set of instructions to create/modify/delete a
vlan protocol profile and to associate it to an ETS port.
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,
Release 5.1 (ETSI)

September 2017
VLAN protocol profile Management 1850 TSS-320/TSS-320H/TSS-160
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.
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 VLAN protocol profile Management
where
vlanprotprofuserlabel is a mnemonic string that addresses the VLAN.
4
Retrieve VLAN protocol profile
Commands below are used to get

• a VLAN protocol profile
Enter vlanprotprofile show [vlanprotprofuserlabel]
where:
vlanprotprofuserlabel is a mnemonic string that addresses the VLAN.
The information can be scoped to one VLAN profile by indicating its user label.
• a VLAN protocol profile associated to an ETS port
To get the VLAN protocol profile associated to a certain Ethernet port defined as ETS port
enter:
interface position namingsetlistlagnumberset show vlanprotprofile
or enter
interface position namingsetlistlagnumberset vlanprotprofile show
[vlanprotprofuserlabel]
• VLANs registered on a port.
To get the VLANs registered on each indicated port enter:
interface position namingsetlistlagnumberset show vlanset
It also gets the VLAN for which each indicated port is in the “VLAN port member set”.
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
Release 5.1 (ETSI)

September 2017
VPLS Instance Management 1850 TSS-320/TSS-320H/TSS-160
interface position namingsetlistlagnumberset vlanprotprofile default
END OF STEPS
10.16 VPLS Instance Management

10.16.1 Purpose
This procedure provides the instructions to retrieve information, create, and delete a VPLS Instance
to be used on 1850 TSS-320, TSS-320H and TSS-160 product.
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).
A VPLS Service allows:

• remote LAN segments to behave as one single LAN via “end to end” connectivity (irrespective
from higher layer protocols) between 2 remote Ethernet stations;
• Ethernet services to exploit “carrier class” MPLS capabilities, relying on both MPLS “connection
oriented” behavior and MPLS QoS capabilities.
Convention name used:
vplsuserlabel: octet string (to be encoded into 8 bytes) as unique VPLS Instance identifier
(example: “100:10” )
namingsetlistlagnumberset: an expression using namingsetlist and lagnumberset, separated by
commas: (e.g. r1sr1sl3-6&18d1p1-3,r1sr1sl7-9&19d1p4-6,lag4-7&18,r1sr1sl7-17d1p10)
pwset: an expression using PW Set ((e.g. 5&7&16)
Generic rules
The parameters between square brackets are optional. If a value is not entered for those
parameters, the system will use the default value.
10.16.4 Procedures
1
Select action.
To retrieve VPLS instance information, go to Step 5.
To create VPLS instance, go to Step 2.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 VPLS Instance Management
To modify VPLS instance, go to Step 4, Step 5, Step 6.

To delete VPLS instance, go to Step 3.
To add both UNI and (or) Core/Spoke MPLS PW’s to a VPLS, go to Step 6
Remove both UNI and (or) Core/Spoke MPLS PW’s to a VPLS Instance, go to Step 7
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
This command configures below attributes for a VPLS Instance:

• enabled/disabled MAC learning;
• behaviour in front of unknown frames.
Enter: vpls config vplsuserlabel [learning {enable | disable}]
[unkdiscarding {enable | disable}]
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]
Release 5.1 (ETSI)

September 2017
VPLS Instance Management 1850 TSS-320/TSS-320H/TSS-160
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
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Software Reference Guide
A Software Reference Guide
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.
A.2 Access Identifiers

A.2.1 General Facility AID Format:
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.
The SDH facilities are of the form:

• facility-bay#-shelf#-slot#-facility#-(AU4#)-(AU3#)
− where: facility = facility 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.
− where: facility# = facility (port) number within the slot.
− where: AU4# = the AU4 number within the signal of the STM facility.
Release 5.1 (ETSI)

September 2017
Access Identifiers 1850 TSS-320/TSS-320H/TSS-160
− where: AU3# = the AU3 number within the AU4.
LOA facilities for SDH are of the form:

• facility--bay#-shelf#-slot#-vc4#-tu3#-tu2#-tu12#
− where: facility = facility name
− where: slot# = the number of the slot or position or entity number within the shelf in which the
LOA facility is present.
− where: VC4# = VC4 number
− where: tu3# = tu3 number in this VC4.
− where: tu2# = tu2 number in the tu3.
− where: tu12# = tu12 number in the tu2.
The facility protection groups are of the form:

• facility-bay#-shelf#-slot#-port#
− where: port# = facility (port as representative of the protection group) number within the slot.
VCG carrying SDH stream on L2 Aggregator cards with PIMMS are of the form:
• facility-bay#-shelf#-slot#-PIM#-(VCG#)-(VC4#)-(TU3#)-(TU12#)
− 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 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.
Gigabit Ethernet facilities on 10xANY or Packet cards are of the form:

• GBE-bay#-shelf#-slot#-GBE#
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Access Identifiers
− 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).
A.2.2 General Timing Reference AID Format:
The syntax for NE External Input Timing Port access identifiers in TL1 commands, responses, or
messages is:
• BITS-bay#-shelf#-port#
− 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: 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: 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: 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#
Release 5.1 (ETSI)

September 2017
− where: ref# = 0, because there is only one timing node supported in the system, which will be
represented by this AID.
A.2.3 General Equipment AID Format:
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: 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.
A.2.4 General Profile AID Format:
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.
Release 5.1 (ETSI)

September 2017
A.2.5 Facility AIDs

The following requirements refer to STM ports and their entities.
The AID for an STM1 facility is:

• STM1-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} (STM1)
The AID for an AU4 embedded in a STM1 signal is:

• STM1AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-1 (AU4 embedded within an STM1)

• STM4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} (STM4)

• STM4AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-{1-4} (AU4 embedded within an
STM4)
The AID for an AU4-4C embedded in a STM4 signal is:

• STM4AU44C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-1 (AU4-4c embedded within an
STM4)

• STM16-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4, 5, 7} (STM16 on a 2G5SO or
10xANY)

• STM16AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1-16} (AU4 in an STM16
on a 2G5SO or a 10xANY)

• STM16AU44C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1,5,9,13} (AU4-4c in
an STM16 on a 2G5SO or 10xANY)

• STM16AU416C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-1 (AU4-16c in an STM16
on a 2G5PSO or 10xANY)

• STM64-{1-7}-{1-9}-{2-9,12-19,21-36}-1 (STM64)

• STM64AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-1-{1-64} (AU4 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,
Release 5.1 (ETSI)

September 2017
41,45,49,53,57,61} (AU4-4c embedded within an STM64)

• STM64AU416C-{1-7}-{1-9}-{2-9,12-19,21-36}-1-{1,17,33,49} (AU4-16c
embedded within an STM64)

• STM64AU464C-{1-7}-{1-9}-{2-9,12-19,21-36}-1-1 (AU4-64c embedded within an
STM64)
The following requirements refer to Virtual Concatenation Group and their embedded entities
The AID of the VCG on a Multiservice Collector Card is:

• VCG-{1-7}-{1-9}-{2-9,12-19}-{1-124} (Logical VCG for ethernet switching on a
PP10AD module
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 of a Fast Ethernet Facility is:

• MAU-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1-10} (MAU port on a 10xAny module)
The AID for a GBE port on a 10xAny module is:

• GBE-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} (GBE port on a 10xAny module)
Release 5.1 (ETSI)

September 2017
The following requirements refer to WDM facilities
The AID for an OT Line Port is:

• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 (OTU2 Line port, OT2TDM
module)
The AID of an ODU2 facility in an OTU2 is

• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{C1, L1}-1 (ODU2 facility in an
OTU2)
• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{L1}-1 (ODU2 facility in an
OTU2 on OT2TDM module)
The following requirements refer to CWDM facilities
The AID for an Line port on a CWLA module (OGPORT) is:

• OGPORT-{1-7}-{1-9}-{6-9,12-15}-{1-4} (Line port on a CWLA module - STM16)
The AID for an Client port on a CWLA module (OGPORT) is:

• OGPORT-{1-7}-{1-9}-{6-9,12-15}-{1-4} (Client port on a CWLA module - STM16)
The following requirements refer to the LOA functionality.
The AID for a Modifiable VC4 at LOA is:

• MVC4-{1-7}-{1-9}-{21,22,35,36}-{1-64} (Modifiable VC4 on LOA card)
The AID for a TU12 facility at LOA is:

• MVC4TU12-{1-7}-{1-9}-{21,22,35,36}-{1-64}-{1-3}-{1-7}-{1-3} (TU12
embedded within a Modifiable VC4)
The AID for a TU3 facility at LOA is:

• MVC4TU3-{1-7}-{1-9}-{21,22,35,36}-{1-64}-{1-3} (TU3 embedded within a
Modifiable VC4)
The AID for a lower order pool at LOA is:

• LOPOOL-{1-7}-{1-9}-1 (Lower order pool for all LOA cards within a shelf)
Release 5.1 (ETSI)

September 2017
A.2.6 Fast Facility Protection Group AIDs
The AID for the STM1 FFP is:

• FFPSTM1-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} (STM1 Facility Protection Group)

• FFPSTM4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} (STM4 Facility Protection Group)

• FFPSTM16-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4} (STM16 Facility Protection Group
on a 2G5SO or 10xANY)

• FFPSTM64-{1-7}-{1-9}-{2-9,12-19,21-36}-1 (STM64 Facility Protection Group)
The AID for the TMPLS FFP is:

• FFPTUNNEL-{1-7}-{1-9}{1-4000} (TMPLS TUNNEL Protection Group)
A.2.7 Timing Reference AIDs
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:
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 AID for the Timing Node within a Shelf is:

• SYNC-{1-7}-{1-9}-0 (Timing Node within a Shelf)
Release 5.1 (ETSI)

September 2017
A.2.8 Packet and TDM Equipment AIDs
The AID for the Shelf is:

• SHELF-{1-7}-{1-9} (Shelf)
The AID for the Equipment Controller is:

• EC320-{1-7}-{1-9}-{1,20} (Equipment Controller Card TSS-320)
• EC320-{1-7}-{1-9}-{20} (Equipment Controller Card -Secondary-Protecting TSS-320)
The AID for the Matrix and Timing Module is:

• MT320-{1-7}-{1-9}-{10,11} (Matrix and Timing TSS-320)
• MT320-{1-7}-{1-9}-{10} (Matrix and Timing - Primary Working TSS-320)
• MT160-{1-7}-{1-9}-{10,11} (Matrix and Timing TSS-160)
The AID for the Power Supply Unit is:

• PSF320-{1-7}-{1-9}-{37,39} (Power Supply Filter TSS-320)
The AID for the FAN unit is:

• FAN320-{1-7}-{1-9}-{40,41} (FAN equipment)
The AID for the 10GSO (STM-64/OC-192) card is:

• 10GSO-{1-7}-{1-9}-{2-9,12-19,21-36} (10G Synchronous Optical)
The AID for the 2.5G (STM-16/OC-48) module is:

• 2G5SO-{1-7}-{1-9}-{2-9,12-19,21-36} (2.5G Synchronous Optical)
The AID for the 8 Port STM-1/STM-4/OC-3/OC-12 Card is:

• 8XSO-{1-7}-{1-9}-{2-9,12-19,21-36} (8 x Synchronous Optical)
Release 5.1 (ETSI)

September 2017
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 the XFP on 10GSO modules is:

• XFP-{1-7}-{1-9}-{2-9,12-19,21-36}-1 (XFP on 10GSO modules)
The AID for the SFP on 8XSO modules is:

• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} (SFP on 8XSO modules)
The AID for the TBUS is:

• TBUS-{1-7}-{1-9}-{42,43} (ISPB Termination Bus)
The AID for the 10XANY card is:

• 10XANY-{1-7}-{1-9}-{2-9,12-19,21-36} (10XANY Card)
The AID for the OTU2 card is:

• OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} (G.709 OTU 10GB Card - Provisioned Type =
1POTU2)
The AID for the SFP on the 10XANY modules is:

• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} (SFP on 10XANY modules)
The AID for a Lower Order Adaptation Card (10G) is:

• LOA10G-{1-7}-{1-9}-{21,22,24,33,35,36} (Lower Order Adaptation Card with EPS)
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:
The AID for a Optical Pre-Amplifier 10G is:

• PRE-{1-7}-{1-9}-{2-9,12-19,21-36} (Preamplifier)
The AID for a Optical Booster 10G is:

• BOOST-{1-7}-{1-9}-{2-9,12-19,21-36} (Booster)
The AID for a Line Optical Filter and Attenuator is:

• LOFA-{1-7}-{1-9}-{6-9,12-15} (Line Optical Filter and Attenuator)
The AID for DWDM Optical Transponder with Colored XFPs is:
• DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} (DWDM Optical Transponder)
Release 5.1 (ETSI)

September 2017
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 SFP on PP10 module is:

• SFP-{1-7}-{1-9}-{2-9,12-19}-{1-10} (SFP on PP10 modules)
The AID for a XFP on PP10GE modules is:

• XFP-{1-7}-{1-9}-{2-9,12-19}-1 (XFP on PP10GE modules)
The AID for a XFP modules on DWLA10X is:

• XFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-2} (XFP on DWLA10X Transponder)
Release 5.1 (ETSI)

September 2017
A.2.9 TMPLS AIDs
The AID for a Local MPLS Interface is:

• MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-10} (Local MPLS Interface)
The AID for a VCG MPLS Interface is:

• MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-128} (VCG MPLS Interface)
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 Tunnel Segment is:

• TUSEG-{1-7}-{1-9}-{1-20000} (Tunnel Segment)
The AID for a Pseudowire Segment is:

• PWSEG-{1-7}-{1-9}-{1-128000} (Pseudowire Segment)
The AID for a Tunnel is:

• 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} (Tunnel)
The AID for a Pseudowire is:

• PW-{1-7}-{1-9}-{1-64000} (Pseudowire)
The AID for a MPLS Traffic Descriptor is:

• MPLSTD-{1-10000} (MPLS Traffic Descriptor)
The AID for a PHB Profile is:

• PHBPROF-{1-16} (PHB Profile)
The AID for a User defined PHB Profile is:

• PHBPROF-{3-16} (User defined PHB Profile)
The AID for an OAM Experimental Bit Profile is:

• OAMPHB-{1-8} (OAM PHB Profile)
The AID for a User defined OAM Experimental Bit Profile is:
• OAMPHB-{2-8} (User defined OAM PHB Profile)
Release 5.1 (ETSI)

September 2017
A.2.10 Control Plane AIDs

The following requirements refer to TDM Control Plane:
The AID for a Bundle Link for TMPLS is:

• TBNDL-{10-109} (Bundle Link for TMPLS)
The AID for a Neighbor router ID is:

• {1-126, 128-223}-{0-255}-{0-255}-{1-254} (OSPF neighbor router ID)
The AID for a Unknown neighbor router ID is:

• UNKNOWN (Unknown neighbor router ID)
The AID for a Routing Area ID is:

• {0-255}-{0-255}-{0-255}-{0-255} (Routing Area ID)
The AID for a Port AID if index is:

• {1-2147483646} (Port AID if index)
A.2.11 Common AIDs
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)
Release 5.1 (ETSI)

September 2017
• MDL-{1-7}-{1-9}-{1-39}-{1-10} (Generic PIM/SFP 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 AID of the default OSI Area is:

• OSIAREA-1 (Default OSI Area)
The AID of the Internet Protocol Tunnel is:

• IPT-{1-128} (Internet Protocol Tunnel)
The AID of the Management LAN entity is:

• LAN-1 (Customer LAN)
The generic AID used to address all entities in a particular command is:
• ALL (ALL AID)
A.2.12 Database AIDs
The AIDs for database backups is:

• ACTDSKDB (The system's primary backup database)
• STBYDB (The system's secondary backup database)
• RFSDB (A database backup on a Remote File Server)
A.2.13 Software AIDs
The AIDs for software loads (generics) is:

• STBYSW (The standby software generic on the NE)
• RFSSW (A software generic on a remote file server)
A.2.14 ASAP AIDs
The AIDs for the Alarm Severity Assigned Profiles is:

• ASAPEQPT-{0-1} (NULL and Factory DEFAULT EQPT ASAP)
• ASAPEQPT-{2-255} (User defined EQPT ASAP, where n is a theoretic limit)
• ASAPBITS-{0-1} (NULL and Factory DEFAULT BITS ASAP)
• ASAPBITS-{2-255} (User defined BITS ASAP, where n is a theoretic limit)
Release 5.1 (ETSI)

September 2017
• ASAPTIMING-{0-1} (NULL and Factory DEFAULT Timing ASAP)

• ASAPTIMING-{2-255} (User defined Timing ASAP, where n is a theoretic limit)
• ASAPGBE-{0-1} (NULL and Factory DEFAULT GBE ASAP)
• ASAPGBE-{2-255} (User defined GBE ASAP, where n is a theoretic limit)
• ASAPMAU-{0-1} (NULL and Factory DEFAULT MAU ASAP)
• ASAPMAU-{2-255} (User defined MAU ASAP, where n is a theoretic limit)
• ASAP10GBE-{0-1} (NULL and Factory DEFAULT 10GBE ASAP)
• ASAP10GBE-{2-255} (User defined 10GBE ASAP, where n is a theoretic limit)
• ASAPVCG-{0-1} (NULL and Factory DEFAULT VCG ASAP)
• ASAPVCG-{2-255} (User defined VCG ASAP, where n is a theoretic limit)
• ASAPODU2-{0-1} (NULL and Factory DEFAULT ODU2 ASAP)
• ASAPODU2-{2-255} (User defined ODU2 ASAP, where n is a theoretic limit)
• ASAPOTU2-{0-1} (NULL and Factory DEFAULT OTU2 ASAP)
• ASAPOTU2-{2-255} (User defined OTU2 ASAP, where n is a theoretic limit)
• ASAPOGPORT-{0-1} (NULL and Factory DEFAULT OG PORT ASAP)
• ASAPOGPORT-{2-255} (User defined OG PORT ASAP, where n is a theoretic limit)
• ASAPSECU-{0-1} (NULL and Factory DEFAULT SECU ASAP)
• ASAPSTM1-{0-1} (NULL and Factory DEFAULT STM1 ASAP)
• ASAPSTM1-{2-255} (User defined STM1 ASAP, where n is a theoretic limit)
• ASAPVC4-{0-1} (NULL and Factory DEFAULT VC4 ASAP)
• ASAPVC4-{2-255} (User defined VC4 ASAP, where n is a theoretic limit)
• ASAPVC44C-{0-1} (NULL and Factory DEFAULT VC44C ASAP)
• ASAPVC44C-{2-255} (User defined VC44C ASAP, where n is a theoretic limit)
• ASAPLOVC3-{0-1} (NULL and Factory DEFAULT LOVC3 ASAP)
• ASAPLOVC3-{2-255} (User defined LOVC3 ASAP, where n is a theoretic limit)
• ASAPLOVC12-{0-1} (NULL and Factory DEFAULT LOVC12 ASAP)
• ASAPLOVC12-{2-255} (User defined LOVC12 ASAP, where n is a theoretic limit)
Release 5.1 (ETSI)

September 2017
A.2.15 THP AIDs
The AIDs for the Threshold Profiles is:

• THP10GBE-{0-1} (NULL and Factory DEFAULT 10GBE THP)
• THP10GBE-{2-127} (User defined 10GBE THP, where n is a theoretic limit)
• THPODU2-{0-1} (NULL and Factory DEFAULT ODU2 THP)
• THPODU2-{2-127} (User defined ODU2 THP, where n is a theoretic limit)
• THPOTU2-{0-1} (NULL and Factory DEFAULT OTU2 THP)
• THPOTU2-{2-127} (User defined OTU2 THP, where n is a theoretic limit)
• THPGBE-{0-1} (NULL and Factory DEFAULT GBE THP)
• THPGBE-{2-127} (User defined GBE THP, where n is a theoretic limit)
• THPMAU-{0-1} (NULL and Factory DEFAULT MAU THP)
• THPMAU-{2-127} (User defined MAU THP, where n is a theoretic limit)
• THPVCG-{0-1} (NULL and Factory DEFAULT VCG THP)
• THPVCG-{2-127} (User defined VCG THP, where n is a theoretic limit)
• THPSTM1-{0-1} (NULL and Factory DEFAULT STM1 THP)
• THPSTM1-{2-127} (User defined STM1 THP, where n is a theoretic limit)
• THPVC4-{0-1} (NULL and Factory DEFAULT VC4 THP)
• THPVC4-{2-127} (User defined VC4 THP, where n is a theoretic limit)
• THPVC44C-{0-1} (NULL and Factory DEFAULT VC44C THP)
• THPVC44C-{2-127} (User defined VC44C THP, where n is a theoretic limit)
• THPLOVC3-{0-1} (NULL and Factory DEFAULT LOVC3 THP)
• THPLOVC3-{2-127} (User defined LOVC3 THP, where n is a theoretic limit)
• THPLOVC12-{0-1} (NULL and Factory DEFAULT LOVC12 THP)
• THPLOVC12-{2-127} (User defined LOVC12 THP, where n is a theoretic limit)
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 States
A.2.16 Housekeeping AIDs
The AIDs for Input housekeeping is:

• CPI-{1-7}-{1-9}-1-{1-8} (External Input Point)
The AIDs for Output housekeeping is:

• CPO-{1-7}-{1-9}-1-{1-4} (External Control Point)
A.2.17 PM Global File Collection AIDs
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.
A.3.2 State Names

The system uses entity states to indicate the availability of an entity in providing its functions. (The
term entity represents the resource or service generally identified by the Access Identifier [AID]
parameter.) If an entity is not available, the entity states indicate the cause of the unavailability and
what action can be taken to make the entity available. An entity's state is described by two
parameters, the PST (primary state) and the SST (secondary state).
A.3.3 Primary State Values

The PST indicates the current overall service condition of an entity.
Refer to Table 35, “Primary Equipment Values” (p. 627) for the PST values used in the system.
Table 35 Primary Equipment Values
STATE NAME DEFINITION

IS, IS-NR In_Service, Normal: the entity is capable and allowed to provide its
provisioned functions. (IS and IS-NR may be used interchangeably in this
document.)
IS-ANR In_Service_Abnormal: the entity is capable of most functions, is allowed to
provide its provisioned functions, but is operating in a degraded or abnormal
state (e.g., non-alarmed BER Signal Degrade threshold crossing on an STS)
Release 5.1 (ETSI)

September 2017
States 1850 TSS-320/TSS-320H/TSS-160
Table 35 Primary Equipment Values (continued)

OOS-AU Out_Of_Service-Autonomous: the entity is not available for providing its
provisioned functions but the entity is not intentionally suspended by external
management command (from an OS or craft interface) from performing
these functions. In general, the cause of the incapability is due to an
unsolicited autonomous event detected in the system or in the associated
network (e.g., LOS detected).
OOS-AUMA Out_Of_Service-Autonomous_and_Management: the entity is not available
for providing its provisioned functions because an OOS-AU state transition
has occurred and the entity is intentionally suspended by external
management command (from an OS or craft interface) from performing its
provisioned functions
OOS-MA Out_Of_Service-Management: the entity is intentionally suspended by
external management command (from an OS or craft interface) from
performing its provisioned functions, but the entity may still be operationally
capable of performing its provisioned functions.
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.3.4 Secondary State Values

The SST provides additional information pertaining to the PST.
Multiple SST values may apply to an entity at a particular instant. If more than one SST value
applies to an entity, the SST values are grouped with an ampersand (&) in the output response
message (for example, FAF&SGEO).
Refer to Table 36, “Secondary Equipment Values (TL1 3.0)” (p. 628) for SST values used in the
system.
Table 36 Secondary Equipment Values (TL1 3.0)

FLT Fault - The entity is OOS due to at least one hardware fault.
MEA Mismatch of Equipment and Attributes - The entity is installed with incorrect
equipment or card, or the correct equipment is installed, but it has improper
attributes assigned.
SDEE Supported Entity Exists - The entity is currently supporting other entities.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Codes
Table 36 Secondary Equipment Values (TL1 3.0) (continued)

SGEO Supporting Entity Outage - The associated supporting entity has failed or is
out of service due to management action.
SWDL Software Download - Software entity is currently being loaded with the
necessary software or database data and code.
UAS Unassigned - The entity has not been assigned with necessary provisioning
data.
UEQ Unequipped - The equipment entity is not equipped with necessary
hardware, or software entity is not loaded with necessary data or code.
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
CONDI- DESCRIPRTION EQUIPMENT

TION TYPE
ABNOR- Indicates that a module has been inserted in a position where MDL
MAL it cannot be provisioned, or the module has been deleted but
is still physically present
AIRTEMP The cooling air temperature has exceeded the first (lower) FAN320
threshold, associated with air temperature sensor at the FANs
intake.
BPERROR Backplane Error indicates that a failure has been detected on Shelf
a shelf backplane.
CONTBUS Indicates that the shelf controller is unreachable MT320/160
CONTCOM Indicates that a communication failure has been detected Shelf
between the active and passive FLC cards.
DBF Database Backup Failure, creation of local backup database Shelf
failed.
DBRESET DB reset after FLC restart and FLC-SLC communication is Shelf
inhibited.
Release 5.1 (ETSI)

September 2017
Codes 1850 TSS-320/TSS-320H/TSS-160
Table 37 1850 TSS-320, TSS-320H and TSS-160 Equipment Condition Types (continued)

TION TYPE
FA Fuse alarm and service is affected (i.e. power interruption). It FAN320,
is reported, for POW320, if a Fuse Broken information is POW320,
received from both the POW320 PSF320
FRCD- Forced switch of working module to protection using LOA10G
WKSW SWTOPROTN-EQPT with MODE parameter set to FRCD.
HWFAIL Hardware error is detected associated with a module. 10GSO,2G5SO,
Protection is not available and/or service is affected. 8XSO, EC320,
FAN320,
MT320/160,
OT2TDM.
10XANY, SFP,
XFP, LOA10G,
CWLA, CADM,
CMDX,
Hardware error is detected associated with a module. Service PP10AD,
is not affected PP1GE,
PP10GE,
OMDX8100,
DWLA10X,
PRE10G,
BOOST10G,
LOFA1111
Failure on HW and service could be affected: it is reported as
MJ if an HW Failure information is received from both the
POW320 POW320,
Failure on HW and service is not affected: it is reported as PSF320
MN if an HW Failure information is received from one only
POW320
Release 5.1 (ETSI)

September 2017

TION TYPE
IMPRO- Indicates that physical removal was performed on an 10GSO,2G5SO,
PRMVL equipment module without first logically removing it where 8XSO, EC320,
protection is not available. FAN320,
MT320/160,
OT2TDM.
10XANY, SFP,
XFP, LOA10G,
CWLA, CADM,
CMDX,
Indicates that physical removal was performed on an PP10AD,
equipment module without first logically removing it where PP1GE,
protection is available. PP10GE,
OMDX8100,
DWLA10X,
PRE10G,
BOOST10G,
LOFA1111
INHSWDX Duplex (redundant) one-to-one module is inhibited from copy EC320
switching (disable a switch using INHSWDXEQPT command)
INHSWPR Protection module is inhibited from providing protection LOA10G
(lockout of protection operation using INHSWTOPROTN-
EQPT command).
Working module is inhibited from switching to protection
(lockout a working operation using INHSWTOPROTNEQPT
command).
INIT Initialization, indicates that system initialization is currently in Shelf
progress.
Release 5.1 (ETSI)

September 2017

TION TYPE
MAN Logical removal was performed on an equipment module and EC320, FAN320.
protection is not available MT320/160,
POW320,
Logical removal was performed on an equipment module and
PSF320
protection is available
Logical removal was performed on an equipment module 10GSO,2G5SO,
where no protecting mate is available. For IOCs and 8XSO, EC320,
XFP/SFP modules if the equipment has supported entities FAN320,
provisioned. MT320/160,
OT2TDM.
10XANY, SFP,
XFP, LOA10G,
CWLA, CADM,
CMDX,
Logical removal was performed on an equipment module PP10AD,
where a protecting mate is available. For IOCs and XFP/SFP PP1GE,
modules if the equipment has no supported entities PP10GE,
provisioned. OMDX8100,
DWLA10X,
PRE10G,
BOOST10G,
LOFA1111
MANWK- Manual switch of working module to protection using LOA10G
SWPR SWTOPROTNEQPT with MODE parameter set to NORM.
MISC-1 Indicates that the slave CRU is not tracking the master CRU. MT320/160
MTXLNK- Indicates that at least one NGI payload link from/to IOC slots MT320/160
FAIL to/from one Matrix slot has been detected in failure
NOT-EQPD NOT-EQPD is an EQPS Condition summarizing Card Missing LOA10G
or Card Mismatch situations on a Card of an EPS Group
NT- Network Time Protocol is enabled, but no NTP server is Shelf
POOSYNC reachable.
Release 5.1 (ETSI)

September 2017

TION TYPE
PRC- It is asserted against a non compatible module inserted into a 10GSO,2G5SO,
DRERR shelf and action is SA (that is, a protection is not available). It 8XSO, EC320,
is set when a module not consistent with Hw slot / Sw FAN320,
assignment (also incompatible revision) is detected. Cleared MT320/160,
when the incompatible module is physically removed OT2TDM.
10XANY, SFP,
XFP, LOA10G,
CWLA, CADM,
CMDX,
It is asserted against a non compatible module inserted into a PP10AD,
shelf and action is NSA (protection available). It is set when a PP1GE,
module not consistent with Hw slot / Sw assignment (also PP10GE,
incompatible revision) is detected. Cleared when the PSF320,
incompatible module is physically removed OMDX8100,
DWLA10X,
PRE10G,
BOOST10G,
LOFA1111
PWR Local side Power has been interrupted to a module while PSF320,
Remote side power is available. The condition indicates loss POW320
of a Battery Feed voltage to the rack or an open CB or fuse.
RAIDSYNC The backup FLC disk is being synchronized to the working EC320
FLC by the RAID system. EC320 protection switching is not
available
SWDWN Indicate that the identified module is being downloaded with a 10GSO,2G5SO,
sw 8XSO, EC320,
MT320/160,
PP10AD,
PP1GE,
PP10GE,
SYN- Indicates an equipment failure of both CRUs. MT320/160
CEQPT
Indicates an equipment failure of one CRU, declared against
the hosting matrix board.
WKSWPR Automatic switch of working module to protection. EC320,
MT320/160,
LOA10G,
WTR Working module is in the Wait-to-restore state (the revert LOA10G
timer is running).
Release 5.1 (ETSI)

September 2017
A.4.2 Facility Condition Type Codes

Refer to Table 38, “1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type
Codes” (p. 633) for facility condition type codes used in the 1850 TSS-320, TSS-320H and TSS-160
configuration. The DESCRIPTION column identifies the relationship between facility and condition
type. The FACILITY TYPE column lists applicable facility types for each condition.
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type Codes
CONDI- DESCRIPTION EQUIPMENT

TION TYPE
ACTLPBK The associated entity has a loopback activated at the near GBE, MAU
end.
AIS Indicates that a CRU has detected a AIS for a dedicated BITS BITS
facility.
Alarm Indication Signal STM-n
AIS-P Alarm Indication Signal VCn
AIS-V Alarm Indication Signal LOVCn
APSB Protection Byte Failure has been detected. This failure is STM-n
applicable to 1+1 bidirectional FFP provisioned facilities.
APSCD- APS Condition, Default K-bytes. This condition is set when STM-n
FLTK the default code is detected on the incoming K-bytes.
APSCIMP APS Condition, Improper K-bytes. This condition is set when STM-n
improper K-bytes are detected on the incoming K1-bytes
APSCIN- APS Condition, Inconsistent K-bytes. This condition is set STM-n
CON when inconsistent K-bytes are detected.
APSCM APS Channel Match Failure been detected. This failure is STM-n
applicable to 1+1 bidirectional FFP provisioned facilities.
APSCNMIS APS Condition, Connection Mismatch. This condition is set STM-n
when a Node identifier mismatch in K bytes is detected.
APSMM APS Mode Mismatch Failure has been detected. This failure STM-n
is applicable to 1+1 bidirectional FFP provisioned facilities.
BDI Backward Defect Indicator ODU2, OTU2
DEG Signal Degrade ODU2
EBER Excessive Bit error rate STMn,VCn,
LOVCn
EOC Embedded Operations Channel failure on Section DCC. No STMn
adjacencies formed.
Release 5.1 (ETSI)

September 2017
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type
Codes (continued)

TION TYPE
EOCL Embedded Operations Channel failure on Line DCC. No STMn
adjacencies formed.
FDI An FDI packet with MEL = 0 has been received. TUSEG
FELANLFI Far End LAN Local Fault Indicator, GBE10
FELANLOS Far End LAN Loss of signal GBE10
FELANLLS Far End LAN Loss of synchronization GBE10
FELANRFI Far End LAN Remote Fault Indicator GBE10
FRCD- Timing Selection is forced to a Timing Reference. TIMING
SWTIM-
REF
FRCDWKSWBK-FE
Forced Switch of Service from Protection back to Working FFP
facility due to request from far end.
FRCDWK- Forced Switch of Service from Protection back to Working FFP, LOVCn,
SWBK facility. VCn
FRCDWKSWPR-FE
Forced Switch of Service from Working to Protection facility FFP
die to request from Far End.
FRCDWKSWPR-RING
Forced Working Switch to Protection. This condition indicates FFP
that a forced ring switch from working channels to protection
channels is in effect.
FRCDWKSWPR-RING-FE
Forced Working Switch to Protection. This condition indicates FFP
that a forced ring switch from working channels to protection
channels is in effect as a result of a far-end node's request.
FRCDWK- Forced Switch of Service from Working to Protection facility. FFP, LOVCn,
SWPR VCn
FRNG- Indicates that the system clock is in free running TIMING
SYNC synchronization mode.
GFPCSF Client Signal Failure on the VCG. Always Service affecting. VCG
GFPEXM Extension Header Mismatch on the VCG. Always Service VCG
affecting.
GFPLOF Loss of GFP alignment on the VCG. Always Service VCG
affecting..
GFPUPM User Payload type Mismatch on the VCG. Always Service VCG
affecting..
Release 5.1 (ETSI)

September 2017
Codes (continued)

TION TYPE
HL- Indicates that the system timing is in autonomous holdover TIMING
DOVRSYNC synchronization mode.
IPC- IPCP Line DCC connection failure STMn
PLCON-
FAIL
IPCP- IPCP Section DCC connection failure STMn
SCONFAIL
L2LCONFAIL Layer 2 Line DCC connection failure: Line DCC can not STMn
communicate with far-end Line DCC due to data link
connection problems.
L2SCONFAIL Layer 2 Section DCC connection failure: Section DCC can not STMn
communicate with far-end Section DCC due to data link
connection problems.
LANLFI LAN Local Fault Indicator GBE10
LANLOS LAN Loss of Signal GFC10, GBE10
LANLSS LAN Loss of Synchronization GFC10, GBE10
LANRFI LAN Remote Fault Indicator GBE10
LCK Payload Locked ODU2
LCPLCON- LCP Line DCC connection failure: Alarm raised after STMn
FAIL MAXCONFIG count exhausted.
LCPSCON- LCP Section DCC connection failure: Alarm raised after STMn
FAIL MAXCONFIG count exhausted.
LFD Loss of Frame Delineation GBE10
LFIEGR Local Fault Indicator Egress GBE10
LOCKOUTOFPR-FE
Lock out of Protection facility due to a request from far end. FFP
LOCK- Lock out of Protection facility. FFP, LOVCn,
OUTOFPR VCn
LOCK- Lock out of a Timing Reference from Selection. TIMING
OUT-
OFTIMREF
LOCKOU- Lockout of Protection Span. This condition indicates that a FFP
TOPS lockout of the use of protection channels is in effect.
Release 5.1 (ETSI)

September 2017
Codes (continued)

TION TYPE
LOCK- Lockout of working: LOW-R command prevents the FFP
OUTWR addressed working span from requesting any switch. if it was
in switched state then the switch will be dropped regardless of
the state of the working
LOC Loss of CV packets for a period greater than 3.5 the TUSEG
CVprovisioned period
LOF Loss of Frame OTU2, STMn
Indicates that a CRU has detected a Loss of frame for a BITS
dedicated BITS facility
LOFEGR Loss of Frame egress direction STMn
LOL Loss of Link, GBE / MAU GBE, MAU
LOM Loss of Multiframe OTU2
LOM-P Loss of Multiframe VCn
LOP-P Loss of Pointer VCn
LOP-V Loss of Pointer LOVCn
LOS Loss of Optical Signal GBE, MAU
Loss of Signal OGPORT, STMn
Indicates that a CRU has detected a Loss of signal for a BITS
dedicated BITS facility
LOS-P Loss of Signal - Payload OTU2
LOSEGR Loss of Signal egress GBE10
LSSEGR Loss of Character Synchronization Egress, GFC10, GBE10
MAN Manually taken out of service while it has service affecting GBE
condition.
Manually Taken out of service ODU2, OTU2,
GBE10, GFC10,
MAU, LOVCn,
VCn, OGPORT,
VCG
Indicates that a logical removal was performed on a BITS, TIMING
BITS/timing reference.
Release 5.1 (ETSI)

September 2017
Codes (continued)

TION TYPE
MAN- Timing Selection is switched via Manual command to a Timing TIMING
SWTIM- Reference.
REF
MANSW- Indicates that a manual switch to Internal Timing (i.e. forced TIMING
TOINT holdover mode) has occurred.
MANWKSWBK-FE
Manual Switch of Service from Protection back to Working FFP
facility due to a request from far end.
MANWK- Manual Switch of Service from Protection back to Working FFP, LOVCn,
SWBK facility. VCn
MANWKSWPR-FE
Manual Switch of Service from Working to Protection facility FFP
due to a request from far end.
MANWKSWPR-RING-FE
Manual Working Switch to Protection. This condition indicates FFP
that a manual ring switch from working channels to protection
channels is in effect as aresult of a far-end node's request.
MANWKSWPR-RING
Manual Working Switch to Protection. This condition indicates FFP
that a manual ring switch from working channels to protection
channels is in effect.
MANWK- Manual Switch of Service from Working to Protection facility. FFP, LOVCn,
SWPR VCn
MMG A CV packet with MEL = 0 and an invalid MEG value (that is TUSEG
with a MEG_ID different from theconfigured MEG_ID at the
receiving MEP) has been received.
OCI Open Connection Indication ODU2
OSIN- OSINLCP Line DCC connection failure STMn
LCPLCON-
FAIL
OSINLCP- OSINLCP Section DCC connection failure STMn
SCONFAIL
PLM Payload Type Mismatch ODU2
PLM-P Payload Label Mismatch, Failure VCn
RFI Remote Failure Indication, LOVCn, VCn,
STMn
RFIEGR Remote Fault Indicator Egress, GBE10
Release 5.1 (ETSI)

September 2017
Codes (continued)

TION TYPE
RNG- Traffic on ring squelched. FFP
SQLCH
SDBER Bit error rate is greater than or equal to provisioned threshold VCn, OGPORT,
LOVCn, STMn
SDEG-O SUPVY Signal Degrade OTSPORT
SLTMSIG Indicates that the timing reference frequency has moved off TIMING
the required accuracy limits
SSF Server Signal Failure ODU2, OTU2
SSF-L SSF STMn
SSF-P SSF VCn
SSF-V SSF LOVCn
SSFI LOVCn
SYNCOOS Indicates all available timing reference have failed and the TIMING
system is going into holdover.
SYNCREF- Indicates the timing reference failed. TIMING
FAIL
SYNCRE- Indicates the timing reference is unassigned. TIMING
FUNEQ
SYNCT4OUT Indicates that timing quality for output timing is insufficient and TIMING
therefore squelched
T-BBE- Indicates a T-BBE-HOVC-1-DAY Threshold Crossing was
HOVC-1- detected
DAY
VCn
T-BBE- Indicates a T-BBE-HOVC-15-MIN Threshold Crossing was
HOVC-15- detected
MIN
T-BBE- Indicates a T-BBE-LOVC-1-DAY Threshold Crossing was
LOVC-1- detected
DAY
LOVCn
T-BBE- Indicates a T-BBE-LOVC-15-MIN Threshold Crossing was
LOVC-15- detected
MIN
Release 5.1 (ETSI)

September 2017
Codes (continued)

TION TYPE
T-BBE-MS- Indicates a T-BBE-MS-1-DAY Threshold Crossing was
1-DAY detected
STMn
T-BBE-MS- Indicates a T-BBE-MS-15-MIN Threshold Crossing was
15-MIN detected
T-BBE- Indicates a T-BBE-ODU-1-DAY Threshold Crossing was
ODU-1- detected
DAY
ODU2
T-BBE- Indicates a T-BBE-ODU-15-MIN Threshold Crossing was
ODU-15- detected
MIN
T-BBE- Indicates a T-BBE-OTU-1-DAY Threshold Crossing was
OTU-1-DAY detected
T-BBE- Indicates a T-BBE-OTU-15-MIN Threshold Crossing was OTU2
OTU-15- detected
MIN
T-BBE-RS- Indicates a T-BBE-RS-1-DAY Threshold Crossing was
1-DAY detected
STMn
T-BBE-RS- Indicates a T-BBE-RS-15-MIN Threshold Crossing was
15-MIN detected
T-CV-PCS- Indicates a CV-PCS Threshold Crossing 1 day was detected
1-DAY GBE, GBE10,
T-CV-PCS- Indicates a CV-PCS Threshold Crossing 15 min was detected GFC10, MAU
15-MIN
T-EIFE-1- Indicates a EIFE Threshold Crossing 1 day was detected
DAY GBE, GBE10,
T-EIFE-15- Indicates a EIFE Threshold Crossing 15 min was detected MAU
MIN
T-ES- Indicates a T-ES-HOVC-1-DAY Threshold Crossing was
HOVC-1- detected
DAY
VCn
T-ES- Indicates a T-ES-HOVC-15-MIN Threshold Crossing was
HOVC-15- detected
MIN
Release 5.1 (ETSI)

September 2017
Codes (continued)

TION TYPE
T-ES- Indicates a T-ES-LOVC-1-DAY Threshold Crossing was
LOVC-1- detected
DAY
LOVCn
T-ES- Indicates a T-ES-LOVC-15-MIN Threshold Crossing was
LOVC-15- detected
MIN
T-ES-MS-1- Indicates a T-ES-MS-1-DAY Threshold Crossing was detected
DAY
STMn
T-ES-MS- Indicates a T-ES-MS-15-MIN Threshold Crossing was
15-MIN detected
T-ES-ODU- Indicates a ES-ODU Threshold Crossing 1 day was detected
1-DAY
ODU2
T-ES-ODU- Indicates a ES-ODU Threshold Crossing 15 min was detected
15-MIN
T-ES-OTU- Indicates a ES-OTU Threshold Crossing 1 day was detected
1-DAY
OTU2
T-ES-OTU- Indicates a ES-OTU Threshold Crossing 15 min was detected
15-MIN
T-ES-PCS- Indicates a ES-PCS Threshold Crossing 1 day was detected
1-DAY GBE, GBE10,
T-ES-PCS- Indicates a ES-PCS Threshold Crossing 15 min was detected GFC10, MAU
15-MIN
T-ES-RS-1- Indicates a T-ES-RS-1-DAY Threshold Crossing was detected
DAY
STMn
T-ES-RS- Indicates a T-ES-RS-15-MIN Threshold Crossing was
15-MIN detected
T-FECC-1- Indicates a FECC Threshold Crossing 1 day was detected
DAY
OTU2
T-FECC- Indicates a FECC Threshold Crossing 15 min was detected
15-MIN
T-OFS-RS- Indicates a T-OFS-RS-1-DAY Threshold Crossing was
1-DAY detected
STMn
T-OFS-RS- Indicates a T-OFS-RS-15-MIN Threshold Crossing was
15-MIN detected
Release 5.1 (ETSI)

September 2017
Codes (continued)

TION TYPE
T-SEFS- Indicates a SEFS-PCS Threshold Crossing 1 day was
PCS-L-1- detected
DAY GBE, GBE10,
T-SEFS- Indicates a SEFS-PCS Threshold Crossing 15 min was GFC10, MAU
PCS-L-15- detected
MIN
T-SES- Indicates a T-SES-HOVC-1-DAY Threshold Crossing was
HOVC-1- detected
DAY
VCn
T-SES- Indicates a T-SES-HOVC-15-MIN Threshold Crossing was
HOVC-15- detected
MIN
T-SES- Indicates a T-SES-LOVC-1-DAY Threshold Crossing was
HOVC-1- detected
DAY
LOVCn
T-SES- Indicates a T-SES-LOVC-15-MIN Threshold Crossing was
LOVC-15- detected
MIN
T-SES-MS- Indicates a T-SES-MS-1-DAY Threshold Crossing was
1-DAY detected
STMn
T-SES-MS- Indicates a T-SES-MS-15-MIN Threshold Crossing was
15-MIN detected
T-SES- Indicates a SES-ODU Threshold Crossing 1 day was
ODU-L-1- detected
DAY
ODU2
T-SES- Indicates a SES-ODU Threshold Crossing 15 min was
ODU-L-15- detected
MIN
T-SES- Indicates a SES-OTU Threshold Crossing 1 day was detected
OTU-L-1-
DAY
OTU2
T-SES- Indicates a SES-OTU Threshold Crossing 15 min was
OTU-L-15- detected
MIN
Release 5.1 (ETSI)

September 2017
Codes (continued)

TION TYPE
T-SES- Indicates a SES-PCS Threshold Crossing 1 day was detected
PCS-L-1-
DAY GBE, GBE10,
T-SES- Indicates a SES-PCS Threshold Crossing 15 min was GFC10, MAU
PCS-L-15- detected
MIN
T-SES-RS- Indicates a T-SES-RS-1-DAY Threshold Crossing was
1-DAY detected
STMn
T-SES-RS- Indicates a T-SES-RS-15-MIN Threshold Crossing was
15-MIN detected
TIM Trail trace Identifier Mismatch ODU2, OTU2
TIM-P Trail trace Identifier Mismatch VCn
TIM-S Trail trace Identifier Mismatch STMn
TIM-V Trail trace Identifier Mismatch LOVCn
UAT-HOVC Indicates a Unavailable Time period VCn
UAT-LOVC Indicates a Unavailable Time period LOVCn
UAT-MS Indicates a Unavailable Time period STMn
UAT-ODU Indicates a Unavailable Time period ODU2
UAT-OTU Indicates a Unavailable Time period OTU2
UAT-RS Indicates a Unavailable Time period STMn
UNEQ-P Idle (unequipped) VCn
UNEQ-V Idle (unequipped) LOVCn
UNM A CV packet with MEL = 0 and a valid MEG_ID, but with an TUSEG
invalid MEP (that is with a MEP_ID different from the
configured PeerMEP_ID at the receiving MEP) has been
received.
UNP A CV packet with MEL = 0, valid MEG_ID, valid MEP_ID, but TUSEG
with an invalid CV_Period (that is with a received period value
different from the configured period at the receiving MEP) has
been received.
Release 5.1 (ETSI)

September 2017
Codes (continued)

TION TYPE
UNPHB A CV packet with MEL = 0, valid MEG_ID, valid MEP_ID, but TUSEG
with an invalid CV_PHB (that is with a received PHB value
different from the configured PHB at the receiving MEP) has
been received.
UPM User Payload Identifier Mismatch GBE10
URU-O URU OGPORT, STMn
URU-P URU VCn
URU-S URU STMn
URU-V URU VCn, LOVCn
VCAIS-P VC-AIS VCn
VCAIS-V VC-AIS LOVCn
VCGLOA Loss of Alignment on the VCG while one or more of its VCG
members are cross connected (ACT/BUSY) and enabled to
carry traffic (VCACT). Always service affecting.
VCGLPF LCAS protocol failure on the VCG. Always service affecting. VCG
VCGPLC Partial Loss of Capacity on the VCG. Always non-service VCG
affecting. Only with LCAS enabled.
VCGPLM Payload type Mismatch on the VCG. Always Service affecting. VCG
Only for GBEVCG.
VCGRFI Remote failure indication on the VCG. Always non-service VCG
affecting. Only with LCAS enabled.
VCGSSF Server Signal Failure on the VCG while one or more of its
members are cross connected (ACT/BUSY) and enabled
(VCACT)
VCG
Server Signal Failure on the VCG while either none of its
members are not cross connected or at least one member is
cross connected (ACT/BUSY) but it is not enabled (ACTIDLE)
VCGURU Server Signal Failure on the VCG while one or more of its
members are cross connected (ACT/BUSY) and enabled
(VCACT) VCG
Underlying Resource Unavailble on the VCG. Hardware
failure of the equipment providing VCAT function.
Release 5.1 (ETSI)

September 2017
Codes (continued)

TION TYPE
VCLOM Loss of Multiframe on a path facility that is a member of a LOVCn, VCn
VCG. Always non-service affecting.
VCMND The differential delay on a path facility that is a member of a LOVCn, VCn
VCG cannot be compensated. Always non-service affecting.
VCSQM Sequence Number Mismatch on a path facility that is a LOVCn, VCn
member of a VCG. Always non-service affecting.
WKSWBK-FE (Automatic) Switch of Service from Protection back to FFP
Working facility due to a request from far end.
WKSWBK (Automatic) Switch of Service from Protection back to FFP, LOVCn,
Working facility. VCn
WKSWPR-FE (Automatic) Switch of Service from Working to Protection FFP
facility due to a request from far end.
WKSWPR- Working Switch to Protection: Automatic switch of working FFP
RING-FE facility to protection (ring) as a result of a far-end node's
request.
WKSWPR- Working Switch to Protection: Automatic switch of working FFP
RING facility to protection (ring) as a result of a near-end node's
request.
WKSWPR (Automatic) Switch of Service from Working to Protection FFP, LOVCn,
facility. VCn
WTR (Automatic) Set on Working path of a SNCP when switching is LOVCn, VCn
revertive and defects have cleared on Working and the Wait
to Restore timer is in effect.
(Automatic) Set on a timing reference and defects have TIMONG
cleared and the Wait to Restore timer is in effect.
Wait to Restore state. A failure has cleared and traffic will be FFP
restored to the working side when the revert timer expires
A.4.3 Transient Condition Type Codes

Refer to Table 39, “Transient Condition Type Codes” (p. 646) for transient condition type codes
used in the system.
Release 5.1 (ETSI)

September 2017
Table 39 Transient Condition Type Codes
CONDI- CONDITION DESCRIPRTION AID

TION TYPE
DORMAN- An user remains inactive, without log-on the NE, for a SECU
TUSER configurable interval of time.
FAIL- Fail to Release Ring. This condition is set when any legal FFP
TORLSRING switch release requests that a node (near end or far end)
cannot complete, such as dropping of the bridge or the switch
event.
FAIL- Fail to Switch Ring. This condition is set when any legal FFP
TOSWRING switch request that a node (near end or far end) cannot
complete, such as failure to bridge, failure to switch, no
response from the far-end.
INTRU- Excessive Invalid Login Attempts, or two Consecutive Invalid SECU
SION Login Attempts before the minimum interval.
LOGBUF90-SECULOG
SECULOG has reached 90% of its max size SECU
LOGBUFOVFL-SECULOG
SECULOG has reached its max size, after this event has SECU
been sent the SECULOG wraps reducing its size to the 70%
of its max size discarding the oldest events (30%)
PMGLBE- Entering the Emtpy state of PM Globale File Collection Shelf
MPTY
PMGL- Entering the file transfer running state of PM Globale File Shelf
BFTR Collection
PMGL- Entering the In Preparation state of PM Globale File Shelf
BINPREP Collection
PMGL- Entering the Ready state of PM Globale File Collection Shelf
BREADY
A.4.4 Notification Codes

Refer to Table 40, “Notification Codes” (p. 646) for notification codes reported by the system.
Codes are listed in order of significance.
Table 40 Notification Codes
NOTIFICATION CODE DEFINITION

ALL All codes
CL Cleared
CR Critical alarm, reported by REPT ALM
MJ Major alarm, reported by REPT ALM
Release 5.1 (ETSI)

September 2017
Table 40 Notification Codes (continued)

MN Minor alarm, reported by REPT ALM
NA Not alarmed, reported by REPT EVT
NR Not reported
A.4.5 Service Affect Codes

Refer to Table 41, “Service Affect Codes” (p. 647) for service affect codes that indicate whether a
condition is service-affecting or non-service-affecting.
Table 41 Service Affect Codes

SA Service-affecting, immediate action required
NSA Non-service-affecting, action required
A.4.6 Response (Error) Codes

Refer to Table 42, “Response (Error) Codes” (p. 647) for a list of response (error) codes used in
unsuccessful response messages by the system.
Table 42 Response (Error) Codes
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
Release 5.1 (ETSI)

September 2017
Table 42 Response (Error) Codes (continued)
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
Release 5.1 (ETSI)

September 2017
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
Release 5.1 (ETSI)

September 2017
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
Release 5.1 (ETSI)

September 2017
CODE DEFINITION
SWFA Status, Working unit FAiled
A.4.7 Command Parser Error Codes

Refer to Table 43, “Command Parser Error Codes” (p. 651) for a list of response (error) codes used
in an unsuccessful response message by the system's Command Parser when a command cannot
be successfully parsed.
Table 43 Command Parser Error Codes
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
Release 5.1 (ETSI)

September 2017
Security 1850 TSS-320/TSS-320H/TSS-160
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
A.5.2 Controlling System Access

When the NE is in SECURE mode, only ports 6084 and 6085 (TL1), 6086 (CLI) and 443 (HTTPS)
are opened.
When the NE is in UNSECURE mode only ports 3082 and 3083 (TL1), 1123 (CLI), 22 (debug port
for ROOT access always with SSH), 23 (port for telnet) and 80 (http) shall be opened. System
access requires every user to correctly enter the ACT-USER command using a valid UID and its
corresponding PID within a preset number of attempts.
To prevent an unauthorized bystander from viewing a user's PID, the TL1 command echoes (as the
user types) a series of asterisks (******) in place of the PID as it is typed.
Remote access to the 1850 TSS-100 does not employ an encrypted data path on the the external
link between the user and the LNPT on the system.
When a login is attempted, the system verifies that the command was entered using the correct
syntax and that the UID/PID combination matches encrypted records set up in the internal security
database. If the UID and PID are acceptable, the user can access the system. A message displays
with the date and time of the last successful session and the number of unsuccessful attempts by
that user ID to gain system access since the last successful access.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Security
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.
Entering New Users

The system security administrator sets up and controls the security database. The ENT-USER-
SECU command is used to establish a security record for each person or network entity (such as
an operations support system) that is allowed to access the system.
A UID, a PID, and a User Community Authorization Level (UCAL) are required for every user. Users
must not share a UID/PID. (The UCAL is described in detail later in this section.)
The UID must meet the following requirements:

• UID must be unique within the system.
• UID must be at least five and no more than 12 alphanumeric characters long.
• UID may contain special characters %, +, #, and _ (underscore).
• UID first character must be an alphabetic character.
The PID must meet the following requirements:

• PID must be at least eight and no more than 12 alphanumeric characters long.
• PID must have at least one upper alphabetic character, one lower alphabetic character, and at
least one numeric character.
• PID may contain special characters %, +, #, and _ (underscore).
• PID first character may be an alphabetic, numeric, or a valid special character.
• PID cannot be the same as the UID or the reverse of the UID.
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.
Release 5.1 (ETSI)

September 2017
Security 1850 TSS-320/TSS-320H/TSS-160
User Control of Password

Authorized users can change their own passwords, using the ED-PID command, at any time before
the passwords expire. To change the password, the user must be logged into the system using the
current UID and PID. To change the PID, the user must know the UID and the old PID. This
prevents an unauthorized person from inappropriately changing the currently logged-in user's
password.
The command syntax is:
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).
Invalid Login Attempts

To deter repeated attempts to breach login security measures, the system restricts the number of
unsuccessful login attempts for a session. The maximum number of invalid login attempts for a
session allowed on the NE is provisionable by the system-wide Max Invalid Attempts (MXINV)
parameter.
The maximum number of invalid login attempts allowed is 15. A value of 0 disables this function.
After the maximum number of invalid login attempts for a session, and the consequent lockout, the
system records in the security log the IP address of the source along with the user ID.
After the maximum number of invalid login attempts for a session, an intrusion standing, alarm
condition is reported against a Common access identifier.
The RTRV-DFLT-SECU command is used to retrieve the MXINV parameter and the SET-ATTR-
SECUDFLT command is used to change it.
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).
A.5.3 Controlling Access to System Resources

An important part of system security involves restricting the commands that users are allowed to
execute.
The following paragraphs describe system command security and the tasks required to accomplish
resource control.
Command and User Privileges
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Security
• 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.
System Control of Command Use

The Permission filter compares UAPs assigned to commands with UAPs assigned to users. If a
user enters a restricted command, the comparison fails and the command is denied. This control is
established through the UAP parameter of the ENT-USER-SECU and ED-USER-SECU commands.
Privilege and Category Assignments

The system administrator UID defaults allow access to commands needed to establish user-
security database records and change parameters affecting system security. In the absence of a
system security administrator account, commands that directly affect system security cannot be
executed.
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)
Release 5.1 (ETSI)

September 2017
Performance Monitoring 1850 TSS-320/TSS-320H/TSS-160
• Canceling a User Session (CANC-USER-SECU)

• Inhibiting an existing User (INH-USER-SECU)
• Allowing an inhibited User (ALW-USER-SECU)
A.5.4 Security Audits

The Security Log allows a Security Administrator the capability to investigate, audit, detect, and
analyze security events in order that proper remedial actions can be taken.
The SECULOG is the security log. The RTRV-AUDIt-SECULOG command is used to view the
security log entries.
Each NE is able to log 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).
The security log entry contains:

• the identification, address, and security level of the user that initiated the action that is being
logged.
• the actual attempted action that is being logged (the echo of the command/response message).
• an indication of the success or failure of the activity (command completion code).
• the date, time, and, the action, that is the command or the message, occurred
When the SECULOG records any command in which a PID is entered or changed (ACT-USER,
ENT-USER-SECU, ED-PID, or ED-USER-SECU), the PID is never shown in plain text. This
prevents discovery of a user's password using the SECULOG.
The SECULOG is read-only. It cannot be edited, deleted, or backed up and restored. This prevents
anyone, including the security administrator, from tampering with the data in the log. Information
from the log can be read using the RTRV-AUDIt-SECULOG command.
A.6 Performance Monitoring

A.6.1
The system uses internal equipment monitoring to detect faults and card failures, and to issue
appropriate alarms, alerting users of troubles.
Equipment monitoring does not, however, detect deteriorating conditions that could lead to service-
affecting failures. Performance Monitoring (PM) provides this important function. PM continuously
monitors selected parameters of incoming traffic, detects errors, counts the detected errors, and
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Performance Monitoring
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.
The system performs PM on the following facility types:

• Ethernet (GBE, GBE10, GFC10)
• STM-n, (where n = 1. 4, 16, 64)
• OTU-2, ODU-2
• MAU
The system monitors and reports several performance parameters that let the user distinguish
between a system internal failure and an incoming facility failure. Refer to the Monitored
Parameters subsection in this section for lists and definitions of the parameters monitored for each
facility type.
SET-TH-rr commands (where rr is the facility type) are used to define performance parameter
thresholds for each circuit. The user can select the parameter type and threshold level, and initialize
the error count register on a daily or 15-minute basis. These user-defined thresholds are stored in
the circuit-provisioning database. RTRV-TH-rr commands cause the defined parameter thresholds
to display.
A.6.2 Storage Registers

Refer to Table 44, “Number of Registers for Each PM Parameter Monitored” (p. 656) for a list of the
types and numbers of storage registers provided for each PM parameter monitored.
Table 44 Number of Registers for Each PM Parameter Monitored
NUMBER OF REGISTERS PER MONITORED PARAMETER

REGISTER TYPE 15-MINUTE 1-DAY
Current 1 1
Previous 1 1
Recent 31 6
A.6.3 Register Initialization

Current registers for 15-minute and 1-day counts accumulate error and event counts. When the
count in any of these registers reaches a maximum value, the register remains full until either it is
reset or the value is transferred to the Previous register. Current registers initialize in the following
circumstances:
• Automatically every 15 minutes or 1 day (24 hours) (register value set to 0)
• Manually using the INIT-REG-rr command at any time
The INIT-REG commands let the user reset selected error count registers to zero. The register's
value then increments from that value as new errors are counted. When the end of the time period
for the register (1-DAY or 15-MIN) is reached, its count is automatically initialized to 0.
Release 5.1 (ETSI)

September 2017
A.6.4 Validity Flags
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.
A.6.5 Threshold Registers

Two threshold registers are provided for each parameter monitored; a 15-minute threshold register
and a 1-day threshold register. Threshold registers are supported for all facility PM parameters.
Use the SET-TH-rr command to set threshold register values and use RTRV-TH-rr to retrieve them.
Minimum threshold register size is equal to the corresponding storage register size.
Release 5.1 (ETSI)

September 2017
A.6.6 Threshold Crossing Alerts

A threshold value is crossed when a current value register reaches or exceeds the set value in the
corresponding threshold register. When a threshold crossing is recognized, Threshold Crossing
Alerts (TCAs) are generated using REPT EVT messages.
During an accumulation period, only one TCA is sent for each threshold setting on a Current
register, unless the Current register is reset or the threshold is increased. In that case, the reset
Current register must again reach or exceed its value before another TCA is sent.
A threshold is not crossed (and no TCA is generated) if a register value that has reached a
threshold value is reduced to less than the threshold value when unavailability is declared.
Setting a threshold register value to zero inhibits the corresponding TCA from being generated or
reported. This effectively disables that TCA for that entity.
A.6.7 Retrieving Selective PM Data

The RTRV-PM-rr commands are used to retrieve PM data on selected ports. These commands are
used to let the user receive PM reports on specified ports immediately.
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
A.6.8 Monitored Parameters
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).
Table 45 GBE PM Parameters
Monitored type parameter Definition
• GBE Section Near End PM Parameters
Release 5.1 (ETSI)

September 2017
Table 45 GBE PM Parameters (continued)

CVS-PCS Code Violations - Near End PCS
ES-PCS Errored Seconds - Near End Section
SEFS-PCS Severely Errored Frame Seconds - Section
SES-PCS Severely Errored Seconds - Near End Section
• GBE Ethernet PM Parameters

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
Table 46 OTU2 PM Parameters
• Section Near End

BBE-OTU Background Block Error - Near End OTUk Section
ES-OTU Errored Seconds - Near End OTUk Section
FECC FEC Errors Corrected - Near End
SES-OTU Severely Errored Seconds - Near End OTUk Section
UAS-OTU Unavailable Seconds - Near End OTUk Section
Table 47 ODU2 PM Parameters

BBE-ODU Background Block Error - Near End ODUk Path
ES-ODU Errored Seconds - Near End ODUk Path
SES-ODU Severely Errored Seconds - Near End ODUk Path
UAS-ODU Unavailable Seconds - Near End ODUk Path
Release 5.1 (ETSI)

September 2017
Table 48 10GBE PM Parameters

• 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
Table 49 10GFC PM Parameters

Table 50 STM-n (n = 1, 4, 16, 64) PM Parameters
• STM-n Line Near End

BBE-MS Background Block Errors - Near End Multiplex Section
ES-MS Error Second - Near End Multiplex Section
SES-MS Severely Error Second - Near End Multiplex Section
UAS-MS Unavailable Seconds - Near End Multiplex Section
• STM-n Line Far End
Release 5.1 (ETSI)

September 2017
Table 50 STM-n (n = 1, 4, 16, 64) PM Parameters (continued)

BBE-MS Background Block Errors - Far End Multiplex Section
ES-MS Error Second - Far End Multiplex Section
SES-MS Severely Error Second - Far End Multiplex Section
UAS-MS Unavailable Seconds - Far End Multiplex Section
• STM-n Section Near End

Background Block Errors - Near End Regenerator
BBE-RS
Section
ES-RS Error Second - Near End Regenerator Section
OFS-RS Out of Frame Seconds - Near End Regenerator Section
SES-RS Severely Error Second - Near End Regenerator Section
UAS-RS Unavailable Seconds - Near End Regenerator Section
Table 51 VC4n (n = 4C, 16C, 64C) PM Parameters
• Path Near End

BBE-HOVC Background Block Errors - Near End Higher Order VC
Path
ES-HOVC Error Second - Near End Higher Order VC Path
PJEN-HOVC Negative Pointer Justification Events - Near End Higher
Order VC Path
PJEP-HOVC Positive Pointer Justification Events - Near End Higher
Order VC Path
SES-HOVC Severely Error Second - Near End Higher Order VC
Path
UAS-HOVC Unavailable Seconds - Near End Higher Order VC Path
• Path Far End

BBE-HOVC Background Block Errors - Far End Higher Order VC
Path
ES-HOVC Error Second - Far End Higher Order VC Path
SES-HOVC Severely Error Second - Far End Higher Order VC Path
UAS-HOVC Unavailable Seconds - Far End Higher Order VC Path
Release 5.1 (ETSI)

September 2017
Table 51 VC4n (n = 4C, 16C, 64C) PM Parameters (continued)
• 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
SES-HOVC-FE Severely Error Second - Bidirectional Far End Higher
Order VC Far End
ES-HOVC-IN Severely Error Second - Bidirectional Far End Higher
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
Table 52 LOVCn (n = 3, 12) PM Parameters
• Path Near End

BBE-LOVC Background Block Errors - Near End Lower Order VC
Path
ES-LOVC Error Second - Near End Lower Order VC Path
Release 5.1 (ETSI)

September 2017
Table 52 LOVCn (n = 3, 12) PM Parameters (continued)

SES-LOVC Severely Error Second - Near End Lower Order VC Path
UAS-LOVC Unavailable Seconds - Near End Lower Order VC Path
• Path Far End

BBE-LOVC Background Block Errors - Far End Lower Order VC
Path
ES-LOVC Error Second - Far End Lower Order VC Path
SES-LOVC Severely Error Second - Far End Lower Order VC Path
UAS-LOVC Unavailable Seconds - Far End Lower Order VC Path
• Path Bidirectional
BBE-LOVC-EG Background Block Errors - Bidirectional Far End Lower
BBE-LOVC-FE Background Block Errors - Bidirectional Far End Lower
Order VC Far End
BBE-LOVC-IN Background Block Errors - Bidirectional Far End Lower
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
SES-LOVC-FE Severely Error Second - Bidirectional Far End Lower
Order VC Far End
ES-LOVC-IN Severely Error Second - Bidirectional Far End Lower
SES-LOVC-NE Severely Error Second - Bidirectional Far End Lower
Order VC Near End
Release 5.1 (ETSI)

September 2017
Table 52 LOVCn (n = 3, 12) PM Parameters (continued)

UAS-LOVC-BI Unavailable Seconds - Bidirectional Far End Lower
Order VC Path
Table 53 MAU PM Parameters
• Path Near End

Background Block Errors - Near End Lower Order VC
BBE-LOVC
Path
ES-LOVC Error Second - Near End Lower Order VC Path
SES-LOVC Severely Error Second - Near End Lower Order VC Path
UAS-LOVC Unavailable Seconds - Near End Lower Order VC Path
• Path Far End

Background Block Errors - Far End Lower Order VC
BBE-LOVC
Path
ES-LOVC Error Second - Far End Lower Order VC Path
SES-LOVC Severely Error Second - Far End Lower Order VC Path
UAS-LOVC Unavailable Seconds - Far End Lower Order VC Path
A.6.9 User Command Privilege and Log Indication

Refer to Table 54, “User Command Privilege Defaults” (p. 665) for TL1 commands and their
associated default Command Access Privilege (CAPs). The Security Log column indicates if a
command (and related responses) are stored in the security log file (Y) or are not logged (N).
Table 54 User Command Privilege Defaults
Command Code Default Privilege Default SecuLog

ACT-DB-BACKUP NETADMIN Y
ACT-USER READ Y
ALW-SWDX-EQPT CONF Y
ALW-SWTOPROTN-EQPT CONF Y
ALW-USER-SECU SEC Y
CANC-COPY-RFILE NETADMIN Y
Release 5.1 (ETSI)

September 2017
Table 54 User Command Privilege Defaults (continued)

CANC-DB-BACKUP NETADMIN Y
CANC-USER-SECU SEC Y
CANC-USER READ Y
CNTRL-VCPATH CONF Y
CNVT-CCJ-<RATE> PROV Y
CNVT-CCS-<RATE> PROV Y
CNVT-CCTPR-<RATE> PROV Y
CNVT-CCTU-<RATE> PROV Y
COPY-RFILE NETADMIN Y
DLT-ARPCACHE CONF Y
DLT-ASAP-PROF CONF Y
DLT-CP-COM CONF Y
DLT-CP-RT CONF Y
DLT-CP-TPORT CONF Y
DLT-CPTMPLS-HOPLIST CONF Y
DLT-CRS-<RATE> CONF Y
DLT-CRSPROT-<RATE> CONF Y
DLT-EQPT CONF Y
DLT-FFP-<STMN> CONF Y
DLT-FFP-TMPLS CONF Y
DLT-GBE10 CONF Y
DLT-L2ENCAP-PROF CONF Y
DLT-NE-IPRT NETADMIN Y
DLT-NE-IPT NETADMIN Y
DLT-NETIF NETADMIN Y
DLT-NTP-ADDR NETADMIN Y
DLT-OAMPHB-PROF CONF Y
DLT-OTU2 CONF Y
DLT-OVHCCRS CONF Y
Release 5.1 (ETSI)

September 2017

DLT-PHB-PROF CONF Y
DLT-TH-PROF CONF Y
DLT-TMPLS-PW CONF Y
DLT-TMPLS-PWSEG CONF Y
DLT-TMPLS-TD CONF Y
DLT-TMPLS-TUNNEL CONF Y
DLT-TMPLS-TUSEG CONF Y
DLT-USER-SECU SEC Y
DLT-VCG CONF Y
DLT-<AUN> CONF Y
DLT-<STMN> CONF Y
DLT-<TUN> CONF Y
ED-ASAP-PROF CONF Y
ED-BITS-OUT NETADMIN Y
ED-BITS NETADMIN Y
ED-CMD-SECU SEC Y
ED-CP-COM CONF Y
DLT-CP-OSPFIF CONF Y
ED-CP-TPORT CONF Y
ED-CPTMPLS-HOPLIST CONF Y
ED-CRS-<RATE> CONF Y
ED-CRSPROT-<RATE> CONF Y
ED-DAT CONF Y
ED-EQPT CONF Y
ED-FFP-<STMN> CONF Y
ED-FFP-TMPLS CONF Y
ED-GBE CONF Y
ED-GBE10 CONF Y
ED-IP-ADDR NETADMIN Y
Release 5.1 (ETSI)

September 2017

ED-L2ENCAP-PROF CONF Y
ED-LAC-STATE CONF Y
ED-LAN NETADMIN Y
ED-MAP NETADMIN Y
ED-MAU CONF Y
ED-MGRACD CONF Y
ED-MGRLIST CONF Y
ED-NE-DSCV NETADMIN Y
ED-NE-TL1 NETADMIN Y
ED-NETIF NETADMIN Y
ED-NTP NETADMIN Y
ED-OAMPHB-PROF CONF Y
ED-ODU2 CONF Y
ED-OG CONF Y
ED-OSADDRS NETADMIN Y
ED-OSIAREA NETADMIN Y
ED-OTU2 CONF Y
ED-PHB-PROF CONF Y
ED-PID READ Y
ED-PROT-DCC NETADMIN Y
ED-PTF CONF Y
ED-RINGMAP NETADMIN Y
ED-SQLMAP NETADMIN Y
ED-SYNCN NETADMIN Y
ED-SYNCN-OUT NETADMIN Y
ED-TH-PROF CONF Y
ED-TMPLS-CPGLOBAL CONF Y
ED-TMPLS-CRSPWSEG CONF Y
ED-TMPLS-CRSTUSEG CONF Y
Release 5.1 (ETSI)

September 2017

ED-TMPLS-GLOBAL CONF Y
ED-TMPLS-PW CONF Y
ED-TMPLS-PWSEG CONF Y
ED-TMPLS-TD CONF Y
ED-TMPLS-TUNNEL CONF Y
ED-TMPLS-TUSEG CONF Y
ED-ULCOMPMR NETADMIN Y
ED-USER-SECU SEC Y
ED-VCG CONF Y
ENT-ASAP-PROF CONF Y
ENT-CP-COM CONF Y
ENT-CP-RT CONF Y
ENT-CP-TPORT CONF Y
ENT-CPTMPLS-HOPLIST CONF Y
ENT-CRS-<RATE> CONF Y
ENT-CRSPROT-<RATE> CONF Y
ENT-EQPT CONF Y
ENT-FFP-<STMN> CONF Y
ENT-FFP-TMPLS CONF Y
ENT-GBE10 CONF Y
ENT-L2ENCAP-PROF CONF Y
ENT-NE-IPRT NETADMIN Y
ENT-NE-IPT NETADMIN Y
ENT-NETIF NETADMIN Y
ENT-NTP-ADDR NETADMIN Y
ENT-OAMPHB-PROF CONF Y
ENT-OTU2 CONF Y
ENT-OVHCCRS CONF Y
ENT-PHB-PROF CONF Y
Release 5.1 (ETSI)

September 2017

ENT-TH-PROF CONF Y
ENT-TMPLS-CRSPWSEG CONF Y
ENT-TMPLS-CRSTUSEG CONF Y
ENT-TMPLS-PWSEG CONF Y
ENT-TMPLS-TD CONF Y
ENT-TMPLS-TUNNEL CONF Y
ENT-TMPLS-TUSEG CONF Y
ENT-USER-SECU SEC Y
ENT-VCG CONF Y
INH-SWTOPROTN-EQPT CONF Y
INH-USER-SECU SEC Y
INIT-REG-<SDH/SONET FACILITY> CONF Y
INIT-REG-GBE CONF Y
INIT-REG-GBE10 CONF Y
INIT-REG-MAU CONF Y
INIT-REG-ODU2 CONF Y
INIT-REG-OTU2 CONF Y
INIT-SYS NETADMIN Y
INIT-SYS-NEW NETADMIN Y
INIT-SYS-OLD NETADMIN Y
INIT-TMPLSPM-PWSEG CONF Y
INIT-TMPLSPM-TUSEG CONF Y
MON-LCAS READ N
OPR-ACO-COM CONF Y
OPR-LPBK-<STMN> CONF N
OPR-LPBK-GBE CONF N
OPR-LPBK-MAU CONF N
OPR-PROTNSW-<RATE> CONF N
OPR-PROTNSW-<STMN> CONF N
Release 5.1 (ETSI)

September 2017

OPR-PROTNSW-TMPLS CONF N
OPR-SCRIPT CONF Y
OPR-SYNCNSW NETADMIN Y
OPR-SYNCNSW-OUT NETADMIN Y
RD-SYNCN READ N
RESTORE-DB NETADMIN Y
RLS-CP-RSRCS CONF Y
RLS-LPBK-<STMN> CONF N
RLS-LPBK-GBE CONF N
RLS-LPBK-MAU CONF N
RLS-PROTNSW-<RATE> CONF N
RLS-PROTNSW-<STMN> CONF N
RLS-PROTNSW-TMPLS CONF N
RLS-SYNCNSW NETADMIN Y
RLS-SYNCNSW-OUT NETADMIN Y
RMV-EQPT CONF Y
RMV-ISU-OLD NETADMIN Y
RST-EQPT CONF Y
RTRV-<AUN> READ N
RTRV-<STMNN> READ N
RTRV-<TUN> READ N
RTRV-ALLOWED READ N
RTRV-ALM-<LOVCN> READ N
RTRV-ALM-<STMN> READ N
RTRV-ALM-<VCN> READ N
RTRV-ALM-ALL READ N
RTRV-ALM-BITS READ N
RTRV-ALM-EQPT READ N
RTRV-ALM-GBE READ N
Release 5.1 (ETSI)

September 2017

RTRV-ALM-GBE10 READ N
RTRV-ALM-MAU READ N
RTRV-ALM-ODU2 READ N
RTRV-ALM-OGPORT READ N
RTRV-ALM-OTU2 READ N
RTRV-ALM-TIMING READ N
RTRV-ALM-TUSEG READ N
RTRV-ALM-VCG READ N
RTRV-ARPCACHE READ N
RTRV-ASAP-PROF READ N
RTRV-ATTR-SECULOG READ N
RTRV-AUDIT-SECULOG SEC Y
RTRV-BITS READ N
RTRV-BITS-OUT READ N
RTRV-CHAN-BLSR READ N
RTRV-CKTID READ N
RTRV-CMD-SECU READ N
RTRV-COND-<LOVCN> READ N
RTRV-COND-<STMN> READ N
RTRV-COND-<VCN> READ N
RTRV-COND-ALL READ N
RTRV-COND-BITS READ N
RTRV-COND-EQPT READ N
RTRV-COND-FFP READ N
RTRV-COND-GBE READ N
RTRV-COND-GBE10 READ N
RTRV-COND-LOG READ N
RTRV-COND-MAU READ N
RTRV-COND-ODU2 READ N
Release 5.1 (ETSI)

September 2017

RTRV-COND-OGPORT READ N
RTRV-COND-OTU2 READ N
RTRV-COND-TIMING READ N
RTRV-COND-TUSEG READ N
RTRV-COND-VCG READ N
RTRV-CP-COM READ N
RTRV-CP-OSPFAREA READ N
RTRV-CP-OSPFDB READ N
RTRV-CP-OSPFIF READ N
RTRV-CP-OSPFNEIGHBOR READ N
RTRV-CP-RT READ N
RTRV-CP-TPORT READ N
RTRV-CPTMPLS-HOPLIST READ N
RTRV-CRS READ N
RTRV-CRS-<RATE> READ N
RTRV-CRSPROT READ N
RTRV-CRSPROT-<RATE> READ N
RTRV-DB-LABEL READ N
RTRV-DBMOD READ N
RTRV-DDM READ N
RTRV-DFLT-SECU READ N
RTRV-DOSM-RSRC READ N
RTRV-DX-EQPT READ N
RTRV-EQPT READ N
RTRV-FFP-<STMN> READ N
RTRV-FFP-ALL READ N
RTRV-FFP-TMPLS READ N
RTRV-FSVDATA READ N
RTRV-GBE READ N
Release 5.1 (ETSI)

September 2017

RTRV-GBE10 READ N
RTRV-HDR READ N
RTRV-IP-ADDR READ N
RTRV-ISU-STATUS READ N
RTRV-L2ENCAP-PROF READ N
RTRV-LAC-DFLT READ N
RTRV-LAC-STATE READ N
RTRV-LAN READ N
RTRV--LNKMTX-STATUS READ N
RTRV--LOPOOL READ N
RTRV-LPBK-<STMN> READ N
RTRV-LPBK-GBE READ N
RTRV-LPBK-MAU READ N
RTRV-MAU READ N
RTRV-MGRACD READ N
RTRV-MGRLIST READ N
RTRV-MPLSIF READ N
RTRV-NE-DSCV READ N
RTRV-NE-IPRT READ N
RTRV-NE-IPT READ N
RTRV-NE-TL1 READ N
RTRV-NETIF READ N
RTRV-NSAP READ N
RTRV-NTP READ N
RTRV-NTP-ADDR READ N
RTRV-OAMPHB-PROF READ N
RTRV-ODU2 READ N
RTRV-OG READ N
RTRV-OSADDRS READ N
Release 5.1 (ETSI)

September 2017

RTRV-OSIAREA READ N
RTRV-OTU2 READ N
RTRV-OVHCCRS READ N
RTRV-PATHSL READ N
RTRV-PATHTRC READ N
RTRV-PHB-PROF READ N
RTRV-PM-<SDHFACILITY> READ N
RTRV-PM-GBE READ N
RTRV-PM-GBE10 READ N
RTRV-PM-MAU READ N
RTRV-PM-ODU2 READ N
RTRV-PM-OTU2 READ N
RTRV-PMGLB-STATUS READ N
RTRV-PMMODE-<SDH/SONET FACILITY> READ N
RTRV-PMMODE-GBE READ N
RTRV-PMMODE-GBE10 READ N
RTRV-PMMODE-MAU READ N
RTRV-PMMODE-ODU2 READ N
RTRV-PMMODE-OTU2 READ N
RTRV-PRMTR-NE READ N
RTRV-PROF READ N
RTRV-PTF READ N
RTRV-RFILE READ N
RTRV-RI READ N
RTRV-RINGMAP READ N
RTRV-SECTRC READ N
RTRV-SQLMAP READ N
RTRV-STATUS READ N
RTRV-SYNCN READ N
Release 5.1 (ETSI)

September 2017

RTRV-SYNCN-MSG READ N
RTRV-SYNCN-OUT READ N
RTRV-TCAP-ASGNMT READ N
RTRV-TH-PROF READ N
RTRV-TL1-SYNTAX READ N
RTRV-TMPLS-CPGLOBAL READ N
RTRV-TMPLS-CRSPWSEG READ N
RTRV-TMPLS-CRSTUSEG READ N
RTRV-TMPLS-GLOBAL READ N
RTRV-TMPLS-PW READ N
RTRV-TMPLS-PWSEG READ N
RTRV-TMPLS-TD READ N
RTRV-TMPLS-TUNNEL READ N
RTRV-TMPLS-TUSEG READ N
RTRV-TMPLSPM-PWSEG READ N
RTRV-TMPLSPM-TUSEG READ N
RTRV-ULCOMPMR READ N
RTRV-USER READ N
RTRV-USER-SECU READ N
RTRV-VCG READ N
SET-ATTR-SECUDFLT SEC Y
SET-ATTR-SECULOG SEC Y
SET-LAC-DFLT CONF Y
SET-PMMODE-<SDHFACILITY> CONF Y
SET-PMMODE-GBE CONF Y
SET-PMMODE-GBE10 CONF Y
SET-PMMODE-MAU CONF Y
SET-PMMODE-ODU2 CONF Y
SET-PMMODE-OTU2 CONF Y
Release 5.1 (ETSI)

September 2017

SET-PRMTR-NE CONF Y
SET-SID CONF Y
SET-TMPLSPM-PWSEG CONF Y
SET-TMPLSPM-TUSEG CONF Y
STA-ISU NETADMIN Y
STA-PMGLB PROV Y
STP-ISU NETADMIN Y
SW-DX-EQPT CONF Y
SW-TOPROTN-EQPT CONF Y
SW-TOWKG-EQPT CONF Y
Release 5.1 (ETSI)

September 2017
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Equipment Entities
B Equipment Entities
B.1 Equipment provisionable

B.1.1 List
Equipment entity should be provisioned as one of the following:

• protection EC320
• 10GSO (OC-192/STM-64) card
• 10GSO (OC-192/STM-64) Evolution card
• 2.5G (OC-48/STM-16) module
• 8 Port (OC-3/STM-1)/(OC-12/STM-4) Card
• 8 Port Multirate 8xSTM1/4 - 4xSTM16 Card
• 63 E1 Port Card
• 63 E1 Protection Card • G.709 OTU 10GB Card (OT2TDM)
• G.709 OTU 10GB Card with XFP
• 10XANY 10GB 10xGBE/Sonet Card
• MultiService Adaptation Card for ATM (Packet Module 10G - ETSI only)
• Universal GateWay UGW Adaptation Card (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)
• CWDM OADM 1ch w/o OSC coupler • CWDM OADM 1ch w OSC coupler
Release 5.1 (ETSI)

September 2017
Equipment provisionable 1850 TSS-320/TSS-320H/TSS-160

• SFP on 8XSO
• FE 100BASE-BX20 (Upstream and Downstream)
• OC-48/STM-16 2km BiDi (Upstream and Downstream) Shelf Types
• UNVRSL160C (19” 160 type shelf)
• PDHACCSSHLF (Drop Shelf for E1 collecting)
• PDHACCSSHLF120 (Drop Shelf for E1 120ohm balanced collecting)
An equipment entity that has not been provisioned has a PST,SST values of OOS-MA,UAS if still
plugged in or OOS-AUMA, UAS&UEQ if it isn't still plugged in.
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.
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Card vs Allowed SFP/XFP ProvisionedType
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.
Before that can occur

• mandatory equipment entities: an EC320 and dual MT320, MT160, FAN, POW320, TBUS
modules - must be in the shelf that will be the Main Shelf
• The shelf equipment hardware preset on this shelf must be set so as to indicate that the shelf is
the Main Shelf.
B.2 Card vs Allowed SFP/XFP ProvisionedType

B.2.1 SFPs and the XFPs ProvisionedType
Table 55 SFPs and the XFPs ProvisionedType allowed per IOC Card
IOC CLIENT SIDE LINESIDE

CLNT- TYPE ALLOWED TYPE ALLOWED SFP/XFP PROVISIONED-
SEL SFP/XFP TYPE
PROVISIONED-
TYPE
PP1GE N.A NGI N.A. 10- Colored: SS162C SL162C
SFP Any data: ANY-DATAS
Electrical: ETHEMR (only 1000MB)
OptFastEth: 100FXETH
Bidir: 100BX-20 (U/D)
1000BX-20 (U/D)
1000BX-40 (U/D)
PP20x1GE N.A. NGI N.A 20- Colored: SS162C SL162C
Electrical: ETHEMR (only 1000MB;
Synch not supported)
Bidir:
100BX-20 (U/D)
1000BX-20 (U/D)
1000BX-40 (U/D)
Release 5.1 (ETSI)

September 2017
Card vs Allowed SFP/XFP ProvisionedType 1850 TSS-320/TSS-320H/TSS-160
Table 55 SFPs and the XFPs ProvisionedType allowed per IOC Card (continued)

SEL SFP/XFP TYPE
PROVISIONED-
TYPE
PP1GESY N.A. NGI N.A. 10- Colored: SS162C SL162C
Electrical: ETHEMR (only 1000MB;
Synch not supported)
Bidir: 100BX-20 (U/D)
1000BX-20 (U/D)
1000BX-40 (U/D)
PP10GE N.A. NGI N.A. 1-XFP Colored: XL-642C
Any data: ANY-DATAX
PP2x10G E N.A. NGI N.A. 2-XFP Colored: XL-642C
Any data: ANY-DATAX
1P10GSO N.A. NGI N.A. 1-XFP Black&White XI-641 XI-642 XI-643
and XI-645 XS-641 XS-642 XS-643 XS-645
1P10GSO XL-641 XL-643 XV-642 XV-643
E XP1L12D2
Colored: XL-642C
Any TDM: ANY-OM10G
4P2G5SO N.A. NGI N.A. 4-SFP Black&White SS-161AR SI-161 SS-161
SS-162 SL-161 SL-162
Colored: SS162C SL162C
Any TDM: ANY-OM2G5
Bidir: SI-16D SI-16U SS-16D SS-16U
SL-16D SL-16U
8PSO N.A. NGI N.A. 8-SFP Black&White: SI-11 SS-11 SL-11 SL-12
SS-41 SL-41 SL-42
Any TDM: ANY-OM155 ANY-OM622
Bidir: 100BX-20 (U/D) 1000BX-20 (U/D)
1000BX-40 (U/D)
MTSYNT N.A. To be N.A. 2-SFP Black&White: SS-41
H4 (*) added
Release 5.1 (ETSI)

September 2017

SEL SFP/XFP TYPE
PROVISIONED-
TYPE
MRSOE N.A. NGI N.A. 4/8- Black&White: SI-11 SS-11 SL-11 SL-12
SFP SS-41 SL-41 SL-42 SS-161AR SI-161
SS-161 SS-162 SL-161 SL-162
Colored: SS162C SL162C
ANY-OM2G5
Bidir: 100BX-20 (U/D) 1000BX-20 (U/D)
1000BX-40 (U/D) SI-16D SI-16U SS-16D
SS-16U SL-16D SL-16U
10XANY N.A. NGI N.A. 10- Black&White: SL-12 SS-41 SL-41 SL-42
SFP SS-161AR SI-161 SS-161 SS-162
SL-161 SL-162 Colored: SS162C
SL162C
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
Bidir: SI-16D SI-16U
SS-16D SS-16U SL-16D SL-16U
100BX-20 (U/D) 1000BX-20 (U/D)
1000BX-40 (U/D)
OT2TDM N.A. NGI N.A. 1-TUNABLambda Value
LE
MSA
OT2TDM N.A. NGI N.A. 1-XFP Colored: XL-642C
XB
Release 5.1 (ETSI)

September 2017

SEL SFP/XFP TYPE
PROVISIONED-
TYPE
DWLA10X [ET- 1-XFP Black&White: 1-XFP Colored: XL-642C
SI]STM XI-641 XI-642
64 XI-643 XI-645
OTU2 XS-641 XS-642
10GBE XS-643 XS-645
XL-641 XL-643
XV-642 XV-643
XP1L12D2
Colored: XL-642C
Any TDM:
ANY-OM10G Any
data: ANY-DATAX
(*) (*): Only for
CLNTSEL=
[]10GBE.
CWLA3(O [ET- 2-SFP Black&White: 2-SFP Colored: SS162C SL162C
P) SI]STM SS-161AR SI-161
16 SS-161 SS-162
SL-161 SL-162
Colored: SS162C
SL162C
Any TDM:
ANY-OM2G5
Bidir: SI-16D
SI-16U SS-16D
SS-16U SL-16D
SL-16U
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
B.2.2 Any-xx ProvisionedType vs ActualType

The table below specifies the ANY-xx ProvisionedTypes of the SFP/XFP for not having any
mismatch with the physically plugged one:
Release 5.1 (ETSI)

September 2017
Release 5.1 (ETSI)

September 2017
B.2.3 1850 TSS-160 Supported Modules
Table 56 1850 TSS-160 Supported Modules
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.
Release 5.1 (ETSI)

September 2017
Figure 37 1850 TSS-160 Shelf 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
Quad area (ROADM)
B.2.4 1850 TSS-320 Supported Modules
Table 57 1850 TSS-320 Supported Modules
REQUIRED/
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
Release 5.1 (ETSI)

September 2017
Table 57 1850 TSS-320 Supported Modules (continued)
REQUIRED/
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
0/16 02 to 09 - 12 to 19
Adaptation Card Packet
PP10AD F
Modules 10G
Release 5.1 (ETSI)

September 2017
Table 57 1850 TSS-320 Supported Modules (continued)
REQUIRED/
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.
Release 5.1 (ETSI)

September 2017
Figure 38 1850 TSS-320 Shelf Slot Locations
Access Shelf Interconnection Panel
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
Quad area (ROADM)
Table 58 Supported SFP/XFP Optics Modules - Line Side
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
Release 5.1 (ETSI)

September 2017
Table 58 Supported SFP/XFP Optics Modules - Line Side (continued)
LINE Side
Unit
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
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
OT2TDM 1-TUNABLE MSA Lambda Value
DWLA10X 1-XFP Colored: XL-642C
CWLA3(OP) 2-SFP Colored: SS162C, SL162C
Release 5.1 (ETSI)

September 2017
AIDs 1850 TSS-320/TSS-320H/TSS-160
Table 59 Supported SFP/XFP Optics Modules - Client Side
CLIENT Side
Unit
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
Any TDM: ANY-OM2G5
B.3 AIDs
B.3.1
Below the AIDs value and their description:

• SHELF-{1-7}-{1-9} (Shelf)
• EC320-{1-7}-{1-9}-{20} (Equipment Controller Card -Secondary-Protecting TSS-320)
• E1M-{1-7}-{2}-{7-14} ETSI (63 E1 Multiplexer Card)
• E1ACC-{1-7}-{2}-{3-5,16-18} ETSI (63 E1 Access Card)
• E1PR-{1-7}-{2}-{2,19} ETSI (63 E1 EPS Card)
• 10GSO-{1-7}-{1-9}-{2-9,12-19,21-36} (10G Synchronous Optical)
• 2G5SO-{1-7}-{1-9}-{2-9,12-19,21-36} (2.5G Synchronous Optical)
• 8XSO-{1-7}-{1-9}-{2-9,12-19,21-36} (8 x Synchronous Optical)
• MRSOE-{1-7}-{1-9}-{2-9,12-19,21-36} (8xSTM1/4 - 4xSTM16 Synchronous Optical)
• OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} (G.709 OTU 10GB Card - Provisioned Type = 1POTU2)
• OT2TDMXB-{1-7}-{1-9}-{2-9,12-19,21-3 6} (G.709 OTU 10GB Card - XFP Based)
• 10XANY-{1-7}-{1-9}-{2-9,12-19,21-36} (10XANY Card)
• XFP-{1-7}-{1-9}-{2-9,12-19,21-36}-1 (XFP on 10GSO modules)
• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4} (SFP on 2G5SO or on CWLA modules)
• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} (SFP on 8XSO modules)
• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10 } (SFP on 10XANY modules)
• LOA10G-{1-7}-{1-9}-{21,22,24,33,35,36 } (Lower Order Adaptation Card with EPS)
• PRE-{1-7}-{1-9}-{2-9,12-19,21-36} (Preamplifier)
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Provisioned Types
• 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)
• 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)
B.4 Provisioned Types

B.4.1
The 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).
Below the list of all the Proviosioned types and their description:
• UNVRSL320 Shelf 320 Type In-Service
• UNVRSL160 Generic 160 type Shelf
• UNVRSL160C 19” 160 type shelf
• PDHACCSSHLF ETSI 1662-based drop shelf
• PDHACCSSHLF120 ETSI 1662-based 120ohm-E1 drop shelf
• EC320 Equipment Controller
• 1P10GSO 10G Synchronous Optical
• 1P10GSOE 10G Synchronous Optical Evolution
• 4P2G5SO 4x2.5G Synchronous Optical
• 8PSO 8 x Synchronous Optical
Release 5.1 (ETSI)

September 2017
Provisioned Types 1850 TSS-320/TSS-320H/TSS-160
• MRSOE SDX/SONET Multirate Card

• P63E1 ETSI 63 x E1 Port Module
• A63E1A ETSI 63 x E1 Access Module 75ohm unb
• A63E1B ETSI 63 x E1 Access Module 120ohm bal
• LSPROT ETSI 63 x E1 Access Protection Module
• 1POTU2 G.709 OTU 10GB Card
• 1POTU2XB G.709 OTU 10GB Card - XFP based
• 10XANY 10GB 10 x GBE/Sonet
• 1000BX-20D 1000BASE-BX20 / OC-12 -STM-4 15km BiDi - Downstream
• 1000BX-20U 1000BASE-BX20 / OC-12 -STM-4 15km BiDi - Downstream
• 1000BX-40D 1000BASE-BX20 / OC-12 -STM-4 15km BiDi - Downstream
• 1000BX-40U 1000BASE-BX20 / OC-12 -STM-4 15km BiDi - Downstream
• 100BX-20D FE 100BASE-BX20 / OC-3 -STM-1 15km BiDi - Downstream
• 100BX-20U FE 100BASE-BX20 / OC-3 -STM-1 15km BiDi - Upstream
• SI-16D Intraoffice OC-48/STM-16 2km BiDi-Downstream
• SI-16U Intraoffice OC-48/STM-16 2km BiDi-Upstream
• SS-16D Short Haul OC-48/STM-16 15km BiDi-Downstream
• SS-16U Short Haul OC-48/STM-16 15km BiDi-Upstream
• SL-16D Long Haul OC-48/STM-16 40km BiDi-Downstream
• SL-16U Long Haul OC-48/STM-16 40km BiDi-Upstream
• SI-11 Intraoffice STM-1 (wl1310) B&W for STM-1 port
• SS-11 Short Haul STM-1 (wl1310) B&W for STM-1port
• SL-11 Long Haul STM-1 (wl1310) B&W for STM-1 port
• SS-41 Short Haul STM-4 (wl1310) B&W for STM-4 port
• SS-161AR Short Haul STM-16 (wl1310) B&W AnyRate (Max Rate STM-16) port
• SI-161 Intraoffice STM-16 (wl1310) B&W for STM-16 port
• SS-161 Short Haul STM-16 (wl1310) B&W for STM-16 port
• SS-162 Short Haul STM-16 (wl1550)B&W for STM-16 port
• XI-641 Intraoffice STM-64 (wl1310) B&W for STM-64 port
• XI-642 Intraoffice STM-64 (wl1550) B&W for STM-64 port
• XI-643 Intraoffice STM-64 (3) B&W for STM-64 port
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Provisioned Types
• XI-645 Intraoffice STM-64 (5) B&W for STM-64 port

• XS-641 Short Haul STM-64 (wl1310) B&W for STM-64 port
• XS-642 Short Haul STM-64 (wl1550) B&W for STM-64 port
• XS-643 Short Haul STM-64 (3) B&W for STM-64 port
• XS-645 Short Haul STM-64 (5) B&W for STM-64 port
• XL-641 Long Haul STM-64 (wl1310) B&W for STM-64 port
• XP1L12D2 XFP G.959.1 Long Haul (wl1550) STM-64/OC-192 (5) B&W
• LOA10G Lower Order Adpatation Card 10G
• PRE10G Optical Pre-Amplifer 10G
• BOOST10G Optical Booster 10G
• LOFA1111 Line Optical Filter and Attenuator
• DWLA10X DWDM Optical Transponder with Colored XFPs
• CWLA3 CWDM Optical Transponder (2.5G) without Optical Protection
• CWLA3OP CWDM Optical Transponder (2.5G) with Optical Protection
• CADM4 CWDM OADM 4ch w/o OSC coupler
• CADM4S CWDM OADM 4ch w OSC coupler
• CMDX8 CWDM Mux/Demux 8ch w/o OSC coupler
• CMDX8S CWDM Mux/Demux 8ch with OSC coupler
• OMDX8100 DWDM Mux/Demux 8 channels L1 & L2 band without S-band input/output
• PP10MS MultiService Adaptation Card (Packet Module 10G)
• PP10GATM ETSI MultiService Adaptation Card for ATM (Packet Module 10G)
• PP2G5UGW ETSI UGW Adaptation Card - Packet Module 2.5G
• PP1GE Packet Module 10x1GbEthernet (Packet Module 10G)
• PP1GEX20 Packet Module 20x1GbEthernet (Packet Module 20G)
• PP1GESY Packet Module 10x1GbEthernet with Synchronization (Packet Module 10G)
• PP10AD Adaptation Card Packet Modules 10G
• PP10GEX2 Packet Module 2x10Gb (Packet Module 20G)
• PP10GESY Packet Module 1x10GbEthernet with Synchronization (Packet Module 10G)
• ETHEMR Electrical SFP 10/100/1000
• 100FXETH 100FX SFP
• 100B-LX SFP 100B LX 10km
Release 5.1 (ETSI)

September 2017
Provisioned Types 1850 TSS-320/TSS-320H/TSS-160
• SS162C CWDM SFP STM-16/OC-48 Short haul

• SL162C CWDM SFP STM-16/OC-48 Long haul
• SL-162CD DWDM SFP STM-16/OC-48 1GBE Long haul
• XL-642C DWDM/CWDM XFP STM-64/OC-192 Long haul
• XL-643 Long Haul STM-64 (3) B&W for STM-64 port
• XV-642 Very Long Haul STM-64(2) B&W for STM-64 port
• XV-643 Very Long Haul STM-64(3)B&W for STM-64 port
• ANY-OM155 Generic MSA SFP module (OC3/STM1 case)
• ANY-OM622 Generic MSA SFP module (OC12/STM4 case)
• ANY-OM2G5 Generic MSA SFP module (OC48/STM16 case)
• ANY-OM10G Generic MSA XFP module (OC192/STM64 case)
• ANY-DATAS Generic MSA SFP module (Ethernet GBE case)
• COLOUR-DATAS Generic Colored MSA SFP module (Ethernet GBE case)
• ANY-DATAX Generic MSA XFP module (Ethernet 10GBE case)
• COLOUR-DATAX Generic Colored MSA XFP module (Ethernet 10GBE case)
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160 Glossary
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
Release 5.1 (ETSI)

September 2017
Glossary 1850 TSS-320/TSS-320H/TSS-160
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.).
Release 5.1 (ETSI)

September 2017
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.
Release 5.1 (ETSI)

September 2017
CVFE (Coding Violation Far-End)

An indication returned to the transmitting terminal that an errored block has been detected at the
receiving terminal.
CWDM
Coarse Wavelength Division Multiplexing
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.
Release 5.1 (ETSI)

September 2017
Drop and Continue

A technique that allows redundant signal appearances at two central offices in a DRI network, allowing
protection against central office failures.
DT
Distant Terminal
DTE
Data Terminating Equipment
DTE (Data Terminating Equipment)
That part of a data station that serves as a data source (originates data for transmission), a data sink
(accepts transmitted data), or both.
DWDM
Dense Wavelength Division Multiplexing
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
Release 5.1 (ETSI)

September 2017
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.
Release 5.1 (ETSI)

September 2017
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).
Release 5.1 (ETSI)

September 2017
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
Release 5.1 (ETSI)

September 2017
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.
Release 5.1 (ETSI)

September 2017
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
Release 5.1 (ETSI)

September 2017
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
Release 5.1 (ETSI)

September 2017
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
Release 5.1 (ETSI)

September 2017
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
Release 5.1 (ETSI)

September 2017
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
Release 5.1 (ETSI)

September 2017
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.
Release 5.1 (ETSI)

September 2017
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
Release 5.1 (ETSI)

September 2017
ZIC
Zero Installation Craft terminal
Release 5.1 (ETSI)

September 2017
1850 TSS-320/TSS-320H/TSS-160
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
Release 5.1 (ETSI)

September 2017

Nokia 8DG09603CAAATQZZA Issue 4 PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Nokia 8DG09603CAAATQZZA Issue 4 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

1850 Transport Service Switch

(TSS-320, TSS-320H and TSS-

TL1 User Provisioning Guide

Release 5.1 (ETSI)

About this document..........................................................................................................................................21

1 Line Command User's Interface Introduction ...........................................................................................29

3 Task Index List (IXL) ....................................................................................................................................57

Release 5.1 (ETSI)

3.20 IXL-19: Enhanced Shelf Equipment Functions .................................................................................66

4 Nontrouble Procedure (NTP).......................................................................................................................67

5 Control Plane Functions............................................................................................................................107

Release 5.1 (ETSI)

5.5 Administer Control Plane - Tranport Port ........................................................................................119

6 Detailed Level Procedure ..........................................................................................................................135

Release 5.1 (ETSI)

6.32 Administer STM-n Facility Protection Group ...................................................................................237

Release 5.1 (ETSI)

6.69 Remove/Restore Equipment ...........................................................................................................393

7 S320H Shelf Detailed Level Procedure ....................................................................................................451

8 TMPLS/MPLS-TP Detailed Level Procedure ............................................................................................463

Release 5.1 (ETSI)

8.11 Administer T-MPLS Pseudo Wire....................................................................................................510

9 1662 Drop Shelf Detailed Level Procedure ..............................................................................................555

Release 5.1 (ETSI)

10.14 LAG Management ..........................................................................................................................602

A Software Reference Guide.........................................................................................................................611

Release 5.1 (ETSI)

Release 5.1 (ETSI)

Table 32 CCT usage rules depending on TUSegment DIR parameter ...........................................................535

Release 5.1 (ETSI)

Release 5.1 (ETSI)

Figure 32 MEP/MIP configuration for loopback connectivity verification..........................................................472

Release 5.1 (ETSI)

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.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.23 PW Termination Management (Case of VPLS) .......................................................................................97

4.25 VCG Deprovisioning ..............................................................................................................................100

Release 5.1 (ETSI)

4.26 VCG Provisioning ..................................................................................................................................100

4.27 VPLS Deprovisioning.............................................................................................................................102

4.28 VPLS Provisioning .................................................................................................................................102

4.29 UGW Protection Provisioning ................................................................................................................104

5.2 Administer T-MPLS Control Plane Global Parameters ..........................................................................110

5.3 Administer Control Plane - Control Routing Port....................................................................................111

5.4 Administer Control Plane - IP Route ......................................................................................................115