tl1 user provisioning guide transport service switch (tss-320, tss-320h and tss-160) release 5.1...

714
1850 Transport Service Switch (TSS-320, TSS-320H and TSS- 160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Upload: lamnga

Post on 05-Apr-2018

256 views

Category:

Documents


7 download

TRANSCRIPT

Page 1: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

1850 Transport Service Switch(TSS-320, TSS-320H and TSS-160)Release 5.1 (ETSI)

TL1 User Provisioning Guide

8DG09603CAAATQZZA

Issue 4

September 2017

Page 2: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Legal notice

Nokia is a registered trademark of Nokia Corporation. Other products and company names mentioned herein may be trademarks ortradenames 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 accessfeatures. In such an event, applicable tariffs require that the customer pay all network charges for traffic. Nokia cannot be responsible forsuch 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.

1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

2 Issue 4

Page 3: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

Release 5.1 (ETSI)September 2017Issue 4 38DG09603CAAATQZZA

Page 4: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

4 Issue 4

Page 5: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

Release 5.1 (ETSI)September 2017Issue 4 58DG09603CAAATQZZA

Page 6: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

6 Issue 4

Page 7: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

Release 5.1 (ETSI)September 2017Issue 4 78DG09603CAAATQZZA

Page 8: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

8 Issue 4

Page 9: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

Release 5.1 (ETSI)September 2017Issue 4 98DG09603CAAATQZZA

Page 10: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

List of tablesTable 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

1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

10 Issue 4

Page 11: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

Release 5.1 (ETSI)September 2017Issue 4 118DG09603CAAATQZZA

Page 12: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

List of figuresFigure 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

1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

12 Issue 4

Page 13: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

Release 5.1 (ETSI)September 2017Issue 4 138DG09603CAAATQZZA

Page 14: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

14 Issue 4

Page 15: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

Release 5.1 (ETSI)September 2017Issue 4 158DG09603CAAATQZZA

Page 16: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

16 Issue 4

Page 17: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

Release 5.1 (ETSI)September 2017Issue 4 178DG09603CAAATQZZA

Page 18: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

18 Issue 4

Page 19: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

Release 5.1 (ETSI)September 2017Issue 4 198DG09603CAAATQZZA

Page 20: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

20 Issue 4

Page 21: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

About this document

Purpose

This document provides the information and procedures necessary to install, self-test and turn upthe 1850 Transport Service Switch TSS-320, TSS-320H and TSS-160 (1850 TSS-320, TSS-320Hand TSS-160) system.

What's new

This is Issue 4 of the 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release5.1 TL1 User Provisioning Guide.

Document history is captured in the following table:

Issue Date Reason

4 September 2017 Rebranding.

3 June 2015The command to modify equipment is added with newAID'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 anindependent description. This ensures that readers can inform themselves according to their specialneeds. Before you start reading the manual, it is therefore necessary to assess which aspects orchapters will cover the individual area of interest.

1850 TSS-320/TSS-320H/TSS-160

Release 5.1 (ETSI)September 2017Issue 4 218DG09603CAAATQZZA

Page 22: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 1 Chapter contents

Chapter Description

“About this document” Defines and explains the following:

• describes the guide's purpose, intendedaudience, and organization

• lists related documentation

• explains how to comment on this document

Chapter 1, “Line Command User's InterfaceIntroduction”

This chapter provides an overview todocument and describes the writingconventions used.

Chapter 2, “Getting started” This chapter contains a procedure to initiate aTL1 or CLI session.

Chapter 3, “Task Index List (IXL)” This chapter provides IXLs group proceduresby function. Each IXL lists proceduresalphabetically by name and refers the user tothe appropriate procedure number.

Chapter 4, “Nontrouble Procedure (NTP)” This chapter lists the major steps required tocomplete a task. This list may be all anexperienced user requires. For aninexperienced user, each step refers to a DLP.The steps must be performed in the orderlisted.

Chapter 5, “Control Plane Functions” This chapter contain detailed steps andsupporting information required to complete atask when the Control Plane (CP) is used.

Chapter 6, “Detailed Level Procedure” The Detailed Level Procedures (DLP) containdetailed steps and supporting informationrequired to complete a task.

Chapter 7, “S320H Shelf Detailed LevelProcedure”

The system supports the provisioning andmanagement of new shelves types (“enhancedshelf”) to improve cost optimization respect tothe current available for TSS-320 and 160equipment.

Chapter 8, “ TMPLS/MPLS-TP Detailed LevelProcedure”

This chapter provides detailed procedures onTMPLS.

Chapter 9, “1662 Drop Shelf Detailed LevelProcedure”

This chapter provides information on 1662Drop shelf DLPs.

Chapter 10, “CLI Procedures” CLI procedures list the major steps required tocomplete a task.

1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

22 Issue 4

Page 23: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 1 Chapter contents (continued)

Chapter Description

Appendix A, “Software Reference Guide” This Software Reference Guide providessupplementary information to be used with the8DG09603BAAATQZZA — 1850 TransportService Switch (TSS-320, TSS-320H andTSS-160) Release 5.1 User ProvisioningGuide.

Appendix B, “Equipment Entities” This chapter describes the details onequipment 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 pointswhere risks of damage to personnel, equipment, and operation may exist. Failure to follow thedirections 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 SwitchTSS-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:

1850 TSS-320/TSS-320H/TSS-160

Release 5.1 (ETSI)September 2017Issue 4 238DG09603CAAATQZZA

Page 24: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

DANGER

Optional Content

Possibility of personal injury.

Optional Content added above. Please modify as needed.

WARNING

Optional Content

Possibility of equipment damage.

Optional Content added above. Please modify as needed.

NOTICE

Optional Content

Possibility of service interruption.

Optional Content added above. Please modify as needed.

Packaging collection and recovery requirements

Countries, states, localities, or other jurisdictions may require that systems be established for thereturn and/or collection of packaging waste from the consumer, or other end user, or from the wastestream. Additionally, reuse, recovery, and/or recycling targets for the return and/or collection of thepackaging waste may be established.

For more information regarding collection and recovery of packaging and packaging waste withinspecific jurisdictions, please contact the Nokia Field Services/Installation - Environmental Healthand 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 theEuropean Union, are collected and treated at the end of their useful life, in compliance withapplicable European Union and local legislation. They must not be disposed of as part of unsortedmunicipal waste.

The product may contain materials such as heavy metals or batteries. Appropriate disposal of suchmaterials is necessary to avoid a negative impact on the environment and human health.

1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

24 Issue 4

Page 25: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Note:In the European Union, a solid bar under the crossed-out wheeled bin indicates that the product was puton 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 usefullife, or products displaced by Nokia equipment offers.

For information regarding take-back of equipment by Nokia, or for more information regarding therequirements for recycling/disposal of product:

• Contact your Nokia account manager

• Contact Nokia Asset Recovery (mailto: [email protected]).

• Contact Nokia Global Sustainability (mailto: [email protected]).

• 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 TL1Command Builder.

Helvetica typeface indicates a faceplate or 1850 TSS-320, TSS-320H and TSS-160 labeldesignation, as in the ACTIVE LED on a circuit pack.

Courier Bold indicates a TL1 command typed in a terminal window by the user, as inact-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 of1850 Transport Service Switch TSS-320, TSS-320H and TSS-160 in most cases.

1850 TSS-320/TSS-320H/TSS-160

Release 5.1 (ETSI)September 2017Issue 4 258DG09603CAAATQZZA

Page 26: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Related information

The following documents provide additional information about the 1850 Transport Service SwitchTSS-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, hardwaresettings, 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 bymeans 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 Language1 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 andTroubleclearing 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 againstpersonal 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 linesystem.

• 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 theCommand 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, screendescriptions 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 EquipmentInstallation.

• 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 abovelisted documents.

Document support

For support in using this or any other Nokia document, contact Nokia at one of the followingtelephone numbers:

• 1-888-582-3688 (for the United States)

• 1-630-224-2485 (for all other countries)

1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

26 Issue 4

Page 27: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 NetworksOnline 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:[email protected]).

1850 TSS-320/TSS-320H/TSS-160

Release 5.1 (ETSI)September 2017Issue 4 278DG09603CAAATQZZA

Page 28: TL1 User Provisioning Guide 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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

28 Issue 4

Page 29: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 completeTL1 and CLI commands at the prompt. This user's interface is recommended only for users who arefamiliar with TL1 and CLI commands, parameters, and syntax.

Each procedure contains important introductory information that is essential to understanding andcompleting the task properly.

Procedures must be started at step 1, and steps must be performed in the order given. Failure to doso may cause unforeseen hazardous conditions.

1.1.2 Writing Conventions

Boldface characters indicate commands or parameters that must be entered or keys that must bepressed. 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 refersthe 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 userrequires. For an inexperienced user, each step refers to a DLP. The steps must be performed inthe order listed.

• Detailed Level Procedure (DLP)

DLPs contain detailed steps and supporting information required to complete a task. When aDLP is referenced from another part of the manual, perform the DLP, then return to the pointwhere the DLP was referenced.

• CLI Procedure (CLIP)

CLIPs contain detailed steps and supporting information required to complete a task. When aCLIP is referenced from another part of the manual, perform the CLIP, then return to the pointwhere the CLIP was referenced. Generally CLIP are to be used during DLPs execution.

1850 TSS-320/TSS-320H/TSS-160 Line Command User's Interface Introduction

Release 5.1 (ETSI)September 2017Issue 4 298DG09603CAAATQZZA

Page 30: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

Overview 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

30 Issue 4

Page 31: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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:

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 orinjury

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)

SAMPLELifting this equipment by yourself can result in injurydue to the size and weight of the equipment.

Always use three people or a lifting device to transportand position this equipment. [ABC123]

CAUTION

Lifting hazard

1850 TSS-320/TSS-320H/TSS-160 Structure of safety statements

Release 5.1 (ETSI)September 2017Issue 4 318DG09603CAAATQZZA

Page 32: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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, willresult in death or serious injury.

WARNING Indicates a hazardous situation which, if not avoided, could result indeath or serious injury.

CAUTION Indicates a hazardous situation which, if not avoided, could result inminor 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 elementarrangement; that is, how elements are delimited or separated using special characters andpunctuation.

For the system to understand a command entered in Direct mode, the precise command structureand 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 thataction.

• Input parameters: directs a command to the appropriate processing environment or supplies thedata required to execute the command. Parameters can be either required or optional dependingon the command.

• Special characters and punctuation: identify command elements, separate each element, andend each command.

1.3.2 Command Code

The command code contains up to three elements: a verb and one or two verb modifiers. A hyphenseparates each element of a command. Command codes are usually abbreviations of the meaningof the command.

An example of a command code is ENT-CRS-STS1. In this example, the first element, ENT, is averb 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 anequipment or circuit type). In this case, the first modifier is CRS for cross-connection, which is thetype 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 switchingenvironment. The command code, however, does not specify which circuits to connect. Inputparameters supply the additional information needed to execute the command.

TL1 Command Structure and Syntax 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

32 Issue 4

Page 33: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

1.3.3 Input Parameters

Input parameters specify conditions under which a command executes. Parameters can be eitherrequired or optional. The form screen encloses optional parameters in brackets. Three examples ofinput 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 aparameter block. Colons ( : ) separate parameter blocks. Within a block, commas ( , ) separateindividual parameters.

The cross-connect system generally uses the following parameter types; however, the parametersin 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 ofwhich must be alphabetic. It identifies the processing location for a command. When a value isnot entered, the system defaults to the uppercase Site Identifier (SID) value. When a value isentered, it must match the SID. If the entered value does not match the SID, the system deniesthe command.

• b = AID—Access Identifier. The AID identifies a facility port, removable equipment unit, or otherobject entity. Examples of parameters in this field are: From Location, To Location, and ControlPort. Some commands have multiple AID fields (FROM,TO).

• c = CTAG—Correlation Tag. The CTAG is a 1 to 6 alphanumeric block that identifies atransaction. The CTAG correlates system output messages with the commands that caused themessages. The CTAG is optional; if a CTAG is not entered, the system automatically assignsone.

• 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 orsequence in the block. Brackets indicate optional parameter values. Absence of bracketsindicates that the parameter value must be entered. If one or more parameter values is omittedfrom 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 valuesfollowing, all intervening placeholder commas must be provided to indicate that no value is beingentered for that parameter. The system assumes the default or existing parameter value foromitted optional parameter values. Parameter value combinations are verified by the systemwhether 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 parametername. A value for a keyword parameter is specified by entering the parameter name followed byan equal sign (=) followed by the parameter value. Keyword parameters may be entered in anyorder within the keyword block, but keyword parameters must be separated by a comma. Onlycommas separating each keyword parameter are required in the keyword parameter block, butthekeyword block may not begin or end with a comma. Brackets indicate optional parametersand their associated comma separators. Absence of brackets indicates that the parameter andany comma separator must be entered.

1850 TSS-320/TSS-320H/TSS-160 TL1 Command Structure and Syntax

Release 5.1 (ETSI)September 2017Issue 4 338DG09603CAAATQZZA

Page 34: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• g = State Block—The state parameter block is a positional block with parameters defined bytheir position or sequence in the block. The state block defines parameters that relate to theprimary and/or secondary state of equipment. The state block is supported only by commandsthat include the state block in the input format of a command. When supported, up to twoparameters are possible for the state block, the PST (primary state) parameter and the SST(secondary state) parameter. Brackets indicate optional parameter values. Absence of bracketsindicates that the parameter value must be entered. If the SST parameter value is omitted fromthe end of the block, the trailing comma associated with it may be omitted. However, if anoptional PST parameter value is omitted with an SST positional parameter value following, theintervening placeholder comma must be provided to indicate that no value is being entered forthe PST parameter. The system assumes the default parameter value for omitted optionalparameter values.

Keyword parameters require a parameter name assignment with each parameter value. Enterkeyword parameters in any order within a block. Positional parameters must occur in the orderspecified by the TL1 command.

In this manual, only required entries and/or parameters are given in the command string. Refer tothe 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 CommandGuide for optional parameter values.

1.3.4 Special Characters

TL1 uses characters that have special meanings depending on where the characters appear or howthey are used. Refer to table 2-A for the characters used with commands, parameters, and outputmessages.

Table 2 TL1 Special Characters

Specialcharacter

Description

< > Enclosing less-than and greater-than signs are used to enclose a descriptionof the parameter's domain when this is more understandable than an exactdefinition 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 commandecho line and in describing an output parameter's value set. The enclosingbraces are not part of the actual input command or output message.

[ ] In syntax statements, paired brackets enclose an optional commandargument; for example: [TID]. These enclosing brackets are not part of theactual input command or output message.

The following characters are entered in TL1 commands.

- Hyphen. Separates elements of TL1 command codes. Also combineselements of a compound parameter.

, Comma. Separates parameter values when multiple values exist.

TL1 Command Structure and Syntax 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

34 Issue 4

Page 35: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 2 TL1 Special Characters (continued)

Specialcharacter

Description

: Colon. Separates the command code segment from the parameters. Alsoseparates succeeding parameter blocks.

; Semicolon. Terminates a command entry and starts execution.

= Equal sign. Associates a parameter name with the assigned parameter. Aparameter must be entered in uppercase exactly as specified. A value of theparameter follows the equal sign.

& Ampersand. Groups parameter values in an input command (as list ofparameter values is generated), and combines parameter values in anoutput message.

&& Double ampersand. Represents numeric ranging in the last argument valueof a parameter (simple or compound) in an input command. It generates asequential range of parameter values, beginning with the first term specifiedthrough the last term specified.

When using the equal sign with positional parameters, the parameter must be entered in the correctposition. If this is not done, the system rejects the command.

Brackets [ ] indicate an optional parameter. Brackets are used in system documentation to indicateoptional 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 AIDvalues, 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 thelast 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 thesequential 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 thesystem as OC48STS1-1-3-2-1-2-1, OC48STS1-1-3-2-1-2-2, andOC48STS1-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 asOC48-1-3-2-1, OC48-1-3-2-3, and OC48-1-3-2-5. The range ends at the highest value lessthan or equal to the end value; OC48-1-3-2-1&&-6.++.2 is also understood asOC48-1-3-2-1, OC48-1-3-2-3, and OC48-1-3-2-5.

1850 TSS-320/TSS-320H/TSS-160 TL1 Command Structure and Syntax

Release 5.1 (ETSI)September 2017Issue 4 358DG09603CAAATQZZA

Page 36: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 portsOC3STS1-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 isnumeric. 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 willnot 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 thecommand 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 statusof 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 successfulresponse message if the command executed properly or an unsuccessful response message if thecommand failed. The system records all command transactions, successful and unsuccessful, inthe system's Audit Log.

For more information on the Audit Log, refer to the Appendix A, “Software Reference Guide” in theback of this manual.

Successful response messages have the following general content and format:

TL1 System Messages 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

36 Issue 4

Page 37: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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:

1850 TSS-320/TSS-320H/TSS-160 TL1 System Messages

Release 5.1 (ETSI)September 2017Issue 4 378DG09603CAAATQZZA

Page 38: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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-charactermnemonic that indicates the cause of the failure. For example, IISP means "Input, Invalid Syntax or

TL1 System Messages 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

38 Issue 4

Page 39: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Punctuation"; PICC means "Privilege, Invalid Command Code." The information displayed in thesuccessful or partially successful response message varies for different commands. Refer to theAppendix A, “Software Reference Guide” in the back of this manual for a list of error codes anddefinitions.

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 messagesdo not interrupt other output responses.

1.4.4 Alarm Messages

Alarm notifications are sent to active login sessions (with alarm output subscription level) instandard 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 formatrequirements.

It has to be taken into account that each naming format can use own specific symbols for "ANDoperation", "range interval", "list elements separation".

This Handbook considers only one naming format which is coherent with the operator labelspecification document and uses ampersand ( & ), hyphen ( - ), comma ( , ) for respectively "ANDoperation", "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.

1850 TSS-320/TSS-320H/TSS-160 CLI Command Structure and Syntax

Release 5.1 (ETSI)September 2017Issue 4 398DG09603CAAATQZZA

Page 40: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

2. aceorder_number An integer value, indicating the ordering position of execution of an AccessControl 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 theadmitted 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 andDesignated 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 Messageby Designated Ports; an integer value, measured in 0.01seconds, in the range [100 ... 200] withdefault value=200.

7. bridge_max_age The maximum age of the information transmitted by the Bridge when it isthe Root Bridge; an integer value, measured in 0.01seconds, in the range [600 ... 4000] withdefault value=2000.

8. bridge_pri Writable portion of the bridge identifier (the first 2 byte of 8 byte); an integer valuein 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-serviceaffecting" in the set: critical, major, minor, warning, indeterminate and cleared.

13. ctrl_frame_32bits It identifies the control frame types for managing their passing throughor 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 inposition 0 ... 31 with 0 being most significant bit) indicates if the frame type represented by thisbit (0 ... 31) is discarded (bit=0) or passed (bit=1). Data frame have to be always passed. Bitmapping 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. Ithas the form disk/folder/sub-folder/.../sub-folder where the last sub-folder contains the softwarepackage.

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 ofa DSCP range).

17. dscp_set An expression using integer values in the range [0 ... 63], and specific symbols forrepresenting 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.

CLI Command Structure and Syntax 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

40 Issue 4

Page 41: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

18. ebs_value An integer number, in the range [0-min [64MB, 256 * corresponding_CBS]] with 1byte granularity.

19. eir_value An integer number, in the range [3 kbit/s ... port line rate] with 1 kbit/sgranularity.

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 specificHousekeeping Input.

23. extpointout_naming An integer number in the range [1 ... 4], indicating the specificHousekeeping Output.

24. eventtype_id An integer number, indicating the specific event type (within the allowed set) tobe 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 beassociated 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 (see1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 UserProvisioning 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 anEtherType 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.

1850 TSS-320/TSS-320H/TSS-160 CLI Command Structure and Syntax

Release 5.1 (ETSI)September 2017Issue 4 418DG09603CAAATQZZA

Page 42: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

41. max_response_time An integer value, measured in 0.1seconds, in the range [1 ... 255] andwith 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 specificsymbols for representing a set of MSTP instance value ranges. For instance 1-3&21 means thatthe values 1, 2, 3 and 21 are specified.

45. mtu_value An integer value, indicating the MTU/MRU in byte. MTU/MRU allowed and defaultvalues 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&frac14;0and drawer=port=0; in commands that apply to a port, the naming must have rack, subrack,board, port&frac14;0.

47. naming_set An expression using integer values in the range [1 ... 4094], ampersand (&) andhyphen (-) 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 withthe 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]] with1 byte granularity.

CLI Command Structure and Syntax 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

42 Issue 4

Page 43: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

54. pcause A string representing a probable cause are in the Table 4, “Alarm and causerelationship” (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. ifthe link speed of the port is Mbit/s, port_path_cost = an integer value in the range [1 ... 200 000000] 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 therange [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 PRIrange).

61. pri_set An expression using integer values in the range [0 ... 7], and specific symbols forrepresenting 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 thatcolor 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 onGFP/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 aVLAN ID range).

74. vlan_set An expression using integer values in the range [1 ... 4094] and specific symbols forrepresenting a set of VLAN value ranges.

1850 TSS-320/TSS-320H/TSS-160 CLI Command Structure and Syntax

Release 5.1 (ETSI)September 2017Issue 4 438DG09603CAAATQZZA

Page 44: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

For instance 100-103&2555 means that the VLAN values 100, 101, 102, 103 and 2555 arespecified.

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 resourcesinside 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-07 7

Reserved for future bridge applications 01-80-C2-00-00-09 9

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

CLI Command Structure and Syntax 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

44 Issue 4

Page 45: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 to01-80-C2-00-00-2F

19 to32

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 EnvironmentalTemperature

excessiveenvironmentaltemperature

Link Failure receiverfailure

Housekeeping not available housekeepingalarm

PLM plm

TSF tsf

TSD / DEG sdhconcdegrade

LOS los

1850 TSS-320/TSS-320H/TSS-160 CLI Command Structure and Syntax

Release 5.1 (ETSI)September 2017Issue 4 458DG09603CAAATQZZA

Page 46: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 userlabels for a specified resource are unambiguous.

2. Operator can define user labels containing blank characters. In this case, the string must be ininverted 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 theASAP 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 correspondingcurrently configured value remains unchanged (if no value had been previously configured thedefault value applies). In the commands where a different behavior is applied, it is explicitlystated.

6. The CLI command is atomic. If any command parameter setting fails, the entire command isrejected.

7. For commands, which set parameters that are modifiable only when a certain resource isadministratively disabled, it is required to check if this condition is satisfied and, if not, to rejectthe command advising properly the operator.

8. If a CLI command fails, the error code currently defined for the corresponding managementfunction 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 specificscenario 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 forshowing information by 24rows pages. For simplicity sake, [more] is not repeated in all showcommands along the document.

11. Some commands requires a confirmation for allowing operator an after-editing verification.

Conventions used in CLI command definition 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

46 Issue 4

Page 47: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 certainparameter, the command, defined in this document for setting that parameter, refers always tothe "change" management function. This policy has to be applied independent of which of thetwo management function ("change" or "condition") is referred in the command referencesection.

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 formanaging 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 fromthe 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 isforwarded 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

1850 TSS-320/TSS-320H/TSS-160 Answers to CLI commands

Release 5.1 (ETSI)September 2017Issue 4 478DG09603CAAATQZZA

Page 48: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

>> warning: already present value for AdminStatus of rlsrls16d1p1

>> warning: already present value for AdminStatus of rlsrls16d1p2

>> warning: already present value for AdminStatus of rlsrls16d1p3

>> warning: already present value for AdminStatus of rlsrls16d1p4

>> 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

Answers to CLI commands 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

48 Issue 4

Page 49: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 inorder 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

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.

Figure 1 LAN cable

1850 TSS-320/TSS-320H/TSS-160 Getting started

Release 5.1 (ETSI)September 2017Issue 4 498DG09603CAAATQZZA

Page 50: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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:

Figure 2 Connection to the interface

TL1 and CLI sessions 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

50 Issue 4

Page 51: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

3

Press OK button to activate the command console as shown in the following picture:

Figure 3 CMD console selection

Figure 4 CMD console activation

1850 TSS-320/TSS-320H/TSS-160 TL1 and CLI sessions

Release 5.1 (ETSI)September 2017Issue 4 518DG09603CAAATQZZA

Page 52: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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:

5

Press Enter key, and the client area console shows the prompt and the window header showsthe node address, as shown in the following picture:

Figure 5 Telnet session activation

TL1 and CLI sessions 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

52 Issue 4

Page 53: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 6 Telnet console

Figure 7 Logging the system

1850 TSS-320/TSS-320H/TSS-160 TL1 and CLI sessions

Release 5.1 (ETSI)September 2017Issue 4 538DG09603CAAATQZZA

Page 54: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

ACT-USER::UID:::PID;

where:

• UID = User Identifier, specifies a unique user ID. Valid values for UID are <5-12 VALID UIDCHARACTERS>, case-sensitive alphanumeric characters where the first character mustalways be an alphabetic character.

• PID = Password Identifier, specifies the user's login password. Valid values for PID are astring of <8-12 VALID PID CHARACTERS> case-sensitive alphanumeric characters.

for further details, see 6.57 “Log Into System” (p. 354).

7

The response for a successful access is the following:

8

Now it is possible to enter a command, e.g. with the RTRV-EQPT::ALL; the relevant responseis the following:

Figure 8 Successful login answer

TL1 and CLI sessions 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

54 Issue 4

Page 55: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Figure 9 Command response example

1850 TSS-320/TSS-320H/TSS-160 TL1 and CLI sessions

Release 5.1 (ETSI)September 2017Issue 4 558DG09603CAAATQZZA

Page 56: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

END OF STEPS

TL1 and CLI sessions 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

56 Issue 4

Page 57: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 theuser 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

1850 TSS-320/TSS-320H/TSS-160 Task Index List (IXL)

Release 5.1 (ETSI)September 2017Issue 4 578DG09603CAAATQZZA

Page 58: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

3.2 IXL-1: User Administration

3.2.1 Overview

Refer to Table 6, “Common User Administration Functions” (p. 57) to identify a common useradministration 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 thecorresponding 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)

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

58 Issue 4

Page 59: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 equipmentprovisioning 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 andthe 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)

1850 TSS-320/TSS-320H/TSS-160 IXL-3: Equipment Provisioning and Deprovisioning

Release 5.1 (ETSI)September 2017Issue 4 598DG09603CAAATQZZA

Page 60: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 andthe 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)

8.22 “Set Performance Monitoring (PM) Data for T-MPLS” (p. 552)

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 correspondingprocedure.

IXL-5: System Administration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

60 Issue 4

Page 61: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 thecorresponding procedure.

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)

8.22 “Set Performance Monitoring (PM) Data for T-MPLS” (p. 552)

6.50 “Display MPLS interface parameters” (p. 328)

8.6 “Administer (T-MPLS/MPLS-TP) DM tool ” (p. 491)

1850 TSS-320/TSS-320H/TSS-160 IXL-7: T-MPLS/MPLS-TP Functions

Release 5.1 (ETSI)September 2017Issue 4 618DG09603CAAATQZZA

Page 62: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 thecorresponding procedure.

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 correspondingprocedure.

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 correspondingprocedure.

IXL-8: VC & LOVC Functions 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

62 Issue 4

Page 63: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 correspondingprocedure.

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 thecorresponding procedure.

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)

1850 TSS-320/TSS-320H/TSS-160 IXL-11: OTU Functions

Release 5.1 (ETSI)September 2017Issue 4 638DG09603CAAATQZZA

Page 64: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

3.14 IXL-13: Maintenance Operation

3.14.1 Overview

Refer to Table 18, “ Maintenance Operation Functions” (p. 63) to identify a maintenance operationand 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 andthe 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 correspondingprocedure.

Table 20 WDM Functions

FUNCTION

6.10 “Administer Line Optical Connection Management” (p. 163)

6.11 “ Administer PassThrough Optical Connection Management” (p. 167)

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

64 Issue 4

Page 65: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 correspondingprocedure.

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 thecorresponding procedure.

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)

1850 TSS-320/TSS-320H/TSS-160 IXL-16: ATM Functions

Release 5.1 (ETSI)September 2017Issue 4 658DG09603CAAATQZZA

Page 66: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 shelfequipment 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 shelfequipment 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)

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

66 Issue 4

Page 67: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 userrequires. For an inexperienced user, each step refers to a DLP. The steps must be performed in theorder 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

1850 TSS-320/TSS-320H/TSS-160 Nontrouble Procedure (NTP)

Release 5.1 (ETSI)September 2017Issue 4 678DG09603CAAATQZZA

Page 68: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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.

ATM Protection Provisioning 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

68 Issue 4

Page 69: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4.2.3 General

4.2.4 Procedures

1

Provision boards and modules. No module provisioning for the ATM board.

For details, refer to 6.67 “Provision Equipment” (p. 385).

Example:

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:;

Figure 10 Functional architecture of the Multiservice ATM Collector card

1850 TSS-320/TSS-320H/TSS-160 ATM Protection Provisioning

Release 5.1 (ETSI)September 2017Issue 4 698DG09603CAAATQZZA

Page 70: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 alarmsenter: rtrv-alm-all;

3

On the SNMP (i.e. CLI) side: the ATM interfaces administrative status are UP (it is not possibleto 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;

ATM Protection Provisioning 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

70 Issue 4

Page 71: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• ENT-TMPLS-TD::::::CIR=100000,PIR=100000,CBS=12800,PBS=12800;

• ED-TMPLS-PW::PW-1-1-1::::TD-ID=MPLSTD-2,STATUS=ON;

5

Create the ATM on PW cross-connection. For details refer to 8DG09603EAAATQZZA1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 CommandLine 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-directionalcross-connection between them, i.e. cross-connection between the mpls port r1sr1sl19d0p1and 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 8DG09603EAAATQZZA1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 CommandLine 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-connectionbetween 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 twounprotected equipment entities is created with the TL1 command: ENT-DX-EQPT. For detailssee 6.4 “Administer Duplex Switching Equipment Protection Group” (p. 143)

Example: The example below to create the EPS Protection Group between two AdaptationCard 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 EquipmentProtection 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.

1850 TSS-320/TSS-320H/TSS-160 Basic Control Plane TL1 Provisioning sequence

Release 5.1 (ETSI)September 2017Issue 4 718DG09603CAAATQZZA

Page 72: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4.3.2 Prerequisites

For more information about TL1 command syntax, system responses, and an explanation of errormessages refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1TL1 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 LineInterface Guide.

To create a control plane link minimum 2 NE are necessary and only point-to-point configuration isavailable. Each 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATAboards.

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

1

TL1 side:

1. Provision board and unit.

For details, refer to 6.67 “Provision Equipment” (p. 385).

2. Provision the Network Interface on a specified DCC channel on an optical port for datacommunication purposes. See 6.20 “Administer Network Interface” (p. 199).

2

CLI side:

• Verify that the ETS ports created in the step before are present, refer to 10.12 “GeneralInterface Management” (p. 599).

• Retrieve port mau configuration (i.e. in order to see if the ports have same mauconfigurations), 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 “ EthernetPort management (over MAU)” (p. 595).

3

TL1 side:

• Provision the Node IP address, OSPF Area Identifiers, refer to 5.2 “Administer T-MPLSControl Plane Global Parameters” (p. 110).

Basic Control Plane TL1 Provisioning sequence 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

72 Issue 4

Page 73: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• Provision Control Plane Transport Port, refer to 5.5 “ Administer Control Plane - TranportPort” (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 TerminatedTunnels; one of the two Tunnel is called Working TUNNEL and the other is called ProtectingTUNNEL.

At node level the NE generates TMPLS OAM (the default value is T-MPLS). To change to MPLS-TPrefer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration” (p. 504).

4.4.4 Procedures

1

Via TL1:

Provision boards and modules.

For details, refer to 6.67 “Provision Equipment” (p. 385).

2

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).

1850 TSS-320/TSS-320H/TSS-160 Bicast&Merge provisioning

Release 5.1 (ETSI)September 2017Issue 4 738DG09603CAAATQZZA

Page 74: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

3

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/VPLSETS InFlow/OutFlow on which it is transported. Creates also the crossconnection betweenthem, see 10.4 “ Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow ”(p. 582).

For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)Release 5.1 Command Line Interface Guide

END OF STEPS

4.5 CP Provisioning

4.5.1 Purpose

This procedure provides instructions and sequence to provision Control Plane.

4.5.2 Prerequisites

For information about TL1/CLI command syntax, system responses, and an explanation of errormessages refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1TL1 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 isavailable. Each 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATAboards.

CP Provisioning 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

74 Issue 4

Page 75: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 differentNE boards (i.e. minimum configuration shall have 2 NEs). All ports involved in the CP link shouldhave 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 FlowControl.

• 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: inband in fiber, out band in fiber , out fiber.

4.5.4 Procedures

1

TL1 side:

Provision board and unit.

For details, refer to 6.67 “Provision Equipment” (p. 385).

2

CLI side:

• Verify that the ETS ports created in the step before are present, refer to 10.12 “GeneralInterface Management” (p. 599).

• Retrieve port mau configuration (i.e. in order to see if the ports have same mauconfigurations), 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 “ EthernetPort management (over MAU)” (p. 595).

3

TL1 side:

• Set the Node IP address, OSPF Area Identifiers, refer to 5.2 “Administer T-MPLS ControlPlane Global Parameters” (p. 110).

1850 TSS-320/TSS-320H/TSS-160 CP Provisioning

Release 5.1 (ETSI)September 2017Issue 4 758DG09603CAAATQZZA

Page 76: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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 ControlPlane - 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, thendelete commands cannot be used to erase facilities. In this mode, facility deletion occurs only whenthe supporting equipment or logical resource is deleted (see6.35 “Administer SystemConfiguration” (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

Ethernet Deprovisioning 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

76 Issue 4

Page 77: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 10XANY

• DWLA10X

4.7.3 General

Gigabit Ethernet facilities are associated with ports on a GBE module, and support GBEVCGfacilities 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 (see6.67 “Provision Equipment” (p. 385)). Automatically entered facilities are created with defaultprovisioning, with AINS active. Provisioning changes may be made to an automaticallyentered ethernet facility using the TL1 edit commands.

4.7.4 Procedures

1

Provision board.

For details, refer to 6.67 “Provision Equipment” (p. 385).

2

Provision Ethernet facility.

For details, refer to 6.8 “Administer Ethernet Facility ” (p. 155).

END OF STEPS

4.8 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 alreadyin use; and for “MPLS label based” In Fiber In Band Management Interface is defined on a MPLSport 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:

1850 TSS-320/TSS-320H/TSS-160 In Fiber In Band for Control Plan Provisioning

Release 5.1 (ETSI)September 2017Issue 4 778DG09603CAAATQZZA

Page 78: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• VLAN basedIn Fiber In Band Management Interface;

• MPLS label basedIn Fiber In Band Management Interface

4.8.4 Procedures

1

Provision board and unit.

For details, refer to 6.67 “Provision Equipment” (p. 385).

2

Verify (CLI side) the unit type provisioned in Step 1.

For details, refer to 10.12 “General Interface Management” (p. 599).

3

Choose (CLI side) the “VLAN based” or “MPLS Label based” In Fiber In Band ManagementInterface.

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 ManagementInterface.

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 theiradministrative status set to down. LAG deactivation is then achieved is similar way.

4.9.4 Procedure

1

Retrieve board and the module.

LAG Deprovisioning 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

78 Issue 4

Page 79: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

For details, refer to 6.67 “Provision Equipment” (p. 385).

2

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 ETSinterface).

Note: It must be remarked that, policing rate that can be applied for flooding control shouldbe:

• 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 happenswhen 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 FlowControl.

• 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).

1850 TSS-320/TSS-320H/TSS-160 LAG Provisioning

Release 5.1 (ETSI)September 2017Issue 4 798DG09603CAAATQZZA

Page 80: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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. Theresulting aggregate link will be treated by the system (with regard to instances about IGMP, networkprotections, 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 automaticallydistributed over the other links of the aggregate).

4.10.4 Procedure

1

Provision board and the module.

For details, refer to 6.67 “Provision Equipment” (p. 385).

2

Verify CLI side conditions for Link Aggregation:

• that the ETS ports created in the step before is present see 10.12 “General InterfaceManagement” (p. 599)

• Verify all ports that will belong to LAG have same mau configuration see 10.10 “ EthernetPort 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 ETSinterface).

Note: It must be remarked that, policing rate that can be applied for flooding control shouldbe:

• On board basis.

A single rate policer is applied to all ingress aggregation ports of a LAG.

LAG Provisioning 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

80 Issue 4

Page 81: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• On port basis.

A rate policer is applied to each ingress aggregation port of a LAG. This case happenswhen 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. tunnelterminated).

4.11.2 Prerequisites

The 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA boards.

4.11.3 General

At node level the NE generates TMPLS OAM (the default value is T-MPLS). To change to MPLS-TPrefer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration” (p. 504).

4.11.4 Procedure

1

Via TL1:

Provision boards and modules.

For details, refer to 6.67 “Provision Equipment” (p. 385).

2

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).

3

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 ofthe unique terminated segment, see 8.15 “Administer T-MPLS Tunnel” (p. 524).

3. Configure parameters (VTs, Traffic Descriptor) of automatic created tunnel. See8.15 “Administer T-MPLS Tunnel” (p. 524).

END OF STEPS

1850 TSS-320/TSS-320H/TSS-160 LER Tunnel Management (Tunnel Terminated)

Release 5.1 (ETSI)September 2017Issue 4 818DG09603CAAATQZZA

Page 82: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 swapand tunnel not terminated).

4.12.2 Prerequisites

The 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA boards.

4.12.3 General

At node level the NE generates TMPLS OAM (the default value is T-MPLS). To change to MPLS-TPrefer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration” (p. 504).

4.12.4 Procedure

1

Via TL1:

Provision boards and modules.

For details, refer to 6.67 “Provision Equipment” (p. 385).

2

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).

3

Via TL1:

1. Create the Traffic Descriptor, see 8.14 “Administer T-MPLS Traffic Descriptor” (p. 521).

2. Create the first segment, providing as reference the MPLS IF (interface) created in Step 2.Refer to 8.17 “Administer T-MPLS Tunnel Segment” (p. 531).

3. Create the second segment, providing as reference the MPLS IF (interface) created inStep 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), see8.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).

LSR Tunnel Management (Label swap and Tunnel not Terminated) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

82 Issue 4

Page 83: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Note: With TUSEG creation it is possible to provide the indication of the PHB profileassociated 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 communicationsbetween the customer and the NE shall be alowed only with strong encryption and cryptographicprotection in order to provide confidentiality, integrity, and replay protection.

By default the NE shall start in UNSECURE mode. This allows backward compatibility towardsexisting NMS that do not support encryption.

When the NE is in secure mode, the secure connection between the user and the NE shall beaccomplished 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 keysand certificate.

The TL1 command SET-ATTR-SECUDFLT shall provide the capability of configuring the NE issecure or unsecure mode

When the NE is in secure mode it shall support SSH-2 encryption protocol for TL1 and CLI, SSLencryption 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 connectionsvia encryption; only ports 6084 and 6085 (TL1), 6086 (CLI), 22 (debug port for ROOT accessalways with SSH) and 443 (HTTPS) are opened and the NE shall support SNMPv3 and shall

1850 TSS-320/TSS-320H/TSS-160 NE Secure mode configuration

Release 5.1 (ETSI)September 2017Issue 4 838DG09603CAAATQZZA

Page 84: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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.

4

Select action:

• Establish a SSH2 session using SecureCRT on port 6084 for TL1.

• Establish a SSH2 session using SecureCRT on port 6085 for TL1.

• Establish a SSH2 session using SecureCRT for port 6086 for CLI.

• Access debug port for ROOT access always with SSH for port 22

• Manage NE using SSL protocol https://<ipaddress>:443

Result: Secure connection is created via encryption

Note: When NE secure mode configuration fails (e.g. failed exchange of public-keys). please configure the NE unsecure mode and update keys manually.

5

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).

4.14.3 Before you begin

The NE needs to be connected to the Network Management System.

NE Unsecure mode configuration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

84 Issue 4

Page 85: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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) areopened.

3

Verify the NE secure has been set to UNSECURE MODE, enter:

RTRV-DFLT-SECU;

4

Select action:

• Establish a SSH2 session using SecureCRT on port 3082 for TL1.

• Establish a SSH2 session using SecureCRT on port 3083 for TL1.

• Establish a SSH2 session using SecureCRT for port 1123 for CLI.

• Establish a session using telnet for port 23 for CLI.

• Access debug port for ROOT access always with SSH for port 22

• Manage the NE on http://<ipaddress>:80

5

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.

1850 TSS-320/TSS-320H/TSS-160 SSH keys configuration

Release 5.1 (ETSI)September 2017Issue 4 858DG09603CAAATQZZA

Page 86: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4.15.2 General

The new pair of SSH keys on the NE is used by the NE for establishing new sessions. Because anSSH session uses asymmetric encryption by means of public & private keys for initial authenticationphase, currently existing sessions remain open and working. The new session is symmetricallyencrypted by means of a common shared secret key, which is exchanged after authenticationcompletion, and remains valid for the entire session.

The NMS can transfer and install the NMS SSH public key onto the NE via COPY-RFILE.-SECUTL1 command. The NE adds that key to its own NMS SSH public keys list, in order to acceptconnections form that NMS too, from that point on.

4.15.3 Before you begin

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) forNE 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 andprivate) for the NE.

Note: SSH Keys should be periodically updated according to a centralized policy.

Result: REPT^EVT^SECU with CONDTYPE=SSHKEY is sent when INIT-SSH-KEY issuccessfully 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 thatNE too, from that point on.

Result: REPT^EVT^SECU with CONDTYPE=OSSSHKEY is sent when COPY-RFILE-SECU

with FROM=LOCSSHKEY and TO=RFSSSHKEY is successfully completed.

SSH keys configuration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

86 Issue 4

Page 87: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

5

A user with security privileges can retrieve the NE SSH public key, keytype and key-length, bymeans 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 thatNMS too, from that point on.

Result: REPT^EVT^SECU with CONDTYPE=OSSSHKEY shall be sent whenCOPY-RFILE-SECU with FROM=RFSSSHKEY and TO=LOCSSHKEY is successfullycompleted.

END OF STEPS

1850 TSS-320/TSS-320H/TSS-160 SSH keys configuration

Release 5.1 (ETSI)September 2017Issue 4 878DG09603CAAATQZZA

Page 88: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4.15.5

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 onlyapplies in the case where the NMS is configured to act as a certificate authority (CA) for themanaged network elements.

Figure 11 SSH key management

SSL keys configuration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

88 Issue 4

Page 89: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4.16.2 General

The generation and installation of NE SSL certificate is initiated by the NMS administrator and onlyapplies in the case where the NMS is configured to act as a certificate authority (CA) for themanaged 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 ofCA Certificates that an NMS can manage:

• Self-signed CA-certificate: In this case there is no need to manage an external CA and NMS cangenerate its own root self-signed CA certificate using which it will sign all end-entity certificatesgenerated for the NEs.

• Cross-certificate CA-certificate: Not applicable in this release. In this case, an external CAdelivers a CA-certificate (called CA cross-certificate see X.509 for more reference) to NMSmaking NMS itself able to act as a second level CA. In practice, a Cross-certificate CA is justissued 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 trustedCA in this schema, forming what is generally called a trusted certification chain, able toconsistently generate and issue certificates for end-entity Network Element.

4.16.3 Before you begin

The NE needs to be connected to the Network Management System where NMS is a root CAowning 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), throughINIT-SSL-KEY TL1 command. This step is optional and is triggered only if a new SSL keygeneration is necessary. If new key generation is not triggered by NMS, the NE simply uses thecurrent key in the next steps.

Note: SSL certificates should be periodically updated according to a centralized policy. Itis expected that NMS should generate them with an expiration age of 10 years but theyshould be periodically updated.

Result: The NE generates a new SSL key pair (public and private) and then sends anotification warning to all network administrators, through REPT^EVT^SECU withCONDTYPE=SSLKEY is sent when INIT-SSL-KEY is successfully completed. and a new

1850 TSS-320/TSS-320H/TSS-160 SSL keys configuration

Release 5.1 (ETSI)September 2017Issue 4 898DG09603CAAATQZZA

Page 90: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

key has been generated. NOTE: The NMS user that issued the INIT-SSL-KEY command isaware of the new key because of the INIT-SSL-KEY COMPLD response, butREPT^EVT^SECU is mandatory to notify all network administrators.

4

The NMS triggers the NE to generate a CRS, through INIT-SSL-CSR TL1 command, andoptionally 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) messagethrough which a user applies for a certificate. The message is generated on the server that thecertificate and is used and is signed with the applicant private key. A CSR contains the followinginformation 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 (OpticsDivision).

• City/Locality: The city where your organization is located (Rome).

• State/County/Region: The state/region where your organization is located (should not beabbreviated, 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 isNOT to be included in the CSR and needs to be kept as private information to be neverdisclosed.

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 andwhen completed sends a notification warning through REPT^EVT^SECU, that the CSR hasbeen generated.

5

NMS triggers the CSR file transfer upload from the NE to the NMS, throughCOPY-RFILE-SECU. The NE starts the CSR file transfer onto the NMS machine locationspecified in the COPY-RFILE-SECU.

Result: REPT^EVT^SECU with CONDTYPE=SSLCSR is sent when COPY-RFILE-SECU

with FROM=LOCCSRPEM and TO=RFSCSRPEM is successfully completed.

REPT^EVT^SECU with CONDTYPE=SSLCSR is sent when COPY-RFILE-SECU withFROM=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.

SSL keys configuration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

90 Issue 4

Page 91: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

7

NMS makes a new PEM format certificate available for download by the NE and triggers the NEitself to download it from a location specified in input parameter, through COPY-RFILE-SECU.

Result: REPT^EVT^SECU with CONDTYPE=SSLCERT is sent when COPY-RFILE-SECU

with FROM=RFSX509PEM and TO=LOCX509PEM is successfully completed.

REPT^EVT^SECU with CONDTYPE=SSLCERT is sent when COPY-RFILESECU withFROM=RFSX509TEXT and TO=LOCX509TEXT is successfully completed.

8

NE starts downloading the certificate from the NMS machine location specified in the triggeringrequest. At the end of the file transfer phase, NE sends a notification to NMS, throughREPT^EVT^SECU.

9

NE validates the downloaded certificate and, in case of success, installs it and sends a COMPDresponse to the COPY-RFILE-SECU in Step 7. In case a new SSL key generation is called inthe time between a CSR generation request Step 4 and the new certificate installation in thisstep, a mismatch would arise in the NE, as the certificate would not be consistent with the keyanymore. In this case NE has to detect the error and to refuse the certificate installationreturning 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, bothin 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 textand PEM formats, by means of the RTRV-SSL-CSR TL1 command.

END OF STEPS

1850 TSS-320/TSS-320H/TSS-160 SSL keys configuration

Release 5.1 (ETSI)September 2017Issue 4 918DG09603CAAATQZZA

Page 92: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4.16.5

4.17 ODU2 Deprovisioning

4.17.1 Purpose

This procedure provides instructions and sequence to deprovision an ODU2 facility.

4.17.2 Prerequisites

None

Figure 12 SSL key management

ODU2 Deprovisioning 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

92 Issue 4

Page 93: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4.17.3 General

Since the ODU2 object entity is automatically created (on the line side by the system when theOTU-2 board is inserted and provisioned) the deprovision indicates only a change of state for theODU2 object.

The RMV-ODU2 command causes the specified facility client/line to be placed in an out-of-servicestate for maintenance purposes.

After the maintenance phase the specified facility client/line can be restored with the RST-ODU2

command.

4.17.4 Procedure

1

Deprovision ODU2 facility.

For details, refer to 6.25 “Administer ODU2 Facility” (p. 212).

2

Restore the ODU2 facility.

For details, refer to 6.25 “Administer ODU2 Facility” (p. 212).

END OF STEPS

4.18 ODU2 Provisioning

4.18.1 Purpose

This procedure provides instructions and sequence to provision an ODU2 facility.

4.18.2 Prerequisites

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-2board 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.

1850 TSS-320/TSS-320H/TSS-160 ODU2 Provisioning

Release 5.1 (ETSI)September 2017Issue 4 938DG09603CAAATQZZA

Page 94: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

For details, refer to 6.25 “Administer ODU2 Facility” (p. 212).

END OF STEPS

4.19 OTU2 Deprovisioning

4.19.1 Purpose

This procedure provides the instructions and sequence to deprovision an OTU2 facility.

4.19.2 Prerequisites

None.

4.19.3 General

This procedure provides the instructions to deprovision a specified OTU2 client and line/port or tochange the port state.

4.19.4 Procedure

1

Deprovision the OTU2 facility.

For details, refer to 6.26 “Administer OTU2 Facility” (p. 218).

2

Change the port state.

For details, refer to 6.26 “Administer OTU2 Facility” (p. 218).

END OF STEPS

4.20 OTU2 Provisioning

4.20.1 Purpose

This procedure provides instructions and sequence to provision an OTS facility.

4.20.2 Prerequisites

The node shall be equipped with one of the following modules:

• DWLA10X

• OTU-2

4.20.3 General

The OTU2 object entity shall be automatically created on the line side by the system when theOTU-2 or DWLA10X is inserted and provisioned.

OTU2 Deprovisioning 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

94 Issue 4

Page 95: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 thiscreate command cannot be used to enter facilities. In this mode, facilities are automatically enteredwhen the supporting equipment is entered (see 6.67 “Provision Equipment” (p. 385)).

4.20.4 Procedure

1

Provision the OTU-2 facility.

For details, refer to 6.26 “Administer OTU2 Facility” (p. 218).

END OF STEPS

4.21 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.2 Prerequisites

The 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA boards.

4.21.3 General

None.

4.21.4 Procedure

1

Via TL1:

Provision boards and modules.

For details, refer to 6.67 “Provision Equipment” (p. 385).

2

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).

1850 TSS-320/TSS-320H/TSS-160 PW Stitching Management (Case of label swap)

Release 5.1 (ETSI)September 2017Issue 4 958DG09603CAAATQZZA

Page 96: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

3

Via TL1:

1. Create the Traffic Descriptor, see 8.14 “Administer T-MPLS Traffic Descriptor” (p. 521).

2. Create the first PW segment over a terminated tunnel or physical interface, i.e. TUSEG orMPLS 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. TUSEGor 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. Referto 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 to8.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

This procedure provides instructions and sequence to provision a PW terminated segment.

4.22.2 Prerequisites

The 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA boards.

4.22.3 General

None.

4.22.4 Procedure

1

Via TL1:

Provision boards and modules.

For details, refer to 6.67 “Provision Equipment” (p. 385).

2

Via CLI side:

• Verify the ETS ports presence, see 10.12 “General Interface Management” (p. 599).

PW Termination Management (Case of point-to-point) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

96 Issue 4

Page 97: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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).

3

Via TL1:

1. Create the Traffic Descriptor, see 8.14 “Administer T-MPLS Traffic Descriptor” (p. 521).

2. Create an unique terminated segment over Tunnel or physical interface (i.e. the“termination” option is chosen for TL1 command). Refer to 8.12 “Administer T-MPLSPseudo Wire Segment” (p. 514).

3. Configure some PW parameters (including possible association with TD and VT). Refer to8.11 “Administer T-MPLS Pseudo Wire” (p. 510).

Note: It is possible to move one PW from one underlying tunnel to another tunnel, seealso8.11 “Administer T-MPLS Pseudo Wire” (p. 510).

4

Via CLI:

Create, configure, activate an ETS to Provider Bridge PW bidirectional flow, refer to 10.4 “Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow ” (p. 582).

END OF STEPS

4.23 PW Termination Management (Case of VPLS)

4.23.1 Purpose

This procedure provides instructions and sequence to provision a PW terminated segment.

4.23.2 Prerequisites

The 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA boards.

4.23.3 General

None.

4.23.4 Procedure

1

Via TL1:

Provision boards and modules.

For details, refer to 6.67 “Provision Equipment” (p. 385).

1850 TSS-320/TSS-320H/TSS-160 PW Termination Management (Case of VPLS)

Release 5.1 (ETSI)September 2017Issue 4 978DG09603CAAATQZZA

Page 98: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

2

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).

3

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-MPLSPseudo Wire Segment” (p. 514).

3. Configuration of parameters of PW. Refer to 8.11 “Administer T-MPLS Pseudo Wire”(p. 510).

4

Via CLI:

• Bind between VPLS instance and PW, refer to 10.16 “VPLS Instance Management” (p. 608).

• Create, configure, activate an ETS to Provider Bridge VPLS bidirectional flow refer to 10.4 “Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow ” (p. 582).

END OF STEPS

4.24 Tunnel Protection Management (Label swap and Tunnel notTerminated)

4.24.1 Purpose

This procedure provides instructions and sequence to provision an Tunnel Protection (in Release4.0) only Tunnel Protection is performed.

4.24.2 Prerequisites

The 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA boards.

In Release 4.0 Tunnel termination is needed.

4.24.3

At node level the NE generates TMPLS OAM (the default value is T-MPLS). To change to MPLS-TPrefer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration” (p. 504).

Tunnel Protection Management (Label swap and Tunnel not Terminated) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

98 Issue 4

Page 99: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4.24.4 General

Scenario in case of protection: when protection is configured, the PW is anyway associated to themain tunnel.

When switch occurs the relationship between PW and Tunnel doesn’t change (the switchingposition is retrievable inside the protection group). It is possible to remove the protection groupleaving 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 tospare).

4.24.5 Procedure

1

Via TL1:

Provision boards and modules.

For details, refer to 6.67 “Provision Equipment” (p. 385).

2

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).

3

Via TL1:

1. Create two MPLS Tunnels (not protected), both sharing the same ingress/egress LSRinformation 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”), see8.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

1850 TSS-320/TSS-320H/TSS-160 Tunnel Protection Management (Label swap and Tunnel not Terminated)

Release 5.1 (ETSI)September 2017Issue 4 998DG09603CAAATQZZA

Page 100: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4.25 VCG Deprovisioning

4.25.1 Purpose

This procedure provides instructions and sequence to deprovision an VCG facility.

4.25.2 Prerequisites

Please verify the VCG presence with the TL1 retrieve command (see 6.40 “Administer VCGFacility” (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/OutFlowinvolved in the VCG CLI side (i.e. Verify CLI side no cross connections are present for the VCGto 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 forthe VCG to deprovision).

For details, refer to 6.39 “Administer VC Cross-Connection” (p. 267).

3

Deactivate the ETS port CLI side.

For details, refer to 10.10 “ Ethernet Port management (over MAU)” (p. 595).

4

Deprovision VCG facility.

For details, refer to 6.40 “Administer VCG Facility” (p. 277).

END OF STEPS

4.26 VCG Provisioning

4.26.1 Purpose

This procedure provides instructions and sequence to provision an VCG facility.

VCG Deprovisioning 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

100 Issue 4

Page 101: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4.26.2 Prerequisites

The node should be equipped with one of the following boards:

• PP10AD

• 10XANY.

4.26.3 General

During a Virtual Concatenation Group creation also initial group of SDH Virtual Containers areassigned to the VCG.

The Type of Virtual Container is specified in VCGTYPE parameter and can be for ETSI: VC4, VC3,VC12.

The VCG is used to map data on SDH, i.e. to map Ethernet, ATM on SDH.

4.26.4 Procedure

1

Provision board and the module.

For details, refer to 6.67 “Provision Equipment” (p. 385).

2

Provision the VCG facility.

For details, refer to 6.40 “Administer VCG Facility” (p. 277).

3

Verify CLI side.

• that the VCG created on the ETS port is present, refer to 10.12 “General InterfaceManagement” (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-ETSbidirectional (port to port configuration)” (p. 585).

4

Provision the VC cross connection.

For details, refer to 6.39 “Administer VC Cross-Connection” (p. 267).

For 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.

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

Release 5.1 (ETSI)September 2017Issue 4 1018DG09603CAAATQZZA

Page 102: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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.

4.27.2 Prerequisites

Verify the VPLS instance presence (see 10.16 “VPLS Instance Management” (p. 608)).

4.27.3 General

The VPLS Service is removed only using CLI commands.

4.27.4 Procedure

1

Delete ETS InFlow/OutFlow and the Provider Bridge/PW/VPLS ETS InFlow/OutFlow on which itis transported. Creates also the cross connection between them, refer to 10.4 “ Administer ETSto Provider Bridge ETS/PW/VPLS bidirectional flow ” (p. 582).

For details, refer to 8DG09603EAAATQZZA — 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 Command Line Interface Guide.

2

Delete VPLS Instance.

For details, refer to 10.16 “VPLS Instance Management” (p. 608).

END OF STEPS

4.28 VPLS Provisioning

4.28.1 Purpose

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

4.28.2 Prerequisites

The node should be equipped with one of the following boards:

• PP10GE

• PP1GE.

VPLS Deprovisioning 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

102 Issue 4

Page 103: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4.28.3 General

A VPLS Service is a provider service based on “L2VPN” logical model with multi-point connectivitythat makes it possible to interconnect several LAN segments over a VPLS Network (consisting offully 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 (irrespectivefrom higher layer protocols) between 2 remote Ethernet stations;

• Ethernet services to exploit “carrier class” MPLS capabilities, relying on both MPLS “connectionoriented” behavior and MPLS QoS capabilities.

4.28.4 Procedure

1

Provision board and the module.

For details, refer to 6.67 “Provision Equipment” (p. 385).

2

Change ports involved in VPLS in MPLS ones.

For details, refer to 10.10 “ Ethernet Port management (over MAU)” (p. 595).

3

Activate the VPLS ports.

For details, refer to 10.16 “VPLS Instance Management” (p. 608).

4

Provision the T-MPLS Traffic Descriptor for each Pseudo Wire that will be created for the VPLS.

For details, refer to 8.14 “Administer T-MPLS Traffic Descriptor” (p. 521).

5

Provision the Terminated Pseudo Wire.

For details, refer to 8.11 “Administer T-MPLS Pseudo Wire” (p. 510).

6

Create, activate and configure an ETS traffic descriptor.

For details, refer to 10.7 “Administer Traffic Descriptor” (p. 589).

7

Create and activate an VPLS instance see 10.16 “VPLS Instance Management” (p. 608)

For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)Release 5.1 Command Line Interface Guide.

1850 TSS-320/TSS-320H/TSS-160 VPLS Provisioning

Release 5.1 (ETSI)September 2017Issue 4 1038DG09603CAAATQZZA

Page 104: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

8

Create configure and activate ETS InFlow/OutFlow and the Provider Bridge/PW/VPLS ETSInFlow/OutFlow on which it is transported. Creates also the cross connection between them,see 10.4 “ Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow ” (p. 582).

For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)Release 5.1 Command Line Interface Guide.

END OF STEPS

4.29 UGW Protection Provisioning

4.29.1 Purpose

This procedure provides an UGW facility (and protection) provisioning example.

4.29.2 Prerequisites

The node should be equipped with the following boards (and their modules):

• the UGW card, i.e. 2.5 Gb/s portless Universal Gateway (UGW)

• the SDH card (for example the 8PSO)

• the DATA card (for example the PP1GE).

Note: In current release, only TDM CES function is supported (2.5 Gb/s switching capability)

4.29.3 General

UGW card interfaces with both TDM matrix and Packet matrix which connects to the physical linecards 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 aTDM 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 overPackets”), 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 SNMPagent, i.e. via CLI commands.

UGW Protection Provisioning 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

104 Issue 4

Page 105: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4.29.4 Procedures

1

Provision boards and modules. No module provisioning for the UGW board.

For details, refer to 6.67 “Provision Equipment” (p. 385).

Example:

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..

For details, refer to 6.39 “Administer VC Cross-Connection” (p. 267).

Example: Example with TDM card STM16 (AU4 range: 1 - 16):ENT-CRS-VC4::STM16AU4-1-1-12-2-1,UGMVC4-1-1-17-2;

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 notpossible 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)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

1850 TSS-320/TSS-320H/TSS-160 UGW Protection Provisioning

Release 5.1 (ETSI)September 2017Issue 4 1058DG09603CAAATQZZA

Page 106: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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;

• ENT-TMPLS-TD::::::CIR=100000,PIR=100000,CBS=12800,PBS=12800;

• ED-TMPLS-PW::PW-1-1-1::::TD-ID=MPLSTD-2,STATUS=ON;

5

Create the 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 iscreated with the TL1 command: ENT-DX-EQPT::PPUGW-1-1-12,PPUGW-1-1-19;. Fordetails 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 EquipmentProtection Group” (p. 143) .

END OF STEPS

UGW Protection Provisioning 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

106 Issue 4

Page 107: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

5 Control Plane Functions

5.1 Overview

5.1.1 Purpose

The Detailed Level Procedures (DLP) described in this chapter contain detailed steps andsupporting information required to complete a task when the CP is used. When a DLP is referencedfrom another part of the manual, perform the DLP, then return to the point where the DLP wasreferenced.

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), inGMPLS 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 orientedto data service application (MPLS encapsulation of Ethernet, ATM, IP packets).

CP ROUTE defines global parameters of the network , Control Channel configuration and routingmanagement, 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 beachieved.

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

1850 TSS-320/TSS-320H/TSS-160 Control Plane Functions

Release 5.1 (ETSI)September 2017Issue 4 1078DG09603CAAATQZZA

Page 108: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 andconsolidate 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 tosupport GMPLS functionalities (routing and signaling) of GMPLS entities (known as GMPLSControllers).

SCN is a Layer -3 network and is defined independently from MCN (Management CommunicationNetwork), assigned to a Network Manager.

SCN is built over IP Control Channel (IPCC) network, through point-to-point communication linksbetween 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, asdefined from ITUT-T recommendation G.8080, under ASON network architecture concept.

A complex network can be partitioned into different subnetworks, each of them will behomogeneous 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 interconnectionbetween domains.

Routing protocols requires minumum basic provisioning set by CP for their operation. The followingset 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)

Overview 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

108 Issue 4

Page 109: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

I.e. Operator should define IP address for network nodes assigned to CP for their managementin routing , signaling and transport port provisioning.

In E-NNI routing environment, node IP is the Router IDentifier for the routing protocol running onthe relevant hierarchical level.

The node IP address, which is the router loopback address (always reachable) is common toboth 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 routinginterfaces 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 to4294967295 (232 -1) and is expressed in four dot separated numeric string with range {0-255}foreach string.

If not specified backbone area (Area 0 ) is applied at default on such interfaces Default Area IDcan 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 Channeltermination 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 isautomatically 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 bydefault).

• IP static routes advertisements

Operator is able to define advertise mode of all IP static routes created on local node and addedto the relevant routing table, under CP management.

• Notification events by CP.

Operator should configure notification events by CP relating to the assigned resources (transportport, routing interface, signaling control)

Depending on the selected mode notification (enabled or disabled) the events from the relevantresources 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 , throughED-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

1850 TSS-320/TSS-320H/TSS-160 Overview

Release 5.1 (ETSI)September 2017Issue 4 1098DG09603CAAATQZZA

Page 110: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 networkparameters 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 ControlPlane (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 loopbackinterface, located on the OSPF backbone default area (0.0.0.0). If the entry for ED-CP-GLOBALcommand is only for a change of the OSPF default area , this can be done before the node IPaddress 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] ;

Administer T-MPLS Control Plane Global Parameters 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

110 Issue 4

Page 111: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Modify Control Plane parameters

Enter ED-TMPLS-CPGLOBAL::::::[IPADDR=][,OSPFAREAIDDFLT=][,AUTOCONFIG=][,ADVERTISE=][,CP-PORTEVNT=][,CP-ROUTPROTEVNT=][,CP-SIGNEVNT=

];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

where:

IPADDR= Internet Protocol address, it is the IP address of the NE for the Control Plane inT-MPLS application. The address 0-0-0-0 is not allowed. Neither the network nor the hostportion 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 aControl 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 NetworkParameters” (p. 502)

5.3.3 General

IP Control Channel (IPCC) is the communication channel inside the SCN network to carry GMPLSrouting and signaling protocols packets.

Depending on the selected control channel port type (I-NNI or E-NNI) , associated routing interfacewill 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

1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane - Control Routing Port

Release 5.1 (ETSI)September 2017Issue 4 1118DG09603CAAATQZZA

Page 112: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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 -OutOf-Band (OF-OOB) Control Channel port configuration, used for routing purpose, under CPmanagement.

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 canbe 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 interfacesover 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)

• Administrative status

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 andadmnistrative status of control channel. set-up configuration, used for routing purpose, under CPmanagement.

This command allows to change setting of the ARP protocol (Address Resolution Protocol) in MPLSinterfaces, together with ARP timeout (aging time of ARP table entries) and flushing of the ARPtable (deleting all ARP entries).

The DLT-CP-COM command deletes the previously defined control channel termination port, usedfor 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.

To end this procedure, go to Step 10.

2

Retrieve Control Channel Termination Port information

Administer Control Plane - Control Routing Port 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

112 Issue 4

Page 113: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter RTRV-CP-COM::AID::::[APPLY=][,ARP-TABLE=];

where: AID = Access IDentifier of the control channel termination port to be retrieved. If ALL isselected all the control channel termination ports are retrieved. Possible values:

• ALL

• LAN-1 for Customer LAN

• MPLSIF-{1-7}-{1-9}-{2-9,12-19}-{1-10} for Local MPLS Interface

• MPLSIF-{1-7}-{1-9}-{2-9,12-19}-{1-128} for VCG MPLS Interface

• TIPIP-{10-300000} for Virtual Link using IPover IP encapsulation for TMPLS

• TGRE-{10-300000} for Virtual Link using GRE encapsulation for TMPLS

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Examine output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane - Control Routing Port

Release 5.1 (ETSI)September 2017Issue 4 1138DG09603CAAATQZZA

Page 114: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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, MPLSinterfaces are used (local GbE or logical VCG's ). For OF-OOB, T-MPLS instance can usevirtual tunnel encapsulation with TIPIP-n or TGRE-n AID. Possible values as for Step 2 ALLexcluded...

Administer Control Plane - Control Routing Port 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

114 Issue 4

Page 115: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Go to Step 1.

7

Modify Control Channel Termination Port parameters

Enter ED-CP-COM::AID::::[MTU=][,ARP=][,ARP-TIMEOUT=] [,ARP-FLUSHING=][,

STATUS=];

where:

• AID = Access Identifier, specifies the control channel termination port. Possible values as forStep 2 ALL excluded..

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

8

Go to Step 1.

9

Delete Control Channel Termination Port

Enter DLT-CP-COM::AID:;

where:

• AID = Access Identifier, specifies an access to the facility. Possible values as for Step 2 ALLexcluded..

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

10

STOP. This procedure is complete.

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 staticIP 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 IProuting table of a local node.

1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane - IP Route

Release 5.1 (ETSI)September 2017Issue 4 1158DG09603CAAATQZZA

Page 116: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

5.4.2 Prerequisites

Network node ID, where this command is applied, must be previously defined by CP via5.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 “AdministerT-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 physicaltermination 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 sourceattributes (static or dynamic).

If advertise mode is set in CP global parameter configuration, all IP static entries of a local node areleaked 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, throughaccess to the control channel termination port

An IP route is a route to the destination IP address through a network interface , that is defined asthe "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 ora subnetwork.

If IP mask is not all “ones” , a route to a subnetwork is defined, and the corresponding field ofdestination 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 (hostnode or subnetwork). This interface has to be provisioned only if control channel termination portshave a multiple access through a LAN or a MPLS IF. Metric is the provisioned static route costthrough 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, byCP.

• If the AID specifies a STM-n then the NEXTHOP parameter should not be specified.

Administer Control Plane - IP Route 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

116 Issue 4

Page 117: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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 routesgenerated by OSPF software.

If the operator specifies in the command the destination IP address and mask, only the IP routescontained 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 IProute’s parameters specified define univocally the entry in the IP routing table that has to bedeleted. If a match with all the specified parameters cannot be found, an error message will bereturned inresponse.

5.4.6 Procedure

1

Select action.

To perform Static routing removal, go to Step 2.

To perform Static routing configuration, go to Step 5.

To perform Static routing removal, go to Step 7

To end this procedure, go to Step 8.

2

Retrieve Control Plane IP Route information

Enter RTRV-CP-RT:::::[DESTADDR],[MASK];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Examine output, as detailed in the relevant command guide, refer to “Command details”(p. 107)

4

Go to Step 1.

5

Create Control Plane IP Route

Enter ENT-CP-RT::AID:::DESTADDR,MASK,[NEXTHOP],[METRIC];

where:

• AID = Access IDentifier, specifies the access interface for the static routing. Possible values:− LAN-1 for Customer LAN

− MPLSIF-{1-7}-{1-9}-{2-9,12-19}-{1-10} for Local MPLS Interface

− MPLSIF-{1-7}-{1-9}-{2-9,12-19}-{1-128} for VCG MPLS Interface

− TIPIP-{10-300000} for Virtual Link using IPover IP encapsulation for TMPLS

1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane - IP Route

Release 5.1 (ETSI)September 2017Issue 4 1178DG09603CAAATQZZA

Page 118: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

− 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 , incombination with IP subnet mask (NETMASK). If NETMASK is not all “1” (i.e., a networkroute 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). Themask 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 addressof the next interface in the route (in the format nnn-nnn-nnn-nnn). The target NE shall bedirectly connected to this interface. The address 0-0-0-0 is not allowed. Neither the networknor the host portion of the address when viewed in binary format may be all 0’s or all 1’s. TheNEXTHOP address must be in the address range of the IP subnet configured on theCustomer 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}.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

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 , incombination with IP subnet mask (NETMASK). If NETMASK is not all “1” (i.e., a networkroute 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). Themask 0-0-0-0 is used to specify a default route. Possible values: {0-255} - {0-255} - {0-255} -{0-255}.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

8

STOP. This procedure is complete.

END OF STEPS

Administer Control Plane - IP Route 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

118 Issue 4

Page 119: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

5.5 Administer Control Plane - Tranport Port

5.5.1 Purpose

This procedure provides the instructions to retrieve information on, create, modify and delete aControl 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 NetworkParameters” (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. INOF-OOB (Out Fiber -Out of Band) configuration TE link can be provisioned on different CCinterfaces.

The REMOTE-PORT-AID parameter must be provisioned together with REMOTE-ROUTER-ADDRparameter.

The ENT-CP-TPORT command can be also used to create Bundle links. Link Bundling occurswhen 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 createdprovisioning 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 ofbundle 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 informationprovisioned with ENT-CP-TPORT command. The ED-CP-TPORT command can be also used toedit Bundle links.

5.5.4 Before you begin

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 groupingand/or ranging addressing.

The System shall not permit to define a Bundle link inside another Bundle link.

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

Release 5.1 (ETSI)September 2017Issue 4 1198DG09603CAAATQZZA

Page 120: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

5.5.5 Procedure

1

Select action.

To retrieve Control Plane Tranport Port information, go to Step 2.

To create Control Plane Tranport Port, go to Step 4.

To modify Control Plane Tranport Port parameters, go to Step 5.

To delete Control Plane Tranport Port, go to Step 6.

To end this procedure, go to Step 7.

2

Retrieve Control Plane Tranport Port information

Enter RTRV-CP-TPORT::AID::::[SHOW-MODE=][,FILTER=];

where: AID = Access Identifier, specifies an access to the NE CP facility. Possible values:

• MPLSIF-{1-7}-{1-9}-{2-9,12-19}-{1-10} for Local MPLS Interface

• MPLSIF-{1-7}-{1-9}-{2-9,12-19}-{1-128} for VCG MPLS Interface

• TBNDL-{10-109} Bundle Link for TMPLS)

• ALL

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Examine output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

120 Issue 4

Page 121: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 ALLexcluded.

• 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 mustbe the same of that referred by AID: AID=MPLSIF <--> REMOTE-PORT-AID=MPLSIFAID=TBNDL <--> REMOTE-PORT-AID=TBNDL

• REMOTE-ROUTER-ADDR = Neighbour router IP address.

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

Release 5.1 (ETSI)September 2017Issue 4 1218DG09603CAAATQZZA

Page 122: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

The ENT-CP-TPORT command shall be rejected if the Local Router IP address (it is the IPaddress of the NE for the Control Plane.) isn't provisioned.

5

Modify Control Plane Tranport Port parameters

Enter ED-CP-TPORT::AID::::[LINK-ADMIN-STATUS=][,REMOTE-PORT-AID=][,REMOTE-ROUTER-ADDR=][,MAX-BANDWIDTH=][,MAX-RESERVABLEBANDWIDTH=][,

METRIC=][,COLOR=][,SRLG-LIST=][,AUTH=] [,AUTHKEY=];

where:

• AID = Access Identifier, specifies an access to the facility. Possible values as for Step 2.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Delete Control Plane Tranport Port

Enter DLT-CP-TPORT::AID:;

where:

• AID = Access Identifier, specifies an access to the facility. Possible values as for Step 2.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

7

STOP. This procedure is complete.

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 aneighbor OSPF router port, to retrieve the report of routing information exchanged within the ASwhere 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 eachOSPF enabled interface over control channel termination port.

In T-MPLS application OSPF interface can be accessed through MPLS interfaces or specific virtualtunnel encapsulation TIPIP or GRE in OF-OOB configuration.

Administer Control Plane - OSPF routing 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

122 Issue 4

Page 123: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 packetauthentication 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 specificone, 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 specificone, selecting the relevant CPDPR AID.

OSPF interface operational status can be also reported. CP will perform OSPF interface report viathe RTRV-CP-OSPFIF TL1 command. The parameter list that can be retrieved is as follows:

• IP address/network mask

• OSPF Area ID

• OSPF routing timers

• Route metric

• Connection type

• Authentication (Y/N)

• Administrative status

• Operative status

Apart from retrieval of previously configured parameters, in RTRV-CP-OSPFIF CP reports theoperative status of the routing interface as a collection of different states from initial to final ,basedon OSPF routing interface state machine.

5.6.4 Before you begin

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 beOFF.

• the OSPF neighbor interface IP Address ( NEIGHBOR value), matches local OSPF interfacesubnet mask.

5.6.5 Procedure

1

Select action:

1. To modify the OSPF interface parameters, go to Step 2

1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane - OSPF routing

Release 5.1 (ETSI)September 2017Issue 4 1238DG09603CAAATQZZA

Page 124: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 portwhose 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. IfOSPFAREA-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 interfacecreation

3

To retrieve the parameters associated with OSPF on each OSPF enabled interface over controlchannel termination port

Enter:

RTRV-CP-OSPFIF::AID;

AID = Access Identifier of the OSPF interface bound to control channel termination port whoseOSPF 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.

Administer Control Plane - OSPF routing 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

124 Issue 4

Page 125: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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 tunnelpreviously created by Control Plane.

5.7.2 General

This command creates a new LSP tunnel that replaces the old LSP tunnel specified by input AIDparameter; then the command moves the traffic from the old LSP tunnel towards the new LSPtunnel 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 theyassume the same values of the deleting LSP tunnel.

The DIR, LAYER, STATUS and REVERT-MODE old tunnel parameters can't be edited and arecopied 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 partof "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 ofreplacing tunnel, but can not using the same TD ( because there is an association 1:1 betweenTunnel and TD) then the System will set up a new TD and the operator will find a new tunnelassociated 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-PRIOand 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-AIDoutput parameter. This output AID values shall be returned also in the TUNNEL-AID outputparameter of REPT^TMPLSRPLCTUNNEL message associated with this command

Command restriction:

Tunnel referenced by AID must have ACD=CP.

Tunnel referenced by AID must have ROLE=HEAD

5.7.3 Before you begin

Before performing this command:

• Tunnel specified by AID must be present

1850 TSS-320/TSS-320H/TSS-160 Administer CP Tunnels - Make Before Break

Release 5.1 (ETSI)September 2017Issue 4 1258DG09603CAAATQZZA

Page 126: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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 isremoved

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 tunnelto 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:

Administer CP Tunnels - Make Before Break 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

126 Issue 4

Page 127: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

ENT-TMPLS-TD::::::CIR=,CBS=,PIR=,PBS=;

where:

• CIR = MPLS Committed Information Rate. This parameter is valid for Tunnels andPseudoWires 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 PseudoWiresand 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 PseudoWiresand 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 isa 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, IngressLER 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 theProtected, Protecting or Backup Tunnel of the protection scheme; the command affects allthe Tunnels involved in the protection scheme

• parameters specified in this OPR command refer to the new Tunnel set up to substitute theTunnel identified by the entered AID

• the new created Tunnel has the same SRC-ADDR and DEST-ADDR (Destination Node IPAddress 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 tothe value in the Tunnel to be substituted, is taken

• The HOPLIST-ID = NO-HOPLIST allows requiring a new Tunnel without specifying anyhoplist even if the Tunnel to be replaced has an associated HOPLIST

1850 TSS-320/TSS-320H/TSS-160 Administer CP Tunnels - Make Before Break

Release 5.1 (ETSI)September 2017Issue 4 1278DG09603CAAATQZZA

Page 128: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Note: The DIR, LAYER, STATUS and REVERT-MODE old tunnel parameters can't beedited 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 atsource port in the source - destination direction. The Virtual Transport in fact is a logical entityassociated to an output port.

VT-TAIL = Pointer to Virtual Transport, AID of the Virtual Port resource. VT-TAIL is the VT atdestination port in the destination-source direction. The Virtual Transport in fact is a logicalentity associated to an output port.

Note: ACD = Access Control Domain: Local (MP) or Control Plane. It filters output tunnelson 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 setto OFF;

VT-HEAD, VT-TAIL editable in HEAD, TAIL and TRANSIT nodes only allowed to be changedfor Tunnels where STATUS = OFF

END OF STEPS

Administer CP Tunnels - Make Before Break 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

128 Issue 4

Page 129: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 tableto 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 fieldis 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 betweensource 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 identifiedby 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 Hoplistcreation, the user can enter the PATH-INDEX.

With this command the user can add new hops in the path specified by PATH-INDEX parametervalue.

In case of successful response the CP shall return these parameters in the output.Furtherly, if userneeds 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 attributeshave 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 thePATH-INDEX = 1 (adding hops) when the HOPLIST-ID is associated to a Tunnel; it is not possibleto 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-upassigned by user in the CP via ENT-CPTMPLS-HOPLIST command, for T-MPLS instance. This

1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane Hoplist

Release 5.1 (ETSI)September 2017Issue 4 1298DG09603CAAATQZZA

Page 130: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

command is used to modify the parameter attributes associated to a specific hop location definedby the key parameters (HOPLIST-ID, PATH-INDEX, HOP-INDEX).

Command restriction: It is not possible to change parameters of an HOPLIST when thecorresponding PATH is in use: it is not possible to change the PATH-INDEX = 1 related hops whenthe HOPLIST-ID is associated to a Tunnel; it is not possible to change the PATH-INDEX = 2 relatedhops 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 thecommand set.

5.8.4 Procedure

1

Select action.

To retrieve T-MPLS Control Plane Hoplist information, go to Step 2.

To create T-MPLS Control Plane Hoplist, go to Step 4.

To modify T-MPLS Control Plane Hoplist parameters, go to Step 5.

To delete T-MPLS Control Plane Hoplist, go to Step 6.

To end this procedure, go to Step 7.

2

Retrieve T-MPLS Global Network Parameters information

Enter RTRV-CPTMPLS-HOPLIST::HOPLIST-ID::::[PATH-INDEX=] [,HOP-INDEX=];

where: HOPLIST-ID =Hoplist Identifier selected by user to retrieve all the parameter list. If ALLis selected, all the entered HOPLIST-ID will be retrieved. Possible values: ALL or {1-2147483647}.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Examine output for provisioning information, as detailed in the relevant command guide, refer to“Command details” (p. 107).

Administer Control Plane Hoplist 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

130 Issue 4

Page 131: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 ofthe 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 nexthop node in the routing path. Possible values: {1-99, 101-126,128-223} - {0-255} - {0-255} -{1-254}.

1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane Hoplist

Release 5.1 (ETSI)September 2017Issue 4 1318DG09603CAAATQZZA

Page 132: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• INCL-MODE = INCLUDE or EXCLUDE the hop address set for path routing, entered viaHOP-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 applieson the indexed hop in the Hoplist. If LOOSE mode is selected, operator may specify onlyHOP-IP-ADDR for legal use.

Possible values:

− LOOSE: Next hop can be routed via different paths to the destination node.

− STRICT: Next hop is directly connected to the destination node.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

The [HOPLIST-ID=][,PATH-INDEX=] [,HOP-INDEX=] parameters are assigned by system.

5

Modify T-MPLS Control Plane Hoplist parameters

Enter ED-CPTMPLS-HOPLIST::HOPLIST-ID::::PATH-INDEX=,HOP-INDEX=[,HOP-IP-ADDR=][,HOP-UNNUM=][,LABEL-VALUE=][,INCL-MODE=][,

EXPLICIT-MODE=][,LOOSE-MODE=];

where:

• HOPLIST-ID =Hoplist Identifier selected by user for editing. The HOPLIST-ID must be uniquein the system. Possible values: {1-2147483647}.

• PATH-INDEX = {1-2}. Path Identifier as path index value. Identify a specific path componentin 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 isused 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 aPATH-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 acomponent of an assigned PATH -INDEX. Possible values: {0-1024} range.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Delete T-MPLS Control Plane Hoplist

Administer Control Plane Hoplist 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

132 Issue 4

Page 133: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 beunique in the system. Possible values: {1-2147483647}.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

7

STOP. This procedure is complete.

END OF STEPS

1850 TSS-320/TSS-320H/TSS-160 Administer Control Plane Hoplist

Release 5.1 (ETSI)September 2017Issue 4 1338DG09603CAAATQZZA

Page 134: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Administer Control Plane Hoplist 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

134 Issue 4

Page 135: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6 Detailed Level Procedure

6.1 Overview

6.1.1 Purpose

The Detailed Level Procedures (DLP) contain detailed steps and supporting information required tocomplete a task. When a DLP is referenced from another part of the manual, perform the DLP, thenreturn 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 asreference.

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

1850 TSS-320/TSS-320H/TSS-160 Detailed Level Procedure

Release 5.1 (ETSI)September 2017Issue 4 1358DG09603CAAATQZZA

Page 136: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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

Overview 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

136 Issue 4

Page 137: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

1850 TSS-320/TSS-320H/TSS-160 Overview

Release 5.1 (ETSI)September 2017Issue 4 1378DG09603CAAATQZZA

Page 138: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 portnumber and server IP address. The 1850 TSS-320, TSS-320H and TSS-160 uses port 3083 fortelnet 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

Add New User to System 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

138 Issue 4

Page 139: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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)}.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

2

Did system return a successful response?

If yes, go to Step 3.

If no, check error code message and return to Step 1 to retry command.

3

STOP. This procedure is complete.

END OF STEPS

6.3 Administer ASAP

6.3.1 Purpose

This procedure provides the instructions to retrieve information on, create, modify and delete anAlarm 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. Ifno 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.

1850 TSS-320/TSS-320H/TSS-160 Administer ASAP

Release 5.1 (ETSI)September 2017Issue 4 1398DG09603CAAATQZZA

Page 140: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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. TheAID is assigned by the NE with a sequence index number starting from 2, because indexes 0 and 1are 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 profiletype (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 instancespointing to the entered OLD ASAP, go to Step 9.

To delete ASAP, go to Step 10.

To end this procedure, go to Step 11.

2

Retrieve ASAP information

Enter RTRV-ASAP-PROF:::::[ASAPTYPE]:[USERLABEL=];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Examine output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

Administer ASAP 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

140 Issue 4

Page 141: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

[

"<ASAP-AID>,<ASAPTYPE>::DFLT=<value>,USERLABEL=<value>" cr lf

[

"::<CONDTYPE>,<NTFCNCDE>,<SRVEFF>,<LOCN>,[<DIRN>]" cr lf]*]* cr lf

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

4

Go to Step 1.

5

Create ASAP

Enter ENT-ASAP-PROF:::::PFTYPE:[DFLT=][,USERLABEL=][,CLONEFROM=];

where:

• PFTYPE = ASAP type for the ASAP that shall be created. Possible values: EQPT, BITS,TIMING, SECU, GBE, MAU, 10GBE, VCG, OGPORT, OTU, OCH, OTS, OMS, ODUn, STM1,STM4, STM16, STM64, FC200, FC400, VC4, VC44C, VC416C, VC464C, LOVC3, LOVC12,TUSEG, E1, PPSIN, PTP, PHASE

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer ASAP

Release 5.1 (ETSI)September 2017Issue 4 1418DG09603CAAATQZZA

Page 142: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6

Go to Step 1.

7

Modify ASAP parameters

Enter ED-ASAP-PROF::[ASAP-AID]:::[CONDTYPE],[NTFCNCDE],[SRVEFF],[LOCN],[DIRN]:[DFLT=][,USERLABEL=];

where:

• ASAP-AID = ASAP identifier, both for factory default {0-1} and for user defined {2-255}.Possible values: ALL, ASAPEQPT-, ASAPBITS-, ASAPTIMING-, ASAPGBE-, ASAPMAU-,ASAP10GBE-, ASAPVCG-, ASAPOGPORT-, ASAPOTU-, ASAPOTS-, ASAPOMS-,ASAPOCH-, ASAPODUn-, ASAPSTM1-/OC3-, ASAPSTM4-/OC12, ASAPSTM16-/OC48-,ASAPSTM64-/OC192-, ASAPFC200-, ASAPFC400-, ASAPVC4-/STS3-, ASAPVC44C-/STS12-, ASAPVC416C-/STS48-, ASAPVC464C-/STS192-, ASAPLOVC3-/STS1-,ASAPLOVC12-, ASAPTUSEG-, ASAPSECU-, ASAPE1-, ASAPPPSIN-, ASAPPTP-, PTP-,PHASE-

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

8

Go to Step 1.

9

Replace OLD ASAP with the NEW ASAP

Enter ED-ASAP-ASSIGN:[TID]:[OLDASAPAID],[NEWASAPAID]:[CTAG]:::[OLDUSERLABE L=],[NEWUSERLABEL=];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

10

WARNING

Optional Content

• Both null and factory default ASAPs cannot be deleted.

• The command can be issued only by users with appropriate privileges.

Delete ASAP

Enter DLT-ASAP-PROF::::::[USERLABEL=];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Administer ASAP 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

142 Issue 4

Page 143: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

11

STOP. This procedure is complete.

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 aduplex 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 twounprotected equipment entities. After successful command completion, the two specified equipmententities 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 theequipment 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. Whensuccessfully executed, the two specified equipment entities continue to operate in unprotectedmode.

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 regardlessof which copy of equipment is specified (the active copy becomes standby and the standby copybecomes 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 commandenables 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 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

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

Release 5.1 (ETSI)September 2017Issue 4 1438DG09603CAAATQZZA

Page 144: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.4.3 Before you begin

In order for a SW-DX-EQPT command to execute, the standby module has to be provisioned andphysically equipped.

6.4.4 Procedure

1

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-oneredundant (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:

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

144 Issue 4

Page 145: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

ENT-DX-EQPT::AID1,AID2;

where:

• AID1 = Equipment Access Identifier, identifies the protected equipment entity of the duplexswitching 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 duplexswitching equipment protection group.

Possible values:

− PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G

− PPUGW-{1-7}-{1-9}-{2-9,12-19} Universal GateWay Card Packet Module 2e5G

− P42E1-{1-7}-{1-9}-{2,4,6} - 1646DS 42XE1, protecting module.

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 SDEEstate. 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 isNOT allowed for MTSYNTH4 in Drop Shelf EPS.

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

Release 5.1 (ETSI)September 2017Issue 4 1458DG09603CAAATQZZA

Page 146: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Important! It is not recommended to perform a forced protection switch withoutassistance from Nokia CTAC.

5

Duplex switching equipment protection group Deletion

Enter:

DLT-DX-EQPT::AID1,AID2::::[CMDMDE=];

where:

• AID1 = Equipment Access Identifier, identifies the protected equipment entity of the duplexswitching 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 duplexswitching equipment protection group.

Possible values:

− PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G

− PPUGW-{1-7}-{1-9}-{2-9,12-19}- Universal GateWay Card Packet Module 2e5G

− P42E1-{1-7}-{1-9}-{2,4,6} - 1646DS 42XE1, protecting module

• CMDMDE = Command Mode, identifies the Command Execution Mode.

Possible values:

− NORM

− FRCD.

Note: This command fails when both protection units are in UEQ state and CMDMDE isspecified as FRCD and if the unit specified by AID2 is providing actual service (WRKsecondary state).

6

To enable (allow) automatic and manual copy switching for Redundant Equipment

Enter:

ALW-SWDX-EQPT::AID;

where:

AID = Equipment Access Identifier, identifies the equipment entity access identifier.

Possible values are

• PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G.

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

146 Issue 4

Page 147: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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 aduplex 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 to6.4 “Administer Duplex Switching Equipment Protection Group” (p. 143).

Per convention, the equipment with the lower AID position is the protected equipment, and theequipment 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 regardlessof which copy of equipment is specified (the active copy becomes standby and the standby copybecomes active).

This command applies to 1:1 protected modules only (EC320, MT320, PP10AD/ATM).

ALW-SWDX-EQPT enables (allows) automatic and manual copy switching for the specified one-for-one redundant (duplex) equipment. Either copy of equipment can be specified; the commandenables copy switching on both copies of equipment.

The command applies to the following 1:1 protected modules: PP10AD withPROVISIONEDTYPE=PP10GATM

INH-SWDX-EQPT disables (inhibits) automatic and manual copy switching for the specified one-for-one redundant (duplex) equipment. Either copy of equipment can be specified; the commanddisables 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 withPROVISIONEDTYPE=PP10GATM

This command sets the SST of PSI and sets the condition type of INHSWDX on the specified AIDand on its mate.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

6.5.3 Before you begin

In order for a SW-DX-EQPT command to execute, the standby module has to be provisioned andphysically equipped.

1850 TSS-320/TSS-320H/TSS-160 Administer Duplex Switching ATM Protection Group

Release 5.1 (ETSI)September 2017Issue 4 1478DG09603CAAATQZZA

Page 148: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.5.4 Procedure

1

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-oneredundant (duplex) equipment, go to Step 6.

• To disable (inhibit) automatic and manual copy switching for the specified one-for-oneredundant (duplex) ATM equipment, go to Step 7.

2

Retrieve information on a duplex switching ATM protection group

Enter:

RTRV-DX-EQPT::AID;

where:

AID = Equipment Access Identifier, identifies the ATM entity access identifier.

Possible values:

• PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G

• P42E1-{1-7}-{1-9}-{1-6} - 1646DS 42XE1/T1 Card.

• SCC-{1-7}-{1-9}-{7,8} - 1646DS SCC Card.

• ALL - ALL AID.

Example:RTRV-DX-EQPT::ALL;

Result:

PP10AD-1-1-6,PP10AD-1-1-9::ACTIVE=PP10AD-1-1-9,CURRREQ=NOREQ

3

Observe output. Possible request switch states (i.e. CURREQ value) are:

1. NOREQ - no request;

2. FAIL- main or spare hardware failure;

3. INHIBIT - operator inhibited the switch, i.e.no switch can been performed.

4

Perform Copy Switch for Redundant Equipment

To perform a MANUAL switch enter:

Administer Duplex Switching ATM Protection Group 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

148 Issue 4

Page 149: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

SW-DX-EQPT::AID:::[MODE];

where:

• AID = Equipment Access Identifier, identifies the equipment entity access identifier.

Possible values:

PP10AD-{1-7}-{1-9}-{2-9,12-19} for Adaptation Card Packet Modules 10G.

• P42E1-{1-7}-{1-9}-{1-6} - 1646DS 42XE1/T1 Card.

• SCC-{1-7}-{1-9}-{7,8} - 1646DS SCC Card.

• MODE = Command Mode, identifies the Command Execution Mode.

Possible values: NORM, FRCD.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Important! It is not recommended to perform a forced protection switch withoutassistance from Nokia CTAC.

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:

• AID1 = Equipment Access Identifier, identifies the protected equipment entity of the duplexswitching equipment protection group.

Possible values:

− PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G

− P42E1-{1-7}-{1-9}-{1,3,5} - 1646DS 42XE1, protected module

• AID2 = Equipment Access Identifier, identifies the protecting equipment entity of the duplexswitching equipment protection group.

Possible values:

− PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G

− P42E1-{1-7}-{1-9}-{2,4,6} - 1646DS 42XE1, protecting module

• CMDMDE = Command Mode, identifies the Command Execution Mode.

Possible values:

− NORM

− FRCD.

1850 TSS-320/TSS-320H/TSS-160 Administer Duplex Switching ATM Protection Group

Release 5.1 (ETSI)September 2017Issue 4 1498DG09603CAAATQZZA

Page 150: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Note: This command fails when both protection units are in UEQ state and CMDMDE isspecified as FRCD and if the unit specified by AID2 is providing actual service (WRKsecondary 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 copyswitching has been disabled (inhibited). In this case there is a switchback on the MAINand the SPARE reboots.

Example: dlt-dx-eqpt::PP10AD-1-1-6,PP10AD-1-1-9;

6

To enable (allow) automatic and manual copy switching for Redundant Equipment

Enter:

ALW-SWDX-EQPT::AID;

where:

AID = Equipment Access Identifier, identifies the equipment entity access identifier.

Possible value is: PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G.

P42E1-{1-7}-{1-9}-{1-6} - 1646DS 42XE1/T1 Card.

Result: This command removes the SST of PSI on the specified AID and on its mate.

Example: ALW-SWDX-EQPT::PP10AD-1-1-6;

7

To disable (inhibit) automatic and manual copy switching for the specified one-for-oneredundant (duplex) ATM equipment

Enter:

INH-SWDX-EQPT::AID;

where:

AID = Equipment Access Identifier, identifies the equipment entity access identifier.

Possible value is: PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G.

P42E1-{1-7}-{1-9}-{1-6} - 1646DS 42XE1/T1 Card.

Result: This command sets the SST of PSI and sets the condition type of INHSWDX on thespecified 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.

Administer Database Backup 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

150 Issue 4

Page 151: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 backedup includes provisioning, cross-connection, loopback, and test access information. The system alsowrites the system type, the software release identifier, the site identifier, and the backup date andtime 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 restoredusing the data on the media, the system generates a new CRC number by reading the backup dataon 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 isset against the COMMON AID. A DBF condition is cleared by successfully completing a subsequentACT-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:

1850 TSS-320/TSS-320H/TSS-160 Administer Database Backup

Release 5.1 (ETSI)September 2017Issue 4 1518DG09603CAAATQZZA

Page 152: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 6.

5

Cancel Database Backup

Enter CANC-DB-BACKUP;

6

STOP. This procedure is complete.

END OF STEPS

6.7 Administer Database Restore

6.7.1 Purpose

This procedure provides instructions to restore the system database with database informationpreviously backed up to the standby database.

6.7.2 Prerequisites

None.

Administer Database Restore 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

152 Issue 4

Page 153: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.7.3 General

The RTRV-DB-LABEL command reads the database label from the selected backup databasestored on the NE (ACT DSK DB or STDBY DB). If STDBY DB is selected and VERIFY is specifiedfor the VER parameter, a Cyclic Redundancy Check (CRC) verification of the database isperformed. 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 primarybackup 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 performprovisioning, cross-connection, manual protection switching, etc.) is allowed until the restoreddatabase 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 Typemismatch cannot be performed. A database restoral with a software release identifier or SIDmismatch 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 STDBYDB against the CRC stored for the database. A database restoral with a CRC mismatch cannot beperformed.

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 primarybackup database)

2

Examine output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer Database Restore

Release 5.1 (ETSI)September 2017Issue 4 1538DG09603CAAATQZZA

Page 154: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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. Possiblevalues:

• 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 theBACKUP-DATE and BACKUP-TIME on the system (represented in label of the Active LocalPrimary 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 softwarerelease identifier indicated for the system.

• NORM Normal: The command is denied if there is a mismatch between the SID, the softwarerelease identifier, system type or the backup time stamp of the system and the informationstored in the STBYDB.

Administer Database Restore 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

154 Issue 4

Page 155: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4

Did RESTORE-DB command complete?

If yes, go to Step 6.

If no, go to Step 5.

5

Contact Nokia for assistance .

6

STOP. This procedure is complete.

END OF STEPS

6.8 Administer Ethernet Facility

6.8.1 Purpose

This procedure provides the instructions to provision, deprovision and modify a specified GBE orGBE10 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 thismode, facilities are automatically entered when the supporting equipment is entered (See6.35 “Administer System Configuration” (p. 253)and 6.67 “Provision Equipment” (p. 385)) andfacility deletion occurs only when the supporting equipment or logical resource is deleted (See6.35 “Administer System Configuration” (p. 253) ).

6.8.3 General

Gigabit Ethernet facilities are associated with ports on a GBE module, and support GBEVCGfacilities 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 eventsdetected by the system.

When a <ETH> facility is provisioned to an OOS-MA state, a MAN condition type is set for thespecified <ETH>.

When this command is successfully executed on a port residing on a and 8XSO, 10XAR, or othermulti-rate module, the other possible facilities that could have been provisioned on that port willenter OOS-AUMA, UAS, DSBLD state.

1850 TSS-320/TSS-320H/TSS-160 Administer Ethernet Facility

Release 5.1 (ETSI)September 2017Issue 4 1558DG09603CAAATQZZA

Page 156: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

When an <ETH> is in an OOS-MA, OOS-AUMA, or OOS-AU,AINS state, no <ETH> transmissioncondition types or performance monitoring threshold crossing alerts are autonomously reported forthe <ETH>, but <ETH> alarm conditions are monitored and performance monitoring data iscollected for the <ETH> port.

The ED-<ETH> command is used to set parameters related to the encapsulation mode previouslyprovisioned using the ENT-<ETH> command.

This command manages gigabit ethernet (GBE) or the ten gigabit ethernet (GBE10) port facilitieson the following modules:

• 10XANY 10 by Any port module

• PP1GESY Data port module with sync capability

• PP1GE Data port module (10 port)

• PP1GEX20 Data port module (20 port)

• PP10GEX2 Data port module (2 port)

• PP10GESY: Data port module with sync capability (GBE)

• DWLA10X: Optical Transponder (client port) for GBE10

• PP10GESY: Data port module with sync capability for GBE10

Note: The management of facilities on PP1GE, PP1GESY, PP1GEX20, PP10GE,PP10GESY, PP1GEX2 modules is limited to the S1TRANS and TCDLY parameters. All otherfacility management on these modules is accomplished via SNMP S1TRANS and TCDLY arenot 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

1

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

Administer Ethernet Facility 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

156 Issue 4

Page 157: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 orPP10GESY

− 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 commandguide, refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer Ethernet Facility

Release 5.1 (ETSI)September 2017Issue 4 1578DG09603CAAATQZZA

Page 158: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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

For details, refer to 6.67 “Provision Equipment” (p. 385).

Ensure that port is in valid state for provisioning (OOS-MA).

5

Deprovision GBE or GBE10 client signal facility

Enter RTRV-<ETH>::AID;

where:

• <ETH> = GBE or GBE10 client signal facility.

• AID = Access identifier of <ETH> facility

6

Examine output for provisioning information on port, as detailed in the relevant command guide,refer to “Command details” (p. 107).

Administer Ethernet Facility 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

158 Issue 4

Page 159: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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.

If no, go to Step 8.

8

For details refer to 6.47 “Deprovision Equipment” (p. 308).

Note: When this command is successfully executed, the laser on the affected port shallbe turned OFF

9

Modify GBE or GBE10 client signal facility

Enter RTRV-<ETH>::AID;

where:

• <ETH> = GBE or GBE10 client signal facility.

• AID = Access identifier of <ETH> facility.

10

Examine output for provisioning information on port as detailed in the relevant command guide,refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer Ethernet Facility

Release 5.1 (ETSI)September 2017Issue 4 1598DG09603CAAATQZZA

Page 160: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 canadversely 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 andPP10GESY modules.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Administer Ethernet Facility 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

160 Issue 4

Page 161: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 havethe “DUS” message or will have the actual traceability of the signal.

This parameter is only valid for ports belonging to PP1GE, PP1GEX20 and PP1GESYmodules. PP1GE value is restricted to NONE

TCDLY = Transparent Clock Delay, indicates the delay to be considered by IEEE1588v2protocol for Transparent Clock transport. The delay is due to asymmentrical length of the fiberon the link. The length difference determines a propagation delay equal to 2*D, where D is thevalue to be provisioned.

This parameter is only valid for ports belonging to PP1GE, PP1GEX20, and PP1GESYmodules

13

STOP. This procedure is complete.

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 ofwhether 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 beendistinghished in four classes. Each class has a FROM and a TO; FROM and TO are logically andphysically 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 anoptical connection between a MUX and Line amplifier. If the line is not amplified this opticalconnection is not present in the Node itself.

Class 2: PASSTHROUGH, this connection class configures the passthrough between MUXchannels. 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. Cascadehas to be configured, when DWDM system shall operate with channels supported not only by asingle type of MUX.

1850 TSS-320/TSS-320H/TSS-160 Administer Equipment Optical Connection

Release 5.1 (ETSI)September 2017Issue 4 1618DG09603CAAATQZZA

Page 162: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Class 4: ADDRP, this connection class configures the channel added/dropped in/from DWDMsystem. Logically the optical connection moves from MUX Channel to line port of a Transponder orother tributary card.

Each class must be requested with a separate command issue; more than one class can not beprovided in a single command issue.

Each ENT-EQPT-OCONN command, successfully executed, determines the provisioning ofappropriate facilities, according configuration.

Due Hardware configuration of the MUX devices, not every optical connection class can be set upsequencially:

• 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; andviceversa Line connection for a MUX on L2 band can not be set up if it involved in a Cascadeconnection.

According the optical classes porvisoned in the command, the following table specifies associatedfacilities 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), 8omsoch(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), 8omsoch(M1W/M2W)

LINE&ADDRP (Note) ots(M1), oms(M1), 16 omsoch(M1), 1omsochif(M1/M2)

CSD&PT (Note) ots(M1E), oms(M1E), omsband(M1E),ots(M1W/M2W), oms(M1W/M2W),omsband(M1W/M2W), 16 omsoch(M1E), 8omsoch(M1W/M2W)

CSD&ADDRP (Note) ots(M1), oms(M1), 16 omsoch(M1), 1omsochif(M1/M2)

Administer Equipment Optical Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

162 Issue 4

Page 163: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

INPUT CONN CLASS Facility to be provisioned

PT&ADDRP (Note) ots(ME), oms(ME), omsband(ME), ots(MW),oms(MW), omsband(MW), 8 omsoch(ME), 8omsoch(MW), 1 omsochif(ME/MW)

LINE&CSD&PT (Note) ots(L1E), oms(M1E), omsband(M1E),ots(M1W/M2W), oms(M1W/M2W),omsband(M1W/M2W), 16 omsoch(M1E), 8omsoch(M1W/M2W)

LINE&CSD&ADDRP (Note) ots(L1), oms(M1), 16 omsoch(M1), 1omsochif(M1/M2)

LINE&PT&ADDRP (Note) ots(LE), oms(ME), omsband(ME), ots(MW),oms(MW), omsband(MW), 8 omsoch(ME), 8omsoch(MW), 1 omsochif(ME/MW)

CSD&PT&ADDRP (Note) ots(M1E), oms(M1E), omsband(M1E),ots(M1W/M2W), oms(M1W/M2W),omsband(M1W/M2W), 16 omsoch(M1E), 8omsoch(M1W/M2W), 1 omsochif(M1E/M2E/M1W/M2W)

LINE&PT&CSD&ADDRP (Note) ots(L1E), oms(M1E), omsband(M1E),ots(M1W/M2W), oms(M1W/M2W),omsband(M1W/M2W), 16 omsoch(M1E), 8omsoch(M1W/M2W), 1 omsochif(M1E/M2E/M1W/M2W)

Note: such provisioning is the result of separate ENT-EQPT-OCONN issue, one for eachoptical 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 opticalconnection between a MUX and Line amplifier. If the line is not amplified this optical connection isnot present in the Node itself.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

6.10.3 Before you begin

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

1850 TSS-320/TSS-320H/TSS-160 Administer Line Optical Connection Management

Release 5.1 (ETSI)September 2017Issue 4 1638DG09603CAAATQZZA

Page 164: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Cascade connection can not be set up if a Line connection is in place for MUX on L2 band; andviceversa Line connection for a MUX on L2 band can not be set up if it involved in a Cascadeconnection.

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 oneconnector 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 themultiplexer

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}-{EXP}

OMD BAND Passthrough Bidir Port on anOMDX8100 L1 or L2

OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15}-F{9380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240,9230, 9220, 9210, 9200}

OCH Bidir Port on an OMDX8100 L1 or L2

OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28,29-36}-L1

OTU2 Bidir Line port, on a DWLA10Xmodule

OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28,29-36}-1

OTU2 Bidir colored port, on a 1POTU2module

Administer Line Optical Connection Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

164 Issue 4

Page 165: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 oneconnector of LINE connection between a MUX and Line amplifier.

Value Description

LOFOMSPORT-{1-7}-{1-9}-{6-9,12-15}- 1 LOFA OMS Bidir port towards themultiplexer

OMDOMSPORT-{1-7}-{1-9}-{6-9,12-15} -1 OMS Bidir Port on an OMDX8100 L1 or L2

LNTO = Access Identifier identifying the TO connector to be cabled. AID can identify oneconnector of LINE connection between a MUX and Line amplifier.

Value Description

OMDBANDPORT-{1-7}-{1-9}-{6-9,12-15}-{EXP}

OMD BAND Passthrough Bidir Port on anOMDX8100 L1 or L2

OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15}-F{9380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240,9230, 9220, 9210, 9200}

OCH Bidir Port on an OMDX8100 L1 or L2

3

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 isdirected.

• RTRV-OMSBAND::AID::::[PARMS=];

where:

AID = OMSBAND Access Identifier, specifies the selected OMSBAND facility to which thecommand is directed.

• RTRV-OMSOCH::AID::::[PARMS=];

where:

AID = OMSOCH Access Identifier, specifies the selected OMSOCH facility to which thecommand is directed.

• RTRV-OTS::AID::::[PARMS=];

1850 TSS-320/TSS-320H/TSS-160 Administer Line Optical Connection Management

Release 5.1 (ETSI)September 2017Issue 4 1658DG09603CAAATQZZA

Page 166: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

where:

AID = OTS Access Identifier, specifies the selected OTS facility to which the command isdirected.

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-MAor 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:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSBAND-{1-7}-{1-9}-{6-9,12-15}-1-1 (OMSBAND Facility on anOMDX8100 L1 or L2)

• RMV-OMSOCH::AID:::[MODE];

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSOCH-{1-7}-{1-9}-{6-9,12-15}-1-F{9 380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240, 9230, 9220, 9210, 9200} (OMSOCH facility on anOMDX8100 L1 or L2).

• RMV-OTS::AID:::[MODE];

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OTS-{1-7}-{1-9}-{6-9,12-15}-1 (OTS Facility on a LOFA or on OMDX8100 L1or L2)

Note: MODE values are FRCD Forced, NORM Normal.Executing this command causes a state transition for the specified facility from: IS toOOS-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:

Administer Line Optical Connection Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

166 Issue 4

Page 167: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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).

• RST-OMSBAND::AID;

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSBAND-{1-7}-{1-9}-{6-9,12-15}-1-1 (OMSBAND Facility on anOMDX8100 L1 or L2)

• RMV-OMSOCH::AID;

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSOCH-{1-7}-{1-9}-{6-9,12-15}-1-F{9 380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240, 9230, 9220, 9210, 9200} (OMSOCH facility on anOMDX8100 L1 or L2).

• RST-OTS::AID;

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OTS-{1-7}-{1-9}-{6-9,12-15}-1 (OTS Facility on a LOFA or on OMDX8100 L1or 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 opticalconnections.

6.11.2 General

PASSTHROUGH: this connection class configures the passthrough between MUX channels. Incase of line terminal configuration, this optical connection is not present.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

6.11.3 Before you begin

DWDM facility configurations on the Node should be already present (OMS, OMSBAND, OMSCH,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).

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

Release 5.1 (ETSI)September 2017Issue 4 1678DG09603CAAATQZZA

Page 168: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Cascade connection can not be set up if a Passthrough connection is already in place.

6.11.4 Procedure

1

Retrieve the board supporting optical connection Access Identifiers.

Enter:

RTRV-EQPT-OPORT::[EQPT-AID]::::[OPORT=];

where:

EQPT-AID = Access Identifier identifying the board supporting optical ports.

Value Description

ALL

OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} G.709 OTU 10GB Card - Provisioned Type =1POTU2

DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} DWDM Optical Transponder

LOFA-{1-7}-{1-9}-{6-9,12-15} Line Optical Filter and Attenuator

OMDX8-{1-7}-{1-9}-{6-9,12-15} DWDM MUX/DEMUX 8 channels

OPORT = Access Identifier identifying the FROM connector to be cabled. AID can identify oneconnector 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 themultiplexer

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}-{EXP}

OMD BAND Passthrough Bidir Port on anOMDX8100 L1 or L2

OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15}-F{9380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240,9230, 9220, 9210, 9200}

OCH Bidir Port on an OMDX8100 L1 or L2

OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28,29-36}-L1

OTU2 Bidir Line port, on a DWLA10Xmodule

OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28,29-36}-1

OTU2 Bidir colored port, on a 1POTU2module

2

Enter:

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

168 Issue 4

Page 169: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

ENT-EQPT-OCONN::::::[PSSTRFROM=][,PSSTRTO=];

where:

PSSTRFROM = Access Identifier identifying the FROM connector to be cabled. AID can identifyonly one connector of the passthrough between MUX channels. Connectors can be channelspecific (OMDOCHPORT) or a bundle of channels (OMDBANDPORT).

Value Description

OMDBANDPORT-{1-7}-{1-9}-{6-9,12-15}-{EXP}

OMD BAND Passthrough Bidir Port on anOMDX8100 L1 or L2

OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15}-F{9380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240,9230, 9220, 9210, 9200}

OCH Bidir Port on an OMDX8100 L1 or L2

PSSTRTO = Access Identifier identifying the TO connector to be cabled. AID can identify onlyone connector of the passthrough between MUX channels. Connectors can be channel specific(OMDOCHPORT) or a bundle of channels (OMDBANDPORT).

Value Description

OMDBANDPORT-{1-7}-{1-9}-{6-9,12-15}-{EXP}

OMD BAND Passthrough Bidir Port on anOMDX8100 L1 or L2

OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15}-F{9380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240,9230, 9220, 9210, 9200}

OCH Bidir Port on an OMDX8100 L1 or L2

3

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 isdirected.

• RTRV-OMSBAND::AID::::[PARMS=];

where:

AID = OMSBAND Access Identifier, specifies the selected OMSBAND facility to which thecommand is directed.

• RTRV-OMSOCH::AID::::[PARMS=];

where:

AID = OMSOCH Access Identifier, specifies the selected OMSOCH facility to which thecommand is directed.

• RTRV-OTS::AID::::[PARMS=];

where:

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

Release 5.1 (ETSI)September 2017Issue 4 1698DG09603CAAATQZZA

Page 170: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

AID = OTS Access Identifier, specifies the selected OTS facility to which the command isdirected.

4

Remove an OMDX8 facility

The REMOVE command causes the specified facility to be placed in an out-of-service (OOS-MAor 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:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSBAND-{1-7}-{1-9}-{6-9,12-15}-1-1 (OMSBAND Facility on anOMDX8100 L1 or L2)

• RMV-OMSOCH::AID:::[MODE];

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSOCH-{1-7}-{1-9}-{6-9,12-15}-1-F{9 380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240, 9230, 9220, 9210, 9200} (OMSOCH facility on anOMDX8100 L1 or L2).

• RMV-OTS::AID:::[MODE];

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OTS-{1-7}-{1-9}-{6-9,12-15}-1 (OTS Facility on a LOFA or on OMDX8100 L1or L2)

Note: MODE values are FRCD Forced, NORM Normal.Executing this command causes a state transition for the specified facility from: IS toOOS-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:

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).

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

170 Issue 4

Page 171: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• RST-OMSBAND::AID;

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSBAND-{1-7}-{1-9}-{6-9,12-15}-1-1 (OMSBAND Facility on anOMDX8100 L1 or L2)

• RMV-OMSOCH::AID;

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSOCH-{1-7}-{1-9}-{6-9,12-15}-1-F{9 380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240, 9230, 9220, 9210, 9200} (OMSOCH facility on anOMDX8100 L1 or L2).

• RST-OTS::AID;

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OTS-{1-7}-{1-9}-{6-9,12-15}-1 (OTS Facility on a LOFA or on OMDX8100 L1or L2)

Executing this command causes a state transition for the specified facility from:

• OOS-MA to IS

• OOS-AUMA to OOS-AU.

END OF STEPS

6.12 Administer Cascade Optical Connection Management

6.12.1 Purpose

Use this procedure to configure, modify, remove and restore cascade bidirectional opticalconnections.

6.12.2 General

CASCADE: this connection class configures the cascade of MUX/DMUX devices. Cascade has tobe configured, when DWDM system shall operate with channels supported not only by a single typeof MUX.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

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

Release 5.1 (ETSI)September 2017Issue 4 1718DG09603CAAATQZZA

Page 172: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.12.3 Before you begin

DWDM facility configurations on the Node should be already present (OMS, OMSBAND, OMSCH,OTS), i.e. OMDX8(both L1 and L2 types should be present) cards and their facilities shouldconfigured.

Due Hardware configuration of the MUX devices, not every optical connection class can be set upsequencially:

• 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; andviceversa Line connection for a MUX on L2 band can not be set up if it involved in a Cascadeconnection.

6.12.4 Procedure

1

Retrieve the board supporting optical connection Access Identifiers.

Enter:

RTRV-EQPT-OPORT::[EQPT-AID]::::[OPORT=];

where:

EQPT-AID = Access Identifier identifying the board supporting optical ports.

Value Description

ALL

OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} G.709 OTU 10GB Card - Provisioned Type =1POTU2

DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} DWDM Optical Transponder

LOFA-{1-7}-{1-9}-{6-9,12-15} Line Optical Filter and Attenuator

OMDX8-{1-7}-{1-9}-{6-9,12-15} DWDM MUX/DEMUX 8 channels

OPORT = Access Identifier identifying the FROM connector to be cabled. AID can identify oneconnector 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 themultiplexer

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}-{EXP}

OMD BAND Passthrough Bidir Port on anOMDX8100 L1 or L2

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

172 Issue 4

Page 173: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Value Description

OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15}-F{9380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240,9230, 9220, 9210, 9200}

OCH Bidir Port on an OMDX8100 L1 or L2

OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28,29-36}-L1

OTU2 Bidir Line port, on a DWLA10Xmodule

OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28,29-36}-1

OTU2 Bidir colored port, on a 1POTU2module

2

Enter:

ENT-EQPT-OCONN::::::[CSDFROM=][,CSDTO=];

CSDFROM = Access Identifier identifying the FROM connector to be cabled. AID can identifyonly one connector of bidirectional CASCADE connection. This connection class configures thecascade of MUX/DMUX devices.

Value Description

OMDBANDPORT-{1-7}-{1-9}-{6-9,12-15}-{EXP}

OMD BAND Passthrough Bidir Port on anOMDX8100 L1 or L2

OMDOMSPORT-{1-7}-{1-9}-{6-9,12-15} -1 OMS Bidir Port on an OMDX8100 L1 or L2

CSDTO = Access Identifier identifying the TO connector to be cabled. AID can identify only oneconnector of bidirectional CASCADE connection. This connection class configures the cascadeof MUX/DMUX devices.

Value Description

OMDOMSPORT-{1-7}-{1-9}-{6-9,12-15} -1 OMS Bidir Port on an OMDX8100 L1 or L2

OMDBANDPORT-{1-7}-{1-9}-{6-9,12-15}-{EXP}

OMD BAND Passthrough Bidir Port on anOMDX8100 L1 or L2

3

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 isdirected.

• RTRV-OMSBAND::AID::::[PARMS=];

where:

AID = OMSBAND Access Identifier, specifies the selected OMSBAND facility to which thecommand is directed.

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

Release 5.1 (ETSI)September 2017Issue 4 1738DG09603CAAATQZZA

Page 174: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• RTRV-OMSOCH::AID::::[PARMS=];

where:

AID = OMSOCH Access Identifier, specifies the selected OMSOCH facility to which thecommand is directed.

• RTRV-OTS::AID::::[PARMS=];

where:

AID = OTS Access Identifier, specifies the selected OTS facility to which the command isdirected.

4

Remove an OMDX8 facility

The REMOVE command causes the specified facility to be placed in an out-of-service (OOS-MAor 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:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSBAND-{1-7}-{1-9}-{6-9,12-15}-1-1 (OMSBAND Facility on anOMDX8100 L1 or L2)

• RMV-OMSOCH::AID:::[MODE];

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSOCH-{1-7}-{1-9}-{6-9,12-15}-1-F{9 380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240, 9230, 9220, 9210, 9200} (OMSOCH facility on anOMDX8100 L1 or L2).

• RMV-OTS::AID:::[MODE];

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OTS-{1-7}-{1-9}-{6-9,12-15}-1 (OTS Facility on a LOFA or on OMDX8100 L1or L2)

Note: MODE values are FRCD Forced, NORM Normal.Executing this command causes a state transition for the specified facility from: IS toOOS-MA

5

Restore an OMDX8 Facility

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

174 Issue 4

Page 175: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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:

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).

• RST-OMSBAND::AID;

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSBAND-{1-7}-{1-9}-{6-9,12-15}-1-1 (OMSBAND Facility on anOMDX8100 L1 or L2)

• RMV-OMSOCH::AID;

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSOCH-{1-7}-{1-9}-{6-9,12-15}-1-F{9 380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240, 9230, 9220, 9210, 9200} (OMSOCH facility on anOMDX8100 L1 or L2).

• RST-OTS::AID;

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OTS-{1-7}-{1-9}-{6-9,12-15}-1 (OTS Facility on a LOFA or on OMDX8100 L1or 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.13 Administer ADD/DROP Optical Connection Management

6.13.1 Purpose

Use this procedure to configure, modify, remove and restore add/drop bidirectional opticalconnections.

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 othertributary card.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

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

Release 5.1 (ETSI)September 2017Issue 4 1758DG09603CAAATQZZA

Page 176: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.13.3 Before you begin

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

Retrieve the board supporting optical connection Access Identifiers.

Enter:

RTRV-EQPT-OPORT::[EQPT-AID]::::[OPORT=];

EQPT-AID = Access Identifier identifying the board supporting optical ports.

Value Description

ALL

OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} G.709 OTU 10GB Card - Provisioned Type =1POTU2

DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} DWDM Optical Transponder

LOFA-{1-7}-{1-9}-{6-9,12-15} Line Optical Filter and Attenuator

OMDX8-{1-7}-{1-9}-{6-9,12-15} DWDM MUX/DEMUX 8 channels

OPORT = Access Identifier identifying the FROM connector to be cabled. AID can identify oneconnector 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 themultiplexer

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}-{EXP}

OMD BAND Passthrough Bidir Port on anOMDX8100 L1 or L2

OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15}-F{9380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240,9230, 9220, 9210, 9200}

OCH Bidir Port on an OMDX8100 L1 or L2

OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28,29-36}-L1

OTU2 Bidir Line port, on a DWLA10Xmodule

OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28,29-36}-1

OTU2 Bidir colored port, on a 1POTU2module

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

176 Issue 4

Page 177: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

2

Enter:

ENT-EQPT-OCONN::::::[ADDRPFROM=][,ADDRPTO=];

where:

ADDRPFROM = Access Identifier identifying the TO connector to be cabled. AID can identifyonly one connector of bidirectional ADDRP connection. This connection class configures thechannel added/dropped in/from DWDM system. Logically the optical connection moves fromMUX Channel to line port of a Transponder or other tributary card.

Value Description

OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15}-F{9380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240,9230, 9220, 9210, 9200}

OCH Bidir Port on an OMDX8100 L1 or L2

OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28,29-36}-L1

OTU2 Bidir Line port, on a DWLA10Xmodule

OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28,29-36}-1

OTU2 Bidir colored port, on a 1POTU2module

EXTERNAL

ADDRPTO = Access Identifier identifying the TO connector to be cabled. AID can identify onlyone connector of bidirectional ADDRP connection. This connection class configures the channeladded/dropped in/from DWDM system. Logically the optical connection moves from MUXChannel to line port of a Transponder or other tributary card.

Value Description

OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28,29-36}-L1

OTU2 Bidir Line port, on a DWLA10Xmodule

OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28,29-36}-1

OTU2 Bidir colored port, on a 1POTU2module

OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15}-F{9380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240,9230, 9220, 9210, 9200}

OCH Bidir Port on an OMDX8100 L1 or L2

EXTERNAL

3

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 isdirected.

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

Release 5.1 (ETSI)September 2017Issue 4 1778DG09603CAAATQZZA

Page 178: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• RTRV-OMSBAND::AID::::[PARMS=];

where:

AID = OMSBAND Access Identifier, specifies the selected OMSBAND facility to which thecommand is directed.

• RTRV-OMSOCH::AID::::[PARMS=];

where:

AID = OMSOCH Access Identifier, specifies the selected OMSOCH facility to which thecommand is directed.

• RTRV-OTS::AID::::[PARMS=];

where:

AID = OTS Access Identifier, specifies the selected OTS facility to which the command isdirected.

4

Remove an OMDX8 facility

The REMOVE command causes the specified facility to be placed in an out-of-service (OOS-MAor 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:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSBAND-{1-7}-{1-9}-{6-9,12-15}-1-1 (OMSBAND Facility on anOMDX8100 L1 or L2)

• RMV-OMSOCH::AID:::[MODE];

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSOCH-{1-7}-{1-9}-{6-9,12-15}-1-F{9 380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240, 9230, 9220, 9210, 9200} (OMSOCH facility on anOMDX8100 L1 or L2).

• RMV-OTS::AID:::[MODE];

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OTS-{1-7}-{1-9}-{6-9,12-15}-1 (OTS Facility on a LOFA or on OMDX8100 L1or L2)

Note: MODE values are FRCD Forced, NORM Normal.Executing this command causes a state transition for the specified facility from: IS toOOS-MA

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

178 Issue 4

Page 179: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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:

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).

• RST-OMSBAND::AID;

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSBAND-{1-7}-{1-9}-{6-9,12-15}-1-1 (OMSBAND Facility on anOMDX8100 L1 or L2)

• RMV-OMSOCH::AID;

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OMSOCH-{1-7}-{1-9}-{6-9,12-15}-1-F{9 380, 9370, 9360, 9350, 9330, 9320,9310, 9300, 9280, 9270, 9260, 9250, 9240, 9230, 9220, 9210, 9200} (OMSOCH facility on anOMDX8100 L1 or L2).

• RST-OTS::AID;

where:

AID = Access Identifier, specifies the facility.

i.e. AID value is OTS-{1-7}-{1-9}-{6-9,12-15}-1 (OTS Facility on a LOFA or on OMDX8100 L1or 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.14 Administer GBE10 Loopback

6.14.1 Purpose

This procedure provides the instructions to administer GBE10 loopbacks.

6.14.2 Prerequisites

The GBE10 facility to be placed in loopback must have a .PST of OOS-AUMA or OOS-MA and nothave an SST of LPBK (i.e. it is not already in a loopback).

1850 TSS-320/TSS-320H/TSS-160 Administer GBE10 Loopback

Release 5.1 (ETSI)September 2017Issue 4 1798DG09603CAAATQZZA

Page 180: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.14.3 General

The RTRV-LPBK-GBE10 command retrieves the GBE10 facilities that are in a loopback within thespecified range of GBE10 AIDs. The command is executed regardless of the provisioning of thespecified facilities.

The successful response for a RTRV-LPBK-GBE10 contains one line of parsable data, in ascendingorder, for each GBE10 facility that is in a loopback within the specified range of AIDs. No outputdata 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 onthe 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 “Commanddetails” (p. 107).

6.14.4 Steps

1

NOTICE

Possibility of service interruption.

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.

To end this procedure, go to Step 18.

4

Retrieve Loopback Information

Select RTRV-LPBK-GBE10::[AID];

where:

Administer GBE10 Loopback 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

180 Issue 4

Page 181: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 specifiedrange of AIDs. No information displays for facilities that are not in loopback.

6

Go to Step 3.

7

Establish Loopback

Enter RTRV-GBE10::AID; to retrieve the current PST and SST of the GBE10 facility.

where:

AID=GBE10 access identifier

Possible values are:

• GBE10-{1-7}-{1-9}-{2-9,12-19,21-36}-1 (10 GBE Port on a DWLA10X)

8

Observe output.

9

Select action.

If the PST for the GBE10 facility is IS or OOS-AU, go to Step 10.

If the PST for the GBE10 facility is OOS-AUMA or OOS-MA, go to Step 11.

10

Before establishing a loopback, the facility must be placed out of service.

Enter ED-GBE10::AID:::::OOS;

where:

AID=GBE10 access identifier

Possible values are:

• 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).

1850 TSS-320/TSS-320H/TSS-160 Administer GBE10 Loopback

Release 5.1 (ETSI)September 2017Issue 4 1818DG09603CAAATQZZA

Page 182: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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.

Possible values are:

• FACILITY Specifies a loopback at the receive side (from the network) to the transmit side (tothe network) of the specified facility.

• TERMINAL Specifies a loopback where the signal that is about to be transmitted is connectedto 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

Examine output. One line of information displays for each facility in loopback within specifiedrange of AIDs. No information displays for facilities that are not in loopback.

15

Go to Step 3.

16

Release Loopback

Enter RLS-LPBK-GBE10::AID:::[LOCN],,,[LPBKTYPE]; to release the GBE10 loopback.

where:

AID = GBE10-{1-7}-{1-9}-{2-9,12-19,21-36}-1 (10 GBE Port on a DWLA10X)

LOCN={NEND}

LPBKTYPE={FACILITY, TERMINAL}

Note: To execute a RLS-LPBK-GBE10, the specified GBE10 must have a PST,SST ofOOS-AUMA,LPBK or OOS-MA,LPBK.

Administer GBE10 Loopback 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

182 Issue 4

Page 183: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

17

Enter ED-GBE10::AID:::::IS; to place the facility back in service.

where:

AID=Access identifier of GBE10 facility.

18

STOP. This procedure is complete.

END OF STEPS

6.15 Administer GBE Loopback

6.15.1 Purpose

This procedure provides the instructions to administer GBE loopbacks.

6.15.2 Prerequisites

To execute an OPR-LPBK-GBE, the specified GBE must have a PST of OOS-AUMA or OOS-MAand 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 thespecified range of GBE AIDs. The command is executed regardless of the provisioning of thespecified facilities.

The successful response for a RTRV-LPBK-GBE contains one line of parsable data, in ascendingorder, for each GBE facility that is in a loopback within the specified range of AIDs. No output datais 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 onthe 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 orOOS-MA,LPBK.

For parameter descriptions of TL1 commands used in this procedure, refer to the “Commanddetails” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer GBE Loopback

Release 5.1 (ETSI)September 2017Issue 4 1838DG09603CAAATQZZA

Page 184: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.15.4 Steps

1

NOTICE

Possibility of service interruption.

Performing loopbacks interrupts traffic.

2

Review the GBE loopback diagrams.

3

Select action.

To retrieve current loopback status of GBE facility, go to Step 4.

To establish loopback, go to Step 7.

To verify loopback status, go to Step 13.

To release loopback, go to Step 16.

To end this procedure, go to Step 18.

4

Retrieve Loopback Information

Select RTRV-LPBK-GBE::[AID];

where:

AID=GBE Access Identifier, specifies the GBE facility.

Possible values:

• GBE-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10 } (GBE port on a 10xAny module)

• ALL (ALL AID)

5

Examine output. One line of information displays for each facility in loopback within specifiedrange of AIDs. No information displays for facilities that are not in loopback.

6

Go to Step 3.

7

Establish Loopback

Enter RTRV-GBE::AID; to retrieve the current PST and SST of the GBE facility.

where:

Administer GBE Loopback 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

184 Issue 4

Page 185: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

AID=GBE Access Identifier, specifies the GBE facility.

8

Observe output.

9

Select action.

If the PST for the GBE facility is IS or OOS-AU, go to Step 10.

If the PST for the GBE facility is OOS-AUMA or OOS-MA, go to Step 11.

10

Before establishing a loopback, the facility must be placed out of service.

Enter ED-GBE::AID:::::OOS;

where:

AID=Access identifier of GBE facility.

11

Enter OPR-LPBK-GBE10::AID:::[LOCN],,,[LPBKTYPE];

where:

AID=Access identifier of GBE facility.

LOCN= Location, identifies the location in which the loopback is performed. Value is: {NEND} -Near End.

LPBKTYPE= Loopback Type, specifies the type of loopback.

Possible values are:

• FACILITY Specifies a loopback at the receive side (from the network) to the transmit side (tothe network) of the specified facility.

• TERMINAL Specifies a loopback where the signal that is about to be transmitted is connectedto the associated incoming receiver.

12

Go to Step 3.

13

Verify Loopback Status

Enter RTRV-LPBK-GBE::[AID]; to verify the GBE facility is in loopback status.

where:

AID=Access identifier of GBE facility.

1850 TSS-320/TSS-320H/TSS-160 Administer GBE Loopback

Release 5.1 (ETSI)September 2017Issue 4 1858DG09603CAAATQZZA

Page 186: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

14

Examine output. One line of information displays for each facility in loopback within specifiedrange of AIDs. No information displays for facilities that are not in loopback.

15

Go to Step 3.

16

Release Loopback

Enter RLS-LPBK-GBE::AID:::[LOCN],,,[LPBKTYPE]; to release the GBE loopback.

where:

AID = GBE-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10 } (GBE port on a 10xAny module)

LOCN={NEND}

LPBKTYPE={FACILITY, TERMINAL}

17

Enter ED-GBE::AID:::::IS; to place the facility back in service.

where:

AID=GBE Access Identifier, specifies the GBE facility.

18

STOP. This procedure is complete.

END OF STEPS

6.16 Administer L2 Encapsulation Profile

6.16.1 Purpose

This procedure provides the instructions to retrieve information on, create, modify and delete a L2Encapsulation Profile user defined.

6.16.2 Prerequisites

The System shall not permit to modify and/or delete the profile if referenced by a TUSEG and/orPWSEG.

6.16.3 General

This command permits to define the configuration of MAC DA and other parameters for theencapsulation 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.

Administer L2 Encapsulation Profile 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

186 Issue 4

Page 187: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.16.4 Procedure

1

Select action.

To retrieve L2 Encapsulation Profile information, go to Step 2.

To create L2 Encapsulation Profile, go to Step 5.

To modify L2 Encapsulation Profile parameters, go to Step 7.

To delete L2 Encapsulation Profile, go to Step 9.

To end this procedure, go to Step 10.

2

Retrieve L2 Encapsulation Profile information

Enter RTRV-L2ENCAP-PROF:[TID]:[AID]:[CTAG];

where:

TID = Target IDentifier, identifies the network node TID for the command. Default value is SID.Valid TID values.

AID = L2 Encapsulation Profile AID. Possible values: ALL or L2ENCAPPROF-{1-32}.

CTAG = Correlation TAG, associates the input command with its output responses.Possiblevalues are 1-6 Valid CTAG characters.

3

Examine output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer L2 Encapsulation Profile

Release 5.1 (ETSI)September 2017Issue 4 1878DG09603CAAATQZZA

Page 188: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 isSID. Valid TID values.

• CTAG = Correlation TAG, associates the input command with its output responses.Possiblevalues are 1-6 Valid CTAG characters.

• MAC-DA = Medium Access Control Address, it is the MAC Destination Address to be used incase of mapping of MPLS over Ethernet when a switched network is present. Possible valuesare 12 hexadecimal characters.

• TAG = Flag Tagged/Untagged. Possible values: UNTAGGED or TAGGED.

Administer L2 Encapsulation Profile 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

188 Issue 4

Page 189: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• VLAN-ID = This is the VLAN Identifier to be used in case of mapping of MPLS over Ethernetwhen 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}. Thedefault value is 0.

• DE = Drop Eligible indication according with 802.1ad. The possible values are 0 and 1. Thedefault value is 0.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Go to Step 1.

7

WARNING

Optional Content

The System does't permit to modify the profile if referenced by a TUSEG and/or PWSEG.

Optional Content added above. Please modify as needed.

Modify L2 Encapsulation Profile parameters

Enter ED-L2ENCAP-PROF:[TID]:AID:[CTAG]:::[MAC-DA=][,TAG=][,VLAN-ID=][,PRIORITY=][,DE=];

where:

• AID = L2 Encapsulation Profile AID. Possible values: L2ENCAPPROF-{2-32} - User definedL2 encapsulation profile.

• VLAN-ID and DE (Drop Eligible indication) are parameters not valid if profile is UNTAGGED.

The parameter values are reffered in Step 5

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

8

Go to Step 1.

9

WARNING

Optional Content

The System does't permit to delete the profile if referenced by a TUSEG and/or PWSEG.

Optional Content added above. Please modify as needed.

Delete L2 Encapsulation Profile

1850 TSS-320/TSS-320H/TSS-160 Administer L2 Encapsulation Profile

Release 5.1 (ETSI)September 2017Issue 4 1898DG09603CAAATQZZA

Page 190: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter DLT-L2ENCAP-PROF:[TID]:AID:[CTAG];

where:

• AID = L2 Encapsulation Profile AID. Possible values: L2ENCAPPROF-{2-32}.

The parameter values are reffered in Step 5

10

STOP. This procedure is complete.

END OF STEPS

6.17 Administer MAC FILE COLLECTION

6.17.1 Purpose

This procedure provides the instructions to initiate NE globally the preparation of the MAC FileCollection and retrieve this file.

6.17.2 Prerequisites

The start of the MAC File Collection preparation is allowed when no file collection preparation or filetransfer is in progress. (MACADDCOLLECTIONSTATE equal to READY / EMPTY).

It can be forced when the file preparation is in progress(MACADDCOLLECTIONSTATE equal toINPREP), but not when the file transfer is in progress (MACADDCOLLECTIONSTATE equal toFTRUNNING).

6.17.3 General

The mechanism of MAC File Collection is an efficient way of collecting MAC adrresses of the entireNE in a single file.

After issuing this command the MACADDCOLLECTIONSTATE will become INPREP (inpreparation).

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 filtersconsists 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 thelearned triplets MAC/port/vsi by the TCAM on board of the entered SLOTAID, where "port" shallbe 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 tripletsMAC/port/vsi by the TCAM on board of the entered SLOTAID, where "port" shall indicate all theequipped ports.

Administer MAC FILE COLLECTION 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

190 Issue 4

Page 191: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• If only PORTAID is entered, then the command shall start the collection of all the learned tripletsMAC/port/vsi by the TCAM on board of the equipped slots, where port shall be equal toPORTAID.

• If neither SLOTAID nor PORTAID is entered, then the command shall start the collection of allthe learned triplets MAC/port/vsi by the TCAM on board of the equipped slots, where "port" shallindicate all the equipped ports.

The MAC File Collection then generated will contain one line (record) fr every retrieved MACaddress in the NE according to the input filtering.

When the MAC File Collection is complete (MACADDCOLLECTIONSTATE equal to READY) thefile is directly available in gzip (compressed) format.

6.17.4

The RTRV-MACGLB-STATUS command retrieves the current status of the MAC File Collectionprocess.

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. Thiscould be e.g. after the first start of the NE.

• READY: The MAC File is available. Once the MAC file was successfully created, it iscompressed via gzip and the state READY is entered. In this state a MAC file is available (onlyin gzip format), which can be either retrieved via COPY-RFILE. A COPY-RFILE command wouldbe accepted in the READY state, which starts the MAC file transfer from the NE to themanagement 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 commandthe 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 wouldbe not accepted in the INPREP state, which starts the file transfer from the NE to themanagement system for the MAC file.

• FTRUNNING: File Transfer is currently running.

The FTRUNNING state would be entered with the COPY-RFILE command requesting the MACfile transfer between the NE and the management system. No other file transfer for MAC file canbe started in this state. The state will be left by canceling the file transfer by CANC-COPY-FILEor 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.

1850 TSS-320/TSS-320H/TSS-160 Administer MAC FILE COLLECTION

Release 5.1 (ETSI)September 2017Issue 4 1918DG09603CAAATQZZA

Page 192: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 Step8

• 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.

If no, go to Step 5.

5

Is the MACADDCOLLECTIONSTATE value INPREP or FTRUNNING?

If yes, wait until the MACADDCOLLECTIONSTATE becomes READY.

6

Is the MACADDCOLLECTIONSTATE value READY?

To perform a new MAC file collection, go to Step 7.

To retrieve the gzip file, go to Step 8.

7

Start the MAC File Collection

Enter STA-MACGLB:::::[MAC],[PORTAID],[SLOTAID],[FDBIDVLAN],[FDBIDVPLS],[FDBIDPBB],[TYPE];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

8

Retrieve the gzip MAC File Collection

Administer MAC FILE COLLECTION 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

192 Issue 4

Page 193: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Verify the MAC File Collection is complete (i.e. MACADDCOLLECTIONSTATE equal toREADY).

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 commandcompletion.

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 (MediumAccess Unit) represents the physical layer termination for a sub-set of Ethernet ports.

6.18.2 Prerequisites

The facility provisioning mode of this NE is automatic, i.e., PROVMODE = AUTOEQ-AUTOFC, thenthis means that command cannot be used to enter/delete facilities. In this mode, facilities areautomatically entered when the supporting equipment is entered (See 6.35 “Administer SystemConfiguration” (p. 253)). Besides in this mode, facility deletion occurs only when the supportingequipment 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,SSTstate for the specified MAU port. The MAU port's current provisioned values and conditions (ifprovisioned), and state are retrieved from the system database. The command is executedregardless 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 Ethernetports.

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

1850 TSS-320/TSS-320H/TSS-160 Administer MAU Facility

Release 5.1 (ETSI)September 2017Issue 4 1938DG09603CAAATQZZA

Page 194: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• PP1GESY Data port module with sync capability

• PP1GE Data port module (10 port)

• PP1GEX20 Data port module (20 port)

The management of facilities on PP1GE, PP1GESY, PP1GEX20 modules is limited to theS1TRANS and TCDLY parameters. All other facility management on these modules isaccomplished 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 specifiedMAU. Secondary states associated with the MAU after the command is executed depend uponevents detected by the system.

6.18.4 Procedure

1

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 commandguide, refer to “Command details” (p. 107).

4

Modify MAU facility parameters

Possibility of service interruption. Editing port parameters of a traffic bearing port canadversely affect service.

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}.

Administer MAU Facility 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

194 Issue 4

Page 195: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 byIEEE1588v2 protocol for Transparent Clock transport. The delay is due to asymmetrical lengthof 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 theone in the opposite direction, value to be configured is positive; if length from transmitter toreceiver is lower than the one in the opposite direction, value to be configured is negative.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Note: S1TRANS parameter is only valid for ports belonging to PP1GE, PP1GEX20 andPP1GESY modules. The parameter value is restricted to NONE for PP1GE and forelectrical FE ports on any module

Note: TCDLY parameter is only valid for ports belonging to PP1GE, PP1GEX20, andPP1GESY modules

6

STOP. This procedure is complete.

END OF STEPS

6.19 Administer MAU Loopback

6.19.1 Purpose

This procedure provides the instructions to administer MAU loopbacks.

6.19.2 Prerequisites

The MAU facility to place in loopback must have a Primary State (PST) of OOS-AUMA or OOS-MA.

6.19.3 General

The RTRV-LPBK-MAU command retrieves the MAU facilities that are in a loopback within thespecified range of MAU AIDs. The command is executed regardless of the provisioning of thespecified facilities.

The successful response for a RTRV-LPBK-MAU contains one line of parsable data, in ascendingorder, for each MAU facility that is in a loopback within the specified range of AIDs. No output datais 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 onthe specified MAU facility.

The RLS-LPBK-MAU command releases the loopback previously established by an OPR-LPBK-MAU command on the specified MAU facility.

1850 TSS-320/TSS-320H/TSS-160 Administer MAU Loopback

Release 5.1 (ETSI)September 2017Issue 4 1958DG09603CAAATQZZA

Page 196: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

To execute a near-end or far-end RLS-LPBK-MAU, the specified MAU must have a PST of IS.

For parameter descriptions of TL1 commands used in this procedure, refer to the “Commanddetails” (p. 107).

6.19.4 Steps

1

NOTICE

Possibility of service interruption.

Performing loopbacks interrupts traffic.

2

Review the MAU loopback diagrams.

3

Select action.

To retrieve current loopback status of MAU facility, go to Step 4.

To establish loopback, go to Step 7.

To verify loopback status, go to Step 13.

To release loopback, go to Step 16.

To end this procedure, go to Step 19.

4

Retrieve Loopback Information

Select RTRV-LPBK-MAU::[AID];

where:

AID=MAU access identifier

Possible values:

• ALL (ALL AID)

• MAU-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1-10} - MAU port on a 10xAny module.

5

Examine output. One line of information displays for each facility in loopback within specifiedrange of AIDs. No information displays for facilities that are not in loopback.

6

Go to Step 3.

Administer MAU Loopback 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

196 Issue 4

Page 197: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

7

Establish Loopback

Enter RTRV-MAU::AID; to retrieve the current PST and SST of the MAU facility.

where:

AID=MAU access identifier

Possible values are:

• 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

Before establishing a loopback, the facility must be placed out of service.

Enter ED-MAU::AID:::::OOS;

where:

AID=MAU access identifier

Possible values are:

• 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}.

LOCN= Location, identifies the location in which the loopback is performed. Value is: {NEND} -Near End.

LPBKTYPE= Loopback Type, specifies the type of loopback.

Possible values are:

• FACILITY Specifies a loopback at the receive side (from the network) to the transmit side (tothe network) of the specified facility.

• TERMINAL Specifies a loopback where the signal that is about to be transmitted is connected

1850 TSS-320/TSS-320H/TSS-160 Administer MAU Loopback

Release 5.1 (ETSI)September 2017Issue 4 1978DG09603CAAATQZZA

Page 198: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

to the associated incoming receiver.

12

Go to Step 3.

13

Verify Loopback Status

Enter RTRV-LPBK-MAU::[AID]; to verify the MAU facility is in loopback status.

where:

AID=MAU Access Identifier

14

Examine output. One line of information displays for each facility in loopback within specifiedrange of AIDs. No information displays for facilities that are not in loopback.

15

Go to Step 3.

16

Release Loopback

Enter RLS-LPBK-MAU::AID:::[LOCN],,,[LPBKTYPE]; to release the MAU loopback.

where:

AID=MAU Access Identifier

LOCN={NEND}

LPBKTYPE={FACILITY, TERMINAL}

Note: To execute a RLS-LPBK-MAU, the specified MAU must have a PST,SST of OOS-AUMA,LPBK or OOS-MA,LPBK.

17

Enter ED-MAU::AID:::::IS; to place the facility back in service.

where:

AID=MAU Access Identifier

18

Go to Step 3.

19

STOP. This procedure is complete.

END OF STEPS

Administer MAU Loopback 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

198 Issue 4

Page 199: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.20 Administer Network Interface

6.20.1 Purpose

This procedure provides the instructions to retrieve, provision and delete a network interface on aspecified DCC channel on an optical port for data communication purposes.

6.20.2 Prerequisites

None

6.20.3 General

A maximum of 32 DCC channels (line and/or section DCC) can be provisioned.

The interfaces supporting DCC channels can not be derived by more than 16 boards.

The interfaces supporting DCC channels can not be more than 4 for the same board.

The ENT-NETIF command creates a network interface on a specified DCC channel on an opticalport for data communication purposes. The network interface can be provisioned on the line/MS orsection/RS DCC of the specific STMn facility. The DCC is identified by means of the STM-n AID andthe DCCCHNL parameter.

The ED-NETIF command allows the operator to modify the various network interface parameterson a specified DCC channel on an optical port for data communication purposes. The networkinterface must be first provisioned on the line or section DCC of the specific STMn facility via theENT-NETIF command. The DCC is identified by means of the STM-n AID and the DCCCHNLparameter.

The RTRV-NETIF command retrieves the network interface which uses a specified DCC channel onan optical port. The network interface can be provisioned on the line or section DCC of the specificSTMn 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 DCCchannel on an optical port (via ENT-NETIF) and disables DCC communication on that link. Thenetwork interface can be provisioned on the line or section DCC of the specific STMn facility. TheDCC 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

1850 TSS-320/TSS-320H/TSS-160 Administer Network Interface

Release 5.1 (ETSI)September 2017Issue 4 1998DG09603CAAATQZZA

Page 200: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter RTRV-NETIF::AID;

where AID=Access IDentifier, specifies the OCn/STMn or OTS facility.

3

Provision Network Interface

Enter ENT-NETIF::AID::::[DCCCHNL=][,IP=][,INTISIS=][,L2SIDE=][,L3QOS=],LLMODE= [,OSI=][,OSIAREA=][,CHNLUSEDBY= ];

where AID=Access IDentifier, specifies the OCn/STMn or OTS facility.

Example: In the following example, ENT-NETIF is used to create a TCP/IP over LAPD protocolstack with the NE being the user side on the Layer 2 connection, and establish that the OSPFwill be used as routing algorithm on the specified Multiplex Section DCC of the STM16 facility:ENT-NETIF::STM16-1-1-3-1:C000:::DCCCHNL=LINE,IP=Y,L2SIDE=USER,LLMODE =LAPD;

4

Delete Network Interface

Enter DLT-NETIF::AID::::[DCCCHNL=];

where AID=Access IDentifier, specifies the OCn/STMn or OTS facility.

5

Modify Network Interface

Enter ED-NETIF::AID::::[DCCCHNL=][,IP=][,INTISIS=][,L2SIDE=][,OSI=][,OSIAREA=];

where AID=Access IDentifier, specifies the OCn/STMn or OTS facility.

Example: In the following example, ED-NETIF is used to enable the Integrated IS-IS protocolon 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 IProuting table.

6.21.2 Prerequisites

None.

6.21.3 General

This procedure allows the operator to enter (add) and retrieve all the IP routes contained in the IProuting table.

Administer NE IP Route 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

200 Issue 4

Page 201: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Retrieved IP routes can be static routes edited via the ENT-NE-IPRT command or dynamic routesgenerated by OSPF or Integrated IS-IS software.

If the AID specifies a STM-n then the DCCCHNL parameter must be specified, and the NEXTHOPparameter should not be specified.

If the AID specifies the LAN, then the NEXTHOP parameter must be specified, and the DCCCHNLparameters 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 IProute's parameters specified define univocally the entry in the IP routing table that has to bedeleted. If a match with all the specified parameters cannot be found, an error message will bereturned 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

1

Select action:

• Retrieve IP routes in the IP routing table, go to Step 2

• Provision a new static IP route in the IP routing table, go to Step 5

• Deprovision a new static IP route in the IP routing table, go to Step 6

2

Retrieve IP routes

Enter RTRV-NE-IPRT:::;

3

Examine output for provisioning information on NE, as detailed in the relevant command guide,refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer NE IP Route

Release 5.1 (ETSI)September 2017Issue 4 2018DG09603CAAATQZZA

Page 202: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 thenext hop network interface or identifies the IP Tunnel or Customer LAN. Possible values aspreviously described.

• DESTADDR = Destination Address, it is the IP address of the destination host or network (inthe format nnn-nnn-nnn-nnn). The address 0-0-0-0 is used to specify a default route. IfNETMASK is not all '1' (i.e., a network route is specified), the host portion of the DESTADDRmust 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). Themask 0-0-0-0 is used to specify a default route. Possible values as previously described.

Administer NE IP Route 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

202 Issue 4

Page 203: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Deprovision a new static IP route in the IP routing table

Enter DLT-NE-IPRT::AID:::DESTADDR,MASK[,DCCCHNL];

where:

• AID = Access IDentifier, specifies the STMn facility carrying the DCC with the next hopnetwork 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 (inthe format nnn-nnn-nnn-nnn). Possible values: {1-99, 101-126,128-223} - {0-255} - {0-255} -{0-254}.

• MASK = IP Mask, it is the IP subnet mask of the route (in the format nnn-nnn-nnn-nnn).Possible values: {0-255} - {0-255} - {0-255} - {0-255}.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

7

STOP. This procedure is complete.

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.

6.22.2 Prerequisites

None.

6.22.3 General

This procedure allows the operator to create an IP tunnel instance on the NE. The IP tunnel thathas to be created is specified by its AID. If the AID specified matches any of the ID for existing IPtunnels, 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 notsupported.

The remote OSI System at the other end the tunnel can be addressed either by NSAP address orby TID; those input parameters are mutually exclusive, but one of those must be specified.

1850 TSS-320/TSS-320H/TSS-160 Administer NE IP Tunnel

Release 5.1 (ETSI)September 2017Issue 4 2038DG09603CAAATQZZA

Page 204: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The delete procedure allows the operator to delete an IP tunnel associated with the NE. The IPtunnel that has to be deleted is specified by its ID parameter. If the ID specified does not match withany of the ID for existing IP tunnels, an error message will be returned in response.

6.22.4 Procedure

1

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. Possiblevalues: ALL for all AID or IPT-{1-128} for Internet Protocol Tunnel.

3

Examine output for provisioning information on NE, as detailed in the relevant command guide,refer to “Command details” (p. 107).

Administer NE IP Tunnel 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

204 Issue 4

Page 205: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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. Possiblevalues: IPT-{1-128} for Internet Protocol Tunnel.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

5

Delete an IP tunnel instance on the NE

Enter RTRV-NE-IPT::AID:;

where: AID = IP Tunnel Identifier, it is the identifier of the specific IP tunnel to retrieve. Possiblevalues: ALL (ALL AID) or IPT-{1-128} (Internet Protocol Tunnel).

1850 TSS-320/TSS-320H/TSS-160 Administer NE IP Tunnel

Release 5.1 (ETSI)September 2017Issue 4 2058DG09603CAAATQZZA

Page 206: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6

Examine output for provisioning information on NE, as detailed in the relevant command guide,refer to “Command details” (p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

[

"<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. Possiblevalues: IPT-{1-128} (Internet Protocol Tunnel).

8

STOP. This procedure is complete.

END OF STEPS

Administer NE IP Tunnel 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

206 Issue 4

Page 207: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.23 Administer Network Time Protocol (NTP)

6.23.1 Purpose

This procedure provides the instructions to retrieve the NTP server IP address, provision NTPservers, and delete NTP servers. It also provides instructions to enable NTP, modify NTPparameters, and disable NTP.

6.23.2 Prerequisites

None

6.23.3 General

NTP servers are used for time of day synchronization when the NTP protocol is enabled. If no NTPserver has been entered and the NTP protocol is enabled, the time-of-day clock will synchronizewith the last known internal clock frequency.

When NTP is enabled, the NE internal time-of-day clock uses the calculated Coordinated UniversalTime (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 toan 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. TheNE is polling the NTP server and periodically making corrections to its internal clock so as tomaintain the same clock time as the NTP server.

• Non-synchronized, holdover mode—NTP is enabled and the NE has lost NTP serverconnectivity 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 serveramong equally usable and qualified servers. In the case where more than one server is determinedto be the optimum server, the server with the preferred attribute is selected. The ENT-NTP-ADDRcommand is used to provision NTP servers.

The RTRV-NTP-ADDR command is used to retrieve the attributes and service states of alldesignated 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 internalclock will adopt the last value of the NTP server time as its set time and will continue to calculatetime stamps using the provisioned offset.

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

Release 5.1 (ETSI)September 2017Issue 4 2078DG09603CAAATQZZA

Page 208: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.23.4 Procedure

1

Enter RTRV-NTP;

2

Examine output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

"::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.

To end this procedure, go to Step 19.

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

208 Issue 4

Page 209: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4

Retrieve NTP Server IP Addresses

Enter RTRV-NTP-ADDR;

5

Examine output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

"::NETADDR=<value>:<PST>[,SST] " cr lf

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

6

Go to Step 3.

7

Provision NTP Server IP Addresses

Enter ENT-NTP-ADDR::::::NETADDR==x;

where: x = IP address of an NTP server. Possible values: {{0-99,101-126,128-223}-{0-255}-{0-255}-{0-255}}.

8

Go to Step 3.

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

Release 5.1 (ETSI)September 2017Issue 4 2098DG09603CAAATQZZA

Page 210: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

9

Delete NTP Server IP Addresses

Enter DLT-NTP-ADDR::::::IP=x;

where: x = IP address of an NTP server to be deleted. Possible values: {{0-99,101-126,128-223}-{0-255}-{0-255}-{0-255}}.

10

Go to Step 3.

11

Enable NTP

Enter RTRV-NTP-ADDR;

12

Observe output, as described in Step 5.

13

Is an NTP server provisioned?

If yes, go to Step 14.

If no, go to step 7 to provision an NTP server.

14

Enter ED-NTP::::::NTP=[,OFFSET=];

where: NTP = Enable or disable time synchronization from the NTP server. Possible values:ENABLE or DISABLE. Factory Default is DISABLE

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

15

Go to Step 19.

16

Modify NTP Parameters

Enter ED-NTP::::::[NTP=],OFFSET=;

where OFFSET = Time offset to apply to NTP server UTC time, +/- HH-MM, for all events andtime stamps reported by this NE. Possible values: { +,- }{ 00-23 }-{ 00-59}. Factory default is+00-00.

17

Go to Step 19.

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

210 Issue 4

Page 211: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

18

Disable NTP

Enter ED-NTP::::::NTP=DISABLE;

19

STOP. This procedure is complete.

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 specifiedAID(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-NEcommand and the TRC_NGHBRDISC parameter. When enabled, the discovery trace message issent as the default trace message. Note that provisioning a non-default trace message on an STMnoverrides the sending of the discovery message (See ED-STMn).

The RTRV-NEIGHBORS command retrieves a list of the immediate STMn neighbor(s) of thespecified AID(s), that have been previously captured by reading a discovery trace messagetransmitted 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 theNeighbor NE, and the NE TID, if available.

RTRV-SECTRC retrieves the contents of the Regenerator SectionTrace. This command may beused to retrieve the “incoming” accepted Regenerator Section Trace, the expected RegeneratorSection 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 onthe outgoing signal. The expected and transmitted Regenerator Section Trace is provisioned via theED facilities command. If no TRACEMSG has been returned and the command did not fail, thesystem will output the /“ /” string.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

6.24.3 Before you begin

ED-IP-ADDR must be entered before procedure execution.

1850 TSS-320/TSS-320H/TSS-160 Administer STMn Neighbor Discovery

Release 5.1 (ETSI)September 2017Issue 4 2118DG09603CAAATQZZA

Page 212: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 hostIP address and the AID of the transmitting facility are encoded on the 16 byte TRC messageaccording to ITU-G-7714.1.

Note: The setting of this parameter does not affect already provisioned trace messages orfacilities 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-2board is inserted and provisioned.

6.25.2 Prerequisites

Verify the board is in appropriate slot (02 to 09 - 12 to 19 - 21 to 28 - 29 to 36).

Administer ODU2 Facility 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

212 Issue 4

Page 213: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.25.3 General

The ED-ODU2 command is used to edit parameters related to the ODU2 tributary for specifiedclient/line facility.

The ENT-ODU2 command is not supported. The ODU2 object entity shall be automatically createdon the client side by the system when the Client OTU2 facility os created. The ODU2 object entityshall be automatically created on the line side by the system when the OT circuit pack isprovisioned.

The ODU2 object entity shall be automatically created on the line side by the system when theOT2TDM module is provisioned..

6.25.4 Procedure

1

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 aDWLA10X module

• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{L1}-1 for ODU2 facility in an OTU2 onOT2TDM module.

3

Examine output for provisioning information on port, as detailed in the relevant command guide,refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer ODU2 Facility

Release 5.1 (ETSI)September 2017Issue 4 2138DG09603CAAATQZZA

Page 214: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 onthe client side by the system when the Client OTU2 facility is created (see 6.67 “ProvisionEquipment” (p. 385)). The ODU2 object entity shall be automatically created on the line side bythe system when the OT circuit pack is provisioned (see 6.67 “Provision Equipment” (p. 385))..

6

Remove and restore ODU2 tributary for specified client/line facility

Enter RTRV-ODU2::AID;

where: AID = Access Identifier, specifies an access Identifier to the OT client or line port.Possible values:

• ALL

Administer ODU2 Facility 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

214 Issue 4

Page 215: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{C1, L1}-1 for ODU2 facility in an OTU2 on aDWLA10X module

• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{L1}-1 for ODU2 facility in an OTU2 onOT2TDM module

7

Examine output for provisioning information on port, as detailed in the relevant command guide,refer to “Command details” (p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

"<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 facilityin an OTU2 on a DWLA10X module.

1850 TSS-320/TSS-320H/TSS-160 Administer ODU2 Facility

Release 5.1 (ETSI)September 2017Issue 4 2158DG09603CAAATQZZA

Page 216: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 aDWLA10X module.

10

Modify ODU2 tributary for specified client/line facility

Enter RTRV-ODU2::AID;

where: AID = Access Identifier, specifies an access Identifier to the OT (client or line) port.Possible values:

• ALL

• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{C1, L1}-1 for ODU2 facility in an OTU2 on aDWLA10X module

• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{L1}-1 for ODU2 facility in an OTU2 onOT2TDM module

11

Examine output for provisioning information on port as detailed in the relevant command guide,refer to “Command details” (p. 107).

Administer ODU2 Facility 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

216 Issue 4

Page 217: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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]

;

Possibility of service interruption. Editing port parameters of a traffic bearing port canadversely affect service.

12

Enter ED-ODU2::AID::::[,ALMPROF=][,TCAPROF=]:[PST],[SST];

where: AID = Access Identifier, specifies an access Identifier to the OT (client or line) port.Possible values:

• ALL

• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{C1, L1}-1 for ODU2 facility in an OTU2 on aDWLA10X module

• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{L1}-1 for ODU2 facility in an OTU2 onOT2TDM module

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer ODU2 Facility

Release 5.1 (ETSI)September 2017Issue 4 2178DG09603CAAATQZZA

Page 218: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

13

STOP. This procedure is complete.

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 clientsignal facility.

The OTU2 object entity is automatically created on the line side by the system when the OTU-2 isinserted and provisioned

6.26.2 Prerequisites

Verify the board is in appropriate slot (02 to 09 - 12 to 19 - 21 to 28 - 29 to 36).

The ED-OTU2 command is supported for the line ports on the OT2TDM module.

6.26.3 General

The ENT-OTU2 on the line side is not supported. The OTU2 object entity shall be automaticallycreated 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, thenthis command cannot be used to enter facilities. In this mode, facilities are automatically enteredwhen 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-OTU2command.

Executing an ED-OTU2 command causes the following primary state transitions for the specifiedOTM0.2 facility. Secondary states associated with the OTM0.2 facility after the command isexecuted depend upon events detected by the system.

Refer to the 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1Command Guide for details on parameter values.

6.26.4 Procedure

1

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

Administer OTU2 Facility 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

218 Issue 4

Page 219: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

2

Retrieve OTU2 facility information

Enter RTRV-OTU2::AID;

where: AID = Access Identifier, specifies an access Identifier to the OT client or line port.Possible values:

• ALL for all AID

• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port, OT2TDM orDWLA10X module

• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module -OTU2, STM-64, 10GE.

3

Examine output for provisioning information on port, as detailed in the relevant command guide,refer to “Command details” (p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

"<AID>::[AINSTH=<value>][,AINSTIMER=<value>] [,FECTYPE=<value>][,

ALMPROF=<value>][,TCAPROF=<value>] [,OTU2CHNL=<value>][,MGRACD=

<value>]:<PST> [,<SST>]" cr lf

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

4

Provision OTU2 facility

1850 TSS-320/TSS-320H/TSS-160 Administer OTU2 Facility

Release 5.1 (ETSI)September 2017Issue 4 2198DG09603CAAATQZZA

Page 220: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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. Possiblevalues:− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module

- OTU2, STM-64, 10GE.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Deprovision OTU2 facility

Enter RTRV-OTU2::AID;

where: AID = Access Identifier, specifies an access Identifier to the OT client or line port.Possible values:

• ALL

• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port, OT2TDM orDWLA10X module

• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module -OTU2, OC192, STM-64, 10GE, 10GFC)

7

Examine output for provisioning information on port, as detailed in the relevant command guide,refer to “Command details” (p. 107).

Administer OTU2 Facility 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

220 Issue 4

Page 221: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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>][,

ALMPROF=<value>][,TCAPROF=<value>] [,OTU2CHNL=<value>][,MGRACD=

<value>]:<PST> [,<SST>]" cr lf

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

8

Enter DLT-OTU2::AID;

where:

• AID = Access Identifier, specifies an access Identifier to the OT client port (client AID).Possible values: OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on aDWLA10X module - OTU2, OC192, STM-64, 10GE, 10GFC.

9

Enter RMV-OTU2::AID;

where:

• AID=Access Identifier, specifies an access Identifier to the OT client port (client AID).Possible values:− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port, OT2TDM or

DWLA10X module

− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module- OTU2, OC192, STM-64, 10GE, 10GFC

1850 TSS-320/TSS-320H/TSS-160 Administer OTU2 Facility

Release 5.1 (ETSI)September 2017Issue 4 2218DG09603CAAATQZZA

Page 222: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

10

Enter RST-OTU2::AID;

where:

• AID=Access Identifier, specifies an access Identifier to the OT client port (client AID).Possible values:− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port, OT2TDM or

DWLA10X module

− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module- OTU2, OC192, STM-64, 10GE, 10GFC

11

Modify OTU2 facility

Enter RTRV-OTU2::AID;

where: AID = Access Identifier, specifies an access Identifier to the OT (client or line) port.Possible values:

• ALL

• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port, or OT2TDM orDWLA10X module

• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port or on a DWLA10X module -OTU2, STM-64, 10GE )

12

Examine output for provisioning information on port as detailed in the relevant command guide,refer to “Command details” (p. 107).

Administer OTU2 Facility 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

222 Issue 4

Page 223: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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>][,

ALMPROF=<value>][,TCAPROF=<value>] [,OTU2CHNL=<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 canadversely affect service.

13

Enter ED-OTU2::AID::::[AINSTH=][,FECTYPE=][,ALMPROF=] [,TCAPROF=][,

OTU2CHNL=]:[PST],[SST];

where: AID = Access Identifier, specifies an access Identifier to the OT (client or line) port.Possible values:

• ALL

• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port, or OT2TDM orDWLA10X module

• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port or on a DWLA10X module -OTU2, STM-64, 10GE )

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer OTU2 Facility

Release 5.1 (ETSI)September 2017Issue 4 2238DG09603CAAATQZZA

Page 224: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

14

STOP. This procedure is complete.

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 pathprotected cross-connection entity and establishes a one-way (unidirectional) or two-way(bidirectional) SNCP cross connection between the specified rate facilities.

6.27.2 Prerequisites

To establish an VCn cross-connection, the required facilities must be provisioned. Refer to6.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 twoVCn 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 specifiedVCn facilities.

The ENT-CRSPROT-VCn command is used to create a protected connection between the specifiedVCn 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 orENT-CRSPROT-VCn commands.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

Administer Path Protected Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

224 Issue 4

Page 225: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.27.4 Procedure

1

Select action.

To retrieve VCn path protected cross-connection information, go to Step 2.

To create VCn path protected cross-connection, go to Step 5.

To modify VCn path protected cross-connection, go to Step 6.

To delete VCn path protected cross-connection, go to Step 7.

To end this procedure, go to Step 9.

2

Retrieve VCn/STSn Path Protected Cross-Connection Information

Enter RTRV-CRSPROT-<rate>::AID;

where:

rate

Values are:

• for ETSI: VC4, VC44C, VC416C, VC464C, LOVC12, LOVC3

AID = Access Identifier.

It specifies the selected facility(ies) to which the command is directed. AID of ALL retrieves allthe cross connects in the system.

3

Observe output.

4

Go to Step 1.

5

Create VCn Path Protected Cross-Connection

Enter ENT-CRSPROT-<rate>::FROMPED,FROMPING,TO:::[CCT]:[CKTID=][,RVRTV=][,RVRTTIM=][,HLDFFTIM=][,PTYPE=];

where:

rate

Values are:

• for ETSI: VC4, VC44C, VC416C, VC464C, LOVC12, LOVC3

FROMPED = AID of connection point;

MVC4TU12-{1-7}-{1-9}-{7}-{1-16}-{1-3}- {1-7}-{1-3} - for TU12 within a MVC4 on SCC card on1646 Drop shelf

MVC4TU3-{1-7}-{1-9}-{7}-{1-16}-{1-3} - for TU3 within a MVC4 on SCC card on 1646 Drop shelf

1850 TSS-320/TSS-320H/TSS-160 Administer Path Protected Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 2258DG09603CAAATQZZA

Page 226: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Indicates the FROMPED (protected receive side from the network, protected source of cross-connection) facility of the cross-connection.

FROMPING = AID of connection point.

Indicates the FROMPING (protecting receive side from the network, protecting source of cross-connection) facility of the cross-connection.

TO = AID of connection point.

MVC4TU12-{1-7}-{1-9}-{7}-{1-16}-{1-3}- {1-7}-{1-3} - for TU12 within a MVC4 on SCC card on1646 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 willuse the default value. Refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide for details on parameter values.

6

Modify Protected Cross-Connections

ED-CRSPROT-<rate>::FROMPED,FROMPING,TO:::[CCT]:[CKTID=][,RVRTV=][,

RVRTTIM=][,HLDFFTIM=][,PTYPE=];

where:

rate

Values are:

• for ETSI: VC4, VC44C, VC416C, VC464C, LOVC12, LOVC3

FROMPED = AID of connection point.

Indicates the FROMPED (protected receive side from the network, protected source of cross-connection) facility of the cross-connection.

FROMPING = AID of connection point.

Indicates the FROMPING (protecting receive side from the network, protecting source of cross-connection) facility of the cross-connection.

TO = AID of connection point.

Indicates the TO (transmit side to the network, sink of cross-connection) facility of the cross-connection.

7

Delete Protected Cross-Connections

DLT-CRSPROT-<rate>::FROMPED,FROMPING,TO:::[CCT];

where:

Administer Path Protected Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

226 Issue 4

Page 227: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

rate

Values are:

• for ETSI: VC4, VC44C, VC416C, VC464C, LOVC12, LOVC3

FROMPED = AID of connection point.

Indicates the FROMPED (protected receive side from the network, protected source of cross-connection) facility of the cross-connection.

FROMPING = AID of connection point.

Indicates the FROMPING (protecting receive side from the network, protecting source of cross-connection) facility of the cross-connection.

TO = AID of connection point;

Indicates the TO (transmit side to the network, sink of cross-connection) facility of the cross-connection.

8

Go to Step 1.

9

STOP. This procedure is complete.

END OF STEPS

6.28 Administer Per Hop Behaviour Profile (PHBprofile)

6.28.1 Purpose

This procedure provides the instructions to create, modify and delete a Per Hop Behaviour Profileuser defined.

6.28.2 Prerequisites

None

6.28.3 General

A PHB is the externally observable forwarding behavior applied at a DS-compliant (Diff-Serv) nodebelonging to a DS domain.

A set of “data treatments” (defined as PSCs) are requested to be applied to packets on each NEinside 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;

1850 TSS-320/TSS-320H/TSS-160 Administer Per Hop Behaviour Profile (PHBprofile)

Release 5.1 (ETSI)September 2017Issue 4 2278DG09603CAAATQZZA

Page 228: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Queue types (either Strict Priority queue or Weighted Fair Queue).

In the System already exists the factory default PHB Profile, its AID is PHBPROF-1.

In the System exists also a second factory PHB Profile its AID is PHBPROF-2.

6.28.4 Procedure

1

Enter RTRV-PHB-PROF;

To retrieve one or all Per Hop Behaviour Profile stored in the System.

2

Examine output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

Figure 13 PSC set and related CIR,PIR,CBS and PBS relationship

Administer Per Hop Behaviour Profile (PHBprofile) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

228 Issue 4

Page 229: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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-1and 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 arefactory 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/orPWSegment.

Enter ED-PHB-PROF::AID:::[EXP0],[EXP1],[EXP2],[EXP3], [EXP4],[EXP5],

[EXP6],[EXP7];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

END OF STEPS

6.29 Administer Radius server

6.29.1 Purpose

Use this procedure to add, modify, retrieve and delete RADIUS server attributes.

1850 TSS-320/TSS-320H/TSS-160 Administer Radius server

Release 5.1 (ETSI)September 2017Issue 4 2298DG09603CAAATQZZA

Page 230: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.29.2 General

RADIUS is a networking protocol, based on RADIUS servers, that provides centralizedAuthentication, Authorization and Accounting (AAA) services.

The user sends a connection request to a Network Access Server (NAS), which acts as RADIUSclient 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 NASrequest. In turn the NAS accepts or, respectively, rejects the user connection.

The following Figure shows the general RADIUS scenario.

The NAS role is covered by the NE.

The Figure shows the messages exchange between the user, the NE and the RADIUS server, forthe three possible cases of authentication and authorization.

When the RADIUS server receives an access request, it searches a database of users to find theuser whose name matches the request. If the username is found and the password is correct, theRADIUS 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 userpassword shall be encrypted by a shared key (between the NE and the RADIUS server). Thisshared 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 thatthe client can communicate with a server for authentication.

Figure 14 RADIUS general scenario

Administer Radius server 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

230 Issue 4

Page 231: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 whichare provisioned through ENT-RADIUS-SERVER command.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

6.29.3 Before you begin

Make sure that an alarms free 1850-TSS320 system with LAN port on MT320 needs to beconnected to PC. NE needs to be connected to the Network Management System and RADIUSserver.

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 shallbe an ascii string between 5 to 32 characters. The secret key must be encrypted on the NEusing AES or 3DES.

Example: The following example illustrates the command and associated output forprovisioning the attributes of a RADIUS server number, IP address, secret key (zxcvbn).ENT-RADIUS-SERVER::RAD1:132-117-112-192,,zxcvbn;

1850 TSS-320/TSS-320H/TSS-160 Administer Radius server

Release 5.1 (ETSI)September 2017Issue 4 2318DG09603CAAATQZZA

Page 232: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 yes, go to Step 3.

If no, go to Step 7

7

To delete the Radius server enter:

DLT-RADIUS-SERVER:::::SERVERNUM;

where:

SERVERNUM = valid server number to provision the server.

END OF STEPS

6.30 Administer Security Log File

6.30.1 Purpose

This procedure provides the instructions to retrieve all output response messages generated by thesystem and to provision the security log file parameters.

6.30.2 Prerequisites

Retrieving the security log file and provisioning security log file parameters can only be performedby administrators with security privileges.

Administer Security Log File 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

232 Issue 4

Page 233: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 toinactivity timeout)

RTRV-AUDIT-SECULOG retrieves the security log entries that were generated by the systembetween the specified FRDATM (From Date and Time) to the specified TODATM (To Date andTime) 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 securitylog. The LOGEVENT parameter specifies the list of events that are to be recorded in the securitylog.

The following parameter options are available:

• EIUA—Records logins, logoffs, invalid user authentication attempts and the alarms/alertsgenerated due to the invalid authentication attempts. Commands creating log events of this typeare: 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. Commandscreating 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 standardoperations and maintenance procedures. This does not address creations and modificationscarried offline. Commands creating log events of this type are all the commands not mentionedin 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'sdisk 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.

1850 TSS-320/TSS-320H/TSS-160 Administer Security Log File

Release 5.1 (ETSI)September 2017Issue 4 2338DG09603CAAATQZZA

Page 234: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

2

Provision Security Log Parameters

Enter RTRV-ATTR-SECULOG; to retrieve current security log parameter values.

3

Examine output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

"::LOGEVENT=<value>,UPSLG=<value>[,WARN=<value>]" cr lf

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

4

Enter SET-ATTR-SECULOG::::::[,LOGEVENT=][,UPSLG=][,WARN=];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

5

Enter RTRV-ATTR-SECULOG; to verify changes.

6

Go to Step 9.

Administer Security Log File 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

234 Issue 4

Page 235: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

7

Retrieve Security Log File

Enter RTRV-AUDIT-SECULOG:::::["FRDATM","TODATM"],[UID];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

8

Observe output.

9

STOP. This procedure is complete.

END OF STEPS

6.31 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.

6.31.2 Prerequisites

An STMn module must be provisioned before STMn facilities can be provisioned. Refer to6.67 “Provision Equipment” (p. 385) to provision STMn modules.

6.31.3 General

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

6.31.4

1

Enter RTRV-STMn::AID;

where:

STMn=Optical Facility type (STM1, STM4, STM16, STM64)

AID=STMn Access Identifier

2

Examine output for provisioning information on port.

3

Does facility have PST and SST of OOS-MA,UAS?

1850 TSS-320/TSS-320H/TSS-160 Administer STMn Facility

Release 5.1 (ETSI)September 2017Issue 4 2358DG09603CAAATQZZA

Page 236: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

If yes, go to Step 4.

If no, the ED-STMn command cannot be performed on the specified STMn facility. Go to Step5.

4

Enter ED-<STMn>:[TID]:AID:[CTAG]:::[AINSTH=][,S1TRANS=][,ALSENB=][,PMODE=][,AINSCRIT=][,PSTCORR=][,SDSFMODE=][,BRSTINTVL=][,BRSTTH=][,

SDTH=][,SFTH=][,RSBRSTINTVL=][,RSBRSTTH=][,TRCSENTMODE=][,TRC=][,

TRCRCVMODE=][,TRCEXPECTED=][,TRCMON=][,TRCCONSACT=][,ALMPROF=][,

TCAPROF=][,CMDMDE=][,HOS TRUCT=]:[PST],[SST];

where:

STMn=STM1, STM4, STM16, STM64

AID=STMn Access Identifier

Other parameters are optional. If a value is not entered for these parameters, the system willuse the default value. Refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide for details on parameter values.

Example: In the following example, STM-16 port 1 of slot 5, HOSTRUCT is set to a mix of AU4and 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:AU4If the operator wants only to change a sub-part of the payload structure, he still needs tospecify the complete payload structure for the whole port bandwidth. If in the previousexample the payload of the 3. AUG4 shall be changed from AU44c to 4xAU4, then thefollowing 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. Inthat case the following command needs to be issued:

ED-STM16::STM16-1-1-5-1::::HOSTRUCT=8xDC-1xAU44C-4xDC;

Administer STMn Facility 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

236 Issue 4

Page 237: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

5

STOP. This procedure is complete.

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, anddeprovision STM-n facility protection groups.

6.32.2 Prerequisites

The working and protection STM-n facilities in facility protection groups must be provisioned.

6.32.3 General

An STM-n facility protection group consists of a pair of adjacent STM-n facilities: one protect facilityand one working facility.

The types of facility protection groups that can be provisioned on a port-pair basis with thiscommand 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 twodifferent 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 AUntributaries 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 twodifferent 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 embeddedAUn tributaries within the protection bandwidth of the east and west port will be deleted. If one ofthese 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 thecorresponding 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 wherethe 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. Uponsuccessful completion of ED-FFP-<STMn> parameter changes will be applied to the protectiongroup and the system will send areport database change message.

1850 TSS-320/TSS-320H/TSS-160 Administer STM-n Facility Protection Group

Release 5.1 (ETSI)September 2017Issue 4 2378DG09603CAAATQZZA

Page 238: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

If the NodeId for the node is changed, then also all entries in squelch and ring map referencing theold 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 theDLT-FFP-<STMn> command, the protection group is deleted, and the working facilities that havebeen disassociated from facility protection function as unprotected facilities. In addition theprotection facility can be used again for normal unprotected traffic.

The DLT-FFP-<STMn> command can only be executed against STMn facilities that are provisionedas a protection group (e.g., provisioned via the ENT-FFP-<STMn> command). Successfulexecution of the DLT-FFP-<STMn> command results in the SST of STBYH, STBYS, and WRKbeing cleared on the protecting and working STMn facilities.

The successful completion of a DLT-FFP-<STMn> command for linear 1+1 MSP FFP instance alsocreates the embedded AUn tributaries according to the factory default payload structure of theprotection port.

The successful completion of a DLT-FFP-<STMn> command for MS-SPRing FFP instance alsocreates the embedded AUn tributaries in the former protection bandwidth according to the factorydefault payload structure of the east and west port.

The successful completion of a DLT-FFP-<STMn> command for a MS-SPRing FFP also deletes themap instances associated with the protection group, i.e. ring map and squelch map.

6.32.4 Procedure

1

Select action.

To retrieve STM-n facility protection group, go to Step 2.

To provision STM-n facility protection group, go to Step 5.

To modify linear STM-n facility protection group attributes, go to Step 7.

To deprovision STM-n facility protection group, go to Step 9.

To end the procedure, go to Step 11.

2

Retrieve STM-n Facility Protection Group

Enter RTRV-FFP-<STMn>::AID;

where:

• <STMn> = rate of the facility protection group used as command modifier. Possible values:− STM1 for FFP with STM-1 rate.

− STM4 for FFP with STM-4 rate.

− STM16 for FFP with STM16 rate.

− STM64 for FFP with STM-64 rate.

• AID = STM-n facility protection group. Possible values:− FFPSTM64-{1-7}-{1-9}-{2-9,12-19,21-36 }-1 for STM64 Facility Protection Group

Administer STM-n Facility Protection Group 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

238 Issue 4

Page 239: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

− FFPSTM16-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7} for STM16 Facility Protection Group ona 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

Examine output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

[

"AID::PTYPE=<value>[,RVRTV=<value>][,RVRTTIM=<value>][,HLDFFTTIM

=<value>][,WKG=<value>[,PROTN=<value>][,PSDIRN=<value>][,ACTIVE=

<value>][,CURRREQ=<value>][,PENDREQ=<value>][,EAST=<value>][,WEST=

<value>][,NODEID=<value>][,NODEDESCR=<value>],NODESTATUS=<value>][,

EASTACTIVE=<value>][,EASTCURRREQ=<value>][,EASTPENDREQ=<value>][,

WESTACTIVE=<value>][,WESTCURRREQ=<value>][,WESTPENDREQ=<value>]" cr

lf]*

[

/*

<Command_Echo>

<CTAG>

(<Session_Number>)

*/ cr lf]

;

4

Go to Step 1.

5

Provision STM-n Facility Protection Group

1850 TSS-320/TSS-320H/TSS-160 Administer STM-n Facility Protection Group

Release 5.1 (ETSI)September 2017Issue 4 2398DG09603CAAATQZZA

Page 240: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 valuespreviously described.

• AID = Access identifier of the FFP. Possible values previously described.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Go to Step 1.

7

Modify Linear STM-n Facility Protection Group Attributes

Enter ED-FFP-<STMn>::AID::::[,RVRTV=][,RVRTTIM=][,HLDFFTTIM=][,NODEID=][,NODEDESCR=];

where:

• <STMn> = rate of the facility protection group used as command modifier. Possible valuespreviously described.

• AID = Access identifier of the FFP. Possible values previously described.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

8

Go to Step 1.

9

Deprovision STM-n Facility Protection Group

Enter DLT-FFP-<STMn>::AID:;

where:

• <STMn> = ate of the facility protection group used as command modifier. Possible valuespreviously described.

• AID = Access identifier of the FFP. Possible values previously described.

10

Go to Step 1.

Administer STM-n Facility Protection Group 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

240 Issue 4

Page 241: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

11

STOP. This procedure is complete.

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.

6.33.2 Prerequisites

The STMn facility to place in loopback must have a Primary State (PST) of OOS-AUMA or OOS-MA.

6.33.3 General

Loopbacks are test features that can be set to loop a signal back at different points along the signalpath. 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. TheAlarm 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 stillforwarded to the network. See Figure 16, “Terminal Loopback” (p. 242).

Figure 15 Facility Loopback

1850 TSS-320/TSS-320H/TSS-160 Administer STMn Loopback

Release 5.1 (ETSI)September 2017Issue 4 2418DG09603CAAATQZZA

Page 242: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

For parameter descriptions of TL1 commands used in this procedure, refer to the “Commanddetails” (p. 107).

6.33.4 Steps

1

NOTICE

Possibility of service interruption.

Performing loopbacks may interrupt service if a protection line or protecting path is notavailable.

2

Review the loopback diagrams in Figures Figure 15, “Facility Loopback” (p. 241) and Figure16, “Terminal Loopback” (p. 242).

3

Select action.

To retrieve current loopback status of STMn facility, go to Step 4.

To establish STMn loopback, go to Step 7.

To verify loopback status, go to Step 13.

To release loopback, go to Step 16.

To end this procedure, go to Step 19.

Figure 16 Terminal Loopback

Administer STMn Loopback 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

242 Issue 4

Page 243: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4

Retrieve Loopback Information

Select RTRV-LPBK-STMn::[AID];

where:

STMn=Optical facility type (STM1, STM4, STM16, or STM64).

AID=STMn Access Identifier

5

Examine output. One line of information displays for each facility in loopback within specifiedrange of AIDs. No information displays for facilities that are not in loopback.

6

Go to Step 3.

7

Establish Loopback

Enter RTRV-STMn::AID; to retrieve current PST and SST of facility.

where:

STMn=Optical facility type (STM1, STM4, STM16, or STM64).

AID=STMn Access Identifier

8

Observe output.

9

Select action.

If the PST for the facility is IS or OOS-AU, go to Step 10.

If the PST for the facility is OOS-AUMA or OOS-MA, go to Step 11.

10

Before establishing a loopback, the facility must be placed out of service.

Enter ED-STMn::AID:::::OOS;

where:

STMn = STM1, STM4, STM16, STM64

AID=STMn Access Identifier

11

Enter

1850 TSS-320/TSS-320H/TSS-160 Administer STMn Loopback

Release 5.1 (ETSI)September 2017Issue 4 2438DG09603CAAATQZZA

Page 244: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

OPR-LPBK-STMn::AID:::[LOCN],,,[LPBKTYPE]:[LPBKCONSACT=];

where:

• STMn = The rate of the loopback used as command modifier.

STM1 for a STM-1 loopback

STM4 for a STM-4 loopback

STM16 for a STM-16 loopback

STM64 for a STM-64 loopback

• AID=STMn Access Identifier

Specifies the STM-n port facility. The rate of the port identified by AID must match thecommand rate modifier.

• LOCN=NEND

• LPBKTYPE={TERMINAL, FACILITY}

12

Go to Step 3.

13

Verify Loopback Status

Enter RTRV-LPBK-STMn::[AID]; to verify the STMn facility is in loopback status.

where:

STMn=Optical facility type (STM1, STM4, STM16, or STM64).

AID=STMn Access Identifier

14

Examine output. One line of information displays for each facility in loopback within specifiedrange of AIDs. No information displays for facilities that are not in loopback.

15

Go to Step 3.

16

Release Loopback

Enter RLS-LPBK-STMn::AID:::[LOCN],,,[LPBKTYPE];

where:

STMn=Optical facility type (STM1, STM4, STM16, or STM64).

AID=STMn Access Identifier

LOCN=NEND

LPBKTYPE={TERMINAL, FACILITY}

Administer STMn Loopback 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

244 Issue 4

Page 245: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

17

Enter ED-STMn::AID:::::IS; to place the facility back in service.

where:

STMn=Optical facility type (STM1, STM4, STM16, or STM64).

AID=STMn Access Identifier

18

Go to Step 3.

19

STOP. This procedure is complete.

END OF STEPS

6.34 Administer STMn MS-SPRING

6.34.1 Purpose

This procedure provides the instructions to retrieve information on, provision, and deprovision aBidirectional Line Switched Ring (MS-SPRING) in which two fiber facilities are used to transporttraffic 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 isconnected 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.

6.34.2 Prerequisites

Two STM-16 or STM-64 facilities must be provisioned using the ENT-STMn command, beforeprotection groups can be established.

To modify MS-SPRING squelch maps and ring maps manually, the automap feature must bedisabled.

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 a1+1 MSP protection group.

The 1850 TSS-320, TSS-320H and TSS-160 node supports as many as 20 MS-SPRING STM16MS-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 andTSS-160 node and up to 4 MS-SPRING STM64 rings.

1850 TSS-320/TSS-320H/TSS-160 Administer STMn MS-SPRING

Release 5.1 (ETSI)September 2017Issue 4 2458DG09603CAAATQZZA

Page 246: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• STMn MS-SPRING rings may co-exist with other SNCP protection groups, other 1+1 protectiongroups, 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 onenode.

− MS-SPRING Switch initiation criteria includes external initiated switching commands, andautomatic initiated switching request.

− Automatic switching is initiated by the 1850 TSS-320, TSS-320H and TSS-160 nodedetecting either MSP channel signaled commands including LP-S, FS-R, MS-R, andautomatic initiated requests including SF-R, SD-R, RR-R, and WTR.

− External switch commands (OPR-PROTNSW-STMn) can be entered to manually initiateprotection switching of MS-SPRING. Refer to 6.32 “Administer STM-n Facility ProtectionGroup” (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 anddeprovisioning 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 enteredvia 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 nodesappear 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 everyprovisioned 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 toeach node on a ring. The NODEID is a number from zero to 15; therefore a maximum of 16 nodeson a 2-fiber MS-SPRING are allowed. The node ID an be edited when both MS-SPRING facilitiesare locked out or in the forced switch state. The local node ID can be changed when the auto mapfeature is enabled or disabled.

EAST (and/or WEST) parameter of the ENT-FFP-STM16/64 command is used to identify theaccess identifier of the east (and/or west) side port of a MS-SPRing FFP.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

6.34.4

1

Select action.

To provision STMn MS-SPRING Node, go to Step 2.

Administer STMn MS-SPRING 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

246 Issue 4

Page 247: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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.

To end this procedure, go to Step 37.

2

CONFIGURE STM-16 or STM-64 FACILITY IN WORKING SLOT OF STMn PAIR (WESTFACILITY)

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 ofSTMn pair (west facility).

where:

STMn=Optical facility type (STM-16 or STM-64).

AID=STM-16 or STM-64 access identifier

Other parameters are optional. If a value is not entered for these parameters, the system willuse the default value. Refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide for details on parameter values.

3

Repeat Step 2 to configure protection STMn facility (East facility).

4

Will ring maps and squelch maps be manually entered or automatically learned?

If manually entered, go to Step 11.

If automatically learned, go to Step 5.

5

Enable DCC

Select action.

To enable DCC on line of STMn, go to Step 6.

To enable DCC on section of STMn, go to Step 9.

6

Enter ENT-NETIF::AID::::[DCCCHNL=][,IP=][,INTISIS=][,L2SIDE=][,L3QOS=],LLMODE=[,OSI=][,OSIAREA=][,CHNLUSEDBY= ];;

where:

AID=Protected (west) STM-16 or STM-64 access identifier

1850 TSS-320/TSS-320H/TSS-160 Administer STMn MS-SPRING

Release 5.1 (ETSI)September 2017Issue 4 2478DG09603CAAATQZZA

Page 248: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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

Enter ENT-NETIF::AID::::[DCCCHNL=][,IP=][,INTISIS=][,L2SIDE=][,L3QOS=],LLMODE=[,OSI=][,OSIAREA=][,CHNLUSEDBY= ];

where:

AID=Protected (west) STM-16 or STM-642 AID

DCCCHNL=SECTION, DCC Channel is a Section/RS DCC.

10

Repeat Step 9 for protecting (east) STM-16 or STM-64.

11

Enable MS-SPRING Operation

Enter ENT-FFP-<STMn>:[TID]:[AID]:[CTAG]:::PTYPE=[,RVRTV=][,RVRTTIM=][,HLDFFTTIM=][,WKG=][,PROTN=][,PSDIRN=][,PROTOCOL=][,EAST=][,WEST=][,

NODEID=][,NODEDESCR=]; to enable MS-SPRING node operation.

where:

STMn=Optical facility type (STM-16 or STM-64).

WEST=Access identifier of west STMn in MS-SPRING

EAST=Access identifier of east STMn in MS-SPRING

NODEID=Local node identifier. Must be unique within a MS-SPRING. {0-15}

Other parameters are optional. If a value is not entered for these parameters, the system willuse the default value.

For parameter descriptions of TL1 commands used in this procedure, refer to the1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1Command 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

Administer STMn MS-SPRING 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

248 Issue 4

Page 249: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 switchingon the entire ring. If any working traffic is using the ring protection channels, this commandcauses working traffic to be switched back to the working channels regardless of the conditionof the working channels.

WEST: Execute the requested switch action on the facility/span toward the west side of the MS-SPRing

16

Enter OPR-PROTNSW-<STMn>::AID:::LOP-S:EAST;

where:

AID=FFPSTM-16 or FFPSTM-64 access identifier of MS-SPRING Facility Protection Group

AID=West STMn facility access identifier

17

Enter ED-RINGMAP::AID::::RINGMAP=;

where:

AID=FFPSTM-16 or FFPSTM-64 access identifier of MS-SPRING Facility Protection Group

RINGMAP=Sequence of node IDs within a MS-SPRING. (0-15) Ampersand (&) grouping isused to join each node ID value (up to 15 values). The first RINGMAP value defines the nodeID of the adjacent MS-SPRING node (east side). Subsequent RINGMAP values define thenode ID of the MS-SPRING node (in the eastward side). The last RINGMAP value defines thenode ID of the adjacent MS-SPRING node (west side).

Go to Step 13.

18

Enter RTRV-RINGMAP::[AID]; to verify the new ring map.

where:

AID=FFPSTM-16 or FFPSTM-64 access identifier of MS-SPRING Facility Protection Group

1850 TSS-320/TSS-320H/TSS-160 Administer STMn MS-SPRING

Release 5.1 (ETSI)September 2017Issue 4 2498DG09603CAAATQZZA

Page 250: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

19

Enter RLS-PROTNSW-<STMn>:[TID]:AID:[CTAG]::LOP-S:WEST;

where:

AID=FFPSTM-16 or FFPSTM-64 access identifier of MS-SPRING Facility Protection Group

AID=West STMn facility access identifier

LOP-S: Clear a previously existing Lockout of Protection-Span.

WEST Execute the requested clear action on the facility/span toward the west side of the MS-SPRing

20

Enter RLS-PROTNSW-<STMn>:[TID]:AID:[CTAG]::LOP-S:EAST;

where:

STMn=Optical facility (STM-16 or STM-64)

AID=East STMn facility access identifier

EAST: Execute the requested clear action on the facility/span toward the east side of the MS-SPRing

21

Every node in the ring needs an entry for the MS-SPRING Ring Map. Are there other nodes toperform this procedure on in the MS-SPRING Ring?

If yes, go to Step 12.

If no, go to Step 1.

22

Modify MS-SPRING Squelch Map

Enter RTRV-SQLMAP::AID; to retrieve current squelch map.

where:

AID=AU4n access identifier or FFPSTM16/STM-64 facility protection group access identifier

23

Observe output. Note values for ENTRY and EXIT parameters. (A value of 255 means the nodeID 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 thesource node in the MS-SPRING.

Administer STMn MS-SPRING 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

250 Issue 4

Page 251: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

EXIT= Node identifier of the destination node for a path in MS-SPRing ring. Node ID (0-15) ofthe 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 connectionsof the MS-SPRING that need squelch map entries?

If yes, go to Step 27.

If no, go to Step 1.

27

Modify MS-SPRING Node ID

Enter RTRV-FFP-STMn::[AID];

where:

AID=FFPSTM-16 or FFPSTM-64 access identifier of MS-SPRING Facility Protection Group

AID=STM-16/STM-64 access identifier

28

Observe output and note current value of NODEID parameter.

29

Enter OPR-PROTNSW-<STMn>::AID:::LOP-S:WEST;

where:

STMn=Optical facility (STM-16 or STM-64)

AID=East STMn facility access identifier

30

Enter OPR-PROTNSW-<STMn>::AID:::LOP-S:EAST;

where:

STMn=Optical facility (STM-16 or STM-64)

AID=West STMn facility access identifier

31

Enter ED-FFP-STMn::AID::::,NODEID=;

where:

STMn=Optical facility type (STM-16 or STM-64)

1850 TSS-320/TSS-320H/TSS-160 Administer STMn MS-SPRING

Release 5.1 (ETSI)September 2017Issue 4 2518DG09603CAAATQZZA

Page 252: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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:

STMn=Optical facility (STM-16 or STM-64)

AID=West STMn facility access identifier

33

Enter RLS-PROTNSW--<STMn>::AID:::LOP-S:EAST;

where:

STMn=Optical facility (STM-16 or STM-64)

AID=East STMn facility access identifier

34

Enter RTRV-FFP-STMn::[AID]; to verify new node ID value.

where:

STMn=Optical facility type (STM-16 or STM-64)

AID=FFPSTM-16/FFPSTM64 facility protection group access identifier

35

Go to Step 1.

36

Deprovision STMn MS-SPRING Facilities

Enter DLT-FFP-STMn::AID; to deprovision MS-SPRING node application.

where:

AID=FFPSTM16/FFPSTM64 facility protection group access identifier

STMn=Optical facility type (STM-16 or STM-64).

Note: The STMn protection pair must be in an unswitched state to allow the protectionpair to be deleted. Clear any switched states on the pair.

37

STOP. This procedure is complete.

END OF STEPS

Administer STMn MS-SPRING 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

252 Issue 4

Page 253: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 ofNE Application.

6.35.2 Prerequisites

After the first ACT-USER, edit the password, close the telnet session login again ACT-USER withnew 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-NEare 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 PROVMODEparameter, it cannot be changed without scratching and resetting the database.

• The type of provisioning that is set through PROVMODE parameter could be changed during NElife without scratching and resetting the database.

• DB backup and restore have to record and check the region. It should not be allowed to restorean 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).

1850 TSS-320/TSS-320H/TSS-160 Administer System Configuration

Release 5.1 (ETSI)September 2017Issue 4 2538DG09603CAAATQZZA

Page 254: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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=];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Administer System Configuration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

254 Issue 4

Page 255: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4

STOP. This procedure is complete.

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 IntegratedTiming Source (BITS) timing and to switch system clock synchronization from one reference to theother.

6.36.2 Prerequisites

None.

6.36.3 General

The NE utilizes external Building Integrated Timing Supply (BITS) timing to synchronize the system.The system is externally timed to either a Primary or Secondary BITS reference. The redundantsynchronization subsystem acts in an active/standby relationship.

DS1 BITS timing enters the system either directly via the backplane (Rear Access Shelf) or viadedicated front plane integral (a panel just below the fan) (Front Access Shelf). BITS timing isthrough-connected to the redundant Clock Reference Unit (CRU). The CRUs reside on the matrixmodules (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 processcan 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 tothe same synchronization source selected by the active one. Both CRUs receive the samereference sources.

The supported clock modes (operational states of a clock) follows:

• Locked mode (normal mode)—Steady state. The SETG generated clock signal is controlled bythe 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 andis using data previously acquired (when it was operating in the normal mode) to control its outputsignal.

• Free-running mode—Temporary operating mode. The operating condition when the output signalis 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 BITSfacilities for clock synchronization purposes.

1850 TSS-320/TSS-320H/TSS-160 Administer System Timing/BITS

Release 5.1 (ETSI)September 2017Issue 4 2558DG09603CAAATQZZA

Page 256: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The ED-BITS command modifies the provisioning of one or more ports dedicated to BITS facilitiesfor 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 orSecondary) clock reference source for system clock synchronization. It is also used to switch thesystem 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 orBITS-{1-7}-{1-9}-{0,1} (Default= ALL).

3

Examine output for provisioning information, as detailed in the relevant command guide, refer to“Command details” (p. 107).

Administer System Timing/BITS 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

256 Issue 4

Page 257: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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.

1850 TSS-320/TSS-320H/TSS-160 Administer System Timing/BITS

Release 5.1 (ETSI)September 2017Issue 4 2578DG09603CAAATQZZA

Page 258: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• FRCD - for node working in SDH mode.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

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. Thefollowing 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 referencestatus 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 forSystem Timing

8

STOP. This procedure is complete.

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 clocksynchronization from one reference to the other.

6.37.2 General

The ED-SYNCN command modifies the provisioning for the following entities:

• system timing

Administer Clock references - Synchronization 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

258 Issue 4

Page 259: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The system timing entity controls the timing selection. It covers everything related to the NEinternal clock and the system timing selection process. One instance will be created/deleted inthe 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 timingselection 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 beassigned 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 toswitch to another reference or to Holdover.

Executing an ED-SYNCN command causes the following primary state transitions for the specifiedtiming 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 alarmreporting service

Executing a RMV-SYNCN command causes a state transition for the specified system timingreference 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 aMAN 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 areautonomously 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 timingreference from:

• OOS-MA to IS-NR

1850 TSS-320/TSS-320H/TSS-160 Administer Clock references - Synchronization

Release 5.1 (ETSI)September 2017Issue 4 2598DG09603CAAATQZZA

Page 260: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

When a system timing reference transits from the OOS-MA to an IS-NR state, the MAN conditiontype 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 ofparsable output data, listing data for timing entities (matrix boards host the Clock ReferenceUnits (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 oneline 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. Thefollowing switch hierarchy is valid w.r.t. acceptance of the switch commands:− LOCKOUT is the highest request and always accepted

Administer Clock references - Synchronization 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

260 Issue 4

Page 261: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

− 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 referencestatus 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 forSystem 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 portconnected 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 forSystem Timing)

PROVQL specifies the provisioned quality level of a timing reference. Two different methodsare supported; i.e. the quality level is either derived from the incoming SSM value or a fixedquality value is set. The value AUTO is only allowed for ports supporting SSM.

Possible values are:

• 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-TRec. 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)

1850 TSS-320/TSS-320H/TSS-160 Administer Clock references - Synchronization

Release 5.1 (ETSI)September 2017Issue 4 2618DG09603CAAATQZZA

Page 262: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• SEC ETSI quality level value is fixed to SEC (SDH Equipment Clock, specified in G.813option 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 bothCRUs 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 thecommand is directed.

Possible values are:

• 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 forSystem 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

Administer Clock references - Synchronization 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

262 Issue 4

Page 263: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.38 Administer Users with Security Administrator Privileges

6.38.1 Purpose

This procedure describes authorized users creation, modification, deletion and how these usersmanage system security resources.

6.38.2 General

The ENT-USER-SECU command is used to create a new user profile in the User SecurityDatabase.

To change a user profile the ED-USER-SECU command, this command is used by a user withsecurity 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 effectimmediately, 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. whatprovided by means of ENT/ED-USER-SECU commands (user privilege level, max interval for linktimeout and user provided name) and some dynamic user information (uid status depending on theresult of INH/ALW-USER-SECU issued commands, uid status depending on whether or not thepassword is expired and no more possible to be changed and, finally, the time remaining to thepassword expiration).

The RTRV-USER-SECU command retrieves all the user profile parameters that are actually activein that moment, for the entered user/users. In fact, a given user profile could have some parametersthat have been modified at system level, but still not applied to the user profile, because the userwas logged on when the system parameters values have been modified, and the user is stillcurrently logged on.

The RTRV-USER-SECU command retrieves also those system parameters that are notprovisionable by means of ED/ENT-USER-SECU, but only by means of SET-ATTR-SECUDFLT. Forthese system parameters, RTRV-USER-SECU shall report the values that are actually applied inthat moment, for the entered user/users.

Only a user with administrator privileges can retrieve any or all user profile entries. Any other usercan 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 getan 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 targetuser and inhibit him/her.

The INH-USER-SECU command shall be denied when issued against the user that is issuing thecommand itself, that is no auto inhibition is allowed. This also prevents the inhibition of the lastremaining administrative user.

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

Release 5.1 (ETSI)September 2017Issue 4 2638DG09603CAAATQZZA

Page 264: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The ALW-USER-SECU command shall allow to reinstate users, so the user can again establish asession with the system.

The ALW-USER-SECU command allows reinstatement of users that have been disabled by thefollowing 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 thespecified 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 offusers, 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.ea user for which an INTRUSION alarm was emitted, the NE also clears the INTRUSION alarm forthat UID.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

6.38.3 Before you begin

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 isprompted to change password.

6.38.4 Procedure

1

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

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

264 Issue 4

Page 265: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Login to the NE with ADMIN User (default password).

3

Create a new user (for example: USER01) with “Security Administrator” Privileges (setUAP=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 ofall IO cards, ports, interfaces and circuits. Users may configure all subsystems which donot allow for system wide effect. The user may perform nondestructive provisioning of IOcards, ports and interfaces, initiate test procedures which are not service affecting andretrieve information about the system)

− NETADMIN (Network Administrator. A network administrator may configure anything in thesystem except user accounts)

− PROV (Provision. The user may perform non-destructive provisioning of IO cards, portsand interfaces, initiate test procedures which are not service affecting and retrieveinformation 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, andmodify user accounts. A security user need not be a network administrator, but can createuser accounts with network administrator privilege. User shall be able to issue allcommands. User shall not be able to use debug and software development tools.)

− DEBUG (Test)

− NOTMOUT (No inactivity timeout applied to the user.)

Other parameters are optional. If a value is not entered for these parameters, the system willuse the default value. Refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide for details on parameter values.

4

Login to the NE with the new user (for ex.: USER01).

Verify that the command is completed with response ‘COMPLD” and Login is successful.

5

Retrieve user with Security Administrator Privileges

After the login to the NE with the user created (for ex.:USER01).

Enter:

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

Release 5.1 (ETSI)September 2017Issue 4 2658DG09603CAAATQZZA

Page 266: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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, andassociated 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 offailed login (MXINV), or has entered consecutive invalid login attempts within the minimumallowed 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 outthe user.

Observe that the user with Security Administrator Privileges (for ex.: USER01) session isterminated

7

From ADMIN session Inhibit to disable the user with Security Administrator Privileges (for ex.:USER01).

Enter:

INH-USER-SECU:::::UID;

where:

UID = User Identifier, specifies a unique user ID.

8

Retrieve to check the user's state.

Result: Retrieval shows the user “USER01” in suspended state (STATE=SUSPENDED).

9

Enable user with Security Administrator Privileges

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

266 Issue 4

Page 267: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

From ADMIN session enable the user with Security Administrator Privileges (for ex.: USER01).

Enter

ALW-USER-SECU:::::UID;

where:

UID = User Identifier, specifies a unique user ID.

10

Check that the command is completed and that retrieval command shows the user withSecurity Administrator Privileges (for ex.: USER01) is in active state (STATE=ACTIVE).

11

Change user with Security Administrator Privileges

Enter:

ED-USERSECU::UID:::[NEWUID],[NEWPID],[CONFIRMPID],[UAP]:[PAGE=][,PCND

=][,PCNN=][,POINT=][,UOUT=][,PRIVPROT=][,AUTHPROT=];

where:

UID = User Identifier, specifies a unique user ID.

Other parameters are optional. If a value is not entered for these parameters, the system willuse the default value. Refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide for details on parameter values.

12

Delete user with Security Administrator Privileges

Enter:

DLT-USER-SECU::UID;

where:

UID = User Identifier, specifies a unique user ID.

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 andestablishes a one-way (unidirectional), two-way (bidirectional) cross connection between thespecified facilities.

6.39.2 Prerequisites

This command is used for ETSI.

1850 TSS-320/TSS-320H/TSS-160 Administer VC Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 2678DG09603CAAATQZZA

Page 268: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.39.3 General

Multicast cross connections are established by creating of many 1WAY cross connections startingfrom 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 thenetwork, 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 samefacility (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 TOfacilities.

If for the FROM or TO facility a LOPOOL is specified a new free modifiable vc4 (MVC4) will beallocated. This allocated MVC4 will be reported in the command response and data base changemessage 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 newallocated. 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

Administer VC Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

268 Issue 4

Page 269: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

If ampersand ranging (&&) is used for an AID, the same CKTID value is applied to each connectionwithin the AID range.

The ACD Parameter retrievable by RTRV-CRS-<rate> will be set to LOCAL for the cross connectioncreated by this command.

It is allowed to reenter an existing cross connection. This means FROM and TO are identical to analready existing cross connection and all other parameter values are identical to this crossconnection. 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 SymbolicCircuit 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 typescontaining 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 aone-way bridge connection.

2WAY, 2WAYSNCP: One line of data for each two-way cross-connection. If no cross-connectcontaining a CKTID or CKTIDTF parameter matching the input Circuit ID is found, then a COMPLDmessage is returned without any output parameters.

Figure 19 1WAY multicast cross-connection build from single 1WAY cross-connections

Figure 20 1WAY loopback through cross-connect matrix

1850 TSS-320/TSS-320H/TSS-160 Administer VC Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 2698DG09603CAAATQZZA

Page 270: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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.

To end this procedure, go to Step 14.

2

Retrieve Cross-Connection Information

Enter RTRV-CRS::AID:::[RTRVMODE=];

where:

• AID = selected facility(ies) to which the command is directed. AID of ALL retrieves all thecross 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 anSTM64

− STM64AU416C-{1-7}-{1-9}-{2-9,12-19,2 1-36}-1-{1,17,33,49} for AU4-16c embeddedwithin 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,45,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 a2G5PSO 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 anSTM16on 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 a2G5SO 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 a10xAny 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 ona 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 a10xAny module - 24xVC4)

Administer VC Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

270 Issue 4

Page 271: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

− VCGLOVC3-{1-7}-{1-9}-{2-9,12-19}-{1-24}-{1-24} for LO VC3 within a logical VCG on aMultiservice Packet Card

− VCGLOVC12-{1-7}-{1-9}-{2-9,12-19}-{1-124}-{1-63} for LO VC12 within a logical VCG ona Multiservice Packet Card

− MVC4TU12-{1-7}-{1-9}-{21,22,35,36}-{1-64}-{1-3}-{1-7}-{1-3} for TU12 embedded within aModifiable VC4

− MVC4TU3-{1-7}-{1-9}-{21,22,35,36}-{1-64}-{1-3} for TU3 embedded within a ModifiableVC4

− AID = selected facility(ies) to which the command is directed. AID of ALL retrieves all thecross 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 anSTM64

− STM64AU416C-{1-7}-{1-9}-{2-9,12-19,2 1-36}-1-{1,17,33,49} for AU4-16c embeddedwithin 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,45,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 a2G5PSO 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 anSTM16on 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 a2G5SO 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} for VC4 within a VCG on a 10xAnymodule

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

− VCGLOVC3-{1-7}-{1-9}-{2-9,12-19}-{1-24}-{1-24} for LO VC3 within a logical VCG on aMultiservice Packet Card

− VCGLOVC12-{1-7}-{1-9}-{2-9,12-19}-{1-124}-{1-63} for LO VC12 within a logical VCG ona Multiservice Packet Card

− MVC4TU12-{1-7}-{1-9}-{21,22,35,36}-{1-64}-{1-3}-{1-7}-{1-3} for TU12 embedded within aModifiable VC4

− MVC4TU3-{1-7}-{1-9}-{21,22,35,36}-{1-64}-{1-3} for TU3 embedded within a ModifiableVC4

− STM1AU4-{1-7}-{1-9}-{7}-{1}-1 for AU4 embedded within STM1 on Sub-module on SCC of1646DS

1850 TSS-320/TSS-320H/TSS-160 Administer VC Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 2718DG09603CAAATQZZA

Page 272: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

− 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 of1646 shelf

− MVC4TU12-{1-7}-{1-9}-{7}-{1-16}-{1-3}- {1-7}-{1-3} for TU12 within a MVC4 on SCC cardon 1646 Drop shelf

− MVC4TU3-{1-7}-{1-9}-{7}-{1-16}-{1-3} for TU3 within a MVC4 on SCC card on 1646 Dropshelf

− PDHLOVC12-{1-7}-{2}-{8-10, 11-13}-{1-63} for VC12 with E1 client on the PDH Accessshelf E1 Port Module

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

Administer VC Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

272 Issue 4

Page 273: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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, sourceof cross-connection) facility of the cross-connection.

Possible values for VC4 rate:

− STM1AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-1 for AU4 embedded within an STM1

− STM64AU4-{1-7}-{1-9}-{2-9,12-19,21-3 6}-1-{1-64} for AU4 embedded within an STM64

− STM16AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1-16} for AU4 in an STM16 on a2G5SO or a 10xANY

1850 TSS-320/TSS-320H/TSS-160 Administer VC Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 2738DG09603CAAATQZZA

Page 274: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

− STM4AU4-{1-7}-{1-9}-{2-9,12-19,21-36} -{1-8}-{1-4} for AU4 embedded within an STM4

− 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 a10xAny 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 ona 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 a10xAny module - 24xVC4)

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

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,45,49,53,57,61} for 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 AU4-4c in anSTM16on a 2G5SO or 10xANY

− STM4AU44C-{1-7}-{1-9}-{2-9,12-19,21- 36}-{1-8}-1 for AU4-4c embedded within an STM4

Possible values for VC416C rate:

− STM64AU416C-{1-7}-{1-9}-{2-9,12-19,2 1-36}-1-{1,17,33,49} for AU4-16c embeddedwithin 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 a2G5PSO or 10xANY

Possible values for VC464C rate:

− STM64AU464C-{1-7}-{1-9}-{2-9,12-19,2 1-36}-1-1 for AU4-64c embedded within anSTM64

Possible values for LOVC12 rate:

− VCGLOVC12-{1-7}-{1-9}-{2-9,12-19}-{1-124}-{1-63} for LO VC12 within a logical VCG ona Multiservice Packet Card

− MVC4TU12-{1-7}-{1-9}-{21,22,35,36}-{1-64}-{1-3}-{1-7}-{1-3} for TU12 embedded within aModifiable VC4

− MVC4TU12-{1-7}-{1-9}-{7}-{1-16}-{1-3}-{1-7}-{1-3} for TU12 within a MVC4 on SCC cardon 1646 Drop shelf

− PDHLOVC12-{1-7}-{1-9}-{1-6}-{1-42} for VC12 with E1 client on the PDH Port Module of1646 shelf.

Possible values for LOVC3 rate:

− VCGLOVC3-{1-7}-{1-9}-{2-9,12-19}-{1-24}-{1-24} for LO VC3 within a logical VCG on aMultiservice Packet Card

− MVC4TU3-{1-7}-{1-9}-{21,22,35,36}-{1-64}-{1-3} for TU3 embedded within a ModifiableVC4

− MVC4TU3-{1-7}-{1-9}-{7}-{1-16}-{1-3} for TU3 within a MVC4 on SCC card on 1646 Dropshelf

• 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.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Administer VC Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

274 Issue 4

Page 275: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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, doublequote, greater than, lesser than and backslash characters) within enclosing double quotes. Anasterisk (*) may be used as a wildcard character.

8

Observe output (output displays all connections containing specified circuit ID), as detailed inthe 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

1850 TSS-320/TSS-320H/TSS-160 Administer VC Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 2758DG09603CAAATQZZA

Page 276: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter ED-CRS-<rate>::FROM,TO:::[CCT]:[CKTID=];

where:

• <rate> = crossconnection rate on which the command acts. Possible values: VC4, VC44C,VC416C, VC464C, LOVC12, LOVC3.

• FROM = AID of connection point. Indicates the FROM (receive side from the network, sourceof cross-connection) facility of the cross-connection. Possible values as referred in Step 5.

• TO = AID of connection point. Indicates the TO (transmit side to the network, sink of cross-connection) facility of the cross-connection. Possible values as referred in Step 5.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

11

Go to Step 1.

12

NOTICE

Optional Content

Possibility of service interruption. Deleting an active cross-connection always affects service.

Optional Content added above. Please modify as needed.

Delete Cross-Connection

Enter DLT-CRS-<rate>::FROM,TO:::[CCT];

where:

• <rate> = crossconnection rate on which the command acts. Possible values: VC4, VC44C,VC416C, VC464C, LOVC12, LOVC3.

• FROM = AID of connection point. Indicates the FROM (receive side from the network, sourceof cross-connection) facility of the cross-connection. Possible values as referred in Step 5.

• TO = AID of connection point. Indicates the TO (transmit side to the network, sink of cross-connection) facility of the cross-connection. Possible values as referred in Step 5.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

13

Go to Step 1.

14

STOP. This procedure is complete.

END OF STEPS

Administer VC Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

276 Issue 4

Page 277: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.40 Administer VCG Facility

6.40.1 Purpose

This procedure provides the instructions to provision/deprovision/modify a Virtual ConcatenationGroup.

6.40.2 Prerequisites

A VCG must be assigned to an ethernet port.

The port must be provisioned first. Refer to the following procedures to provision parent facilities:

• GBE port on 10XANY board: 6.8 “Administer Ethernet Facility ” (p. 155)

• MAU port on 10XANY board: 6.18 “Administer MAU Facility” (p. 193)

Besides the the VCG entity could be a logical VCG for ethernet switching on a PP10AD module

6.40.3 General

The RTRV-VCG command retrieves provisioned values of a specified VCG entity and its currentPST, 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 initialgroup 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 specifiedVCG.

When a VCG is in an OOS-MA, OOS-AUMA state, no VCG condition types are autonomouslyreported for the VCG, but VCG alarm conditions are monitored (retrievable with the RTRV-VCGcommand).

When a VCG is in an OOS-MA, OOS-AUMA state, no VCG condition types are autonomouslyreported for the VCG, but VCG alarm conditions are monitored (retrievable with the RTRV-VCGcommand).

If command is successful, path terminations functions in the number of MAXMBR will be created asmembers of VCG.

The ED-VCG command is used to enable or disable LCAS on a VCG and also set parametersrelated to the LCAS protocol previously provisioned using the ENT-VCG command. RTRV-VCG canbe used to view the parameters.

1850 TSS-320/TSS-320H/TSS-160 Administer VCG Facility

Release 5.1 (ETSI)September 2017Issue 4 2778DG09603CAAATQZZA

Page 278: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 PP10ADmodule

• GBEVCG-{1-7}-{1-9}-{2-9,12-19,21-36}- {1-10} for VCG on a GBE port on a 10xAny module

• MAUVCG-{1-7}-{1-9}-{2-9,12-19,21-36}- {1-10} for VCG on a MAU port on a 10xAny module

• FC200VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1,3,5,7,9} for FC200 VCG on a 10xAny module-12xVC4 )

• FC400VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{3,7} for FC400 VCG on a 10xAny module -24xVC4)

2

Examine output for provisioning information on port, as detailed in the relevant command guide,refer to “Command details” (p. 107).

Administer VCG Facility 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

278 Issue 4

Page 279: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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

[

/*

<Informational_Description_Text>

*/ cr lf]

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

3

Ensure that port is in valid state for provisioning (OOS-MA, UAS).

4

Enter ENT-VCG::AID::::MAXMBR=,VCGTYPE=[,CSFPROP=][,CSFTYPE=][,PRTCLTYPE=][,ALMPROF=]:[PST];

where:

• AID = VCG Access Identifier, specifies the VCG entity. Possible values:

1850 TSS-320/TSS-320H/TSS-160 Administer VCG Facility

Release 5.1 (ETSI)September 2017Issue 4 2798DG09603CAAATQZZA

Page 280: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

− VCG-{1-7}-{1-9}-{2-9,12-19}-{1-124} for Logical VCG for ethernet switching on a PP10ADmodule

− GBEVCG-{1-7}-{1-9}-{2-9,12-19,21-36}- {1-10} for VCG on a GBE port on a 10xAnymodule

− MAUVCG-{1-7}-{1-9}-{2-9,12-19,21-36}- {1-10} for VCG on a MAU port on a 10xAnymodule

− FC200VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1,3,5,7,9} for FC200 VCG on a 10xAnymodule- 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 inVCGTYPE 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).

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Example: In the following example, VCG number 32 on the Multiservice Collector module inslot 5 is provisioned with 10 VC4s members. The VCGVC4-1-1-5-32-1 is given a sequencenumber 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 5VC4 members.

ENT-VCG::GBEVCG-1-1-5-3:::MAXMBR=5, VCGTYPE=VC4;

5

Deprovision VCG facility

Enter RTRV-VCG::AID;

where: AID = VCG Access Identifier, specifies the VCG entity. Possible values:

• VCG-{1-7}-{1-9}-{2-9,12-19}-{1-124} for Logical VCG for ethernet switching on a PP10ADmodule

• 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 )

Administer VCG Facility 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

280 Issue 4

Page 281: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• FC400VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{3,7} for FC400 VCG on a 10xAny module -24xVC4)

• ALL for all AID

6

Examine output for provisioning information on port, as detailed in the relevant command guide,refer to “Command details” (p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

"<AID>::ACTMBR=<value>[,HLDOFFTIME=<value>],LCASENABLE=<value>,

MAXMBR=<value>,PROVMBR=<value>[,RSQACKTOUT=<value>][,SDMODE=<value>],

VCGTYPE=<value>[,WTRTIME=<value>][,BIDISERVPROP=<value>][,PRTCLTYPE=

<value>][,MAXDIFFDLY=<value>][,ALMPROF=<value>][,ACD=<value>][,

MGRACD=<value>]:<PST>,<SST>" cr lf

[

/*

<Informational_Description_Text>

*/ cr lf]

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

7

Does port have SST of ACT, BUSY, SDEE, TRM, or UAS?

If yes, DLT-VCG command cannot be performed on the specified VCG port. Go to Step 12.

1850 TSS-320/TSS-320H/TSS-160 Administer VCG Facility

Release 5.1 (ETSI)September 2017Issue 4 2818DG09603CAAATQZZA

Page 282: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

If no, go to Step 8.

8

Enter DLT-VCG::AID;

where: AID = VCG Access Identifier, specifies the VCG entity. Possible values previouslydecribed.

Example: In the following example, VCG number 32 on the Multiservice Collector card in slot 5is de-provisioned:

DLT-VCG::VCG-1-1-5-32;

In the following example, VCG number 7 on the 10XANY module in slot 5 is de-provisioned:

DLT-VCG::GBEVCG-1-1-5-7;

9

Modify VCG Facility

Enter RTRV-VCG::AID;

where: AID = VCG Access Identifier, specifies the VCG entity. Possible values:

• ALL for all AID

• VCG-{1-7}-{1-9}-{2-9,12-19}-{1-124} for Logical VCG for ethernet switching on a PP10ADmodule

• GBEVCG-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} for VCG on a GBE port on a 10xAny module

• MAUVCG-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} for VCG on a MAU port on a 10xAny module

• FC200VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1,3,5,7,9} for FC200 VCG on a 10xAny module-12xVC4 )

• FC400VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{3,7} for FC400 VCG on a 10xAny module -24xVC4)

10

Examine output for provisioning information on port as detailed in the relevant command guide,refer to “Command details” (p. 107).

Administer VCG Facility 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

282 Issue 4

Page 283: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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

[

/*

<Informational_Description_Text>

*/ 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 forthe time that the LCAS on both nodes is established.

11

Enter ED-VCG::AID::::[MAXMBR=][,HLDOFFTIME=][,LCASENABLE=][,RSQACKTOUT=][,SDMODE=][,CSFPROP=][,CSFTYPE=][,ALMPROF=][,MODE=]:[PST];

where: AID = VCG Access Identifier, specifies the VCG entity. Possible values:

• VCG-{1-7}-{1-9}-{2-9,12-19}-{1-124} for Logical VCG for ethernet switching on a PP10ADmodule

1850 TSS-320/TSS-320H/TSS-160 Administer VCG Facility

Release 5.1 (ETSI)September 2017Issue 4 2838DG09603CAAATQZZA

Page 284: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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)

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

12

STOP. This procedure is complete.

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 managerits own presence, once it has been put in the network and configures as address.

6.41.2 Prerequisites

None.

6.41.3 General

This procedure allows the operator to enable or disable the capability of the node to notify to themanager 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 ofautonomous messages with proprietary format towards the network managers. The period is fixedto 5min.

Successful completion of this command with disabling set, stops the periodical sent of autonomousmessage 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.

Auto Discovery Function 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

284 Issue 4

Page 285: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

STOP. This procedure is complete.

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 andthen acts as a 1588 GrandMaster for all outgoing links.

1850 TSS-320/TSS-320H/TSS-160 Boundary TOD Card administration

Release 5.1 (ETSI)September 2017Issue 4 2858DG09603CAAATQZZA

Page 286: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

When the system operates as Boundary Clock, PTP operates as Slave on a certain port and asMaster on one other (or more) port(s). The Slave Port drives in term of Frequency and/or Phase theassociated Master port(s). Boundary Clock function is activated in order to ensure an efficienttransmission of PTP messages withing a hop-by-hop deployment of a packet network.

6.42.3 Procedure

1

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.

Figure 21 Boundary clock schema

Boundary TOD Card administration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

286 Issue 4

Page 287: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 inBoundary 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 forinternal 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 internalPhase 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 beprovisioned:

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 asinput (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

1850 TSS-320/TSS-320H/TSS-160 Boundary TOD Card administration

Release 5.1 (ETSI)September 2017Issue 4 2878DG09603CAAATQZZA

Page 288: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

synchronization. The delay is due to the lenght of the cable on the link. The lenghtdetermines a propagation delay equal to D [ns], where D is the value to be provisioned. Theparameter applies to the receiver; normally positive values shall be provisioned; but negativevalues can be provisioned as well for compensating excessive dalys provisioned at the oterside 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 moreports, 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 ofparsable output data, in ascending order, listing the possible timing input ports used by thesystem.

6

For PPS-OUT the facility PPSOUT-r-s-b-1 is created and the following parameters can beprovisioned

ED-PPSOUT::AID::::[S1TRANS=][,TOD=][,DLY=];

where:

• AID = PPSOUT-{1-7}-{1-9}-{2-9, 12-19, 21-36}-1 (Pulse Per Second Output Port)

I.e. Access Identifier, specifies the output port transmitting the PPS signal.

• S1TRANS = {ACT, PRC, SSUL, SSUT, SEC, DUS, NONE}.

Sync message byte to be transmitted, determines if the transmitted byte will have the "DUS"message or will have the actual traceability of the signal.

• TOD= Time Of Day, determines if the information about Time Of Day shall be expected asinput (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 forsynchronization. The delay is due to the lenght of the cable on the link. The lenghtdetermines a propagation delay equal to D [ns], where D is the value to be provisioned. Theparameter applies to the receiver; normally positive values shall be provisioned; but negativevalues can be provisioned as well for compensating excessive dalys provisioned at the oterside transmitter. The unit of measure is nanosecond.

7

Enter:

RTRV-PPSOUT::[AID]:;

To retrieve the provisioning and state information of one or more ports, in the 1588v2application, dedicated to the transmission of the PPS signal.

Boundary TOD Card administration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

288 Issue 4

Page 289: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Result: The successful response for a RTRV-PPSOUT command contains one or more linesof parsable output data, in ascending order, listing the possible timing output ports used bythe 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 morelines of parsable output data, in ascending order (from lowest specified PTPSLAVE AID tothe largest specified PTPSLAVE AID), for each PTPSLAVE AID specified.

9

Enter:

RTRV-PTPMASTER:[TID]:[AID]:[CTAG];

the command retrieves the state information of one or more ports, in the 1588v2 application.

Result: The successful response for a RTRV-PTPMASTER command contains one or morelines of parsable output data, in ascending order (from lowest specified PTPMASTER AID tothe 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 clockport), go to Step 11

To configure the timing reference selected for output synchronization (T4) via TOD cardinterface (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 portconnected 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 inputsource from the line.

• ASSPORTAID = specifies whether the timing reference is assigned to a port and if assignedit 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)

1850 TSS-320/TSS-320H/TSS-160 Boundary TOD Card administration

Release 5.1 (ETSI)September 2017Issue 4 2898DG09603CAAATQZZA

Page 290: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Note: Executing an ED-SYNCN command causes the following primary state transitionsfor 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 systemtiming 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 orthe output timing reference entity to which the command is directed.

Select one of the “LINEREFOUT Identifier” (LINEREFOUT-1-1- 0-..5) to provide configurationfor the TOD card interface reference signal

• TCLCK = Transparent Clock function, determines if transport of Transparent Clock isdisabled 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 IEEE1588v2protocol.

Restriction: The parameter is only applicable for the output timing entity.

• ASSPORTAID = specifies whether the timing reference is assigned to a port and if assignedit specifies the AID of the port. The following port types can be used for establishing aconnection 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 statetransitions for the specified timing reference.

15

Retrieve provisioning and state information.

Enter:

Boundary TOD Card administration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

290 Issue 4

Page 291: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 ofsystem 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 portconnected 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 SystemPhase)

• SYNCMSG = SYNCMSG, determines if the timing reference selection for system phase isusing 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 bypriorities as second criteria.

• ASSPORTAID = ASSPORTAID specifies whether the phase reference is assigned to a portand if assigned it specifies the AID of the port. The following port types can be used forestablishing a connection towards a timing reference: PPS Input assigned to a phasereference

Note: The user is able to select the AID of the phase entity to be modified for the SyncMessaging (SYNMSG) management , specifying if the phase reference selection forsystem 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 toconfigure 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

1850 TSS-320/TSS-320H/TSS-160 Boundary TOD Card administration

Release 5.1 (ETSI)September 2017Issue 4 2918DG09603CAAATQZZA

Page 292: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 commandguide.

21

Management Operator Disabling of PTP protocol over PTP logical Master port via setting ofieee1588PtpPortDSAdminStatus 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 CLIcommand guide.

24

The TOD card shall be logically removed.

Enter:

RMV-EQPT::AID;

or

ED-EQPT::AID:OOS;

where:

• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card

Note: TOD Card logical removal is mandatory also for avoiding traffic hits upon NGI linksof otherCollector cards eventually present in the shelf.

25

Enter:

Boundary TOD Card administration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

292 Issue 4

Page 293: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

DLT-EQPT::AID;

where:

• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card

Result: The command causes the Deactivation/Deletion of PTP Master logical port (bothSNMP 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.

6.43.2 Prerequisites

None.

6.43.3 General

In this procedure, enter parameter values only for indicated fields. Leave remaining fields blank forsystem 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

1850 TSS-320/TSS-320H/TSS-160 Change Facility Service State

Release 5.1 (ETSI)September 2017Issue 4 2938DG09603CAAATQZZA

Page 294: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter RMV-x::AID;

where:

• x=Facility type (GBE10, GBE, ODU2, OTU2, VCG, MAU, BITS, SYNCN, SYNC-OUT)

• AID=Access Identifier of port to be retrieved

5

Go to Step 7.

6

Restore Facility

Enter RST-x::AID:::SWTCHCMD;

where:

• x=Facility type (GBE10, GBE, ODU2, OTU2, VCG, MAU, BITS, SYNCN, SYNC-OUT)

• AID=Access Identifier of port to be retrieved

7

STOP. This procedure is complete.

END OF STEPS

6.44 Change User Password

6.44.1 Purpose

This procedure provides the instructions to change a user's login Password Identifier (PID).

6.44.2 Prerequisites

The personal User Identification (UID) and current PID for the user must be known.

6.44.3 General

ED-PID is used to change a user's own password, and the user must enter the current UID andPID.

If a PID or UID has been deactivated or removed, only a System Administrator account user canenter a new PID or UID database entry.

Change User Password 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

294 Issue 4

Page 295: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.44.4 Procedure

1

WARNING

Optional Content

This command should be done after the first login to the system, i.e. after the first ACT-USER.

Optional Content added above. Please modify as needed.

Enter ED-PID:[TID]:UID:[CTAG]::OLDPID,NEWPID,CONFIRMPID;

where:

• UID: User Identifier, specifies a unique user ID. Valid values for UID are 5 to 12, case-sensitive alphanumeric characters where the first character must always be an alphabeticcharacter. The following special characters are also accepted as valid characters and will bepart of the UID: % (percent sign), + (plus sign), # (pound sign), and _ (under score). Possiblevalues: 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 loginpassword.

Note: The confirmation password (CONFIRMPID) shall be the same as the entered newpassword (NEWPID)

2

Did system return a successful response?

If yes, go to Step 5.

If no, go to Step 3.

3

Check error code message.

4

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.

1850 TSS-320/TSS-320H/TSS-160 Change User Password

Release 5.1 (ETSI)September 2017Issue 4 2958DG09603CAAATQZZA

Page 296: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

5

STOP. This procedure is complete.

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.

6.45.2 Prerequisites

For a join to 2WAY operation resulting in one cross connection of CCT=2WAY is the existence oftwo cross connections of CCT=1WAY. This two 1WAY cross connections must connect the sameFROM and TO, but in opposite direction.

For a join 2WAYSNCP operation resulting in one cross connection of CCT=2WAYSNCP is theexistence 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 1WAYSNCPcross connection. The other 1WAY cross connection must connect the TO and FROMPING facilitiesof the 1WAYSNCP cross connection.

6.45.3 General

Join and split

The CNVT-CCJ-<rate> command joins unidirectional cross connections to one bidirectional crossconnection.

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 1WAYcross connection addressed by the TO parameter if not provided. Addressed by TO means: inputparameter TO of CNVT-CCJ-<rate> is equal TO of the cross connection.

• Join to 2WAYSNCP see Figure 23, “Conversion of 1WAYSNCP <--> 2WAYSNCP crossconnection” (p. 298)

All parameters of the protection switch will be not changed and taken over to from the1WAYSNCP cross connection to the 2WAYSNCP cross connection. The protection switch stateremains unchanged by the join operation. The role of FROMPED and FROMPING will be notchanged.

Convert a Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

296 Issue 4

Page 297: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The CKTID of the new 2WAYSNCP cross connection will be taken over from the previous1WAYSNCP cross connection if not provided.

Figure 22 Conversion of 1WAY <--> 2WAY cross connection

1850 TSS-320/TSS-320H/TSS-160 Convert a Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 2978DG09603CAAATQZZA

Page 298: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 existingpath protection cross connection.

The cross connection to be modified will be addressed by the TO parameter. (called originalcross connection)

The CKTID will be taken over from the already existing cross connection if not provided.

Figure 23 Conversion of 1WAYSNCP <--> 2WAYSNCP cross connection

Convert a Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

298 Issue 4

Page 299: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 parametersmust 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 aprotection switch.

When deleting a protection leg it can be specified which leg (FROMPING or FROMPED) will bethe new FROM (NEWFROM) of the unprotected cross connection. The NEWFROM parameterof the command must be one of the FROMPED or FROMPING of the original path protectioncross connection.

Deleting a protection leg may lead to a reconnection of the new FROM and TO depending of theprotection 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

1850 TSS-320/TSS-320H/TSS-160 Convert a Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 2998DG09603CAAATQZZA

Page 300: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.45.3 Procedure

1

Select action.

To join unidirectional cross connections to one bidirectional cross connection, go to Step 2.

To split a bidirectional cross connection into unidirectional cross connections, go to Step 8.

To add a protection leg to a cross connection, go to Step 12.

To removes a protection leg from a cross connection, go to Step 16.

To end this procedure, go to Step 18.

2

Join unidirectional cross connections to one bidirectional cross connection

Enter RTRV-CRS::AID:::[RTRVMODE=];

where:

• AID = selected facility(ies) to which the command is directed. AID of ALL retrieves all thecross connects in the system. Possible values are described in 6.39 “Administer VC Cross-Connection” (p. 267).

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Figure 25 Conversion of 2WAYSNCP <--> 2WAY - adding/removing a protection leg

Convert a Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

300 Issue 4

Page 301: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

3

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

[

"<FROM>,<TO>:<CTYPE>,<LEVEL>:[CKTID=<value>]

[,CKTIDTF=<value>][,ALTERNATE=<value>][,FROMPING=<value>][,ACD=

<value>]:<PST>[,<SST>]" cr lf]

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

4

Enter CNVT-CCJ-<rate>::TO::::[CKTID=];

where:

• <rate> = crossconnection rate on which the command acts. Possible values: VC4, VC44C,VC416C, VC464C, LOVC12, LOVC3.

• TO=AID of the TO facility of the cross connection to be converted. In case of a 2WAY crossconnection both ends of the cross connection can be used for addressing. In case of a join to2WAY 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 mustbe addressed. All other involved cross connections can be calculated and must exist for asuccessful acceptance of the command. Possible values are decribed in 6.39 “AdministerVC Cross-Connection” (p. 267).

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Convert a Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 3018DG09603CAAATQZZA

Page 302: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

5

Go to Step 1.

6

Split a bidirectional cross connection into unidirectional cross connections

Enter RTRV-CRS::AID:::[RTRVMODE=];

where:

• AID = selected facility(ies) to which the command is directed. AID of ALL retrieves all thecross connects in the system. Possible values are described in 6.39 “Administer VC Cross-Connection” (p. 267).

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

7

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

Convert a Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

302 Issue 4

Page 303: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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]

;

8

Enter CNVT-CCS-<rate>::TO::::[CKTID=];

where:

• <rate> = crossconnection rate on which the command acts. Possible values: VC4, VC44C,VC416C, VC464C, LOVC12, LOVC3.

• TO=AID of the TO facility of the cross connection to be converted. In case of a 2WAY crossconnection both ends of the cross connection can be used for addressing. Possible valuesare decribed in 6.39 “Administer VC Cross-Connection” (p. 267).

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

9

Go to Step 1.

10

Add a protection leg to a cross connection

1850 TSS-320/TSS-320H/TSS-160 Convert a Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 3038DG09603CAAATQZZA

Page 304: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter RTRV-CRS::AID:::[RTRVMODE=];

where:

• AID = selected facility(ies) to which the command is directed. AID of ALL retrieves all thecross connects in the system. Possible values are described in 6.39 “Administer VC Cross-Connection” (p. 267).

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

11

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

Convert a Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

304 Issue 4

Page 305: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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]

;

12

Enter CNVT-CCTPR-<rate>::TO::::NEWFROMPED=,NEWFROMPING= [,RVRTV=][,

RVRTTIM=][,HLDFFTIM=][,PTYPE=];

where:

• <rate> = crossconnection rate on which the command acts. Possible values: VC4, VC44C,VC416C, VC464C, LOVC12, LOVC3.

• TO=AID of connection point; Indicates the TO (transmit side to the network, sink of cross-connection) facility of the cross-connection. It addresses the cross connection to beconverted. Possible values are described in 6.39 “Administer VC Cross-Connection”(p. 267).

• NEWFROMPED=AID of connection point; Indicates the new FROMPING (protecting receiveside 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 thisfacility gets the role of the new FROMPED. Possible values are described in6.39 “Administer VC Cross-Connection” (p. 267).

• NEWFROMPING=AID of connection point; Indicates the new FROMPING (protecting receiveside from the network, protecting source of cross-connection) facility of the cross-connection.

1850 TSS-320/TSS-320H/TSS-160 Convert a Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 3058DG09603CAAATQZZA

Page 306: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

If the AID is the same as from the FROM facility of the original cross connection, then thisfacility gets the role of the new FROMPING. Possible values are described in6.39 “Administer VC Cross-Connection” (p. 267).

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

13

Go to Step 1.

14

Remove a protection leg to a cross connection

Enter RTRV-CRS::AID:::[RTRVMODE=];

where:

• AID = selected facility(ies) to which the command is directed. AID of ALL retrieves all thecross connects in the system. Possible values are described in 6.39 “Administer VC Cross-Connection” (p. 267).

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

15

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

Convert a Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

306 Issue 4

Page 307: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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]

;

16

Enter CNVT-CCTU-<rate>::TO::::NEWFROM=;

where:

• <rate> = crossconnection rate on which the command acts. Possible values: VC4, VC44C,VC416C, VC464C, LOVC12, LOVC3.

• TO=AID of connection point; Indicates the TO (transmit side to the network, sink of cross-connection) facility of the cross-connection. It addresses the cross connection to beconverted. 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. TheAID must be one of the FROMPED or FROMPING of the original cross connection. In casethe cross connection is converted to a cross connection of type 1WAY or 2WAY theprotection leg will be deleted. Possible values are described in 6.39 “Administer VC Cross-Connection” (p. 267).

17

Go to Step 1.

1850 TSS-320/TSS-320H/TSS-160 Convert a Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 3078DG09603CAAATQZZA

Page 308: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

18

STOP. This procedure is complete.

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).

6.46.2 Prerequisites

The UID must be known before it can be deleted.

6.46.3 General

DLT-USER-SECU command deletes user profiles in the User Security Database, for the specifiedUser Identifier (UID).

Only the security administrator can delete a user profile entry in the User Security Database. Inaddition, 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 offusers, and logged on users. The deletion of a logged on user shall log off the target user and deletehim/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 alphabeticcharacter. The following special characters are also accepted as valid characters and will bepart of the UID: % (percent sign), + (plus sign), # (pound sign), and _ (under score).

2

STOP. This procedure is complete.

END OF STEPS

6.47 Deprovision Equipment

6.47.1 Purpose

This procedure provides instructions to deprovision modules in the system.

Delete User from System 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

308 Issue 4

Page 309: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.47.2 Prerequisites

This procedure is service-affecting if any cross-connections are active on the module. All cross-connections must be deleted. Once cross-connections are deleted, ports associated with themodule must be deprovisioned. Refer to Table 25, “Procedures Required Before DeprovisioningModules” (p. 308) for appropriate procedures.

Table 25 Procedures Required Before Deprovisioning Modules

Port TypeDelete CrossConnections

Delete ConferenceConnections

Deprovisioning port

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 deletedfrom 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

1850 TSS-320/TSS-320H/TSS-160 Deprovision Equipment

Release 5.1 (ETSI)September 2017Issue 4 3098DG09603CAAATQZZA

Page 310: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

− CWDM Optical Transponder (2.5G) with Optical Protection

− CWDM OADM 4ch w/o OSC coupler

− CWDM OADM 4ch w OSC coupler

− CWDM OADM 2ch w/o OSC coupler

− CWDM OADM 2ch w OSC coupler

− CWDM OADM 1ch w/o OSC coupler

− CWDM OADM 1ch w OSC coupler

− CWDM Mux/Demux 8ch w/o OSC coupler

− CWDM Mux/Demux 8ch with OSC coupler

− CWDM Mux/Demux 2ch with OSC coupler

− CWDM Mux/Demux 1ch with OSC coupler

− DWDM Mux/Demux 8 channels L1 band without S-band input/output

• 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 cannotbe deleted separately. I/O equipment can only be deleted if all supported facilities are deprovisionedfirst.

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 typesassociated 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) ofthe 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-EQPTcommand.

Deprovision Equipment 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

310 Issue 4

Page 311: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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.

where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.Possible values:

• 10GSO-{1-7}-{1-9}-{2-9,12-19,21-36} as10G Synchronous Optical

• 2G5SO-{1-7}-{1-9}-{2-9,12-19,21-36} as 2.5G Synchronous Optical

• 8XSO-{1-7}-{1-9}-{2-9,12-19,21-36} as 8 x Synchronous Optical

• OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} as G.709 OTU 10GB Card (Provisioned Type =1POTU2)

• 10XANY-{1-7}-{1-9}-{2-9,12-19,21-36} as 10XANY Card

• XFP-{1-7}-{1-9}-{2-9,12-19,21-36}-1 as XFP on 10GSO modules

• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} as SFP on 8XSO modules

• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} as SFP on 10XANY modules

• LOA10G-{1-7}-{1-9}-{21,22,24,33,35,36} as Lower Order Adaptation Card with EPS

3

What is PST and SST of module to delete?

If IS-NR or OOS-AU, go to Step 4.

If OOS-MA or OOS-AUMA, go to Step 5.

If OOS-MA,UAS, module is already deprovisioned. Go to Step 20.

4

Enter RMV-EQPT::AID:::[MODE];

where: AID=Equipment Access Identifier, identifies the equipment entity access identifier, asdecribed in Step 2

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Deprovision Equipment

Release 5.1 (ETSI)September 2017Issue 4 3118DG09603CAAATQZZA

Page 312: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

5

Enter DLT-EQPT::AID;

where: AID=Equipment Access Identifier, identifies the equipment entity access identifier, asdecribed in Step 2

6

Go to Step 20.

7

For DATA boards

Enter RTRV-EQPT::AID; to view equipment service states.

where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.Possible values:

• PP1GE-{1-7}-{1-9}-{2-9,12-19} as Packet Module 10x1Gb

• PP10GE-{1-7}-{1-9}-{2-9,12-19} as Packet Module 1x10Gb

• PP10AD-{1-7}-{1-9}-{2-9,12-19} as Adaptation Card Packet Modules 10G

• SFP-{1-7}-{1-9}-{2-9,12-19}-{1-10} as SFP on PP10 modules

• XFP-{1-7}-{1-9}-{2-9,12-19}-1 as XFP on PP10GE modules

8

What is PST and SST of module to delete?

If IS-NR or OOS-AU, go to Step 9.

If OOS-MA or OOS-AUMA, go to Step 10.

If OOS-MA,UAS, module is already deprovisioned. Go to Step 20.

9

Enter RMV-EQPT::AID:::[MODE];

where: AID=Equipment Access Identifier, identifies the equipment entity access identifier, asdecribed in Step 7

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

10

Enter DLT-EQPT::AID;

where: AID=Equipment Access Identifier, identifies the equipment entity access identifier, asdecribed in Step 7

11

Go to Step 20.

Deprovision Equipment 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

312 Issue 4

Page 313: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

12

For WDM board

Enter RTRV-EQPT::AID; to view equipment service states.

where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.Possible values:

• PRE-{1-7}-{1-9}-{2-9,12-19,21-36} as Preamplifier

• BOOST-{1-7}-{1-9}-{2-9,12-19,21-36} as Booster

• LOFA-{1-7}-{1-9}-{6-9,12-15} as Line Optical Filter and Attenuator

• DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} as DWDM Optical Transponder

• CWLA-{1-7}-{1-9}-{6-9,12-15} as CWDM Optical Transponder

• CADM-{1-7}-{1-9}-{6,7,8,9,12,13,14,15} as CWDM OADM

• CMDX-{1-7}-{1-9}-{6-9,12-15} as CWDM MUX/DEMUX

• OMDX8-{1-7}-{1-9}-{6-9,12-15} as DWDM MUX/DEMUX 8 channels

• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4} as SFP on 2G5SO or on CWLA modules

13

What is PST and SST of module to delete?

If IS-NR or OOS-AU, go to Step 14.

If OOS-MA or OOS-AUMA, go to Step 15.

If OOS-MA,UAS, module is already deprovisioned. Go to Step 20.

14

Enter RMV-EQPT::AID:::[MODE];

where: AID=Equipment Access Identifier, identifies the equipment entity access identifier, asdecribed in Step 12

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

15

Enter DLT-EQPT::AID;

where: AID=Equipment Access Identifier, identifies the equipment entity access identifier, asdecribed in Step 12

16

Go to Step 20.

1850 TSS-320/TSS-320H/TSS-160 Deprovision Equipment

Release 5.1 (ETSI)September 2017Issue 4 3138DG09603CAAATQZZA

Page 314: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

17

WARNING

Optional Content

EC320 in slot 1 (whatever is the EPS status), working EC320 (whatever is the slot), MT320(MT160 in Tss160 Shelf), TBUS, POW and FAN cannot be deleted.

Optional Content added above. Please modify as needed.

For common boards

Read the following WARNING.

18

Go to Step 20.

19

WARNING

Optional Content

If an unit is deleted, also all related XFP/SFPs are deleted (if present) even if not logicallyremoved.

Optional Content added above. Please modify as needed.

For XFP/SFP Module

Read the following WARNING.

20

STOP. This procedure is complete.

END OF STEPS

6.48 Disable/Enable User Account

6.48.1 Purpose

This procedure provides the instructions to disable (inhibit) existing users in order to prohibit accessto the system. This procedure also provides instructions to reenable user accounts.

6.48.2 Prerequisites

The user must have administrator privileges to enable/disable a user account.

Disable/Enable User Account 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

314 Issue 4

Page 315: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 thetarget user unless the logged on user is a security administrator. In that case, the command isdenied.

The ALW-USER-SECU command is used to reinstate users that have been disabled by the INH-USER-SECU command.

6.48.4 Procedure

1

Select action.

To disable user account, go to Step 2.

To enable user account, go to Step 8.

2

Disable User Account

Enter RTRV-USER-SECU::[UID];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Observe output. Verify STATE=ACTIVE, as detailed in the relevant command guide, refer to“Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Disable/Enable User Account

Release 5.1 (ETSI)September 2017Issue 4 3158DG09603CAAATQZZA

Page 316: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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-sensitivealphanumeric characters where the first character must always be an alphabetic character. Thefollowing 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 definedfor the system.

5

Enter RTRV-USER-SECU::[UID];

where: UID=User Identifier of user just disabled

6

Observe output. Verify STATE=SUSPENDED, as detailed in the relevant command guide, referto “Command details” (p. 107).

Disable/Enable User Account 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

316 Issue 4

Page 317: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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]

;

7

Go to Step 13.

8

Enable User Account

Enter RTRV-USER-SECU::[UID];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

9

Observe output. Verify STATE=SUSPENDED, as detailed in the relevant command guide, referto “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Disable/Enable User Account

Release 5.1 (ETSI)September 2017Issue 4 3178DG09603CAAATQZZA

Page 318: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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]

;

10

Enter ALW-USER-SECU:::::UID;

where: UID=User Identifier of user to disable. Valid values for UID are 5 to 12, case-sensitivealphanumeric characters where the first character must always be an alphabetic character. Thefollowing special characters are also accepted as valid characters and will be part of the UID: %(percent sign), + (plus sign), # (pound sign), and _ (under score).

11

Enter RTRV-USER-SECU::[UID];

where: UID=User Identifier of user just enabled

12

Observe output. Verify STATE=ACTIVE, as detailed in the relevant command guide, refer to“Command details” (p. 107).

Disable/Enable User Account 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

318 Issue 4

Page 319: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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]

;

13

STOP. This procedure is complete.

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 alarmconditions in the system, or any alarm conditions matching a specified combination of position-defined input parameters.

6.49.2 Prerequisites

None.

1850 TSS-320/TSS-320H/TSS-160 Display Alarms

Release 5.1 (ETSI)September 2017Issue 4 3198DG09603CAAATQZZA

Page 320: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.49.3 General

The alarm conditions to be retrieved can be specified by using the input parameters NTFCNCDEand/or CONDTYPE as the filter, i.e., existing conditions satisfying all the specified input parameterswill be reported in the message response.

The successful response for a RTRV-ALM-ALL command contains one line of parsable output datafor each alarm condition being reported. If multiple alarm conditions exist, a line of output isprovided for each alarm.

Each equipment entity with alarms is grouped by equipment type and displayed in ascending orderof each of the AID fields (excluding the equipment type field) left to right, and in ascending order bydate and time of occurrence.

Each common (no specific entity) alarm is displayed in ascending order by date and time ofoccurrence.

Each facility entity with alarms grouped by facility type is displayed in ascending order of each ofthe AID fields (excluding the facility type field, if any) left to right, and in ascending order by dateand time of occurrence.

For standing (i.e. non-transient) Threshold Crossing Alerts the Parameters MONVAL, THLEV andTMPER will be reported. The parameters contain the values which are provided at the time thecondition 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]; toretrieve the current status of all alarms or conditions.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

Display Alarms 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

320 Issue 4

Page 321: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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]; toretrieve the current status of any existing, alarm conditions for the specified equipment AID, orfor the specified AID and any alarm conditions matching the specified combination ofposition-defined input parameters.

where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.Possible values:

• EC320-{1-7}-{1-9}-{1,20} for Equipment Controller Card TSS-320

• MT320-{1-7}-{1-9}-{10,11} for Matrix and Timing TSS-320

• MT160-{1-7}-{1-9}-{10,11} for Matrix and Timing TSS-160

• LOA10G-{1-7}-{1-9}-{21,22,24,33,35,36} for Lower Order Adaptation Card with EPS

• PSF320-{1-7}-{1-9}-{37,39} for Power Supply Filter TSS-320

1850 TSS-320/TSS-320H/TSS-160 Display Alarms

Release 5.1 (ETSI)September 2017Issue 4 3218DG09603CAAATQZZA

Page 322: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 DWLA10Xmodule

• 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

• PP10GE-{1-7}-{1-9}-{2-9,12-19} for Packet Module 1x10Gb

• 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

Display Alarms 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

322 Issue 4

Page 323: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

"<AID>[,<AIDTYPE>]:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>,

<LOCN>" cr lf

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

7

Go to Step 14.

8

Retrieve All BITS Alarms

Enter RTRV-ALM-BITS::AID:::[NTFCNCDE],[CONDTYPE],[SRVEFF]; to retrieve thecurrent status of specified BITS facilities.

where:

• ALL for all AID

• BITS-{1-7}-{1-9}-{0,1} for Shelf External Timing Input Port

• BITSOUT-{1-7}-{1-9}-0 for Shelf External Timing Output Port

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Display Alarms

Release 5.1 (ETSI)September 2017Issue 4 3238DG09603CAAATQZZA

Page 324: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

9

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

"<AID>[,<AIDTYPE>]:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>"

cr lf

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

10

Go to Step 14.

11

Retrieve Facility Alarms

Enter RTRV-ALM-x::AID:::[NTFCNCDE],[CONDTYPE],[SRVEFF],[LOCN], [DIRN]; toretrieve the current status of all alarms or conditions, where the possible values for the relevantAID = 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− 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.

Display Alarms 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

324 Issue 4

Page 325: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• x= LOVCN

Values valid for: LOVC12 command modifier

− VCGLOVC12-{1-7}-{1-9}-{2-9,12-19}-{1-124}-{1-63} for LO VC12 within a logical VCG ona Multiservice Packet Card

− MVC4TU12-{1-7}-{1-9}-{21,22,35,36}-{1-64}-{1-3}-{1-7}-{1-3} for TU12 embedded within aModifiable VC4

− PDHLOVC12-{1-7}-{1-9}-{1-6}-{1-42} for VC12 with E1 client on the PDH Port Module of1646 shelf

− MVC4TU12-{1-7}-{1-9}-{7}-{1-16}-{1-3}- {1-7}-{1-3} for TU12 within a MVC4 on SCC cardon 1646 Drop shelf.

Values valid for: LOVC3 command modifier

− VCGLOVC3-{1-7}-{1-9}-{2-9,12-19}-{1-24}-{1-24} for LO VC3 within a logical VCG on aMultiservice Packet Card

− MVC4TU3-{1-7}-{1-9}-{21,22,35,36}-{1- 64}-{1-3} for TU3 embedded within a ModifiableVC4.

− MVC4TU3-{1-7}-{1-9}-{7}-{1-16}-{1-3} for TU3 within a MVC4 on SCC card on 1646 Dropshelf

• x= MAU− MAU-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1-10} for MAU port on a 10xAny module

• x= ODU2− OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{C1, L1}-1 for ODU2 facility in an OTU2

on a DWLA10X module

• x=FC

− FC200-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1,3,5,7,9} for FC200 port on a 10xAny module

− FC400-{1-7}-{1-9}-{2-9,12-19, 21-36}-{3,7} for FC400 port on a 10xAny module

• x= OGPORT− OGPORT-{1-7}-{1-9}-{6-9,12-15}-{1-4} for Line port on a CWLA module - STM16

• x= OTU2− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port, OT2TDM or

DWLA10X module

− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module- OTU2, OC192, STM-64, 10GE

• x= STMN− STM1-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for STM1

− STM4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8 } for STM4

− STM16-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4, 5, 7} for STM16 on a 2G5SO or 10xANY

− OGPORT-{1-7}-{1-9}-{6-9,12-15}-{1-4} for Client port on a CWLA module-STM16

− STM64-{1-7}-{1-9}-{2-9,12-19,21-36}-1 for STM64

− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module- OTU2, OC192, STM-64, 10GE

− STM1-{1-7}-{1-9}-{7,8}-{1} for STM1 on Sub-module on SCC of 1646DS

− STM4-{1-7}-{1-9}-{7,8}-{1} for STM4 on Sub-module on SCC of 1646DS

− STM16-{1-7}-{1-9}-{7,8}-{1} for STM16 on Sub-module on SCC of 1646DS

1850 TSS-320/TSS-320H/TSS-160 Display Alarms

Release 5.1 (ETSI)September 2017Issue 4 3258DG09603CAAATQZZA

Page 326: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 selectablefor System Timing

− LINEREFOUT-{1-7}-{1-9}-{0-5} for Timing Reference of a Shelf for a Line Port selectablefor 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 PP10ADmodule

− MAUVCG-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} for VCG on a MAU port on a 10xAnymodule

− FC200VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1,3,5,7,9} for FC200 VCG on a 10xAnymodule- 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 a10xAny module - 24xVC4

− VCGVC4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10}-{1-7} for VC4 within a VCG on a 10xAnymodule

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

− MVC4-{1-7}-{1-9}-{21,22,35,36}-{1-64} for Modifiable VC4 on LOA card

− STM4AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-{1-4} for AU4 embedded within an STM4

− STM16AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1-16} for AU4 in an STM16 on a2G5SO or a 10xANY

− STM64AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-1-{1-64} for AU4 embedded within an STM64

− STM1AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-1 for AU4 embedded within an STM1

− STM4AU44C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-1 for AU4-4c embedded within an STM4

− STM16AU44C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1,5,9,13} for AU4-4c in anSTM16on a 2G5SO or 10xANY

− STM64AU44C-{1-7}-{1-9}-{2-9,12-19,21-36}-1-{1,5,9,13,17,21,25,29,33,37,41,45,49,53,57,61} for AU4-4c embedded within an STM64

− STM16AU416C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-1 for AU4-16c in an STM16 on a2G5PSO or 10xANY

− STM64AU416C-{1-7}-{1-9}-{2-9,12-19,21-36}-1-{1,17,33,49} for AU4-16c embeddedwithin an STM64

Display Alarms 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

326 Issue 4

Page 327: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module- OTU2, STM-64, 10GE , 10GFC

− 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 of1646DS

− MVC4-{1-7}-{1-9}-{7}-{1-16} for MVC4 on SCC card on 1646 Drop shelf

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

12

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

[

"<AID>,<AIDTYPE>:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>,

<LOCN>,<DIRN>,[<MONVAL>],[<THLEV>],[<TMPER>]" cr lf]*

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

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.

1850 TSS-320/TSS-320H/TSS-160 Display Alarms

Release 5.1 (ETSI)September 2017Issue 4 3278DG09603CAAATQZZA

Page 328: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

13

Go to Step 14.

14

STOP. This procedure is complete.

END OF STEPS

6.50 Display MPLS interface parameters

6.50.1 Purpose

This procedure provides the instructions to view the MPLS Interface parameters.

6.50.2 Prerequisites

The MPLS port (on DATA side) must be already set.

6.50.3 General

The RTRV-MPLSIF command retrieves MPLS Interface parameters (according to RFC3813mplsInterfaceTable parameters. This table represents the interfaces that are MPLS capable. Anentry is created for every MPLS capable interface on a LSR). MPLS Interface exists if and only if acorresponding entry in ifTable exists (with ifType = mpls (166)).

6.50.4 Procedure

1

Enter RTRV-MPLSIF::[AID]::::[SHOW-MODE=];

where:

• AID = Optional parameter. Access Identifier, specifies an access to the MPLS interfaces.Possible values:− ALL for all AID

− MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-10} for Local MPLS Interface

− MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-128} for VCG MPLS Interface

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

2

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

Display MPLS interface parameters 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

328 Issue 4

Page 329: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

"<AID>::MPLSIF-LABEL-MIN-IN=<value>,MPLSIF-LABEL-MAX-IN=<value>,

MPLSIF-LABEL-MIN-OUT=<value>,MPLSIF-LABEL-MAX-OUT=<value>,

MPLSIF-TOTAL-BAND=<value>,MPLSIF-AVAILABLE-BAND=<value>,

MPLSIF-LABEL-PARTICIPATION-TYPE=<value>,MPLSIF-VT-LIST=<value>:<PST>

"cr lf

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

3

STOP. This procedure is complete.

END OF STEPS

6.51 Display Status and Conditions

6.51.1 Purpose

This procedure provides the instructions to view the current status of any reported existing standingconditions in the system (alarmed and not alarmed for Equipment, Facility, and Common AIDs) orany standing conditions matching the specified combination of position-defined input parameters.

6.51.2 Prerequisites

None.

1850 TSS-320/TSS-320H/TSS-160 Display Status and Conditions

Release 5.1 (ETSI)September 2017Issue 4 3298DG09603CAAATQZZA

Page 330: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.51.3 General

The successful response for a RTRV-COND-ALL command contains one line of parsable outputdata for each condition being retrieved. If multiple conditions exist, a line of output is provided foreach.

Output is given for:

• Each equipment entity with standing conditions grouped by equipment type displayed inascending order of each of the AID fields (excluding the equipment type field) left to right, and inascending order by date and time of occurrence.

• All common (no specific entity) standing conditions in ascending order by date and time ofoccurrence.

• Each facility entity with standing conditions grouped by facility type displayed in ascending orderof each of the AID fields (excluding the facility type field, if any) left to right, and in ascendingorder by date and time of occurrence.

For standing (i.e. non-transient) Threshold Crossing Alerts the Parameters MONVAL, THLEV andTMPER will be reported. The parameters contain the values which are provided at the time thecondition 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 statusof any reported existing standing conditions in the system (alarmed and not alarmed forEquipment, Facility, and Common AIDs) or any standing conditions matching the specifiedcombination of position-defined input parameters.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

Display Status and Conditions 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

330 Issue 4

Page 331: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 19.

5

Retrieve Equipment status and conditions

Enter RTRV-COND-EQPT::AID:::[CONDTYPE],[LOCN]; to retrieve the current status ofany existing, standing conditions, for the specified equipment AID, in the system (alarmed, notalarmed, 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 toA.2 “Access Identifiers” (p. 611) for details on parameter values.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Display Status and Conditions

Release 5.1 (ETSI)September 2017Issue 4 3318DG09603CAAATQZZA

Page 332: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

"<AID>[,<AIDTYPE>]:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>,

<LOCN>" cr lf

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

7

Go to Step 19.

8

Retrieve All BITS status and conditions

Enter RTRV-COND-BITS::AID::[CONDTYPE]; to retrieve the current status of any reportedalarmed, not alarmed or not reported standing conditions, for the specified BITS AID, matchingthe 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

Display Status and Conditions 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

332 Issue 4

Page 333: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

9

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

"<AID>[,<AIDTYPE>]:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>"

cr lf

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

10

Go to Step 19.

11

Retrieve Facility status and conditions

Enter RTRV-COND-x::AID::[CONDTYPE],[LOCN],[DIRN]; to retrieve the current statusof 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

1850 TSS-320/TSS-320H/TSS-160 Display Status and Conditions

Release 5.1 (ETSI)September 2017Issue 4 3338DG09603CAAATQZZA

Page 334: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

may be retrieved with the RTRV-<x> command. The command is completed regardless ofwhether 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) fordetails on parameter values.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

12

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

[

"<AID>,<AIDTYPE>:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>,

<LOCN>,<DIRN>,[<MONVAL>],[<THLEV>],[<TMPER>]" cr lf]*

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

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.

Display Status and Conditions 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

334 Issue 4

Page 335: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 reportedalarmed, not alarmed, or not reported standing conditions, for the specified FFP AID, matchingthe specified combination of position-defined input parameters. The command is completedregardless of whether the FFP is provisioned.

where:

• AID = FFP Access Identifier, specifies the FFP facility in the FFP<x>-Rack-Shelf-Slot-Moduleformat 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 a2G5SO or 10xANY

− FFPSTM4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for STM4 Facility Protection Group

− FFPSTM1-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for STM1 Facility Protection Group

− FFPTUNNEL-{1-7}-{1-9}{1-4000} for TMPLS TUNNEL Protection Group

− FFPOC192-{1-7}-{1-9}-{2-9,12-19,21-36}-1 for OC192 Facility Protection Group

− FFPOC48-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4, 5, 7} for OC48 Facility Protection Group ona 2G5SO or 10XANY

− FFPOC12-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for OC12 Facility Protection Group

− FFPOC3-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} (OC3 Facility Protection Group)

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

15

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

1850 TSS-320/TSS-320H/TSS-160 Display Status and Conditions

Release 5.1 (ETSI)September 2017Issue 4 3358DG09603CAAATQZZA

Page 336: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 theconditions log file of the NE. The retrieved data can be filtered on any combination of thefollowing input parameter: an interval of dates and times, specific AID type, alarm events,non-alarmed events.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

18

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

Display Status and Conditions 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

336 Issue 4

Page 337: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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]

;

19

STOP. This procedure is complete.

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).

6.52.2 Prerequisites

The user must have administrator privileges to edit a user profile.

1850 TSS-320/TSS-320H/TSS-160 Edit User Profile

Release 5.1 (ETSI)September 2017Issue 4 3378DG09603CAAATQZZA

Page 338: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.52.3 General

The ED-USER-SECU command allows a user with administrator privileges to edit the existing userprofile entry, in the User Security Database. The command is denied if the user identified by thespecified 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

Enter RTRV-USER-SECU::[UID];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

2

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

Edit User Profile 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

338 Issue 4

Page 339: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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]

;

3

Enter RTRV-STATUS;

4

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

1850 TSS-320/TSS-320H/TSS-160 Edit User Profile

Release 5.1 (ETSI)September 2017Issue 4 3398DG09603CAAATQZZA

Page 340: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

(

":<SESSION>,[<UID>]:ADDR=<value>[,LAST=<value>]" cr lf)+

[

/*

<Command

Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

5

Is user to edit logged in?

If yes, user profile cannot be edited. Go to Step 9.

If no, go to Step 6.

6

Enter ED-USER-SECU::UID:::[NEWUID],[NEWPID,CONFIRMPID],,[UAP]:[PAGE=][,PCND=][,PCNN=][,POINT=][,UOUT=];

where: UID=User Identifier, specifies a unique user ID. Valid values for UID are <5-12 VALIDUID CHARACTERS>, case-sensitive alphanumeric characters where the first character mustalways be an alphabetic character. The following special characters are also accepted as validcharacters and will be part of the UID: % (percent sign), + (plus sign), # (pound sign), and _(under score).

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

7

Enter RTRV-USER-SECU::[UID];

Edit User Profile 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

340 Issue 4

Page 341: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

8

Observe output. Verify changes to user profile. All changes to the provisioned values take effectimmediately except for the PID parameter, which takes effect only on the next login for thatuser.

9

STOP. This procedure is complete.

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 thehousekeeping alarms and controls.

6.53.2 General

The NE is able to receive and process eight (8) separate customer-defined inputs for faultconditions arising externally to the NE.

The fault conditions is processed and reported as for internally detected fault conditions. It ispossible 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 circuitstate 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 anenvironmental 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 animpedance less than 470 Ohms. Driver applied voltage if any must be greater than -4v. Drivercircuit must be able to supply at lease 2mA minimum. A closed relay contact shall sufficient tocause a Low indication by the HKP alarms sensors.

• Alarm sensor inputs shall indicate a HIGH state when the customer driving circuitry has animpedance greater than 100K ohms. An open relay contact shall sufficient to cause a HIGHindication by the HKP alarms sensors.

1850 TSS-320/TSS-320H/TSS-160 Housekeeping Alarms Management

Release 5.1 (ETSI)September 2017Issue 4 3418DG09603CAAATQZZA

Page 342: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 26 Housekeeping input characteristics

Polarity Environment ConditionDetected

Physical signal

ALOW yes 0

AHIGH yes 1

ALOW no 1

AHIGH no 0

6.53.3 Before you begin

EC320 board must be provisioned.

6.53.4 Procedure

1

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 inputpoint 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

Housekeeping Alarms Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

342 Issue 4

Page 343: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 bySET-ATTR-ENV.

• ALMMSG identifies the alarm message, i.e. the text message associated with theenvironmental alarm as set by the SET-ATTR-ENV command.

4

Retrieve housekeeping alarm condition

It retrieves the current status of any existing, standing, housekeeping conditions in the system(alarmed, not alarmed, or not reported).

Enter:

RTRV-COND-ENV::AID;

where:

• AID = Access Identifier, identifies the entity access identifier.

Possible values:

CPI-{1-7}-{1-9}-1-{1-8} in the Rack-Shelf-Slot-External Input Point format.

ALL

5

Examine output:

where:

• NTFCNCDE identifies the type of alarm generated by the system upon occurrence of the eventidentified by the CONDTYPE.

Values are:

− CR critical alarm

− MJ major alarm

− MN minor alarm

− WR warning alarm ALMTYPE

− NA Not Alarmed

− NR Not Reported

1850 TSS-320/TSS-320H/TSS-160 Housekeeping Alarms Management

Release 5.1 (ETSI)September 2017Issue 4 3438DG09603CAAATQZZA

Page 344: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• ALMTYPE specifies the alarm type. Alarm type identifies the type of alarm as provisioned bySET-ATTR-ENV.

• ALMMSG identifies the alarm message, i.e. the text message associated with theenvironmental alarm as set by the SET-ATTR-ENV command.

6

Retrieve housekeeping alarm attribute

It retrieves the attributes associated with an environmental alarm. These attributes are includedwhen an environmental alarm is reported or retrieved.

Enter:

RTRV-ATTR-ENV::AID;

where:

• AID = Access Identifier, identifies the entity access identifier.

Possible values: CPI-{1-7}-{1-9}-1-{1-8} in the Rack-Shelf-Slot-External Input Point format.

7

Examine output:

where:

• NTFCNCDENoTiFiCatioNCoDE. Determines the severity of the alarm type.

Values are:

− CR critical alarm

− MJ major alarm

− MN minor alarm

− WR warning alarm ALMTYPE

− NA Not Alarmed

− NR Not Reported

• ALMTYPE specifies the alarm type. Alarm type identifies the type of alarm as provisioned bySET-ATTR-ENV.

• ALMMSG identifies the alarm message, i.e. the text message associated with theenvironmental alarm as set by the SET-ATTR-ENV command.

• Polarity. Determine when the external control is active. Values are: AHIGH Active highALOW Active low

8

Set housekeeping alarm attribute

To define on the input external-control points, an environment alarm type, a correspondingalarm message text, and a polarity, enter:

Housekeeping Alarms Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

344 Issue 4

Page 345: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

SET-ATTR-ENV::AID:::[NTFCNCDE],[ALMTYPE],[ALMMSG],[POLARITY];

where:

• AID = Access Identifier, identifies the entity access identifier.

Possible values: CPI-{1-7}-{1-9}-1-{1-8} in the Rack-Shelf-Slot-External Input Point format.

• NTFCNCDE = NoTiFiCatioN CoDE, specifies the notification code for the specified alarmtype. 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 VALIDCHARACTERS>. Default value: previously existing value.

• ALMMSG = Alarm Message. A text string that can be used to describe what the externalinput 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 beMANUAL (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. Theseattributes are used when an external control is operated or released. The related input command isRTRV-ATTR-CONT.

Releasing an external control means deactivating the relay.

In case of the automatic operation, a ConditionType and the associated AID can be configuredwhich 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, thenthe 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 operationalstate is released. If the operational state is OPER then the RLS-EXT-CONT command must beexecuted prior. The change from automatic to manual operation is always possible - if theoperational state was OPER before the execution of this command then the operational state is setto its default value implicitly.

OPR-EXT-CONT instructs an NE to operate an external control, such as a relay activation. Therelated contact pair is operated continuously.

1850 TSS-320/TSS-320H/TSS-160 Housekeeping Controls Management

Release 5.1 (ETSI)September 2017Issue 4 3458DG09603CAAATQZZA

Page 346: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

RLS-EXT-CONT instructs an NE to release an external control, such as a relay deactivation. Thecontrol 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. Thecommand 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. Thecommand can be used to audit the result of an OPR-EXT-CONT or a RLS-EXT-CONT command.

6.54.3 Procedure

1

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

Housekeeping Controls Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

346 Issue 4

Page 347: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 isALOW.

For parameter descriptions of TL1 commands used in this procedure, refer to the1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1Command Guide.

5

Operate housekeeping control

The user can de/activate output external-control points.

Enter:

OPR-EXT-CONT::AID;

where:

AID = Access IDentifier of the external control output points.

6

Release housekeeping control

Enter:

RLS-EXT-CONT::AID;

where:

AID = Access IDentifier of the external control output points.

END OF STEPS

1850 TSS-320/TSS-320H/TSS-160 Housekeeping Controls Management

Release 5.1 (ETSI)September 2017Issue 4 3478DG09603CAAATQZZA

Page 348: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.55 Initialize System Processors

6.55.1 Purpose

This procedure provides the instructions to reset processor-based modules provisioned andinstalled in the system.

6.55.2 Prerequisites

None.

6.55.3 General

This procedure is used to cold start, warm start, and power-on start the processor-based modulesprovisioned 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 isproviding service.

3. POWER-ON: full restart (as if unplugged and plugged), including reloading of processor, sw, dband matrix reinitialization. It is supported only by MT320/MT160, by Packets Processor Car andit 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 coldrestart of MT320/MT160, no reloading of IOCs FPGA. MODE= FRCD and PHASE=COLD arenecessary.

• power-on full reset of the NE is traffic affecting, it consists of cold restart of EC320, power-onrestart of MT320/MT160 and cold restart of IOCs if present. MODE= FRCD andPHASE=POWER-ON are necessary.

If an entity is providing service, COLD and POWER-ON restarts are allowed only if the FRCD modeis 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)

Initialize System Processors 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

348 Issue 4

Page 349: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 10XANY 10GB 10xGBE Card

• MultiService Adaptation Card (Packet Module 10G)

• Packet Module 10x1GbEthernet (Packet Module 10G)

• Packet Module 1x10GbEthernet (Packet Module 10G)

• Optical Pre-Amplifer 10G

• Optical Booster 10G Line

• Optical Filter and Attenuator (LOFA)

• DWDM Optical Transponder with Colored XFPs

• CWDM Optical Transponder (2.5G) without Optical Protection

• CWDM Optical Transponder (2.5G) with Optical Protection

• CWDM OADM 4ch w/o OSC coupler

• CWDM OADM 4ch w OSC coupler

• CWDM OADM 2ch w/o OSC coupler

• CWDM OADM 2ch w OSC coupler

• CWDM OADM 1ch w/o OSC coupler

• CWDM OADM 1ch w OSC coupler

• CWDM Mux/Demux 8ch w/o OSC coupler

• CWDM Mux/Demux 8ch with OSC coupler

• CWDM Mux/Demux 2ch with OSC coupler

• CWDM Mux/Demux 1ch with OSC coupler

• DWDM Mux/Demux 8 channels L1 band without S-band input/output

Shelf Types

• UNVRSL320 (Generic 320 type shelf)

• UNVRSL160 (Generic 160 type shelf)

• ALL (MT320/MT160 and all the boards equipped in the NE)

6.55.4 Procedure

1

Select action.

To initialize an individual module, go to Step 2.

To initialize system, go to Step 4.

2

Initialize an Individual Module

1850 TSS-320/TSS-320H/TSS-160 Initialize System Processors

Release 5.1 (ETSI)September 2017Issue 4 3498DG09603CAAATQZZA

Page 350: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter INIT-SYS::AID:::PHASE,[MODE];

where:

• AID=Access identifier of equipment entity. Possible values:− ALL for all equipped board in the NE

− SHELF-{1-7}-{1-9} for Shelf

− EC320-{1-7}-{1-9}-{1,20} for Equipment Controller Card TSS-320

− MT320-{1-7}-{1-9}-{10,11} for Matrix and Timing TSS-320

− MT160-{1-7}-{1-9}-{10,11} for Matrix and Timing TSS-160

− 10GSO-{1-7}-{1-9}-{2-9,12-19,21-36} for 10G Synchronous Optical

− 2G5SO-{1-7}-{1-9}-{2-9,12-19,21-36} for 2.5G Synchronous Optical

− 8XSO-{1-7}-{1-9}-{2-9,12-19,21-36} for 8 x Synchronous Optical

− OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} for G.709 OTU 10GB Card - Provisioned Type =1POTU2

− 10XANY-{1-7}-{1-9}-{2-9,12-19,21-36} for 10XANY Card

− LOA10G-{1-7}-{1-9}-{21,22,24,33,35,36} for Lower Order Adaptation Card with EPS

− PRE-{1-7}-{1-9}-{2-9,12-19,21-36} for Preamplifier

− BOOST-{1-7}-{1-9}-{2-9,12-19,21-36} for Booster

− LOFA-{1-7}-{1-9}-{6-9,12-15} for Line Optical Filter and Attenuator

− DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} for DWDM Optical Transponder

− CWLA-{1-7}-{1-9}-{6-9,12-15} for CWDM Optical Transponder

− CADM-{1-7}-{1-9}-{6,7,8,9,12,13,14,15} for CWDM OADM

− CMDX-{1-7}-{1-9}-{6-9,12-15} for CWDM MUX/DEMUX

− OMDX8-{1-7}-{1-9}-{6-9,12-15} for DWDM MUX/DEMUX 8 channels

− PP10AD-{1-7}-{1-9}-{2-9,12-19} for Adaptation Card Packet Modules 10G

− PP1GE-{1-7}-{1-9}-{2-9,12-19} for Packet Module 10x1Gb

− PP10GE-{1-7}-{1-9}-{2-9,12-19} for Packet Module 1x10Gb

• PHASE = identifies the type of restart. Possible values:− WARM: reload of dynamic data only (db in RAM).

− COLD: reload of dynamic and static data (db and sw). It is supported by MT320/MT160,EC320, IOC. It is used with AID=ALL for normal full reset of the NE (cold restart of EC320followed by cold restart of MT320/MT160).

− POWER-ON: full restart (as if unplugged and plugged), including processor restart andreloading sw and db. It is supported by MT320/MT160. It is used with AID=ALL forpower-on full reset of the NE (cold restart of EC320, power-on restart of MT320/MT160,cold restart of IOCs).

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Go to Step 5.

Initialize System Processors 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

350 Issue 4

Page 351: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4

Initialize System

Enter INIT-SYS::ALL:::PHASE,FRCD;

where:

• PHASE = identifies the type of restart. Possible values above described.

• FRCD = Forced. The command is completed even if the result of its execution is service-affecting.

5

STOP. This procedure is complete.

END OF STEPS

6.56 LCAS Monitoring

6.56.1 Purpose

This procedure provides the instructions to monitor the Link Capacity Adjustment Scheme (LCAS)protocol.

6.56.2 Prerequisites

None.

6.56.3 General

The procedure monitors the Link Capacity Adjustment Scheme (LCAS) protocol. This procedurecan 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 ordisabled.

The successful response for a MON-LCAS command contains multiple lines of parsable outputdata.

The first line contains information pertaining to the overall virtual concatenation group level followedby one line each for information regarding each member the Virtual Concatenation group, in theascending 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.

1850 TSS-320/TSS-320H/TSS-160 LCAS Monitoring

Release 5.1 (ETSI)September 2017Issue 4 3518DG09603CAAATQZZA

Page 352: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 ona PP20G module

• GBEVCG-{1-7}-{1-9}-{2-9,12-19,21-36}- {1-10} for VCG on a GBE port on a 10xAny module

• MAUVCG-{1-7}-{1-9}-{2-9,12-19,21-36}- {1-10} for VCG on a MAU port on a 10xAny module)

• FC200VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1,3,5,7,9} for FC200 VCG on a 10xAny module-12xVC4 )

• FC400VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{3,7} for FC400 VCG on a 10xAny module -24xVC4)

2

Examine output as detailed in the relevant command guide, refer to “Command details”(p. 107).

LCAS Monitoring 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

352 Issue 4

Page 353: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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]+

[

/*

<Informational_Description_Text>

*/ cr lf]

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

3

STOP. This procedure is complete.

END OF STEPS

1850 TSS-320/TSS-320H/TSS-160 LCAS Monitoring

Release 5.1 (ETSI)September 2017Issue 4 3538DG09603CAAATQZZA

Page 354: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.57 Log Into System

6.57.1 Purpose

This procedure provides the instructions to establish a session with the network element (NE) andto log in a specific user to the 1850 TSS-320, TSS-320H and TSS-160.

6.57.2 Prerequisites

The User Identifier (UID) and current Password Identifier (PID) must be known before login can beaccomplished.

6.57.3 General

To access the system via telnet (either with or without the EMA), port 3083 must be used. To accessthe 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 thepassword. 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 usercan 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 UIDCHARACTERS>, case-sensitive alphanumeric characters where the first character mustalways be an alphabetic character. The following special characters are also accepted asvalid 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 byEMS ZIC. Valid values for OMSID are an <Alphanumeric string>.

• PID = Password Identifier, specifies the user's login password. Valid values for PID are astring of <8-12 VALID PID CHARACTERS> case-sensitive alphanumeric characters. The PIDmust contain at least three of the following: at least one upper alphabetic character, at leastone lower alphabetic character, at least one numeric character, at least one special character.The following special characters shall be valid: % (percent sign), + (plus sign), # (poundsign), and _ (under score). The first character of the PID can be an alphabetic, numeric, or avalid special character.

• HOSTIP = IP address of the PC hosting the Web Browser for ZIC GUI application. Valid

Log Into System 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

354 Issue 4

Page 355: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

values for HOSTIP are {0-255}-{0-255}-{0-255}-{0-255}. This parameter is optionally passedto NE by ZIC application in order to provide to the NE the needed information for correct LOGand reporting.

2

Did system return a successful response?

If no, go to Step 3.

If yes, go to Step 4.

3

System returns error code when current logged-in user enters ACT-USER command. Refer toA.4 “Codes” (p. 629) in this manual for complete list of error codes and definitions. For securitypurposes, system does not return error code when user who is not logged into system entersunsuccessful 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 systemlogin.

4

STOP. This procedure is complete.

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 aspecific user.

6.58.2 Prerequisites

None

6.58.3 General

A user can log only their own active User Identification (UID) out of the system. A SystemAdministrator can log any other user out of the system.

The CANC-USER command unauthenticates a session with the addressed NE (identified byoptional 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-offanother user. The log-off of another user is up to users with security administration privileges and itis realized by means of the CANC-USER-SECU command,

1850 TSS-320/TSS-320H/TSS-160 Log Out of System

Release 5.1 (ETSI)September 2017Issue 4 3558DG09603CAAATQZZA

Page 356: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The CANC-USER-SECU command unauthenticates a session with the addressed NE (identified byoptional 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 securityadministrator, 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 VALIDUID CHARACTERS>, case-sensitive alphanumeric characters where the first character mustalways be an alphabetic character. The following special characters are also accepted as validcharacters and will be part of the UID: % (percent sign), + (plus sign), # (pound sign), and _(under score).

3

Go to Step 5. Log Out Other UID

4

Enter CANC-USER-SECU::UID;

where UID = User Identifier, specifies a unique user ID. Valid values for UID are <5-12 VALIDUID CHARACTERS>, case-sensitive alphanumeric characters where the first character mustalways be an alphabetic character. The following special characters are also accepted as validcharacters and will be part of the UID: % (percent sign), + (plus sign), # (pound sign), and _(under score).

5

Observe output.

6

Did system return a successful response?

If yes, go to Step 10.

If no, go to Step 7.

Log Out of System 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

356 Issue 4

Page 357: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

7

Check error code message. Does error code indicate invalid input parameters?

If yes, check input and spelling. Go to Step 4 to retry command.

If no, go to Step 8.

8

Check error code message. Does error code indicate requested operation failed?

If yes, go to Step 4 to retry command.

If no, go to “” (p. 356) to determine next command to execute.

Find appropriate command in this manual or refer to “Command details” (p. 107).

9

Go to Step 10.

10

STOP. This procedure is complete.

END OF STEPS

6.59 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 aservice as per IEEE1588 recommendation.

The System supports the Best master clock selection algorithm to provide protection accordingIEEE 1588 recommendation.

The purpose of Time of Day feature is to distribute a local 1 second period time of day signal toother 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 configuredvalue 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 onthe 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.

1850 TSS-320/TSS-320H/TSS-160 Master TOD Card Management

Release 5.1 (ETSI)September 2017Issue 4 3578DG09603CAAATQZZA

Page 358: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Note: TOD information via 1588 PTP and TOD information via NTP are managed in parallelby 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 systemallows 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 1588logical port.

6.59.3 Before you begin

Before provisioning insert TOD card. The card is auto-provisioned if NE is in AutoProvision mode.

6.59.4 Procedure

1

Select action

• Master TOD Card Creation, go to Step 2

• Phase Synchronization reference configuration, go to Step 11

• Master TOD Card Deletion, go to Step 14.

2

Master TOD Card Creation

Enter:

ENT-EQPT::AID::::PROVISIONEDTYPE=PP1588, CKMODE=MASTER;

where:

• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card

• CKMODE=MASTER means that the PP1588 card is configured in Master ClockConfiguration.

Result:

The following resources are enabled:

• 1 PPS-IN port

• 1 PPS-OUT port

• 1 PTP Slave port

3

Check the card InService state.

Enter:

RTRV-PTPMASTER::[AID];

Master TOD Card Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

358 Issue 4

Page 359: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

where:

AID = PTPMASTER-{1-7}-{1-9}-{2-9, 12-19, 21-36}-1

4

Select action:

manage PPS-IN port facility, go to Step 5

manage PPS-OUT port facility, go to Step 8

manage PTP Master port facility, go to Step 10

5

For PPS-IN port the facility PPSIN-r-s-b-1 is created and the following parameters can beprovisioned:

ED-PPSIN::AID::::[CMDMDE=][,TOD=][,DLY=][,ALMPROF=]:[PST];

where:

• AID = PPSIN-{1-7}-{1-9}-{2-9, 12-19, 21-36}-1 (Pulse Per Second Input Port).

PPSIN Access Identifier, specifies the input port receiving the PPS signal

• TOD= Time Of Day, determines if the information about Time Of Day shall be expected asinput (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 forsynchronization. The delay is due to the length of the cable on the link. The lengthdetermines a propagation delay equal to D [ns], where D is the value to be provisioned. Theparameter applies to the receiver; normally positive values shall be provisioned; but negativevalues can be provisioned as well for compensating excessive delays provisioned at theother side transmitter. The unit of measure is nanosecond.

6

Enter:

RTRV-PPSIN::[AID];

The RTRV-PPSIN command retrieves the provisioning and state information of one or moreports, 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 ofparsable output data, in ascending order, listing the possible timing input ports used by thesystem.

7

Each timing reference can be assigned (i.e. connected) to a port. The PPS IN port (i.e. linetiming reference) can be assigned to a timing reference.

1850 TSS-320/TSS-320H/TSS-160 Master TOD Card Management

Release 5.1 (ETSI)September 2017Issue 4 3598DG09603CAAATQZZA

Page 360: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

8

For PPS-OUT the facility PPSOUT-r-s-b-1 is created and the following parameters can beprovisioned

ED-PPSOUT::AID::::[S1TRANS=][,TOD=][,DLY=];

where:

• AID = PPSOUT-{1-7}-{1-9}-{2-9, 12-19, 21-36}-1 (Pulse Per Second Output Port)

I.e. Access Identifier, specifies the output port transmitting the PPS signal.

• S1TRANS = {ACT, PRC, SSUL, SSUT, SEC, DUS, NONE}.

Sync message byte to be transmitted, determines if the transmitted byte will have the "DUS"message or will have the actual traceability of the signal.

• TOD= Time Of Day, determines if the information about Time Of Day shall be expected asinput (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 forsynchronization. The delay is due to the length of the cable on the link. The lengthdetermines a propagation delay equal to D [ns], where D is the value to be provisioned. Theparameter applies to the receiver; normally positive values shall be provisioned; but negativevalues can be provisioned as well for compensating excessive delays provisioned at theother side transmitter. The unit of measure is nanosecond.

9

Enter:

RTRV-PPSOUT::[AID]:;

To retrieve the provisioning and state information of one or more ports, in the 1588v2application, dedicated to the transmission of the PPS signal.

Result: The successful response for a RTRV-PPSOUT command contains one or more linesof parsable output data, in ascending order, listing the possible timing output ports used bythe 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 moreports, in the 1588v2 application.

The command is executed regardless of the state of the Master port.

Master TOD Card Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

360 Issue 4

Page 361: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The successful response for a RTRV-PTPMASTER command contains one or more lines ofparsable output data, in ascending order (from lowest specified PTPMASTER AID to the largestspecified PTPMASTER AID), for each PTPMASTER AID specified.

11

The Phase configuration applies either to input and output direction.

Provide phase distribution from ToD signal info or from the input PPS interface.

12

Enter:

ED-PHASE::AID::::[SYNCMSG=][,ASSPORTAID=][,PROVQL=][,REFP RIO=];

where:

• AID = Phase Access Identifier, specifies either the phase node for the system phase entity(delivering the system phase reference PH0) or a phase reference (PPS or Slave Clock portconnected 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 SystemPhase)

• SYNCMSG = SYNCMSG, determines if the timing reference selection for system phase isusing 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 bypriorities as second criteria.

• ASSPORTAID = ASSPORTAID specifies whether the phase reference is assigned to a portand if assigned it specifies the AID of the port. The following port types can be used forestablishing a connection towards a timing reference: PPS Input assigned to a phasereference

Note: The user is able to select the AID of the phase entity to be modified for the SyncMessaging (SYNMSG) management , specifying if the phase reference selection forsystem phase is using sync messaging (SSM Qualities) or not. (Y/N)

13

To configure PTP clock and ports refer to the 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 Command Line Interface Guide.

Note: After the proper configuration of the 1588 port and parameters configure an ELANservice to connect the 1588 port with the ‘bridge’ function needed to forward / receivepackets to / from the network.

14

1850 TSS-320/TSS-320H/TSS-160 Master TOD Card Management

Release 5.1 (ETSI)September 2017Issue 4 3618DG09603CAAATQZZA

Page 362: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

TOD Card deletion

Note: The steps below should be done using the SNMP or CLI commands.

First the user should:

• 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

The ETS Cross-connection should be deactivated and deleted, refer to the the CLI commandguide.

16

Management Operator Disabling of PTP protocol over PTP logical Master port via setting ofieee1588PtpPortDSAdminStatus to Disabled value. See CLI Command Guide.

17

If PPSIN has been configured as input for CRU (T0 and/or T4) or for internal Phase Distributor,it has to be de-provisioned.

18

The PTP logical Master port must be disabled at SNMP side. Please refer to the CLI commandguide.

19

The TOD card shall be logically removed.

Enter:

RMV-EQPT::AID;

or

ED-EQPT::AID:OOS;

where:

• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card

Note: TOD Card logical removal is mandatory also for avoiding traffic hits upon NGI linksof otherCollector cards eventually present in the shelf.

20

Enter:

Master TOD Card Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

362 Issue 4

Page 363: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

DLT-EQPT::AID;

where:

• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card

Result: The command causes the Deactivation/Deletion of PTP Master logical port (bothSNMP and TL1 side), of PPSIN and PPSOUT ports.

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 ofRx power falling below or raising above a configured threshold in order to identify intrusion in theoptical line.

The mechanism shall be applicable to UNI/NNI interfaces.

The following proposal is aimed to use the values retrieved by DDM for providing degradeinformation and are hereafter described:

• The operator/NMS provides a configurable threshold (“delta” with 0.1dB granularity) for eachSTM-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 thecomparison 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 intrusionmonitoring” 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 automaticallycleared at time out expiration (default value equal to 24 h).

• The default ASAP severity is MAJ instead of WR.

1850 TSS-320/TSS-320H/TSS-160 Optical Intrusion Overview

Release 5.1 (ETSI)September 2017Issue 4 3638DG09603CAAATQZZA

Page 364: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.60.3 New alarm definition

New alarm requires the introduction of a new standing condition associated to STM64 facility, whichshall 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 notificationhas been emitted (i.e. OIDET parameter is equal to RAISED), monitoring of received optical poweron 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 previouslydetected.

It shall be noticed that at NE restart all optical intrusion alarms, currently active just before NErestart, will be raised again without changing Conddescr string respect to the previous alarmnotification.

6.61 Optical Intrusion Adminstration

6.61.1 Purpose

Use this procedure to enable/disable the mechanism for intrusion detection and configure thethreshold 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

1

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

Optical Intrusion Adminstration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

364 Issue 4

Page 365: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 theoptical intrusion detection is disabled or not on the port. Once enabled, if an optical intrusionevent has been detected, the value changes autonomously to raised. Once raised, the alarmclear notification can be triggered by changing the value to enabled or to disabled. Otherwisethe alarm clear notifcation occurs when global times TOUT-CLR expires, changing the valuefrom 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 isdirected.

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 twomeasurements of received power, PRx(tn)-PRx(tn+1); if the calculated value is higher than thisvalue, 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 isdirected.

Result: The command shows the OITHR output parameter value and format

1850 TSS-320/TSS-320H/TSS-160 Optical Intrusion Adminstration

Release 5.1 (ETSI)September 2017Issue 4 3658DG09603CAAATQZZA

Page 366: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6

For the threshold configuration also the TimeOut of Clear alarm notification should bedefined. Enter:

SET-PRMTR-NE::::::[,TOUT-CLR=];

where:

TOUT-CLR= TimeOut of Clear alarm notification, represents the maximum time that alarm shallstay on, before sending an esplicit clear alarm notification. Affected Alarms are the ones withoutan 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 withoutchanging the local alarm reporting.

6.62.2 Prerequisites

None

6.62.3 General

The OPR-ACO-COM command is used to cut off the office audible alarm indications withoutchanging 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 newaudible 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 ACOLED is turned on and a new alarm arrives, it is presented to the audible closures. The ACO LED isturned 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 arestill present; only new alarms will be presented to the audible closures.

6.62.4 Procedure

1

Enter OPR-ACO-COM;

2

STOP. This procedure is complete.

END OF STEPS

Perform Audible Alarm Cutoff 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

366 Issue 4

Page 367: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 protectedboards (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 associatedprotection module.

6.63.2 Prerequisites

For redundant equipment, both copies must be provisioned and in service (IS).

The Protection Group associated to LOA10G is created on LOA10G creation in protection slot: thatis, the Switching mechanism starts when the protection slot is provisioned. In the shelf twoProtection groups are settable: one with slot 24 for protection and slots 21 and 22 as working andanother 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 ismanually 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 enabledand 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, clearsthe 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

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

Release 5.1 (ETSI)September 2017Issue 4 3678DG09603CAAATQZZA

Page 368: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter SW-TOPROTN-EQPT::AID:::[MODE]

where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.Possible values:

• LOA10G-{1-7}-{1-9}-{21,22,24,33,35,36} for Lower Order Adaptation Card with EPS

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Important! It is not recommended to perform a forced protection switch withoutassistance from Nokia CTAC.

3

Go to Step 7.

4

Switch LOA10G to Working

Enter SW-TOWKG-EQPT::AID:::[MODE];

where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.Possible values:

• LOA10G-{1-7}-{1-9}-{21,22,24,33,35,36} for Lower Order Adaptation Card with EPS

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Important! It is not recommended to perform a forced protection switch withoutassistance from Nokia CTAC.

5

Go to Step 7.

6

Perform Copy Switch for Redundant Equipment

Enter SW-DX-EQPT::AID:::[MODE];

where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.Possible values:

• EC320-{1-7}-{1-9}-{1,20} for Equipment Controller Card TSS-320

• MT320-{1-7}-{1-9}-{10,11} for Matrix and Timing TSS-320

• MT160-{1-7}-{1-9}-{10,11} for Matrix and Timing TSS-160

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Important! It is not recommended to perform a forced protection switch withoutassistance from Nokia CTAC.

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

368 Issue 4

Page 369: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

7

STOP. This procedure is complete.

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 toa Remote File Server Database (RFSDB), and to cancel an in-progress file transfer.

6.64.2 Prerequisites

To perform this procedure the NE being backed up must have IP-based access and the user mustbe 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. Thesystem 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 toautomatically 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 asuccessful file transfer operation.

• STDBY DB—Secondary backup database on the NE's disk. This database is created during asuccessful backup operation. It is copied to the ACTV DSK DB and ACT CPU DB during asuccessful restoration operation. The STDBY DB can also be copied to/from the RFS.

1850 TSS-320/TSS-320H/TSS-160 Perform Remote Database Backup

Release 5.1 (ETSI)September 2017Issue 4 3698DG09603CAAATQZZA

Page 370: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

ACT-DB-BACKUP is used to perform a backup of the primary database (ACT DSK DB) to thesecondary database (STDBY DB). The database information backed up includes provisioning andcross-connection information. ACT-DB-BACKUP will also write the system type, software releaseidentifier, 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 specifiedRemote 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 initiatedCOPY-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 alreadytransferred 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

Figure 26 Database Types

Perform Remote Database Backup 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

370 Issue 4

Page 371: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

files might exist on the RFS after an upload gets canceled. The system does not take care ofthese remote files. It is the responsibility of the RFS maintainer in this case to do the clean up, orto 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 toFigure 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-RFILEcommand 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 (REPTCOPY RFILE).

1850 TSS-320/TSS-320H/TSS-160 Perform Remote Database Backup

Release 5.1 (ETSI)September 2017Issue 4 3718DG09603CAAATQZZA

Page 372: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.64.4 Procedure

1

Select action.

To perform remote database backup, go to Step 2.

Figure 27 Database Backup and File Transfer to RFS

Perform Remote Database Backup 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

372 Issue 4

Page 373: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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'ssecondary backup database) or RFSDB (A database backup on a Remote File Server) orRFSSW (A software generic on a remote file server) or LOCPMGLB (Local NE PM Global filecollection) or RFSSCRIPT (A script files collection on a remote file server), LOCFILE (LocalNE 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. Possiblevalues: RFSDB (A database backup on a Remote File Server) or STBYDB (The system'ssecondary backup database) or STBYSW (The standby software generic on the NE) orRFSPMGLB (Remote File Server PM Global file collection) or LOCSCRIPT (Local NE scriptfiles collection), RFSFILE (A single file on a remote file server), or RFSMACGLB (The MACFile Collection on a Remote File Server). The following table shows the allowed combinations

1850 TSS-320/TSS-320H/TSS-160 Perform Remote Database Backup

Release 5.1 (ETSI)September 2017Issue 4 3738DG09603CAAATQZZA

Page 374: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 betransferred. 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 thefollowing syntax: [/]<cwd1>/<cwd2>/.../<cwdN> where <cwd1> through <cwdN>

are strings that identify directories. The <cwd1>-<cwdN> portion of the <url-path> isinterpreted 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.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

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. Possiblevalues previously referred in Step 4.

• TO=It specifies the entity that gets created as the result of the command completion of theCOPY-RFILE to be canceled. Possible values previously referred in Step 4..

Perform Remote Database Backup 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

374 Issue 4

Page 375: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

7

STOP. This procedure is complete.

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.

6.65.2 Prerequisites

To perform this procedure the NE being restored must have IP-based access and the user must belogged 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 toautomatically 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 asuccessful file transfer operation.

• STDBY DB—Secondary backup database on the NE's disk. This database is created during asuccessful backup operation. It is copied to the ACTV DSK DB and ACT CPU DB during asuccessful restoration operation. The STDBY DB can also be copied to/from the RFS.

1850 TSS-320/TSS-320H/TSS-160 Perform Remote Database Restore

Release 5.1 (ETSI)September 2017Issue 4 3758DG09603CAAATQZZA

Page 376: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

RTRV-RFILE is used to retrieve information related to transferred files (database) on a Remote FileServer (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 abackup 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 systemmatches information in the description file for the database to be restored. This information includesthe system type, software release stream, software release number, time stamp, and SystemIdentifier (SID).

The RESTORE-DB command copies the backup database stored on STDBY DB to the primarybackup 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

Figure 28 Database Types

Perform Remote Database Restore 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

376 Issue 4

Page 377: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

on the NE (ACT DSK DB or STDBY DB). If STDBY DB is selected and VERIFY is specified for theVER parameter, a Cyclic Redundancy Check (CRC) verification on the database is performed. Ifthe calculated CRC and stored CRC do not match, an unsuccessful response (DENY) message isreturned for the RTRV-DB-LABEL command.

The following steps describe the basic procedure of creating a remote database restore. Refer toFigure 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-RFILEcommand 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 (REPTCOPY RFILE).

6. The RESTORE-DB command is sent to the NE to start the activation of the restored database.

1850 TSS-320/TSS-320H/TSS-160 Perform Remote Database Restore

Release 5.1 (ETSI)September 2017Issue 4 3778DG09603CAAATQZZA

Page 378: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Figure 29 Database Transfer and Restore from RFS to NE

Perform Remote Database Restore 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

378 Issue 4

Page 379: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 Adatabase backup on a Remote File Server

• LOCATION= Location indicates the source/destination of the files on an RFS. The syntax ofthe 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 thefollowing syntax: [/]<cwd1>/<cwd2>/.../<cwdN> where <cwd1> through <cwdN> arestrings that identify directories. The <cwd1>-<cwdN> portion of the <url-path> is interpretedas a series of FTP commands as each of the cwd elements is to be supplied, sequentially, asthe argument to an FTP CWD (change working directory) command.

2

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

1850 TSS-320/TSS-320H/TSS-160 Perform Remote Database Restore

Release 5.1 (ETSI)September 2017Issue 4 3798DG09603CAAATQZZA

Page 380: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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

[

/*

<Informational_Description_Text>

*/ cr lf]

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

3

Enter COPY-RFILE::FROM,TO::::,LOCATION=[,CMDMDE=];

where:

• FROM= Specifies the entity to be transferred. Possible values: STBYDB (The system'ssecondary backup database) or RFSDB (A database backup on a Remote File Server) orRFSSW (A software generic on a remote file server) or LOCPMGLB (Local NE PM Global filecollection) or RFSSCRIPT (A script files collection on a remote file server), LOCFILE (LocalNE 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. Possiblevalues: RFSDB (A database backup on a Remote File Server) or STBYDB (The system'ssecondary backup database) or STBYSW (The standby software generic on the NE) orRFSPMGLB (Remote File Server PM Global file collection) or LOCSCRIPT (Local NE scriptfiles collection), RFSFILE (A single file on a remote file server), or RFSMACGLB (The MACFile Collection on a Remote File Server). The following table shows the allowed combinations

Perform Remote Database Restore 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

380 Issue 4

Page 381: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 betransferred. 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 thefollowing syntax: [/]<cwd1>/<cwd2>/.../<cwdN> where <cwd1> through <cwdN>

are strings that identify directories. The <cwd1>-<cwdN> portion of the <url-path> isinterpreted 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.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

4

Wait for command completion message.

5

Enter RESTORE-DB::::::[CMDMDE=];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Wait for command completion.

7

Enter RTRV-DB-LABEL; to verify newly restored database is present in the system.

The answer of the system will be the following, as detailed in the relevant command guide, referto “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Perform Remote Database Restore

Release 5.1 (ETSI)September 2017Issue 4 3818DG09603CAAATQZZA

Page 382: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

"<AID>:[<SYSTYPE>],[<RLSID>],[<SID>],[<DATE>],[<TIME>][,<CRC>]" cr lf

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

8

STOP. This procedure is complete.

END OF STEPS

6.66 Port segregation Management

6.66.1 Purpose

Use this procedure to avoid remote NE’s (RNE) inter-communication via ingress ports, formanagement purposes.

6.66.2 General

The typical scenario is shown below, with RNEs (TSS3) of different customers. NM shall be able tocommunicate with all TSS3, but TSS3 nodes shall not communicate between them:

Port segregation Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

382 Issue 4

Page 383: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The system supports configuration of a list of IP addresses, called “port segregation list”, containingthe IP addresses of the machines that are connected to the network and are allowed tocommunicate 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 asingle NE.

6.66.3 Before you begin

Port Segregation is enabled/disabled via TL1 command (SET-ATTRSECUDFLT) with NE inSECURE mode. By default this feature is disabled (i.e. no check & filtering is applied by the systemon RNEs IP addresses).

Note: Port Segregation must not be enabled if the “port segregation list” is empty, since it willmake the NE unreachable.

Figure 30 Port segregation scenario

1850 TSS-320/TSS-320H/TSS-160 Port segregation Management

Release 5.1 (ETSI)September 2017Issue 4 3838DG09603CAAATQZZA

Page 384: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 addedto 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 anIP 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, onlyports 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 transferfiles to/from the NE.

• SECPORTMODE=ENABLE, the NE shall discard all the IP packets with either SA or DA notmatching with any IP address in the current port-segregation list (see ED-PORTSEGLIST).

Port segregation Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

384 Issue 4

Page 385: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

When the feature is disabled (SECPORTMODE=DISABLE), the NE shall not apply theport-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 thesystem.

6.67.2 Prerequisites

The NE is based on three different Main Shelf versions, that is UNVRSL320, UNVRSL160 andUNVRSL160C. 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 thespecified equipment (also called pre-provisioning) regardless of whether the equipment is installedin 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 cardbeing inserted.

The following equipment is non-mandatory and can be pre-provisioned into the system:

• protection EC320

• Lower Order Adaptation Card 10G

• 10GSO (STM-64) card

• 10GSO (OC-192/STM-64) Evolution card

• 2.5G (STM-16) module

• 8 Port (STM-1)/(STM-4) card

• 8 Port Multirate 8xSTM1/4 - 4xSTM16 Card

• 63 E1 Port Card

• 63 E1 Access Card (75 vs 120 ohm)

1850 TSS-320/TSS-320H/TSS-160 Provision Equipment

Release 5.1 (ETSI)September 2017Issue 4 3858DG09603CAAATQZZA

Page 386: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 63 E1 Protection Card

• G.709 OTU 10GB Card (OT2TDM)

• G.709 OTU 10GB Card with XFP

• ANYFC 10GB 10 x FC-2/FC-4

• 10XANY 10GB 10xGBE Card

• MultiService Adaptation Card (Packet Module 10G)

• MultiService Adaptation Card for ATM (Packet Module 10G)

• Universal GateWay UGW Adaptation Card (Packet Module 10G)

• Packet Module 10x1GbEthernet (Packet Module 10G)

• Packet Module 20x1GbEthernet

• Packet Module 1x10GbEthernet (Packet Module 10G)

• Packet Module 2x10GbEthernet

• Optical Pre-Amplifer 10G

• Optical Booster 10G Line

• Optical Filter and Attenuator (LOFA)

• DWDM Optical Transponder with Colored XFPs

• CWDM Optical Transponder (2.5G) without Optical Protection

• CWDM Optical Transponder (2.5G) with Optical Protection

• CWDM OADM 4ch w/o OSC coupler

• CWDM OADM 4ch w OSC coupler

• CWDM OADM 2ch w/o OSC coupler

• CWDM OADM 2ch w OSC coupler

• CWDM OADM 1ch w/o OSC coupler

• CWDM OADM 1ch w OSC coupler

• CWDM Mux/Demux 8ch w/o OSC coupler

• CWDM Mux/Demux 8ch with OSC coupler

• CWDM Mux/Demux 2ch with OSC coupler

• CWDM Mux/Demux 1ch with OSC coupler

• DWDM Mux/Demux 8 channels L1 band without S-band input/output

• XFP on 10GSO modules

• SFP on 2G5SO modules

• SFP on 8XSO modules

• SFP on 10XANY modules

• 1000BASE-BX20 (Upstream and Downstream)

• 1000BASE-BX40 (Upstream and Downstream)

• FE 100BASE-BX20 (Upstream and Downstream)

• OC-48/STM-16 40km BiDi (Upstream and Downstream)

Provision Equipment 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

386 Issue 4

Page 387: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• OC-48/STM-16 15km BiDi (Upstream and Downstream)

• OC-48/STM-16 2km BiDi (Upstream and Downstream)

Shelf Types

• UNVRSL320 (Generic 320 type shelf)

• UNVRSL160 (Generic 160 type shelf)

• 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 AppendixB, “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 NOWAITindicates an alarm is generated due to an unplugged module.

The PROVISIONEDTYPE parameter identifies the Nokia mnemonic stored in the Remote InventoryEPROM 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 theREGION 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

1850 TSS-320/TSS-320H/TSS-160 Provision Equipment

Release 5.1 (ETSI)September 2017Issue 4 3878DG09603CAAATQZZA

Page 388: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 accessidentifier 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 andUNVRSL160C

• SR2U - 1646SM R2.0 2RU Drop Shelf

• P63E1 - 63 x E1 Port Module

• A63E1A - 63 x E1 Access Module 75ohm unb

• A63E1B - 63 x E1 Access Module 120ohm bal

• LSPROT - 63 x E1 Access Protection Module

• PE1A - 1646DS 42XE1 120 OHM Card

• PE1B - 1646DS 42XE1 75 OHM Card

• M1S1 - 1646DS 1XSTM1 sub-module

• M1S4 - 1646DS 1XSTM4 sub-module

• M1S16 - 1646DS 1XSTM16 sub-module

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Note:When a Shelf is provisioned, there are automatically created some Mandatory EquipmentEntities, according to the following list:

• UNVRSL320 Main Shelf Role: EC320 (slot 1), MT320 (slot 10 and 11), PSF320 (slot37 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 (slot37 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 (slot37 and 39), TB160J (slot 42 and 43), FANDRAWER (slot 40 and 41)

5

This command fails if:

• the first ENT command received is not the one related to AID Assignment to the Main Shelf

Provision Equipment 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

388 Issue 4

Page 389: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• the first ENT command received is the one related to AID Assignment to the Main Shelf, butat 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, andthe assigned AID is different from <SHELF-1-1>

• a Main Shelf is already provisioned and a new ENT-EQPT command has been received withthe PARAMETER SHELFROLE set to MAIN <SHELF-1-1>

• the command is input for an AID which is not a Shelf with Provisioned Type = UNVRSL320 orUNVRSL160 or UNVRSL160C and at least one PARAMETER among SHELFNUM orSHELFROLE is set

• the command is input for a Shelf AID which has a Provisioned Type = UNVRSL320 orUNVRSL160 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. Possiblevalues: refer to B.3 “AIDs” (p. 692) or to “Command details” (p. 107).

• PROVISIONEDTYPE = Nokia mnemonic stored in the Remote Inventory EPROM for thegiven equipment.

For possible values please refer to B.4 “Provisioned Types” (p. 693).

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Note: When the ENT-EQPT command is entered with AID 10GSO/ CWLA/CMDX/PP10AD/PP10GE/PP1GE/PPUGW/PP1GEX20/PP10GEX2 the relatedPROVISIONEDTYPE should be specified

9

Is the board provided with an XFP or SFP module?

If yes, go to Step 10.

If no, go to Step 12.

1850 TSS-320/TSS-320H/TSS-160 Provision Equipment

Release 5.1 (ETSI)September 2017Issue 4 3898DG09603CAAATQZZA

Page 390: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

10

XFP/SFP module provision

Verify the XFP/SFP module on the board (ref. to Table 59, “Supported SFP/XFP OpticsModules - Client Side” (p. 692)).

11

Enter ENT-EQPT::AID::::PROVISIONEDTYPE=[,AINSMODE=][,SHELFNUM=][,SHELFROLE=][,APTMODE=][,VOAMODE=][,APSD1=][,APSD2=][,OPWRL1=][,

OPWRL2=][,VOA=][,EOLSPAN=][,N1=][,PCH1=][,IT=][,LAMBDASET=][,ALMPROF=

][,CLNTSEL=][,OPWRLOT2=][,SSBIT=]:[PST];

where:

• AID=Module Access Identifier previously referred in Step 8

• PROVISIONEDTYPE= Nokia mnemonic stored in the Remote Inventory EPROM for thegiven 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 onthe Client side Port of a Transponder Card or mounted on any Port of the 10XANY card withPROVISIONEDTYPE equal to ANYFC.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

12

STOP. This procedure is complete.

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 RADIUSserver.The failure is declared after the timeout is elapsed. The supported value range for timeoutis 1 to 1000. The default value is 5.

• Retries: This is the number of attempts that the NE will try to contact the specified RADIUSserver that has failed to respond during the previous request(s). If there is no response from theserver after the specified tries then the NE will try to contact the second RADIUS server if one isprovisioned (status: “Enabled”). The retries range is 0 to 100 with default value 3.

Radius server authentication ordering 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

390 Issue 4

Page 391: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 theuserID 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 NEuserID.

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 duringaccess 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 administrativeprivilege.

6.68.3 Before you begin

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.

2

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).

1850 TSS-320/TSS-320H/TSS-160 Radius server authentication ordering

Release 5.1 (ETSI)September 2017Issue 4 3918DG09603CAAATQZZA

Page 392: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4

Configure RADIUS server as first server on NE.For details, refer to 6.29 “Administer Radiusserver” (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 serverdatabase

6

Configure authentication order as LOCAL, to perform this operation enter:

SET-RADIUS-AUTH:::::LOCAL:[RETRIES=][,TIMEOUT=];

For parameter descriptions of TL1 commands used in this procedure, refer to the1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1Command 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) toprovision the same user on the local DB. In case a user is configured both locally and in theRADIUS server and the passwords are different, when the user tries to authenticate usingRADIUS password the access is denied, because the check is firstly performed in the local DBand 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 Radiusserver” (p. 229).

11

Set the user's (USER01) and the RADIUS passwords.

Radius server authentication ordering 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

392 Issue 4

Page 393: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 serverdatabase

12

Configure authentication order as RADIUS, to perform this operation enter:

SET-RADIUS-AUTH:::::RADIUS:[RETRIES=][,TIMEOUT=];

For parameter descriptions of TL1 commands used in this procedure, refer to the1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1Command 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 toservice. Them was been previously provisioned as described in 6.67 “Provision Equipment”(p. 385).

6.69.2 Prerequisites

The user should verify by means of the RTRV-EQPT command the devices presence and state intothe equipment before removing/restoring it.

6.69.3 General

RMV-EQPT causes the specified equipment to be placed in the out-of-service management servicestate. The command can be applied to the following equipment:

• EC320

• MT320

• MT160

• PSF320 and POW320

1850 TSS-320/TSS-320H/TSS-160 Remove/Restore Equipment

Release 5.1 (ETSI)September 2017Issue 4 3938DG09603CAAATQZZA

Page 394: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• FAN

• Lower Order Adaptation Card 10G

• 10GSO (STM-64) card

• 2.5G (STM-16) module

• 8 Port (STM-1)/(STM-4) card

• G.709 OTU 10GB Card (OT2TDM)

• ANYFC 10GB 10 x FC-2/FC-4

• 10XANY 10GB 10xGBE Card

• MultiService Adaptation Card (Packet Module 10G)

• Packet Module 10x1GbEthernet (Packet Module 10G)

• Packet Module 1x10GbEthernet (Packet Module 10G)

• Optical Pre-Amplifer 10G

• Optical Booster 10G Line

• Optical Filter and Attenuator (LOFA)

• DWDM Optical Transponder with Colored XFPs

• CWDM Optical Transponder (2.5G) without Optical Protection

• CWDM Optical Transponder (2.5G) with Optical Protection

• CWDM OADM 4ch w/o OSC coupler

• CWDM OADM 4ch w OSC coupler

• CWDM OADM 2ch w/o OSC coupler

• CWDM OADM 2ch w OSC coupler

• CWDM OADM 1ch w/o OSC coupler

• CWDM OADM 1ch w OSC coupler

• CWDM Mux/Demux 8ch w/o OSC coupler

• CWDM Mux/Demux 8ch with OSC coupler

• CWDM Mux/Demux 2ch with OSC coupler

• CWDM Mux/Demux 1ch with OSC coupler

• DWDM Mux/Demux 8 channels L1 band without S-band input/output

• XFP on 10GSO modules

• SFP on 2G5SO modules

• SFP on 8 port (STM-1)/(STM-4) modules (8XSO)

• SFP on 10XANY modules

Executing a RMV-EQPT command causes a primary state transition from IS or OOS-AU toOOS-MA or OOS-AUMA respectively. Secondary states associated with the equipment entity beforeand 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.

Remove/Restore Equipment 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

394 Issue 4

Page 395: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

A module which is NOTswitched to protection (regardless of whether the ports are provisioned on itor paths are cross connected) can be logically removed only with the MODE parameter set toFRCD

When the RMV-EQPT command is entered for an active module, only the MODE=FRCD isaccepted, and it is up to the operator to manually execute the switch to the other copy before orafter 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 beforeperforming a RMV-EQPT.

This command causes a clear message to be sent for any condition that has already beenautonomously reported. It prevents any subsequent conditions declared against the equipment frombeing autonomously reported but the conditions are still retrievable.

The RST-EQPT command causes the specified equipment to be placed in the IS or OOS-AUprimary state. Secondary states associated with the equipment entity before and after thecommand is executed depend upon events detected by the system.

This command allows any active condition declared against the equipment to be autonomouslyreported.

Neither intrusive diagnostics nor SW downloads are done during a restore operation.

A forced restoral is allowed setting MODE parameter to FRCD.

6.69.4 Procedure

1

Select action.

To remove equipment, go to Step 2.

To restore equipment, go to Step 9.

2

Remove Equipment

Enter RTRV-EQPT::AID; to view equipment service states.

where:

• AID=Equipment Access Identifier, identifies the equipment entity access identifier. Possiblevalues:− 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

1850 TSS-320/TSS-320H/TSS-160 Remove/Restore Equipment

Release 5.1 (ETSI)September 2017Issue 4 3958DG09603CAAATQZZA

Page 396: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

− 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

− PP1GE-{1-7}-{1-9}-{2-9,12-19} for Packet Module 10x1Gb

− PP10GE-{1-7}-{1-9}-{2-9,12-19} for Packet Module 1x10Gb

− 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 IS-NR or OOS-AU, go to Step 4.

If OOS-MA or OOS-AUMA, module is already removed from service. Go to Step 12.

4

Is 10GSO, 2G5SO, 8XSO, SFP, or XFP, to be removed?

If yes, go to Step 5.

If no, go to Step 7.

A forced removal may result in an interruption of traffic.

5

Go to Step 7.

6

Switch module to protection. Refer to 6.63 “Perform Module Protection Switch or Copy Switch”(p. 367).

Remove/Restore Equipment 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

396 Issue 4

Page 397: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

7

Enter RMV-EQPT::AID:::[MODE];

where:

• AID=Access Identifier of specified equipment as previously referred.

• MODE= NORM (Normal, the command is denied if the result of its execution is service-affecting) or FRCD (Forced, the command is completed even if the result of its execution isservice-affecting).

8

Go to Step 12.

9

Restore Equipment

Enter RTRV-EQPT::AID; to view equipment service states as previously referred.

10

What is PST of module to restore?

If OOS-MA or OOS-AUMA, go to Step 11.

If IS-NR or OOS-AU, module is already restored to service. Go to Step 12

11

Enter RST-EQPT::AID:::[MODE];

where:

• AID=Access Identifier of specified equipment as previously referred.

• MODE= NORM (Normal, the command is denied if the result of its execution is service-affecting) or FRCD (Forced, the command is completed even if the result of its execution isservice-affecting).

12

STOP. This procedure is complete.

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.

1850 TSS-320/TSS-320H/TSS-160 Report Performance Monitoring (PM) Data

Release 5.1 (ETSI)September 2017Issue 4 3978DG09603CAAATQZZA

Page 398: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.70.2 Prerequisites

None.

6.70.3 General

PM commands operate only on provisioned ports.

PM commands are used to monitor defect conditions, and can be used to track system efficiency.By tracking efficiency, users can recognize gradual deterioration of system performance.

RTRV-PM-x retrieves facility PM current and/or historical data 15-minute or 1-day PM data thatcorresponds to the facility PM data collection registers.

INIT-REG-x initializes the current 15-minute and current 1-day PM collection registers for themonitored parameters.

6.70.4 Procedure

1

Select action.

To retrieve PM data, go to Step 2.

To initialize PM data collection register, go to Step 5.

To initialize PM data collection register, go to Step 5.

To end this procedure, go to Step 7.

2

Retrieve PM Data

Enter RTRV-PM-x::AID:::[MONTYPE],[MONLEV],[LOCN],[DIRN],[TMPER],[MONDAT],[MONTM],[NUM15MIN],[NUM1DAY];

where:

• x= GBE10, GBE, ODU2, OTU2, MAU, STM1, STM4, STM16, STM64, VC4, VC44C,VC416C, VC464C, LOVC12, LOVC3.

• AID=Access Identifier, identifies the entity access identifier. Only valid sdhFacility / AIDcombinations are allowed, all other shall be rejected.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Examine output for PM information, as detailed in the relevant command guide, refer to“Command details” (p. 107).

Report Performance Monitoring (PM) Data 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

398 Issue 4

Page 399: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

[

"<AID>,<AIDTYPE>:<MONTYPE>,<MONVAL>/<MONLEV>,<VLDTY>,<LOCN>,<DIRN>,

<TMPER>,<MONDAT>,<MONTM>,<ELTM>" cr lf]

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

4

Go to Step 1.

5

Initialize PM Data Collection Register

Enter INIT-REG-x::AID:::[MONTYPE],[MONVAL],[LOCN],[DIRN],[TMPER];

where:

• x= GBE10, GBE, ODU2, OTU2, MAU, STM1, STM4, STM16, STM64, VC4, VC44C,VC416C, VC464C, LOVC12, LOVC3.

• AID=Access Identifier, identifies the entity access identifier. Possible values: refer toA.2 “Access Identifiers” (p. 611) according to the facility.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Go to Step 1.

1850 TSS-320/TSS-320H/TSS-160 Report Performance Monitoring (PM) Data

Release 5.1 (ETSI)September 2017Issue 4 3998DG09603CAAATQZZA

Page 400: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

7

STOP. This procedure is complete.

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.

6.71.2 Prerequisites

None.

6.71.3 General

The site identifier appears in command response messages, and is used as the target identifierwhen addressing an NE through a TL1 gateway. In this procedure, enter parameter values only forindicated fields. Leave remaining fields blank for system defaults.

The RTRV-HDR command retrieves the system's output response (site) header. The outputresponse header consists of the Site Identifier (SID) and the current date and local time. A specialversion of this command, using the PC option, is available to assist in discovery of the TIDs ofRemote NEs connected to a Gateway NE via OSI over DCC. The PC option also returns the NEtype and software release number. If an NSAP address but not a TID is known for an NE, then theTID 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 TargetIdentifier (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 inthe relevant command guide, refer to “Command details” (p. 107).

Retrieve and Change Site Identifier 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

400 Issue 4

Page 401: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 syntaxrules as the TID value. That is, the SID value can be either up to 20 noncase-sensitivealphanumeric characters, including the special hyphen (-) character, or up to 20 charactersquoted string.

If it is a non quoted string, the hyphen (-) is the only special character allowed. The SID muststart with a letter and shall end with an alphanumeric character. Consecutive hyphens (-) shallnot be allowed. Number of hyphens shall be not greater than 4. If a lower-case character stringis entered for the SID, it is automatically converted to an uppercase character string forcomparison to any TID value entered in a command.

If it is a quoted string, any character is allowed, included any special character, and no caseconversion is applied.

1850 TSS-320/TSS-320H/TSS-160 Retrieve and Change Site Identifier

Release 5.1 (ETSI)September 2017Issue 4 4018DG09603CAAATQZZA

Page 402: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

On initial turnup, the NE shall automatically generate an unique SID, using the last 5hexadecimal 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 hardwaremodule) and stored in the NE's database during any cold restart of the NE, as long as the SIDis already set to PLEASE-SET-SID- xxxxx, or a default database is created.

5

STOP. This procedure is complete.

END OF STEPS

6.72 Retrieve Module Remote Inventory Information

6.72.1 Purpose

This procedure provides instructions to retrieve module remote inventory information.

6.72.2 Prerequisites

None

6.72.3 General

The RTRV-RI command retrieves the remote inventory information for any module physicallypresent in the system regardless the provisioning state.

If the specified board supports a downloadable firmware, the command will retrieve the firmwareversion 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 whichis plugged-in whether the equipment is provisioned or not. If the AID is unassigned, the AID in theoutput will be MDL-x-x-x[-x]. If the AID is assigned, the AID in the output will be the AID of the actualmodule 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. MDLis used to identify a generic non mandatory module (whether it is provisioned or not. ). TheInventory of all the NE is retrieved selecting AID=ALL. The Inventory of all the items pluggedinside a Shelf is retrieved selecting AID=SHELF-1-7-1-9 or AID=MDL-1-7-1-9. Possible values:

• ALL for all AID

• SHELF-{1-7}-{1-9} for the Shelf

• EC320-{1-7}-{1-9}-{1,20} for Equipment Controller Card TSS-320

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

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

402 Issue 4

Page 403: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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

• 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

• LOA10G-{1-7}-{1-9}-{21,22,24,33,35,36} for Lower Order Adaptation Card with EPS

• PRE-{1-7}-{1-9}-{2-9,12-19,21-36} for Preamplifier

• BOOST-{1-7}-{1-9}-{2-9,12-19,21-36} for Booster

• LOFA-{1-7}-{1-9}-{6-9,12-15} for Line Optical Filter and Attenuator

• DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} for DWDM Optical Transponder

• CWLA-{1-7}-{1-9}-{6-9,12-15} for CWDM Optical Transponder

• CADM-{1-7}-{1-9}-{6,7,8,9,12,13,14,15} for CWDM OADM

• CMDX-{1-7}-{1-9}-{6-9,12-15} for CWDM MUX/DEMUX

• OMDX8-{1-7}-{1-9}-{6-9,12-15} for DWDM MUX/DEMUX 8 channels

• PP10AD-{1-7}-{1-9}-{2-9,12-19} for Adaptation Card Packet Modules 10G

• PP1GE-{1-7}-{1-9}-{2-9,12-19} for Packet Module 10x1Gb

• PP10GE-{1-7}-{1-9}-{2-9,12-19} for Packet Module 1x10Gb

• 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

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

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

Release 5.1 (ETSI)September 2017Issue 4 4038DG09603CAAATQZZA

Page 404: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

"<AID>::[COMPANY=/"<value>/"][,MNEMONIC=/"<value>/"][,CLEI=/"<value>

/"][,PARTNUM=/"<value>/"][,SWPARTNUM=/"<value>/"][,FACTORY=/"<value>

/"][,SERIAL=/"<value>/"][,DATE=<value>][,EXTRADATA=/"<value>/"]"

cr lf

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

3

STOP. This procedure is complete.

END OF STEPS

6.73 Retrieve Section Trace

6.73.1 Purpose

This procedure provides instructions to retrieve the contents of the Section Trace message.

6.73.2 Prerequisites

None

6.73.3 General

The RTRV-SECTRC retrieves the contents of the Regenerator SectionTrace using the 16-byteframe format as defined in G.707. This command may be used to retrieve the "incoming" accepted

Retrieve Section Trace 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

404 Issue 4

Page 405: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Regenerator Section Trace, the expected Regenerator Section Trace as used for the dTIM (TraceIdentifier Mismatch) supervision and the "outgoing" transmitted Regenerator Section Trace that isinserted into the Regenerator Section overhead on the outgoing signal. The expected andtransmitted Regenerator Section Trace is provisioned via the ED facilities command. If noTRACEMSG 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 supportsprovisioning of normal TL1 section trace messages, but it is possible to retrieve incoming messagesin hex format that may be generated by other NEs.

6.73.4 Procedure

1

Enter RTRV-SECTRC::AID:::[INCMSGFMT];

where:

• AID=Access identifier of the optical facility. Possible values:− Client port on a DWLA10X module - OTU2, STM-64, 10GE

− STM1

− STM4

− STM16 on a 2G5SO or 10xANY

− STM64

− Client port on a DWLA10X module - OTU2, STM-64, 10GE , 10GFC

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

2

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

1850 TSS-320/TSS-320H/TSS-160 Retrieve Section Trace

Release 5.1 (ETSI)September 2017Issue 4 4058DG09603CAAATQZZA

Page 406: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

STOP. This procedure is complete.

END OF STEPS

6.74 Retrieve System Configuration

6.74.1 Purpose

This procedure provides the instructions to retrieve general system level and global systemconfiguration information.

6.74.2 Prerequisites

None.

Retrieve System Configuration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

406 Issue 4

Page 407: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.74.3 General

The procedure retrieves general system level configuration information that consists of the followingparameters:

• System type

• Software release identifier

• Software release date

• Matrix size

• System restart status

6.74.4 Procedure

1

Enter RTRV-PRMTR-NE; to retrieve system configuration parameters.

2

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

1850 TSS-320/TSS-320H/TSS-160 Retrieve System Configuration

Release 5.1 (ETSI)September 2017Issue 4 4078DG09603CAAATQZZA

Page 408: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

STOP. This procedure is complete.

END OF STEPS

Retrieve System Configuration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

408 Issue 4

Page 409: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.75 Retrieve TL1 Command Syntax

6.75.1 Purpose

This procedure provides the instructions to retrieve the syntax of a TL1 command, including adescription of the command parameters.

6.75.2 Prerequisites

None.

6.75.3 General

The RTRV-TL1-SYNTAX command is used to retrieve the syntax of a TL1 command, including adescription 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 “Commanddetails” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Retrieve TL1 Command Syntax

Release 5.1 (ETSI)September 2017Issue 4 4098DG09603CAAATQZZA

Page 410: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

STOP. This procedure is complete.

END OF STEPS

6.76 Retrieve User Session Information

6.76.1 Purpose

This procedure provides instructions to retrieve user session information.

6.76.2 Prerequisites

None.

Retrieve User Session Information 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

410 Issue 4

Page 411: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.76.3 General

The procedure retrieves the user profile entry for the specified user. It retrieves both the static userprovisioning 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 providedname. 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 isexpired and can no longer be changed, and the time remaining for password expiration. Refer to6.48 “Disable/Enable User Account” (p. 314).

The system administrator or Nokia account user can retrieve any or all user profile entries. Anyother 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/orauthenticated (logged on) users. The address information (ADDR parameter) consists of either theuser TCP/IP address, if the user is connected by TCP/IP, or the string "DCC", if the user isconnected by means of DCC.

6.76.4 Procedure

1

Select action.

To retrieve user profile information for other user, go to Step 2.

To retrieve own user profile information, go to Step 5.

2

Retrieve user profile information

Enter RTRV-USER-SECU::[UID];

where: UID=User Identifier, specifies a unique user ID. Possible values for UID are: 5 to 12,case-sensitive alphanumeric characters where the first character must always be an alphabeticcharacter. The following special characters are also accepted as valid characters and will bepart of the UID: % (percent sign), + (plus sign), # (pound sign), and _ (under score) or ALL forall of the users defined for the system.

3

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

1850 TSS-320/TSS-320H/TSS-160 Retrieve User Session Information

Release 5.1 (ETSI)September 2017Issue 4 4118DG09603CAAATQZZA

Page 412: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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

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 alphabeticcharacter. The following special characters are also accepted as valid characters and will bepart of the UID: % (percent sign), + (plus sign), # (pound sign), and _ (under score).

6

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

Retrieve User Session Information 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

412 Issue 4

Page 413: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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]

;

7

Enter RTRV-STATUS;

8

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

1850 TSS-320/TSS-320H/TSS-160 Retrieve User Session Information

Release 5.1 (ETSI)September 2017Issue 4 4138DG09603CAAATQZZA

Page 414: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

(

":<SESSION>,[<UID>]:ADDR=<value>[,LAST=<value>]" cr lf)+

[

/*

<Command

Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

9

STOP. This procedure is complete.

END OF STEPS

6.77 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.

6.77.2 Prerequisites

None

6.77.3 General

The NE has one provisionable IP address for all external IP communications via ethernet, localLAN, and DCC.

Retrieve/Provision IP Address of NE 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

414 Issue 4

Page 415: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The ED-IP-ADDR command sets the TCP/IP stack parameters and controls whether the TCP/IPstack is enabled/disabled on the NE. Once enabled, TL1 commands may be sent to the NE usingan 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.

To end this procedure, go to Step 9.

2

Retrieve IP Address of NE

Enter RTRV-IP-ADDR;

3

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

1850 TSS-320/TSS-320H/TSS-160 Retrieve/Provision IP Address of NE

Release 5.1 (ETSI)September 2017Issue 4 4158DG09603CAAATQZZA

Page 416: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 notallowed. Neither the network nor the host portion of the address when viewed in binaryformat 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, inbinary representation, must contain a contiguous string of 1s (the network portion) and acontiguous string of 0s (the host portion). Possible values: {128-255} - {0-255} - {0-255} - {0-255}.

6

Enter RTRV-IP-ADDR;

Retrieve/Provision IP Address of NE 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

416 Issue 4

Page 417: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

7

Observe output and verify change was made.

8

Go to Step 1.

9

STOP. This procedure is complete.

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 toprovision 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 thepassword)

• 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 touser 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, beforethat 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 bedisabled on this port) and Q can be disabled via ED-LAN command.

1850 TSS-320/TSS-320H/TSS-160 Security Defaults Administration

Release 5.1 (ETSI)September 2017Issue 4 4178DG09603CAAATQZZA

Page 418: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Most of the above described parameters (PAGE, PCNN, PCND, POINT and UOUT) can also beprovisioned 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 consideredNULL and the system value takes precedence. This way you can change the global value and allusers are affected unless they have had their parameters specifically set.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

6.78.3 Procedure

1

Login in to NE with an authorized user (i.e. SEC Privileged User, for ex.: USER01).

2

To retrieve provisioned values for the system-wide user security information, enter:

RTRV-DFLT-SECU:[TID]::[CTAG];

Result: Command is completed and retrieval shows system wide security information,

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=];

For parameter descriptions of TL1 commands used in this procedure, refer to the1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1Command Guide.

4

Observe the changes entering the retrieve command.

Security Defaults Administration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

418 Issue 4

Page 419: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

5

To retrieve the parameters in use for the security log enter:

RTRV-ATTR-SECULOG:[TID]::[CTAG];

Result: The list of events that, upon their occurrence, are included in the securitylog (i.e.,events that are specified for logging, if they occur).

6

To set the parameters in use for the security log enter:

SET-ATTR-SECULOG::::::[LOGEVENT=][,UPSLG=][,WARN=];

Other parameters are optional. If a value is not entered for these parameters, the system willuse the default value. Refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide for details on parameter values.

END OF STEPS

6.79 Set Performance Monitoring (PM) Mode

6.79.1 Purpose

This procedure provides the instructions to set or change Performance Monitoring (PM) mode forspecified GBE10, GBE, ODU2, OTU2, MAU, SDH FACILITY ports. The PM mode controls the datacollection for specific types of PM data (section, line, path, or all applicable locations).

6.79.2 Prerequisites

None.

6.79.3 General

PM commands operate only on provisioned ports.

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 dataare 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 toretrieve the Performance Monitoring data collection for the GBE10, GBE, ODU2, OTU2, MAU,SDH facilities.

1850 TSS-320/TSS-320H/TSS-160 Set Performance Monitoring (PM) Mode

Release 5.1 (ETSI)September 2017Issue 4 4198DG09603CAAATQZZA

Page 420: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

2

Examine output to determine current PM mode, as referred in 6.70 “Report PerformanceMonitoring (PM) Data” (p. 397) procedure.

3

Enter SET-PMMODE-x::AID:::LOCN,MODETYPE,[PMSTATE],[DIRN]: [TMPER=];

where:

• x= GBE10, GBE, ODU2, OTU2, MAU, STM1, STM4, STM16, STM64, VC4, VC44C,VC416C, VC464C, LOVC12, LOVC3.

• AID=Access Identifier, identifies the entity access identifier. Possible values:− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module

- OTU2,, STM-64, 10GE, 10GFC

− GBE-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10 } for GBE Port

− MAU-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1-10} for MAU port on a 10xAny module

− OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{C1, L1}-1 for ODU2 facility in an OTU2ona DWLA10X module

− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port,OT2TDM orDWLA10X module

− STM1-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for an STM1

− STM4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for an STM4

− STM16-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4, 5, 7} for an STM16 on a 2G5SO or 10xANY

− STM64-{1-7}-{1-9}-{2-9,12-19,21-36}-1 for an STM64

− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module- OTU2, STM-64, 10GE)

− STM1AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-1 for an AU4 embedded within an STM1

− STM64AU4-{1-7}-{1-9}-{2-9,12-19,21-3 6}-1-{1-64} for an AU4 embedded within anSTM64

− STM16AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1-16} for an AU4 in an STM16 on a2G5SO 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 10xAnymodule

− VCGVC4-{1-7}-{1-9}-{2-9,12-19}-{1-64}-{1-64} for a VC4 within a logical VCG on aMultiservice 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 anSTM64

− STM16AU44C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1,5,9,13} for an AU4-4c inanSTM16 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 anSTM4

Set Performance Monitoring (PM) Mode 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

420 Issue 4

Page 421: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

− STM64AU416C-{1-7}-{1-9}-{2-9,12-19,21-36}-1-{1,17,33,49} for an AU4-16c embeddedwithin 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 ona 2G5PSO or 10xANY

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

− VCGLOVC12-{1-7}-{1-9}-{2-9,12-19}-{1-124}-{1-63} for a LO VC12 within a logical VCGon 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 withina Modifiable VC4

− VCGLOVC3-{1-7}-{1-9}-{2-9,12-19}-{1-24}-{1-24} for a LO VC3 within a logical VCG on aMultiservice Packet Card

− MVC4TU3-{1-7}-{1-9}-{21,22,35,36}-{1-64}-{1-3} for a TU3 embedded within a ModifiableVC4

− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module- OTU2,, STM-64, 10GE , 10GFC

• 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.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

4

STOP. This procedure is complete.

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 forDWDM, ETSI SDH, Packet profile types.

6.80.2 Prerequisites

None.

1850 TSS-320/TSS-320H/TSS-160 Set Performance Monitoring (PM) Threshold Levels

Release 5.1 (ETSI)September 2017Issue 4 4218DG09603CAAATQZZA

Page 422: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.80.3 General

PM commands operate only on provisioned ports.

PM commands are used to monitor signal overhead that is used to track system efficiency. Bytracking 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 hardwareresources of more than one profile. Depending of the created profile types and their relation to thesupporting 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 createdfor 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 typesin 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 clearthreshold may be supported.

The ED-TH-PROF command modifies values of thresholds for the specified monitored types in aspecified 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. Onlyfor 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 foreach montype specified.

6.80.4 Procedure

1

TCA profile instance information

Enter RTRV-TH-PROF::[TCA-AID]:::[PFTYPE][:USERLABEL=]; to retrieve currentthreshold levels for the facility.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

2

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

Set Performance Monitoring (PM) Threshold Levels 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

422 Issue 4

Page 423: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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)

1850 TSS-320/TSS-320H/TSS-160 Set Performance Monitoring (PM) Threshold Levels

Release 5.1 (ETSI)September 2017Issue 4 4238DG09603CAAATQZZA

Page 424: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

− {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=][,THLEV=][,USERLABEL=][,DIRN=][,THLEVCL=];

where:

• TCA-AID= TCA-AID input parameter should be specified only for changing the USERLABEL,otherwise it should not be entered and it has not any impact on command behavior

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

TCA profile instance deletion

DLT-TH-PROF::[TCA-AID]::::[USERLABEL=];

where:

TCA-AID = TCA profile ID which is being deleted. The TCA ID consists of leading string THPfollowed 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 beenentered.

7

STOP. This procedure is complete.

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.

Slave TOD Card Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

424 Issue 4

Page 425: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Running BMCA, Slave is able to establish as well as all concurring Masters, which one will be theActive Master inside a clock domain; it will then answer to this one, without performing any localselection.

In case of PTP over UDP, each Slave port is able to communicate with Unicast signalling only witha single Master clock.

Redundancy is obtained, at system level, configuring two slave ports (i.e. TOD Slave Card), eachone belonging to a different clock domain.

The selection among different PTP clock sources (i.e. Master clock) is performed by A-BMCAmechanism.

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

1

Select action

• Slave TOD Card Creation, go to Step 2

• Phase Synchronization reference configuration, go to Step 9

• Slave TOD Card Deletion, go to Step 12.

2

Slave TOD Card Creation

Enter:

ENT-EQPT::AID::::PROVISIONEDTYPE=PP1588, CKMODE=SLAVE;

where:

• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card

• CKMODE=SLAVE means that the PP1588 card is configured in Slave Clock Configuration.

Result:

The following resources are enabled:

• 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 forinternal Phase Distributor.

3

Select action:

1850 TSS-320/TSS-320H/TSS-160 Slave TOD Card Management

Release 5.1 (ETSI)September 2017Issue 4 4258DG09603CAAATQZZA

Page 426: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 beprovisioned:

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 asinput (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 forsynchronization. The delay is due to the lenght of the cable on the link. The lenghtdetermines a propagation delay equal to D [ns], where D is the value to be provisioned. Theparameter applies to the receiver; normally positive values shall be provisioned; but negativevalues can be provisioned as well for compensating excessive dalys provisioned at the oterside transmitter. The unit of measure is nanosecond.

Note: In addition PPS-IN can be selected as input for CRU and for internal PhaseDistributor.

5

Enter:

RTRV-PPSIN::[AID];

The RTRV-PPSIN command retrieves the provisioning and state information of one or moreports, 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 ofparsable output data, in ascending order, listing the possible timing input ports used by thesystem.

6

For PPS-OUT the facility PPSOUT-r-s-b-1 is created and the following parameters can beprovisioned

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}.

Slave TOD Card Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

426 Issue 4

Page 427: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Sync message byte to be transmitted, determines if the transmitted byte will have the "DUS"message or will have the actual traceability of the signal.

• TOD= Time Of Day, determines if the information about Time Of Day shall be expected asinput (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 forsynchronization. The delay is due to the lenght of the cable on the link. The lenghtdetermines a propagation delay equal to D [ns], where D is the value to be provisioned. Theparameter applies to the receiver; normally positive values shall be provisioned; but negativevalues can be provisioned as well for compensating excessive dalys provisioned at the oterside transmitter. The unit of measure is nanosecond.

Note: PPS-OUT is automatically locked to internal T0 and to the internal PhaseDistributor.

7

Enter:

RTRV-PPSOUT::[AID]:;

To retrieve the provisioning and state information of one or more ports, in the 1588v2application, dedicated to the transmission of the PPS signal.

Result: The successful response for a RTRV-PPSOUT command contains one or more linesof parsable output data, in ascending order, listing the possible timing output ports used bythe 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 morelines of parsable output data, in ascending order (from lowest specified PTPSLAVE AID tothe largest specified PTPSLAVE AID), for each PTPSLAVE AID specified.

9

The Phase configuration applies either to input and output direction.

PTPSlave port and PPS Input port can be assigned to phase reference for the selection ofsystem phase/TOD reference of all PTPMaster ports and PPSoutput ports.

10

Enter:

1850 TSS-320/TSS-320H/TSS-160 Slave TOD Card Management

Release 5.1 (ETSI)September 2017Issue 4 4278DG09603CAAATQZZA

Page 428: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 portconnected 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 SystemPhase)

• SYNCMSG = SYNCMSG, determines if the timing reference selection for system phase isusing 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 bypriorities as second criteria.

• ASSPORTAID = ASSPORTAID specifies whether the phase reference is assigned to a portand if assigned it specifies the AID of the port. The following port types can be used forestablishing a connection towards a timing reference: PPS Input assigned to a phasereference

Note: The user is able to select the AID of the phase entity to be modified for the SyncMessaging (SYNMSG) management , specifying if the phase reference selection forsystem phase is using sync messaging (SSM Qualities) or not. (Y/N)

11

To configure PTP clock and ports refer to the the CLI command guide.

Note: After the proper configuration of the 1588 port and parameters it is needed toconfigure an ELAN service in order to be able to connect the 1588 port with the ‘bridge’function needed to forward / receive packets to / from the network.

12

Slave TOD Card deletion

Note: The steps below should be done using the SNMP or CLI commands.

First the user should:

• 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

Slave TOD Card Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

428 Issue 4

Page 429: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

13

The ETS Cross-connection should be deactivated and deleted, refer to the the CLI commandguide.

14

Management Operator Disabling of PTP protocol over PTP logical Master port via setting ofieee1588PtpPortDSAdminStatus to Disabled value. See CLI Command Guide.

15

If PPSIN has been configured as input for CRU (T0 and/or T4) or for internal Phase Distributor,it has to be de-provisioned.

16

The PTP logical slave port must be disabled at SNMP side. Please refer to the CLI commandguide.

17

The TOD card shall be logically removed.

Enter:

RMV-EQPT::AID;

or

ED-EQPT::AID:OOS;

where:

• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card

Note: TOD Card logical removal is mandatory also for avoiding traffic hits upon NGI linksof otherCollector cards eventually present in the shelf.

18

Enter:

DLT-EQPT::AID;

where:

• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card

Result: The command causes the Deactivation/Deletion of PTP Master logical port (bothSNMP and TL1 side), of PPSIN and PPSOUT ports.

END OF STEPS

1850 TSS-320/TSS-320H/TSS-160 Slave TOD Card Management

Release 5.1 (ETSI)September 2017Issue 4 4298DG09603CAAATQZZA

Page 430: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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.

6.82.2 Prerequisites

None.

6.82.3 General

The procedure retrieves the system's output response (site) header. The output response headerconsists 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 couldresult 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 detailedin the relevant command guide, refer to “Command details” (p. 107).

Set System Date and Time 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

430 Issue 4

Page 431: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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

Is it necessary to change date and time?

If yes, go to Step 5.

If no, go to Step 7.

5

Change System Date and Time

Enter ED-DAT:::::DATE,TIME;

where:

• DATE=identifies the new system date in the format of <YY>-<MM>-<DD>.

• TIME=identifies the new system time in the format of <HH>-<MM>-<SS>. The entered valueshould be the actual desired local time to be displayed by the NE, not modified by any offset.

6

Go to Step 2 in order to check the changes.

7

STOP. This procedure is complete.

END OF STEPS

1850 TSS-320/TSS-320H/TSS-160 Set System Date and Time

Release 5.1 (ETSI)September 2017Issue 4 4318DG09603CAAATQZZA

Page 432: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 usersecurity parameters related to the password aging (PAGE, PCNN, PCND, POINT), the minimuminterval between consecutive failed login attempts (MININTVL), the maximum number of failed loginattempts (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 theirpassword (MAXSESSION).

6.83.2 Prerequisites

None.

6.83.3 General

Most of the described parameters (PAGE, PCNN, PCND, POINT and UOUT) can also beprovisioned on a user basis, by the commands ENT-USER-SECU and ED-USER-SECU. So thefollowing rule shall be applied for the provisioning of these parameters: unless a parameter isspecified when entering or editing a user, the value shall be considered <null> and the systemvalue takes precedence. This way you can change the global value and all users are affectedunless they have had their parameters specifically set.

Note: In the rule above must be considered that, however, the changes to system values shalltake effect immediately only on currently not logged on users, while for logged on users theyshall take effect only after logout. Anyway, the modified system values shall be retrievable byRTRV-DFLT-SECU.

6.83.4 Procedure

1

Select action.

To retrieve default security parameters, go to Step 2.

To set default security parameters, go to Step 5.

2

Retrieve Default Security Parameters

Enter RTRV-DFLT-SECU;

3

Observe output, as detailed in the relevant command guide, refer to “Command details”(p. 107).

Set System-Wide User Security Parameters 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

432 Issue 4

Page 433: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

":/"DEFAULTS

/":PAGE=<value>,PCND=<value>,PCNN=<value>,POINT=<value>,KAMINTVL=

<value>,MAXSESSION=<value>,MININTVL=<value>,MXINV=<value>,TMOUT=

<value>,UOUT=<value>" cr lf

[

/*

<Command

Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

4

Is it necessary to change parameters?

If yes, go to Step 5.

If no, go to Step 6.

5

Set Default Security Parameters

Enter SET-ATTR-SECUDFLT::::::[PAGE=][,PCND=][,PCNN=][,POINT=][,MININTVL=][,MXINV=][,TMOUT=][,UOUT=][,KAMINTVL=] [,MAXSESSION=];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Set System-Wide User Security Parameters

Release 5.1 (ETSI)September 2017Issue 4 4338DG09603CAAATQZZA

Page 434: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6

STOP. This procedure is complete.

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.

6.84.2 Prerequisites

STMn facilities must be provisioned. Refer to 6.31 “ Administer STMn Facility” (p. 235).

STMn facilities must be provisioned as a facility protection group (FFP). Refer to 6.32 “AdministerSTM-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 protectfacility when the command is issued, traffic switches to the working facility and remains thereuntil the lockout is released. For this switch command, the protect AID must be specified. ALockout overrides a Forced Switch and a Manual Switch.

• Forced Switch (FRCD) forces traffic to either the working facility or the protect facility. Specifyinga working AID forces the traffic to the protect facility, and specifying a protect AID forces traffic tothe 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. Specifyinga working AID moves the traffic to the protect facility, and specifying a protect AID moves trafficto 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-SPRINGprotection group. This command performs the ring switch from the working channels to theprotection channels for the span between the node at which this command is initiated and theadjacent node. This switch occurs regardless of the state of the protection channels, unless thering 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 thering protection channels, this command causes working traffic to be switched back to theworking 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

Switch STMn Line to Protection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

434 Issue 4

Page 435: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

protection group. This command performs the ring switch from working channels to theprotection channels for the span between the node at which this command is initiated and theadjacent node.

• LOW-R (MS-SPRING) Lockout of working channels - ring switch. This command shall preventthe working channels over the addressed span from accessing the protection channels for a ringswitch by disabling the node's capability to request a ring switch for the working channels on theaddressed span. If any working channel is already on protection, the ring switch is droppedregardless 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 spanscommand applies only to the protection channel and not the working channels. This commandhas no impact on the use of the protection channels for any other span (e.g., the node can gointo 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 ifautomatic 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. Ithas no significance when the automatic learning protocol is not enabled.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

6.84.4

1

Select action.

To retrieve information on STMn facilities and FFP, go to Step 2.

To initiate STMn switch to protection, go to Step 7.

To release STMn switch to protection, go to Step 9.

To end this procedure, go to Step 11.

2

Retrieve Information on STMn Facilities and FFP

Enter RTRV-STMn::[AID];

where:

STMn=Optical facility type (STM1, STM4, STM16, or STM64).

AID=STMn Access Identifier

3

Examine output. Note states and other pertinent information.

4

Enter RTRV-FFP-STMn::[AID];

where:

STMn=Optical facility type STM1, STM4, STM16, or STM64).

1850 TSS-320/TSS-320H/TSS-160 Switch STMn Line to Protection

Release 5.1 (ETSI)September 2017Issue 4 4358DG09603CAAATQZZA

Page 436: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

AID=STMn Facility Protection Group Access Identifier

5

Examine output. The output response displays FFP information about the specified AID. Noinformation displays for ports that are not in an FFP group.

6

Go to Step 1.

7

Perform STMn Protection Switch

Enter OPR-PROTNSW-STMn::AID:::SWTCHCMD;

where:

STMn=Optical facility type (STM1, STM4, STM16, or STM64).

AID=STMn Access Identifier

SWTCHCMD={FRCD, LOCKOUT, MAN} for Linear protections

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-SPRINGprotections

8

Go to Step 1.

9

Release STMn Protection Switch

Enter RLS-PROTNSW-STMn::AID;

where:

STMn=Optical facility type (STM1, STM4, STM16, or STM64).

AID=STMn Access Identifier

10

Go to Step 1.

11

STOP. This procedure is complete.

END OF STEPS

Switch STMn Line to Protection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

436 Issue 4

Page 437: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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.

6.85.2 Prerequisites

VC-n path facilities must be provisioned.

STM-n facilities that support the VC-n must be provisioned for SNCP/UPSR.

6.85.3 General

OPR-PROTNSW-<rate> will be used for initiating of switch commands for SNCP or UPSR.. Thecommand initiates external switch requests for path protected cross-connections of type2WAYSNCP and 1WAYSNCP. The command requests the system to switch the path selector to theprotected or protecting path of the SNCP. User switch requests initiated with this command remainactive until they are released via the RLS-PROTNSW-<rate> command or overridden by a higherpriority protection switch request.

When initiating a protection switch using OPR-PROTNSW-<rate>, three options for the switchcommand (SWTCHCMD) parameter are available: LOCKOUT, FRCD, and MAN. When thecommand executes, the path selector switches to the specified destination facility (WKG -FROMPED/PREFFERED or PROTN - FROMPING/ALTERNATE). If the new external request ishigher priority than the current request for the group and in the event that the switch/selector isalready at the destination position, then no switch actually occurs, but the switch state andconditions are updated to match the new current request.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

6.85.4

1

Select action.

To retrieve information on VC-n facilities, go to Step 2.

To retrieve VC-n cross-connections, go to Step 5.

To perform VC-n switch to protection, go to Step 8.

To release VC-n switch to protection, go to Step 10

To end this procedure, go to Step 12.

2

Retrieve Information on VC-n Facilities

Enter RTRV-VCn::[AID];

where:

VCn/STSn=Facility type{VC4, VC44C, VC416C, VC464C, LOVC12, LOVC3)

1850 TSS-320/TSS-320H/TSS-160 Switch VCn Line to Protection

Release 5.1 (ETSI)September 2017Issue 4 4378DG09603CAAATQZZA

Page 438: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

Switch VCn Line to Protection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

438 Issue 4

Page 439: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

11

Go to Step 1.

12

STOP. This procedure is complete.

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 theASAPSECU assignment for the AID SECU, which supports the INTRUSION alarm.

When the ASAPSECU assignment is changed, the NE recalculates the INTRUSION severityaccording to the new assigned ASAPSECU contents.

If the same userID tries unsuccessfully (wrong password) to connect to the same NE for aconfigurable 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 ofinvalid 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 TL1autonomous messages shall provide this functionality. See Table SECU-2 for all supportedsecurity conditions).

The RTRV-ALM-SECU command retrieves the current status of any security alarmed standingcondition. 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 ofparsable output data for each SECU-UID, with CONDDESCR indicating the UID, and associatedremote port address, for which the INTRUSION has been detected.

An INTRUSION alarm is cleared when the UID - for which INTRUSION has been arised - is deletedor reallowed. The UID is deleted, via DLT-USER-SECU, when the secu admin considered theINTRUSION a real attack, while is re-allowed, via ALW-USER-SECU, when the secu adminconsidered the INTRUSION a simple mistake by a valid UID.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

1850 TSS-320/TSS-320H/TSS-160 System Access Control (intrusion alarm)

Release 5.1 (ETSI)September 2017Issue 4 4398DG09603CAAATQZZA

Page 440: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 uponoccurrence of the event identified by the CONDTYPE. CL Cleared Alarm CR Critical alarmMJ 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 theINTRUSION 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 remoteport address, for which the INTRUSION has been detected.

6

To clear INTRUSION alarm for an UID:

• delete UID (secu admin performs this operation when he considers the INTRUSION a realattack), go to Step 7

• re-allow UID (secu admin performs this operation when he considers the INTRUSION asimple mistake by a valid UID), go to Step 8

7

Enter:

DLT-USER-SECU::UID;

where.

System Access Control (intrusion alarm) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

440 Issue 4

Page 441: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

UID = User Identifier, specifies a unique user ID.

Result: The NE clears the INTRUSION alarm for that UID.

8

Enter:

ALW-USER-SECU:::::UID;

where.

UID = User Identifier, specifies a unique user ID.

Result: The NE clears the INTRUSION alarm for that UID.

END OF STEPS

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 ableto:

• 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 loggedwith DEBUG,CLI and ZIC sessions),

• Inhibit and allow users,

• Set system wide user security attributes and retrieve the security information aboutauthenticated and unauthenticated session.

1850 TSS-320/TSS-320H/TSS-160 Users with Security Administrator Privileges Overview

Release 5.1 (ETSI)September 2017Issue 4 4418DG09603CAAATQZZA

Page 442: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• Set command privilege partitioning.

A normal user (i.e., a user without security administration privileges, that means with UAP notincluding 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 VirtualConcatenation paths of the addressed VCG.

6.88.2 Prerequisites

None.

6.88.3 General

The ways are provided for enabling/disabling VCG members:

• the first one, via NUMPATH parameter, addresses a range of members;

• the second one, via PROVMBRID parameter, addresses a single member. This second way canbe allowed only if LCAS is enabled.

Both NUMPATH and PROVMBRID parameters can not be specified at the same time in thecommand.

Virtual Concatenation Path Check 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

442 Issue 4

Page 443: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The command is denied if the NUMPATH exceeds the maximum number of members within theaddressed 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. Possiblevalues:− 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 throughthe path.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Example: In the following example, all the members of the VCG number 3 on the Multiservicecollector 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 slot5 are being disabled from sending traffic.

CNTRL-VCPATH::GBEVCG-1-1-5-7::::ACTSTATE=IDLE,NUMPATH=ALL;

2

Examine output.

1850 TSS-320/TSS-320H/TSS-160 Virtual Concatenation Path Check

Release 5.1 (ETSI)September 2017Issue 4 4438DG09603CAAATQZZA

Page 444: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

[

/*

<Informational_Description_Text>

*/ cr lf]

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

3

STOP. This procedure is complete.

END OF STEPS

6.89 Modify Equipment Management for Data units

6.89.1 Purpose

This procedure provides instructions for the operator to change the following provisioned andoperating cards:

• PP1GE or PP1GESY card with 10x1GE ports, into a PP1GEX20 or PP1GE20E card with20x1GE ports, saving all the Transmission provisioning over the original ports (Modify 10G to20G).

• PP10GE or PP10GESY card with 1x10GE port, into a PP10GEX2 or PP10GE2E card with2x10GE ports, saving all the Transmission provisioning over the original ports (Modify 10G to20G).

Modify Equipment Management for Data units 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

444 Issue 4

Page 445: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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 & NMside 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 thenew card.

The following table depicts the features that are available or not available, comparing the AID to bemodified with the allowed new AID.

Table 27 Supported features in the modified AIDs

AID to be modified Allowed new AID Not supportedfeatures in the newAID

Description

PP10GEX2 PP10GE6

PP10GE10

T-MPLS In case of presenceof TUSEG withOAM-TYPE =T-MPLS

PWOAM In case of PWSEGwith MEP = ENABLE

Section OAM In case of MPLSIFwith MEP = ENABLE

NNI ring In case of PORT thatare Ring NNI

Access ring In case of UNI PORTcrossconnected to anRing NNI

The MODIFY-EQPT command prepares the addressed card for modifying the AID andPROVISIONEDTYPE parameters with a following execution command.

The MODIFY-EXEC command executes ALL the pending NE card modifications for the new AID andPROVISIONEDTYPE parameters.

The operation is called Modify Equipment or Density Upgrade, and is performed in the followingphases:

• Preparation phase (started with the TL1 command MODIFY-EQPT on each interested PP Card)

1850 TSS-320/TSS-320H/TSS-160 Modify Equipment Management for Data units

Release 5.1 (ETSI)September 2017Issue 4 4458DG09603CAAATQZZA

Page 446: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• Execution phase (started with the TL1 command MODIFY-EXEC for addressing the related NEUpgrade)

During the modify phases, the following equipment commands are denied on the cards/SFPsinvolved 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;

where ALL means all the AID.

2

Examine the response and determine which card you want to change.

Original card Modified card

PP1GE PP1GEX20 or PP1GE20E

PP10GE PP10GEX2 or PP10GE2E

PP10GEX2 PP10GE6 or PP10GE10

3

To remove the card from the shelf, enter MODIFY-EQPT:[TID]:AID:[CTAG]:::NEWAID=,NEWPROVISIONEDTYPE=:;

where:

• AID = Equipment Access Identifier, identifies the equipment entity access identifier.

− PP1GE-{1-7}-{1-9}-{2-9,12-19} UNIV (Packet Module 10x1Gb)

− PP10GE-{1-7}-{1-9}-{2-9,12-19} UNIV (Packet Module 1x10Gb)

− PP10GEX2-{1-7}-{1-9}-{2-9,12-19} ENH (Packet Module 2x10Gb)

• NEWAID = Equipment Access Identifier, identifies the equipment entity access identifier.

− PP1GEX20-{1-7}-{1-9}-{2-9,12-19} UNIV (Packet Module 20x1Gb)

− PP10GEX2-{1-7}-{1-9}-{2-9,12-19} UNIV (Packet Module 2x10Gb)

− PP10GE10-{1-7}-{1-9}-{2,4,6,8,12,14,16,18} ENH (Packet Module 10x10Gb)

Modify Equipment Management for Data units 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

446 Issue 4

Page 447: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 EPROMfor the given equipment.

− PP1GEX20 UNIV Packet Module 20x1GbEthernet (Packet Module 20G)

− PP1GE20E UNIV Packet Module 20x1GbEthernet Evolution (20G)

− PP10GEX2 UNIV Packet Module 2x10GbEthernet (Packet Module 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 toUNVRSL160, 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 arenot related to a Packet Module 20x1GbEthernet

• The addressed AID is a PP10GE and the NEWAID and /or the NEWPROVISIONEDTYPEare 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 thecorresponding slot

• The entity is not in OOS-[AU]MA state

• The command is entered to change the AID/PROVISIONEDTYPE of an Equipment AID butthey 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 andPROVISIONEDTYPE 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 atthe start and completion of processing of the command.

1850 TSS-320/TSS-320H/TSS-160 Modify Equipment Management for Data units

Release 5.1 (ETSI)September 2017Issue 4 4478DG09603CAAATQZZA

Page 448: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 newcard.

8

STOP. This procedure is complete.

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 andoperating cards:

• PP1GEX20 (legacy) card with 20x1GE ports, into a PP1GE20E (enhanced) card with 20x1GEports, 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 2x10GEports, 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 & NMside 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 anprovisioned/unprovisioned slot, pim or port.

If the addressed AID is provisioned, the output is a sequence of rows, one for each provisioned typevalue:

• Allowed by the ED-EQPT command as a substitute for the current provisioned type (that iswithout 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. Thisis a limited capability to allow substitution of compatible module types in certain cases or to changeXFP/SFP features (short/long/intraoffice haul and so on).

Modify Equipment Management for Data units 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

448 Issue 4

Page 449: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6.89.7 Procedure

Perform the following steps:

1

To retrieve the compatible cards, enter RTRV-COMPATIBLE:[TID]:AID:[CTAG];

where:

AID = Equipment Access Identifier, identifies the equipment entity access identifier.

• PP1GEX20-{1-7}-{1-9}-{2-9,12-19} (Packet Module 20x1Gb)

• PP10GEX2-{1-7}-{1-9}-{2-9,12-19} (Packet Module 2x10Gb)

2

To modify the retrieved compatible cards, enter ED-EQPT:[TID]:AID:[CTAG]:::[PROVISIONEDTYPE=][,AINSMODE=][,ALMPROF=] [,CMDMDE=][,APTMODE=][,

VOAMODE=][,APSD1=][,APSD2=][,OPWRL1=][,OPWRL2=][,VOA=][,EOLSPAN=]

[,N1=][,PCH1=][,IT=][,LAMBDASET=][,OPWRLOT2=][,SSBIT=]:[PST];

where:

• AID = Equipment Access Identifier, identifies the equipment entity access identifier.− PP1GEX20-{1-7}-{1-9}-{2-9,12-19} (Packet Module 20x1Gb)

− PP10GEX2-{1-7}-{1-9}-{2-9,12-19} (Packet Module 2x10Gb)

• PROVISIONED TYPE = AID of the provisioned type.− PP1GEX20 UNIV Packet Module 20x1GbEthernet (Packet Module 20G)

− PP1GE20E Packet Module 20x1GbEthernet Evolution (20G)

− PP10GEX2 UNIV Packet Module 2x10GbEthernet (Packet Module 20G)

− PP10GE2E Packet Module 2x10GbEthernet Evolution (20G)

For parameter descriptions of TL1 commands used in this procedure, refer to the1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1Command Guide

3

Enter RTRV-EQPT::ALL; and verify that the AID and PROVISIONEDTYPE match the newcard.

4

STOP. This procedure is complete.

END OF STEPS

1850 TSS-320/TSS-320H/TSS-160 Modify Equipment Management for Data units

Release 5.1 (ETSI)September 2017Issue 4 4498DG09603CAAATQZZA

Page 450: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Modify Equipment Management for Data units 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

450 Issue 4

Page 451: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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”) toimprove cost optimization respect to the current available for TSS-320 equipment.

The new shelf model is referenced as S320H for comparison respectively with current supportedmodel (UNVRSL320).

The Detailed Level Procedures (DLP) contains detailed steps and supporting information requiredto complete a task.

When a DLP is referenced from another part of the manual, perform the DLP, then return to thepoint 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 packsand modules in the system.

7.2.2 Prerequisites

The Enhanced Shelf version is S320H (ENH Shelf 320). Mandatory equipment shall beautomatically 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

1850 TSS-320/TSS-320H/TSS-160 S320H Shelf Detailed Level Procedure

Release 5.1 (ETSI)September 2017Issue 4 4518DG09603CAAATQZZA

Page 452: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

7.2.3 General

The procedure assigns an equipment object entity at the AID physical location and provisions thespecified equipment (also called pre-provisioning) regardless of whether the equipment is installedin 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 cardbeing inserted.

New shelves types (“enhanced shelf”) have been introduced to improve cost optimization respect tothe current available for TSS-320 equipment. The new shelf model is referenced as S320H forcomparison 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 NOWAITindicates an alarm is generated due to an unplugged module.

The PROVISIONEDTYPE parameter identifies the Nokia mnemonic stored in the Remote InventoryEPROM for the module. It is mandatory to specify this parameter for XFP/SFP modules.

The value ANY is used for generic XFP/SFP.

Once equipment is provisioned, ED-EQPT can be used to alter parameters.

7.2.4 Procedure

1

Verify the shelf type entering RTRV-EQPT::ALL;

where ALL means all the AID.

2

Examine the response, as detailed in the relevant command guide, refer to “Command details”(p. 107).

3

Select action.

For Shelf provision, go to Step 4.

For Unit provision, go to Step 7.

For XFP/SFP module provision, go to Step 10.

4

Shelf provision

Provision Equipment (S320H) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

452 Issue 4

Page 453: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 accessidentifier in the {RACK}-{SHELF} format.

• PROVISIONEDTYPE parameter with the value S320H for ENH Shelf 320 HT

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Note:When a Shelf is provisioned, the following Mandatory Equipment Entities areautomatically 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)

5

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, butat 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, andthe assigned AID is different from <SHELF-1-1>

• a Main Shelf is already provisioned and a new ENT-EQPT command has been received withthe 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:

1850 TSS-320/TSS-320H/TSS-160 Provision Equipment (S320H)

Release 5.1 (ETSI)September 2017Issue 4 4538DG09603CAAATQZZA

Page 454: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

8

Enter ENT-EQPT::AID::::[PROVISIONEDTYPE=][,AINSMODE=][,SHELFNUM=][,SHELFROLE=][,LAMBDASET=][,ALMPROF=][,CLNTSEL=][,OPWRLOT2=][,SSBIT=]:

[PST];

where:

• AID=Equipment Access Identifier, identifies the equipment entity access identifier. Possiblevalues: refer to B.3 “AIDs” (p. 692) or to “Command details” (p. 107).

• PROVISIONEDTYPE = Nokia mnemonic stored in the Remote Inventory EPROM for thegiven equipment.

For possible values please refer to B.4 “Provisioned Types” (p. 693).

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

For Card's administration details please refer to 7.3 “Administer S320H module” (p. 455).

Figure 31 S320H enhanced shelf (operator view)

Provision Equipment (S320H) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

454 Issue 4

Page 455: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

9

Is the board provided with an XFP or SFP module?

If yes, go to Step 10.

If no, go to Step 12.

10

XFP/SFP module provision

Verify the XFP/SFP module on the board (ref. to Table 59, “Supported SFP/XFP OpticsModules - Client Side” (p. 692)).

11

Enter ENT-EQPT::AID::::PROVISIONEDTYPE=[,AINSMODE=][,SHELFNUM=][,SHELFROLE=][,APTMODE=][,VOAMODE=][,APSD1=][,APSD2=][,OPWRL1=][,

OPWRL2=][,VOA=][,EOLSPAN=][,N1=][,PCH1=][,IT=][,LAMBDASET=][,ALMPROF=

][,CLNTSEL=][,OPWRLOT2=][,SSBIT=]:[PST];

where:

• AID=Module Access Identifier previously referred in Step 8

• PROVISIONEDTYPE= Nokia mnemonic stored in the Remote Inventory EPROM for thegiven equipment. It is mandatory to specify this parameter for XFP/SFP modules (ANY-<type> is used for generic MSA XFP/SFP). For details see B.4 “Provisioned Types” (p. 693).

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

12

STOP. This procedure is complete.

END OF STEPS

7.3 Administer S320H module

7.3.1 Purpose

This procedure provides instructions to provision “enhanced shelf” boards/circuit packs andmodules in the system.

7.3.2 General

New shelf equipment for TSS-320 is provisioned with TDM, (High Order), ODU or Packet Modulecards with enhanced switching capability (including optical cards from PSS equipment), taking intoaccount 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

1850 TSS-320/TSS-320H/TSS-160 Administer S320H module

Release 5.1 (ETSI)September 2017Issue 4 4558DG09603CAAATQZZA

Page 456: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Note: The potential switching capability of the new TSS-320 shelf (full equipped) shall beextended 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 costreduction:

• 20x1GbE enhanced card with pluggable SFP modules.

The 20x1GbE enhanced card supports 100-FX physical SFP module type and it is capable toperform 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 toperform Ethernet loopback facility (both line and internal)

The system provides provisioning and management of a server card in order to support 1588v2 andTime 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 thespecified module.

If the PST is set to IS the command behaves like RST-EQPT, with the same capabilities andrestrictions described for that command, causing the specified equipment to be placed in the IS orOOS-AU primary state.

If the PST is set to OOS the command behaves like RMV-EQPT, with the same capabilities andrestrictions described for that command, causing a primary state transition from IS or OOS-AU toOOS-MA or OOS-AUMA respectively.

7.3.3 Before you begin

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 itsplugging-in, is activated or not according to the PROVMODE parameter value set with theSET-PRMTR-NE command.

7.3.4 Procedure

1

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.

Administer S320H module 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

456 Issue 4

Page 457: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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

Enter ENT-EQPT::AID::::[PROVISIONEDTYPE=][,AINSMODE=][,SHELFNUM=][,SHELFROLE=][,LAMBDASET=][,ALMPROF=][,CLNTSEL=][,OPWRLOT2=][,SSBIT=]:

[PST];

where:

• AID=Equipment Access Identifier, identifies the equipment entity access identifier. Possiblevalues see “Procedure” (p. 457).

• PROVISIONEDTYPE = Nokia mnemonic stored in the Remote Inventory EPROM for thegiven equipment.

For possible values please refer to “Procedure” (p. 457).

AID Provisioned Type Description

[ETSI] E1M-{1-7}-{2}-{7-14} [ETSI] P63E1ETSI 63 x E1 PortModule

[ETSI] E1ACC-{1-7}-{2}-{3-5,16-18}

[ETSI] A63E1AETSI 63 x E1 AccessModule 75ohm unb

[ETSI] A63E1BETSI 63 x E1 AccessModule 120ohm bal

[ETSI] E1PR-{1-7}-{2}-{2,19} [ETSI] LSPROTETSI 63 x E1 AccessProtection Module

10GSO-{1-7}-{1-9}-{2-9,12-19,21-36}

1P10GSO10G SynchronousOptical

1P10GSOE10G SynchronousOptical Evolution

1850 TSS-320/TSS-320H/TSS-160 Administer S320H module

Release 5.1 (ETSI)September 2017Issue 4 4578DG09603CAAATQZZA

Page 458: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

AID Provisioned Type Description

2G5SO-{1-7}-{1-9}-{2-9,12-19,21-36}

4P2G5SO4x2.5G SynchronousOptical

8XSO-{1-7}-{1-9}-{2-9,12-19,21-36}

8PSO8 x SynchronousOptical

MRSOE-{1-7}-{1-9}-{2-9,12-19,21-36}

MRSOESDX/SONET MultirateCard

OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36}

1POTU2 G.709 OTU 10GB Card

OT2TDMXB-{1-7}-{1-9}-{2-9,12-19,21-36}

1POTU2XBG.709 OTU 10GB Card- XFP based

10XANY-{1-7}-{1-9}-{2-9,12-19,21-36}

10XANY 10GB 10 x GBE/Sonet

PRE-{1-7}-{1-9}-{2-9,12-19,21-36}

PRE10GOptical Pre-Amplifer10G

BOOST-{1-7}-{1-9}-{2-9,12-19,21-36}

BOOST10G Optical Booster 10G

DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36}

DWLA10XDWDM OpticalTransponder withColored XFPs

PP10AD-{1-7}-{1-9}-{2-9,12-19} PP10MSMultiService AdaptationCard (Packet Module10G)

PP10AD-{1-7}-{1-9}-{2-9,12-19} [ETSI] PP10GATM

ETSI MultiServiceAdaptation Card forATM (Packet Module10G)

PPUGW-{1-7}-{1-9}-{2-9,12-19} [ETSI] PP2G5UGWETSI UGW AdaptationCard - Packet Module2.5G

PP1GEX20-{1-7}-{1-9}-{2-9,12-19}

PP1GE20EPacket Module20x1GbEthernetEvolution (20G)

PP10GEX2-{1-7}-{1-9}-{2-9,12-19}

PP10GE2E

PP10GE2E PacketModule2x10GbEthernetEvolution (20G)

Administer S320H module 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

458 Issue 4

Page 459: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

AID Provisioned Type Description

PTP-{1-7}-{1-9}-{2-9,12-19,21-36}

PP1588Time Of Day - TODCard

PTP Packet Processor

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

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 specifiedequipment 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 thegiven equipment.

• PST = Primary State, specifies the primary state to which the equipment is set. Possiblevalues are: IS, OOS.

For possible AID and PROVISIONEDTYPE values please refer to “Procedure” (p. 457).

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Example: The following command performs logical removal for the module 10GSO-1-1-5.ED-EQPT:: 10GSO-1-1-5:::::OOS;

10

Remove board

1850 TSS-320/TSS-320H/TSS-160 Administer S320H module

Release 5.1 (ETSI)September 2017Issue 4 4598DG09603CAAATQZZA

Page 460: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

To place in the out-of-service management service state specified equipment enter:

RTRV-EQPT::AID;

where:

• AID = Equipment Access Identifier, identifies the equipment entity access identifier

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 provisionedon it or paths are cross connected) can be logically removed only with the MODE parameter setto FRCD. the same for an active module, only the MODE=FRCD is accepted, and it is up to theoperator to manually execute the switch to the other copy before or after the logical removal ofthe 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

Administer S320H module 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

460 Issue 4

Page 461: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter:

RTRV-EQPT::AID;

where:

• AID = Equipment Access Identifier, identifies the equipment entity access identifier

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:

• AID = Equipment Access Identifier, identifies the equipment entity access identifier

• MODE = Command Mode, identifies the Command Execution Mode. Values are:

NORM Normal, the command is denied if the result of its execution is service-affecting.

FRCD Forced, the command is completed even if the result of its execution isservice-affecting. Forced mode is used also to force a transition from OOS-AUMA,FLT toOOS-AU,FLT state.

END OF STEPS

1850 TSS-320/TSS-320H/TSS-160 Administer S320H module

Release 5.1 (ETSI)September 2017Issue 4 4618DG09603CAAATQZZA

Page 462: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Administer S320H module 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

462 Issue 4

Page 463: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

8 TMPLS/MPLS-TP Detailed Level Procedure

8.1 Overview

8.1.1 Purpose

The Detailed Level Procedures (DLP) contains detailed steps and supporting information requiredto 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

1850 TSS-320/TSS-320H/TSS-160 TMPLS/MPLS-TP Detailed Level Procedure

Release 5.1 (ETSI)September 2017Issue 4 4638DG09603CAAATQZZA

Page 464: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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-TPLoopback 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 specifieddestination.

• On-demand bidirectional connectivity verification: this implies the verification that in theindicated 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 optionallyand implies the activation of bidirectional connectivity verification).

• Whether Test TLV shall be included or not in transmitted LBM frame with the possibility toconfigure Test-Type

When the LBM packet is sent to a target MIP, the source MEP MUST know the hop count to thetarget MIP and set the TTL field accordingly.

In case of connectivity verification the configuration of the following parameters is needed for theMIP:

• MEG ID

• Expected MEP ID

Besides when the LBM packet is sent to a target MIP the following configurations shall be possible:

• TTL (Time To Live)

• Target MIP-ID (includes Node and Port Identifiers).

• PHB

• Packet Length

• LBM packet interval

• Start Date & TIME, and End Date & TIME, or Number of LBM frames to be sent Activation of

Administer MPLS-TP Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

464 Issue 4

Page 465: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

bidirectional connectivity verification (this can be done only if the source MEP and the targetMIP have been configured with all expected parameters).

• Whether Test TLV shall be included or not in transmitted LBM frame with the possibility toconfigure 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 commandspecifying 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 andDISCOVERY=NODISCOVERY then this command will be refused.

It is possible to have more LoopBack Tool instances from this TUSEG (=MEP) to different MEP/MIPwith 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 snapshotvalue of the measurement counters at the time when RTRV-TMPLS-ODLBOUTPUT command isissued.

For one on-demand LB instance with LB-TOOL-STATE==CONFIGURED, it shall return the currentvalue of the measurement counters collected by the instance during last run.

8.2.5 Before you begin

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

1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Loopback OAM tool

Release 5.1 (ETSI)September 2017Issue 4 4658DG09603CAAATQZZA

Page 466: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• TARGET-MEPID=NOTARGET and TARGET-MIPID=NOTARGET andDISCOVERY=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

1

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_TPthat

It is required that for that terminated TUSEG

• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} thisis 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

Administer MPLS-TP Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

466 Issue 4

Page 467: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 (nodewhere the TTL expires)

• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent: this is in alternativeto TARGET-MEPID or DISCOVERY; no default

• TARGET-MIPICC = ITU-T Carrier Code for LoopBack Tool to be inserted in LBM packet. Thisparameter is used to complete the TARGET-MIPID

• DISCOVERY = to indicate if the ingress or egress MIP has to be addressed in the discoverycase 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 Testpattern type.

Note: It is not possible to have Loopback to MIP/MEP at the same time as DISCOVERYtool 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 modulatecommand behavior.

Restrictions:If AID=ALL then the Operator must enter TOOL parameter. If AID<>ALL theTOOL 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 Toolwhen 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/EDcommand, that is the MEP begins to send and receive packet depending on theconfigured SEND-PKT-NUM or according to the START-TIME value

1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Loopback OAM tool

Release 5.1 (ETSI)September 2017Issue 4 4678DG09603CAAATQZZA

Page 468: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 Demandtools.

4

To change the LB tool settings

Retrieve OAM On Demand LB-Tool information entered with ENT-TMPLS-ODLB command.

Enter:

RTRV-TMPLS-ODLB::[AID]:::[TERM-AID];

where:

AID = ODLBS-{1-512} - On Demand OAM LB-Tool Sender.

5

Examine output.

Is the NE-LB-TOOLS output parameter value CONFIGURED?

If YES, go to Step 6.

If NO, go to Step 1.

6

Enter

ED-TMPLS-ODLB::AID::::[TARGET-MEPID=][,LB-PHB=][,PERIOD=]

[,SEND-PKT-NUM=][,PKT-LENGTH=][,START-TIME=][,END-TIME=][,SRC-ID=][,

TTL=][,TARGET-MIPID=][,TARGET-MIPICC=][,DISCOVERY=][,TEST-TLV=][,TES

T-TYPE=];

where:

AID = ODLBS-{1-512} -On Demand OAM LB-Tool Sender.

TARGET-MEPID = The MEP Identifier of peer MEP where MPLS-TP LBM is destinated for.

Note: RestrictionsIf TARGET-MIPID=NOTARGET and DISCOVERY=NODISCOVERY then this parametermust be entered with a valid numeric value.If NOTARGET value is used for this parameter then TARGET-MIPID or DISCOVERYparameter must be exclusively edited with TARGET-MIPID<>NOTARGET orDISCOVERY<>NODISCOVERY.If the entered LB-Tools already exists for the value pair (AID, TARGET-MEPID), then thecommand shall be denied.

LB-PHB = PHB value associated to LBM packets

Administer MPLS-TP Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

468 Issue 4

Page 469: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Note: Restrictions: The chosen LB-PHB must be present into PHB profile used byTerminated TMPLS Facility where the LB-Tool has been configured.

TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent. The TARGET-MIPIDis composed by two ID:

MIP-NODEID parameter definition of ED-TMPLS-GLOBAL command.

IF-NUM: {1-7}-{1-9}-{1-63}-{1-1024} AID of the physical interface.

7

To delete the LB tool

Enter:

RTRV-TMPLS-ODLB::[AID]:::[TERM-AID];

where:

AID = ODLBS-{1-512} - On Demand OAM LB-Tool Sender.

8

Examine output.

Is the NE-LB-TOOLS output parameter value CONFIGURED?

If YES, go to Step 9.

If NO, go to Step 1.

9

Enter:

DLT-TMPLS-ODLB]:AID;

where:

AID = ODLBS-{1-512} - On Demand OAM LB-Tool Sender.

10

To retrieve the DM data

Enter:

RTRV-TMPLS-ODLB::[AID]:::[TERM-AID];

where:

AID = ODLBS-{1-512} - On Demand OAM LB-Tool Sender.

TERM-AID = AID of the Terminated TMPLS facility where the LB-Tool has been configured.

Result:

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.

1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Loopback OAM tool

Release 5.1 (ETSI)September 2017Issue 4 4698DG09603CAAATQZZA

Page 470: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 inthe discovery case.

11

Retrieve LB tool measurement results

Enter:

RTRV-TMPLS-ODLB::[AID]:::[TERM-AID];

where:

AID = ODLBS-{1-512} - On Demand OAM LB-Tool Sender.

12

Examine output.

Is the NE-LB-TOOLS output parameter value CONFIGURED?

If YES, Step 13.

If NO, go to Step 15.

13

Enter:

RTRV-TMPLS-ODLBOUTPUT::AID;

where:

AID = ODLBS-{1-512} - On Demand OAM LB-Tool Sender.

14

Examine output. It returns the current value of the measurement counters collected by theinstance during last run.

15

If the NE-LB-TOOLS output parameter value is Runningthen enter:

RTRV-TMPLS-ODLBOUTPUT::AID;

where:

AID = ODLBS-{1-512} - On Demand OAM LB-Tool Sender.

16

Examine output. It returns the snapshot value of the measurement counters at the time whenRTRV-TMPLS-ODLBOUTPUT command is issued.

END OF STEPS

Administer MPLS-TP Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

470 Issue 4

Page 471: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 theindicated destination there is the match of the expected MEG/MEP IDs

When the LBM packet is sent to a target MEP, following configurations shall be possible:

• Target MEP ID

• PHB

• Packet Length

• LBM packet interval

• Start Date & TIME, and End Date & TIME, or Number of LBM frames to be sent

• Whether Requesting MEP ID shall be included or not in transmitted LBM frame (this optionallyand implies the activation of bidirectional connectivity verification).

• Whether Test TLV shall be included or not in transmitted LBM frame with the possibility toconfigure Test-Type

When the LBM packet is sent to a target MIP, the source MEP MUST know the hop count to thetarget MIP and set the TTL field accordingly.

In case of connectivity verification the configuration of the following parameters is needed for theMIP:

• MEG ID

• Expected MEP ID

Besides when the LBM packet is sent to a target MIP the following configurations are possible:

• TTL (Time To Live)

• Target MIP-ID (includes Node and Port Identifiers).

• PHB

• Packet Length

• LBM packet interval

• Start Date & TIME, and End Date & TIME, or Number of LBM frames to be sent Activation ofbidirectional connectivity verification (this can be done only if the source MEP and the targetMIP have been configured with all expected parameters).

• Whether Test TLV shall be included or not in transmitted LBM frame with the possibility toconfigure Test-Type.

1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Connectivity verification Loopback OAM tool

Release 5.1 (ETSI)September 2017Issue 4 4718DG09603CAAATQZZA

Page 472: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

8.3.3 Before you begin

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

• TARGET-MEPID=NOTARGET and TARGET-MIPID=NOTARGET andDISCOVERY=NODISCOVERY not an accettable value

• the Terminated TMPLS facility(i.e. TUSEG) specified by AID should be MPLS_TP, BIDIR,MEP=ENABLE.

Figure 32 MEP/MIP configuration for loopback connectivity verification

Administer MPLS-TP Connectivity verification Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

472 Issue 4

Page 473: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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. Thedefault value for this parameter is 4.

• PHB-RANGE-SEL = Selector of the default value for PHBPROF (PHBPROF-1 orPHBPROF-2) for creation of new TUSEGs, PWSEGs and TUNNELs. The default value forthis 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 defaultvalue for this parameter is 5.

• ICC-LB = ITU-T Carrier Code for LoopBack Tool to be inserted in Replying MIP ID TLV. Thedefault value for this parameter is the string "000000".

• MIP-NODEID = Node-ID for MIP addressing. It is a 32 bit number entered using IP Addressformat. The choosen value must be unique in the network. The initial value for this parameteris 0-0-0-0. When the MIP-NODEID is uqual to 0-0-0-0 then the System will use the IPaddress 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=]

1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Connectivity verification Loopback OAM tool

Release 5.1 (ETSI)September 2017Issue 4 4738DG09603CAAATQZZA

Page 474: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 TUSegmentTermination (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. Thevalue 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.

5

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 Step10.

6

Connectivity verification loopback (TARGET = MEP)

Enter:

ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,DISCOVERY=];

where:

• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.

Remember: It is required that the TUSEG involved must have:

− DIR = BIDIR

− MEP = enable

Administer MPLS-TP Connectivity verification Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

474 Issue 4

Page 475: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

− TYPE=TERMINATED

− OAM-TYPE=MPLS_TP

• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} thisis 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 beaddressed in the discovery case this is in alternative to TARGET-MEPID or TARGET-MIPID;

Note: It is not possible to have Loopback to MIP/MEP at the same time as DISCOVERYtool from a TUSEG.

7

Connectivity verification loopback (TARGET = MIP)

Enter:

ENT-TMPLS-ODLB::AID::::[,SRC-ID=][,TTL=][,TARGET-MIPID=][,DISCOVERY=];

where:

• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.

Remember: It is required that the TUSEG involved must have:

− DIR = BIDIR

− MEP = enable

− TYPE=TERMINATED

− OAM-TYPE=MPLS_TP

• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.

Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then thisparameter must be entered with a valid MIP-NODEID and IF-NUM.

If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>NODISCOVERY then this parameter can't be entered.

If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,TARGET-MIPICC), then the command shall be denied.

• SRC-ID = ENABLE. It indicates whether Requesting MEP ID TLV shall be included or not{ENABLE, DISABLE}

• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back(node where the TTL expires)

• DISCOVERY = NODISCOVERY. It indicates if the ingress or egress MIP has to beaddressed in the discovery case this is in alternative to TARGET-MEPID or TARGET-MIPID;

Note: It is not possible to have Loopback to MIP/MEP at the same time as DISCOVERYtool from a TUSEG.

1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Connectivity verification Loopback OAM tool

Release 5.1 (ETSI)September 2017Issue 4 4758DG09603CAAATQZZA

Page 476: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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:

• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.

Remember: It is required that the TUSEG involved must have:

− DIR = BIDIR

− MEP = enable

− TYPE=TERMINATED

− OAM-TYPE=MPLS_TP

• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} thisis in alternative to TARGET-MIPID or DISCOVERY;

• SRC-ID = ENABLE. It indicates whether Requesting MEP ID TLV shall be included or not{ENABLE, DISABLE}

• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back(node where the TTL expires)

• PKT-LENGTH = 101, 104 – 1500 (Default = 101).

This parameter is used to define the length of the LBM frames to be sent.

Restrictions: If TEST-TLV = DISABLE and SRC-ID = ENABLE then PKT-LENGTH ≥ 101and ≠ (102, 103)

• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.

Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then thisparameter must be entered with a valid MIP-NODEID and IF-NUM.

If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>NODISCOVERY then this parameter can't be entered.

If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,TARGET-MIPICC), then the command shall be denied.

• DISCOVERY = It indicates if the ingress or egress MIP has to be addressed in the discoverycase this is in alternative to TARGET-MEPID or TARGET-MIPID;

• TEST-TLV = DISABLE.

This parameter enables the insertion of the Test TLV in the Loopback packet.

9

Connectivity verification Test TLV without CRC

To perform CV loopback without TLV on MEP/MIP targert or with the Discovery feature enabled,enter:

Administer MPLS-TP Connectivity verification Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

476 Issue 4

Page 477: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,PKT-LENGTH=]

[,TARGET-MIPID=][,DISCOVERY=][,TEST-TLV=][,TEST-TYPE=];

where:

• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.

Remember: It is required that the TUSEG involved must have:

− DIR = BIDIR

− MEP = enable

− TYPE=TERMINATED

− OAM-TYPE=MPLS_TP

• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} thisis in alternative to TARGET-MIPID or DISCOVERY;

• SRC-ID = ENABLE. It indicates whether Requesting MEP ID TLV shall be included or not{ENABLE, DISABLE}

• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back(node where the TTL expires)

• PKT-LENGTH = 105 – 1500 (Default = 105).

This parameter is used to define the length of the LBM frames to be sent.

Restrictions: If TEST-TLV = ENABLE and SRC-ID = ENABLE and TEST-TYPE = 0, 2 thenPKT-LENGTH ≥ 105

• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.

Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then thisparameter must be entered with a valid MIP-NODEID and IF-NUM.

If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>NODISCOVERY then this parameter can't be entered.

If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,TARGET-MIPICC), then the command shall be denied.

• DISCOVERY = It indicates if the ingress or egress MIP has to be addressed in the discoverycase this is in alternative to TARGET-MEPID or TARGET-MIPID;

• TEST-TLV = ENABLE.

This parameter enables the insertion of the Test TLV in the Loopback packet.

• TEST-TYPE = 0, 2. Pattern Type value that it is included in the optional Test TLV identifingthe Test pattern type.

Where:

0 = Null signal (all-zeros) without CRC-32.

2 = PRBS 2-31-1 without CRC-32.

10

Connectivity verification Test TLV with CRC enabled

To perform CV loopback without TLV on MEP/MIP targert or with the Discovery feature enabled,enter:

1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Connectivity verification Loopback OAM tool

Release 5.1 (ETSI)September 2017Issue 4 4778DG09603CAAATQZZA

Page 478: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,PKT-LENGTH=]

[,TARGET-MIPID=][,DISCOVERY=][,TEST-TLV=][,TEST-TYPE=];

where:

• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.

Remember: It is required that the TUSEG involved must have:

− DIR = BIDIR

− MEP = enable

− TYPE=TERMINATED

− OAM-TYPE=MPLS_TP

• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} thisis in alternative to TARGET-MIPID or DISCOVERY;

• SRC-ID = ENABLE. It indicates whether Requesting MEP ID TLV shall be included or not{ENABLE, DISABLE}

• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back(node where the TTL expires)

• PKT-LENGTH = 109 – 1500 (Default = 109).

This parameter is used to define the length of the LBM frames to be sent.

Restrictions: If TEST-TLV = ENABLE and SRC-ID = ENABLE and TEST-TYPE = 1, 3 thenPKT-LENGTH ≥ 109

• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.

Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then thisparameter must be entered with a valid MIP-NODEID and IF-NUM.

If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>NODISCOVERY then this parameter can't be entered.

If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,TARGET-MIPICC), then the command shall be denied.

• DISCOVERY = It indicates if the ingress or egress MIP has to be addressed in the discoverycase this is in alternative to TARGET-MEPID or TARGET-MIPID;

• TEST-TLV = ENABLE.

This parameter enables the insertion of the Test TLV in the Loopback packet.

• TEST-TYPE = 1, 3. Pattern Type value that it is included in the optional Test TLV identifingthe Test pattern type.

Where:

1 = Null signal (all-zeros) with CRC-32.

3 = PRBS 2-31-1 with CRC-32.

END OF STEPS

Administer MPLS-TP Connectivity verification Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

478 Issue 4

Page 479: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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-TPDiagnostic 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 specifieddestination.

8.4.3 Before you begin

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.

Figure 33 Diagnostic loopback

1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Diagnostic Loopback OAM tool

Release 5.1 (ETSI)September 2017Issue 4 4798DG09603CAAATQZZA

Page 480: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• LB-PHB parameter value is into PHB profile used by this Terminated TMPLS facility

• START-TIME is not antecedent to “Current System Date-Time”

• END-TIME is not antecedent or equal to START-TIME

• START-TIME/END-TIME parameter is not entered together with SEND-PKT-NUM parameter

• TARGET-MEPID=NOTARGET and TARGET-MIPID=NOTARGET andDISCOVERY=NODISCOVERY not an accettable value

• the Terminated TMPLS facility(i.e. TUSEG) specified by AID should be MPLS_TP, BIDIR,MEP=ENABLE.

8.4.4 Procedure

1

Check if global network parameters assigned to T-MPLS should be changed.

Enter:

RTRV-TMPLS-GLOBAL:[TID]::[CTAG];

2

Examine output.

3

Enter:

ED-TMPLS-GLOBAL:[TID]::[CTAG]:::[OAM-CVPERIOD-SEL=][,PHB-RANGE-SEL=]

[,OAM-TYPE-SEL=][,OAM-RX-DETECT=][,CHANNEL-TYPE=][,PROLM-MODE-BIT=][,

LBR-TIMEOUT=][,ICC-LB=][,MIP-NODEID=][,APSRING-CHANNEL-TYPE=][,CHAN

NEL-TYPE-RX1=][,CHANNEL-TYPE-RX2=][,APSRING-CHANNEL-TYPE-RX1=][,APSR

ING-CHANNEL-TYPE-RX2=][,IGNORE-SEC-BIT=][,STATUS-BIT=];

where:

• OAM-CVPERIOD-SEL = Selector of values range for CV Period into OAM CV frames. Thedefault value for this parameter is 4.

• PHB-RANGE-SEL = Selector of the default value for PHBPROF (PHBPROF-1 orPHBPROF-2) for creation of new TUSEGs, PWSEGs and TUNNELs. The default value forthis 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 defaultvalue for this parameter is 5.

• ICC-LB = ITU-T Carrier Code for LoopBack Tool to be inserted in Replying MIP ID TLV. Thedefault value for this parameter is the string "000000".

• MIP-NODEID = Node-ID for MIP addressing. It is a 32 bit number entered using IP Addressformat. The choosen value must be unique in the network. The initial value for this parameteris 0-0-0-0. When the MIP-NODEID is uqual to 0-0-0-0 then the System will use the IPaddress value of this NE as Node-ID for MIP LoopBack addressing.

Administer MPLS-TP Diagnostic Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

480 Issue 4

Page 481: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

4

Create the Terminated TMPLS facility(i.e. TUSEG) specified by AID should be MPLS_TP,BIDIR, MEP=ENABLE.

Enter:

ENT-TMPLS-TUSEG:[TID]::[CTAG]::PORT,[TYPE],[DIR],[USERNAME]:

[L2ENCAPPROF-AID=][,INLABEL=][,OUTLABEL=][,PHBPROF-AID=][,OAMPHB-AID=]

[,MEP= ][,MEG-ID=][,MEP-ID=][,EXPMEP-ID=][,CVRX=][,CVTX=][,CVPERIOD=]

[,CVPH B=][,ALMPROF=][,ADD-GROUP=][,PS-DDM-SD=][,OAM-TYPE=][,

PROSLMCVTX=][,PROSLMCVRX=][,PROLM-PLP=][,PROLM-SD-CROSSTH=][,

PROLM-SD-CLEARTH=][,P RODM=][,PRODM-PHB=][,PRODM-PERIOD=][,

PRODM-PKT-LENGTH=][,TCAPROF=][, RDI-SD=][,MIPING-EXPMEP-ID=][,

MIPEGR-EXPMEP-ID=][,RING=];

where:

• PORT = AID of the port which is server of the MPLS TUSegment.

• TYPE = TERMINATION.

• DIR = BIDIR

• MEP=ENABLE

• OAM-TYPE=MPLS_TP

• MEP-ID= {0-8191}. Transmitted MEP value, integer associated to Source TUSegmentTermination (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. Thevalue 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.

5

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)

1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Diagnostic Loopback OAM tool

Release 5.1 (ETSI)September 2017Issue 4 4818DG09603CAAATQZZA

Page 482: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter:

ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,DISCOVERY=];

where:

• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.

Remember: It is required that the TUSEG involved must have:

− DIR = BIDIR

− MEP = enable

− TYPE=TERMINATED

− OAM-TYPE=MPLS_TP

• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} thisis in alternative to TARGET-MIPID or DISCOVERY;

• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not{ENABLE, DISABLE}

• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back(node where the TTL expires)

• DISCOVERY = NODISCOVERY. It indicates if the ingress or egress MIP has to beaddressed in the discovery case this is in alternative to TARGET-MEPID or TARGET-MIPID;

Note: It is not possible to have Loopback to MIP/MEP at the same time as DISCOVERYtool from a TUSEG.

7

Diagnostic loopback (TARGET = MIP)

Enter:

ENT-TMPLS-ODLB::AID::::[,SRC-ID=][,TTL=][,TARGET-MIPID=][,DISCOVERY=];

where:

• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.

Remember: It is required that the TUSEG involved must have:

− DIR = BIDIR

− MEP = enable

− TYPE=TERMINATED

− OAM-TYPE=MPLS_TP

• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.

Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then thisparameter 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.

Administer MPLS-TP Diagnostic Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

482 Issue 4

Page 483: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not{ENABLE, DISABLE}

• TTL = {1-255}. Time To Live used to identify the MIP where the LBM packet has to be sentback (node where the TTL expires)

• DISCOVERY = NODISCOVERY. It indicates if the ingress or egress MIP has to beaddressed in the discovery case this is in alternative to TARGET-MEPID or TARGET-MIPID;

Note: It is not possible to have Loopback to MIP/MEP at the same time as DISCOVERYtool from a TUSEG.

8

Diagnostic loopback - No test TLV

To perform CV loopback without TLV on MEP/MIP targert or with the Discovery feature enabled,enter:

ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,PKT-LENGTH=]

[,TARGET-MIPID=][,DISCOVERY=][,TEST-TLV=];

where:

• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.

Remember: It is required that the TUSEG involved must have:

− DIR = BIDIR

− MEP = enable

− TYPE=TERMINATED

− OAM-TYPE=MPLS_TP

• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} thisis in alternative to TARGET-MIPID or DISCOVERY;

• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not{ENABLE, DISABLE}

• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back(node where the TTL expires)

• PKT-LENGTH = 45, 48 – 1500(Default = 45).

This parameter is used to define the length of the LBM frames to be sent.

Restrictions: If TEST-TLV = DISABLE and SRC-ID = DISABLE then PKT-LENGTH ≥ 45 and≠ (46, 47)

• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.

Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then thisparameter must be entered with a valid MIP-NODEID and IF-NUM.

If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>NODISCOVERY then this parameter can't be entered.

If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,TARGET-MIPICC), then the command shall be denied.

• DISCOVERY = It indicates if the ingress or egress MIP has to be addressed in the discoverycase this is in alternative to TARGET-MEPID or TARGET-MIPID;

1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Diagnostic Loopback OAM tool

Release 5.1 (ETSI)September 2017Issue 4 4838DG09603CAAATQZZA

Page 484: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• TEST-TLV = DISABLE.

This parameter enables the insertion of the Test TLV in the Loopback packet.

9

Diagnostic loopback - Test TLV without CRC

To perform CV loopback without TLV on MEP/MIP targert or with the Discovery feature enabled,enter:

ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,PKT-LENGTH=]

[,TARGET-MIPID=][,DISCOVERY=][,TEST-TLV=][,TEST-TYPE=];

where:

• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.

Remember: It is required that the TUSEG involved must have:

− DIR = BIDIR

− MEP = enable

− TYPE=TERMINATED

− OAM-TYPE=MPLS_TP

• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} thisis in alternative to TARGET-MIPID or DISCOVERY;

• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not{ENABLE, DISABLE}.

• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back(node where the TTL expires)

• PKT-LENGTH = 49 – 1500 (Default = 49).

This parameter is used to define the length of the LBM frames to be sent.

Restrictions: If TEST-TLV = ENABLE and SRC-ID = DISABLE and TEST-TYPE = 0, 2 thenPKT-LENGTH ≥ 49

• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.

Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then thisparameter must be entered with a valid MIP-NODEID and IF-NUM.

If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>NODISCOVERY then this parameter can't be entered.

If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,TARGET-MIPICC), then the command shall be denied.

• DISCOVERY = It indicates if the ingress or egress MIP has to be addressed in the discoverycase this is in alternative to TARGET-MEPID or TARGET-MIPID;

• TEST-TLV = ENABLE.

This parameter enables the insertion of the Test TLV in the Loopback packet.

• TEST-TYPE = 0, 2. Pattern Type value that it is included in the optional Test TLV identifingthe Test pattern type.

Where:

0 = Null signal (all-zeros) without CRC-32.

Administer MPLS-TP Diagnostic Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

484 Issue 4

Page 485: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

2 = PRBS 2-31-1 without CRC-32.

10

Diagnostic Loop - Test TLV with CRC enabled

To perform CV loopback without TLV on MEP/MIP targert or with the Discovery feature enabled,enter:

ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,PKT-LENGTH=]

[,TARGET-MIPID=][,DISCOVERY=][,TEST-TLV=][,TEST-TYPE=];

where:

• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.

Remember: It is required that the TUSEG involved must have:

− DIR = BIDIR

− MEP = enable

− TYPE=TERMINATED

− OAM-TYPE=MPLS_TP

• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} thisis in alternative to TARGET-MIPID or DISCOVERY;

• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not{ENABLE, DISABLE}

• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back(node where the TTL expires)

• PKT-LENGTH = 101, 104 – 1500 (Default = 101).

This parameter is used to define the length of the LBM frames to be sent.

Restrictions: If TEST-TLV = ENABLE and SRC-ID = DISABLE and TEST-TYPE = 1, 3 thenPKT-LENGTH ≥ 53

• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.

Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then thisparameter must be entered with a valid MIP-NODEID and IF-NUM.

If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>NODISCOVERY then this parameter can't be entered.

If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,TARGET-MIPICC), then the command shall be denied.

• DISCOVERY = It indicates if the ingress or egress MIP has to be addressed in the discoverycase this is in alternative to TARGET-MEPID or TARGET-MIPID;

• TEST-TLV = ENABLE.

This parameter enables the insertion of the Test TLV in the Loopback packet.

• TEST-TYPE = 1, 3. Pattern Type value that it is included in the optional Test TLV identifingthe Test pattern type.

Where:

1 = Null signal (all-zeros) with CRC-32.

1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Diagnostic Loopback OAM tool

Release 5.1 (ETSI)September 2017Issue 4 4858DG09603CAAATQZZA

Page 486: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 issent 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 theLSP Tunnel.

Figure 34 Discovery loopback - target = MEP

Administer MPLS-TP Discovery Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

486 Issue 4

Page 487: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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-ODLBcommand.

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 thegeneration 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 thevalue of the TransID, so the type of DISCOVERY (ingress/egress) associated to the ODLBS-i AIDcan 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

8.5.4 Before you begin

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

• TARGET-MEPID=NOTARGET and TARGET-MIPID=NOTARGET andDISCOVERY=NODISCOVERY not an accettable value

Figure 35 Discovery loopback - target = MIP

1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Discovery Loopback OAM tool

Release 5.1 (ETSI)September 2017Issue 4 4878DG09603CAAATQZZA

Page 488: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• the Terminated TMPLS facility(i.e. TUSEG) specified by AID should be MPLS_TP, BIDIR,MEP=ENABLE.

Note: It is not possible to have Loopback to MIP/MEP at the same time as DISCOVERY toolfrom a TUSEG. It is possible the following:

• one tool for each <AID, TARGET-MEPID,DISCOVERY>

• one tool for each <AID, TARGET-MIPID,DISCOVERY>

8.5.5 Procedure

1

Check if global network parameters assigned to T-MPLS should be changed.

Enter:

RTRV-TMPLS-GLOBAL;

2

Examine output.

3

Enter:

ED-TMPLS-GLOBAL::::::[OAM-CVPERIOD-SEL=][,PHBRANGE-SEL=]

[,OAM-TYPE-SEL=] [,OAM-RX-DETECT=][,CHANNELTYPE=][,PROLM-MODE-BIT=]

[,LBR-TIMEOUT=][,ICC-LB=][,MIP-NODEID];

where:

• OAM-CVPERIOD-SEL = Selector of values range for CV Period into OAM CV frames. Thedefault value for this parameter is 4.

• PHB-RANGE-SEL = Selector of the default value for PHBPROF (PHBPROF-1 orPHBPROF-2) for creation of new TUSEGs, PWSEGs and TUNNELs. The default value forthis 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 defaultvalue for this parameter is 5.

• ICC-LB = ITU-T Carrier Code for LoopBack Tool to be inserted in Replying MIP ID TLV. Thedefault value for this parameter is the string "000000".

• MIP-NODEID = Node-ID for MIP addressing. It is a 32 bit number entered using IP Addressformat. The choosen value must be unique in the network. The initial value for this parameteris 0-0-0-0. When the MIP-NODEID is uqual to 0-0-0-0 then the System will use the IPaddress 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.

Administer MPLS-TP Discovery Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

488 Issue 4

Page 489: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter:

ENT-TMPLS-TUSEG:::::PORT,[TYPE],[DIR],[USERNAME]: [L2ENCAPPROF-AID=][,

INLABEL=][,OUTLABEL=][,PHBPROF-AID=][,OAMPHB-AID=] [,MEP=][,MEG-ID=][,

MEP-ID=][,EXPMEP-ID=][,CVRX=][,CVTX=][,CVPERIOD=][,CVPHB=]

[,ALMPROF=][,ADD-GROUP=][,OAM-TYPE=] [,TCAPROF=][,RDI-SD=][,

MIPING-EXPMEP-ID][,MIPEGR-EXPMEP-ID];

where:

• PORT = AID of the port which is server of the MPLS TUSegment.

• TYPE = TERMINATION.

• DIR = BIDIR

• MEP=ENABLE

• OAM-TYPE=MPLS_TP

• MEP-ID= {0-8191}. Transmitted MEP value, integer associated to Source TUSegmentTermination (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. Thevalue 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.

5

Select action:

• To perform the Discovery loopback (TARGET = MEP), go to Step 6.

• To perform the Discovery loopback (TARGET = MIP), go to Step 7.

6

Discovery loopback (TARGET = MEP)

Enter:

ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,DISCOVERY=];

where:

• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.

Remember: It is required that the TUSEG involved must have:

− DIR = BIDIR

− MEP = enable

− TYPE=TERMINATED

1850 TSS-320/TSS-320H/TSS-160 Administer MPLS-TP Discovery Loopback OAM tool

Release 5.1 (ETSI)September 2017Issue 4 4898DG09603CAAATQZZA

Page 490: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

− OAM-TYPE=MPLS_TP

• TARGET-MEPID = NOTARGET.

Restrictions:

If TARGET-MIPID=NOTARGET and DISCOVERY=NODISCOVERY then this parameter mustbe entered with a valid numeric value.

If TARGET-MIPID<>NOTARGET then this parameter can't be entered.

If DISCOVERY<>NODISCOVERY then this parameter can't be entered.

If the entered LB-Tools already exists for the value pair (AID, TARGET-MEPID), then thecommand shall be denied.

• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not{ENABLE, DISABLE}

• TTL = {1-255}. Time To Live used to identify the MIP where the LBM packet has to be sentback (node where the TTL expires)

• DISCOVERY = INGRESS EGRESS. It indicates if the ingress or egress MIP has to beaddressed in the discovery case this is in alternative to TARGET-MEPID or TARGET-MIPID;

Restrictions:

− If TARGET-MEPID=NOTARGET and TARGET-MIPID=NOTARGET then this parametermust 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 bedenied.

− If TARGET-MIPID<>NOTARGET then this parameter can't be entered.

7

Discovery loopback (TARGET = MIP)

Enter:

ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,TTL=][,TARGET-MIPID=]

[,DISCOVERY=];

where:

• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.

Remember: It is required that the TUSEG involved must have:

− DIR = BIDIR

− MEP = enable

− TYPE=TERMINATED

− OAM-TYPE=MPLS_TP

• TARGET-MEPID = NOTARGET.

Restrictions:

If TARGET-MIPID=NOTARGET and DISCOVERY=NODISCOVERY then this parameter mustbe 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.

Administer MPLS-TP Discovery Loopback OAM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

490 Issue 4

Page 491: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

If the entered LB-Tools already exists for the value pair (AID, TARGET-MEPID), then thecommand shall be denied.

• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not{ENABLE, DISABLE}

• TTL = {1-255}. Time To Live used to identify the MIP where the LBM packet has to be sentback (node where the TTL expires)

• TARGET-MIPID = NOTARGET.

Restrictions:

If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then this parametermust be entered with a valid MIP-NODEID and IF-NUM.

If TARGET-MEPID<>NOTARGET then this parameter can't be entered

If DISCOVERY<>NODISCOVERY then this parameter can't be entered.

If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,TARGET-MIPICC), then the command shall be denied.

• DISCOVERY = INGRESS, EGRESS. It indicates if the ingress or egress MIP has to beaddressed in the discovery case this is in alternative to TARGET-MEPID or TARGET-MIPID;

Restrictions:

− If &-grouping addressing is used then NODISCOVERY value can't be used together withINGRESS value.

− If &-grouping addressing is used then NODISCOVERY value can't be used together withEGRESS value

− If TARGET-MEPID=NOTARGET and TARGET-MIPID=NOTARGET then this parametermust 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 bedenied.

− 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 (DelayMeasurement) 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 receivesback DMR packets received from the symmetrical tool RDMT (i.e. from peer MEP point).

1850 TSS-320/TSS-320H/TSS-160 Administer (T-MPLS/MPLS-TP) DM tool

Release 5.1 (ETSI)September 2017Issue 4 4918DG09603CAAATQZZA

Page 492: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• RESPONDER DM-Tool. MEP point that sends back DMR packets when receives DMM packetsent 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 commandspecifying 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 packetsreceived.

• Stop OAM tools. OAM Tool doesn't send Packets.

Note: Command restriction: OAM tool referenced by this command must be previouslyentered trough ENT-TMPLS-<tool> command.

The DLT-TMPLS-OD2WAYDM command deletes On Demand OAM 2-Way DM (DelayMeasurement) 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 butnot this command.

When a SENDER DM-Tool is deleted then also its file containing Delay Measurement data will beerased.

The T-MPLS DM tool is available on demand. The T-MPLS DM tool is a T-MPLS OAM tool availablefor 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 <TUSEGwith MEP enabled, PHB>

When the transmission of T-MPLS DM is enabled on one <TUSEG, PHB> pair, automatically alsothe reception of DMR is enabled.

Upon reception of one DMR, NE shall check whether there is an active T-MPLS DM instance forthis 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 theDMR 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).

Administer (T-MPLS/MPLS-TP) DM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

492 Issue 4

Page 493: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 theSET 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 alsoduring the measurement (updated with defined periodicity)

When the DM instance is deleted using the DLT command, also the corresponding output file isdeleted.

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 isstopped

• when one or more parameters are edited or the measurement is stopped and restarted theassociated changes are written in the output file

8.6.4 Before you begin

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). Tochange to MPLS-TP refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration”(p. 504).

8.6.5 Procedure

1

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.

1850 TSS-320/TSS-320H/TSS-160 Administer (T-MPLS/MPLS-TP) DM tool

Release 5.1 (ETSI)September 2017Issue 4 4938DG09603CAAATQZZA

Page 494: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 packetsinterval 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 intervalends

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 andend-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-TYPEparameter value of ENT-TMPLS-TUSEG command. The minimum/default value is:

− 41 if OAM-TYPE=T-MPLS

− 45 if OAM-TYPE=MPLS-TPPKT-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”

Administer (T-MPLS/MPLS-TP) DM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

494 Issue 4

Page 495: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

If AID=ALL then the Operator will use TOOL parameters as filter to modulate commandbehavior.

Restrictions:If AID=ALL then the Operator must enter TOOL parameter. If AID<>ALL theTOOL parameter can't be entered.

• TOOL = OD2WAYDMS. With this parameter the Operator can chose the OAM Tool whenAID=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-NUMvalue 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 Demandtools.

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 haveDM-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 (seeRTRV-TMPLS-OD2WAYDM command). The chosen DM-PHB must be present into PHBprofile used by Terminated TMPLS Facility where the DM-Tool has been configured. Ifalready exists a tool defined on Terminated TMPLS Facility with chosen DM-PHB value thenthe command will be refused.

• PERIOD = Period for the transmission of DMM packets.

Restrictions: This parameter can be edited only if DM-TOOL-STATE=CONFIGURED (seeRTRV-TMPLS-OD2WAYDM command).

• SEND-PKT-NUM = Number of DMM packets to send.

Restrictions: This parameter can be edited only if DM-TOOL-STATE=CONFIGURED (seeRTRV-TMPLS-OD2WAYDM command). The System can send max 10.000 DMM packets forthis DM-Tool

• PKT-LENGTH = Length in byte of DMM packet to send.

Restrictions: This parameter can be edited only if DM-TOOL-STATE=CONFIGURED (seeRTRV-TMPLS-OD2WAYDM command).

• START-TIME = This parameter is used to establish when Sender DM-Tool starts to send

1850 TSS-320/TSS-320H/TSS-160 Administer (T-MPLS/MPLS-TP) DM tool

Release 5.1 (ETSI)September 2017Issue 4 4958DG09603CAAATQZZA

Page 496: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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.

Restrictions: This parameter can be edited only if DM-TOOL-STATE=CONFIGURED (seeRTRV-TMPLS-OD2WAYDM command). This parameter can't be entered together withSEND-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 sendpackets. The format is END-TIME=YY-MM-DD-hh-mm-ss. Warning: SEND-PKT-NUMparameter 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.

Restrictions: This parameter can be edited only if DM-TOOL-STATE=CONFIGURED (seeRTRV-TMPLS-OD2WAYDM command). This parameter can't be entered together withSEND-PKT-NUM parameter. If END-TIME is antecedent or equal to START-TIME then thecommand 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 andENABLED)

• 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 tooldefault = 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

Administer (T-MPLS/MPLS-TP) DM tool 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

496 Issue 4

Page 497: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 isnot 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 withACTION = ENABLE; the tool is actually not running because current time < START- TIME ornot 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 facilityprotection group.

8.7.2 Prerequisites

None.

8.7.3 General

The ENT-FFP-TMPLS command creates a facility protection group. The following types of facilityprotection group can be provisioned with (T)MPLS tunnels as protection group members with thiscommand:

• 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 AIDof the FFP will be returned as output.

Note: Command restriction: The System will refuse the ENT-FFP-TMPLS command if oneof the specified tunnel (WKG or PROTN) which should become member of the new FFP isalready a member of a TMPLS GROUP previously created with the ENT-TMPLS-GROUPcommand. The System will refuse the ENT-FFP-TMPLS command if at Board-Level thereservation of resources to be used for PW in case of protection switching to the ProtectingTunnel has as consequence the reaching of the maximum number of MPLS PW that can becreated on the card: there is a resources pool to be shared in general at NNI (for BIDIR oUNIDIR_OUT Tunnel and PW, <port,VLAN>).

The RTRV-FFP-TMPLS command retrieves provisioned parameter values, pertaining to thespecified FFP protection group. The RTRV-FFP-TMPLS command is executed regardless of thestate of the specified facility.

The RTRV-FFP-TMPLS command retrieves provisioned parameter values and the current switchingstate for all the provisioned facility protection groups.

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Facility Protection Group

Release 5.1 (ETSI)September 2017Issue 4 4978DG09603CAAATQZZA

Page 498: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

This command return also the Access Control Domain to know if the FFP has been createdmanually (by means this procedure) or via control plane (please refer to 8.15 “Administer T-MPLSTunnel” (p. 524)).

The ED-FFP-TMPLS command modifies the FFP protection group previously provisioned throughENT-FFP-TMPLS. It allows the user to change facility protection group attributes: Wait_To_Restoretime value and Hold-off timer value. Upon successful completion of ED-FFP-TMPLS, parameterchanges 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 ofthe DLT-FFP-TMPLS command, the protection group is deleted, and the working facilities that havebeen disassociated from facility protection function as unprotected facilities. In addition theprotection facility can be used again for normal unprotected traffic.

The RLS-PROTNSW-TMPLS command is used to clear a protection switch request on a TMPLSFFP group.

The OPR-PROTNSW-TMPLS command is used to initiate protection commands for provisionedfacility 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 SFcondition on the working or protection tunnel, or a forced switch request on the working orprotection 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 whichare present of the FFP group identified by the specified by the AID, and will honor the highestpriority request. This request may not have been honored earlier because of an earlier requestedhigher 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 theservice will be switched back to working.

8.7.4 Before you begin

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 alreadya member of another FFP protection group

• one of the specified tunnel which shall become member of the new FFP is not already a memberof a TMPLS GROUP created previously with the ENT-TMPLS-GROUP

Administer T-MPLS Facility Protection Group 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

498 Issue 4

Page 499: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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

Note: At node level the NE generates TMPLS OAM (the default value is T-MPLS). Tochange to MPLS-TP refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration”(p. 504).

8.7.5 Procedure

1

Select action.

To retrieve T-MPLS Facility Protection Group information, go to Step 2.

To create T-MPLS Facility Protection Group, go to Step 5.

To modify T-MPLS Facility Protection Group parameters, go to Step 7.

To delete T-MPLS Facility Protection Group, go to Step 9.

To initiate protection commands for provisioned T-MPLS Facility Protection Groups, go to Step10

To clear a protection switch request on a TMPLS FFP group, go to Step 11

To end this procedure, go to Step 12.

2

Retrieve T-MPLS Facility Protection Group information

Enter RTRV-FFP-TMPLS::AID:;

where: AID =Access identifier of the FFP to retrieve. Possible values: ALL or FFPTUNNEL-{1-7}-{1-9}-{1-4000} in the Rack, Shelf, FFP index, format.

3

Examine output for provisioning information, as detailed in the relevant command guide, refer to“Command details” (p. 107).

4

Go to Step 1.

5

Create T-MPLS Facility Protection Group

Enter ENT-FFP-TMPLS::::::WKG=,PROTN=[,LAYER=][,RVRTTIM=][,PTYPE=][,RVRT=][,HLDFFTTIM=][,APSPHB=][,FFP-ID=];

where:

• WKG = Access identifier of the working tunnel. Possible values: TUNNEL-{1-7}-{1-9}-{1-

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Facility Protection Group

Release 5.1 (ETSI)September 2017Issue 4 4998DG09603CAAATQZZA

Page 500: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

10000}-{0-65535}-{0-255}-{0-255}-{0-255}-{0-255}-{0-255}-{0-255}-{0-255}-{0-255} in theRack, Shelf, FFP Id, FFP Instance format.

Restriction: The Tunnel used as TUNNEL-WKG can’t be referenced by a TUSEG withADD-GROUP = TRUE. The bandwidth of the protecting tunnel should always be >= respectto the bandwidth of the protected tunnel If the working TUNNEL has STATUS=OFF then thecommand 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 theRack, Shelf, FFP Id, FFP Instance format.

Restriction: The Tunnel used as TUNNEL-PROTN can’t be referenced by a TUSEG withADD-GROUP = TRUE. The bandwidth of the protecting tunnel should always be >= respectto the bandwidth of the protected tunnel If the protecting TUNNEL has STATUS=OFF thenthe command shall be rejected.

• RVRT= Determines if the protection shall be revertive or not.

Y = Automatically reverts to working.

N = Doesn't revert automatically.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Go to Step 1.

7

Modify T-MPLS Facility Protection Group parameters

Enter ED-FFP-TMPLS::AID::::[RVRTTIM=][,HLDFFTTIM=][,APSPHB=][,FFP-ID=];

where:

• AID =Access identifier of the FFP to edit. Possible values: FFPTUNNEL-{1-7}-{1-9}-{1-4000}in the Rack, Shelf, FFP index, format.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

8

Go to Step 1.

9

WARNING

Optional Content

The deletion can only be executed against TUNNEL facilities that are provisioned as aprotection group (e.g., provisioned via the ENT-FFP-TMPLS command).

Delete T-MPLS Facility Protection Group

Administer T-MPLS Facility Protection Group 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

500 Issue 4

Page 501: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

10

To initiate protection commands for provisioned T-MPLS Facility Protection Groups

Enter OPR-PROTNSW-TMPLS::AID:::SWTCHCMD[,DESTINATION];

where:

• AID = Access identifier of the FFP to switch. Possible value: FFPTUNNEL-{1-7}-{1-9}-{1-4000} - TMPLS TUNNEL Protection Group

• SWTCHCMD={FRCD, LOCKOUT, MAN }

Default: Entry required Addressing: None Description: Switch Command to be performed.

− FRCD=Forced Switch: If the DESTINATION identifies the protection line, a Forced Switchto protection tunnel occurs. A Forced Switch to protection switches the specified channelto 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 fromswitching to the protection tunnel. If already switched to the protection side, a switch backto working occurs.

− MAN=Manual Switch: If the DESTINATION identifies the protection tunnel, a ManualSwitch to protecting tunnel occurs. A Manual Switch to protection switches the specified tothe protection tunnel unless a request of equal or higher priority is in effect. If theDESTINATION identifies the working tunnel, a Manual switch to working occurs. A ManualSwitch to working switches the specified channel back from the protection tunnel to theworking 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 protectionsection of the protection group.

Note: The following items have to be taken into account for protection states andcondition types:

• All WTR (Wait-To-Restore) values will only occur if revertive switching is supported andprovisioned at least on one end

• DNR (Do Not Revert) value will only occur if non-revertive switching is supported andprovisioned at least on one end.

11

To clear a protection switch request on a TMPLS FFP group

Enter RLS-PROTNSW-TMPLS::AID;

where:

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Facility Protection Group

Release 5.1 (ETSI)September 2017Issue 4 5018DG09603CAAATQZZA

Page 502: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

AID = FFPTUNNEL-{1-7}-{1-9}{1-4000}

Note: A clear command will clear only those externally initiated commands issued at thatnode. The clear command (i.e. RLS-PRONTSW) , will clear the WTR if the node is inWTR state.

12

STOP. This procedure is complete.

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 networkparameters 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 toT-MPLS by the ED-TMPLS-GLOBAL command.

8.8.4 Procedure

1

Select action.

To retrieve T-MPLS Global Network Parameters information, go to Step 2.

To modify T-MPLS Global Network Parameters, go to Step 5.

To end this procedure, go to Step 7.

2

Retrieve T-MPLS Global Network Parameters information

Enter RTRV-TMPLS-GLOBAL:::;

3

Examine output for provisioning information, as detailed in the relevant command guide, refer to“Command details” (p. 107).

Administer T-MPLS Global Network Parameters 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

502 Issue 4

Page 503: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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=];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Go to Step 1.

7

STOP. This procedure is complete.

END OF STEPS

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Global Network Parameters

Release 5.1 (ETSI)September 2017Issue 4 5038DG09603CAAATQZZA

Page 504: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 toT-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 ofthis NE parameter.

It is possible to change the OAM selection with Tunnel granularity, allowing for single Tunnel adifferent 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 bothT-MPLS and MPLS-TP OAM tools or of only the OAM tools configured for generation at Tunnellevel.

By default the behaviour that allows to receive and to process both T-MPLS and MPLS-TP isselected. A change of this configuration affects all the already created Tunnel Termination.

Administer T-MPLS/ MPLS-TP Node configuration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

504 Issue 4

Page 505: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

8.9.6

8.9.7 Procedure

1

Select action.

To retrieve T-MPLS OAM Packets type information, go to Step 2.

To modify OAM Packets type, go to Step 5.

To perform T-MPLS to MPLS-TP migration, go to Step 7.

To end this procedure, go to Step 10.

2

Retrieve T-MPLS Global Network Parameters information

Enter RTRV-TMPLS-GLOBAL:::;

3

Examine output for provisioning information, as detailed in the relevant command guide, refer to“Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS/ MPLS-TP Node configuration

Release 5.1 (ETSI)September 2017Issue 4 5058DG09603CAAATQZZA

Page 506: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 thedefault value assigned to the TUSegment OAM-TYPE parameter (if it is not specified by theOperator); therefore it is possible to change the OAM type with TUSegment granularity (seeOAM-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 isBOTH.

Possible values are:

BOTH T-MPLS and MPLS_TP. I.e. the receiver MEP accepts both “OAM T-MPLS packets”and “MPLS_TP OAM packets”.

Administer T-MPLS/ MPLS-TP Node configuration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

506 Issue 4

Page 507: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

TYPE-SEL OAM packets type selected by OAM-TYPE-SEL parameter. I.e. the receiver MEPaccepts only “OAM packets type” established by OAM-TYPE-SEL parameter value.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Go to Step 1.

7

The migration from T-MPLS to MPLS-TP can be done without interruption of the data traffic andwithout spurious alarms, using the T-MPLS/MPLS-TP OAM configurability at node and MEPlevels.

8

Set first the parameter (at node level) that allows receiving both T-MPLS and MPLS-TP OAMpackets, 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 fornode 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 MEPaccepts 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 continuesto be correctly received in termination nodes

10

STOP. This procedure is complete.

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).

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS OAM (T-MPLS Tunnel protection)

Release 5.1 (ETSI)September 2017Issue 4 5078DG09603CAAATQZZA

Page 508: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

8.10.2 Prerequisites

In order to enable the T-MPLS Tunnel protection, it is required to create the Protection Group (see8.7 “Administer T-MPLS Facility Protection Group” (p. 497)), constituted by a Protected (Main) Unitand a Protecting (Spare) Unit. It is requested that the two tunnels, that assume the role of Main Unitand Spare Unit, have been already created and activated (see 8.18 “Administer T-MPLS TunnelSegment Cross-Connection” (p. 535)).

PWs can be previously mapped only in the Tunnel that becomes the Protected one, the tunnel thatassumes 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-MPLSTunnel labels.

The two Tunnels have the same bandwidth, use the same PHB Profile and the same TrafficDescriptor.

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, togetherwith other information about the Protection Group configuration and status.

It is required that before creating the Protection Group, bidirectional MEPS are created andactivated 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 theCV 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-MPLSAPS OAM, in order to control protection switching operations and synchronize the actions at thetwo 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 ofthe 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 APSpackets.

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 theworking path again, in revertive mode of operation.

Administer T-MPLS OAM (T-MPLS Tunnel protection) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

508 Issue 4

Page 509: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 accordingto the direction of TUSegment. For a MEP sink point, it enables the capability to process thereceived 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 TUSegmentTermination (MEP_ID in T-MPLS CV OAM frame identifying the transmitting MEP). Thisparameter is unique inside MEG_ID.

EXPMEP-ID = (0-8191). Expected MEP values list, integer associated to Sink TUSegmentTermination, also called PeerMEP-ID. In case of p2p TUSegment, this is only one integernumber. 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 toSource TUSegment Term.

CVPERIOD= (3.33ms,10ms,100ms,1s,10s,20ms,50ms,1m,10m). Period (1/Frequency) of CVpacket 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,

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS OAM (T-MPLS Tunnel protection)

Release 5.1 (ETSI)September 2017Issue 4 5098DG09603CAAATQZZA

Page 510: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 see4.11 “ LER Tunnel Management (Tunnel Terminated)” (p. 81)

4

Create the bidirectional 1:1 (T)MPLS FFP of two tunnels (working and protection tunnel) withthe ENT-FFP-TMPLS command, for details see 8.7 “Administer T-MPLS Facility ProtectionGroup” (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 to4.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 Wireto be used on 1850 TSS-320, TSS-320H and TSS-160 product.

8.11.2 Prerequisites

PW creation can be performed only via Management Plane (static) (see 8.11 “Administer T-MPLSPseudo Wire” (p. 510) ).

At the first time it is necessary to create the MPLS port, and the traffic descriptor which must beassociated with the Pseudo Wire.To make operative the Pseudo Wire the ED-TMPLS-PWcommand must be used (with the TD and Status as ON).

8.11.3 General

The Pseudo Wire (PW) can be:

• Terminated

Administer T-MPLS Pseudo Wire 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

510 Issue 4

Page 511: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• Stitched (= swapped) in case of Multi-Segment PW

Via ENT-TMPLS-PWSEG providing as reference the Tunnel Segment Index or (in case of PWdirectly over physical link) the physical Interface Index a new entry is created (ifType =166). Thisentry 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 CACpurposes) 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.

To end this procedure, go to Step 11.

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Pseudo Wire

Release 5.1 (ETSI)September 2017Issue 4 5118DG09603CAAATQZZA

Page 512: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 relevantcommand 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

Administer T-MPLS Pseudo Wire 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

512 Issue 4

Page 513: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 aTUSegment. If the parameter refers to a port, it must be already provisioned. If the parameterrefers to a TUSegment, it must be already defined and TYPE must be equal toTERMINATION. Possible values: MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-10} for Local MPLSInterface or MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-128} for VCG MPLS Interface or TUSEG-{1-7}-{1-9}-{1-20000} for Tunnel Segment.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Go to Step 1.

7

NOTICE

Equipment damage hazard

Possibility of service interruption. Editing port parameters of a traffic bearing port can adverselyaffect 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 theRack, Shelf, PW index, format.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

8

Does Pseudo Wire Termination involved for point-to-point services?

If yes, erase services (For details, refer to 8DG09603EAAATQZZA — 1850 Transport ServiceSwitch (TSS-320, TSS-320H and TSS-160) Release 5.1 Command Line Interface Guide).

If no, go to Step 1.

9

Does Pseudo Wire Termination associated to VPLS?

If yes, erase services and VPLS facility (For details, refer to 8DG09603EAAATQZZA —1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 CommandLine Interface Guide

If no, go to Step 1.

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Pseudo Wire

Release 5.1 (ETSI)September 2017Issue 4 5138DG09603CAAATQZZA

Page 514: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

10

Does Pseudo Wire involved in PW swapping?

If yes, see 8.13 “Administer T-MPLS Pseudo Wire Segment Cross-Connection” (p. 517).

If no, go to Step 1.

11

Delete T-MPLS Pseudo Wire Segment

Does Pseudo Wire Segment is active?

If yes, see WARNING.

If no, go to Step 12.

12

Enter DLT-TMPLS-PW::AID;

where: AID = AID of PW that defines PW AID. Possible values: ALL or PW-{1-7}-{1-9}-{1-64000}in the Rack, Shelf, PW index, format.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Note: A pseudowire could be deleted only if its STATUS = OFF.

Result: After this command, all the corresponding PWSEG and CRSPWSEG are deleted.

13

STOP. This procedure is complete.

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 tobe used on 1850 TSS-320, TSS-320H and TSS-160 product.

8.12.2 Prerequisites

A Packet Card has to be created (see 6.67 “Provision Equipment” (p. 385) )

8.12.3 General

The ENT-TMPLS-PWSEG command creates a Pseudo Wire Segment.

Successful completion of this command generates automatically a Pseudo Wire only ifTYPE=TERMINATION. The PW parameters can be modified using ED-TMPLS-PW command. ThePW can be deleted using DLT-TMPLS-PW command.

Administer T-MPLS Pseudo Wire Segment 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

514 Issue 4

Page 515: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The RTRV-TMPLS-PWSEG command retrieves the provisioned parameters for MPLSPWSegments.

The ED-TMPLS-PWSEG command edits MPLS PWSegment parameters.

Table 28 PST usage rules depending on PWSegment current PST value

PWSEG PSTentered

PWSEG current PST

IS OOS-AU OOS-MA OOS-AUMA

IS Denied Denied IS OOS-AU

OOS OOS-MA OOS-AUMA Denied Denied

The RTRV-TMPLS-PWSEG command retrieves the provisioned parameters for MPLSPWSegments.

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 stillthe 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.

To end this procedure, go to Step 11.

2

RetrieveT-MPLS Pseudo Wire Segment information

Enter RTRV-TMPLS-PWSEG::[AID]:::[USERNAME];

where:

• AID = Access Identifier, specifies an access to the T-MPLS PWSegments entered. Thisparameter will be used when the User want retrieve complete list of PWSegments entered onthis LSR (AID=ALL) or a single PWSegment or a range of PWSegments. If the user uses thisparameter 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 ifUSERNAME parameter not provided.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Pseudo Wire Segment

Release 5.1 (ETSI)September 2017Issue 4 5158DG09603CAAATQZZA

Page 516: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

3

Examine output for provisioning information on Pseudo Wire Segment, as detailed in therelevant 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 aTUSegment. If the parameter refers to a port, it must be already provisioned. If the parameterrefers to a TUSegment, it must be already defined and TYPE must be equal toTERMINATION. Possible values: MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-10} for Local MPLSInterface 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.

Administer T-MPLS Pseudo Wire Segment 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

516 Issue 4

Page 517: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Go to Step 1.

7

Modify T-MPLS Pseudo Wire Segment

Enter ED-TMPLS-PWSEG::AID:::[PORT],[DIR],[USERNAME]: [L2ENCAPPROF-AID=]

[,INLABEL=][,OUTLABEL=][,PHBPROF-AID=] [,CW=];

where: AID = Access IDentifier, specifies an access to the facility. Possible values: PWSEG-{1-7}-{1-9}-{1-128000}.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

8

Go to Step 1.

9

Delete T-MPLS Pseudo Wire Segment

Does Pseudo Wire Segment involved in a cross-connection or in client services?

If yes, see WARNING.

If no, go to Step 10.

10

Enter DLT-TMPLS-PWSEG::AID:;

where: AID = Access IDentifier, specifies an access to the facility. Possible values: PWSEG-{1-7}-{1-9}-{1-128000}.

11

STOP. This procedure is complete.

END OF STEPS

8.13 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-connectentity and establishes a one-way, two-way cross-connection between the specified PWSegments.

8.13.2 Prerequisites

None.

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Pseudo Wire Segment Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 5178DG09603CAAATQZZA

Page 518: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 “AdministerT-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 followingTable 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.

Administer T-MPLS Pseudo Wire Segment Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

518 Issue 4

Page 519: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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.

To end this procedure, go to Step 11.

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 thecommand is directed. This parameter is used when the User want retrieve complete list ofPWSegment cross connections entered on this LSR (AID=ALL) or cross connections where thePWSegment, 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, asdetailed 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.

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Pseudo Wire Segment Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 5198DG09603CAAATQZZA

Page 520: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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. Thereferenced 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 referencedPWSegment must have TYPE=SWAP. Possible values: PWSEG-{1-7}-{1-9}-{1-128000}.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Go to Step 1.

7

Modify T-MPLS Pseudo Wire Segment Cross-Connection parameters

Enter ED-TMPLS-CRSPWSEG::FROM,TO:::CCT;

where:

• FROM = PWSegment AID, identifies the FROM entity of the cross-connection. Possiblevalues: 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 FROMand TO facility PWSegments.

Default value: previously existing value.

8

Go to Step 1.

9

WARNING

Optional Content

A pseudowire can be deleted only if its STATUS = OFF (see 8.11 “Administer T-MPLS PseudoWire” (p. 510)).

After this command, all the corresponding PWSEG and CRSPWSEG are deleted.

Administer T-MPLS Pseudo Wire Segment Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

520 Issue 4

Page 521: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Delete T-MPLS Pseudo Wire Segment Cross-Connection

Please refer to 8.11 “Administer T-MPLS Pseudo Wire” (p. 510) procedure to delete thePseudo Wire cross connection

10

STOP. This procedure is complete.

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 (TrafficDescriptor) also called MPLS Tunnel Resource Descriptor.

8.14.2 Prerequisites

None.

8.14.3 General

A TD can be associated:

• to Tunnels using the 8.15 “Administer T-MPLS Tunnel” (p. 524) procedure.

• to PseudoWires using 8.11 “Administer T-MPLS Pseudo Wire” (p. 510) procedure.

A TD is the a set of CIR, CBS, PIR and PBS parameters used by the System for bandwidth checksrelated to "port bit rate" or "Virtual Transport port bit rate" on which Tunnels/PseudoWires aredefined.

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 andoutput VT bandwidth. CBS and PBS values are used only for CAC checks with respect to thecorresponding 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 areinvolved 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.

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Traffic Descriptor

Release 5.1 (ETSI)September 2017Issue 4 5218DG09603CAAATQZZA

Page 522: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

To delete T-MPLS Traffic Descriptor, go to Step 10.

To end this procedure, go to Step 11.

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 therelevant command guide, refer to “Command details” (p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

"<AID>:: CIR=<value>,CBS=<value>,PIR=<value>,PBS=<value>,

INUSE=<value> cr lf

[

/*

<Command

Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

4

Go to Step 1.

Administer T-MPLS Traffic Descriptor 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

522 Issue 4

Page 523: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 andPseudoWires and it is a positive value. The CIR value must be <= of PIR value. If this TD isused by a Tunnel or by a PseudoWire, then CIR parameter value variation is constrained toverification of CAC checks. Possible values: <POSITIVE INTEGER> expressed in kbit/sec.

• CBS = MPLS Committed Burst Size. This parameter is valid for Tunnels and PseudoWiresand it is a positive value. The CBS value must be <= of PBS value. If this TD is used by aTunnel or by a PseudoWire, then CBS parameter value variation is constrained to verificationof CAC checks. Possible values: <POSITIVE INTEGER> expressed in byte.

• PIR = MPLS Peak Information Rate. This parameter is valid for Tunnels and PseudoWiresand it is a positive value. The PIR value must be >= of CIR value. If this TD is used by aTunnel or by a PseudoWire, then PIR parameter value variation is constrained to verificationof 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 isa positive value. The PBS value must be >= of CBS value. If this TD is used by a Tunnel orby a PseudoWire, then PBS parameter value variation is constrained to verification of CACchecks. Possible values: <POSITIVE INTEGER> expressed in byte.

6

Go to Step 1.

7

NOTICE

Optional Content

Possibility of service interruption. Editing port parameters of a traffic bearing port can adverselyaffect service.

If this TD is used by a Tunnel or by a PseudoWire, then CIR, PIR, CBS, PBS parameters valuevariation is constrained to verification of CAC checks.

Optional Content added above. Please modify as needed.

Modify T-MPLS Traffic Descriptor parameters

Enter ED-TMPLS-TD::AID::::[CIR=][,CBS=][,PIR=][,PBS=];

where: AID = Access Identifier, specifies an access Identifier to the MPLS TD. Possible values:MPLSTD-{1-10000}.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Traffic Descriptor

Release 5.1 (ETSI)September 2017Issue 4 5238DG09603CAAATQZZA

Page 524: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

8

Go to Step 1.

9

WARNING

Optional Content

The system is reject the command if TD is currently used (INUSE=YES) by a Tunnel or aPseudoWire

Optional Content added above. Please modify as needed.

Delete T-MPLS Traffic Descriptor

Does Traffic Descriptor in use?

If yes, see WARNING.

If no, go to Step 10.

10

Enter DLT-TMPLS-TD::AID:;

where: AID = Access Identifier, specifies an access Identifier to the MPLS TD. Possible values:MPLSTD-{1-10000}.

11

STOP. This procedure is complete.

END OF STEPS

8.15 Administer T-MPLS Tunnel

8.15.1 Purpose

This procedure provides the instructions to retrieve information, create, and delete an LSP tunnelbetween source and destination point.

8.15.2 Prerequisites

None.

8.15.3 General

The ENT-TMPLS-TUNNEL creates an LSP tunnel between source and destination point and usesextended RSVP-TE protocol for signaling. In the LSP Tunnel set-up, input parameters for LSPbandwidth 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))

Administer T-MPLS Tunnel 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

524 Issue 4

Page 525: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

As result of successful response, the Control Plane automatically assigns a TUNNEL AID outputparameter 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 thehighest value of the Tunnel Instance parameter (that is 2). The MEP (with default values) arecreated but it is needed anyway (via 8.17 “Administer T-MPLS Tunnel Segment” (p. 531) ) toconfigure 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 usedin a connection service. Path calculation allows user to know which will be the route before theservice is committed On the other hand, when service is active, operator can trigger calculation ofthe route without affecting actual path and check difference with the "computed" path, based onconstrains status at tunnel commit.

As output parameter, the command can return also the ACD (Access Control Domain) to know if thetunnel has been created manually (see 8.17 “Administer T-MPLS Tunnel Segment” (p. 531) and8.18 “Administer T-MPLS Tunnel Segment Cross-Connection” (p. 535) ) or via control plane (bymeans of this procedure).

The DLT-TMPLS-TUNNEL command removes a LSP Tunnel assigned by CP and by MP. Tunnelremoval is done with graceful deletion at source node. After this command, all the correspondingTUSEG and CRSTUSEG are deleted.

8.15.4 Procedure

1

Select action.

To retrieve T-MPLS Tunnel information, go to Step 2.

To create T-MPLS Tunnel, go to Step 5.

To modify T-MPLS Tunnel, go to Step 7.

To delete T-MPLS Tunnel, go to Step 9.

To end this procedure, go to Step 10.

2

Retrieve T-MPLS Tunnel information

Enter RTRV-TMPLS-TUNNEL::AID::::[TUNNEL-ID=][,ACD=][,SHOW-DETAILS=][,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. Defaultvalue: ALL

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Tunnel

Release 5.1 (ETSI)September 2017Issue 4 5258DG09603CAAATQZZA

Page 526: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

3

Examine output for provisioning information on tunnel, as detailed in the relevant commandguide, refer to “Command details” (p. 107).

Example: RTRV-TMPLS-TUNNEL::ALL::::SHOW-DETAILS=ALL;NE162BA 10-07-14 17:08:30 M 35 COMPLD

TUNNEL-1-1-1-2-20-0-0-10-20-0-0-13:TUNNEL-ID=,ACD=CP,DIR=BIDIR,TD-ID=

MPLSTD-1,SEGTO-AID=TUSEG-1-1-2,PROT-TYPE=FULL-REROUTE,LAYER=PSC,

SRC-ADDR=20-0-0-10,DEST-ADDR=20-0-0-13,INCL-ALL=0,INCL-ANY=0,EXCL-ANY=

0,ROLE=HEAD,PRIMARY-ID=2,SETUP-PRIO=7,HOLD-PRIO=0,DIVERSITY=SRLG,

RESTORED-HOPLIST=3,TOTAL-UP-TIME=17084,PRIMARY-UP-TIME=17084,

INSTANCE-UP-TIME=17084,PATH-CHANGES=0,LAST-PATH-CHANGE=0,

CREATION-TIME=10-07-14-17-00-30,STATE-CHANGES=1,STATUS=ON,STATE=UP

TUNNEL-1-1-1-2-20-0-0-10-20-0-0-13::HOP-IPADDR=20-0-0-11,HOP-UNNUM=

MPLSIF-1-1-16-3

4

Go to Step 1.

5

Create T-MPLS Tunnel information

Enter ENT-TMPLS-TUNNEL::::::TUNNEL-ID=[,DESCR=][,DIR=],TD-ID=[,HOPLIST-ID=][,PROT-TYPE=][,LAYER=][,SRC-ADDR=],DEST-ADDR=[,INCL-ALL=]

[,INCL-ANY=][,EXCL-ANY=][,REPLACE=][,STATUS=][,PHBPROF-AID=][,

REVERT-MODE=][,HOLD-PRIO=][,SETUP-PRIO=][,DIVERSITY=];

where:

• TUNNEL-ID = Tunnel Identifier assigned by user in the Control Plane. In case of protectedTunnel, the TUNNEL-ID parameter value for the BackUp-Tunnel will be assignedautomatically by the System. Possible values: <1-30 VALID NAME CHARACTERS>.

• TD-ID = Traffic Descriptor Identifier (assigned by user in the Control Plane). It definesbandwidth profile for the LSP tunnel. TD identifier can be recovered by means of the8.14 “Administer T-MPLS Traffic Descriptor” (p. 521) procedure. For Packet connection onlyPSC is supported. Command shall be rejected if matching TD could not be found. Possiblevalues: MPLSTD-{1-10000}.

for INNI connections

• SRC-ADDR = Source Node IP Address as originating point of the LSP Tunnel. It is the IPaddress 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 IPaddress of the Egress LER, used in TUNNEL AID output parameter. Possible values: {1-99,101-126,128-223} - {0-255} - {0-255} - {1-254}.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Administer T-MPLS Tunnel 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

526 Issue 4

Page 527: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6

Go to Step 1.

7

NOTICE

Optional Content

Possibility of service interruption. Editing port parameters of a traffic bearing port can adverselyaffect service.

Optional Content added above. Please modify as needed.

Modify T-MPLS Tunnel

Enter ED-TMPLS-TUNNEL::AID::::[TUNNEL-ID=][,DESCR=][,TD-ID=][,PROT-TYPE=][,STATUS=][,VT-HEAD=][,VT-TAIL=][,REVERT-MODE=];

where: AID = AID of LSP Tunnel that defines TUNNEL AID. Ingress LER address, Egress LERaddress. Possible values: TUNNEL-{1-7}-{1-9}-{1-10000}-{0-6553 5}-{0-255}-{0-255}-{0-255}-{0-255}-{0-25 5}-{0-255}-{0-255}-{0-255} in the Rack, Shelf, Tunnel Id, Tunnel Instance format.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Go to Step 1.

8

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 = ONreferencing this TUNNEL.

Optional Content added above. Please modify as needed.

Delete T-MPLS Tunnel

Does tunnel has active or protected?

If no, go to Step 9.

9

Enter DLT-TMPLS-TUNNEL::[AID];

where:

• AID = AID of LSP Tunnel that defines TUNNEL AID. It is made by six parameters: Rack,Subrack.Tunnel Id, Tunnel Instance, Ingress LER address, Egress LER address.

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Tunnel

Release 5.1 (ETSI)September 2017Issue 4 5278DG09603CAAATQZZA

Page 528: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

i.e. 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}

Note: This command will be refused when the Tunnel is active, when the tunnel isprotected.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

10

STOP. This procedure is complete.

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 bytwo already created Terminated Tunnels; one of the two Tunnel is called Working TUNNEL and theother is called Protecting TUNNEL.

This procedure provides the instructions to setup the bicast&merge functionality (specificallydeveloped to allow the "Single Node Ring Closure" in the TSS-320 / TSS-40 IWI scenarios).

8.16.2 Prerequisites

This functionality is available for Tunnels only, they can be unidirectional or bidirectional.

8.16.3 General

ENT-TMPLS-GROUP creates an association between two Terminated Tunnels. When the TYPE ofassociation is BICASTANDMERGE the bicast function is implemented in the OUT direction and themerge function is implemented in the IN direction - it is defined for Interworking scope of TSS-320with TSS-40, when “Single Node Ring Closure” and/or “Single Node Multi Ring Closure” feature isrequired.

Two Tunnels are associated; at the egress direction the traffic is bicasted, that is the same traffic issent on both Tunnels, at the ingress direction the traffic is received from two ports and the twoassociated Tunnels are merged, actually in this interworking application packets are received onlyfrom one port, one direction in normal condition, from the other direction in case of ring protectionactivated in another node of the network.

The functionality is implemented creating and configuring the TMPLS Tunnels Group, constituted bytwo already created Terminated Tunnels; one of the two Tunnel is called Working TUNNEL and theother 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 asprotecting has a specific characteristic, that is the possibility to share the ingress label with onenormal Tunnel. It is mandatory for the operator to provide this INLABEL to the Protecting TUSEG.

Administer TMPLS Tunnels Group 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

528 Issue 4

Page 529: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Furthermore the Protecting Tunnel has not the possibility to have PW attached or been used asprotecting 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 TunnelsGroup 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 thiscommand, the TMPLS Tunnels Group is deleted, and the working and protecting facilities remaindisassociated. The working tunnel can be used as a normal Tunnel, instead PW can’t be connectedto the protecting Tunnel, because it has the referenced TUSEG with ADD-GROUP = TRUE. Usingthe DLT-TMPLS-TUNNEL the two Tunnels can be deleted.

With regard to the OAM funcionality, the transmission of CV packets is unidirectional, in the egressdirection 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 isbicasted (CV_TX = ENABLE); these CV packets are received and processed by TSS40s in the ringfor alarm detection.

Whereas the reception of CV from the ring has to be disabled (CV_RX = DISABLE) in the TSS320implementing the Bicast&Merge and the transmission of CV packets has to be disabled in TSS40sin the ring.

8.16.4 Procedure

1

Select action.

To retrieve TMPLS Tunnels Group information, go to Step 2.

To create TMPLS Tunnels Group, go to Step 4.

To delete TMPLS Tunnels Group, go to Step 6.

To end this procedure, go to Step 7.

2

Retrieve TMPLS Tunnels Group information

Enter RTRV-TMPLS-GROUP::[AID];

where: AID = AID of Tunnels Group. Possible values: ALL or TUNNELGROUP-{1-7}-{1-9}-{1-4000}

The command returns the TUNNEL AIDs involved in the GROUP and the behavior Type of the"Tunnels Group".

1850 TSS-320/TSS-320H/TSS-160 Administer TMPLS Tunnels Group

Release 5.1 (ETSI)September 2017Issue 4 5298DG09603CAAATQZZA

Page 530: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 thesame of Tunnel Identifier chosen for TUNNEL-PROT. The Tunnel chosen must beTERMINATED, with ADD-GROUP = FALSE and its INLABEL must be equal to INLABEL ofthe Tunnel chosen as TUNNEL-PROT

• TUNNEL-PROT = Tunnel AID. .Restrictions: Tunnel Identifier for TUNNEL-PROT can't be thesame 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 asTUNNEL-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 areunidirectional, the traffic is bicasted if the correspondent TUSEG have DIR = UNIDIROUT,the traffic is merged if the correspondent TUSEG have DIR = UNIDIRIN

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

5

Go to Step 1.

6

Delete TMPLS Tunnels Group

Enter DLT-TMPLS-GROUP::AID;

where:

• AID = Possible values: ALL or TUNNELGROUP-{1-7}-{1-9}-{1-4000} (Tunnels Group)

7

STOP. This procedure is complete.

END OF STEPS

Administer TMPLS Tunnels Group 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

530 Issue 4

Page 531: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

8.17 Administer T-MPLS Tunnel Segment

8.17.1 Purpose

This procedure provides the instructions to retrieve information, create, and delete a TunnelSegment to be used on 1850 TSS-320, TSS-320H and TSS-160 product.

8.17.2 Prerequisites

A Packet Card has to be created (see 6.67 “Provision Equipment” (p. 385) )

8.17.3 General

The ENT-TMPLS-TUSEG command shall create a TUSegment to be used on 1850 TSS-320, TSS-320H and TSS-160 product.

Successful completion of this command generates automatically a TUNNEL only ifTYPE=TERMINATION. The TUNNEL parameters can be modified using ED-TMPLS-TUNNELcommand. 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 ifbandwidth 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 PSTentered

TUSEG current PST

IS OOS-AU OOS-MA OOS-AUMA

IS Denied Denied IS OOS-AU

OOS OOS-MA OOS-AUMA Denied Denied

The RTRV-TMPLS-PWSEG command retrieves the provisioned parameters for MPLSTUSegments.

The DLT-TMPLS-TUSEG command deletes the provisioned Swapped T-MPLS TUSegment entity.

Note: At node level the NE generates TMPLS OAM (the default value is T-MPLS). Tochange to MPLS-TP refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration”(p. 504).

8.17.4 Procedure

1

Select action.

To retrieve T-MPLS Tunnel Segment information, go to Step 2.

To create T-MPLS Tunnel Segment, go to Step 5.

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Tunnel Segment

Release 5.1 (ETSI)September 2017Issue 4 5318DG09603CAAATQZZA

Page 532: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 theUser want retrieve complete list of TUSegments entered on this LSR (AID=ALL) or a singleTUSegment or a range of TUSegments. If the user uses this parameter then he can't useUSERNAME parameter. Possible values: ALL or TUSEG-{1-7}-{1-9}-{1-20000} in the Rack,Shelf, TUSegment Id, format. Default value: ALL if USERNAME parameter not provided.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Examine output for provisioning information on Tunnel Wire Segment, as detailed in therelevant command guide, refer to “Command details” (p. 107).

Example: RTRV-TMPLS-TUSEG::TUSEG-1-1-10:TS002;ALU-01 03-07-19 09:08:33 M TS002 COMPLD

TUSEG-1-1-10: MPLSIF-1-1-2-4, TERMINATION, BIDIR,TESTUNNEL:

INLABEL=1024, OUTLABEL=10024, PHBPROF-AID=PHBPROF-1, OAMPHB-AID=

OAMPHB-2, MEP=ENABLE, MEG-ID=/"Rome-Milan/", MEP-ID=100, EXPMEP-ID=

200, CVRX=ENABLE, CVTX=ENABLE, CVPERIOD=10ms, CVPHB=EF, ACD=CP,

ALMPROF=tunnelasap-1, ADD-GROUP=FALSE, PS-DDM-SD=ENABLED,OAM-TYPE=

T-MPLS, PROSLMCVTX=DISABLE, PROSLMCVRX=DISABLE,PROLM-PLP=6,

PROLM-SD-CROSSTH=10, PROLM-SD-CLEARTH=10,PRODM=ENABLE, PRODM-PHB=EF,

PRODM-PERIOD=1m,PRODM-PKT-LENGTH=64,TCAPROF=tunneltcap-1,RDI-SD=

ENABLE:IS

4

Go to Step 1.

5

Create T-MPLS Tunnel Segment

Enter ENT-TMPLS-TUSEG:[TID]::[CTAG]::PORT,[TYPE],[DIR],[USERNAME]:[L2ENCAPPROF-AID=][,INLABEL=][,OUTLABEL=][,PHBPROF-AID=][,OAMPHB-AID=]

[,MEP=][,MEG-ID=][,MEP-ID=][,EXPMEP-ID=][,CVRX=][,CVTX=][,CVPERIOD=][,

CVPHB=][,ALMPROF=][,ADD-GROUP=][,PS-DDM-SD=][,OAM-TYPE=][,PROSLMCVTX=]

Administer T-MPLS Tunnel Segment 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

532 Issue 4

Page 533: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

[,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 referto a provisioned port. Possible values: MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-10} for Local MPLSInterface or MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-128} for VCG MPLS Interface.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Note: The maximum number of MPLS TUSegments that can be created at Board-Leveldepends on the available resources: there is a resources pool to be shared in general atNNI (for BIDIR o UNIDIR_OUT Tunnel and PW, <port, VLAN>).

6

Go to Step 1.

7

NOTICE

Optional Content

Possibility of service interruption. Editing port parameters of a traffic bearing port can adverselyaffect 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 PseudoWire Segment” (p. 514) ).

Optional Content added above. Please modify as needed.

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}.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Tunnel Segment

Release 5.1 (ETSI)September 2017Issue 4 5338DG09603CAAATQZZA

Page 534: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

8

Go to Step 1.

9

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 PseudoWire 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 = ONreferencing this TUNNEL.

For Termination TUSegment, the command will be refused because on TUSegment there is stillthe TUNNEL automatically generated (ref. to Step 5).

Optional Content added above. Please modify as needed.

Delete T-MPLS Tunnel Segment

Does Tunnel Segment involved in a cross-connection or referenced to PWSegment?

If yes, see WARNING.

If no, go to Step 10.

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-Toolsdefined on this TUSeg (see ENT-TMPLS-ODXXX commands and related) will be deleted

11

STOP. This procedure is complete.

END OF STEPS

Administer T-MPLS Tunnel Segment 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

534 Issue 4

Page 535: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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-connectentity and establishes a one-way, two-way cross-connection between the specified TUSegments.

8.18.2 Prerequisites

None.

8.18.3 General

The ENT-TMPLS-CRSTUSEG command creates a cross-connect entity and establishes a one-way,two-way cross-connection between the specified TUSegments.

Successful completion of this command generates automatically a TUNNEL (see 8.15 “AdministerT-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 followingTable 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

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Tunnel Segment Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 5358DG09603CAAATQZZA

Page 536: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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.

To end this procedure, go to Step 11.

2

Retrieve T-MPLS Tunnel Segment Cross-Connection information

Enter RTRV-TMPLS-CRSTUSEG::AID:;

where: AID =TUSegment AID, specifies the selected TUSegment facility to which the commandis directed. This parameter will be used when the User want retrieve complete list ofTUSegment cross connections entered on this LSR (AID=ALL) or cross connections where theTUSegment, 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 detailedin 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

Administer T-MPLS Tunnel Segment Cross-Connection 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

536 Issue 4

Page 537: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter ENT-TMPLS-CRSTUSEG::FROM,TO:::[CCT];

where:

• FROM = TUSegment AID, identifies the FROM entity of the cross-connection. The referencedTUSegment 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 referencedTUSegment must have TYPE=SWAP. Possible values: TUSEG-{1-7}-{1-9}-{1-20000}.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

Example: ENT-TMPLS-CRSTUSEG::TUSEG-1-1-10,TUSEG-1-1-20:TS001;ALU-01 03-07-19 09:08:33 M TS001 COMPLD

TUNNEL-AID=1-1-1-120-1-0-0-0-0-0-0-0-0

6

Go to Step 1.

7

WARNING

Optional Content

The System supports the PWSegment cross connections satisfying rules described into Table32, “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 hasSTATUS=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. Possiblevalues: 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 FROMand TO facility TUSegments.

8

Go to Step 1.

1850 TSS-320/TSS-320H/TSS-160 Administer T-MPLS Tunnel Segment Cross-Connection

Release 5.1 (ETSI)September 2017Issue 4 5378DG09603CAAATQZZA

Page 538: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

9

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 crossconnection.

10

STOP. This procedure is complete.

END OF STEPS

8.19 Proactive DM

8.19.1 Purpose

This procedure provides the instructions to configure, enable/disable the Proactive DM tool atTUSEG 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 ofDMM 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 enableboth 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 DMRpacket when the DMM one is received, is automatically present when a MEP is created on theTUSEG from this release onwards.

The parameter provided for the provisioning of both Proactive and On-Demand DMM tool for a<TUSEG, PHB> pair are:

Proactive DM 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

538 Issue 4

Page 539: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

the period for the generation of the DMM packets (1 sec, 10 sec, 1 minutes, 10 minutes). Thedefault 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 theDM PDU + ACH and GAL in MPLS-TP casegenerated DMM/DMR packets; also a random length(between 64 45 and 1500 bytes) option (with single polynomial algorithm TBC) is supported

Note: At node level the NE generates TMPLS OAM (the default value is T-MPLS). Tochange to MPLS-TP refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration”(p. 504).

8.19.3 Before you begin

Terminated Tunnels can be created with Proactive DM enabled or can be created without DMoptions 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 countersare 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 notretrievable)

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 beused when the User want retrieve complete list of TUSegments entered on this LSR (AID=ALL)or a single TUSegment or a range of TUSegments.

1850 TSS-320/TSS-320H/TSS-160 Proactive DM

Release 5.1 (ETSI)September 2017Issue 4 5398DG09603CAAATQZZA

Page 540: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Examine output as detailed in the relevant command guide, refer to “Command details”(p. 107).

4

If no Proactive DM parameters have been configured on the tunnel, first change the tunneladministrative 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 ifPW 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 thecommand will be refused.If STATUS=ON and ACD=LOCAL and OUTLABEL of correspondent TUSEG is notentered 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 theTUSegment facility.

• MEP = ENABLE, DISABLE.

For enabling MEP function (only for termination TUSegment), the direction of MEP isaccording to the direction of TUSegment. For a MEP sink point, it enables the capability toprocess the received CV packets and generate the correspondent alarms.

• MEG-ID= MEG, 13 ASCII chars string.

Proactive DM 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

540 Issue 4

Page 541: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• ,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 TUSegmentTermination, also called PeerMEP-ID. In case of p2p TUSegment, this is only one integernumber. In case of p2mp TUSegment, this parameter represents the list of expected MEP-ID.

• CVPERIOD{0.1ms,0.5ms,1ms,3.33ms,10ms,20ms, 50ms,100ms,1s,10s,1m,10m}. Period(1/Frequency) of CV packet transmission

• OAM-TYPE = OAM Packets type. Values are: T-MPLS MPLS_TP.

• PRODM = {ENABLE/DISABLE}. Enabling/disabling proactive delay measurement overTUSEG.

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 morethan 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 randomlength between 41 and 1500 byte.

The allowed minimum value and the default value of this parameter is related to OAM-TYPEparameter value of ENT-TMPLS-TUSEG command.

The minimum/default value is:

41 if OAM-TYPE=T-MPLS

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Change the tunnel administrative status to ON. Enter:

ED-TMPLS-TUNNEL::AID::::STATUS=ON;

where:

AID = TUNNEL-{1-7}-{1-9}-{1-10000}-{0-6553 5}-{0-255}-{0-255}-{0-255}-{0-255}-{0-25 5}-{0-255}-{0-255}-{0-255}.

AID of LSP Tunnel that defines TUNNEL AID. The former is made by six parameters: Rack,Subrack, Tunnel Index, Tunnel Instance, Ingress LER address, Egress LER address.

Note: STATUS indicates the Tunnel administrative status.

• ON: The Tunnel is committed to carrying traffic.

• OFF: The Tunnel is not committed to carrying traffic.

7

To enable/freeze/disable the PM data collection for the facility

1850 TSS-320/TSS-320H/TSS-160 Proactive DM

Release 5.1 (ETSI)September 2017Issue 4 5418DG09603CAAATQZZA

Page 542: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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. Currentdata and History data are retrievable.

− OFF PM collection for all MONTYPE is disabled. Current data and History data areretrievable.

− DISABLED PM collection for all MONTYPE is disabled. Current data and History data arenot retrievable.

At facility creation default value for PM collection is DISABLED.

When PMSTATE changes from ON to DISABLED, counters are not retrievable becauseresources are released.

When PMSTATE changes from ON to OFF, collection is stopped but counters areretrievable.

When PMSTATE changes from OFF to ON, counters are cleared (0) and collection startsagain.

When PMSTATE changes from OFF to DISABLE, counters are not retrievable becauseresources are released.

When PMSTATE changes from DISABLE to OFF (or ON) , counters resources areallocated 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 thencollection is stopped and counters resource are released.

Note: PM can be enabled for DM only if the proactive DM tool has been enabled for theassociated termination (for TUSEG only in Rel 4.0)

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

8

To verify the settings done in the step before, enter

RTRV-TMPLSPM-PRODM::AID::::[MONTYPE=][,MONLEV=][,TMPER=] [,MONDAT=][,

MONTM=][,NUMMIN=][,NUMDAY=][,LOCN=];

where:

AID = ALL (All facilities with OAM DM enabled) or TUSEG-{1-7}-{1-9}-{1-20000} (TunnelSegment)

This command retrieves the current 15-minute and/or 1-day PM data corresponding to the PMdata collection register(s) selected for the specified facility.

Proactive DM 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

542 Issue 4

Page 543: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

9

To reset PM collection register to zero value for the near-end/far-end side pertaining to thefacility 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} (TunnelSegment).

11

STOP. This procedure is complete.

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 atTUSEG 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/CCMpacket to “1”. The position of the LM Mode bit in the reserved bits of the Flags in the CV/CCMpacket 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

1850 TSS-320/TSS-320H/TSS-160 Proactive LM (Synthetic Loss Measurement)

Release 5.1 (ETSI)September 2017Issue 4 5438DG09603CAAATQZZA

Page 544: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 theTUSEG related to that Tunnel. It is necessary to disable the tool and then it is possible to deletethe Tunnel.

The activation of Connectivity Verification only or Connectivity Verification and Synthetic LossMeasurement functionalities have to be done considering two different parameters in the TL1commands:

• 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 thesame 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 theassociated 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 or1 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 or10 min.

Note: At node level the NE generates TMPLS OAM (the default value is T-MPLS). Tochange to MPLS-TP refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration”(p. 504).

8.20.4 Before you begin

Terminated Tunnels can be created with Proactive LM (SLM) enabled or can be created withoutSLM 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 countersare 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 notretrievable)

Proactive LM (Synthetic Loss Measurement) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

544 Issue 4

Page 545: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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

Examine output as detailed in the relevant command guide, refer to “Command details”(p. 107).

4

Enter:

ED-TMPLS-GLOBAL::::::[OAM-CVPERIOD-SEL=][,PHB-RANGE-SEL=][,

OAM-TYPE-SEL=][,OAM-RX-DETECT=][,CHANNEL-TYPE=][,PROLM-MODE-BIT=];

where:

• OAM-CVPERIOD-SEL = Selector of values range for CV Period into OAM CV frames. Thedefault value for this parameter is 4.

• OAM-TYPE-SEL= T-MPLS, MPLS_TP.

General default value for all TUSEG in the NE default = T-MPLS.

Then it is possible to change the OAM selection with TUSEG granularity (see TUSEGcommand).

• OAM-RX-DETECT = General selection for OAM packets detection. The default value isBOTH.

• 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 LMMode. 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.

1850 TSS-320/TSS-320H/TSS-160 Proactive LM (Synthetic Loss Measurement)

Release 5.1 (ETSI)September 2017Issue 4 5458DG09603CAAATQZZA

Page 546: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

6

Enable/disable the SLM functionality

Enter:

RTRV-TMPLS-TUSEG::[AID]:::[USERNAME];

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

7

Examine output as detailed in the relevant command guide, refer to “Command details”(p. 107).

8

If no Proactive LM parameters have been configured on the tunnel, first change the tunneladministrative 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 ifPW 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 thecommand will be refused.If STATUS=ON and ACD=LOCAL and OUTLABEL of correspondent TUSEG is notentered 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 theTUSegment facility.

• MEP = ENABLE, DISABLE.

Proactive LM (Synthetic Loss Measurement) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

546 Issue 4

Page 547: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

For enabling MEP function (only for termination TUSegment), the direction of MEP isaccording to the direction of TUSegment. For a MEP sink point, it enables the capability toprocess 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 TUSegmentTermination, also called PeerMEP-ID. In case of p2p TUSegment, this is only one integernumber. In case of p2mp TUSegment, this parameter represents the list of expected MEP-ID.

• CVPERIOD{0.1ms,0.5ms,1ms,3.33ms,10ms,20ms, 50ms,100ms,1s,10s,1m,10m}. Period(1/Frequency) of CV packet transmission

• PROSLMCVTX = {ENABLE/DISABLE}

Enabling/disabling proactive loss measurement and connectivity verification over TUSEG.

Enable Proactive CVTX + SLM functionality in Tx direction LM-Mode bit is set to 1 forTransmitted 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 forReceived CV packets(synthetic LM)

• PROLM-PLP = {4,5,6,7,8,9}. Proactive LM Packet Loss Probability. Six values are defined inthe 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 Degradedetected on the TUSEG using SLM tool. This parameter is meaningful for a terminatedTUSEG with MEP = ENABLE and PROSLMCVTX=ENABLE and PROSLMCVTX=ENABLE.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

10

Note: PROSLMCVTX and PROSLMCVRX parameter are used to enable both Synthetic LossMeasurement 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 CVor PROSLMCV are enabled

• in order to enable the dual-ended SLM functionality both PROSLMCVTX andPROSLMCVRX should be ENABLE

1850 TSS-320/TSS-320H/TSS-160 Proactive LM (Synthetic Loss Measurement)

Release 5.1 (ETSI)September 2017Issue 4 5478DG09603CAAATQZZA

Page 548: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• in order to activate the SLM and associated CV functionality the recommendedsequence 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 bothPROSLMCVTX and PROSLMCVRX in the other MEP, at the end enable alsoPROSLMCVRX in the first mentioned MEP.If the CV function was previous active, it is necessary first to disable it and then toenable the SLMCV function

Note: Note: the 0.1ms, 0.5ms, 1ms are CV PERIOD values accepted only for enabledSLM tool (when PROSLMCVTX = ENABLE or PROSLMCVRX = ENABLE)

11

Change the tunnel administrative status to ON. Enter:

ED-TMPLS-TUNNEL::AID::::STATUS=ON;

where:

AID = TUNNEL-{1-7}-{1-9}-{1-10000}-{0-6553 5}-{0-255}-{0-255}-{0-255}-{0-255}-{0-25 5}-{0-255}-{0-255}-{0-255}.

AID of LSP Tunnel that defines TUNNEL AID. The former is made by six parameters: Rack,Subrack, Tunnel Index, Tunnel Instance, Ingress LER address, Egress LER address.

Note: STATUS indicates the Tunnel administrative status.

• ON: The Tunnel is committed to carrying traffic.

• OFF: The Tunnel is not committed to carrying traffic.

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. Currentdata and History data are retrievable.

− OFF PM collection for all MONTYPE is disabled. Current data and History data areretrievable.

− DISABLED PM collection for all MONTYPE is disabled. Current data and History data arenot retrievable.

At facility creation default value for PM collection is DISABLED.

Proactive LM (Synthetic Loss Measurement) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

548 Issue 4

Page 549: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

When PMSTATE changes from ON to DISABLED, counters are not retrievable becauseresources are released.

When PMSTATE changes from ON to OFF, collection is stopped but counters areretrievable.

When PMSTATE changes from OFF to ON, counters are cleared (0) and collection startsagain.

When PMSTATE changes from OFF to DISABLE, counters are not retrievable becauseresources are released.

When PMSTATE changes from DISABLE to OFF (or ON) , counters resources areallocated 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 thencollection is stopped and counters resource are released.

Note: PM can be enabled for SLM only if the proactive LM tool has been enabled for theassociated termination (for TUSEG only in Rel 4.0)

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

13

To verify the settings done in the step before, enter

RTRV-TMPLSPM-PROLM::AID::::[MONTYPE=][,MONLEV=][,TMPER=] [,MONDAT=][,

MONTM=][,NUMMIN=][,NUMDAY=][,LOCN=];

where:

AID = ALL (All facilities with OAM LM enabled) or TUSEG-{1-7}-{1-9}-{1-20000} (TunnelSegment)

This command retrieves the current 15-minute and/or 1-day PM data corresponding to the PMdata collection register(s) selected for the specified facility.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

14

To reset PM collection register to zero value for the near-end/far-end side pertaining to thefacility 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:

1850 TSS-320/TSS-320H/TSS-160 Proactive LM (Synthetic Loss Measurement)

Release 5.1 (ETSI)September 2017Issue 4 5498DG09603CAAATQZZA

Page 550: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

RTRV-PMMODE-PROLM::AID::::[TMPER=][,LOCN=];

where:

AID = ALL (All facilities with OAM tool enabled) TUSEG-{1-7}-{1-9}-{1-20000} (TunnelSegment).

16

STOP. This procedure is complete.

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.

8.21.2 Prerequisites

The System supports only the initial value 0 to be set in the cleared counters.

8.21.3 General

PM commands operate only on provisioned ports.

PM commands are used to monitor defect conditions, and can be used to track system efficiency.By tracking efficiency, users can recognize gradual deterioration of system performance.

RTRV-TMPLSPM-<SEG> retrieves the current 15-minute (60-minute) and/or 1-day PM datacorresponding 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 current1-Day (specified by TMPER parameter) PM collection register (counters) for the near-end sidepertaining to the specified Segment. The historical counters aren't cleared.

8.21.4 Procedure

1

Select action.

To retrieve PM data, go to Step 2.

To initialize PM data collection register, go to Step 5.

To end this procedure, go to Step 7.

2

Retrieve PM Data

Report Performance Monitoring (PM) Data for T-MPLS 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

550 Issue 4

Page 551: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 (tunnelsegment)

• AID = Access Identifier, identifies the entity access identifier. Possible values:− ALL (all AID)

− PWSEG-{1-7}-{1-9}-{1-128000} (Pseudowire Segment)

− TUSEG-{1-7}-{1-9}-{1-20000} (Tunnel Segment)

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

3

Examine output for PM information, as detailed in the relevant command guide, refer to“Command details” (p. 107).

cr lf lf

<SID>

<YY-MM-DD>

<HH:MM:SS> cr lf

M

<CTAG>

COMPLD cr lf

[

"<AID>:<PMSTATE>[,<MONTYPE>,<MONVAL>,<VLDTY>,<TMPER>,<MONDAT>,

<MONTM>]" cr lf]

[

/*

<Command_Echo>

[<CTAG>]

(<Session_Number>)

*/ cr lf]

;

4

Go to Step 1.

1850 TSS-320/TSS-320H/TSS-160 Report Performance Monitoring (PM) Data for T-MPLS

Release 5.1 (ETSI)September 2017Issue 4 5518DG09603CAAATQZZA

Page 552: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

5

Initialize PM Data Collection Register

Enter INIT-TMPLSPM-<SEG>::AID::::[MONTYPE=][,TMPER=];

where:

• SEG= identifies the type of segment. PWSEG (pseudo wire segment) or TUSEG (tunnelsegment)

• AID = Access Identifier, identifies the entity access identifier. Possible value:− PWSEG-{1-7}-{1-9}-{1-128000} (Pseudowire Segment)

− TUSEG-{1-7}-{1-9}-{1-20000} (Tunnel Segment)

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

6

Go to Step 1.

7

STOP. This procedure is complete.

END OF STEPS

8.22 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.

8.22.2 Prerequisites

None.

8.22.3 General

The SET-TMPLSPM-<SEG> command enables/freezes/disables the PM data collection for thePseudoWire 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 allcounters 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 resourceare released.

In the following table are reported all the counters foreseen for <SEG> facility.

Set Performance Monitoring (PM) Data for T-MPLS 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

552 Issue 4

Page 553: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 tothe PM data collection register(s) selected for the specified facility.

The successful response for this command contains lines of parsable output data for eachprovisioned AID specified. No output data is provided if the <SEG> is not provisioned or if PMcounters aren't started (PMSTATE=DISABLED) No output data is provided if the date and timespecified exceeds the available collection periods (i.e., exceeds 8 hours of 15-minute PM registersor 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 thespecified <SEG> facility.

If AID=ALL is specified, all the (enabled) <SEG> PM counters residing in the NE should bereturned.

For each monitored counter, the current and/or up to thirty-two (32) 15-minute historical PMregisters, or the current and/or up to seven (7) 1-day historical PM registers or both 15-minute and1-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 PMregisters 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) procedurein order to retrieve the Performance Monitoring data collection for the PseudoWire or TunnelSegment facility.

2

Examine output to determine current PM mode, as referred in 8.21 “Report PerformanceMonitoring (PM) Data for T-MPLS” (p. 550) procedure.

1850 TSS-320/TSS-320H/TSS-160 Set Performance Monitoring (PM) Data for T-MPLS

Release 5.1 (ETSI)September 2017Issue 4 5538DG09603CAAATQZZA

Page 554: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

3

Enter SET-TMPLSPM-<SEG>::AID:::[PMSTATE]:[TMPER=];

where:

• SEG= identifies the type of segment. PWSEG (pseudo wire segment) or TUSEG (tunnelsegment)

• AID = Access Identifier, identifies the entity access identifier. Possible value:− PWSEG-{1-7}-{1-9}-{1-128000} (Pseudowire Segment)

− TUSEG-{1-7}-{1-9}-{1-20000} (Tunnel Segment)

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will use the default value, refer to “Command details” (p. 107).

4

STOP. This procedure is complete.

END OF STEPS

Set Performance Monitoring (PM) Data for T-MPLS 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

554 Issue 4

Page 555: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

9 1662 Drop Shelf Detailed Level Procedure

9.1 Overview

9.1.1 Purpose

The Detailed Level Procedures (DLP) contains detailed steps and supporting information requiredto 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 integratedPDH 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 between1662SMC E1 and UGW E1.

In the 1850TSS-320 the E1 access has been integrated by managing a 1662SMC drop shelf (withthe 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 providemanagement access from main shelf to drop shelf.

1850 TSS-320/TSS-320H/TSS-160 1662 Drop Shelf Detailed Level Procedure

Release 5.1 (ETSI)September 2017Issue 4 5558DG09603CAAATQZZA

Page 556: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 companionaccess 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.

1662SMC Drop Shelf Overview 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

556 Issue 4

Page 557: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

9.2.4 1850TSS equipping rules

The connection between 1850TSS-320 main shelf and 1662SMC drop shelf is provided with STM-4lines.

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 orinside 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.

1850 TSS-320/TSS-320H/TSS-160 1662SMC Drop Shelf Overview

Release 5.1 (ETSI)September 2017Issue 4 5578DG09603CAAATQZZA

Page 558: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

9.2.5 Shelf creation

As a precondition, the REGION parameter should be equal to ETSI then the Drop Shelf should becreated 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 creationand 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 shelfmanagement 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}

1662SMC Drop Shelf Overview 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

558 Issue 4

Page 559: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• Optical Mod synth4 ProvisionedType: OPTMODSS41

On creation of Drop Shelf and so of MTSYNTH4, the following Facilities and Connections areautocreated

• 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 dropshelf.

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 thepointed 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 ofrows, one for each PROVISIONEDTYPE value located in the immediate Lower level AID that isUnprovisioned.

The RTRV-EQPT command addressed to a Drop Shelf retrieves all the provisioned equipmentinformation related to the same shelf (e.g. the Shelf Type) and to the Equipment Entitiesprovisioned in it.

The RTRV-RI command addressed to a Drop Shelf retrieves all the provisioned equipmentinformation related to the same shelf (e.g. the Shelf Type) and to the Equipment Entitiesprovisioned in it.

1850 TSS-320/TSS-320H/TSS-160 1662SMC drop shelf management

Release 5.1 (ETSI)September 2017Issue 4 5598DG09603CAAATQZZA

Page 560: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 allthe IOC (eg.E1M) slots to/from the matrix (eg MSYNTH4) slots.

9.3.3 Before you begin

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

1

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 informationrelated to the same shelf (e.g. the Shelf Type) and to the Equipment Entities provisioned in it.

4

Modify the 1662 subshelf

1662SMC drop shelf management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

560 Issue 4

Page 561: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter:

ED-EQPT::AID::::[,ALMPROF=]:[PST];

where:

• AID = 1662 subshelf. Access Identifier

• ALMPROF = The Alarm Severity Assignement profile (ASAP) name to use with thisequipment 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 parametersediting is denied

For parameter descriptions of TL1 commands used in this procedure, refer to the .

5

Delete the 1662 subshelf

Enter:

RTRV-EQPT::SHELF-1-2;

6

The specified equipment entity must be in an OOS-[AU]MA state.

If not enter the remove command:

RMV-EQPT::SHELF-1-2;

7

Enter:

RTRV-EQPT::SHELF-1-2;

Result: The specified equipment entity state changed in OOS-[AU]MA state.

8

Deprovision the shelf using the following command:

DLT-EQPT::SHELF-1-2;

END OF STEPS

9.4 Administer 1662 Subshelf E1 cards

9.4.1 Purpose

Use this procedure to administer the following cards:

• 63 E1 Port Card

• 63 E1 Access Card (75 vs 120 ohm)

1850 TSS-320/TSS-320H/TSS-160 Administer 1662 Subshelf E1 cards

Release 5.1 (ETSI)September 2017Issue 4 5618DG09603CAAATQZZA

Page 562: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 63 E1 Protection Card

9.4.2 Procedure

1

Select action

• To create E1 port module E1M, go to Step 2.

To delete E1 port module E1M, go to Step 3.

• create E1 protection module E1PR, go to Step 4.

To delete E1 protection module E1PR, go to Step 5.

• create E1 access module E1ACC, go to Step 6

To delete E1 access module E1ACC, go to Step 7.

• Create a pair of E1M and E1ACC module, go to Step 8

• Create a pair of E1PR and E1ACC module, go to Step 9

2

E1 port module E1M creation

Enter:

ENT-EQPT::AID::::[PROVISIONEDTYPE=][,AINSMODE=][,ALMPROF=][,SSBIT=]:

[PST];

where:

• AID = E1M-{1-7}-{2}-{7-14} ETSI (63 E1 Multiplexer Card).

I.e. The Equipment Access Identifier, identifies the equipment entity access identifier

• PROVISIONEDTYPE = P63E1 ETSI 63 x E1 Port Module.

No other Autocreation is implied.

For parameter descriptions of TL1 commands used in this procedure, refer to the .

3

E1 port module E1M deletion

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).

I.e. The Equipment Access Identifier, identifies the equipment entity access identifier

4

E1 protection module E1PR creation

Administer 1662 Subshelf E1 cards 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

562 Issue 4

Page 563: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter:

ENT-EQPT::AID::::[PROVISIONEDTYPE=][,AINSMODE=][,ALMPROF=][,SSBIT=]:

[PST];

where:

• AID = E1PR-{1-7}-{2}-{2,19} ETSI (63 E1 EPS Card)

I.e. The Equipment Access Identifier, identifies the equipment entity access identifier

• PROVISIONEDTYPE = LSPROT - ETSI 63 x E1 Access Protection Module

No other Autocreation is implied.

5

E1 protection module E1PR deletion

Note: The specified equipment entity must be in an OOS-[AU]MA state.

Enter:

DLT-EQPT::AID;

where:

• AID = E1PR-{1-7}-{2}-{2,19} ETSI (63 E1 EPS Card)

I.e. The Equipment Access Identifier, identifies the equipment entity access identifier

6

E1 access module E1ACC creation

Enter:

ENT-EQPT::AID::::[PROVISIONEDTYPE=][,AINSMODE=][,ALMPROF=][,SSBIT=]:

[PST];

where:

• AID = E1ACC-{1-7}-{2}-{3-5,16-18} ETSI (63 E1 Access Card)

I.e. The Equipment Access Identifier, identifies the equipment entity access identifier

• PROVISIONEDTYPE = A63E1A/A63E1B: i.e. ETSI 63 x E1 Access Module 75ohm unb/ETSI 63 x E1 Access Module 120ohm bal

No other Autocreation is implied.

7

E1 access module E1ACC deletion

Note: The specified equipment entity must be in an OOS-[AU]MA state.

Enter:

1850 TSS-320/TSS-320H/TSS-160 Administer 1662 Subshelf E1 cards

Release 5.1 (ETSI)September 2017Issue 4 5638DG09603CAAATQZZA

Page 564: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

DLT-EQPT::AID;

where:

• AID = E1ACC-{1-7}-{2}-{3-5,16-18} ETSI (63 E1 Access Card)

I.e. The Equipment Access Identifier, identifies the equipment entity access identifier

8

Create a pair of E1M and E1ACC module

Provision 63XE1 module on 1662 subshelf and its companion access module in working slots.

As soon as a pair E1M-E1ACC is created with ENT-EQPT, also all the related (fixed)connections are created (i.e. 2WAY connections from VC12 on E1M-E1ACC to TU12 onSYNTH).

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 EPSgroup 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 the1662 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 correspondingSTM4AU4 facility, i.e. six 2-WAY crossconnections are created.

1662 Subshelf Facilities Overview 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

564 Issue 4

Page 565: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

When the subshelf is deleted all the above mentioned facilities, FFPS and crossconnections areautomatically deleted.

Six PTF instances of MODVC4 are automatically created/deleted on a 1662 subshelf when theshelf is provisioned. These MODVC4s have limited fixed capabilities and are always terminated in63 TU12s.

63 instances of PDHLOVC12 are automatically creted/deleted on a 1662 sub shelf whenever a63xE1 module is provisioned. These facilities have limited fixed capabilities and are alwaysterminated 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 viaautoprovisioning.

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 theside received from the internal TDM matrix/cross-connect and Ingress side is always received fromthe physical port or packet source

For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 TransportService Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.

1850 TSS-320/TSS-320H/TSS-160 1662 Subshelf Facilities Administration

Release 5.1 (ETSI)September 2017Issue 4 5658DG09603CAAATQZZA

Page 566: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

9.6.3 Procedure

1

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;

1662 Subshelf Facilities Administration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

566 Issue 4

Page 567: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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.

Possible values are:

• 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 Accessshelf 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 shelfE1 Port Module

• PDHLOVC12-{1-7}-{1-9}-{1-6}-{1-42} - VC12 with E1 client on the PDH Port Module of 1646shelf

Above are present only the AU4 editable parameters.

7

Enter:

RTRV-PTF::AID::::PTFTYPE=,PTFRATE=[,PARMS=][,TRCFMT=];

AID = PTF Access Identifier, specifies the PTF facility.

Possible values are:

• 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 Accessshelf 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:

1850 TSS-320/TSS-320H/TSS-160 1662 Subshelf Facilities Administration

Release 5.1 (ETSI)September 2017Issue 4 5678DG09603CAAATQZZA

Page 568: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

AID = MVC4TU12-{1-7}-{2}-{6}-{1-6}-{1-3}-{1- 7}-{1-3} (TU12 within a MVC4 on SYNTH4module 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 1646Drop shelf.

Above are present only the AU4 editable parameters.

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 SYNTH4module on a 1662 PDH access shelf).

Result: Ouput retrievable parameters are: AINSTIMER, MGRACD.

10

Manage 1662 subshelf E1 facilities

Enter:

ED-E1::AID::::[AINSTH=][,CMDMDE=][,ALMPROF=]:[PST],[SST];

where:

AID = E1-{1-7}-{2}-{8-10, 11-13}-{1-63} (E1 on the PDH Access shelf E1 Port Module)

E1-{1-7}-{1-9}-{1-6}-{1-42} - E1 on the PDH Port Module of 1646 shelf

Above are present only the AU4 editable parameters.

11

Enter:

RTRV-E1::AID::::[PARMS=];

where:

AID = E1-{1-7}-{2}-{8-10, 11-13}-{1-63} (E1 on the PDH Access shelf E1 Port Module)

Result: Ouput retrievable parameters are: AINSTIMER, MGRACD, PORTTYPE.

12

Retrieve 1662 subshelf STM4 FFP information

RTRV-FFP-STM4::AID;

where:

FFPSTM4-{1-7}-{2}-15-{1-2} (STM4 Facility Protection Group on PDH Access Shelf)

Result: Ouput retrievable parameters are: PTYPE, WKG, PROTN, PSDIRN, PROTOCOL,ACTIVE,CURRREQ.

END OF STEPS

1662 Subshelf Facilities Administration 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

568 Issue 4

Page 569: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

9.7 Database backup and restore from remote file server on 1662subshelf

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 DSKDB) to the secondary backup data base (STBYDB).

The RTRV-DB-LABEL command reads the database label of the selected backup database storedon the NE (ACT DSK DB or STBYDB).

The RTRV-RFILE command is used to read information related to transferred files (i.e. database)on a Remote File Server.

9.7.3 Before you begin

This procedure is done on the TSS320, when the TSS320 database backup and restore procedureis 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 andtime.

5

Check the time and date. It should be the latest date and time of back up.

1850 TSS-320/TSS-320H/TSS-160 Database backup and restore from remote file server on 1662 subshelf

Release 5.1 (ETSI)September 2017Issue 4 5698DG09603CAAATQZZA

Page 570: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 recenttransfer.

RTRV-RFILE::AID::::LOCATION=;

where:

AID = Identifies the database for which the information is retrieved.

Possible values are:

RFSDB - A database backup on a Remote File Server

Location indicates the source/destination of the transferred files on an RFS. The syntax of theurl 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 andtime 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

Database backup and restore from remote file server on 1662 subshelf 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

570 Issue 4

Page 571: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 isenabled) for the specified facility.

The SET-PMMODE-E1 command sets the mode of PM data collection for the specified facility.

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 dataare 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.

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 datacorresponding 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 PMregisters, or the current and/or up to seven (7) 1-day historical PM registers or both 15-minute and1-day PM registers can be retrieved.

1850 TSS-320/TSS-320H/TSS-160 1662 subshelf PM Administration (E1)

Release 5.1 (ETSI)September 2017Issue 4 5718DG09603CAAATQZZA

Page 572: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

9.8.3 Before you begin

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/AIDcombinations are allowed, all other shall be rejected.

Result: The command returns the PM State. Default PM state is disabled.

2

To “enable”or “disable” PM state enter:

SET-PMMODE-E1::AID:::LOCN,MODETYPE,[PMSTATE],[DIRN]:[TMPER=];

where:

AID = ALL, i.e. Access Identifier, identifies the entity access identifier. Only valid sdhFacility/AIDcombinations are allowed, all other shall be rejected.

LOCN = Location specifies the location where PM data collection is to be enabled or disabled.

Possible values are:

• 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 thespecified 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:

1662 subshelf PM Administration (E1) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

572 Issue 4

Page 573: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

RTRV-PM-E1::AID:::[MONTYPE],[MONLEV],[LOCN],[DIRN],[TMPER],[MONDAT],

[MONTM],[NUM15MIN],[NUM1DAY];

where:

AID = ALL, i.e. Access Identifier, identifies the entity access identifier. Only valid sdhFacility/AIDcombinations are allowed, all other shall be rejected.

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 BIDIR1-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 collectionis enabled) for the specified facility.

The SET-PMMODE-STM4 command sets the mode of PM data collection for the specified facility.

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 dataare 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.

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 PMdata 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 PMregisters, or the current and/or up to seven (7) 1-day historical PM registers or both 15-minute and1-day PM registers can be retrieved.

1850 TSS-320/TSS-320H/TSS-160 1662 subshelf PM Administration (STM4)

Release 5.1 (ETSI)September 2017Issue 4 5738DG09603CAAATQZZA

Page 574: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 / AIDcombinations 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 aModifiable VC4)

• PDHLOVC12-{1-7}-{2}-{8-10, 11-13}-{1-63} (VC12 with E1 client on the PDH Access shelf E1Port Module)

LOCN = Location specifies the location where PM data collection is to be enabled or disabled.

Possible values are:

• 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 thespecified mode type is enabled or disabled.

1662 subshelf PM Administration (STM4) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

574 Issue 4

Page 575: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 / AIDcombinations 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 aModifiable VC4)

• PDHLOVC12-{1-7}-{2}-{8-10, 11-13}-{1-63} (VC12 with E1 client on the PDH Access shelf E1Port 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 BIDIR1-DAY 24 hour registers.BOTH 15 minutes and 24 hour registers

END OF STEPS

1850 TSS-320/TSS-320H/TSS-160 1662 subshelf PM Administration (STM4)

Release 5.1 (ETSI)September 2017Issue 4 5758DG09603CAAATQZZA

Page 576: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

1662 subshelf PM Administration (STM4) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

576 Issue 4

Page 577: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 onthe mau interface.

1850 TSS-320/TSS-320H/TSS-160 CLI Procedures

Release 5.1 (ETSI)September 2017Issue 4 5778DG09603CAAATQZZA

Page 578: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Note: This command does not apply to Optical FE and 10GE interfaces, since they do notsupport autonegotation, and to Electrical 1GE interfaces, since they support mandatoryautonegotation. It applies to Electrical FE and optical 1GE interfaces that support configurableautonegotation.

10.2.2 Prerequisites

The node shall be equipped with data modules.

10.2.3 General

The 1850TSS at the startup has autonegotation disabled on interface mau.

Specifically, the System shall operate, the FE/GE autonegotation process, as follows:

• full duplex capability shall be supported by the System

• one locally supported speed is assumed as provisioned by manager.

• both symmetric/asymmetric “pause function” shall be supported and advertised.

The management system is required to also set a “default MAU mode” to which the MAU mustrevert when the autonegotation is disabled.

The management system can, at any time, force an autonegotation restart.

10.2.4 Procedure

1

Select action:

To retrieve the autonegotation value, go to Step 2

To enable or disable the autonegotation, go to Step 3

To restart the autonegotation between network devices, go to Step 4

To set the autonegotiation capability to be advertised, go to Step 5

For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)Release 5.1 Command Line Interface Guide.

2

Retrieve the autonegotation value

Enter interface position namingsetlist localeth show autoneg

where

• namingsetlist is one or more ports on which autonegotation should be retrieved

This command reports:

• Whether or not the autonegotation is enabled on the mau.

• The current status of the autonegotation process autonegotation capabilities supported bymau.

Administer Autonegotation 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

578 Issue 4

Page 579: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• autonegotation capabilities advertised by mau.

• The autonegotation capabilities advertised by the remote end: reported capabilities areconsidered.

• 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

STOP. This procedure is complete.

END OF STEPS

1850 TSS-320/TSS-320H/TSS-160 Administer Autonegotation

Release 5.1 (ETSI)September 2017Issue 4 5798DG09603CAAATQZZA

Page 580: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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.

10.3.2 Prerequisites

The 1850TSS shall be equipped with one or more DATA boards. The first Ethernet Flow Classifier isautomatically 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. Thecreation of a Classifier criteria requires corresponding ETS InFlow (with Ethernet or ATM as ServiceType) 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 parametersconsisting 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.1Command 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.

Administer Ethernet Flow Classifier 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

580 Issue 4

Page 581: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

2

Create, configure and activate an ETS InFlow classifier

Before adding a inflow classifier an ETS InFlow should exist, see 10.4 “ Administer ETS toProvider 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 portssupporting 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 sameETS 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 correspondingSNMP 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). Theinformation can be scoped to classifiers for a certain ETS InFlow by indicating the flow userlabel.

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

1850 TSS-320/TSS-320H/TSS-160 Administer Ethernet Flow Classifier

Release 5.1 (ETSI)September 2017Issue 4 5818DG09603CAAATQZZA

Page 582: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 ETSInFlow

Note: Attention during this operation if the default ETS flow classifier is removed allpackets are dropped at ingress.

END OF STEPS

10.4 Administer ETS to Provider Bridge ETS/PW/VPLS bidirectionalflow

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.

10.4.2 Prerequisites

The 1850TSS shall be equipped with one or more DATA boards.

10.4.3 General

ETS Flow Management This section exploits below NE functional blocks involved in Trafficclassification and ETS Flow Management (Figure 2) and their mapping with NE Functionalarchitecture:

• Classifier.

• ETS Flow Meter/Policer.

• ETS Flow Cross Connector.

• ETS Flow Adapter.

Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

582 Issue 4

Page 583: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 descriptorparameters;

• traffic descriptor association to the ETS Provider Bridge InFlow. It carries information of CoS withnull traffic descriptor parameters. If not present, the same CoS of the ETS InFlow in thecorresponding bidirectional connection is used ;

• a choice among: SVID definition for the Provider Bridge ETS InFlow/OutFlow; or PW for PWETS InFlow/OutFlow; OR VPLS Id for VPLS ETS InFlow//OutFlow; output Interface for EthernetETS InFlow/OutFlow;

• management of the received L2 control frames (tunneled or discarded) for the ETS InFlow L2control frames, configured to be discarded at the ETS flow level will be classified as notbelonging 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 classifiercriteria.

The figure below exploits below NE functional blocks involved in Traffic classification and ETS FlowManagement and their mapping with NE Functional architecture:

1850 TSS-320/TSS-320H/TSS-160 Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow

Release 5.1 (ETSI)September 2017Issue 4 5838DG09603CAAATQZZA

Page 584: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• Policing management for the ETS InFlow. It can be either color blind, IETF color-aware, MEFcolor-aware without coupling flag, (for future releases) MEF color aware with coupling flag ordisabled. 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 dropprecedence = “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 isdisabled 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/VPLSETS InFlow/OutFlow go to Step 2.

To retrieve ETS InFlow/OutFlow with the Provider Bridge/PW/VPLS ETS InFlow/OutFlow go toStep 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 toStep 5.

2

Create, configure and activate an ETS InFlow/OutFlow and the Provider Bridge/PW/VPLS/ETSETS 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 alsothe 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) Release5.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 ETSInFlow/OutFlow on which they are transported.

Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

584 Issue 4

Page 585: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 ETSInFlow. Since transport network is based on Provider Bridge, the L2 control frames with MACDA 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 trafficdescriptor 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 onwhich it is transported and corresponding cross-connections, see 10.4 “ Administer ETS toProvider 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

This procedure is aimed to be used as a guideline for a set of instructions to create, configure,activate and delete an ETS to ETS bidirectional Transparent Mapping (port to port configuration).

10.5.2 Prerequisites

The 1850TSS shall be equipped with one or more DATA boards.

10.5.3 General

A ETS flow can be defined as a unidirectional traffic stream that shares a common forwarding andQoS behavior on the transport network. The granularity of ETS flow definition depends on thetransport 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

1850 TSS-320/TSS-320H/TSS-160 Administer ETS-to-ETS bidirectional (port to port configuration)

Release 5.1 (ETSI)September 2017Issue 4 5858DG09603CAAATQZZA

Page 586: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 followinginformation;

− 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 toStep 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 FlowClassifier” (p. 580).

In “Port to Port Service” both creation and activation operations of default classifier criteria onan 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 “AdministerTraffic Descriptor” (p. 589).

• management of the received L2 control frames: all control frames are tunneled, see also10.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) isapplied, 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) Release5.1 Command Line Interface Guide

Administer ETS-to-ETS bidirectional (port to port configuration) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

586 Issue 4

Page 587: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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.

10.6.2 Prerequisites

The configuration of either dynamic or static routing is performed ONLY via TL1 command (see5.2 “Administer T-MPLS Control Plane Global Parameters” (p. 110)) and is supposed to beindependent 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 configurationover those “on per port basis” SNMP entries (e.g. ifEntry), shared between Data andManagement Planes;

• The administrative and operational status of “In fiber-In Band” management plane interface is atall 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 supportingno data traffic;

• PPP protocol, stacked over underlying either Ethernet/LAG or MPLS Interface (see above Figure1), is allowed to be disabled (Default value: enabled) from Management Operator;

• L3 protocol for Management Interface Plane, irrespective of underlying either Ethernet or MPLSInterface, is only IP: the packets received on “In Fiber In Band” Management Interface will beextracted and forwarded (based on IP protocol) to upper layer IP protocol module;

1850 TSS-320/TSS-320H/TSS-160 Administer In Fiber In Band for Control Plan

Release 5.1 (ETSI)September 2017Issue 4 5878DG09603CAAATQZZA

Page 588: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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 in3 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 VLANID 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 LinkAggregation interface):

Enter: infiberinband delete port {naming | lagnumber}

where

• namingmust have rack, subrack, board≠0 and drawer=port=0; in commands that apply to aport, the naming must have rack, subrack, board, port≠0;

4

Retrieve IF-IB

Enter: infiberinband show [port {naming | lagnumber}]

Administer In Fiber In Band for Control Plan 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

588 Issue 4

Page 589: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Note: If the optional parameter is absent, this command retrieves detailed informationabout all configured DCN management interfaces (either Ethernet or Link Aggregationinterface). The user can retrieve detailed information of only a single DCN managementinterface by providing its naming.

END OF STEPS

10.7 Administer Traffic Descriptor

10.7.1 Purpose

This procedure is aimed to be used as a guideline for a set of instructions to create, configure,activate and delete a traffic descriptor.

10.7.2 Prerequisites

The System shall support the Traffic Descriptor change (i.e. values of the corresponding IETFBandwidth 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 aTraffic Descriptor to an input ETS Flow or to a group of input ETS Flows according to Trafficdescriptor 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 toEnhanced ETS traffic Descriptor) to an ETS Flow for PHB enforcement purposes, without anyenforcement in terms of both ETS Policing/Metering and ETS CAC Policies to be applied over thatETS Flow.

NULL Traffic Descriptor is able to represent Input (Colored) PHB tightly coupled with input ETSFlow, BOTH as input parameters for ETS cross-connections.

NE functions to handle (inside ETS Layer) outgoing Ethernet traffic are requested to take intoaccount:

• adopted Traffic Descriptor (either ETS Traffic Descriptor or NULL Traffic Descriptor);

• specific output logical interface (MPLS VC LSP, UNI/IWI, Provider Bridge Virtual interface) ategress from ETS Layer.

For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1Command Line Interface Guide.

1850 TSS-320/TSS-320H/TSS-160 Administer Traffic Descriptor

Release 5.1 (ETSI)September 2017Issue 4 5898DG09603CAAATQZZA

Page 590: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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) orMEF (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:

Administer Traffic Descriptor 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

590 Issue 4

Page 591: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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

This procedure is aimed to be used as a guideline for a set of instructions to create, configure,activate and delete a color profile.

10.8.2 Prerequisites

The 1850TSS shall be equipped with one or more DATA boards.

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”(EthernetForwarding Class, DP) has been previously both “policed” and “pre-colored”;

• incoming ETS Traffic, characterized from an already assigned “colored PHB” (EthernetForwarding 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 algorithmshave 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.

1850 TSS-320/TSS-320H/TSS-160 Color Profile Management

Release 5.1 (ETSI)September 2017Issue 4 5918DG09603CAAATQZZA

Page 592: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

The color-aware mode assumes that incoming ETS Traffic has been pre-colored (as green, yellowor red). The behavior of the color-aware ETS policing algorithms implemented according to MEFwith 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 ETSTraffic Descriptors

• ensures the use of network resources within the limits of agreed Traffic Descriptor and performsthose reactive actions over marked packets.

Each color profile considers either PRI or DSCP values, and associates to each of them a dropprecedence [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).

For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1Command Line Interface Guide.

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 togreen(g) by default) are set to any supported drop precedence values (green, yellow, red)

3

Retrieve a color profile

Color Profile Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

592 Issue 4

Page 593: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enter

colorprofile show [colorprofuserlabel]

where:

If colorprofuserlabel is not specified the list of color profiles with their drop precedenceinformation is shown.

4

Delete a color profile

The Delete Color Profile Management Function is possible if no input ETS Flow is referringColour 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.

10.9.2 Prerequisites

The node should be equipped with one of the following boards:

• only optical GE (1000BaseX-FD)

• (from Rel.3.0 onward) Electrical GE interface.

10.9.3 General

The steps below explain how to to set the default MAU type for interface and retrieve itsinformation.

General MAU information retrieved:

• mau and operational status

• jack type: jack connector type and jabber status: it can be {other | no jabber | jabbering}. It ismeaningful 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

1850 TSS-320/TSS-320H/TSS-160 Ethernet Physical management

Release 5.1 (ETSI)September 2017Issue 4 5938DG09603CAAATQZZA

Page 594: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• interface alarm status

For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1Command Line Interface Guide.

10.9.4 Procedure

1

Set the default interface MAU type

This operation can be performed only when the administrative status of supporting Ethernetinterface is down.

To verify Ethernet interface administrative status refer to 10.10 “ Ethernet Port management(over MAU)” (p. 595)

Is the port administrative status is “up”?

If yes go to Step 2

If no, go to Step 3

2

Enter:

interface position namingsetlist localeth deactivate

where:

namingsetlist is one or more ports configured that should be deactivated.

3

If the port administrative status is down enter:

interface position namingsetlist localeth defaulttype {10 | 100 | 1000

}

where:

namingsetlist is one or more ports configured with TL1 configuration commands.

4

Retrieve general MAU information

Enter:

interface position namingsetlist localeth show mauinfo

where:

namingsetlist is one or more ports configured with TL1 configuration commands.

END OF STEPS

Ethernet Physical management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

594 Issue 4

Page 595: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

10.10 Ethernet Port management (over MAU)

10.10.1 Purpose

This procedure provides instructions and sequence to manage a Ethernet local port.

10.10.2 Prerequisites

The node should be equipped with one of the following boards:

• 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;

For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1Command Line Interface Guide.

10.10.4 Procedure

1

Select action:

Retrieve Ethernet local port information, go to Step 2

Activate/Deactivate Ethernet local port, go to Step 3

Configure Ethernet local port type, go to Step 4

Configure Ethernet local port maximum MTU/MRU, go to Step 5

Configure some Ethernet local port parameters using a single command, go to Step 6

2

Retrieve Ethernet local port information

Enter interface position namingsetlist localeth show ethinfo

where:

namingsetlist is one or more ports configured with TL1 configuration commands.

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

1850 TSS-320/TSS-320H/TSS-160 Ethernet Port management (over MAU)

Release 5.1 (ETSI)September 2017Issue 4 5958DG09603CAAATQZZA

Page 596: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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 to00: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 whichactivation 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 Step3.

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:

Ethernet Port management (over MAU) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

596 Issue 4

Page 597: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

namingsetlistis one or more ports (configured with TL1 configuration commands) on whichMTU/MRU should be changed.

Note: The operation is rejected If ifAdminStatus is set to “up” value.

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 GFPport..

10.11.2 Prerequisites

The node should be equipped with one of the following boards:

• 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;

For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1Command Line Interface Guide.

10.11.4 Procedure

1

Select action:

Retrieve Ethernet remote port information, go to Step 2

Activate/Deactivate Ethernet remote port, go to Step 3

1850 TSS-320/TSS-320H/TSS-160 Ethernet Port management (over GFP)

Release 5.1 (ETSI)September 2017Issue 4 5978DG09603CAAATQZZA

Page 598: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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:

namingsetlist is one or more ports configured with TL1 configuration commands.

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 to00: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:

namingsetlistis one or more ports (configured with TL1 configuration commands) on whichactivation 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, seeStep 3.

The default Ethernet remote port type is ETS.

Ethernet Port management (over GFP) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

598 Issue 4

Page 599: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Enterinterface position namingsetlist remoteeth portservice {ets |

bridge | mpls | iw}

Note: The operation is rejected If ifAdminStatus is set to “up” value.

5

Configure Ethernet remote port maximum MTU/MRU

Enter interface position namingsetlist remoteeth maxmtu mtu_value

where:

namingsetlistis one or more ports (configured with TL1 configuration commands) on whichMTU/MRU should be changed.

Note: The operation is rejected If ifAdminStatus is set to “up” value.

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.

10.12.2 Prerequisites

None.

10.12.3 General

Below the list of the configured interfaces information retrievable:

• the administrative status

• the interface type

• the Ethernet port client layer

• the traffic port enabling

• the operational status

• the line rate

• the traffic rate to which transmission is limited (only for remote ethernet port)

• the ingress port admitted flooding rate (i.e. the threshold value of received admitted bandwidth,generating flooding traffic, on this ingress interface).

1850 TSS-320/TSS-320H/TSS-160 General Interface Management

Release 5.1 (ETSI)September 2017Issue 4 5998DG09603CAAATQZZA

Page 600: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1Command Line Interface Guide.

10.12.4 Procedure

1

To retrieve the following information:

• administrative status

• operational status

• the traffic rate to which transmission is limited

• the traffic port enabling

• the ingress port admitted flooding rate

Enter:

interface trafficshow [namingsetlist]

where:

namingsetlist is one or more ports configured with TL1 configuration commands.

The parameters between square brackets are optional. If a value is not entered for theseparameters, the system will show all configured interfaces values.

2

To retrieve the following information:

• the administrative status

• the interface type

• the Ethernet port client layer

• ETS Service Type and ETS Service Status

• the traffic port enabling

Enter interface show [namingsetlist]

where:

namingsetlist is one or more ports configured with TL1 configuration commands.

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 ordiscarded) received at a certain Ethernet port or a LAG Port configured as ETS port.

L2 control frames management (in Provider Bridge) 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

600 Issue 4

Page 601: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

10.13.2 Prerequisites

Provider Bridge is installed and one or more data boards are configured. Before the L2 controlframes configuration the Administrative Status of all underlying local/remote ethernet interface isrequested 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 Protocolframes 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 toenabled 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 interfacesconfigured in promiscuous mode with an ETS client type) and forces an automatic change (incharge of NE) on the actual layer 2 control frame disposition on all the active InFlows associated tothe ETS interface.

Incoming L2 control frames (received from NE incoming either (local/remote) Ethernet interface orLAG Interface) are recognized by looking at their MAC Destination Address field. Customer L2Control Protocols received on UNI/ETH-IWI can be either tunnelled or discarded according to theservice configuration. At Provider Bridge UNI for security reasons any received Provider BPDUframe is always discarded from NE (there is not configuration option for this behaviour).

For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1Command Line Interface Guide.

10.13.4 Procedure

1

Select action:

Manage L2 control frames go to Step 3

Retrieve L2 control frames information go to Step 4.

2

Verify the port type is ETS and its administrative status is UP, see 10.10 “ Ethernet Portmanagement (over MAU)” (p. 595).

3

Manage L2 control frames

Enter interface position namingsetlistlagnumberset l2ctrlframe

ctrlframe32bits {pass | drop}.

where:

1850 TSS-320/TSS-320H/TSS-160 L2 control frames management (in Provider Bridge)

Release 5.1 (ETSI)September 2017Issue 4 6018DG09603CAAATQZZA

Page 602: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

ctrlframe32bits identifies the control frame types for managing their passing through ordiscarding

4

Retrieve L2 control frames information

To get the L2 control frames management (tunneled or discarded) associated to a certainEthernet 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, LAGInterface).

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 Aggregationmanagement. .

10.14.2 Prerequisites

The 1850TSS320 shall be equipped with one or more DATA boards. Ports involved in a LAG canbelong 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 ormore physical ports , the “Aggregation Ports” (AP), of the same speed and configuration (MAUsetting) :

• 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 portsbelonging 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 Aggregationfunction 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 LAPDUformat packets

LAG Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

602 Issue 4

Page 603: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Traffic is shared among Aggregated Links belonging to an Aggregated system, by means of aproprietary algorithm (“hashing” function). Basic principle of the algorithm is that a set of orderedframes from two end-point users (end stations), also known as “Conversation” can transit on onlyone link . Therefore, load balancing is not taken for grant , because of statistical distribution of trafficover link aggregation interface. Furthermore, an Aggregated Link can carry out more that oneConservation.

Inherent protection mechanism ensures that, in case of failure of one or more links , traffic isredistributed 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 byaggregated links, due to new computation of hashing function. Therefore, traffic is not hitless for allthe conversation set.

Default LAG size is 8.

For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1Command Line Interface Guide.

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.

Figure 36 Fig1. Link Aggregation concept

1850 TSS-320/TSS-320H/TSS-160 LAG Management

Release 5.1 (ETSI)September 2017Issue 4 6038DG09603CAAATQZZA

Page 604: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 sameLAG 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 Lagcreation/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 Lagcreation/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;

LAG Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

604 Issue 4

Page 605: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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) withthe 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 avlan protocol profile and to associate it to an ETS port.

10.15.2 Prerequisites

The 1850TSS should be equipped with one or more data boards.

10.15.3 General

This Management function permits to associate a VLAN Protocol Profile to an underlying (local/remote) Ethernet interface: incoming Ethernet frames, received on that Ethernet interface andmatching that “per interface” VLAN Protocol Type, are handled as VLAN Tagged frame (QTagged,

1850 TSS-320/TSS-320H/TSS-160 VLAN protocol profile Management

Release 5.1 (ETSI)September 2017Issue 4 6058DG09603CAAATQZZA

Page 606: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

PTagged or STagged). If no VLAN Protocol Profile is associated to this Ethernet interface, DefaultVLAN Protocol Type (0x8100) is implicitly associated.

Briefly, the association between Vlan protocol Profile and port can be done in two different ways:

• create first the vlan profile and then create the association between the port and the vlan profile(i.e. two CLI commands are used to perform this operation);

• or create and activate the association and vlan profile using a single CLI command.

For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1Command Line Interface Guide.

10.15.4 Procedure

1

Select action

To create a vlan protocol profile go to Step 2.

To delete vlan protocol profile go to Step 3.

To retrieve a vlan protocol profile information go to Step 4.

To associate ports to a Vlan profile go to Step 5

2

Create and activate VLAN protocol profile

Enter vlanprotprofile activate vlanprotprofuserlabel [type

ethertypevalue]

where:

vlanprotprofuserlabel is a mnemonic string to address the VLAN.

If EtherType is not specified, it is initiated with EtherType=0x8100

Vlan profile can be created during Vlan profile port association see Step 5

The ethertype is an hexadecimal value for the provider protocol-type (PT) that is inserted intothe 2 bytes field of the Stacked VLAN shim header; the value identifies the network providerand has to be 2 bytes long in hexadecimal notation; the third non-included byte is forced bydefault to “0x”.

The PT is used to recognize the type of different VLAN frames, i.e. if they are “SVlan tagged” orothers; 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 of8100 is interpreted as QVlan tagged. Other values of PT will be interpreted as generic StackedVlan 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

VLAN protocol profile Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

606 Issue 4

Page 607: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 portenter:

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: incomingEthernet frames, received on that Ethernet interface and matching that VLAN EtherType, arehandled 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

1850 TSS-320/TSS-320H/TSS-160 VLAN protocol profile Management

Release 5.1 (ETSI)September 2017Issue 4 6078DG09603CAAATQZZA

Page 608: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 Instanceto 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 connectivitythat makes it possible to interconnect several LAN segments over a VPLS Network (consisting offully 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 (irrespectivefrom higher layer protocols) between 2 remote Ethernet stations;

• Ethernet services to exploit “carrier class” MPLS capabilities, relying on both MPLS “connectionoriented” 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 bycommas: (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 thoseparameters, the system will use the default value.

For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1Command Line Interface Guide.

10.16.4 Procedures

1

Select action.

To retrieve VPLS instance information, go to Step 5.

To create VPLS instance, go to Step 2.

VPLS Instance Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

608 Issue 4

Page 609: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 InstanceEgress 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 portbelonging 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 VPLSInstance.

Enter: vpls add vplsuserlabel [portset namingsetlistlagnumberset] [pwset

pwset] [spokepwset pwset]

1850 TSS-320/TSS-320H/TSS-160 VPLS Instance Management

Release 5.1 (ETSI)September 2017Issue 4 6098DG09603CAAATQZZA

Page 610: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

7

Remove elements to a VPLS Instance

This command removes both (either) UNI and (or) Core/Spoke MPLS PW’s from a createdVPLS Instance.

Enter: vpls remove vplsuserlabel [portset namingsetlistlagnumberset]

[pwset pwset] [spokepwset pwset]

END OF STEPS

VPLS Instance Management 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

610 Issue 4

Page 611: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

A Software Reference Guide

A.1 Introduction

A.1.1

This Software Reference Guide provides supplementary information to be used with the1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 User ProvisioningGuide.

• 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 systemcommands and determines each user's access level.

• A.6 “Performance Monitoring” (p. 656) lists PM parameters supported in the system, parametermaximum 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 thefacility 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.

1850 TSS-320/TSS-320H/TSS-160 Software Reference Guide

Release 5.1 (ETSI)September 2017Issue 4 6118DG09603CAAATQZZA

Page 612: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

− 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: 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 or entity number within the shelf in which theLOA 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: 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: 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: bay# = the number of the bay within the system.

− where: shelf# = the number of the shelf within the specified bay.

− where: slot# = the number of the slot or position within the shelf.

− where: PIM# = the PIM number within the slot,

− where VCG# = the VC group number on the L2 aggregator

− where VC4# = the VC4 facility number within the VC group.

− where TU3# = the TU3 facility number within the VC4.

− where TU12# = the TU12 facility number within the TU3.

VCGs and its PTFs for units without PIMMS are from:

• facility-bay#-shelf#-slot#-(VCG#)-(VC4#)-(TU3#)-(TU12#)

− where: bay# = the number of the bay within the system.

− where: shelf# = the number of the shelf within the specified bay.

− where: slot# = the number of the slot or position within the shelf.

− where VCG# = the VC group number on the L2 aggregator

− where VC4# = the VC4 facility number within the VC group.

− where TU3# = the TU3 facility number within the VC4.

− where TU12# = the TU12 facility number within the TU3.

Gigabit Ethernet facilities on 10xANY or Packet cards are of the form:

• GBE-bay#-shelf#-slot#-GBE#

Access Identifiers 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

612 Issue 4

Page 613: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

− where: GBE# = the Gigabit Ethernet port number within the card (that's the same as the SFPnumber).

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, ormessages is:

• BITS-bay#-shelf#-port#

− where: bay# = the number of the bay within the system.

− where: shelf# = the number of the shelf within the specified bay.

− where: port# = the port number of the timing source: 0 = Port A on the TC, 1 = Port B on theTC.

BITS AID is used for functions related to the NE external timing input port (signal source) onthe main shelf. (The main shelf would not have a TREFIN AID)

The syntax for External Timing Reference for the System Timing access identifiers in TL1commands, responses, or messages is:

• EXTREF-bay#-shelf#-ref#

− where: bay# = the number of the bay within the system.

− where: shelf# = the number of the shelf within the specified bay.

− where: ref# = the number of the external timing reference: There are 2 external timingreferences supported with the numbers 0,1.

The syntax for Line Timing Reference for the System Timing access identifiers in TL1 commands,responses, or messages is:

• LINEREFSYS-bay#-shelf#-ref#

− where: bay# = the number of the bay within the system.

− where: shelf# = the number of the shelf within the specified bay.

− where: ref# = the number of the line timing reference: There are 6 line timing referencessupported with the numbers 0,1,2,3,4,5.

The syntax for Line Timing Reference for the Output Timing access identifiers in TL1 commands,responses, or messages is:

• LINEREFOUT-bay#-shelf#-ref#

− where: bay# = the number of the bay within the system.

− where: shelf# = the number of the shelf within the specified bay.

− where: ref# = the number of the line timing reference: There are 6 line timing referencessupported with the numbers 0,1,2,3,4,5.

The syntax for NE Timing Node access identifiers in TL1 commands, responses, or messages is:

• SYNC-bay#-shelf#-ref#

− where: bay# = the number of the bay within the system.

− where: shelf# = the number of the shelf within the specified bay.

1850 TSS-320/TSS-320H/TSS-160 Access Identifiers

Release 5.1 (ETSI)September 2017Issue 4 6138DG09603CAAATQZZA

Page 614: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

− where: ref# = 0, because there is only one timing node supported in the system, which will berepresented by this AID.

A.2.3 General Equipment AID Format:

The syntax for equipment identifiers (i.e. equipment AIDs) in TL1 commands, responses, ormessages is:

• Equipment name-bay#-shelf#-slot#-(PIM#/SFP/XFP#)-(SFP/XFP#)

− where: equipment name = the circuit pack mnemonic/name

− where: bay# = the number of the bay within the system.

− where: shelf# = the number of the shelf within the specified bay.

− where: slot# = the number of the slot or position within the shelf in which the equipment ispresent.

− 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 pluggablemodules.

− where: SFP/XFP# = the SFP number within the PIM -or- the XFP number within the PIM. Thisis an optional parameter used only for pluggable modules within PIM for L2 Aggregatorboards.

A.2.4 General Profile AID Format:

The syntax for ASAP (Alarm Severity Assigned Profile) identifiers in TL1 commands or responsesis:

• 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 ASAPinstances, 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 THPinstances, while the other indexes are assigned by the NE at the THP instances creation.

Access Identifiers 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

614 Issue 4

Page 615: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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)

The AID for an STM4 facility is:

• STM4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} (STM4)

The AID for an AU4 embedded in a STM4 signal is:

• STM4AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-{1-4} (AU4 embedded within anSTM4)

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 anSTM4)

The AID for an STM16 facility is:

• STM16-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4, 5, 7} (STM16 on a 2G5SO or10xANY)

The AID for an AU4 embedded in a STM16 signal is:

• STM16AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1-16} (AU4 in an STM16on a 2G5SO or a 10xANY)

The AID for an AU4-4C embedded in a STM16 signal is:

• STM16AU44C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1,5,9,13} (AU4-4c inan STM16 on a 2G5SO or 10xANY)

The AID for an AU4-16C embedded in a STM16 signal is:

• STM16AU416C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-1 (AU4-16c in an STM16on a 2G5PSO or 10xANY)

The AID for an STM64 facility is:

• STM64-{1-7}-{1-9}-{2-9,12-19,21-36}-1 (STM64)

The AID for an AU4 embedded in a STM64 signal is:

• STM64AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-1-{1-64} (AU4 embedded within anSTM64)

The AID for an AU4-4C embedded in a STM64 signal is:

• STM64AU44C-{1-7}-{1-9}-{2-9,12-19,21-36}-1-{1,5,9,13,17,21,25,29,33,37,

1850 TSS-320/TSS-320H/TSS-160 Access Identifiers

Release 5.1 (ETSI)September 2017Issue 4 6158DG09603CAAATQZZA

Page 616: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

41,45,49,53,57,61} (AU4-4c embedded within an STM64)

The AID for an AU4-16C embedded in a STM64 signal is:

• STM64AU416C-{1-7}-{1-9}-{2-9,12-19,21-36}-1-{1,17,33,49} (AU4-16cembedded within an STM64)

The AID for an AU4-64C embedded in a STM64 signal is:

• STM64AU464C-{1-7}-{1-9}-{2-9,12-19,21-36}-1-1 (AU4-64c embedded within anSTM64)

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 aPP10AD 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 aMultiservice 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 ona 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 VCGon 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 10xAnymodule)

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 10xAnymodule)

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 a10xAny 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)

Access Identifiers 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

616 Issue 4

Page 617: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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, OT2TDMmodule)

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 anOTU2)

• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{L1}-1 (ODU2 facility in anOTU2 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} (TU12embedded 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 aModifiable 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)

1850 TSS-320/TSS-320H/TSS-160 Access Identifiers

Release 5.1 (ETSI)September 2017Issue 4 6178DG09603CAAATQZZA

Page 618: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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)

The AID for the STM4 FFP is:

• FFPSTM4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} (STM4 Facility Protection Group)

The AID for the STM16 FFP is:

• FFPSTM16-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4} (STM16 Facility Protection Groupon a 2G5SO or 10xANY)

The AID for the STM64 FFP is:

• 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:

• LINEREFSYS-{1-7}-{1-9}-{0-5} (Timing Reference of a Shelf for a Line Port selectable forSystem 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 forOutput Timing)

The AID for the Timing Node within a Shelf is:

• SYNC-{1-7}-{1-9}-0 (Timing Node within a Shelf)

Access Identifiers 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

618 Issue 4

Page 619: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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)

1850 TSS-320/TSS-320H/TSS-160 Access Identifiers

Release 5.1 (ETSI)September 2017Issue 4 6198DG09603CAAATQZZA

Page 620: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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:

• PP10GE-{1-7}-{1-9}-{2-9,12-19} (Packet Module 1x10Gb)

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)

Access Identifiers 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

620 Issue 4

Page 621: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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)

1850 TSS-320/TSS-320H/TSS-160 Access Identifiers

Release 5.1 (ETSI)September 2017Issue 4 6218DG09603CAAATQZZA

Page 622: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 MPLSInterface)

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 MPLSInterface)

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)

Access Identifiers 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

622 Issue 4

Page 623: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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)

1850 TSS-320/TSS-320H/TSS-160 Access Identifiers

Release 5.1 (ETSI)September 2017Issue 4 6238DG09603CAAATQZZA

Page 624: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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)

Access Identifiers 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

624 Issue 4

Page 625: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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)

• ASAPSTM4-{0-1} (NULL and Factory DEFAULT STM4 ASAP)

• ASAPSTM4-{2-255} (User defined STM4 ASAP, where n is a theoretic limit)

• ASAPSTM16-{0-1} (NULL and Factory DEFAULT STM16 ASAP)

• ASAPSTM16-{2-255} (User defined STM16 ASAP, where n is a theoretic limit)

• ASAPSTM64-{0-1} (NULL and Factory DEFAULT STM64 ASAP)

• ASAPSTM64-{2-255} (User defined STM64 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)

• ASAPVC416C-{0-1} (NULL and Factory DEFAULT VC416C ASAP)

• ASAPVC416C-{2-255} (User defined VC416C ASAP, where n is a theoretic limit)

• ASAPVC464C-{0-1} (NULL and Factory DEFAULT VC464C ASAP)

• ASAPVC464C-{2-255} (User defined VC464C 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)

1850 TSS-320/TSS-320H/TSS-160 Access Identifiers

Release 5.1 (ETSI)September 2017Issue 4 6258DG09603CAAATQZZA

Page 626: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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)

• THPSTM4-{0-1} (NULL and Factory DEFAULT STM4 THP)

• THPSTM4-{2-127} (User defined STM4 THP, where n is a theoretic limit)

• THPSTM16-{0-1} (NULL and Factory DEFAULT STM16 THP)

• THPSTM16-{2-127} (User defined STM16 THP, where n is a theoretic limit)

• THPSTM64-{0-1} (NULL and Factory DEFAULT STM64 THP)

• THPSTM64-{2-127} (User defined STM64 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)

• THPVC416C-{0-1} (NULL and Factory DEFAULT VC416C THP)

• THPVC416C-{2-127} (User defined VC416C THP, where n is a theoretic limit)

• THPVC464C-{0-1} (NULL and Factory DEFAULT VC464C THP)

• THPVC464C-{2-127} (User defined VC464C 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)

Access Identifiers 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

626 Issue 4

Page 627: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 the1850 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. (Theterm 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 andwhat action can be taken to make the entity available. An entity's state is described by twoparameters, 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 itsprovisioned functions. (IS and IS-NR may be used interchangeably in thisdocument.)

IS-ANR In_Service_Abnormal: the entity is capable of most functions, is allowed toprovide its provisioned functions, but is operating in a degraded or abnormalstate (e.g., non-alarmed BER Signal Degrade threshold crossing on an STS)

1850 TSS-320/TSS-320H/TSS-160 States

Release 5.1 (ETSI)September 2017Issue 4 6278DG09603CAAATQZZA

Page 628: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 35 Primary Equipment Values (continued)

STATE NAME DEFINITION

OOS-AU Out_Of_Service-Autonomous: the entity is not available for providing itsprovisioned functions but the entity is not intentionally suspended by externalmanagement command (from an OS or craft interface) from performingthese functions. In general, the cause of the incapability is due to anunsolicited autonomous event detected in the system or in the associatednetwork (e.g., LOS detected).

OOS-AUMA Out_Of_Service-Autonomous_and_Management: the entity is not availablefor providing its provisioned functions because an OOS-AU state transitionhas occurred and the entity is intentionally suspended by externalmanagement command (from an OS or craft interface) from performing itsprovisioned functions

OOS-MA Out_Of_Service-Management: the entity is intentionally suspended byexternal management command (from an OS or craft interface) fromperforming its provisioned functions, but the entity may still be operationallycapable of performing its provisioned functions.

If an entity is out of service (OOS), the PST indicates whether the out-of-service condition is due toan external management command (from an OS or user interface) or is caused by the systembecause of an internal event, or both.

When provisioning an entity and specifying a PST value in a command, the PST name is shortenedto IS (in service) or OOS, but the full PST name (for example, OOS-AUMA) is used when providedin 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 valueapplies to an entity, the SST values are grouped with an ampersand (&) in the output responsemessage (for example, FAF&SGEO).

Refer to Table 36, “Secondary Equipment Values (TL1 3.0)” (p. 628) for SST values used in thesystem.

Table 36 Secondary Equipment Values (TL1 3.0)

STATE NAME DEFINITION

FLT Fault - The entity is OOS due to at least one hardware fault.

MEA Mismatch of Equipment and Attributes - The entity is installed with incorrectequipment or card, or the correct equipment is installed, but it has improperattributes assigned.

SDEE Supported Entity Exists - The entity is currently supporting other entities.

States 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

628 Issue 4

Page 629: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 36 Secondary Equipment Values (TL1 3.0) (continued)

STATE NAME DEFINITION

SGEO Supporting Entity Outage - The associated supporting entity has failed or isout of service due to management action.

SWDL Software Download - Software entity is currently being loaded with thenecessary software or database data and code.

UAS Unassigned - The entity has not been assigned with necessary provisioningdata.

UEQ Unequipped - The equipment entity is not equipped with necessaryhardware, 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-160configuration. The DESCRIPTION column identifies the relationship between equipment andcondition type. The EQUIPMENT column lists applicable equipment for each condition.

Table 37 1850 TSS-320, TSS-320H and TSS-160 Equipment Condition Types

CONDI-TION TYPE

DESCRIPRTION EQUIPMENT

ABNOR-MAL

Indicates that a module has been inserted in a position whereit cannot be provisioned, or the module has been deleted butis still physically present

MDL

AIRTEMP The cooling air temperature has exceeded the first (lower)threshold, associated with air temperature sensor at the FANsintake.

FAN320

BPERROR Backplane Error indicates that a failure has been detected ona shelf backplane.

Shelf

CONTBUS Indicates that the shelf controller is unreachable MT320/160

CONTCOM Indicates that a communication failure has been detectedbetween the active and passive FLC cards.

Shelf

DBF Database Backup Failure, creation of local backup databasefailed.

Shelf

DBRESET DB reset after FLC restart and FLC-SLC communication isinhibited.

Shelf

1850 TSS-320/TSS-320H/TSS-160 Codes

Release 5.1 (ETSI)September 2017Issue 4 6298DG09603CAAATQZZA

Page 630: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 37 1850 TSS-320, TSS-320H and TSS-160 Equipment Condition Types (continued)

CONDI-TION TYPE

DESCRIPRTION EQUIPMENT

FA Fuse alarm and service is affected (i.e. power interruption). Itis reported, for POW320, if a Fuse Broken information isreceived from both the POW320

FAN320,POW320,PSF320

FRCD-WKSW

Forced switch of working module to protection usingSWTOPROTN-EQPT with MODE parameter set to FRCD.

LOA10G

HWFAIL Hardware error is detected associated with a module.Protection is not available and/or service is affected.

10GSO,2G5SO,8XSO, EC320,FAN320,MT320/160,OT2TDM.10XANY, SFP,XFP, LOA10G,CWLA, CADM,CMDX,PP10AD,PP1GE,PP10GE,OMDX8100,DWLA10X,PRE10G,BOOST10G,LOFA1111

Hardware error is detected associated with a module. Serviceis not affected

Failure on HW and service could be affected: it is reported asMJ if an HW Failure information is received from both thePOW320 POW320,

PSF320Failure on HW and service is not affected: it is reported asMN if an HW Failure information is received from one onlyPOW320

Codes 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

630 Issue 4

Page 631: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 37 1850 TSS-320, TSS-320H and TSS-160 Equipment Condition Types (continued)

CONDI-TION TYPE

DESCRIPRTION EQUIPMENT

IMPRO-PRMVL

Indicates that physical removal was performed on anequipment module without first logically removing it whereprotection is not available.

10GSO,2G5SO,8XSO, EC320,FAN320,MT320/160,OT2TDM.10XANY, SFP,XFP, LOA10G,CWLA, CADM,CMDX,PP10AD,PP1GE,PP10GE,OMDX8100,DWLA10X,PRE10G,BOOST10G,LOFA1111

Indicates that physical removal was performed on anequipment module without first logically removing it whereprotection is available.

INHSWDX Duplex (redundant) one-to-one module is inhibited from copyswitching (disable a switch using INHSWDXEQPT command)

EC320

INHSWPR Protection module is inhibited from providing protection(lockout of protection operation using INHSWTOPROTN-EQPT command).

Working module is inhibited from switching to protection(lockout a working operation using INHSWTOPROTNEQPTcommand).

LOA10G

INIT Initialization, indicates that system initialization is currently inprogress.

Shelf

1850 TSS-320/TSS-320H/TSS-160 Codes

Release 5.1 (ETSI)September 2017Issue 4 6318DG09603CAAATQZZA

Page 632: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 37 1850 TSS-320, TSS-320H and TSS-160 Equipment Condition Types (continued)

CONDI-TION TYPE

DESCRIPRTION EQUIPMENT

MAN Logical removal was performed on an equipment module andprotection is not available

EC320, FAN320.MT320/160,POW320,PSF320Logical removal was performed on an equipment module and

protection is available

Logical removal was performed on an equipment modulewhere no protecting mate is available. For IOCs andXFP/SFP modules if the equipment has supported entitiesprovisioned.

10GSO,2G5SO,8XSO, EC320,FAN320,MT320/160,OT2TDM.10XANY, SFP,XFP, LOA10G,CWLA, CADM,CMDX,PP10AD,PP1GE,PP10GE,OMDX8100,DWLA10X,PRE10G,BOOST10G,LOFA1111

Logical removal was performed on an equipment modulewhere a protecting mate is available. For IOCs and XFP/SFPmodules if the equipment has no supported entitiesprovisioned.

MANWK-SWPR

Manual switch of working module to protection usingSWTOPROTNEQPT with MODE parameter set to NORM.

LOA10G

MISC-1 Indicates that the slave CRU is not tracking the master CRU. MT320/160

MTXLNK-FAIL

Indicates that at least one NGI payload link from/to IOC slotsto/from one Matrix slot has been detected in failure

MT320/160

NOT-EQPD NOT-EQPD is an EQPS Condition summarizing Card Missingor Card Mismatch situations on a Card of an EPS Group

LOA10G

NT-POOSYNC

Network Time Protocol is enabled, but no NTP server isreachable.

Shelf

Codes 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

632 Issue 4

Page 633: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 37 1850 TSS-320, TSS-320H and TSS-160 Equipment Condition Types (continued)

CONDI-TION TYPE

DESCRIPRTION EQUIPMENT

PRC-DRERR

It is asserted against a non compatible module inserted into ashelf and action is SA (that is, a protection is not available). Itis set when a module not consistent with Hw slot / Swassignment (also incompatible revision) is detected. Clearedwhen the incompatible module is physically removed

10GSO,2G5SO,8XSO, EC320,FAN320,MT320/160,OT2TDM.10XANY, SFP,XFP, LOA10G,CWLA, CADM,CMDX,PP10AD,PP1GE,PP10GE,PSF320,OMDX8100,DWLA10X,PRE10G,BOOST10G,LOFA1111

It is asserted against a non compatible module inserted into ashelf and action is NSA (protection available). It is set when amodule not consistent with Hw slot / Sw assignment (alsoincompatible revision) is detected. Cleared when theincompatible module is physically removed

PWR Local side Power has been interrupted to a module whileRemote side power is available. The condition indicates lossof a Battery Feed voltage to the rack or an open CB or fuse.

PSF320,POW320

RAIDSYNC The backup FLC disk is being synchronized to the workingFLC by the RAID system. EC320 protection switching is notavailable

EC320

SWDWN Indicate that the identified module is being downloaded with asw

10GSO,2G5SO,8XSO, EC320,MT320/160,PP10AD,PP1GE,PP10GE,

SYN-CEQPT

Indicates an equipment failure of both CRUs. MT320/160

Indicates an equipment failure of one CRU, declared againstthe 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 reverttimer is running).

LOA10G

1850 TSS-320/TSS-320H/TSS-160 Codes

Release 5.1 (ETSI)September 2017Issue 4 6338DG09603CAAATQZZA

Page 634: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

A.4.2 Facility Condition Type Codes

Refer to Table 38, “1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition TypeCodes” (p. 633) for facility condition type codes used in the 1850 TSS-320, TSS-320H and TSS-160configuration. The DESCRIPTION column identifies the relationship between facility and conditiontype. 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-TION TYPE

DESCRIPTION EQUIPMENT

ACTLPBK The associated entity has a loopback activated at the nearend.

GBE, MAU

AIS Indicates that a CRU has detected a AIS for a dedicated BITSfacility.

BITS

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 isapplicable to 1+1 bidirectional FFP provisioned facilities.

STM-n

APSCD-FLTK

APS Condition, Default K-bytes. This condition is set whenthe default code is detected on the incoming K-bytes.

STM-n

APSCIMP APS Condition, Improper K-bytes. This condition is set whenimproper K-bytes are detected on the incoming K1-bytes

STM-n

APSCIN-CON

APS Condition, Inconsistent K-bytes. This condition is setwhen inconsistent K-bytes are detected.

STM-n

APSCM APS Channel Match Failure been detected. This failure isapplicable to 1+1 bidirectional FFP provisioned facilities.

STM-n

APSCNMIS APS Condition, Connection Mismatch. This condition is setwhen a Node identifier mismatch in K bytes is detected.

STM-n

APSMM APS Mode Mismatch Failure has been detected. This failureis applicable to 1+1 bidirectional FFP provisioned facilities.

STM-n

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. Noadjacencies formed.

STMn

Codes 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

634 Issue 4

Page 635: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition TypeCodes (continued)

CONDI-TION TYPE

DESCRIPTION EQUIPMENT

EOCL Embedded Operations Channel failure on Line DCC. Noadjacencies formed.

STMn

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-SWTIM-REF

Timing Selection is forced to a Timing Reference. TIMING

FRCDWKSWBK-FEForced Switch of Service from Protection back to Workingfacility due to request from far end.

FFP

FRCDWK-SWBK

Forced Switch of Service from Protection back to Workingfacility.

FFP, LOVCn,VCn

FRCDWKSWPR-FEForced Switch of Service from Working to Protection facilitydie to request from Far End.

FFP

FRCDWKSWPR-RINGForced Working Switch to Protection. This condition indicatesthat a forced ring switch from working channels to protectionchannels is in effect.

FFP

FRCDWKSWPR-RING-FEForced Working Switch to Protection. This condition indicatesthat a forced ring switch from working channels to protectionchannels is in effect as a result of a far-end node's request.

FFP

FRCDWK-SWPR

Forced Switch of Service from Working to Protection facility. FFP, LOVCn,VCn

FRNG-SYNC

Indicates that the system clock is in free runningsynchronization mode.

TIMING

GFPCSF Client Signal Failure on the VCG. Always Service affecting. VCG

GFPEXM Extension Header Mismatch on the VCG. Always Serviceaffecting.

VCG

GFPLOF Loss of GFP alignment on the VCG. Always Serviceaffecting..

VCG

GFPUPM User Payload type Mismatch on the VCG. Always Serviceaffecting..

VCG

1850 TSS-320/TSS-320H/TSS-160 Codes

Release 5.1 (ETSI)September 2017Issue 4 6358DG09603CAAATQZZA

Page 636: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition TypeCodes (continued)

CONDI-TION TYPE

DESCRIPTION EQUIPMENT

HL-DOVRSYNC

Indicates that the system timing is in autonomous holdoversynchronization mode.

TIMING

IPC-PLCON-FAIL

IPCP Line DCC connection failure STMn

IPCP-SCONFAIL

IPCP Section DCC connection failure STMn

L2LCONFAIL Layer 2 Line DCC connection failure: Line DCC can notcommunicate with far-end Line DCC due to data linkconnection problems.

STMn

L2SCONFAIL Layer 2 Section DCC connection failure: Section DCC can notcommunicate with far-end Section DCC due to data linkconnection problems.

STMn

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-FAIL

LCP Line DCC connection failure: Alarm raised afterMAXCONFIG count exhausted.

STMn

LCPSCON-FAIL

LCP Section DCC connection failure: Alarm raised afterMAXCONFIG count exhausted.

STMn

LFD Loss of Frame Delineation GBE10

LFIEGR Local Fault Indicator Egress GBE10

LOCKOUTOFPR-FELock out of Protection facility due to a request from far end. FFP

LOCK-OUTOFPR

Lock out of Protection facility. FFP, LOVCn,VCn

LOCK-OUT-OFTIMREF

Lock out of a Timing Reference from Selection. TIMING

LOCKOU-TOPS

Lockout of Protection Span. This condition indicates that alockout of the use of protection channels is in effect.

FFP

Codes 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

636 Issue 4

Page 637: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition TypeCodes (continued)

CONDI-TION TYPE

DESCRIPTION EQUIPMENT

LOCK-OUTWR

Lockout of working: LOW-R command prevents theaddressed working span from requesting any switch. if it wasin switched state then the switch will be dropped regardless ofthe state of the working

FFP

LOC Loss of CV packets for a period greater than 3.5 theCVprovisioned period

TUSEG

LOF Loss of Frame OTU2, STMn

Indicates that a CRU has detected a Loss of frame for adedicated BITS facility

BITS

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 adedicated BITS facility

BITS

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 affectingcondition.

GBE

Manually Taken out of service ODU2, OTU2,GBE10, GFC10,MAU, LOVCn,VCn, OGPORT,VCG

Indicates that a logical removal was performed on aBITS/timing reference.

BITS, TIMING

1850 TSS-320/TSS-320H/TSS-160 Codes

Release 5.1 (ETSI)September 2017Issue 4 6378DG09603CAAATQZZA

Page 638: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition TypeCodes (continued)

CONDI-TION TYPE

DESCRIPTION EQUIPMENT

MAN-SWTIM-REF

Timing Selection is switched via Manual command to a TimingReference.

TIMING

MANSW-TOINT

Indicates that a manual switch to Internal Timing (i.e. forcedholdover mode) has occurred.

TIMING

MANWKSWBK-FEManual Switch of Service from Protection back to Workingfacility due to a request from far end.

FFP

MANWK-SWBK

Manual Switch of Service from Protection back to Workingfacility.

FFP, LOVCn,VCn

MANWKSWPR-FEManual Switch of Service from Working to Protection facilitydue to a request from far end.

FFP

MANWKSWPR-RING-FEManual Working Switch to Protection. This condition indicatesthat a manual ring switch from working channels to protectionchannels is in effect as aresult of a far-end node's request.

FFP

MANWKSWPR-RINGManual Working Switch to Protection. This condition indicatesthat a manual ring switch from working channels to protectionchannels is in effect.

FFP

MANWK-SWPR

Manual Switch of Service from Working to Protection facility. FFP, LOVCn,VCn

MMG A CV packet with MEL = 0 and an invalid MEG value (that iswith a MEG_ID different from theconfigured MEG_ID at thereceiving MEP) has been received.

TUSEG

OCI Open Connection Indication ODU2

OSIN-LCPLCON-FAIL

OSINLCP Line DCC connection failure STMn

OSINLCP-SCONFAIL

OSINLCP Section DCC connection failure STMn

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

Codes 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

638 Issue 4

Page 639: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition TypeCodes (continued)

CONDI-TION TYPE

DESCRIPTION EQUIPMENT

RNG-SQLCH

Traffic on ring squelched. FFP

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 offthe required accuracy limits

TIMING

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 thesystem is going into holdover.

TIMING

SYNCREF-FAIL

Indicates the timing reference failed. TIMING

SYNCRE-FUNEQ

Indicates the timing reference is unassigned. TIMING

SYNCT4OUT Indicates that timing quality for output timing is insufficient andtherefore squelched

TIMING

T-BBE-HOVC-1-DAY

Indicates a T-BBE-HOVC-1-DAY Threshold Crossing wasdetected

VCnT-BBE-HOVC-15-MIN

Indicates a T-BBE-HOVC-15-MIN Threshold Crossing wasdetected

T-BBE-LOVC-1-DAY

Indicates a T-BBE-LOVC-1-DAY Threshold Crossing wasdetected

LOVCnT-BBE-LOVC-15-MIN

Indicates a T-BBE-LOVC-15-MIN Threshold Crossing wasdetected

1850 TSS-320/TSS-320H/TSS-160 Codes

Release 5.1 (ETSI)September 2017Issue 4 6398DG09603CAAATQZZA

Page 640: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition TypeCodes (continued)

CONDI-TION TYPE

DESCRIPTION EQUIPMENT

T-BBE-MS-1-DAY

Indicates a T-BBE-MS-1-DAY Threshold Crossing wasdetected

STMnT-BBE-MS-15-MIN

Indicates a T-BBE-MS-15-MIN Threshold Crossing wasdetected

T-BBE-ODU-1-DAY

Indicates a T-BBE-ODU-1-DAY Threshold Crossing wasdetected

ODU2T-BBE-ODU-15-MIN

Indicates a T-BBE-ODU-15-MIN Threshold Crossing wasdetected

T-BBE-OTU-1-DAY

Indicates a T-BBE-OTU-1-DAY Threshold Crossing wasdetected

OTU2T-BBE-OTU-15-MIN

Indicates a T-BBE-OTU-15-MIN Threshold Crossing wasdetected

T-BBE-RS-1-DAY

Indicates a T-BBE-RS-1-DAY Threshold Crossing wasdetected

STMnT-BBE-RS-15-MIN

Indicates a T-BBE-RS-15-MIN Threshold Crossing wasdetected

T-CV-PCS-1-DAY

Indicates a CV-PCS Threshold Crossing 1 day was detected

GBE, GBE10,GFC10, MAUT-CV-PCS-

15-MINIndicates a CV-PCS Threshold Crossing 15 min was detected

T-EIFE-1-DAY

Indicates a EIFE Threshold Crossing 1 day was detected

GBE, GBE10,MAUT-EIFE-15-

MINIndicates a EIFE Threshold Crossing 15 min was detected

T-ES-HOVC-1-DAY

Indicates a T-ES-HOVC-1-DAY Threshold Crossing wasdetected

VCnT-ES-HOVC-15-MIN

Indicates a T-ES-HOVC-15-MIN Threshold Crossing wasdetected

Codes 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

640 Issue 4

Page 641: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition TypeCodes (continued)

CONDI-TION TYPE

DESCRIPTION EQUIPMENT

T-ES-LOVC-1-DAY

Indicates a T-ES-LOVC-1-DAY Threshold Crossing wasdetected

LOVCnT-ES-LOVC-15-MIN

Indicates a T-ES-LOVC-15-MIN Threshold Crossing wasdetected

T-ES-MS-1-DAY

Indicates a T-ES-MS-1-DAY Threshold Crossing was detected

STMnT-ES-MS-15-MIN

Indicates a T-ES-MS-15-MIN Threshold Crossing wasdetected

T-ES-ODU-1-DAY

Indicates a ES-ODU Threshold Crossing 1 day was detected

ODU2T-ES-ODU-15-MIN

Indicates a ES-ODU Threshold Crossing 15 min was detected

T-ES-OTU-1-DAY

Indicates a ES-OTU Threshold Crossing 1 day was detected

OTU2T-ES-OTU-15-MIN

Indicates a ES-OTU Threshold Crossing 15 min was detected

T-ES-PCS-1-DAY

Indicates a ES-PCS Threshold Crossing 1 day was detected

GBE, GBE10,GFC10, MAUT-ES-PCS-

15-MINIndicates a ES-PCS Threshold Crossing 15 min was detected

T-ES-RS-1-DAY

Indicates a T-ES-RS-1-DAY Threshold Crossing was detected

STMnT-ES-RS-15-MIN

Indicates a T-ES-RS-15-MIN Threshold Crossing wasdetected

T-FECC-1-DAY

Indicates a FECC Threshold Crossing 1 day was detected

OTU2T-FECC-15-MIN

Indicates a FECC Threshold Crossing 15 min was detected

T-OFS-RS-1-DAY

Indicates a T-OFS-RS-1-DAY Threshold Crossing wasdetected

STMnT-OFS-RS-15-MIN

Indicates a T-OFS-RS-15-MIN Threshold Crossing wasdetected

1850 TSS-320/TSS-320H/TSS-160 Codes

Release 5.1 (ETSI)September 2017Issue 4 6418DG09603CAAATQZZA

Page 642: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition TypeCodes (continued)

CONDI-TION TYPE

DESCRIPTION EQUIPMENT

T-SEFS-PCS-L-1-DAY

Indicates a SEFS-PCS Threshold Crossing 1 day wasdetected

GBE, GBE10,GFC10, MAUT-SEFS-

PCS-L-15-MIN

Indicates a SEFS-PCS Threshold Crossing 15 min wasdetected

T-SES-HOVC-1-DAY

Indicates a T-SES-HOVC-1-DAY Threshold Crossing wasdetected

VCnT-SES-HOVC-15-MIN

Indicates a T-SES-HOVC-15-MIN Threshold Crossing wasdetected

T-SES-HOVC-1-DAY

Indicates a T-SES-LOVC-1-DAY Threshold Crossing wasdetected

LOVCnT-SES-LOVC-15-MIN

Indicates a T-SES-LOVC-15-MIN Threshold Crossing wasdetected

T-SES-MS-1-DAY

Indicates a T-SES-MS-1-DAY Threshold Crossing wasdetected

STMnT-SES-MS-15-MIN

Indicates a T-SES-MS-15-MIN Threshold Crossing wasdetected

T-SES-ODU-L-1-DAY

Indicates a SES-ODU Threshold Crossing 1 day wasdetected

ODU2T-SES-ODU-L-15-MIN

Indicates a SES-ODU Threshold Crossing 15 min wasdetected

T-SES-OTU-L-1-DAY

Indicates a SES-OTU Threshold Crossing 1 day was detected

OTU2T-SES-OTU-L-15-MIN

Indicates a SES-OTU Threshold Crossing 15 min wasdetected

Codes 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

642 Issue 4

Page 643: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition TypeCodes (continued)

CONDI-TION TYPE

DESCRIPTION EQUIPMENT

T-SES-PCS-L-1-DAY

Indicates a SES-PCS Threshold Crossing 1 day was detected

GBE, GBE10,GFC10, MAUT-SES-

PCS-L-15-MIN

Indicates a SES-PCS Threshold Crossing 15 min wasdetected

T-SES-RS-1-DAY

Indicates a T-SES-RS-1-DAY Threshold Crossing wasdetected

STMnT-SES-RS-15-MIN

Indicates a T-SES-RS-15-MIN Threshold Crossing wasdetected

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 aninvalid MEP (that is with a MEP_ID different from theconfigured PeerMEP_ID at the receiving MEP) has beenreceived.

TUSEG

UNP A CV packet with MEL = 0, valid MEG_ID, valid MEP_ID, butwith an invalid CV_Period (that is with a received period valuedifferent from the configured period at the receiving MEP) hasbeen received.

TUSEG

1850 TSS-320/TSS-320H/TSS-160 Codes

Release 5.1 (ETSI)September 2017Issue 4 6438DG09603CAAATQZZA

Page 644: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition TypeCodes (continued)

CONDI-TION TYPE

DESCRIPTION EQUIPMENT

UNPHB A CV packet with MEL = 0, valid MEG_ID, valid MEP_ID, butwith an invalid CV_PHB (that is with a received PHB valuedifferent from the configured PHB at the receiving MEP) hasbeen received.

TUSEG

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 itsmembers are cross connected (ACT/BUSY) and enabled tocarry traffic (VCACT). Always service affecting.

VCG

VCGLPF LCAS protocol failure on the VCG. Always service affecting. VCG

VCGPLC Partial Loss of Capacity on the VCG. Always non-serviceaffecting. Only with LCAS enabled.

VCG

VCGPLM Payload type Mismatch on the VCG. Always Service affecting.Only for GBEVCG.

VCG

VCGRFI Remote failure indication on the VCG. Always non-serviceaffecting. Only with LCAS enabled.

VCG

VCGSSF Server Signal Failure on the VCG while one or more of itsmembers are cross connected (ACT/BUSY) and enabled(VCACT)

VCGServer Signal Failure on the VCG while either none of itsmembers are not cross connected or at least one member iscross connected (ACT/BUSY) but it is not enabled (ACTIDLE)

VCGURU Server Signal Failure on the VCG while one or more of itsmembers are cross connected (ACT/BUSY) and enabled(VCACT) VCG

Underlying Resource Unavailble on the VCG. Hardwarefailure of the equipment providing VCAT function.

Codes 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

644 Issue 4

Page 645: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition TypeCodes (continued)

CONDI-TION TYPE

DESCRIPTION EQUIPMENT

VCLOM Loss of Multiframe on a path facility that is a member of aVCG. Always non-service affecting.

LOVCn, VCn

VCMND The differential delay on a path facility that is a member of aVCG cannot be compensated. Always non-service affecting.

LOVCn, VCn

VCSQM Sequence Number Mismatch on a path facility that is amember of a VCG. Always non-service affecting.

LOVCn, VCn

WKSWBK-FE (Automatic) Switch of Service from Protection back toWorking facility due to a request from far end.

FFP

WKSWBK (Automatic) Switch of Service from Protection back toWorking facility.

FFP, LOVCn,VCn

WKSWPR-FE (Automatic) Switch of Service from Working to Protectionfacility due to a request from far end.

FFP

WKSWPR-RING-FE

Working Switch to Protection: Automatic switch of workingfacility to protection (ring) as a result of a far-end node'srequest.

FFP

WKSWPR-RING

Working Switch to Protection: Automatic switch of workingfacility to protection (ring) as a result of a near-end node'srequest.

FFP

WKSWPR (Automatic) Switch of Service from Working to Protectionfacility.

FFP, LOVCn,VCn

WTR (Automatic) Set on Working path of a SNCP when switching isrevertive and defects have cleared on Working and the Waitto Restore timer is in effect.

LOVCn, VCn

(Automatic) Set on a timing reference and defects havecleared and the Wait to Restore timer is in effect.

TIMONG

Wait to Restore state. A failure has cleared and traffic will berestored to the working side when the revert timer expires

FFP

A.4.3 Transient Condition Type Codes

Refer to Table 39, “Transient Condition Type Codes” (p. 646) for transient condition type codesused in the system.

1850 TSS-320/TSS-320H/TSS-160 Codes

Release 5.1 (ETSI)September 2017Issue 4 6458DG09603CAAATQZZA

Page 646: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 39 Transient Condition Type Codes

CONDI-TION TYPE

CONDITION DESCRIPRTION AID

DORMAN-TUSER

An user remains inactive, without log-on the NE, for aconfigurable interval of time.

SECU

FAIL-TORLSRING

Fail to Release Ring. This condition is set when any legalswitch release requests that a node (near end or far end)cannot complete, such as dropping of the bridge or the switchevent.

FFP

FAIL-TOSWRING

Fail to Switch Ring. This condition is set when any legalswitch request that a node (near end or far end) cannotcomplete, such as failure to bridge, failure to switch, noresponse from the far-end.

FFP

INTRU-SION

Excessive Invalid Login Attempts, or two Consecutive InvalidLogin Attempts before the minimum interval.

SECU

LOGBUF90-SECULOGSECULOG has reached 90% of its max size SECU

LOGBUFOVFL-SECULOGSECULOG has reached its max size, after this event hasbeen sent the SECULOG wraps reducing its size to the 70%of its max size discarding the oldest events (30%)

SECU

PMGLBE-MPTY

Entering the Emtpy state of PM Globale File Collection Shelf

PMGL-BFTR

Entering the file transfer running state of PM Globale FileCollection

Shelf

PMGL-BINPREP

Entering the In Preparation state of PM Globale FileCollection

Shelf

PMGL-BREADY

Entering the Ready state of PM Globale File Collection Shelf

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

Codes 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

646 Issue 4

Page 647: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 40 Notification Codes (continued)

NOTIFICATION CODE DEFINITION

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 acondition is service-affecting or non-service-affecting.

Table 41 Service Affect Codes

NOTIFICATION CODE DEFINITION

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 inunsuccessful 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

1850 TSS-320/TSS-320H/TSS-160 Codes

Release 5.1 (ETSI)September 2017Issue 4 6478DG09603CAAATQZZA

Page 648: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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

Codes 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

648 Issue 4

Page 649: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 42 Response (Error) Codes (continued)

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

1850 TSS-320/TSS-320H/TSS-160 Codes

Release 5.1 (ETSI)September 2017Issue 4 6498DG09603CAAATQZZA

Page 650: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 42 Response (Error) Codes (continued)

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

Codes 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

650 Issue 4

Page 651: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 42 Response (Error) Codes (continued)

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 usedin an unsuccessful response message by the system's Command Parser when a command cannotbe 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

1850 TSS-320/TSS-320H/TSS-160 Codes

Release 5.1 (ETSI)September 2017Issue 4 6518DG09603CAAATQZZA

Page 652: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

A.5 Security

A.5.1

TL1 commands are used to control the 1850 TSS-320, TSS-320H and TSS-160 and to optimize itsoperation and maintenance. Unauthorized use of these commands can degrade or completelydestroy the functionality of the system. Security is concerned with two major sources ofinappropriate use of system commands:

• Intruders who may maliciously take control of the system with the intent of damaging or disablingthe system

• Authorized users who use commands with which they are either unfamiliar or that are outsidetheir scope of responsibility

System security, when properly set up, effectively prevents unauthorized users from accessingsystem commands, responses, and messages. This includes both preventing intruders fromaccessing the system and restricting authorized users from using TL1 commands that are outsidetheir scope of responsibility.

The security scheme is based on setting up security values to restrict access to the system and itsresources. This section describes how the system administrator uses security measures toproactively establish and maintain local security policies and practices.

All new systems are shipped with default security values. Before customizing the security schemeby altering default values, the system administrator should read this section completely. Majortopics 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 portfor ROOT access always with SSH), 23 (port for telnet) and 80 (http) shall be opened. Systemaccess requires every user to correctly enter the ACT-USER command using a valid UID and itscorresponding PID within a preset number of attempts.

To prevent an unauthorized bystander from viewing a user's PID, the TL1 command echoes (as theuser 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 externallink between the user and the LNPT on the system.

When a login is attempted, the system verifies that the command was entered using the correctsyntax and that the UID/PID combination matches encrypted records set up in the internal securitydatabase. If the UID and PID are acceptable, the user can access the system. A message displayswith the date and time of the last successful session and the number of unsuccessful attempts bythat user ID to gain system access since the last successful access.

Security 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

652 Issue 4

Page 653: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 loginintentionally provides no additional information to the user. This prevents an intruder fromdiscovering the ACT-USER command syntax, then repeatedly attempting login until a valid UID andcorresponding 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 asan 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. Usersmust 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 atleast 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. Thisfeature 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. Thisnumber specifies the number of days that a user's PID is aged before the system prompts the userto change to a new password. The user must use the ED-PID command to enter a new PID beforethe grace period ends and the number of extra logins during the grace period expires. The graceperiod is determined by the PCND parameter and the number of extra logins is determined by thePCNN parameter.

1850 TSS-320/TSS-320H/TSS-160 Security

Release 5.1 (ETSI)September 2017Issue 4 6538DG09603CAAATQZZA

Page 654: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

User Control of Password

Authorized users can change their own passwords, using the ED-PID command, at any time beforethe passwords expire. To change the password, the user must be logged into the system using thecurrent UID and PID. To change the PID, the user must know the UID and the old PID. Thisprevents an unauthorized person from inappropriately changing the currently logged-in user'spassword.

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 ofunsuccessful login attempts for a session. The maximum number of invalid login attempts for asession 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, thesystem 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, alarmcondition 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 periodof inactivity. Inactivity is defined as lack of user input. The inactivity interval is provisionable per uservia the User Session Activity Link TimerOut parameter (TMOUT). The longest interval allowed is999 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 toexecute.

The following paragraphs describe system command security and the tasks required to accomplishresource 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 retrieveinformation about the system.

Security 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

654 Issue 4

Page 655: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• PROV (provisioning)—The user may perform non-destructive provisioning of I/O cards, portsand interfaces, initiate test procedures which are not service affecting, and retrieve informationabout the system.

• CONF (configure)—User may configure the system, performing provisioning and testing of all I/Ocards, ports, interfaces, and circuits.

Users may configure all subsystems which do not allow for system wide effect. The user mayperform nondestructive provisioning of I/O cards, ports and interfaces, initiate test procedureswhich are not service affecting, and retrieve information about the system.

• NETADMIN (network administrator)—A network administrator may configure anything in thesystem except user accounts.

• SEC (security administrator)—A user with the security privilege flag may create, delete, andmodify user accounts. A security user need not be a network administrator (but can create useraccounts with network administrator privilege). He/she is able to issue all commands. He/she isnot 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 ofusing 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, bymeans 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 auser enters a restricted command, the comparison fails and the command is denied. This control isestablished 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 asystem security administrator account, commands that directly affect system security cannot beexecuted.

Command Privileges

The NE supports the ability for a user with sufficient Security Level privileges to change theCommand Security Level assigned to a specified external command. The ED-CMD-SECU TL1command provides this functionality.

The security command access privilege level (CAP) of the following commands is SEC and itcannot 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)

1850 TSS-320/TSS-320H/TSS-160 Security

Release 5.1 (ETSI)September 2017Issue 4 6558DG09603CAAATQZZA

Page 656: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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, andanalyze 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 thesecurity 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 toinactivity timeout).

The security log entry contains:

• the identification, address, and security level of the user that initiated the action that is beinglogged.

• 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. Thisprevents 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 preventsanyone, including the security administrator, from tampering with the data in the log. Informationfrom 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 issueappropriate 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 continuouslymonitors selected parameters of incoming traffic, detects errors, counts the detected errors, and

Performance Monitoring 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

656 Issue 4

Page 657: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

reports daily error accumulations and at 15-minute intervals. PM also compares the error countswith user-defined thresholds and issues a REPT EVT (report event) message when any error countcrosses 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 distinguishbetween a system internal failure and an incoming facility failure. Refer to the MonitoredParameters subsection in this section for lists and definitions of the parameters monitored for eachfacility type.

SET-TH-rr commands (where rr is the facility type) are used to define performance parameterthresholds for each circuit. The user can select the parameter type and threshold level, and initializethe error count register on a daily or 15-minute basis. These user-defined thresholds are stored inthe circuit-provisioning database. RTRV-TH-rr commands cause the defined parameter thresholdsto display.

A.6.2 Storage Registers

Refer to Table 44, “Number of Registers for Each PM Parameter Monitored” (p. 656) for a list of thetypes 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 thecount in any of these registers reaches a maximum value, the register remains full until either it isreset or the value is transferred to the Previous register. Current registers initialize in the followingcircumstances:

• 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'svalue then increments from that value as new errors are counted. When the end of the time periodfor the register (1-DAY or 15-MIN) is reached, its count is automatically initialized to 0.

1850 TSS-320/TSS-320H/TSS-160 Performance Monitoring

Release 5.1 (ETSI)September 2017Issue 4 6578DG09603CAAATQZZA

Page 658: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

A.6.4 Validity Flags

Each register marks accumulation data with an associated validity (VLDTY) flag. The system setsthe 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 datacollection 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 dueto:

• Failure (lasting more than 10 seconds) of a module involved in PM collection

• Board initialization (via INIT-SYS) occurs without equipment protection during the accumulationperiod

• 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 shorterthan 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 entireaccumulation 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 theaccumulation 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 accumulatedover 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 descendingorder.

A.6.5 Threshold Registers

Two threshold registers are provided for each parameter monitored; a 15-minute threshold registerand 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.

Performance Monitoring 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

658 Issue 4

Page 659: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 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 thecorresponding threshold register. When a threshold crossing is recognized, Threshold CrossingAlerts (TCAs) are generated using REPT EVT messages.

During an accumulation period, only one TCA is sent for each threshold setting on a Currentregister, unless the Current register is reset or the threshold is increased. In that case, the resetCurrent 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 athreshold 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 orreported. 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 areused 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 asfollows:

• 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 the1850 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

1850 TSS-320/TSS-320H/TSS-160 Performance Monitoring

Release 5.1 (ETSI)September 2017Issue 4 6598DG09603CAAATQZZA

Page 660: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 45 GBE PM Parameters (continued)

Monitored type parameter Definition

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

Monitored type parameter Definition

• 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

Monitored type parameter Definition

• Section Near End

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

Performance Monitoring 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

660 Issue 4

Page 661: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 48 10GBE PM Parameters

Monitored type parameter Definition

• Section Near End

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

• 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

Monitored type parameter Definition

• Section Near End

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

Table 50 STM-n (n = 1, 4, 16, 64) PM Parameters

Monitored type parameter Definition

• 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

1850 TSS-320/TSS-320H/TSS-160 Performance Monitoring

Release 5.1 (ETSI)September 2017Issue 4 6618DG09603CAAATQZZA

Page 662: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 50 STM-n (n = 1, 4, 16, 64) PM Parameters (continued)

Monitored type parameter Definition

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

BBE-RSBackground Block Errors - Near End RegeneratorSection

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

Monitored type parameter Definition

• Path Near End

BBE-HOVC Background Block Errors - Near End Higher Order VCPath

ES-HOVC Error Second - Near End Higher Order VC Path

PJEN-HOVC Negative Pointer Justification Events - Near End HigherOrder VC Path

PJEP-HOVC Positive Pointer Justification Events - Near End HigherOrder VC Path

SES-HOVC Severely Error Second - Near End Higher Order VCPath

UAS-HOVC Unavailable Seconds - Near End Higher Order VC Path

• Path Far End

BBE-HOVC Background Block Errors - Far End Higher Order VCPath

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

Performance Monitoring 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

662 Issue 4

Page 663: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 51 VC4n (n = 4C, 16C, 64C) PM Parameters (continued)

Monitored type parameter Definition

• Path Bidirectional

BBE-HOVC-EG Background Block Errors - Bidirectional Far End HigherOrder VC Path Egress

BBE-HOVC-FE Background Block Errors - Bidirectional Far End HigherOrder VC Far End

BBE-HOVC-IN Background Block Errors - Bidirectional Far End HigherOrder VC Path Ingress

BBE-HOVC-NE Background Block Errors - Bidirectional Far End HigherOrder VC Near End

ES-HOVC-EG Error Second - Bidirectional Far End Higher Order VCPath Egress

ES-HOVC-FE Error Second - Bidirectional Far End Higher Order VCFar End

ES-HOVC-IN Error Second - Bidirectional Far End Higher Order VCPath Ingress

ES-HOVC-NE Error Second - Bidirectional Far End Higher Order VCNear End

SES-HOVC-EG Severely Error Second - Bidirectional Far End HigherOrder VC Path Egress

SES-HOVC-FE Severely Error Second - Bidirectional Far End HigherOrder VC Far End

ES-HOVC-IN Severely Error Second - Bidirectional Far End HigherOrder VC Path Ingress

SES-HOVC-NE Severely Error Second - Bidirectional Far End HigherOrder VC Near End

UAS-HOVC-BI Unavailable Seconds - Bidirectional Far End HigherOrder VC Path

Table 52 LOVCn (n = 3, 12) PM Parameters

Monitored type parameter Definition

• Path Near End

BBE-LOVC Background Block Errors - Near End Lower Order VCPath

ES-LOVC Error Second - Near End Lower Order VC Path

1850 TSS-320/TSS-320H/TSS-160 Performance Monitoring

Release 5.1 (ETSI)September 2017Issue 4 6638DG09603CAAATQZZA

Page 664: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 52 LOVCn (n = 3, 12) PM Parameters (continued)

Monitored type parameter Definition

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 VCPath

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 LowerOrder VC Path Egress

BBE-LOVC-FE Background Block Errors - Bidirectional Far End LowerOrder VC Far End

BBE-LOVC-IN Background Block Errors - Bidirectional Far End LowerOrder VC Path Ingress

BBE-LOVC-NE Background Block Errors - Bidirectional Far End LowerOrder VC Near End

ES-LOVC-EG Error Second - Bidirectional Far End Lower Order VCPath Egress

ES-LOVC-FE Error Second - Bidirectional Far End Lower Order VCFar End

ES-LOVC-IN Error Second - Bidirectional Far End Lower Order VCPath Ingress

ES-LOVC-NE Error Second - Bidirectional Far End Lower Order VCNear End

SES-LOVC-EG Severely Error Second - Bidirectional Far End LowerOrder VC Path Egress

SES-LOVC-FE Severely Error Second - Bidirectional Far End LowerOrder VC Far End

ES-LOVC-IN Severely Error Second - Bidirectional Far End LowerOrder VC Path Ingress

SES-LOVC-NE Severely Error Second - Bidirectional Far End LowerOrder VC Near End

Performance Monitoring 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

664 Issue 4

Page 665: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 52 LOVCn (n = 3, 12) PM Parameters (continued)

Monitored type parameter Definition

UAS-LOVC-BI Unavailable Seconds - Bidirectional Far End LowerOrder VC Path

Table 53 MAU PM Parameters

Monitored type parameter Definition

• Path Near End

BBE-LOVCBackground Block Errors - Near End Lower Order VCPath

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

BBE-LOVCBackground Block Errors - Far End Lower Order VCPath

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 theirassociated default Command Access Privilege (CAPs). The Security Log column indicates if acommand (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

1850 TSS-320/TSS-320H/TSS-160 Performance Monitoring

Release 5.1 (ETSI)September 2017Issue 4 6658DG09603CAAATQZZA

Page 666: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 54 User Command Privilege Defaults (continued)

Command Code Default Privilege Default SecuLog

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

Performance Monitoring 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

666 Issue 4

Page 667: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 54 User Command Privilege Defaults (continued)

Command Code Default Privilege Default SecuLog

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

1850 TSS-320/TSS-320H/TSS-160 Performance Monitoring

Release 5.1 (ETSI)September 2017Issue 4 6678DG09603CAAATQZZA

Page 668: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 54 User Command Privilege Defaults (continued)

Command Code Default Privilege Default SecuLog

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

Performance Monitoring 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

668 Issue 4

Page 669: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 54 User Command Privilege Defaults (continued)

Command Code Default Privilege Default SecuLog

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

1850 TSS-320/TSS-320H/TSS-160 Performance Monitoring

Release 5.1 (ETSI)September 2017Issue 4 6698DG09603CAAATQZZA

Page 670: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 54 User Command Privilege Defaults (continued)

Command Code Default Privilege Default SecuLog

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

Performance Monitoring 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

670 Issue 4

Page 671: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 54 User Command Privilege Defaults (continued)

Command Code Default Privilege Default SecuLog

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

1850 TSS-320/TSS-320H/TSS-160 Performance Monitoring

Release 5.1 (ETSI)September 2017Issue 4 6718DG09603CAAATQZZA

Page 672: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 54 User Command Privilege Defaults (continued)

Command Code Default Privilege Default SecuLog

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

Performance Monitoring 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

672 Issue 4

Page 673: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 54 User Command Privilege Defaults (continued)

Command Code Default Privilege Default SecuLog

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

1850 TSS-320/TSS-320H/TSS-160 Performance Monitoring

Release 5.1 (ETSI)September 2017Issue 4 6738DG09603CAAATQZZA

Page 674: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 54 User Command Privilege Defaults (continued)

Command Code Default Privilege Default SecuLog

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

Performance Monitoring 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

674 Issue 4

Page 675: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 54 User Command Privilege Defaults (continued)

Command Code Default Privilege Default SecuLog

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

1850 TSS-320/TSS-320H/TSS-160 Performance Monitoring

Release 5.1 (ETSI)September 2017Issue 4 6758DG09603CAAATQZZA

Page 676: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 54 User Command Privilege Defaults (continued)

Command Code Default Privilege Default SecuLog

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

Performance Monitoring 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

676 Issue 4

Page 677: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 54 User Command Privilege Defaults (continued)

Command Code Default Privilege Default SecuLog

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

1850 TSS-320/TSS-320H/TSS-160 Performance Monitoring

Release 5.1 (ETSI)September 2017Issue 4 6778DG09603CAAATQZZA

Page 678: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Performance Monitoring 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

678 Issue 4

Page 679: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

B Equipment Entities

B.1 Equipment provisionable

B.1.1 List

Equipment entity should be provisioned as one of the following:

• protection EC320

• Lower Order Adaptation Card 10G

• 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 Access Card (75 vs 120 ohm)

• 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 (Packet Module 10G)

• MultiService Adaptation Card for ATM (Packet Module 10G - ETSI only)

• Universal GateWay UGW Adaptation Card (Packet Module 10G)

• Packet Module 10x1GbEthernet (Packet Module 10G)

• Packet Module 20x1GbEthernet • Packet Module 1x10GbEthernet (Packet Module 10G)

• Packet Module 2x10GbEthernet • Optical Pre-Amplifer 10G

• Optical Booster 10G Line • Optical Filter and Attenuator (LOFA)

• DWDM Optical Transponder with Colored XFPs

• CWDM Optical Transponder (2.5G) without Optical Protection

• CWDM Optical Transponder (2.5G) with Optical Protection

• CWDM OADM 4ch w/o OSC coupler

• CWDM OADM 4ch w OSC coupler

• CWDM OADM 2ch w/o OSC coupler

• CWDM OADM 2ch w OSC coupler

• CWDM OADM 1ch w/o OSC coupler • CWDM OADM 1ch w OSC coupler

• CWDM Mux/Demux 8ch w/o OSC coupler

• CWDM Mux/Demux 8ch with OSC coupler

1850 TSS-320/TSS-320H/TSS-160 Equipment Entities

Release 5.1 (ETSI)September 2017Issue 4 6798DG09603CAAATQZZA

Page 680: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• CWDM Mux/Demux 2ch with OSC coupler

• CWDM Mux/Demux 1ch with OSC coupler

• DWDM Mux/Demux 8 channels L1 band without S-band input/output

• XFP on 10GSO modules

• SFP on 2G5SO modules

• SFP on 8XSO

• SFP on 10XANY modules

• 1000BASE-BX20 (Upstream and Downstream)

• 1000BASE-BX40 (Upstream and Downstream)

• FE 100BASE-BX20 (Upstream and Downstream)

• OC-48/STM-16 40km BiDi (Upstream and Downstream)

• OC-48/STM-16 15km BiDi (Upstream and Downstream)

• OC-48/STM-16 2km BiDi (Upstream and Downstream) Shelf Types

• UNVRSL320 (Generic 320 type shelf)

• UNVRSL160 (Generic 160 type shelf)

• 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 stillplugged 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, asfollows:

• If PST=IS to OOS-AU

• If PST=OOS to OOS-AUMA

It is mandatory to specify PROVISIONEDTYPE parameter when XFP/SFP is provisioned, todistinguish XFP/SFP specific features (short/long/intraoffice haul, wavelength,...).

It is also possible to specify PROVISIONEDTYPE = ANY-<type>as generic value for SFP/XFP toallow a generic MSA SFP/XFP to work without mismatch alarms. ANY-DATAS is the standard modeof 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 thisparameter.

It is mandatory to specify PROVISIONEDTYPE parameter when a Shelf is provisioned, todistinguish 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, isactivated or not according to the PROVMODE parameter value set with the SET-PRMTR-NEcommand.

Equipment provisionable 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

680 Issue 4

Page 681: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

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 beprovisioned.

Before that can occur

• mandatory equipment entities: an EC320 and dual MT320, MT160, FAN, POW320, TBUSmodules - 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 isthe 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-SEL

TYPE ALLOWEDSFP/XFPPROVISIONED-TYPE

TYPE ALLOWED SFP/XFP PROVISIONED-TYPE

PP1GE N.A NGI N.A. 10-SFP

Colored: SS162C SL162C

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-SFP

Colored: SS162C SL162C

Any data: ANY-DATAS

Electrical: ETHEMR (only 1000MB;Synch not supported)

OptFastEth: 100FXETH

Bidir:

100BX-20 (U/D)

1000BX-20 (U/D)

1000BX-40 (U/D)

1850 TSS-320/TSS-320H/TSS-160 Card vs Allowed SFP/XFP ProvisionedType

Release 5.1 (ETSI)September 2017Issue 4 6818DG09603CAAATQZZA

Page 682: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 55 SFPs and the XFPs ProvisionedType allowed per IOC Card (continued)

IOC CLIENT SIDE LINESIDE

CLNT-SEL

TYPE ALLOWEDSFP/XFPPROVISIONED-TYPE

TYPE ALLOWED SFP/XFP PROVISIONED-TYPE

PP1GESY N.A. NGI N.A. 10-SFP

Colored: SS162C SL162C

Any data: ANY-DATAS

Electrical: ETHEMR (only 1000MB;Synch not supported)

OptFastEth: 100FXETH

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

1P10GSOand1P10GSOE

N.A. NGI N.A. 1-XFP Black&White XI-641 XI-642 XI-643XI-645 XS-641 XS-642 XS-643 XS-645XL-641 XL-643 XV-642 XV-643XP1L12D2

Colored: XL-642C

Any TDM: ANY-OM10G

4P2G5SO N.A. NGI N.A. 4-SFP Black&White SS-161AR SI-161 SS-161SS-162 SL-161 SL-162

Colored: SS162C SL162C

Any TDM: ANY-OM2G5

Bidir: SI-16D SI-16U SS-16D SS-16USL-16D SL-16U

8PSO N.A. NGI N.A. 8-SFP Black&White: SI-11 SS-11 SL-11 SL-12SS-41 SL-41 SL-42

Any TDM: ANY-OM155 ANY-OM622

Bidir: 100BX-20 (U/D) 1000BX-20 (U/D)1000BX-40 (U/D)

MTSYNTH4 (*)

N.A. To beadded

N.A. 2-SFP Black&White: SS-41

Card vs Allowed SFP/XFP ProvisionedType 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

682 Issue 4

Page 683: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 55 SFPs and the XFPs ProvisionedType allowed per IOC Card (continued)

IOC CLIENT SIDE LINESIDE

CLNT-SEL

TYPE ALLOWEDSFP/XFPPROVISIONED-TYPE

TYPE ALLOWED SFP/XFP PROVISIONED-TYPE

MRSOE N.A. NGI N.A. 4/8-SFP

Black&White: SI-11 SS-11 SL-11 SL-12SS-41 SL-41 SL-42 SS-161AR SI-161SS-161 SS-162 SL-161 SL-162

Colored: SS162C SL162C

Any TDM: ANY-OM155 ANY-OM622ANY-OM2G5

Bidir: 100BX-20 (U/D) 1000BX-20 (U/D)1000BX-40 (U/D) SI-16D SI-16U SS-16DSS-16U SL-16D SL-16U

10XANY N.A. NGI N.A. 10-SFP

Black&White: SL-12 SS-41 SL-41 SL-42SS-161AR SI-161 SS-161 SS-162SL-161 SL-162 Colored: SS162CSL162C

Any TDM: ANY-OM155 ANY-OM622ANY-OM2G5 Any data: ANY-DATAS

Any fiber channel: ANYFC 10GB 10 xFC-2/FC-4

SI-FC4AR FC/2FC/4FC SN-I 850 nm port

SL-FC4AR FC/2FC/4FC LC-L 1310 nmport

OptFastEth: 100FXETH

Bidir: SI-16D SI-16U

SS-16D SS-16U SL-16D SL-16U100BX-20 (U/D) 1000BX-20 (U/D)1000BX-40 (U/D)

OT2TDM N.A. NGI N.A. 1-TUNABLEMSA

Lambda Value

OT2TDMXB

N.A. NGI N.A. 1-XFP Colored: XL-642C

1850 TSS-320/TSS-320H/TSS-160 Card vs Allowed SFP/XFP ProvisionedType

Release 5.1 (ETSI)September 2017Issue 4 6838DG09603CAAATQZZA

Page 684: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 55 SFPs and the XFPs ProvisionedType allowed per IOC Card (continued)

IOC CLIENT SIDE LINESIDE

CLNT-SEL

TYPE ALLOWEDSFP/XFPPROVISIONED-TYPE

TYPE ALLOWED SFP/XFP PROVISIONED-TYPE

DWLA10X [ET-SI]STM64OTU210GBE

1-XFP Black&White:XI-641 XI-642XI-643 XI-645XS-641 XS-642XS-643 XS-645XL-641 XL-643XV-642 XV-643XP1L12D2

Colored: XL-642C

Any TDM:ANY-OM10G Anydata: ANY-DATAX(*) (*): Only forCLNTSEL=[]10GBE.

1-XFP Colored: XL-642C

CWLA3(OP)

[ET-SI]STM16

2-SFP Black&White:SS-161AR SI-161SS-161 SS-162SL-161 SL-162

Colored: SS162CSL162C

Any TDM:ANY-OM2G5

Bidir: SI-16DSI-16U SS-16DSS-16U SL-16DSL-16U

2-SFP Colored: SS162C SL162C

Note: (*) MTSYNTH4 and its SFPs are in this Table only for reference: they really areautomatically provisioned at Drop Shelf Creation, and so not provisionable with ENT-EQPTcommand

B.2.2 Any-xx ProvisionedType vs ActualType

The table below specifies the ANY-xx ProvisionedTypes of the SFP/XFP for not having anymismatch with the physically plugged one:

Card vs Allowed SFP/XFP ProvisionedType 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

684 Issue 4

Page 685: TL1 User Provisioning Guide 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 Card vs Allowed SFP/XFP ProvisionedType

Release 5.1 (ETSI)September 2017Issue 4 6858DG09603CAAATQZZA

Page 686: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

B.2.3 1850 TSS-160 Supported Modules

Table 56 1850 TSS-160 Supported Modules

MODULE FUNCTION SIZEREQUIRED/OPTIONAL

CARD SLOTS

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

0/16 12 to 19 - 29 to 36

4P2G5SO 4x2.5G Sysnc Optical H

8PSO 8x155/622M Sysnc Optical H

OTU-2 1xOTU-2 port slim H

10XANY 10XANY H

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

12 to 19PP10GE 10x1GE Packet module F

PP10ADAdaptation Card PacketModules 10G

F

LOFA1111 Optical Amplifier 17 dBm F0/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-160shelf showing slot locations.

Card vs Allowed SFP/XFP ProvisionedType 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

686 Issue 4

Page 687: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

B.2.4 1850 TSS-320 Supported Modules

Table 57 1850 TSS-320 Supported Modules

MODULE FUNCTION SIZEREQUIRED/OPTIONAL

CARD SLOTS

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

Figure 37 1850 TSS-160 Shelf Slot Locations

40

Fan Tray

Quad area (ROADM)

19 36

18 35

17 34

16 33

1 (MAIN) 20 (SPARE)

42-43

15 32

14 31

13 30

12 29

3937

11

1041

Fan Tray

1850 TSS-320/TSS-320H/TSS-160 Card vs Allowed SFP/XFP ProvisionedType

Release 5.1 (ETSI)September 2017Issue 4 6878DG09603CAAATQZZA

Page 688: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 57 1850 TSS-320 Supported Modules (continued)

MODULE FUNCTION SIZEREQUIRED/OPTIONAL

CARD SLOTS

1P10GSO 1x10G Sysnc Optical H

0/3202 to 09 - 12 to 19- 21 to 28 - 29 to36

4P2G5SO 4x2.5G Sysnc Optical H

8PSO 8x155/622M Sysnc Optical H

OTU-2 1xOTU-2 port slim H

10XANY 10XANY H

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

LOA10G Lower Order adapter 10G H 0/621, 22, 24, 33, 35,36

PP1GE 1x10GE Packet module F

0/16 02 to 09 - 12 to 19PP10GE 10x1GE Packet module F

PP10ADAdaptation Card PacketModules 10G

F

Card vs Allowed SFP/XFP ProvisionedType 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

688 Issue 4

Page 689: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 57 1850 TSS-320 Supported Modules (continued)

MODULE FUNCTION SIZEREQUIRED/OPTIONAL

CARD SLOTS

CWLA3 Dual CWLA3 card N

0/8 06 to 09 - 12 to 15

CWLA3OP Dual CWLA3OP card N

CMDX8 2-fiber 8-channel MDX2 N

CMDX8S2-fiber 8-channel MDX2 w/1310 filter

N

CMDX1S2-fiber 1 channel MDX w/1310 filter

N

CMDX2S2-fiber 2-channel MDX w/1310 filter

N

CADM1OADM 1 channel (1470to1610 nm)

N

CADM1SOADM2 1 channel (1470 to1610 nm)

N

CADM2OADM 2-channel (1470 to1610 nm)

N

CADM2SOADM2 2-channel (1470 to1610 nm)

N

CADM4OADM 4-channel (1470 to1610 nm)

N

CADM4S OADM 4-channel (1470 to1610 nm) w/ 1310 nm filter

N

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-320shelf showing slot locations.

1850 TSS-320/TSS-320H/TSS-160 Card vs Allowed SFP/XFP ProvisionedType

Release 5.1 (ETSI)September 2017Issue 4 6898DG09603CAAATQZZA

Page 690: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 58 Supported SFP/XFP Optics Modules - Line Side

UnitLINE Side

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

Figure 38 1850 TSS-320 Shelf Slot Locations

10 11

12 13 14 15 16 17 18 19

29 30 31 32 33 34 35 36

2 3 4 5 6 7 8 9

21 22 23 24 25 26 27 28

1

20

37

39

38

41

40

Access Shelf Interconnection PanelM

AIN

SP

AR

E

Upper FanTray

Lower FanTray

Quad area (ROADM)

Card vs Allowed SFP/XFP ProvisionedType 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

690 Issue 4

Page 691: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 58 Supported SFP/XFP Optics Modules - Line Side (continued)

UnitLINE Side

Q.ty & Type Allowed Type

1P10GSO 1-XFP Black&White: XI-641, XI-642, XI-643, XI-645,XS-641, XS-642, XS-643, XS-645, XL-641, XL-642,XL-643, XV-642, XV-643

Colored: XL-642C

Any TDM: ANY-OM10G

4P2G5SO 4-SFP Black&White: SS-161AR, SI-161, SS-161, SS-162,SL-161, SL-162

Colored: SS162C, SL162C

Any TDM: ANY-OM2G5

8PSO 8-SFP Black&White: SI-11, SS-11, SL-11, SL-12, SS-41,SL-41, SL-42

Any TDM: ANY-OM155, ANY-OM622

10XANY 10-SFP Black&White: SI-11, SS-11, SL-11, SL-12, SS-41,SL-41, SL-42, SS-161AR, SI-161, SS-161, SS-162,SL-161, SL-162

Colored: SS162C, SL162C

Any TDM: ANY-OM155, ANY-OM622, ANY-OM2G5

Any data: ANY-DATAS

Any fiber channel ANYFC 10GB 10 x FC-2/FC-4

SI-FC4AR FC/2FC/4FC SN-I 850 nm port

SL-FC4AR FC/2FC/4FC LC-L 1310 nm port

Electrical: ETHEMR

OptFastEth: 100FXETH

OT2TDM 1-TUNABLE MSA Lambda Value

DWLA10X 1-XFP Colored: XL-642C

CWLA3(OP) 2-SFP Colored: SS162C, SL162C

1850 TSS-320/TSS-320H/TSS-160 Card vs Allowed SFP/XFP ProvisionedType

Release 5.1 (ETSI)September 2017Issue 4 6918DG09603CAAATQZZA

Page 692: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Table 59 Supported SFP/XFP Optics Modules - Client Side

UnitCLIENT Side

Q.ty & Type Allowed Type

DWLA10X 1-XFP Black&White: XI-641, XI-642, XI-643, XI-645,XS-641, XS-642, XS-643, XS-645, XL-641, XL-642,XL-643, XV-642, XV-643

Colored: XL-642C

Any TDM: ANY-OM10G

Any data: ANY-DATAX (Only for CLNTSEL=[]10GBE)

CWLA3(OP) 2-SFP Black&White: SS-161AR, SI-161, SS-161, SS-162,SL-161, SL-162

Colored: SS162C, SL162C

Any TDM: ANY-OM2G5

B.3 AIDs

B.3.1

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)

AIDs 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

692 Issue 4

Page 693: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• BOOST-{1-7}-{1-9}-{2-9,12-19,21-36} (Booster)

• LOFA-{1-7}-{1-9}-{6-9,12-15} (Line Optical Filter and Attenuator)

• DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} (DWDM Optical Transponder)

• CWLA-{1-7}-{1-9}-{6-9,12-15} (CWDM Optical Transponder)

• CADM-{1-7}-{1-9}-{6,7,8,9,12,13,14,15} (CWDM OADM)

• CMDX-{1-7}-{1-9}-{6-9,12-15} (CWDM MUX/DEMUX)

• OMDX8-{1-7}-{1-9}-{6-9,12-15} (DWDM MUX/DEMUX 8 channels)

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

• PPUGW-{1-7}-{1-9}-{2-9,12-19} (Universal GateWay Card Packet Module 2e5G)

• PP1GE-{1-7}-{1-9}-{2-9,12-19} (Packet Module 10x1Gb)

• PP1GEX20-{1-7}-{1-9}-{2-9,12-19} (Packet Module 20x1Gb)

• PP10GE-{1-7}-{1-9}-{2-9,12-19} (Packet Module 1x10Gb)

• PP10GEX2-{1-7}-{1-9}-{2-9,12-19} (Packet Module 2x10Gb)

• SFP-{1-7}-{1-9}-{2-9,12-19}-{1-10} (SFP on PP10 modules)

• SFP-{1-7}-{1-9}-{2-9,12-19}-{1-20} (SFP on PP20x1 modules)

• XFP-{1-7}-{1-9}-{2-9,12-19}-1 (XFP on PP10GE modules)

• XFP-{1-7}-{1-9}-{2-9,12-19}-{1-2} (XFP on PP2x10GE modules)

• XFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-2} (XFPs on DWLA10X Transponder)

• P42E1-{1-7}-{1-9}-{1-6} (1646DS 42XE1/T1 Card)

• SFP-{1-7}-{1-9}-{7}-{1} (1646DS 1XSTM1/STM4/STM16 Sub-module - Main position)

B.4 Provisioned Types

B.4.1

The Nokia mnemonic stored in the Remote Inventory EPROM for the given equipment. It ismandatory to specifiy this parameter for XFP/SFP modules (ANY-<type> is used for generic MSAXFP/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

1850 TSS-320/TSS-320H/TSS-160 Provisioned Types

Release 5.1 (ETSI)September 2017Issue 4 6938DG09603CAAATQZZA

Page 694: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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

• ANYFC 10GB 10 x FC-2/FC-4

• 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

• SL-12 Long Haul STM-1 (wl1550) B&W for STM-1 port

• SS-41 Short Haul STM-4 (wl1310) B&W for STM-4 port

• SL-41 Long Haul STM-4 (wl1310) B&W for STM-4 port

• SL-42 Long Haul STM-4 (wl1550) 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

• SL-161 Long Haul STM-16 (wl1310) B&W for STM-16 port

• SL-162 Long 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

Provisioned Types 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

694 Issue 4

Page 695: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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

• CADM2 CWDM OADM 2ch w/o OSC coupler

• CADM2S CWDM OADM 2ch w OSC coupler

• CADM1 CWDM OADM 1ch w/o OSC coupler

• CADM1S CWDM OADM 1ch w OSC coupler

• CMDX8 CWDM Mux/Demux 8ch w/o OSC coupler

• CMDX8S CWDM Mux/Demux 8ch with OSC coupler

• CMDX2S CWDM Mux/Demux 2ch with OSC coupler

• CMDX1S CWDM Mux/Demux 1ch 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

1850 TSS-320/TSS-320H/TSS-160 Provisioned Types

Release 5.1 (ETSI)September 2017Issue 4 6958DG09603CAAATQZZA

Page 696: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

• 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)

Provisioned Types 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

696 Issue 4

Page 697: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Glossary

Numerics

1+1The 1+1 protection switching architecture protects against failures of the optical transmit/receiveequipment and their connecting fiber facility. One bidirectional interface (two fibers plus associated OLIUson each end) is designated "service," and the other is designated "protection." In each direction, identicalsignals are transmitted on the service and protection lines ("dual-fed"). The receiving equipment monitorsthe 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 linescould be active at the same time (service in one direction, protection in the other).

A

ACAlarm Cutoff

ACDAccess Control Domain

ACOAlarm Cutoff and Test

ACT-Activate command

ActiveActive identifies a 1+1 protected line which is currently selected by the receiver at either end as thepayload carrying signal or a 1x1 or 1xN protected circuit pack that is currently carrying service. (SeeStandby).

AIDAccess Identifier

AISAlarm Indication Signal

AIS (Alarm Indication Signal)A code transmitted downstream in a digital network that shows that an upstream failure has beendetected and alarmed.

ALW-Allow command

ANSIAmerican National Standards Institute

APSAutomatic Protection Switch

ARPAddress Resolution Protocol

1850 TSS-320/TSS-320H/TSS-160 Glossary

Release 5.1 (ETSI)September 2017Issue 4 6978DG09603CAAATQZZA

Page 698: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

ASCIIAmerican 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 associatedequipment.

AUTOAutomatic

AUTOOne possible state of a service interface port. In this state, the port will automatically be put "in service" ifa good incoming signal is detected on the port.

Automatic Protection SwitchA feature that allows another synchronization source to be automatically selected and thesynchronization source provisioning to be automatically reconfigured in the event of a synchronizationsource failure or network synchronization change, for example, a fiber cut.

Available TimeIn performance monitoring, the 1-second intervals.

B

BERBit Error Ratio

BER (Bit Error Ratio)The ratio of bits received in error to the total bits sent.

BIPBit Interleaved Parity

BIP (Bit Interleaved Parity)A method of error monitoring over a specified number of bits, that is BIP-3 or BIP-8.

BITSBuilding Integrated Timing Supply

BITS (Building Integrated Timing Supply)A single clock that provides all the DS1 and DS0 synchronization references required by clocks in abuilding.

BPBackplane Error

BRIBasic Rate Interface

BroadbandAny communications channel with greater bandwidth than a voice channel; sometimes usedsynonomously with wideband. Also refers to signals at the DS3/E3 (44.736 Mb/s) and higher. Widebandrefers to lower rates (i.e. DS1, VT1.5, etc.).

C

Glossary 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

698 Issue 4

Page 699: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

CACCarrier Access Code

CANC-Cancel command

CBSCommitted Burst Size

CCClear Channel

CCITTInternational Telephone and Telegraph Consultative Committee

CCITT (International Telephone and Telegraph Consultative Committee)An international advisory committee under United Nations' sponsorship that has composed andrecommended for adoption worldwide standards for international communications. Recently changed tothe International Telecommunications Union Telecommunications Standards Sector (ITU-TSS).

CCTCross-connection Type.

CIRCommitted Information Rate

CKTIDFROM and TO Circuit ID

CLICommand Line Interface

CLKClock

CMISECommon Management Information Service Element

CMOSComplementary Metal Oxide Semiconductor

CNVT-Convert command

CPControl Plane

CRCritical (alarm status)

CRSCross Connection

CVCode Violations

CV (Coding Violation)A performance monitoring parameter.

1850 TSS-320/TSS-320H/TSS-160 Glossary

Release 5.1 (ETSI)September 2017Issue 4 6998DG09603CAAATQZZA

Page 700: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

CVFE (Coding Violation Far-End)An indication returned to the transmitting terminal that an errored block has been detected at thereceiving terminal.

CWDMCoarse Wavelength Division Multiplexing

D

DBData Base

DCCData Communications Channel

DCC (Data Communications Channel)The embedded overhead communications channel in the line. It is used for end-to-end communicationsand maintenance. It carries alarm, control, and status information between network elements in anetwork.

DCEData Communications Equipment

DCE (Data Communications Equipment)In a data station, the equipment that provides the signal conversion and coding between the dataterminal equipment (DTE) and the line. The DCE may be separate equipment or an integral part of theDTE or of intermediate equipment. A DCE may perform other functions usually performed at the networkend of the line.

Default ProvisioningThe parameter values that are preprogrammed as shipped from the factory.

DemultiplexingA process applied to a multiplexed signal for recovering signals combined within it and for restoring thedistinct individual channels of these signals.

DEMUXDemultiplexer

Digital MultiplexerEquipment that combines time-division multiplexing several digital signals into a single composite digitalsignal.

DLPDetailed Level Procedure

DLT-Delete command

DRIDual Ring Interworking

DRI (Dual Ring Interworking)Two ring networks interconnected at two common nodes.

Glossary 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

700 Issue 4

Page 701: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

Drop and ContinueA technique that allows redundant signal appearances at two central offices in a DRI network, allowingprotection against central office failures.

DTDistant Terminal

DTEData 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.

DWDMDense Wavelength Division Multiplexing

E

ED-Edit command

EEPROMElectrically-Erasable Programmable Read-Only Memory

EIAElectronic Industries Association

EMCElectromagnetic Compatibility

EMIElectromagnetic Interference

ENT-Enter command

EOOFExcessive Out of Frame

EPROMErasable Programmable Read-Only Memory

EQPTEquipment

EROExplicit Route Object

ESErrored Seconds

ES (Errored Seconds)A performance monitoring parameter.

ESDElectrostatic Discharge

1850 TSS-320/TSS-320H/TSS-160 Glossary

Release 5.1 (ETSI)September 2017Issue 4 7018DG09603CAAATQZZA

Page 702: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

ESFExtended Super Frame

ESF (Extended Super Frame)The format for a DS1 signal.

F

FCCFederal Communications Commission

FEFar 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 IDFar End Identification

FEBEFar 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 thefar end.

FEPROMFlash EPROM

FEPROM (Flash EPROM)Nonvolatile Electrically-erasable Programmable Read-Only Memory.

FERFFar End Receive Failure

FERF (Far End Receive Failure)An indication returned to the transmitting terminal that the receiving terminal has detected an incomingsection failure.

FITFailures in 10-9 hours of operation.

Free RunningAn operating condition of a clock in which its local oscillator is not locked to an internal synchronizationreference and is using no storage techniques to sustain its accuracy.

G

GBEGigabit Ethernet

GNE (Gateway Network Element)A network element that has an active X.25 link. Can also be a DSNE.

Glossary 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

702 Issue 4

Page 703: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

GREGeneric Routing Encapsulation

GUIGraphical User Interface

H

HECIHumans Equipment Catalog Item

HoldoverAn operating condition of a network element in which its local oscillator is not locked to anysynchronization reference but is using storage techniques to maintain its accuracy with respect to the lastknown frequency comparison with a synchronization reference.

I

I/OInput/Output

IC (Internal Clock)Used in synchronization messaging.

IDIdentifier

IDSee shelf ID and site ID.

IECInternational Electrotechnology Commission

IF-IBIn Fiber - In Band

IF-OOBIn Fiber - Out Of-Band

INH-Inhibit command

INIT-Initialize command

IPInternet Protocol

IPIPIP in IP encapsulation

ISIn Service

IS (In Service)One possible state of a DS or DS3/E3 port. Other possible states are "auto" (automatic) and "nmon" (notmonitored).

1850 TSS-320/TSS-320H/TSS-160 Glossary

Release 5.1 (ETSI)September 2017Issue 4 7038DG09603CAAATQZZA

Page 704: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

ISCIIntershelf control Interface

ISDNIntegrated Services Digital Network

ISIIntershelf Interface

ISOInternational Standards Organization

ISPInternet Service Provider

J

JitterTiming jitter is defined as short-term variations of the significant instants of a digital signal from their idealpositions in time.

L

LLine parameters

LANLocal Area Network

LAPDLink Access Procedure "D"

LCASLink Capacity Adjustment Scheme

LEDLight-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 alarmand status condition of the system.

LERLabel Edge Router

LocalSee Near-End.

LOFLoss of Frame

LOF (Loss of Frame)A failure to synchronize to an incoming signal.

LOPLoss of Pointer

Glossary 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

704 Issue 4

Page 705: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

LOSLoss of Signal

LOS (Loss of Signal)The complete absence of an incoming signal.

LPBKLoopback

LSRLabel Switching Router

M

MACMAC layer parameters to be monitored

MAUMedium Access Unit

MDMediation Device

MJMajor Alarm

MNMinor Alarm

MON-Monitor command

MPLSMulti-Protocol Label Switching

MSSPRINGMultiplex Section Switching Protection Ring

MTBFMean Time Between Failures

MultiplexingThe process of combining several distinct digital signals into a single composite digital signal.

MUXMultiplex

N

NENear End

NENetwork Element

NE (Near End)The network element the user is at or working on. Also called local.

1850 TSS-320/TSS-320H/TSS-160 Glossary

Release 5.1 (ETSI)September 2017Issue 4 7058DG09603CAAATQZZA

Page 706: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

NE (Network Element)The basic building block of a telecommunications equipment within a telecommunication network thatmeets 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 accessinterfaces for use by technicians and/or operation systems. In addition, a network element may alsoinclude a time slot interchanger.

NMONNot Monitored (provisioning state)

NNINetwork-Network Interface

NodeA node is a line terminating element.

Non-RevertiveA protection switching mode in which, after a protection switch occurs, the equipment remains in itscurrent configuration after any failure conditions that caused a protection switch to occur clear or afterany external switch commands are reset. See Revertive.

NSANot Service Affecting

NSAPNetwork Services Access Point

NSAP (Network Services Access Point)An address that identifies a network element. Used for maintenance subnetwork communication usingthe OSI protocol.

NTPNetwork Time Protocol

O

OOptical analog parameters

OAM&POperations, Administration, Maintenance, and Provisioning

OF-OOBOut of Fiber -Out Of-Band

OLIUOptical Line Interface Unit

OOFOut of Frame

OPR-Operate command

OSOperations System

Glossary 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

706 Issue 4

Page 707: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

OS (Operations System)A central computer-based system used to provide operations, administration, and maintenance functions.

OSIOpen Systems Interconnection

OSI (Open Systems Interconnection)Referring to the OSI reference model, a logical structure for network operations standardized by theInternation Standards Organization (ISO).

OSPOutside Plant

OSPFOpen Shortest Path First

OTNOptical Transport Node

P

P-bitPerformance Bit

Pass ThroughPaths that are cross-connected directly across an intermediate node in a ring network.

PBSPeak Burst Size

PCPersonal Computer

PCUPower Conversion Unit

PIDPassword Identifier

PINFETPositive Intrinsic Negative Field Effect Transistor

PIRPeak Information Rate

PJCPointer Justification Count

Plesiochronous NetworkA network that contains multiple maintenance subnetworks, each internally synchronous and alloperating at the same nominal frequency, but whose timing may be slightly different at any particularinstant.

PLLPhase-Locked Loop

1850 TSS-320/TSS-320H/TSS-160 Glossary

Release 5.1 (ETSI)September 2017Issue 4 7078DG09603CAAATQZZA

Page 708: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

PMPerformance Monitoring

PM (Performance Monitoring)Measures the quality of service and identifies degrading or marginally operating systems (before analarm would be generated).

POHPath Overhead

POPPoints of Presence

PortThe physical, electrical, or optical interface on a system.

PROTProtection

Protection LineThe protection line is the pair of fibers (one transmit and one receive) that carry the APS channel (K1 andK2 bytes in the line overhead).

PRSPrimary Reference Source

PSTPrimary State

PSUPower Supply Unit

PVCPermanent Virtual Circuit

PWPseudo Wire

PWRPower

PXCPath Cross-Connection

R

RAMRandom Access Memory

RD-Read command

RemoteSee Far-End (FE).

RESTORE-Restore command

Glossary 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

708 Issue 4

Page 709: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

RevertiveA protection switching mode in which, after a protection switch occurs, the equipment returns to thenominal 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 externalswitch commands are reset. See Non-Revertive.

RingA configuration of nodes comprised of network elements connected in a circular fashion. Under normalconditions, each node is interconnected with its neighbor and includes capacity for transmission in eitherdirection between adjacent nodes. Path switched rings use a head-end bridge and tail-end switch. Lineswitched rings actively reroute traffic over a protection line.

RLS-Release command

RMV-Remove command

RS232Serial interface

RST-Restore command

RSVP-TEResource ReserVation Protocol – Traffic Engineering

RTRemote Terminal

RT (Remote Terminal)An unstaffed equipment enclosure that may have a controlled or uncontrolled environment.

RTRV-Retrieve command

S

SSection parameters

SAService Affecting

SDSignal Degrade

SDHSynchronous Digital Hierarchy

SEFSSeverely Errored Frame Seconds

SEOSingle-Ended Operations

1850 TSS-320/TSS-320H/TSS-160 Glossary

Release 5.1 (ETSI)September 2017Issue 4 7098DG09603CAAATQZZA

Page 710: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

SESSeverely Errored Seconds

SES (Severely Errored Seconds)This performance monitoring parameter is a second in which a signal fail occurs, or more than a presetamount of coding violations (dependent on the type of signal) occurs.

SET-Set command

SFSuper Frame

SF (Super Frame)The format for DS1 signals.

SIDSite Identifier

SLAService Level Agreements

SNCPSubNetwork Connection Protection

SPESynchronous Payload Envelope

SSTSecondary State

STA-Start command

StandbyStandby identifies a 1+1 protected line which is not currently selected by the receiver at either end as thepayload carrying signal, or 1x1 or 1xN protected circuit pack that is not currently carrying service. SeeActive.

StatusThe indication of a short-term change in the system.

STMSynchronous Transfer Mode

STP-Stop command

SW-Switch command

SWTCHSwitch

T

Glossary 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

710 Issue 4

Page 711: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

T-MPLSTransport - Multi-Protocol Label Switching

TABSTelemetry Asynchronous Byte Serial (Protocol)

TARPTarget ID Address Resolution Protocol

TCAThreshold-Crossing Alert

TCA (Threshold Crossing Alert)A condition set when a performance monitoring counter exceeds a user-selected threshold. A TCA doesnot generate an alarm but is available on demand through the CIT and causes a message to be sent toNMA via the TL1 interface.

TCP/IPTransmission Control Protocol/Internet Protocol

TDTraffic Descriptor

TDMTime Division Multiplexing

TIDTarget Identifier

TL1Transaction 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.

TLBTiming Looped Back

TSATime Slot Assignment

TSITime Slot Interchange

TSOTechnical Support Organization

U

UASUnavailable Seconds

UAS (Unavailable Seconds)In performance monitoring, the count of seconds in which a signal is declared failed or, in which, 10consecutively severely errored seconds (SES) occurred, until the time when 10 consecutive non-SESoccur.

1850 TSS-320/TSS-320H/TSS-160 Glossary

Release 5.1 (ETSI)September 2017Issue 4 7118DG09603CAAATQZZA

Page 712: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

UIDUser Identifier

UNIUser Network Interface

UnidirectionalA protection switching mode in which the system at each end of an optical span monitors both serviceand protection lines and independently chooses the best signal (unless overridden by an equipmentfailure or by an external request, such as a forced switch or lockout). In a system that uses unidirectionalline switching, both the service and protection lines may be active simultaneously, with one line carryingtraffic in one direction and other line carrying traffic in the other direction. For a 1+1 protection schemethe K1 and K2 bytes in the line overhead are used to convey to the far end which line the near-endreceiver has chosen, so that an "active" indication may be made at the far end.

UPSRUnidirectional Path Switched Ring

USBUniversal Serial Bus

V

VCGVirtual Concatenation Group

VCnVirtual Container of n order

VLANVirtual Local Area Network

VLSIVery Large Scale Integration

VMViolation Monitor

VoIPVoice over Internet Protocol

VPNVirtual Private Network

VTVirtual Tributary

W

WANWide Area Network

WDMWavelength Division Multiplexing

Z

Glossary 1850 TSS-320/TSS-320H/TSS-160

8DG09603CAAATQZZA

Release 5.1 (ETSI)September 2017

712 Issue 4

Page 713: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

ZICZero Installation Craft terminal

1850 TSS-320/TSS-320H/TSS-160 Glossary

Release 5.1 (ETSI)September 2017Issue 4 7138DG09603CAAATQZZA

Page 714: TL1 User Provisioning Guide Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 (ETSI) TL1 User Provisioning Guide 8DG09603CAAATQZZA Issue 4 September 2017

IndexA

administerGBE loopback 183GBE10 loopback 179MAU loopback 195STMn/OCn loopback 241

Autonegotation 577

I

In-Fiber/In-BandIF-IB 587

L

LAGAggregation Ports 602

M

MAU 593

1850 TSS-320/TSS-320H/TSS-160

Release 5.1 (ETSI)September 2017

714 Issue 48DG09603CAAATQZZA