GDM G30fp040!02!0a User Guide

User Guide (UG)
Groove™ G30
FP 4.0
Revision A, April 2019
GDM-G30FP040-02-0A
Coriant is continually striving to reduce the adverse environmental effects of

its products and services. We would like to encourage you as our customers
and users to join us in working towards a cleaner, safer environment. Please
recycle product packaging and follow the recommendations for power use
and proper disposal of our products and their components.
The information in this document is subject to change without notice and describes only the product
defined in the introduction of this documentation. This documentation is intended for the use of Coriant
customers only for the purposes of the agreement under which the document is submitted, and no part of
it may be used, reproduced, modified or transmitted in any form or means without the prior written permis-
sion of Coriant. The documentation has been prepared to be used by professional and properly trained
personnel, and the customer assumes full responsibility when using it. Coriant welcomes customer
comments as part of the process of continuous development and improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity, or perfor-
mance of the mentioned hardware or software products are given "as is" and all liability arising in connec-
tion with such hardware or software products shall be defined conclusively and finally in a separate
agreement between Coriant and the customer. However, Coriant has made all reasonable efforts to
ensure that the instructions contained in the document are adequate and free of material errors and omis-
sions. Coriant will, if deemed necessary by Coriant, explain issues which may not be covered by the docu-
ment. Coriant will correct errors in this documentation as soon as possible.
IN NO EVENT WILL CORIANT BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY
DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE,
BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE
USE OF THIS DOCUMENT OR THE INFORMATION IN IT.
FCC Notification Statement Federal Communications Commission (FCC) Rules require that you be notified of the following:
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant
to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful
interference when the equipment is operated in a commercial environment. This equipment generates,
uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruc-
tion manual, may cause harmful interference to radio communications. Operation of this equipment in a
residential area is likely to cause harmful interference in which case the user will be required to correct the
interference at their own expense.
Changes or modifications not expressly approved by Coriant Operations, Inc., in writing can void the user’s
authority to operate the equipment.
Industry Canada Notification Industry Canada interference-causing equipment regulations require that you be notified of the following:
Statement This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
Voluntary Control Council for
Interference (VCCI)
Copyright Statement This manual is protected by U.S. and international copyright laws, conventions, and treaties. Your right to
use this manual is subject to limitations and restrictions imposed by applicable licenses and copyright laws.
Unauthorized reproduction, modification, distribution, display or other use of this manual may result in
criminal and civil penalties.
Trademark Notice The following trademarks and service marks are owned by Coriant Operations, Inc., or its affiliates in the
United States and/or other countries: Coriant®, Coriant CloudWave™, Coriant Dynamic Optical Cloud®,
Coriant Groove™, Coriant Transcend®, mTera®, Nano™, Pico™, and the Coriant Logos. Any other company
or product names may be trademarks of their respective companies.
Important Notice on Product This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Safety Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and
only after having carefully read the safety information applicable to this product.
The safety information is provided in the “Safety Instructions”, part of this document or documentation set.
The same text in German:
Wichtiger Hinweis zur Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahren-
Produktsicherheit quellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und
qualifiziertes Personal unter Beachtung der anwendbaren Sicherheitsanforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ dieses Dokuments oder dieses
Dokumentationssatzes.
Copyright © Coriant 2019. All rights reserved.
GDM-G30FP040-02-0A Page 2 Rev A, April 2019

User Guide (UG)
Table of Contents
This document has 370 pages.
Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2 Safety and compliances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.1 Electrostatic discharge precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Fiber optic safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2.1 Laser safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2.2 Safety precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.3 Optical fiber handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.3 Environmental specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.4 Standard compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3 Introduction to the Groove™ G30 DCI Platform . . . . . . . . . . . . . . . . . . 18

3.1 Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2 Hardware modules and components . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2.1 G30 chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.2.2 G30 FRCU chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2.3 Fan modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.2.4 Power modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.2.5 Pluggable cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.2.5.1 CHM1/CHM1LH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.2.5.2 CHM1G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.2.5.3 CHM2/CHM2LH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2.5.4 CHM2T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.2.5.5 XTM2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.2.5.6 OMD96 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.2.5.7 OMD48-S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.2.5.8 OMD64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.2.5.9 OCC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.3 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.3.1 Physical measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.3.2 Power consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.3.3 Specifications of transponder side optical pluggable modules . . . . . . . 66
3.3.4 Product requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.3.5 MTBF (Mean Time Between Failure) data. . . . . . . . . . . . . . . . . . . . . . . 67
4 Hardware installation and startup procedures . . . . . . . . . . . . . . . . . . . . 71

4.1 Installation pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.1.1 Unpacking and verifying the G30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.1.2 Required materials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.2 Installation procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

User Guide (UG)
4.2.1 Mounting brackets (Applicable only to normal chassis) . . . . . . . . . . . . . 73

4.2.2 Installing the G30 into the rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4.2.2.1 Installing the G30 into the rack for normal chassis . . . . . . . . . . . . . . . . 74
4.2.2.2 Installing the G30 into the rack for FRCU chassis . . . . . . . . . . . . . . . . . 77
4.2.3 Grounding the G30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.2.4 Installing the AC/DC power modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.2.5 Connecting AC/DC power cords to the G30 . . . . . . . . . . . . . . . . . . . . . 87
4.2.6 Checking power LED status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.2.7 Installing the fan modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.2.8 Installing pluggable modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.2.9 Installing the FRCU controller modules (applicable only for FRCU chssis)
91
4.2.10 Installing the optical modules into the pluggable modules. . . . . . . . . . . 92
4.2.11 Connecting fibers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.3 Startup procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4.3.1 Connecting cables for commissioning port . . . . . . . . . . . . . . . . . . . . . . 94
4.3.2 Launching Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.3.3 Configuring IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4.3.4 Configure NE Time and NTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4.3.5 Zero Touch Commissioning (ZTC). . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4.3.5.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.3.5.2 Prepare the DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.3.5.3 Prepare SFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5 G30 system configuration and management . . . . . . . . . . . . . . . . . . . . 103

5.1 DCN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.1.1 DCN over ETH interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.1.2 DCN over General Communication Channel (GCC) . . . . . . . . . . . . . . 103
5.1.3 DCN over OSC with Multi-span application . . . . . . . . . . . . . . . . . . . . . 108
5.1.4 OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.1.5 Typical DCN provision example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
5.1.6 TCP/IP port information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5.1.7 FIPS Compliance Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.2 Transponder/Muxponder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.2.1 Service configuration references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.2.1.1 Card configuration references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.2.1.2 Port configuration references. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5.2.1.3 Addressing transport layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
5.2.1.4 Facility configuration notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
5.2.2 Service configuration via CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
5.2.2.1 CHM1/CHM1G service provision step by step. . . . . . . . . . . . . . . . . . . 127
5.2.2.2 CHM2 service provision step by step. . . . . . . . . . . . . . . . . . . . . . . . . . 128
5.2.2.3 CHM2T service provision step by step . . . . . . . . . . . . . . . . . . . . . . . . 139
5.2.2.4 XTM2 service provision step by step . . . . . . . . . . . . . . . . . . . . . . . . . . 141
5.2.3 Service configuration via TNMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
5.2.3.1 Connecting to an NE via TNMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
5.2.3.2 Operate an NE via TNMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5.2.4 3R regenaration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

User Guide (UG)
5.2.5 Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

5.2.6 Protocol LLDP (Link Layer Discovery Protocol). . . . . . . . . . . . . . . . . . 150
5.2.7 Diagnosis and testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.2.7.1 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.2.7.2 Test signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.2.7.3 Delay measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.2.8 OTU deny behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
5.3 Open Line System (OLS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.3.1 OCC2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.3.1.1 Multi-span OLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5.3.2 Optical Protection Switch (OPS) module . . . . . . . . . . . . . . . . . . . . . . . 156
5.3.2.1 OTS protection provision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5.3.2.2 OMS protection provision. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.3.2.3 OCH protection provision. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5.3.2.4 Client protection provision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
5.3.2.5 OPS related principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
5.3.2.6 Basic configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
5.3.3 PAM4 application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
5.3.3.1 TDCM modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
5.3.3.2 High power EDFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
5.3.3.3 Automatic Power Shutdown (APSD) for Laser Safety . . . . . . . . . . . . . 163
5.3.4 Optical Time Domain Reflectometer (OTDR) . . . . . . . . . . . . . . . . . . . 165
5.3.5 OCM (Optical Channel Monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
5.3.6 OLS fiber connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5.3.7 Full OLS Scenarios Provision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.4 Operation, Administration, Management and Provisioning (OAMP) . . 175
5.4.1 Session management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5.4.1.1 CLI session lock/unlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
5.4.2 User management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
5.4.2.1 TACACS+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
5.4.3 Database Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
5.4.3.1 Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
5.4.3.2 Database Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5.4.4 Software upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5.4.5 Provision rollback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5.4.6 Certification Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
5.4.7 Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
5.4.7.1 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
5.4.7.2 Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
5.4.8 Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
5.4.9 Performance statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
5.4.10 Telemetry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
5.4.11 Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
5.4.11.1 Alarm Report Control (ARC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
5.4.11.2 TTI (Trail Trace Identifier (TTI)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
5.4.11.3 Alarm Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
5.4.12 Warm restart and cold restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

User Guide (UG)
5.4.13 Log management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

5.4.13.1 System logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
5.4.14 File Transfer Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
5.4.14.1 SFTP (Secure File Transfer Protocol) Transfer Function . . . . . . . . . . 240
5.4.14.2 SCP (Security Copy) Transfer Function. . . . . . . . . . . . . . . . . . . . . . . . 240
5.4.14.3 HTTP (Hypertext Transfer Protocol) Transfer Function . . . . . . . . . . . . 241
5.5 System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
5.5.1 Equipment information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
5.5.2 Inventory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
5.5.3 Third party pluggable modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
5.5.4 Temperature readout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
5.6 Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
5.6.1 Interworking with hiT7300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
5.6.2 Interworking with mTera/7100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
6 Upgrade and maintenance tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

6.1 Replacement and after-sale technical support. . . . . . . . . . . . . . . . . . . 249
6.2 Fiber optic cleaning requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
6.2.1 Fiber optic cleaning tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
6.2.2 Fiber optic cleaning materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
6.3 Fiber optic cleaning procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
6.3.1 Cleaning LC connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
6.3.2 Cleaning MPO connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
7.1 Alarms and Possible Recovery Procedures. . . . . . . . . . . . . . . . . . . . . 253
7.2 How to replace failed components. . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
7.2.1 Removing and replacing a power module . . . . . . . . . . . . . . . . . . . . . . 316
7.2.2 Removing and replacing an FRCU controller module . . . . . . . . . . . . . 317
7.2.3 Removing and replacing a fan module . . . . . . . . . . . . . . . . . . . . . . . . 318
7.2.4 Removing and replacing a pluggable module . . . . . . . . . . . . . . . . . . . 319
7.2.5 Removing and replacing an optical module . . . . . . . . . . . . . . . . . . . . . 320
7.2.6 Removing and replacing a failed shelf controller . . . . . . . . . . . . . . . . . 320
7.2.7 Removing and replacing a failed SD card . . . . . . . . . . . . . . . . . . . . . . 323
7.3 LED Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
8 Appendix A: Ordering guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

8.1 Basic Commissioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
9 Appendix B: Specifications for Optical Pluggable Modules . . . . . . . . . 335
10 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
11 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

User Guide (UG) Preface
1 Preface
This operation manual provides technical data, installation procedures, system func-
tions, maintenance, and troubleshooting for the Coriant GrooveTM G30 DCI platform
(hereinafter referred to as the G30).
1.1 Intended audience

This document is intended for personnel responsible for installing, operating, maintain-
ing, and administrating the Groove™ G30 DCI platform.
1.2 Structure of this document

This document comprises the following main chapters:
Chapter Title Subject

Chapter 1 Preface Provides an introduction and overview of
this manual.
Chapter 2 Safety instructions and com- Provides information about safety
pliances instructions and regulatory compliances.
Chapter 3 Introduction to the Groove™ Provides information about hardware and
G30 DCI Platform the role of a G30 in a network. Includes
architectural and functional overview.
Chapter 4 Installation and startup tasks Provides information about how to install
and bring up the G30.
Chapter 5 G30 system provision and Provides information about the G30
management system functions.
Chapter 6 Upgrade and maintenance Provides information about upgrade and
tasks maintenance tasks.
Chapter 7 Troubleshooting Provides procedures for troubleshooting
the most common operational problems
encountered when operating with the
G30.
Chapter 8 Appendix Provides information about ordering the
G30 components and accessories.
Chapter 9 Glossary List of terms and corresponding defini-
tions used in this document.
Chapter 10 Abbreviations Provides a list of the abbreviations used
in this manual.
Table 1 Structure of the document
t Some features described in this documentation set may not be available. In order to
identify the features for a particular release, please refer to the Release Notes delivered
with the product.

1.3 Symbols and conventions

The following symbols and mark-up conventions are used in this document:
Representation Meaning
fDANGER! A safety message indicates a dangerous situation where

personal injury is possible.
fWARNING! The keywords denote hazard levels with the following meaning:
fCAUTION! DANGER! - Indicates a hazardous situation which, if not
avoided, will result in death or serious (irreversible) personal
injury.
WARNING! - Indicates a hazardous situation which, if not
avoided, could result in death or serious (irreversible) personal
injury.
CAUTION! - Indicates a hazardous situation which, if not
avoided, may result in minor or moderate (reversible) personal
injury.
w NOTICE: A property damage message indicates a hazard that may result

in equipment damage, data loss, traffic interruption, and so on.
g A note provides important information related to the topic, for

example, not obvious exceptions to a rule or side effects.
t A tip provides additional information related to the topic which is

not essential in the context, but given for convenience.
Bold • All names of graphical user interface (GUI) objects, such as
windows, field names, buttons, and so on.
Example: Select the Full Screen check box and press OK.
• Terms and abbreviations which are linked to an entry in the
glossary and list of abbreviations respectively.
• Important key words.
Italic • Files, folders, and file system paths.
Example: sftp://username@remoteHostname/userdir/user-
log.log
• Emphasized words.
typewriter • Input to be typed in a command line or a GUI field.
Examples:
ping -t 192.168.0.1
Enter World in the Domain field.
• Output from a command, error messages, content of a status
line, and so on.
• File content, such as program sources, scripts, logs, and set-
tings.
Table 2 List of symbols and conventions

Representation Meaning
<angle brackets> Placeholders, for example as part of a file name or field value.
Examples:
<picture name>.png or <ip address>:<port number>
[square brackets] A key to be pressed on a PC keyboard, for example [F11].
Keys to be pressed simultaneously are concatenated with a “+”
sign, for example [CTRL]+[ALT]+[DEL].
Keys to be pressed one after another are concatenated with
spaces, for example [ESC] [SPACE] [M].
> The greater than symbol “>” is used to concatenate a series of
GUI items in order to depict a GUI path. This is an abridged pre-
sentation of a procedure to be carried out in order to perform an
action or display a window or dialog box.
Examples:
A simple menu path: File > Save as ...
A more complex GUI path:
> Main window > File menu > Change Password command >
Change Password dialog box
x For convenience, card names are sometimes listed with a lower
(in card names) case x variable, in order to concisely represent multiple cards.
Example:
I01T40G-x (is to be interpreted as I01T40G-1 and I01T40G-2)
Table 2 List of symbols and conventions (Cont.)
Screen-shots of the graphical user interface are examples only to illustrate principles.
This especially applies to a software version number visible in a screen-shot.
1.4 History of changes
Issue Issue date Remarks

A April 2019 Initial version
Table 3 History of change

User Guide (UG) Safety and compliances
2 Safety and compliances
2.1 Electrostatic discharge precautions
f WARNING!
Electrostatic discharge (ESD) may damage sensitive electronic components resulting in
a traffic-affecting condition. Ensure that plug-in modules are stored in static preventive
material. Do not touch any components on the modules. Handle modules by the edges
or front panel. Always wear a properly grounded wrist strap when handling, removing,
or inserting a module and when touching the equipment shelves or cables. ESD protec-
tive flooring, used with proper ESD footwear, may be used as an alternative to a wrist
strap. ESD wrist straps and footwear must be checked daily to verify performance.
2.2 Fiber optic safety

Read the following information about fiber optic safety before installing and operating
the G30:
• Laser safety
• Safety precautions
• Optical fiber handling
2.2.1 Laser safety

Laser products are the subject of federal, state, and local regulations. This product
complies with Code of Federal Regulations (CFR), Title 21, Part 1040.10 and 1040.11
except for deviations pursuant to Laser Notice No.50, dated June 24, 2007, Perfor-
mance Standards for Light-Emitting Products as defined by the Department of Health
and Human Services, which operates under the Food and Drug Administration (FDA);
and International Electrotechnical Committee (IEC) 60825-1: Ed. 2 (2007) and IEC
60825-2:2004+A1:2006+A2:2010 as a hazard level 1M laser product. The hazard level
1M is assigned to any accessible location within the Packet Optical Transport equip-
ment. Groove product has been certified to meet hazard level 1M product certification,
detailed instruction please refer to Safety Instruction manual.
The power level of the visible and invisible laser radiation emitted from an unconnected
optical facility receive cable is not under Coriant’s control and may be dangerous. There-
fore, to ensure safety, assume that it is dangerous to your eyesight.
Although the laser transmitter power output levels from Packet Optical Transport equip-
ment are below those known to cause injury to the eye, for example, from accidental
exposure to the end of an optical cable, direct exposure at close distances should
always be avoided. During normal operation, the laser transmitters emit invisible laser
radiation. The following precautions must be strictly observed when working with Packet
Optical Transport equipment.
f DANGER!
Use of controls, or adjustments, or performance of procedures, other than those speci-
fied herein may result in hazardous radiation exposure.

f DANGER!
Class 1M invisible radiation when open. Do not stare into beam or view directly with
optical instruments. Looking into the end of an optical cable or connector can cause per-
manent eye damage.
f DANGER!
Do not tamper with or open sealed module components.
f DANGER!
Invisible laser radiation - do not stare into beam or view directly with optical instruments.
Looking into the end of an optical cable or connector can cause permanent eye damage.
f DANGER!
Viewing the laser output with certain optical instruments (for example, eye loupes, mag-
nifiers, and microscopes) within a distance of 100 mm may pose an eye hazard.
Strictly observe the following precautions when working with the G30:
• Avoid direct exposure to fiber ends or any other portion of the system where the eye
can be exposed to laser light.
• Protect unterminated optical fiber connectors with dust caps at all times.
• Handle optical fibers with care during installation. Position them in a safe and secure
location.
The use of optical instruments with this product will increase eye hazard. Never view any
unterminated optical fiber cable or connector with optical instruments, as viewing with
optics tends to concentrate the radiation energy and thus may increase the potential risk
of injury.
2.2.2 Safety precautions

Only qualified technicians who are knowledgeable and trained in optical safety hazards
can operate, maintain, install, and service the G30. Optical radiation originates from the
optical connectors, or in the case of a cable rupture, the optical fiber ends.
f DANGER!
When inspecting optical fibers or connectors, always use protected optical viewing aids.
For example, fiberscopes and magnifying glasses must be equipped with protective
filters. Use laser safety glasses that are equipped to protect against all possible wave-
length ranges emitting from the equipment.
f DANGER!
The power level of the visible and invisible laser radiation emitted from an unconnected
facility fiber optical cable is not under Coriant’s control and may be dangerous. There-
fore, to ensure safety, assume that it is dangerous to your eyesight and cap or cover all

loose optical cables. As a general practice, never look into any open optical port or end
of a disconnected optical cable.
f DANGER!
Do not examine fiber optic cables when there is a light source present. Before examining
fiber optic cables with protected magnifying lenses or microscopes, perform the follow-
ing actions to prevent accidental exposure to optical radiation:
perform the necessary steps to disable the laser source of the fiber to be examined
disconnect the optical path from all relevant optical modules
Turning off a laser source in Packet Optical Transport equipment disrupts traffic.
f DANGER!
It is implied in the hazard level 1M classification that there is a risk of hazardous optical
radiation during normal operation and maintenance. Viewing the laser output with
certain optical instruments (for example, eye loupes, magnifiers, and microscopes)
within a distance of 100 mm may pose an eye hazard.
The amplifier modules are designed with an automatic power reduction (APR) circuit to
reduce the laser power when a fiber cable is disconnected or a fiber breaks. The APR
will detect an open fiber within 400 msec and reduce the laser power. The APR is not
designed for manual override.
2.2.3 Optical fiber handling

Optical fibers can break into small glass fragments during handling. These small bits of
glass are almost invisible and can cause physical injury.
f DANGER!
Fiber glass fragments can enter the skin and be very difficult to detect and remove. Do
not handle exposed optical fiber with bare hands or touch it to your body. If there is any
suspicion of glass fiber chips in your eye, seek medical attention at once.
To perform procedures other than those specified in the product documentation can
result in hazardous radiation exposure.
Follow these precautions to prevent physical injury when handling optical fiber:
• Avoid looking directly at the fiber connectors.
• If it is required to look at the connectors, perform the following actions to prevent any
hazard:
• Remove the optical modules or ensure the optical modules are not powered at
both the shelf near end and shelf at the fiber path far end.
• Wear laser safety glasses that block all possible wavelength ranges emitting
from the equipment.
• Wear laser safety glasses when installing optical fibers.

• Wash your hands after handling optical fibers.

• Handle optical fibers with extreme care during installation and position the optical
fibers in a safe and secure location.
• Protect unterminated optical fiber connectors with dust caps at all times.
• Perform the necessary steps to disable the laser source, unplug optical modules,
and disconnect optical paths when using protected magnifying lenses or protected
microscopes.
2.3 Environmental specification

The Groove™ G30 is designed to meet both NEBS and ETSI standards and the follow-
ing environmental specifications:
• Environmental operational range in Table 4
• Electromagnetic Compatibility (EMC) in Table 6
• Health and safety in Table 7
The Telcordia references in this section apply to the issues of Telcordia GR-3160-
CORE, “NEBS Requirements for Telecommunications Data Center Equipment and
Spaces,”, “NEBS Requirements: Physical Protection,” and Telcordia GR-1089-CORE,
“Electromagnetic Compatibility and Electrical Safety,” available at the date of product
release.
NEBS environment standard Description

GR-3160-CORE, 3.4.1 Operating Temperature 1)
Maximum Rate of Temperature Change
Operational Humidity
GR-3160-CORE, 3.4.2 Temperature Margin
GR-3160-CORE, 3.4.3 Heat Dissipation and Energy Efficiency
GR-3160-CORE, 3.4.4 Equipment Airflow
GR-3160-CORE, 3.4.5 Fan-Cooled Equipment
GR-3160-CORE, 3.6.1 and 3.6.2 Equipment Handling Criteria
GR-3160-CORE, 3.7 Earthquake and Office Vibration
GR-3160-CORE, 3.8 Acoustic Noise
GR-3160-CORE, 3.9.1 Illumination
Table 4 Environmental Operational Range - AC Groove™ G30
1) Detailed refer to 3.3.4.

NEBS environment standard ETSI Environment standard
- GR-63-CORE, 4.1.1 transportation ETSI 300 019-2-1, T1.1, weather

and storage environmental criteria protected, not temperature-con-
trolled storage locations
- GR-63-CORE, 4.4.5 transportation ETSI 300 019-2-2, T2.3 public trans-
vibration portation
GR-3160-CORE, 3.4.1 GR-63-CORE, 4.1.2 ETSI 300 019-2-3, T3.1 and T3.1E
Operating Temperature and Opera- Operating Temperature and Opera- Temperature-controlled locations
tional Humidity1) tional Humidity1)
GR-3160-CORE, 3.7 GR-63-CORE, 4.4.1 and 4.4.4
Earthquake and Office Vibration earthquake and office vibration
GR-3160-CORE, 3.4.2 GR-63-CORE, 4.1.4 Temperature -
Temperature Margin Margin Evaluation
GR-3160-CORE, 3.4.5 GR-63-CORE, 4.1.5 -
Fan-Cooled Equipment FAN-Cooled Equipment
GR-3160-CORE, 3.4.3 GR-63-CORE, 4.1.6 -
Heat Dissipation and Energy Effi- Heat Dissipation and Energy Effi-
ciency ciency
GR-3160-CORE, 3.4.4 GR-63-CORE, 4.1.8 Equipment -
Equipment Airflow Airflow
GR-3160-CORE, 3.6.1 and 3.6.2 GR-63-CORE, 4.3.1 and 4.3.2 -
Equipment Handling Criteria Equipment handling criteria
GR-3160-CORE, 3.8 GR-63-CORE, 4.6 -
Acoustic Noise Acoustic noise
GR-3160-CORE, 3.9.1 GR-63-CORE, 4.7 Illumination -
Illumination criteria
- GR-63-CORE, 4.5 airborne contam- -
inants
- GR-63-CORE, 4.1.7 -
Surface Temperature
Table 5 Environmental Operational Range - DC Groove™ G30
1) Detailed refer to 3.3.4.
North American Standard GR-3160- European Standard EN 300 386

CORE
FCC part 15, Subpart B radiated emis- EN55022 radiated emissions, Class A
sions, Class A
Table 6 Electromagnetic Compatibility - AC Groove™ G30(EMC)

North American Standard GR-3160- European Standard EN 300 386

CORE
FCC part 15, Subpart B conducted emis- EN55022 conducted emissions, Class A
sions, Class A
IEC 61000-4-2 ESD IEC 61000-4-2 ESD
EN55024, IEC 61000-4-3 radiated IEC 61000-4-3 radiated immunity
immunity
IEC 61000-4-4 EFT IEC 61000-4-4 EFT
IEC 61000-4-5 surge IEC 61000-4-5 surge
EN55024, IEC 61000-4-6 conducted IEC 61000-4-6 conducted immunity
immunity
- IEC 61000-4-11 voltage dips and interrup-
tions
IEC 61000-3-2 harmonic
IEC 61000-3-3 flicker
Table 6 Electromagnetic Compatibility - AC Groove™ G30(EMC) (Cont.)
Description North America standard European standard

Electrical safety UL 60950, CSA22.2 60950 IEC 60950
Laser safety 21 CFR 1040 US FDA EN60825-1 Safety of laser
CDR, Class 1 products Part 1: Equipment
classification, requirements
and users guide safety
IEC 60825-1 ed. 2 (2007)
laser safety
IEC 60825-2
2004+A1:2006+A2:2010
laser safety, Class 1 M
Table 7 Health and safety - AC Groove™ G30
North American North American European Standard EN

Standard GR-3160-CORE Standard 300 386
GR-1089-CORE
FCC part 15, Subpart B EMI emissions section 3.2 EN55022 radiated emis-
radiated emissions, Class FCC part 15, Subpart B, sions, Class A
A Class A
FCC part 15, Subpart B EN55022 conducted emis-
conducted emissions, sions, Class A
Class A
Table 8 Electromagnetic Compatibility - DC Groove™ G30 (EMC)

North American North American European Standard EN

Standard GR-3160-CORE Standard 300 386
GR-1089-CORE
EN55024, IEC 61000-4-6 EMI immunity section 3.3, IEC 61000-4-6 conducted
conducted immunity Class A immunity
EN55024, IEC 61000-4-3 IEC 61000-4-3 radiated
radiated immunity immunity
IEC 61000-4-2 ESD ESD immunity section 2.1 IEC 61000-4-2 ESD
IEC 61000-4-4 EFT Electrical Fast Transient IEC 61000-4-4 EFT
section 2.2
IEC 61000-4-5 surge - IEC 61000-4-5 surge
Section 10 Criteria for DC
power port
Table 8 Electromagnetic Compatibility - DC Groove™ G30 (EMC) (Cont.)
Description North America standard European standard

Electrical safety UL 60950, CSA22.2 60950 IEC 60950
Electrical safety GR-1089-CORE section 7 -
Bonding and Grounding GR-1089-CORE section 9
System fire GR-63-CORE section 4.2
Laser safety 21 CFR 1040 US FDA EN60825-1 Safety of laser
CDRH products Part 1: Equipment
classification, requirements
and users guide safety
IEC 60825-1 ed. 2 (2007)
laser safety
IEC 60825-2
2004+A1:2006+A2:2010
laser safety
Table 9 Health and safety - DC Groove™ G30
2.4 Standard compliance

• The Groove™ G30 complies with the following standards:
North American Standards:
• GR-3160-CORE
• GR-1089-CORE
• GR-63-CORE
• FCC Part 15B (CFR 47)
• UL/CSA 60950-1
• 21 CFR 1040 FDA laser safety

European Standards:
• ETSI 300 386
• IEC/EN 60950-1
• IEC/EN 60825-1/-2
• ETSI 300 019-1/-2/-3

User Guide (UG) Introduction to the Groove™ G30 DCI Platform
3 Introduction to the Groove™ G30 DCI

Platform
3.1 Product Overview

The Coriant Groove™ G30 DCI Platform is an innovative stackable transport solution
for cloud and data center networks that delivers 3.2 terabits of capacity throughput in a
compact 1RU form factor. The Coriant Groove™ G30 DCI Platform enables Wide Area
Network (WAN) cloud connectivity services, including 10G, 40G, and 100G client ser-
vices. Powered by Coriant CloudWave™ Optics, the Coriant Groove™ G30 DCI
Platform supports programmable DWDM line interface bandwidth and performance to
optimize high-capacity transmission from 100G to 600G per wavelength in metro,
regional, or long-haul DCI applications. As a key solution of Coriant Open Line System
(OLS), Coriant Groove™ G30 DCI Platform provides DWDM Optical Multiplexing/De-
multiplexing, optical amplification, tunable dispersion compensation, optical time
domain reflectometer, optical channel monitor, and protection with relevant Optical
Cards.
Figure 1 G30 DCI platform

The G30 delivers the following benefits:
• Enable high speed connectivity to and between data centers.
• Enhance end-user quality of experience with best-in-class connectivity solutions.
• Reduce total cost of ownership via industry-leading low power consumption and
highest density.
• Maximize optical transmission performance in metro, regional, or long-haul DCI
applications.
• Accelerate revenue and service deployment with operational simplicity and open
interfaces.
• Improve service and application performance by extending automation from the
data center to the network.
3.2 Hardware modules and components

The Groove™ G30 includes the following hardware modules and components:
• G30 chassis
• Fan modules

• Power modules
• Pluggable cards
3.2.1 G30 chassis

The Groove™ G30 has 4 universal service slots, slot-1, slot-2, slot-3 and slot-4. Each
slot can support a single width module. Slot 1 and slot 3 can support a double slot
module. Detailed information about the Groove™ G30 slot/ports are described in Table
10 and Table 11.
Figure 2 G30 front view (with normal chassis)
g The blocking of the cold air intake area would cause thermal issues that will impact the
provisioned traffic and potentially damage the product hence may short the life cycle, so:
• User should not attach any label, tap, or glue on the air intake area on sleds.
• User should not cover the air intake area directly with cable/fiber or any other
physical component. The cable/fiber or any other physical component shall be
routed at the front of the chassis not blocking the air intake.
Item Description
slot 1 – slot 4 Slots for pluggable modules. You can order a blank filler plate to fill
the slot when no module is installed. The thermal alarm is raised if
a slot is empty for 30 seconds.
USB USB port.
Eth1 RJ-45 programmable NE interface.
Console RJ-45 console interface.
Table 10 G30 slot description – front panel
Figure 3 G30 rear view

Item Description
RESET • Press for 5 seconds to cold boot the G30.
• Press for 30 seconds to reset the G30 to the factory defaults,
all provisions will be lost.
Eth2 / Eth3 RJ-45 programmable NE interfaces.
Slot 11 Slots for 2 AC power modules or 2 DC power modules.
Slot 6 – Slot 10 Slots for fan modules.
SD card The SD card is pre-installed with the G30 software and should not
be removed when the G30 is powered on.
Table 11 G30 rear slot description – rear panel
3.2.2 G30 FRCU chassis

G30 FP4.0 introduces a new chassis with Field Replaceable Control Unit (FRCU). The
user can press the Pull button to shut down the control unit then pull it out, to realize
traffic hitless removal and replacement of the control unit. Detailed view of FRCU is as
in Figure 4.
Figure 4 G30 FRCU chassis front view

When the user needs to replace/remove the control unit, the user need to press the Pull
button for 5 seconds, after Pull button pressed (at least for 5 seconds), the Active LED
will become flashing green and the software is preparing for shutdown, when Active LED
becomes red, FRCU is ready for pull out.
Figure 5 G30 FRCU chassis rear view

g The user needs to wait for Active LED to become red then pull out control unit, otherwise
it will impact traffic.
Slot 12 and FRCU card are implicitly created once system initialization and not delet-
able. FRCU supports the following generic card functions:
• Temperature monitoring
• Temperature PM
• Inventory Management
3.2.3 Fan modules

The G30 supports 5 fan modules working in 4+1 protection mode (All 5 fans must be
equipped). Slots 6-10 are assigned as fan slots.
Fan modules consist of the control board, fan and fan tray. Fan modules support the fol-
lowing functions:
- Cooling the equipment.
- Monitoring fan operation.
- Adjusting fan speed to extend the fan service life, to reduce noise, and save energy.
- LED fault indication.
Fan speed is automatically adjusted based on ambient measured temperature. The G30
can sustain one fan module failure without impacting NE performance.
g G30 supports fan automatic control. When fully equipped with CHM cards, the fan speed
is 60%. When fully equipped with OLS, the fan speed is 40%.
3.2.4 Power modules

The G30 includes 2 AC/DC power modules in 1+1 redundancy. Slot 5 and slot 11 are
assigned as power module slots. The PSU types include 110V/220V AC and 48V/240V
DC.
The AC/DC power module has its own fan for cooling. Fan speed automatically changes
according to the temperature.
There is one LED on front panel of the power module showing the status of AC/DC
power module.
f WARNING!
Mixed 110V/220V AC, 48V/240V DC PSU is unsupported and such provision is PRO-
HIBITED.
g Do not remove another PSU in 10s after the new PSU powered up during swapping.
3.2.5 Pluggable cards

G30 supports the following pluggable modules. Functions of each pluggable module are
listed in each sub-chapter.
• CHM1/CHM1LH
• CHM1G

• CHM2/CHM2LH
• CHM2T
• XTM2
• OMD96
• OMD48-S
• OMD64
• OCC2
3.2.5.1 CHM1/CHM1LH
CHM1/CHM1LH are transponder cards which can carry maximum 400G’s traffic.
CHM1LH is long haul version of CHM1 and optimizes the performance with the CFP2-
ACO fixed in the card.
Up to 4 single slot CHM1/CHM1LH modules are supported on G30 chassis, each
module has up to 2 x CFP2-ACO and 4 x QSFP28. The CHM1/CHM1LH module port
numbering is shown in Figure 6.
Figure 6 CHM1/CHM1LH port numbering

The following pluggable modules supported by CHM1/CHM1LH are listed in the follow-
ing table.
Cli- Pluggable Module Part Number Form Wave Length Distance

ent/Line Description Factor (nm) 100GBE OTU4
Line side CFP2-ACO GHP ZXS-C20TSTZZ-00 Refer to Table 92, Table 93, Table 94 in 9 Appendix
CFP2-ACO CHP ZXS-C2ACOTZZ-00 B: Specifications for Optical Pluggable Modules.
Table 12 Pluggable modules supported by CHM1 (GLS-G30CHM1Z-00)/CHM1LH (GLS-G30CHM1L-00)


Client side QSFP28 100G SR4 ZXS-Q8S4ZZZZ-00 QSFP28 850 100m.RF1)
QSFP28 100G LR4 ZXS-Q8L4ZZZZ-00 QSFP28 1295.56 10km
(231.4TH)
1300.05
(230.6TH)
1304.58
(229.8TH)
1309.14
(229.0TH)
QSFP28 100G ZXS-Q8CWDM4Z- QSFP28 1271 2km.RF
CWDM4/CLR4 00 1291
1311
1331
QSFP28, 100G ZXS-Q8PSM4ZZ-00 QSFP28 1310 500m.RF
PSM4
QSFP28 ZXS-Q8L4ZZDR-00 QSFP28 1295.56 10km 10km.GF2)
100GBASE-LR4 1300.05
and OTU4 Dual
1304.58
Rate
1309.14
QSFP28 LR4 DR ZXS-Q8L4PRDR-00 QSFP28 1295.56 10km 10km.GF
FPS 1300.05
1304.58
1309.14
QSFP28 SR4 Multi- ZXS-Q8S4ZZMR-00 QSFP28 850 100m.RF 100m.GF
rate(100GbE,
OTU4, 32GFC)
100Gbe, OTU4
QSFP28 Active ZXS-Q8AOCZZZ-03 QSFP28 850 3m.RF
Optical Cable 3m
QSFP28 Active ZXS-Q8AOCZZZ-10 QSFP28 850 10m.RF
Optical Cable 10m


QSFP28 Active ZXS-Q8AOCZDR- QSFP28 850 1m 100m.GF
Optical Cable DR 01
1m
QSFP28 Active ZXS-Q8AOCZDR- QSFP28 850 5m 100m.GF
Optical Cable DR 05
5m
QSFP28 ER4 ZXS-Q8ER4ZZZ-00 QSFP28 1295.56 30km
(30km). SMF fiber. 1300.05
LC connector
1304.58
1309.14

1) RF represents RS FEC for Ethernet.
2) GF represents OTUx7% GFEC.
The CHM1/CHM1LH module could be installed into any slot of slot 1 ~ 4.

The CHM1/CHM1LH module performs the following functions:
• Supports multiplexing up to 4x100G clients into 2x200G Coherent Line Ports
• Supports flexible rates of 100G(DP-QPSK), 200G(DP-16QAM), 300G(DP-8QAM) at
coherent line interfaces
• Supports Generic Mapping Procedure (GMP) mapping 100GBE into ODU4
• Supports multiplexing 100G ODU into ODU4
• Supports ODU4 path delay measurement
• Supports line-side FEC
• Supports Ethernet FEC on the 100GBE client port
• Supports ODUk pseudo random bit sequence (PRBS) testing
• Supports inserting PCS Idle for 100GBE signal testing
• Supports terminal and facility loopbacks on all client and line ports
• Supports standard G.709 trace on ODU and OTU
• Supports line side pluggable CFP2-ACO cold reboot
• Support Client side ALS (Auto Laser Shutdown) on 100 GBE/OTU4 for fault propa-
gation
The CHM1/CHM1LH module supports fixed traffic cross connections from 100GBE
client port to line port, as indicated in the Table 13.
Line port mode Line Port ODU4 ID on the Connected Client

Line Port Port
QPSK (100G) Port 1 ODU4-1 Port 3
Port 2 ODU4-1 Port 5
Table 13 Traffic Table of CHM1 (GLS-G30CHM1Z-00)/CHM1LH (GLS-G30CHM1L-

00)

Line port mode Line Port ODU4 ID on the Connected Client

Line Port Port
16 QAM (200G) Port 1 ODU4-1 Port 3
ODU4-2 Port 4
Port 2 ODU4-1 Port 5
ODU4-2 Port 6
8 QAM (300G) Port 1 ODU4-1 Port 3
(service is carried ODU4-2 Port 4
on both port 1 and
ODU4-3 Port 5
port 2. All ODU4
containers are
associated with
port 1.)
Table 13 Traffic Table of CHM1 (GLS-G30CHM1Z-00)/CHM1LH (GLS-G30CHM1L-

00)
Below in Figure 7 is the Block Diagram of CHM1/CHM1LH module.
Figure 7 Block Diagram of CHM1 (GLS-G30CHM1Z-00)/CHM1LH (GLS-

G30CHM1L-00)
Specifications of CHM1 with GHP/CHP CFP2-ACO are listed in Table 92 and Table 94
in 9 Appendix B: Specifications for Optical Pluggable Modules.
Specifications of CHM1LH with GHP are listed in Table 93 in 9 Appendix B: Specifica-
tions for Optical Pluggable Modules.
3.2.5.2 CHM1G
CHM1G has similar functions with CHM1 except CHM1 does not support encryption.
CHM1GNC is the non-encryption version of CHM1G. CHM1G and CHM1GNC are
green version of CHM1 with lower power consumption comparing with CHM1.
Up to 4 single slot CHM1G modules, each support 2 x CFP2-ACO and 4 x QSFP28. The
CHM1G module port numbering is shown in Figure 8.

Figure 8 Port numbering of CHM1G (GLS-G30CHM1G-00/GLS-G30CHM1G-NC)

Pluggable modules supported by CHM1G/CHM1GNC are almost same with
CHM1(Table 12) except on line side CHM1G/CHM1GNC does not support CFP2-ACO
CHP.
The CHM1G/CHM1GNC modules could be installed into any slot of slot 1 ~ 4.
The CHM1G module performs the following functions:

• Supports multiplexing up to 4x100G clients into 2x200G Coherent Line Ports
• Supports flexible rates of 100G(DP-QPSK), 200G(DP-16QAM) at coherent line
interfaces
• Supports GMP (Generic Mapping Procedure) mapping 100GBE into ODU4
• Supports 100GbE adaption to OPU4/ODU4, and multiplexing ODU4 into ODUC2 in
200G Line mode
• Supports line-side FEC
• Support SDFEC15, SDFEC15ND, STAIRCASE7(7% HD Staircase FEC differ-
ential), G709 FEC(% GFEC differential) on 100G(DP-QPSK) port mode
• Support SDFEC15ND on 200G(DP-16QAM) port mode
• Support OTU4 QPSK Transparent Mode (ext Framer/FEC) on CHM1G (Rev C)
• Supports Ethernet FEC on the 100GBE client port
• Supports G709 or no FEC on the OTU4 client port
• Supports encryption on line ODU4
• Support GCC0 on line OTUC2/OTU4
• Support Client side ALS (Auto Laser Shutdown) on 100 GBE/OTU4 for fault propa-
gation
The CHM1G module supports fixed traffic cross connections from 100GBE client port to
line port which is same with CHM1, refer to Table 13 Traffic Table of CHM1 (GLS-
G30CHM1Z-00)/CHM1LH (GLS-G30CHM1L-00) for detailed information.

Block Diagram of CHM1G module is the same as CHM1’s, please refer to Figure 7 Block
Diagram of CHM1 (GLS-G30CHM1Z-00)/CHM1LH (GLS-G30CHM1L-00).
Specifications of CHM1G with GHP CFP2-ACO are listed in Table 95 and Table 94 in
9 Appendix B: Specifications for Optical Pluggable Modules.
3.2.5.3 CHM2/CHM2LH
CHM2/CHM2LH is transponder card which can carry maximum 400G’s traffic. CHM2LH
is long haul version of CHM2 and optimizes the performance with the CFP2-ACO fixed
in the card.
The G30 has two different version of transponder CHM2 cards, encrypted version (GLS-
G30CHM2Z-00) and unencrypted version (GLS-G30CHM2Z-NC). Up to 2 double slot
CHM2/CHM2LH modules are supported on one chassis, each support 2 x CFP2-ACO
and 4x QSFP28 or 10x QSFP+. One QSFP+ interface can be connected to four 10G
interfaces using a breakout cable or one 40G interface. The CHM2/CHM2LH module
port numbering is shown in Figure 9.
Figure 9 Port numbering of CHM2 (GLS-G30CHM2Z-00/GLS-G30CHM2Z-

NC)/CHM2LH (GLS-G30CHM2L-00)
The following pluggable modules supported by CHM2/CHM2LH are listed in the follow-
ing table.

Pluggable Module Description
Wave Length (nm)

Part Number
Form Factor
Client/Line
OTU2/2e
100GBE
STM64
FC16G
OC192
OTU4
OTU3
FC8G
GBE
GBE
10
40
Line CFP2-ACO ZXS- Refer to Table 92, Table 93, Table 94 in 9 Appendix B: Specifications for Optical
side GHP C20TSTZ Pluggable Modules.
Z-00
CFP2-ACO ZXS-
CHP C2ACOTZ
Z-00
Table 14 Pluggable modules supported by CHM2 (GLS-G30CHM2Z-00/GLS-G30CHM2Z-NC)/CHM2LH (GLS-

G30CHM2L-00)

Wave Length (nm)

Part Number
Form Factor
Client/Line
OTU2/2e
100GBE
STM64
FC16G
OC192
OTU4
OTU3
FC8G
GBE
GBE
10
40
Client QSFP28 100G ZXS- QSFP2 850 100m.
side SR4 Q8S4ZZZ 8 RF1)
Client Z-00
side
QSFP28 100G ZXS- QSFP2 1295.56 10km
LR4 Q8L4ZZZZ 8 (231.4THz
-00 )
1300.05
(230.6THz
)
1304.58
(229.8THz
)
1309.14
(229.0THz
)
QSFP28 100G ZXS- QSFP2 1271 2km.R

CWDM4/CLR4 Q8CWDM 8 1291 F
4Z-00
1311
1331
QSFP28, 100G ZXS- QSFP2 1310 500m.

PSM4 Q8PSM4Z 8 RF
Z-00
QSFP28 ZXS- QSFP2 1295.56 10km 10km.

100GBASE- Q8L4ZZD 8 1300.05 GF2)
LR4 and OTU4 R-00
1304.58
Dual Rate
1309.14
QSFP28 LR4 ZXS- QSFP2 1295.56 10km 10km.

DR FPS Q8L4PRD 8 1300.05 GF3)
R-00
1304.58
1309.14
QSFP+ 40GBE ZXS- QSFP+ 1271 10km

LR 4 QPL4ZZZ 1291
Z-00
1311
1331
QSFP+ 40GBE 81.71T- QSFP+ 850 150m 150m

INTERFACE - Q40GSR4
100m, 10GBE -R6
SR 100m
QSFP+ ZXS- QSFP+ 1310 10km 10km 10km 10km

4x10GBE QPQ10GL
LR/W PSM W-00
QSFP+, 40G ZXS- QSFP+ 850 450m 450m

eSR4, QPS4EZZ
10GBase-SR Z-00

G30CHM2L-00)

Wave Length (nm)

Part Number
Form Factor
Client/Line
OTU2/2e
100GBE
STM64
FC16G
OC192
OTU4
OTU3
FC8G
GBE
GBE
10
40
Client QSFP+, 40G ZXS- QSFP+ 1271 2km
side IR4 QPI4ZZZZ 1291
-00
1311
1331
QSFP+, 81.71T- QSFP+ 1271 10km. 10km 10km

40GBase- Q40GLR4- 1291 GF
LR4(DR), R6
1311
OTU3/OTU2/O
TU2e/OC192 1331
QSFP+, ZXS- QSFP+ 1271 40km

40GBase-ER4 QPE4ZZZ 1291
Z-00
1311
1331
QSFP+, 4x ZXS- QSFP+ 850 12 19

FC8G, 4x QPFCZZM 5 0
FC16G R-00 m m
QSFP28 ZXS- QSFP2 1310 10 10

4x8/16GFC, Q8FCPSM 8 k k
PSM Z-00 m m
QSFP28 SR4 ZXS- QSFP2 850 100m. 100m.

Multi- Q8S4ZZM 8 RF GF
rate(100GbE, R-00
OTU4, 32GFC)
100Gbe, OTU4
QSFP28 Active ZXS- QSFP2 850 3m.R

Optical Cable Q8AOCZZ 8 F
3m Z-03
QSFP28 Active ZXS- QSFP2 850 10m.

Optical Cable Q8AOCZZ 8 RF
10m Z-10
QSFP28 Active ZXS- QSF 850 1m 1m

Optical Cable Q8AOCZD
DR 1m R-01 P28
QSFP28 Active ZXS- QSF 850 5m 5m
Optical Cable Q8AOCZD
DR 5m R-05 P28
QSFP28 ER4 ZXS- QSFP2 1295.56 30km
(30km). SMF Q8ER4ZZ 8 1300.05
fiber. LC con- Z-00
1304.58
nector
1309.14

G30CHM2L-00)

The CHM2/CHM2LH is a double slot module and can be installed into slot 1 and slot 3.
The CHM2/CHM2LH module performs the following functions:
• Supports Multiplexing up to 40x10G, 10x40G, 4x100G clients into to 2x200G
Coherent Line Ports
• Supports flexible rates of 100G(DP-QPSK), 200G(DP-16QAM), 300G(DP-8QAM) at
coherent line interfaces
• Supports Generic Framing Procedure (GFP-F) and GMP mapping modes to map
100GBE into ODU4 on port 4, 5, 9 and 10
g 100GBE GFP-F mapping will not drop errored Ethernet frames to ensure all
Ethernet frames are transported transparently.
• Supports OTU4 client mode on port 4, 5, 9 and 10

• Supports GMP and GFP-F mapping 40GBE into ODU3 on all client ports
• Supports BMP (Bit-synchronous Mapping Procedure) mapping 40GBE into ODU2e
on port 7 and 12 (restricted ports)
• Supports PREAMBLE, GFP-F mapping 10GBE into ODU2 on all sub-ports
• Supports BMP (fixed stuff) mapping 10GBE into ODU2e on all sub-ports
• Supports BMP mapping FC8G/FC16G into ODUflex on all sub-ports
g There have 1us’ latency difference between different ports of FC8G/FC16G for
CHM2/CHM2LH.
g The cross-connection between two ODUflex should be same client-signal-type.
• Supports AMP (Asynchronous Mapping Procedure)/BMP mapping OC192/STM64

into ODU2 on all sub-ports
• Supports ODUk path delay measurement
• Supports SDFEC on the line interface
• Supports G709 and no-FEC FEC modes on OTU4 client interfaces
• Supports G709, I4, I7, and no-FEC FEC modes on OTU2/OTU2e client interfaces
g The I4 and I7 FEC type for OTU2/OTU2e couldn’t work together on four subports of
the same port.
• Supports IDLE Frame testing on Ethernet ports

• Supports FC8G/FC16G/OC192/STM64 pseudo random bit sequence (PRBS)
testing
• Support J0 label trace monitor on OC192/STM64
• Supports LLDP on all 100GBE, 40GBE, 10GBE client ports
• Support Client side ALS (Auto Laser Shutdown) on 10GBE/40GBE/100
GBE/OTU4/FC8G/FC16G/OC192/STM64 for fault propagation

For each CHM2/CHM2LH module the 12 total client ports are separated into two groups,
Group A and Group B. Refer to Figure 10 of the Block Diagram of CHM2/CHM2LH
module for detailed partition of Group A and Group B.
Port 3~7 are in the group A which support ODU cross-connections on Line Port 1 (non-
8QAM); port 8~12 are in the group B which support ODU cross-connections with Line
Port 2 (non-8QAM).
Figure 10 Block Diagram of CHM2/CHM2LH

The supported ODU cross connections are listed as in Table 15.
Line Port ODU4 ID on the Connected Client

Line Port Port
QPSK (100G) Port 1 ODU4-1 Port 3-7
Port 2 ODU4-1 Port 8-12
16 QAM (200G) Port 1 ODU4-1, ODU4-2 Port 3-7
Port 2 ODU4-1, ODU4-2 Port 8-12
8 QAM (300G) Port 1 ODU4-1, ODU4-2 Port 3-7

(Service is carried ODU4-3 Port 8-12
on both port 1 and
port 2. However all
the ODU4 contain-
ers are logically
associated with
port 1 for ease of
provision manage-
ment.)
Table 15 Traffic table of CHM2 (GLS-G30CHM2Z-00/GLS-G30CHM2Z-

NC)/CHM2LH (GLS-G30CHM2L-00)
For 8QAM mode, port 3-7 in group A can be cross-connected with the first two ODU4 of
line side, and port 8-12 in group B can be cross-connected with the third ODU4 of line

side. Each Client port supports to set 40GBE or 10GBE mode independently and
100GBE with group constraints as in Table 16.
The 100GBE/OTU4 client ports share bandwidth with other client ports in the same
group. When port mode of one client port is set as 100GBE/OTU4, the other ports in the
same group should be set as ‘not-available’ and vice versa.The corresponding relation
between the 100GBE/OTU4 client ports and other client ports are listed as in Table 16.
100GBE/OTU4 client port Other client port in same

group
Port 4 Port 3
Port 5 Port 6, 7
Port 9 Port 8, 12
Port 10 Port 11
Table 16 Client Port Group in CHM2 (GLS-G30CHM2Z-00/GLS-

G30CHM2Z-NC)/CHM2LH (GLS-G30CHM2L-00)
g When client ports are provisioned with mixed client types, please pay attention to limita-
tions in the following:
Figure 11 Reference for client ports’ mixed provision - 1
• Each arrowed line indicates a sharing relation between the ports (including their sub-
ports) within the range of the arrowed line.
• Subports of one port shall be same client port type, OC192/STM64 are considered
as the same port type.
• The ports (including their subports) sharing same signal clock type need to be pro-
visioned to be same type of signals. Note that 10/40/100GBE are viewed as same
type.
• The ports (including their subports) sharing 120G bandwidth need to be provisioned
less than 120G.
• The ports (including their subports) sharing 160 tributary slots (ts) need to be provi-
sioned less than 200G.
Bandwidth Type for Occupied tributary slots Signal Types

bandwidth evaluation number
10G 8 10GBE, OC192, FC8G,
7 specially for FC8G OTU2, OTU2e, STM64
Table 17 Reference for client ports’ mixed provision - 2

Bandwidth Type for Occupied tributary slots Signal Types

bandwidth evaluation number
20G 11 FC16G
40G 31 (GMP, GFP-F mapping) 40GBE
32 (4x10G mapping)
100G 80 OTU4, 100GE (Note 1, 2, 3)
Note 1: When calculating restriction of sharing 120G bandwidth, the signals will be
considered as 120G bandwidth type.
Note 2: 100GBE/OTU4 can be set on port 4, 5, 9, 10 only and if only the ports sharing
120G bandwidth with it are not applicable.
Note 3: When port 7 or port 12 is provisioned to 40GBE with 40GBMP-ODU2e
mapping mode, then the port 4 or port 10 cannot be provisioned as 100GBE or OTU4
correspondingly.
Table 17 Reference for client ports’ mixed provision - 2
Specifications of CHM2 with GHP/CHP CFP2-ACO are listed in Table 92, and Table 94
in 9 Appendix B: Specifications for Optical Pluggable Modules.
Specifications of CHM2LH with GHP are listed in Table 93 in 9 Appendix B: Specifica-
tions for Optical Pluggable Modules.
3.2.5.4 CHM2T
CHM2T is transponder card which can carry maximum 1200G’s traffic. Different with line
side optics of other cards, which need to be inserted with line side pluggable modules,
line side optics of CHM2T is built inside the card.
Up to 2 double slot CHM2T modules are supported on one chassis. One QSFP28 plug-
gable module can be inserted to one 100G interfaces. The CHM2T module port num-
bering is shown in Figure 12.
Figure 12 Port numbering of CHM2T (GLS-G30CHM2T-00)

The following pluggable modules supported by CHM2T are listed in the following table.

Client side Pluggable Part Form Wave 100GBE OTU4

Module Number Factor Length
Descrip- (nm)
tion
QSFP28 100G ZXS- QSFP28 1295.56 10km
LR4 Q8L4ZZZZ-00 (231.4THz)
1300.05
(230.6THz)
1304.58
(229.8THz)
1309.14
(229.0THz)
QSFP28 100G ZXS- QSFP28 1271 2km.RF

CWDM4/CLR4 Q8CWDM4Z- 1291
00
1311
1331
QSFP28 100G ZXS- QSFP28 850 100m.RF1)

SR4 Q8S4ZZZZ-00
QSFP28 ZXS- QSFP28 1295.56 10km 10km.GF2)

100GBASE- Q8L4ZZDR-00 1300.05
LR4 and OTU4
1304.58
Dual Rate
1309.14
QSFP28 LR4 ZXS- QSFP28 1295.56 10km 10km.GF3)

DR FPS Q8L4PRDR-00 1300.05
1304.58
1309.14
QSFP28 Active ZXS- QSFP28 850 3m.RF

Optical Cable Q8AOCZZZ-03
3m
QSFP28 Active ZXS- QSFP28 850 10m.RF

Optical Cable Q8AOCZZZ-10
10m
QSFP28 Active ZXS- QSFP28 850 1m 1m

Optical Cable Q8AOCZDR-
DR 1m 01
QSFP28 Active ZXS- QSFP28 850 5m 5m

Optical Cable Q8AOCZDR-
DR 5m 05
Table 18 Pluggable modules supported by CHM2T (GLS-G30CHM2T-00)

The CHM2T is a double slot module and can be installed into slot 1 and slot 3.
The CHM2T module performs the following functions:

• Supports Multiplexing up to 12x100G clients into to maximum 2*600G Coherent Line
Ports
• Supports programmable line rate of 100G to 600G at coherent line interfaces, as
described in Figure 13. A proper network planning of CHM2T is covered by Infinera
optical planning tools.

Figure 13 Programmable line modes supported by CHM2T
• Support CHM2T interworking with 7300 transponder cards under 200G QPSK 27%
FEC, and 400G 16QAM 27% FEC line modes
• Support CHM2T interworking with Groove OLS under 600G 64QAM 27% FEC
(OMD48-S only), 400G 16QAM 27% FEC, 200G QPSK 27% FEC line modes
• Support CHM2T OMS protection with O2OPS
• Supports LLDP and RMON on CHM2T 100GBE client ports
• Supports GMP mapping mode to map 100GBE into ODU4 from port 3-14 to port 1-2
• Supports ODUk path delay measurement
• Supports SDFEC on the line interface
• Supports terminal loopbacks on all client and line ports. Support facility loopbacks
on client ports
The supported ODU cross connections are listed as in Table 19.
g The cross connection can be flexibly setup from any client port to one of the line port.
Line Port ODU4 ID on the Connected

Line Port Client Port
QPSK (200G) Port 1 ODU4-1 Port 3-8,
Port 2 Port 9-14
16 QAM (400G) Port 1 Port 3-8,
Port 2 ODU4-1, ODU4-2 Port 9-14
64 QAM (600G) Port 1 Port 3-8,
Port 2 ODU4-1, ODU4-2, Port 9-14
ODU4-3
Table 19 Traffic table of CHM2T (GLS-G30CHM2T-00)

3.2.5.5 XTM2
Up to 2 double slot XTM2 Muxponder/Transponder modules, each support 2 x QSFP28
ports and 20x SFP+ ports. The XTM2 module port numbering is shown in Figure 14.
Figure 14 Port numbering of XTM2 (GLS-G30XTM2Z-00)

The following pluggable modules supported by XTM2 are listed in the following table.
Muxponder/Access Interface
Wave Length (nm)
STM64/OC192
OTN OTU2/2e
FC8G/FC16G
Part Number
Form Factor
OTN OTU4
OTU2/2e
OCH-OS
10GBE
Muxpo- QSFP28 ZXS- QSF 1295.56 10km

nder side 100GBAS Q8L4Z P28 1300.05 .GF1)
E-LR4 and ZDR-
1304.58
OTU4 00
Dual Rate 1309.14
QSFP28 ZXS- QSF 1295.56 10km
LR4 DR Q8L4P P28 1300.05 .GF
FPS RDR-
1304.58
00
1309.14
QSFP28 ZXS- QSF 850 10km
SR4 MUL- Q8S4Z P28 .GF
TIRATE ZMR-
(100GBE, 00
OTU4,
32GF)
QSFP28 ZXS- QSF 850 1m
Active Q8AO P28
Optical CZDR-
Cable DR 01
1m


Wave Length (nm)
STM64/OC192
OTN OTU2/2e
FC8G/FC16G
Part Number
Form Factor
OTN OTU4
OTU2/2e
OCH-OS
10GBE
QSFP28 ZXS- QSF 850 5m
Active Q8AO P28
Optical CZDR-
Cable DR 05
5m
Access SFP+, 81.71T- SFP+ 1260 10km
Interface 10GBASE/ SP10G 1335
8G LR-R6
FC/10G
FC-LR/LW
1310 SM
10KM
SFP+ 81.71T- SFP+ 840 300m
10GBASE/ SP10G 860
8G SR-R6
FC/10G
FC-
SR/SW
850 MM
300M
SFP+, 81.71T- SFP+ 1290 7km 7km 7km
1310 SM SPMR 1330
MULTI- SR1-
RATE SR1 R6
7KM
DWDM 81.71T- SFP+ Tunable 80km
TUNABLE SPDW C -Band
88 CH LR2 DM-R6 88-CH
80KM DWDM
SFP+, 81.71T- SFP+ 1310 20km 20km 20km 20km
1310 SM SPMRI
MULTI- R1-R6
RATE IR1
20KM


Wave Length (nm)
STM64/OC192
OTN OTU2/2e
FC8G/FC16G
Part Number
Form Factor
OTN OTU4
OTU2/2e
OCH-OS
10GBE
1550 SM SPMRI
MULTI- R2-R6
RATE IR2
40KM
1550 SM SPMRL
MULTI- R2-R6
RATE LR2
80KM
SFP+, 81.71.S SFP+ Tunable 80km 80km 80km 80km
HIGH PDWD C -Band
POWER MHP- 88-CH
SFP+ R6 DWDM
DWDM
TUNABLE
88 CH
4G-8G- ZXS- SFP+ 850 125m
16G FC, SP16G
125M, FSI-00
MMF
(850NM)
4G-8G- ZXS- SFP+ 1310 10km
16G FC, SP16G
10KM, FSL-00
SMF
(1310NM)
The XTM2 is a double-slot module which can be installed into slot 1 and slot 3.
The XTM2 module performs the following functions:

• Supports Multiplexing up to 20x10G clients into to 2x100G non-coherent ports
• Supports OTU4 mode on port 1 and port 12 multiplexing ports
• Supports OCHOS_OTU2/OCHOS_OTU2e line mode on port 2-11 and port 13-22

g • Default types of all ports are client, when port mode is set to OCHOS_OTU2/2e
the port type will be set to line
• OCHOS OTU2/2e only supports DWDM/Tunable SFP+ pluggable modules,
MEA will be reported with other type SFP+
• Client OTU2/2e only supports SR4/LR4/MR-SR1 SFP+ pluggable modules,
MEA will be reported with DWDM/Tunable SFP+
• Supports 10GBE/OTU2/OTU2e/STM-64/OC192/FC8G/FC16G client mode on port

2-11 and port 13-22
g There have 1us’ latency difference between different ports of FC8G/FC16G for
XTM2.
• Supports transponder 10GBE/OTU2/OTU2e/STM-64/OC192/FC8G/FC16G client

ports into to nearby transponder OCHOS_OTU2/2e line ports
g The transponder relations are fixed, for example, port2 corresponds to port3, port 4
corresponds to port5, and so sequentially ordered; port13 corresponds to port14,
and so on sequentially ordered.
• Supports OC192/STM64 pseudo random bit sequence (PRBS) testing

into ODU2 on all transport port
• Support alarm monitor on 10GBE, OTU4/2/2e, OC192, STM64, FC8G/FC16G,
ODU4/2/2e and OCH-OS layer
• Support performance monitor on 10GBE, OTU4/2/2e, OC192, STM64,
FC8G/FC16G, ODU4/2/2e and OCH-OS layer
• Supports PREAMBLE, GFP-F mapping 10GBE into ODU2
• Supports BMP (fixed stuff) mapping 10GBE into ODU2e
• Supports BMP mapping FC8G/FC16G into ODUflex on all 10G base ports
g The cross-connection between two ODUflex should be same client-signal-type.

into ODU2 on all 10G base ports
• Supports ODUj path delay measurement
• Supports G709,I4, I7 and no-FEC FEC modes on OTU2/OTU2e/OTU2_O-
CHOS/OTU2e_OCHOS interfaces
• Supports pseudo random bit sequence (PRBS) testing on Ethernet ports
• Supports FC8G/FC16G/OC192/STM64 pseudo random bit sequence (PRBS)
testing
• Supports terminal and facility loopbacks on all ports
• Support Client side ALS (Auto Laser Shutdown) on
10GBE/FC8G/FC16G/OC192/STM64/OTU2/OTU2e for fault propagation

For each XTM2 module the total 20 ports are separated into two groups, Group A and
Group B. Refer to Figure 15 of the Block Diagram of XTM2 module for detailed partition
of Group A and Group B.
Port 2~11 are in the group A which support ODU cross-connections on Muxponder Port
1; port 13~22 are in the group B which support ODU cross-connections with Muxponder
Port 12.
Figure 15 Block Diagram of XTM2 (GLS-G30XTM2Z-00)
3.2.5.6 OMD96
OMD96 is a 96-channel Optical Multiplexing/De-multiplexing card, 2-slot width. Up to 2
OMD96 cards can be supported by one G30. Specifications of OMD96 card are listed in
the following table.
Parameter Specification Unit

Operating Wavelength 191.35~196.1 THz
Channel number 96 -
Channel spacing 50G Hz
Low insertion loss 7.7 dB
Bandwidth 46G 3dB dB
MTP port 24 MTP ports for 96 A/D, each has 4 -
channels with 4 pairs of MTP12.
g The Pin-out of MTP port is same

with the MPO based QSFP module
(GVS-MT8LCSMZ-03).
LC port 1 x dual LC connector for DWDM Port, 2 -
x LC connector for DWDM In/Out power
monitor.
Table 20 Specifications of OMD96 (GLS-G30OMD96-00)
Port numbering of the OMD96 module is shown in Figure 16.

Figure 16 Port numbering of OMD96 (GLS-G30OMD96-00) module

The following table lists the OMD96 frequency information for each port.
Figure 17 Port frequency information of OMD96 (GLS-G30OMD96-00)
3.2.5.7 OMD48-S
OMD48-S is a 48-channel Optical Multiplexing/De-multiplexing card, 2-slot width. Up to
2 OMD48-S cards can be supported by one G30. Specifications of OMD48-S card are
listed in the following table.

Channel number 48 -
Table 21 Specifications of OMD48-S (GLS-G30OMD48-SG)


Low insertion loss 6.46dB on Mux and 5.82dB on Demux. dB
Bandwidth 80G 3dB Bandwidth on Mux and 75G dB
3dB Bandwidth on Demux.
MTP port 12 MTP ports for 48 A/D, each has 4 -
channels with 4 pairs of MTP12.
g The Pin-out of MTP port is same

with the MPO based QSFP module
(GVS-MT8LCSMZ-03).
LC port 1x dual LC connector for DWDM Port, -
2XLC connector for DWDM In/Out
power monitor.
Table 21 Specifications of OMD48-S (GLS-G30OMD48-SG)
Port numbering of the OMD48-S module is shown in Figure 18.
Figure 18 Port numbering of OMD48-S module

The following table lists the OMD48-S frequency information for each port.

Figure 19 Port frequency information of OMD48-S (GLS-G30OMD48-SG)
3.2.5.8 OMD64
OMD64 is an off-shelf 64-channel Optical Multiplexing/De-multiplexing card, 2-RU
height. OMD64 is managed through 1-wire cable(250-0321) as an extended OMD card
on virtual slots.
Specifications of OMD64 card are listed in the following table.

Channel number 64 -
Low insertion loss BOL (Begin of Life) 6.16 dB on Mux dB
and 5.82dB on Demux.
Bandwidth 74G 3dB Bandwidth on Mux and dB
Demux.
Table 22 Specifications of OMD64 (GQS-OMD64ZZZ-00)


LC port 64 Add/drop LC port for Mux/Demux. -
1x dual LC connector for DWDM Port,
2XLC connector for DWDM In/Out
power monitor.
RJ45 port To be connected to mini-USB port of
OCC2.
Table 22 Specifications of OMD64 (GQS-OMD64ZZZ-00)
Port numbering of the OMD64 module is shown in Figure 18.
Figure 20 Port numbering of OMD64 module

The following figure lists the OMD64 frequency information for each port.
Figure 21 Port frequency information of OMD64 (GQS-OMD64ZZZ-00)

OMD64 can be added to chassis with virtual slot 80 or 82 for fiber connection purpose.
To add an OMD64 card, use the following command:
add card-1/80 required-type OMD64
or
add card-1/82 required-type OMD64

3.2.5.9 OCC2
Optical Carrier Card, most compact amplifier solution for configurable optical layer. 2-
slot width. Up to 2 OCC2 cards can be supported by one G30. OCC2 card has 3 Optical
Form Factor Pluggable 2 (OFP2) cages and 2 SFP cages. Each OFP2 cage can hold
one OFP2.
Port numbering of the OCC2 module is shown in Figure 22.
Figure 22 Port numbering of OCC2 (GLS-G30OCC2Z-00)

Pluggable Module Description Part Number

OFP2 OFP2 PRE-AMP WITH OSC (PAOSCOFP2) 81.71T-O2PAOSC-R6
pluggable OFP2 PRE-AMP AND BOOSTER AMP 81.71T-O2PABA-R6
modules (PABAOFP2)
supported
by OCC2 IR PRE-AMP + OSC Add/Drop, High Channel 81.71T-O2PAOHIR-R6
Count OFP2 (PAIROFP2)
LR PRE-AMP + OSC Add/Drop, High Channel 81.71T-O2PAOHLR-R6
Count OFP2 (PALROFP2)
ER PRE-AMP + OSC Add/Drop, High Channel 81.71T-O2PAOHER-
Count OFP2 (PAEROFP2) R6
BOOSTER AMP OFP2 (BA OFP2), High 81.71T-O2BAH-R6
Channel Count (BAHOFP2)
OFP2 OMD8 Band 1 (OMD8B1) ZXS-O2OMD8B1-00
OFP2 OMD8 Band 2 (OMD8B2) ZXS-O2OMD8B2-00
OFP2 CAD8 (CAD8) ZXS-O2CAD8ZZ-00
OFP2 CAD8E (CAD8E) ZXS-O2CAD8EZ-00
OFP2 TDCM (TDCMOFP2) ZXS-O2TDCMZZ-00
OFP2 BOOSTER AMP ULTRA HIGH POWER ZXS-O2BAUZZZ-00
(BAUOFP2)
OFP2 PRE-AMP ULTRA HIGH POWER ZXS-O2PAOULR-00
LONGER REACH
(PAULROFP2)
OFP2 1CH OPS MODULE ZXS-O2OPS1ZZ-00
(O2OPS)
OFP2 OTDR 4-PORT ZXS-O2OTDR4Z-00
OFP2 OCM MODULE ZXS-O2OCMZZZ-00
Table 23 Pluggable modules supported by OCC2 (GLS-G30OCC2Z-00)
• PAOSC OFP2 (81.71T-O2PAOSC-R6) is a Variable-Gain Preamplifier with Optical

Supervisory Channel (OSC) function. It’s target output power for 40-channel appli-
cations is -3dBm.
For specifications of PAOSCOFP2 amplifier, refer to Table 98 in 9 Appendix B:
Specifications for Optical Pluggable Modules.
• PABA OFP2 (81.71T-O2PABA-R6) is a Variable-Gain Preamplifier and Fixed-Gain

Booster Amplifier with per channel span launch power of 0dBm, target pre-amplifier
output power for 96-channel applications of -6dBm, and target booster output
power for 16-channel applications of 2dBm.
For specifications of PABA OFP2 amplifier, refer to Table 99 in 9 Appendix B: Spec-
ifications for Optical Pluggable Modules.

• PAIR OFP2 (81.71T-O2PAOHIR-R) is a multi-channel preamplifier with an optical

supervisory channel. It provides EDFA amplifications for up to 96 wavelength chan-
nels. PAIR is used in an intermediate range of 0 - 18 dB.
For specifications of Pre-amplifier PAIROFP2, refer to Table 100 in 9 Appendix B:
• PALR OFP2 (81.71T-O2PAOHLR-R6) is a multi-channel preamplifier with an optical
supervisory channel. It provides EDFA amplifications for up to 96 wavelength chan-
nels. PAIR is used in an intermediate range of 14- 26dB.
For specifications of Pre-amplifier PALROFP2, refer to Table 101 in 9 Appendix B:
• PAER OFP2 (81.71T-O2PAOHER-R6) is a multi-channel preamplifier with an

optical supervisory channel. It provides EDFA amplifications for up to 96 wavelength
channels. PAIR is used in an intermediate range of 25- 35dB.
For specifications of Pre-amplifier PAEROFP2, refer to Table 102 in 9 Appendix B:
• BAH OFP2 (81.71T-O2BAH-R6) is a multi-channel booster amplifier. It provides

EDFA amplifications for up to 96 wavelength channels.
For specifications of Booster Amplifier BAHOFP2, refer to Table 103 in 9 Appendix
B: Specifications for Optical Pluggable Modules.
g It’s not easy to plug out fiber from DCM,DWDM or DWDM line port of PAOHOFP2
card. Use space optimized LC-duplex connectors like LC-HD connector of Senko
and Molex to assist the plug out, part numbers of them should be 255-0083-xxxx.
• The O2OPS OFP2 (ZXS-O2OPS1ZZ-00) is an optical switch module. It can auto-

matically switch the facility side to connect to the working side or to the protected
side during signal receiving. The facility side is also called the client side. The OPS
can be used on both Tx and Rx links.
Specifications of O2OPS major parameters:
• Input power range: -40dBm to +25dBm
• Power accuracy
• +/- 0.5dB for the range [-40, +20] dBm
• +/- 1.5dB for the range [+20, +25] dBm
• The PAULR OFP2 (ZXS-O2PAOULR-00) is an ultra high power preamplifier with an

optical supervisory channel. It provides a long reach range EDFA amplification up to
80 km. The output saturated power can be as high as 24 dBm.
The maximum reach range applies to both the direct detect and the coherent lite
applications for Data Center Interconnect.
For specifications of Booster Amplifier PAULROFP2, refer to Table 104 in
• The BAU OFP2 (ZXS-O2BAUZZZ-00) is a booster amplifier with an ultra high satu-
rated output power up to 25 dBm. It provides an EDFA amplification with the optical
power measurement ability.
For specifications of Booster Amplifier BAUOFP2, refer to Table 105 in 9 Appendix
B: Specifications for Optical Pluggable Modules.

g When using PAULROFP2 and BAUOFP2, pay attention to the laser safety problem,
detailed please refer to POL Manual.
• The TDCM OFP2 (ZXS-O2TDCMZZ-00) is a tunable dispersion compensation

module. It is dedicated for the dispersion compensation for the ultra high power pre-
amplifiers on the G30. When the TDCM supports the PAOULR for the PAM4 appli-
cations, the maximum compensation distance is up to 80 km. The achievable
performance needs to be evaluated against detailed optical link. The current sup-
ported preamplifier is PAULR (ZXS-O2PAOULR-00).
For specifications of TDCMOFP2, refer to Table 106 in 9 Appendix B: Specifications
for Optical Pluggable Modules.
• The OTDR OFP2 (ZXS-O2OTDR4Z-00) is an optical time domain reflectometer-

module. It enables the system to perform real-time OTDR function of detecting the
location of fiber broken and measuring the optical losses in the fiber link.
For specifications of OTDR OFP2, refer to Table 107 in 9 Appendix B: Specifications
for Optical Pluggable Modules.
• The OMD8 OFP2 works as an eight-channel optical multiplexer or de-multiplexer.

G30 supports OMD8 Band 1 (ZXS-O2OMD8B1-00) and Band 2 (ZXS-O2OMD8B2-
00).
For specifications of OMD8B1/B2 OFP2 DWDM filters, refer to Table 108 in
9 Appendix B: Specifications for Optical Pluggable Modules
For optical channel map of OMD8B1/B2 OFP2, refer to Table 109 in 9 Appendix B:
Figure 133 in 9 Appendix B: Specifications for Optical Pluggable Modules lists the
OMD8OFP2 frequency information for each port.
• The CAD8/8E OFP2 works as an colorless 8 channel optical multiplexer or de-mul-

tiplexer who can receive DWDM span signal with whichever wavelength, not like
OMD8 which needs to identify the wavelength. G30 supports CAD8 (ZXS-
O2CAD8ZZ-00) and CAD8E (ZXS-O2CAD8EZZ-00).
For specifications of CAD8/8E OFP2 DWDM filters, refer to Table 110 and Table
111 in 9 Appendix B: Specifications for Optical Pluggable Modules.
• OCM OFP2 is a common OFP2 Form Factor with 4 single LC OCM ports. The
Optical Channel Monitoring (OCM) monitors the power of OMD/OFP2 cards to indi-
vidual port level, at the same time manages the power of DWDM line degree inter-
face besides monitoring. Detailed information please refer to 5.3.5 OCM (Optical
Channel Monitoring).
Refer to Table 112 in 9 Appendix B: Specifications for Optical Pluggable Modules
for specifications of OCM. Refer to Table 113 in 9 Appendix B: Specifications for
Optical Pluggable Modules for optical channel map of OCM.

3.3 Technical data
3.3.1 Physical measurements

The physical measurements of the G30 and its components are listed as follows.
Chassis (Bared frame without any Measurement

pluggable modules)
Height 1.73 inches (44 mm)
Width 17.3 inches (440 mm)
Depth 20.1 inches (510 mm)
Depth with all modules installed 23.3 inches (592 mm)
Weight 7.1 pounds (3.2 kg)
Table 24 Weight and dimensions – chassis (GQS-G30CHASZ-00)
Figure 23 illustrates dimensions of the chassis.
Figure 23 Dimension of the chassis
Item Measurement - AC Power Measurement - 48V/240V

Module DC Power Module
Height 1.6 inches (40 mm) 1.6 inches (40 mm)
Width 2.9 inches (73.5 mm) 2.9 inches (73.5 mm)
Depth 7.7 inches (195 mm) (not 7.3 inches (185 mm) (not
including handle) including handle)
Weight 2.2 pounds (1 kg) 2.2 pounds (1 kg)
Table 25 Weight and dimension – AC/DC power supply module (GPS-G30PSUAC-

00/GPU-G30PSUDC-00-10/)

Figure 24 illustrates dimension of AC power module.
Figure 24 Dimension of AC power module

Figure 25 illustrates dimension of 48V DC power module.
Figure 25 Dimension of 48V DC power module (GPS-G30PSUDC-00)

Figure 25 illustrates dimension of 240V DC power module.

Figure 26 Dimension of 240V DC power module (GPS-G30PSUHV-00)
Fan Module Measurement

Height 1.59 inches (40.5 mm)
Width 1.7 inches (42.5 mm)
Table 26 Weight and dimension – fan module (GFS-G30FANZZ-00)
Figure 27 illustrates dimension of fan module.

Figure 27 Dimension of fan module
CHM1/CHM1LH Measurement
Table 27 Weight and dimension – CHM1 (GLS-G30CHM1Z-00)/ CHM1LH (GLS-

G30CHM1L-00)
CHM1G Measurement
Table 28 Weight and dimension – CHM1G (GLS-G30CHM1G-00)

CHM1G (Non-Encryption) Measurement

Table 29 Weight and dimension – CHM1GNC (GLS-G30CHM1G-NC)
Figure 28 illustrates dimension of CHM1/CHM1LH/CHM1G.
Figure 28 Dimension of CHM1/CHM1LH/CHM1G
CHM2/CHM2LH Measurement
Table 30 Weight and dimension – CHM2 (GLS-G30CHM2Z-00)/CHM2LH (GLS-

G30CHM2L-00)
Figure 29 illustrates dimension of CHM2/CHM2LH.

Figure 29 Dimension of CHM2/CHM2LH
CHM2T Measurement
Table 31 Weight and dimension – CHM2T(GLS-G30CHM2T-00)
Figure 29 illustrates dimension of CHM2T.

Figure 30 Dimension of CHM2T
OMD96 Measurement
Table 32 Weight and dimension – OMD96 (GLS-G30OMD96-00)
OMD48S Measurement
Table 33 Weight and dimension – OMD48S (GLS-G30OMD48-SG)
Figure 31 illustrates dimension of OMD96 and OMD48S.

Figure 31 Dimension of OMD96/OMD48S
OMD64 Measurement
Height 3.48 inches (88 mm)
Depth 19.1 inches (482.6 mm)
Table 34 Weight and dimension – OMD64 (GQS-OMD64ZZZ-00)
Figure 31 illustrates dimension of OMD64.
Figure 32 Dimension of OMD64

OCC2 Measurement
Table 35 Weight and dimension – OCC2 (GLS-G30OCC2Z-00)
Figure 33 illustrates dimension of OCC2.
Figure 33 Dimension of OCC2
XTM2 Measurement
Table 36 Weight and dimension – XTM2 (GLS-G30XTM2Z-00)
Figure 34 illustrates dimension of XTM2.

Figure 34 Dimensions of XTM2
Pluggable Module type Weight

CFP2-ACO 0.24 pounds (110g)
QSFP28 0.09 - 0.13 pounds (40~60g)
QSFP+ 0.09 pounds (40g)
O2OPS OFP2 0.44 pounds (200g)
Other OFP2 modules except O2OPS 0.4 pounds (180g)
Table 37 Weight of each different kind of pluggable modules
3.3.2 Power consumption

Power consumption of both DC shelf and AC shelf is the same, and the total power con-
sumption values of several typical scenarios for G30 equipped with DC or AC power
module are listed in Table 38, Table 39, Table 40, Table 41, Table 42, Table 43, Table
44.
Unit Typical Estimated Quantity Total Total Esti-

power (W) Maximum Typical mated
Power (W) Power (W) Maximum
Power (W)
Shelf (fan 110 170 1 110 170
speed 60%)
Table 38 G30 power consumption (with 2*CHM2T cards)


Power (W)
CHM2T 192 230 2 384 460
module (10 x
QSFP28)
Total - - - 494 630
Table 38 G30 power consumption (with 2*CHM2T cards)

Power (W)
Shelf (fan 110 170 1 110 170
speed 60%)
CHM2/CHM2 302 325 2 604 650
LH module
(10 x QSFP+)
Total - - - 714 820
Table 39 G30 power consumption (with 2*CHM2/CHM2LH cards)
Unit Typical Estimated Quantity Total Total

power (W) Maximum Typical Estimated
Power (W)
Shelf (fan 110 170 1 110 170
speed 60%)
CHM1/CHM1 146 153 4 584 612
LH module (4
x QSFP28)
Total - - - 694 782
Table 40 G30 power consumption (with 4*CHM1/CHM1LH cards)


Power (W)
Shelf (fan 110 170 1 110 170
speed 60%)
CHM1G-NC 88 90 4 352 360
(4 x QSFP28)
Total - - - 462 530
Table 41 G30 power consumption (with 4*CHM1G non encryption cards)

Power (W)
Shelf (fan 110 170 1 110 170
speed 60%)
CHM1G 94 104 4 376 416
module (4 x
QSFP28)
Total - - - 486 586
Table 42 G30 power consumption (with 4*CHM1G encryption cards)

Power (W)
Shelf (fan 62.8 71.8 1 62.8 71.8
speed 40%)
OCC2 module 26.2 39.0 1 26.2 39.0
(1*PABA and
1*PAOSC)
OMD96 0.8 1.1 1 0.8 1.1
Total - - - 89.8 111.9
Table 43 G30 power consumption (with 1*OMD96 card and 1*OCC2 card)


Power (W)
Shelf (Includ- 110 170 1 110 170
ing Main
board, Fan
Unit and
Power
Module)
XTM2 module 80 100 2 160 200
Total - - - 270 370
Table 44 G30 power consumption (with 2*XTM2)
g All of output characteristic can be workable when using within 192V-288 Vdc on AC
PSU. Coriant does not guarantee any safety mark, housing, quality and reliability
requirement when applying DC input condition on AC PSU.
Tested power values of each component included in shelf under maximum situation
(170W) are list in Table 45.
Unit Quantity Estimated Total

Maximum Estimated
Power (W) Maximum
Main board 1 36 36
Fan Unit 5 16.8 84
AC power 2 25 50
module
DC power 2 25 50
module
Total - - 170
Table 45 Shelf power consumption
Tested power values of each pluggable modules included in shelf under typical situation
(110W) and maximum situation (170W) are list in Table 46.
Unit Part Number Estimated Typical Estimated

Power (W) Maximum Power
(W)
CFP2-ACO GHP ZXS-C2OTSTZZ- - 12W
00
Table 46 Power consumption of each pluggable module


(W)
CFP2-ACO CHP ZXS-C2ACOTZZ- - 13W
00
QSFP28 100GE ZXS-Q8S4ZZZZ-00 - 3.5W
SR4
QSFP28 100GE ZXS-Q8L4ZZZZ-00 - 4.5W
LR4
QSFP28 100G ZXS-Q8CWDM4Z- - 3.5W
CWDM4 00
QSFP28 100G ZXS-Q8PSM4ZZ- - 3.5W
PSM4 00
QSFP28 100G LR4 ZXS-Q8L4ZZDR-00 - 4.5W
DR
QSFP28 ER4 ZXS-Q8ER4ZZZ-00 - 4.5W
QSFP28 SR4 MUL- ZXS-Q8S4ZZMR- - 3.5W
TIRATE (100GBE, 00
OTU4, 32GFC)
QSFP28 ACTIVE ZXS-Q8AOCZZZ- - 4.5W
OPTICAL CABLE 03
3M
QSFP28 ACTIVE ZXS-Q8AOCZZZ- - 4.5W
OPTICAL CABLE 10
10M
QSFP28 ZXS-Q8FCPSMZ- - 3.5W
4X8/16GFC, PSM 00
QSFP28 Active ZXS-Q8AOCZDR- - 4.5W
Optical Cable 1m 01
QSFP28 Active ZXS-Q8AOCZDR- - 4.5W
Optical Cable 5m 05
QSFP28 LR4 DR ZXS-Q8L4PRDR- - 4.5W
FPS 00
QSFP+ 40GBE 81.71T-Q40GSR4- - 1.5W
INTERFACE - 100 R6
QSFP+ 40GE LR4 ZXS-QPL4ZZZZ-00 - 3.5W
QSFP+ 4X8/16GFC ZXS-QPFCZZMR- - 3.5W
00
QSFP+ 4x10GE ZXS-QPQ10GLW- - 3.5W
LR/W PSM 00
QSFP+ 40GE IR4 ZXS-QPI4ZZZZ-00 - 3.5W


(W)
QSFP+ 40GE eSR4 ZXS-QPS4EZZZ- - 3.5W
00
QSFP+ 40GBase- ZXS-QPE4ZZZZ-00 - 3.5W
ER4
QSFP+ OTU3, 81.71T-Q40GLR4- - 3.5W
STM256, 40GBE- R6
10KM
OFP2 PREAMP 81.71T-O2PAOSC- 5W 11W
WITH OSC R6
(PAOSCOFP2)
OFP2 PRE-AMP 81.71T-O2PABA- 5.2W 11W
AND BOOSTER R6
AMP (PABAOFP2)
IR Preamp + OSC 81.71T- 6W 11W
Add/Drop, High O2PAOHIR-R6
Channel Count
OFP2 (PAIROFP2)
LR Preamp + OSC 81.71T- 6W 11W
Add/Drop, High O2PAOHLR-R6
Channel Count
OFP2 (PALROFP2)
ER Preamp + OSC 81.71T- 6W 11W
Add/Drop, High O2PAOHER-R6
Channel Count
OFP2 (PAEROFP2)
Booster Amplifier 81.71T-O2BAH-R6 8W 11W
OFP2 (BA OFP2),
High Channel
Count (BAHOFP2)
OFP2 OMD8 Band ZXS-O2OMD8B1- 0.6W 1W
1 (OMD8B1) 00
OFP2 OMD8 Band ZXS-O2OMD8B2- 0.6W 1W
2 (OMD8B2) 00
OFP2 TDCM (TDC- ZXS-O2TDCMZZ- 5W 9W
MOFP2) 00
OFP2 BOOSTER ZXS-O2BAUZZZ- 12W 24W
AMP ULTRA HIGH 00
POWER
(BAUOFP2)


(W)
OFP2 PREAMP ZXS-O2PAOULR- 11W 17W
ULTRA HIGH 00
POWER LONGER
REACH
(PAULROFP2)
OFP2 1CH OPS ZXS-O2OPS1ZZ- 1.7W 2W
MODULE 00
(O2OPS)
OFP2 OTDR 4- ZXS-O2OTDR4Z- 2.7W 3.1W
PORT 00
OFP2 OPTICAL ZXS-O2OCMZZZ- 2.2W 2.5W
CHANNEL 00
MONITOR
OFP2 CAD8 Color- ZXS-O2CAD8ZZ- 0.6W 1W
less Add/Drop 00
OFP2 CAD8E Col- ZXS-O2CAD8EZ- 0.6W 1W
orless Add/Drop 00
Expandable
SFP+, 1310 SM 81.71T-SPMRIR1- - 1.5W
MULTIRATE IR1 R6
20KM
SFP+, 1550 SM 81.71T-SPMRIR2- - 1.5W
MULTIRATE IR2 R6
40KM
SFP+, 1550 SM 81.71T-SPMRLR2- - 1.8W
MULTIRATE LR2 R6
80KM
SFP+, HIGH 81.71.SPDWD- - 1.9W
POWER SFP+ MHP-R6
DWDM TUNABLE
88 CH
4G-8G-16G FC, ZXS-SP16GFSI-00 - 1W
125M, MMF
(850NM)
4G-8G-16G FC, ZXS-SP16GFSL-00 - 1W
10KM, SMF
(1310NM)

3.3.3 Specifications of transponder side optical pluggable modules

Specifications of client side optical pluggable modules for the G30 refer to Table 91 in
G30 supports 3 types of CFP2-ACO line side pluggable modules:
• CFP2-ACO Generic High-performance Pluggable (GHP)
CFP2-ACO GHP is a generic high-performance pluggable module used on line side.
Specifications of line interface with optical pluggable modules GHP CFP2-ACO are
listed in Table 92 in 9 Appendix B: Specifications for Optical Pluggable Modules.
• CFP2-ACO Coriant High-performance Pluggable (CHP)
CFP2-ACO CHP is a high-performance pluggable module developed by Coriant
used on line side. Specifications of line interface with optical pluggable modules
CHP CFP2-ACO are listed in Table 94 in 9 Appendix B: Specifications for Optical
Pluggable Modules.
3.3.4 Product requirements

The product requirements for the Groove™ G30 are listed in Table 47.
Category Item AC Groove™ G30 DC Groove™ G30

Environmental Temperature, ambient 41 to 104°F (5 to 41 to 104°F (5 to 40°C)
1) Derate operating 40°C)1)
maximum allow- Temperature, ambient - 23 to 113°F (-5 to
able dry-bulb operating, short-term 45°C)2)
temperature
Relative humidity, 8 to 85%
1°C/300 m above
ambient (non-condens-
950 m.
ing) operating
2) At sea level
Relative humidity, - 5 to 93
ambient (non-condens-
ing) operating, short-
term
Altitude, operating 2850 ft (950 m) -
Fan failure 40°C at Sea level
Physical dimen- Dimensions (H x W x D) 1.74 x 17.3 x 20.1 in. (44 x 440 x 510 mm)
sions Weight of fully provi- 24.3 lb (11.0 kg)
sioned chassis
Power Input characteristics 100~127V AC or -40.5~-72V DC
200~240V AC, max Max 30A
12A;
50/60 Hz
Maximum power con- 820W
sumption
Table 47 Product requirements of G30

3.3.5 MTBF (Mean Time Between Failure) data

The MTBF data for the Groove™ G30 are listed in Table 48.

Module name Order Number Fit value MTBF

(year)
G30 CHASSIS GQS-G30CHASZ-00 770.00 148.25
G30 chassis with sliding rails GQS-G30CHASR-00 770.00 148.25
G30 field replaceable control- GQS-G30CHASF-00 742.01 154
ler unit (FRCU) chassis
G30 field replaceable control- GCS-G30FRCUZ-00 480.85 237
ler unit (FRCU)
G30 FAN MODULE GFS-G30FANZZ-00 6846.63 17
G30 AC POWER MODULE GPS-G30PSUAC-00 1969.36 58
G30 DC POWER MODULE GPS-G30PSUDC-00 10000.00 11.42
48V
G30 CHM1 (4x100G) GLS-G30CHM1Z-00 1296.10 88
G30 CHM1LH (4x100G) GLS-G30CHM1L-00 8200.91 14
G30 CHM1G (4x100G, GLS-G30CHM1G-00 973.45 117
encryption)
G30 CHM1G (4x100G, no GLS-G30CHM1G-NC 953.25 120
encryption)
G30 CHM2 (40x10G, 10x40G, GLS-G30CHM2Z-00 1897.12 60
4x100G)
G30 CHM2LH (40x10G, GLS-G30CHM2L-00 8803.38 13
10x40G, 4x100G)
G30 CHM2T (12x100G) GLS-G30CHM2T-00 6119.84 19
G30 XTM2 20x10G GLS-G30XTM2Z-00 712.53 160
OCC2 GLS-G30OCC2Z-00 493.11 231.50
OMD96 GLS-G30OMD96-00 238.61 478.41
OMD48-S GLS-G30OMD48-SG 126.67 901
OMD64 (2RU) GQS-OMD64ZZZ-00 96.93 1178
G30 CHM FILLER PLATE GLS-G30CHMFI-00 5.69 20068
QSFP+ 4X10GBELR/W PSM ZXS-QPQ10GLW-00 803.00 142
CFP2-ACO GHP ZXS-C2OTSTZZ-00 2147.00 53
QSFP28 100G SR4 ZXS-Q8S4ZZZZ-00 143.3 797
QSFP28 100G LR4 ZXS-Q8L4ZZZZ-00 614.1 186
QSFP28 100G CWDM4 ZXS-Q8CWDM4Z-00 113.74 1004
QSFP28, 100G PSM4 ZXS-Q8PSM4ZZ-00 2599.5 44
QSFP28 SR4 Multi- ZXS-Q8S4ZZMR-00 106.8 1069
rate(100GbE, OTU4, 32GFC)
QSFP28 4x8/16GFC, PSM ZXS-Q8FCPSMZ-00 1010.70 113


(year)
QSFP28 Active Optical Cable ZXS-Q8AOCZZZ-03 347.7 328
3m
QSFP28 Active Optical Cable ZXS-Q8AOCZZZ-10 347.7 328
10m
SFP+, 10GBASE/8G FC/10G 81.71T-SP10GLR-R6 400.00 285
FC-LR/LW 1310 SM 10KM
SFP+ 10GBASE/8G FC/10G 81.71T-SP10GSR-R6 78.00 1464
FC-SR/SW 850 MM 300M
SFP+, 81.71T-SPMRSR1-R6 423.00 270
1310 SM MULTIRATE SR1
7KM
QSFP+ 40GBE INTERFACE - 81.71T-Q40GSR4-R6 592.76 193
100m
QSFP+ 40GBE LR4 ZXS-QPL4ZZZZ-00 807.6 141
QSFP28 100GBASE-LR4 and ZXS-Q8L4ZZDR-00 113.74 1003.65
OTU4 Dual Rate
QSFP28 LR4 DR FPS ZXS-Q8L4PRDR-00 165.10 691
QSFP28 Active Optical Cable ZXS-Q8AOCZDR-01 347.70 328
DR 1m
QSFP28 Active Optical Cable ZXS-Q8AOCZDR-05 347.70 328
DR 5m
QSFP28 ER4 (30km). SMF ZXS-Q8ER4ZZZ-00 537.30 212
fiber. LC connector
OFP2 PREAMP WITH OSC 81.71T-O2PAOSC-R6 324.76 351.51
OFP2 PRE-AMP AND 81.71T-O2PABA-R6 324.76 351.51
BOOSTER AMP
IR Preamp + OSC Add/Drop, 81.71T-O2PAOHIR-R6 508.24 225
High Channel Count OFP2
LR Preamp + OSC Add/Drop, 81.71T-O2PAOHLR- 394.44 289
High Channel Count OFP2 R6
ER Preamp + OSC Add/Drop, 81.71T-O2PAOHER- 359.05 318
High Channel Count OFP2 R6
Booster Amplifier OFP2 (BA 81.71T-O2BAH-R6 436.84 261
OFP2), High Channel Count
OFP2 OMD8 Band 1 ZXS-O2OMD8B1-00 0.80 142694
OFP2 OMD8 Band 2 ZXS-O2OMD8B2-00 0.80 142694
OFP2 TDCM (Tunable Disper- ZXS-O2TDCMZZ-00 25.63 4453
sion Compensation Module)


(year)
OFP2 BOOSTER AMP ZXS-O2BAUZZZ-00 712 160
ULTRA HIGH POWER
OFP2 PREAMP ULTRA HIGH ZXS-O2PAOULR-00 956.71 119
POWER LONGER REAC
OFP2 1CH OPS MODULE ZXS-O2OPS1ZZ-00 301.07 379
OFP2 OTDR 4-PORT ZXS-O2OTDR4Z-00 354.55 322
OFP2 OPTICAL CHANNEL ZXS-O2OCMZZZ-00 243.35 469
MONITOR
OFP2 CAD8 Colorless ZXS-O2CAD8ZZ-00 220.46 518
Add/Drop
OFP2 CAD8E Colorless ZXS-O2CAD8EZ-00 234.22 487
Add/Drop Expandable
Table 48 MTBF data of G30

User Guide (UG) Hardware installation and startup procedures
4 Hardware installation and startup proce-

dures
g If fully provisioned, the depth of the G30 shelf is longer than 510mm (excluding the
optical modules and fibers) and the weight is more than 10kg. It should be carefully
hand-carried to prevent injury to people and damage to the shelf.
4.1 Installation pre-requisites

The G30 can be installed into the following equipment racks:
• 19-inch
• 21-inch
• 23-inch
• ETSI
The rack should have enough depth to contain the G30 shelf and its cables/fibers routing
(see Figure 35). Ensure there is enough depth behind the front installation post.
Figure 35 Shelf depth behind front installation post

The depth behind the front installation post is shown in Figure 36.
Figure 36 Footprint of the G30 in the rack

g Front depth requirement depends on fiber types. If using short fibers, a minimum of
126mm depth for 19 / 21 / 23 provision or 112mm depth for ETSI provision are required.
4.1.1 Unpacking and verifying the G30

When you receive the package:
1. Unpack the shelf and remove the packaging from the surrounding area.
2. Examine the shelf and confirm the G30 part number (Part number GQS-
G30CHASZ-00).
3. Verify that all items on the packing list are present.
4. Perform a visual inspection for any damage especially mechanical bending, distor-
tion or other mechanical damages. In particular inspect all connectors for damaged
or bent pins. If there is any damage, repack the shelf in its packaging and make
arrangements to return the damaged/defective shelf. For more information about
return and replacement, refer to 6.1 Replacement and after-sale technical support.
4.1.2 Required materials

The following materials, tools, and equipments are required but are not shipped with the
Groove™ G30:
• Equipment rack
• Phillips screwdriver
• Nut driver set
• AC or DC power cords
g • Only 19-inch mounting brackets are shipped with the Groove™ G30 for normal
chassis, and the user needs to order the specific mounting brackets if you intend
to install the G30 in a 21-inch, 23-inch, or ETSI racks
• No mounting bracket is shipped with G30 for FRCU chassis. The user needs to
order the appropriate mounting brackets if intend to install G30 in a 19-inch rack,
19-inch cabinet, 23-inch, or ETSI frameworks.
For more information about items that can be ordered, refer to Appendix A: Ordering
guide or contact your sales representative.
4.2 Installation procedures

This section describes the procedures to install the G30.
• Mounting brackets (Applicable only to normal chassis)
• Installing the G30 into the rack
• Grounding the G30
• Installing the AC/DC power modules
• Connecting AC/DC power cords to the G30
• Checking power LED status
• Installing the fan modules
• Installing pluggable modules
• Installing the FRCU controller modules (applicable only for FRCU chssis)

• Installing the optical modules into the pluggable modules

• Connecting fibers
f Always wear a static protection wriststrap while performing any procedure that requires
you to come in contact with the system. This includes touching modules, cabling, or the
system in any way. Electrostatic Discharge (ESD) can damage system components
resulting in a traffic-affecting condition.
4.2.1 Mounting brackets (Applicable only to normal chassis)

The G30 can be installed in a 19-inch, 21-inch, 23-inch, or ETSI rack. The 19-inch
brackets are mounted by default, optional mounting brackets can be used to install the
G30 to other rack types. To install these racks:
1. Remove the 19-inch brackets and the plastic cover from the Console port.
2. Align the appropriate mount brackets to one side of the chassis.
g Make sure the plastic cover for the Console port is re-installed on the right mount
bracket.
3. Use the nut driver to secure the nuts.

4. Repeat 1. through 3. to mount the bracket on the other side.
Figure 37 Mounting brackets for 23 inch rack

Figure 38 Mounting brackets for ETSI rack
Figure 39 Mounting brackets for 21 inch rack
g To install the G30 on a 21-inch rack, remove the 19-inch bracket on one side and
replace it with one 23-inch bracket.
4.2.2 Installing the G30 into the rack
4.2.2.1 Installing the G30 into the rack for normal chassis
The G30 can be installed into both 2-post and 4-post shelves, hereinafter we exemplify
with a 2-post shelf. For a 4-post shelf, the user only needs to install the adjustable
mounting brackets on the additional 2 posts in the rear.
Make sure the appropriate brackets are mounted before installing the G30 into the rack.
g Basic Mounting Brackets (front mounting brackets), rear mounting brackets and shelf
rails are shipped together with the G30 shelf.
g 21 inch rear mounting brackets will use one 19-inch rear mounting bracket and one 23-
inch rear mounting bracket as front mounting brackets. Detailed information of rear
mounting brackets and shelf rails are listed in Figure 40.

Figure 40 Rear mounting brackets and shelf rails

To install the G30 into the rack:
g You can ignore step 1. to step 3. if you don't plan to install the optional adjustable
mounting brackets.
g Installing only the Basic Mounting Brackets will provide enough strength to support the
shelf and pass all the vibration/earthquake tests specified at NEBS. However, since the
shelf depth exceeds 500mm (excluding the handle and fiber/cables) and the weight is
greater than 10kg when fully provisioned, installing only the Basic Mounting Brackets
will cause the rear shelf to sag by 1-3 degs. Installing the Additional Rear Mounting
Brackets will eliminate the sagging issue.
1. Attach the adjustable shelf rails to each sides of the G30 shelf (for rear mounting
option).
1 Measure the distance S between front installation surface and rear installation
surface from the rack.

Figure 41 Distance S between front and rear installation surfaces
g Distance S should be between 3-20 inches (75mm to 500mm). Otherwise, the

rear mounting brackets can not be installed.
2 Place the shelf rail in an appropriate position (determine the correct position in
accordance with Figure 42. Take off 2 adjacent screws where the shelf will be
attached and install the shelf rail with 2 screws (Part Number 140.0008) at each
side.
Figure 42 How to determine the shelf rail position S1
2. Install the Basic Mounting Brackets (front mounting brackets) to the rack.
1 Make sure proper mounting brackets are already installed to the shelf according
to 4.2.1 Mounting brackets (Applicable only to normal chassis).
2 (Optional) Install the floating nut (Part Number 159-0000-020) to the frame if
needed (especially for the cabinet).
3 Use a nut driver to fix each 2 rack screws (Part Number 140.0039 or 40.0167,
depending on screw holes thread metric on rack) from each side to fix the shelf
from front side.

Figure 43 Fix the Basic Mounting Brackets (front mounting brackets)

4 Use a nut driver to fix each 2 rack screws (Part Number 140.0039 or 40.0167,
depending on screw holes thread metric on rack) from each side to fix the shelf
from front side.
3. Install the rear mounting brackets (for rear mounting option).
1 Lift the shelf to ensure front and rear are in the same RU height.
2 Install the rear brackets to the rack but do not fully tighten the screws.
3 After the shelf is placed on the rear brackets, push inward on the rear brackets
to fit the brackets tightly onto the shelf rail.
4 Tighten the screws.
Figure 44 Install the rear mounting brackets
4.2.2.2 Installing the G30 into the rack for FRCU chassis
Remove the packing brackets

The packing brackets are only used during transportation phase. Remove these two
packing brackets and four screws before the installation.

Figure 45 Remove packing brackets
Installing G30 onto the framework
g The G30 can be installed into both 2-post and 4-post shelves, hereinafter we exemplify
with a 2-post shelf. For a 4-post shelf, the user only needs to install the adjustable
mounting brackets on the additional 2 posts in the rear.
Make sure the appropriate brackets are mounted before installing the G30 into the rack.
Figure 46 Rear mounting brackets and shelf rails
g No mounting bracket is shipped with G30 for FRCU chassis. The user needs to order
the appropriate mounting brackets if intend to install G30 in a 19-inch rack, 19-inch
cabinet, 23-inch, or ETSI frameworks.
To install G30 on the framework, first measure the distance S between front installation
surface and rear installation surface from frame work (Figure 47). That will be the
distance S between front and rear mounting brackets (Figure 48).

Figure 47 Distance S between front and rear installation surfaces - 1
Figure 48 Distance S between front and rear installation surfaces - 2

The distance S for different brackets are listed in the following. If the distance S is not in
this range, the mounting brackets could not be installed.
Bracket type The distance S

Minimum Maximum
19” Cabinet Mounting Brackets 530 mm 815 mm
19” Rack Mounting Brackets 76 mm 127 mm
ETSI / 23” Mounting Brackets 10 mm 607 mm
Table 49 Distance S for different brackets

1 19” rack mounting bracket installation steps

1 Attach the front mounting brackets to G30 shelf and fix them with 4pcs floating
screws. Fix the floating screws (on both sides) into G30 shelf to the front
mounting brackets.
Figure 49 Fix the floating screws into G30 shelf
2 Place the shelf rail to appropriate position of shelf side (there are two optional
positions, decide the right position according to the dimension S, as in Figure
47). Take off 2 adjacent screws and install the shelf rail with 2 140.0008 screws
on each side.
Figure 50 Appropriate position according to the dimension S - 1

Figure 51 Appropriate position according to the dimension S - 1
3 Install the rear mounting brackets and G30 shelf.

a Left the shelf to make sure front and rear are in the same RU height.
Figure 52 Install the rear mounting brackets
b Install the rear brackets to framework, do not fully tighten the screws.
c After put the shelf on the rear brackets, push inward the rear brackets so the
rear brackets fit the shelf rail tightly.
d Tighten the screws.

Figure 53 Insert the shelf rail into the rear bracket
4 Install the G30 shelf with front brackets on the framework and fix it with 4pcs
framework screws (140.0039 or 40.0167, depends on screw holes thread metric
on framework).
2 19” cabinet / ETSI / 23” mounting bracket installation steps

1 Place the proper shelf rails to shelf (on both sides) and fixed it by 10pcs screws
(140.0013).
Figure 55 Place the proper shelf rails to shelf
2 Placed the mounting bracket to appropriate position (This step is only for ETSI /
23” Mounting Brackets).
If 10mm < S < 381mm, then the mounting bracket should be 180 degree reverse
installation:
Figure 56 180 degree reverse installation (ETSI mounting brackets for

example)
If 201mm < S < 607mm, then the mounting bracket should be normal position:

Figure 57 Normal position installation (ETSI mounting brackets for example)
3 Install the Mounting Brackets into the framework.

a Make sure proper shelf rails already been installed to the shelf.
b (Optional) Install the floating nut(159-0000-020) to the frame if needed
(especially for the cabinet).
c Use nut driver to fix two brackets onto framework by eight screws (140.0039
or 40.0167, depends on screw holes thread metric on framework).
DO NOT fully tighten these screws.
Figure 58 Fix the Mounting Brackets (take 23 inch bracket for example)
d Tighten the screws.

4 Install the G30 chassis into the framework and fix it by the floating screw. Tighten
all screws on the mounting brackets.
Figure 60 Install the G30 chassis into the framework
4.2.3 Grounding the G30
g The rack needs to be appropriately grounded before grounding the G30 shelf.
To ground the G30:

1. Prepare a grounding cable that no thinner than 12AWG.
2. Attach the end of the grounding cable to the ground stud on the front of the G30.
3. Tighten the screw to secure the connection.
4. Attach other end of ground cable to an area of the rack or cabinet that has been
prepared (paint or oxidation must be removed from the point of connection) or
ground bus bar.
g The grounding method might be different due to different rack types, this section only
shows an example of the grounding connection between a 19-inch rack and the G30.

Figure 61 Grounding the G30 shelf
4.2.4 Installing the AC/DC power modules

To install the power modules, insert the power module toward the chassis until the
module is securely engaged with the back plane.
To install the AC power module:
Figure 62 Install the AC power module
g Make sure the UP indication label is in correct direction when inserting the power
module.
After the AC power module inserted into the slot, fix one cable tie (attached to the AC
power module) into the hole in power module as in Figure 63 to prevent AC power
module from falling off.

Figure 63 Fix with cable tie to AC PSU
To install the DC power module:
Figure 64 Install the DC power module
4.2.5 Connecting AC/DC power cords to the G30
g The 16 amp circuit breaker is required when Groove™ G30 with AC power module
equipped, and the 30 amp circuit breaker is required when with DC power module
equipped.
g Before connecting power cords, make sure every slot is equipped with components, oth-
erwise the corresponding alarms will be raised.
f DANGER!
Always make sure all AC/DC power cords are disconnected when conducting any oper-
ation on the AC/DC power module.
g When plugging in the AC power cord, it is not permitted to operate with power for safety
reason. Power on chassis after plugging in the power cord.

g IMPORTANT!
Coriant provides 2 kinds of power cables when connecting AC/DC power cords on
customer side. One is with RED/BLACK color and the other is with BLUE/BLACK color.
For RED/BLACK cable:
• RED color wire is defined as high voltage

• BLACK color wire is defined as low voltage
So if using -48V power supply, connect the RED wire to GND post and the BLACK wire
to -48V post. If using +48V power supply, connect the RED wire to +48 post and the
BLACK wire to RTN post.
For BLUE/BLACK cable:

• BLACK color wire is defined as high voltage
• BLUE color wire is defined as low voltage
So if using -48V power supply, connect the BLACK wire to GND post and the BLUE wire
to -48V post. If using +48V power supply, connect the BLACK wire to +48 post and the
BLUE wire to RTN post.
Please refer to the following picture when connecting AC/DC power cords on customer
side for detailed information:
Figure 65 AC/DC power cords indication
To connect power cords to the G30, attach the power cords to the AC/DC power
modules and secure them. Refer to Table 90 G30 part numbers for the AC/DC power
cords that can be used with the G30 power modules.

Figure 66 Connect AC power cord
g For safety reasons, when plugging in the AC/DC power cord, do not have the chassis
powered on. Power on the chassis only after plugging in the power cord.
Figure 67 Connect DC power cord

Unlike the AC power cord, the DC power cord is fixed with screws. It is necessary to
unscrew them using a Phillips screwdriver first. Only then the DC power cord can be
unplugged.
f WARNING!
Mixed DC and AC PSU is unsupported and such provision MUST NOT be done.
4.2.6 Checking power LED status

To verify if the AC/DC power feeds are working:
1 Connect A power feed (power module in slot 5 as in Figure 68) and see if B Power
LED on the back panel is amber (for AC power module) or OFF (for DC power
module).
2 Connect B Power feed (power module in slot 11 as in Figure 68) and verify if both
Power A and Power B LEDs are green when both power feeds are ON.
3 Disconnect A Power feed and verify that the A Power LED is amber (for AC power
module) or OFF (for DC power module).
4 Re-connect A Power feed and verify that the A Power LED is green.

Figure 68 LED indication of power unit
4.2.7 Installing the fan modules

To install the fan modules, push the handle toward the chassis until the module is
securely engaged with the back plane. Power on the G30 and check the fan LED status
to verify if the fan modules work fine. Refer to 7.3 LED Behavior for full description of
LED behaviors.
Figure 69 Install the fan module
4.2.8 Installing pluggable modules

Up to 4 CHM1/CHM1G/CHM1LH modules, 2 CHM2/CHM2LH/CHM2T modules, 2
OMD96/48-S modules, or 2 OCC2 modules can be installed on the G30, and the mixed
operation of CHM1/1LH, CHM2/2LH, CHM2T, OMD96/48-S, and OCC2 is allowed. To
install the pluggable module:
1. (Optional) Lift the latch and pull the handle to remove the filler plate.
2. Push the handle toward the chassis until the module is securely engaged with the
back plane.

Figure 70 Install the pluggable module
g Pay more attention when pulling out PABA and PAOSC OFP2 from OCC2 card which
is little bit hard to be pulled out.
4.2.9 Installing the FRCU controller modules (applicable only for FRCU
chssis)
To install an FRCU controller, insert the FRCU controller toward the chassis until the
module is securely engaged with the back plane:
Figure 71 Install an FRCU controller

To remove an FRCU controller:
1. Push the left button which marked “Pull” for at least 5 seconds, the Active LED will
become flashing green and the software is preparing for shutdown, when Active
LED becomes red, FRCU is ready for pull out.
2. Lift the latch upside and hold it.
3. Pull the FRCU controller out.

Figure 72 To remove an FRCU controller
4.2.10 Installing the optical modules into the pluggable modules

To install the optical module:
1. Remove the dust cover from the slot.
2. Carefully slide the module into its slot. Make sure the module engages the shelf fully
and correctly.
Figure 73 Install optical modules into pluggable modules
g Please pay attention that the insertion direction of QSFPs for Port 7 and Port 8
should be in inverted direction (upside down) which is different from other ports.
4.2.11 Connecting fibers

To connect the fiber to the optical module, remove the dust cover, clean and inspect the
fiber cables, then connect the fiber to the pluggable optic module (CFP, QSFP), ensure
that you hear the click. Refer to 6.2 Fiber optic cleaning requirements and 6.3 Fiber optic
cleaning procedures for more information about fiber optic cleaning.

Figure 74 Install fibers
g Ensure that there have at least 1 inch (25.4 mm) for the optical fiber bending radius.
Figure 75 Minimum fiber bending radius
g To avoid fiber routing of module in middle slot to block the insertion of modules into side
slots, keep at least 17cm’s distance between the bending place of fibers and the face-
plate when routing fibers for the module in middle slot.
Figure 76 Fiber routing allow side module plug in/pull out
g It is recommended to route slot 1 and slot 2 modules' fibers to the left and slot 3 and slot
4 modules' fibers to the right for good fiber alignment.

g System fiber routing should use a proper way, for example, use ducting, conduit or
raceway to fix and protect the fibers, and avoid sharp edges and corners when doing the
layout of fibers, and maintain a certain bending radius for the fibers.
4.3 Startup procedures

This section includes the following topics:
• Connecting cables for commissioning port
• Launching Command Line Interface
• Configuring IP address
4.3.1 Connecting cables for commissioning port

Groove™ G30 supports commissioning the NE both through front panel Ethernet port
and Console port.
g Only administrator level users have the privilege to get access to Console port.
Refer to Figure 77 for detailed location of each port.
Figure 77 The G30 connectivity ports

Connect the relevant port before starting the commissioning.
Configurations for Serial Console are listed in below:
• Serial interface provision:
Configurable baud rate (9600, 19200, 38400, 57600, 115200), 8 bits, no parity
g • The console port baud rate is configurable by user. The default value is 9600.
Use the following commands to set (allowed values are 9600, 19200, 38400,
57600, 115200) and show a new baud rate:
set console baud-rate <value>
show console baud-rate
• On G30 shelf with 1.0 boot revision, the change is persistent only after linux boot
up, which means if the user changes the baud rate to a non-default value, and
reboot the system, the baud rate will at first be reverted to 38400, and reset to
the target value after the linux system is up. During the boot up period the user
will see messy and meaningless output which is normal.
• Groove RS-232 Console port RJ45 Pin-out

Pin-out of Groove RS-232 Console port RJ45 is as in the following:

Figure 78 Coriant RS-232 Console Port RJ45 Pin-out
• Groove Console port RJ45-to-DB9 adaptor:

Coriant part number: 150.1175
To be used with a straight Ethernet cable
Terminal Server cable pinout of Coriant RJ45-to-DB9 adaptor is as in the following:
Figure 79 Coriant RJ45-to-DB9 adaptor
• Groove Console port RJ45-to-RJ45 adaptor:

Coriant part number: 251-0991
To be used as adaptor for external Silver Satin Console Cable.
The pinout of Coriant RJ45-to-RJ45 adaptor is as in the following:

Figure 80 RJ45-to-RJ45 adaptor
4.3.2 Launching Command Line Interface

The CLI is available via the NE's Ethernet port 1 (Eth1) (Refer to Figure 77).
g • The default IP address of the Eth1 interface is 169.254.0.1/16. The user needs to
re-configure PC IP address to make it in the same subnet as Eth1 default IP.
• Groove supports DSA, RSA or ECDSA key for SSH sever currently.
Running a CLI session via Eth1 port is only possible via an SSHv2 session. To launch
a CLI session via SSH complete the following steps:
1 Launch an SSH client such as PuTTY (refer to www.putty.org for further details).
2 Configure the following settings on the SSH client window:
IP address: 169.254.0.1/16
Port: 22
3 The CLI Login prompt is displayed.
4 Use the following credentials to login:
User: administrator
Password: e2e!Net4u#

4.3.3 Configuring IP address

After launching CLI, the user can re-configure the default IP address. Typically a default
route is not required to be provisioned on Eth1 interface, and it is recommended that the
default route to be provisioned on Eth2/3 which is reserved for connection to the DCN
network.
There are two ways to provision IP address, via IPv4 or via IPv6(from FP4.0).
• Use IPv4:
1 By default, Eth2 is provisioned as DHCP, the user needs to change DHCP to
static for Eth2.
set ipv4-eth2 ipv4-address-assignment-method static
2 To set IP address for Eth2, for example to set the IP address as

172.29.132.111 and prefix-length as 24:
add ip-address-eth2 ip 172.29.132.111 prefix-length 24
3 To add static route and next-hop static-route, set the default static-route as
0.0.0.0/0, set IP addresses of two next-hops as 172.29.132.1 and 172.29.132.2
and give them labels as 1211 and 1212:
add static-route-static/static-route/0.0.0.0/0
add next-hop-static/static-route/0.0.0.0/0/1211 outgoing-
interface interface-eth2 next-hop-address 172.29.132.1
add next-hop-static/static-route/0.0.0.0/0/1212 outgoing-
interface interface-eth3 next-hop-address 172.29.132.2
g • Groove can support multi-next-hops by giving them different labels identify-

ing different next hops.
• The label can be any string that is valid on CLI at the same time meaningful
to the user, except ‘dhcp’ and ‘migrate’ which has been booked by Coriant
OS.
• Use IPv6:
1 By default, Eth2 is provisioned as DHCP, the user needs to change DHCP to
static for Eth2.
2 To set IP address for Eth2, for example to set the IP address as

2001:0db8:10c0:d0c5::1 and prefix-length as 64:
add ipv6-address-eth2/1 ip 2001:0db8:10c0:d0c5::1 prefix-

length 64

3 To add static route and next-hop static-route, set the default static-route as
0.0.0.0/0, set IP addresses of two next-hops as 172.29.132.1 and 172.29.132.2
and give them labels as 1211 and 1212:
add static-route-static/static-route/::/0
add next-hop-static/static-route/::/0/1211 outgoing-
interface interface-eth2 next-hop-address
2001:0db8:10c0:d0c5::2
add next-hop-static/static-route/::/0/1212 outgoing-
interface interface-eth2 next-hop-address
2001:0db8:10c0:d0c5::3
g • Groove can support multi-next-hops by giving them different labels identify-

ing different next hops.
• The label can be any string that is valid on CLI at the same time meaningful
to the user, except ‘dhcp’ and ‘migrate’ which has been booked by Coriant
OS.
If the default static-route IP is used, one single command can be used to set IP address
for Ethernet Ports, for example, to set IP address for Eth2 using one command:
• For IPv4:
1 To set Eth2 IP address as 172.29.132.111 and prefix-length as 24; set next-hop
IP address as 172.29.132.1:
ifconfig eth2 172.29.132.111 24 172.29.132.1
• For IPv6:
1 To set Eth2 IP address as 2001:0db8:10c0:d0c5::1 and prefix-length as 64; set
next-hop IP address as 2001:0db8:10c0:d0c5::2:
ifconfig eth2 static-ip6=2001:0db8:10c0:d0c5::1 prefix-

length6=64 gateway-ip6=2001:0db8:10c0:d0c5::2
g To enable ZTC function, Eth2 must be reserved for provisioning ZTC and can not be
used for re-configuring the IP address of NE.
g Functions that support to provision IP address via IPv6 are listed in the following table:
Features support IPv6

Netconf
Ssh/CLI
Restconf
Table 50 Features supporting IPv6

Features support IPv6

Syslog
WebGUI
SFTP/SCP
SNMP
NTP
TACACS+/RADIUS
Telemetry
Table 50 Features supporting IPv6
4.3.4 Configure NE Time and NTP Server
The user must configure the time setting after configuring the IP address.
1 Optionally, in case of an NTP server is not readily available during installation, the
ToD (Time of Day) can be locally set as: 2016-07-01T16:17:50+08:00:
set-time new-time='2016-07-01T16:17:50+08:00'
or
set-time '2016-07-01T16:17:50+08:00'
2 Configure NTP (Network Time Protocol). For example, to configure an NTP server
address of 172.23.132.112:
add ntp-association-172.29.132.112 ntp-admin-state up ntp-

association-type ntp-server
set ntp ntp-enabled true
g The user can configure up to 3 NTP servers, and can select one preferred NTP
server with below command:
set ntp-association-172.29.14.178 preferred-ntp-association
true
3 Configure Time Zone.E.g., set the time zone as Beijing-Chongqing-Hong_Kong-

Urumqi[GMT+08:00]
set system time-manager timezone Beijing-Chongqing-

Hong_Kong-Urumqi[GMT+08:00]

4.3.5 Zero Touch Commissioning (ZTC)

ZTC (Zero Touch Commissioning) is a way to accelerate the network deployment and
service activation, while lowering the operator’s cost. It is an effective way to simplify the
installation and activation of devices in the network. The model is referred to as “plug
and play”, where the user doesn't have to do any additional provision in order to use a
peripheral.
With the Zero Touch Commissioning feature, customers can hire unskilled delivery per-
sonnel with limited networking knowledge to drop off the devices shipped directly from
the factory or from the inventory, hook up the power and cables and expect the device
to be turned up and provisioned automatically.
What is ZTC?
- Plug and play; quick, easy and error/hassle-free commissioning without user interven-
tion
- Factory shipped software and provision turns to field software and DCN provision
- Device ID/Location Validation
- Initial bulk service provision [optional]
The following figure is the topology view for the Zero Touch Commissioning function.
Figure 81 ZTC topology view
g If you do not choose to use ZTC, it's strongly recommend to disable ZTC by using the
following command.
set ztc ztc-enabled false
To re-enable ZTC, set ztc-enabled to be true.
set ztc ztc-enabled true

4.3.5.1 Prerequisites
• DHCP Server needs to be prepared on customer side, and DHCP server needs to
be enabled on ETH2 with the following command:
set ipv4-eth2 ipv4-address-assignment-method dhcp
• SFTP Server needs to be prepared on customer side.

• Two Configuration Files, Index file and NE Configuration file must be created per NE
and must be stored on the SFTP Server in advance.
4.3.5.2 Prepare the DHCP Server

When preparing the DHCP server, pay attention to the following provision strings.
Option 60(VCI Vendor Class- Identifier) value must be ‘Groove G30’.
Option 43(VSI Vendor Specific Information) values are defined as follows:
The option 43 string is defined as a hexadecimal string consisting of 3 sub-options, each
sub-option is a TLV (type-length-value) tuple.
Suboption1 - Config MODE: Type[0x1] Length[1] Value:
> fixed value 0x2: Configuration through ZTC
Suboption2 - Index File: Type[0x2], Length [no longer than 237 bytes] Value[ hexadec-
imal string]
Suboption3 - SFTP server IP: Type[0x3], Length [no longer than 15 bytes] Value [IP
address string]
For example, to configure the NE to download the index file named ‘Index.xml’ from
SFTP server ‘172.29.132.89’.
Suboption1: Type = 1, length =1, value =2
> TLV hex: 01 01 02
Suboption2: Type = 2, length = 9, value = Index.xml
> TLV hex: 02 09 49 6e 64 65 78 2e 78 6d 6c
Suboption3: Type = 3, length = 0x0d (13), value = 172.29.132.89
> TLV hex: 03 0d 31 37 32 2e 32 39 2e 31 33 32 2e 38 39
Combined Vendor Specific Information:
01 01 02 02 09 49 6e 64 65 78 2e 78 6d 6c 03 0d 31 37 32 2e 32 39 2e 31 33 32 2e 38 39
4.3.5.3 Prepare SFTP Server
g • Two Configuration Files, Index file and NE Configuration file need to be stored on
SFTP Server in advance.
• SFTP Server requires a pre-defined account, which is defined by Coriant and used
for NE to login SFTP Server.
User account: g30autoconfig
Password: y^2s>j</4FGKhRtD
A simple example for Index File:

<?xml version="1.0" encoding="UTF-8"?>

<ZTC Description="Zero Touch Commission Profile"
Version="1.0">
<Config>
<Item If-mac="0a:00:27:00:00:00" config-file="fileA"/>
<Item If-mac="00:b0:c7:b0:c7:01" config-file="fileB"/>
</Config>
</ZTC>
g •
•
Each item line entry corresponds to one Groove™ NE.
Content inside “” should be defined by User.
• "If-mac" field is the MAC address of ETH2, use the following command to get the
ETH2 MAC address:
show ethernet-eth2
• "config-file" is the name of the corresponding provision file name which can include
the file path on the SFTP server.
The provision file can include provision commands of the target NE using CLI com-
mands. It is recommended that the provision file be tested and evaluated to ensure that
the provision result is as expected and without error before applying it to the target NE.
A simple example for Configuration file:
set port-1/1/1 port-mode not-applicable

set port-1/1/1 port-mode 16QAM_200G
set port-1/1/1 admin-status up
set och-os-1/1/1 frequency 192000000
set och-os-1/1/1 laser-enable enabled
set port-1/1/3 port-mode not-applicable
set port-1/1/3 port-mode 100GBE
g ZTC function needs to be disabled after completing all of the ZTC provision above and
the NE is reachable by using the following command.
set ztc ztc-enabled false
For detailed information please refer to the Groove™ G30 CLI User Manual (UMN).

User Guide (UG) G30 system configuration and management
5 G30 system configuration and management

The G30 muxponder/transponder functions aggregate 10G, 40G and 100G client
signals to provide Wide Area Network (WAN) cloud connectivity services for metro,
regional, and long haul transport applications. Paring the G30 muxponder/transponder
or working stand alone, G30 Open Line System (OLS), provides comprehensive optical
layer functions such as optical multiplexing/de-multiplexing, amplification, tunable dis-
persion compensation and protections.
G30 supports to provision above functions via Web GUI, Command Line Interface (CLI)
and Telecommunication Network Management System (TNMS).For more information
about the Web GUI, refer to the Groove™ G30 Web GUI User Guide. For more infor-
mation about the CLI, refer to the Groove™ G30 CLI User Manual (UMN). For more
information about TNMS, refer to 5.4 Service configuration via TNMS.
5.1 DCN configuration

Data Communication Network (DCN) is a network that carries management traffic
between NEs, namely Groove™ G30 products, and between NEs and the network man-
agement system.
Groove™ G30 supports two types of DCN management:
• Out-band DCN management using an Ethernet interface. For details, refer to
Chapter 4.1 Using an Ethernet interface in Web GUI User Guide.
• In-band DCN management using General Communication Channel (GCC) and
Optical Supervisory Channel (OSC) with or without the Open Shortest Path First
(OSPF) protocol. For details, refer to Chapter 4.2 Using GCC in Web GUI User
Guide.
g G30 now supports to provision the select-mode (loopback-prefer and link-

prefer) of the source address for next-hop routing.
If loopback IP address has been provisioned, when the selective mode is provisioned
as loopback-prefer, the system will select loopback IP as the source IP address. If
loopback IP address has not been provisioned, the effects for choosing loopback-
prefer or link-prefer are the same.
To provision source IP select mode, perform the following two commands:

set networking source-address-select-mode link-prefer
set networking source-address-select-mode loopback-prefer
5.1.1 DCN over ETH interface

Ethernet interface2/3 are used for out-band DCN management. The user needs to refer
to 4.3.3 Configuring IP address on page 97 to set up out-band DCN.
5.1.2 DCN over General Communication Channel (GCC)

The General Communication Channel (GCC) defined by G.709 is in-band channel to
carry management and signaling information within OTN elements.

Groove™ G30 only uses GCC for management purpose. Currently G30 supports
GCC0. Supported GCC functions for CHM1/CHM1LH, CHM1G, and CHM2/CHM2LH
are listed in the following:
• CHM1/CHM1LH/CHM1G
• Supports GCC0 on Line port OTU4 and OTUCn
• Each CHM1/CHM1G supports up to 2 GCC channels, totally 8 GCC channels
for 4 CHM1/CHM1G
• CHM2/CHM2LH
• Supports GCC0 on Line side OTU4 and OTUCn
• Each CHM2 supports up to 2 GCC channels, totally 4 GCC channels for 2 CHM2
GCC bandwidth
Each GCC0 on OTU4 and OTUCn supports raw data rate up to 12.8 Mbps.
Inter-working
GCC channel of G30 could be interconnected with Coriant mTera with cards OSM2C,
OSM4C, or OSM4F, or interconnected with Coriant 7100 with cards HGTMS or
HGTMMS.
g Due to resource conflicts, currently when GCC is enabled, PRBS/ODU OOS (admin
down)/Client ODU will be denied in particular situations. The deny cases between GCC
provision and PRBS are listed in the following:
GCC provi- Client ODU ODUCn ODU4

sioned
Line side OTU4 Deny (only when - Deny
GCC is provi-
sioned)
Line side OTUC2 Deny Deny (only when Deny
GCC is provi-
sioned)
Line side OTUC3 Deny Deny (only when Deny
GCC is provi-
sioned)
Table 51 PRBS deny cases related with GCC on CHM1
GCC provi- Client ODU ODUCn ODUk

sioned
Line side OTU4 Not affected - Not affected
Line side OTUC2 Not affected Deny (only when Not affected
GCC is provi-
sioned)
GCC is provi-
sioned)
Table 52 PRBS deny cases related with GCC on CHM2

Deny cases between GCC provision and ODU Out of Service (OOS) (admin down) on
are listed in the following:

sioned
GCC is provi-
sioned)
GCC is provi-
sioned)
Table 53 ODU OOS (admin down) deny cases related with GCC on CHM1

sioned
GCC is provi-
sioned)
GCC is provi-
sioned)
Table 54 ODU OOS (admin down) deny cases related with GCC on CHM2
Deny cases between GCC provision and port mode switching are listed in the following
on CHM1:
GCC provi- Port mode switching1)

sioned (If line port1 provisioned as GCC port, port mode of client port 3 cannot be switched
or cannot be set as NA, vise verse. Same limitation between line port2 and client
port5)
Line side OTU4 Deny (only when GCC is provisioned)

Line side OTUC2 Deny (only when GCC is provisioned)
Line side OTUC3 Deny (only when GCC is provisioned)
Table 55 Client ODU deny cases related with GCC on CHM1
GCC interface supports both numbered IP address and unnumbered IP address. The
following examples shows two configurable ways based on numbered IP address and
unnumbered IP address separately.
g When provision GCC, pay attention in the following items:

1. OTN entity can be deleted only after GCC is deleted.

2. For GCC0 on line port1 of CHM1, port mode of client port3 cannot be provisioned
as ‘NA’, otherwise the CABS alarm is triggered and blocking the GCC0 port on line
port 1.
3. For GCC0 on line port2 of CHM1, port mode of client port5 cannot be provisioned
as ‘NA’, otherwise the CABS alarm is triggered and blocking the GCC0 port on line
port2.
• Example of GCC provisioning with numbered IP address
## Config sequence: Interface->PPP->IPv4->IPAddres-

>StaticRoute
add interface-ppp1 if-description "gcc0 of otu4-1/1/1" if-
type ppp
#add interface 'ppp1' with interface description as 'gcc0 of
otu4-1/1/1' and interface type as 'ppp'
add ppp-ppp1 ppp-pf-ref ppp-profile-default ppp-resource-ref

otu4-1/1/1 ppp-type gcc0
#add ppp1 to ppp; set profile reference as default profile,
ppp resource reference as 'otu4-1/1/1', and ppp type as
'gcc0'
add ipv4-ppp1 ipv4-forwarding true

#add ipv4 to ppp1 and set ipv4-forwarding as 'true'
add ip-address-ppp1 ip 130.0.0.1 prefix-length 32

#add ip-address to ppp1 and set ip address of ppp1 as
'130.0.0.1' and prefix-length as 32
g 32 is the only available prefix-length to the loopback interface IPv4 address (for
example, X.X.X.X/32). IPv4 address with prefix-length other than 32 will be denied.
• Example of GCC provisioning with unnumbered IP address

## Configuration sequence: Interface->PPP->IPv4->IP-

Unnumbered->StaticRoute
add interface-LOOPBACK if-description "stable loopback

interface" if-type softwareLoopback
#add interface 'LOOPBACK' with the description of 'stable

loopback interface' and interface type as 'softwareLoopback',
the interface-LOOPBACK is created for parent-interface of
ppp1 for unnumbered ip address
Note: Typically the parent interface type is 'softwareLoopback' for unnumbered IP
address GCC.
add ipv4-LOOPBACK ipv4-forwarding true

#add ipv4 to LOOPBACK and set ipv4-forwarding to 'true'
add ip-address-LOOPBACK ip 110.0.0.1 prefix-length 32

#add ip-address of LOOPBACK with '110.0.0.1' and prefix
length of 32
add interface-ppp1 if-description "gcc0 of otu4-1/1/1" if-

type ppp
#add interface 'ppp1' with interface description as 'gcc0 of
otu4-1/1/1' and interface type as 'ppp'
add ppp-ppp1 ppp-pf-ref ppp-profile-default ppp-resource-ref

otu4-1/1/1 ppp-type gcc0
#add ppp1 to ppp; set profile reference as default profile,
ppp resource reference as 'otu4-1/1/1', and ppp type as
'gcc0'
add ipv4-ppp1 ipv4-forwarding true

#add ipv4 to ppp1 and set ipv4-forwarding as 'true'
add ip-unnumbered-ppp1 unnum-enabled true parent-interface

interface-LOOPBACK
#add ppp1 with ip-unnumbered , set unnm-enabled as 'true' and
set interface-LOOPBACK as parent-interface
g The user can use the ifconfig command to simplify the last 4 steps to one step
when provisioning GCC with unnumbered IP address like in the following:

## Configuration sequence: Interface->PPP->IPv4->IP-

Unnumbered->StaticRoute
add interface-SINTF1 if-description "stable loopback

interface" if-type softwareLoopback
#add interface 'SINTF1' with the description of 'stable

loopback interface' and interface type as 'softwareLoopback',
the interface-SINTF1 is created for parent-interface of ppp1
for unnumbered ip address
Note: Typically the parent interface type is 'softwareLoopback' for unnumbered IP
address GCC.
add ipv4-SINTF1 ipv4-forwarding true

#add ipv4 to SINTF1 and set ipv4-forwarding to 'true'
add ip-address-SINTF1 ip 110.0.0.1 prefix-length 32

#add ip-address of SINTF1 with '110.0.0.1' and prefix length
of 32
ifconfig ppp1 gcc0 otu4-1/1/1 SINTF1

#add interface 'ppp1’ then set ppp type of ‘ppp1’ as ‘gcc0’
and set ppp resource reference of ‘ppp1’ as 'otu4-1/1/1',
then set interface-SINTF1 as parent-interface
g • If the user needs to set up tunneled communications via GCC0/eth2 between

multiple G30 shelves, refer to the steps above between every two NEs.
• If modify the OTU/OTUCn with PPP already created on, the error message that
‘status cannot be disabled when a OTU is related with a configuration ppp inter-
face’. Deleting the existing OTU/OTUCn with PPP already created will resolve
this problem.
5.1.3 DCN over OSC with Multi-span application

The OSC (Optical Supervisory Channel) carries information about the multi-wavelength
optical signal as well as remote conditions at the optical terminal or EDFA site. It is also
normally used for remote software upgrades and user (i.e., network operator) Network
Management information. It is the multi-wavelength analogue to OTN GCC.
The OSC ECC channel is divided into two extension channels, named OSCX-1 and
OSCX-2:
• In the ingress direction, the OSCX-1 is identified by the HDLC protocol 0x0021.
OSCX-2 is identified by HDLC protocol) 0x005B.

• In the egress direction, the OSCX-1 and OSCX-2 channels are identified by VLAN
tags, which are set to the FPGA registers by software.
Typical scenario of Groove DCN over OSC with a multi-span application is as in Figure
82.
Figure 82 Typical OSC Scenario with a multi-span application

Here in the following gives a provision example of DCN over OSC:
add interface-oscx1 if-description "oscx111" if-type oscx

#add interface 'oscx1' with the description of 'oscx111' and
interface type as 'oscx'
add oscx-oscx1 oscx-channel 1 oscx-resource-ref osc-1/3.1/1

#add ascx-channel 1 to oscx1 based on physical interface osc-
1/3.1/1
add ipv4-oscx1
#add an ipv4 MO for oscx1
add ip-address-oscx1 ip 130.1.0.100 prefix-length 32

#add ip-address of oscx1 with '130.1.0.100' and prefix length
of 32
add ospf-area-ospfv2/ospfv2-route/0.0.0.0
#add ospf area ospfv2
add ospf-interface-ospfv2/ospfv2-route/0.0.0.0/oscx1 ospf-

linkpf default
#put oscx1 into ospf area ospfv2

5.1.4 OSPF
Groove™ G30 supports OSPFv2 protocol for management purpose. OSPF (Open
Shortest Path First) is supported all out band and in band DCN.
Below in Figure 83 is the typical OSPF scenario for Groove™ G30:
Figure 83 Typical OSPF scenario for Groove™ G30

Groove™ G30 supports the following OSPF functions:
• ASBR (Autonomous System Boundary Router)
Groove™ G30 supports to inject static route to OSPF if ASBR is enabled
• Multiple OSPF areas
• To display the OSPF adjacency status
• To display the neighbor router ID of an OSPF adjacency
• To attach the OSPF link profile to an interface in an OSPF area
Supports up to 10 OSPF link profiles. The parameters that can be provisioned for
OSPF interface by OSPF link profile are: OSPF hello interval, Router dead interval,
retransmission interval.
The default router ID of Groove™ G30 is 169.254.0.1. Two OSPF interface states are
supported: ACTIVE and PASSIVE.
OSPF stub area
A stub area is an area which does not receive route advertisements external to the
autonomous system (AS) and routing from within the area is based entirely on a default
route. When using MCN/Flat IP for a Groove+ hiT7300 network, in order to reduce
number of routes, OSPF stub area is introduced, in this way the user can configure and
enable DCN areas as stub areas.
To provision OSPF stub area, use the following command:
add ospf-area-ospfv2/ospfv2-route/1.1.1.1 ospf-area-type stub

5.1.5 Typical DCN provision example

In the following gives an example to provision a typical DCN network scenario. Figure
84 gives a diagram for a typical DCN network scenario.
Figure 84 Typical DCN network scenario

The following gives the provisions via CLI for this typical DCN network scenario.
On NE128 side:

#Configure loopback interface:

add interface-loopback if-description "loopback" if-type
softwareLoopback
add ipv4-loopback
add ip-address-loopback ip 10.168.101.128 prefix-length 32
#Create GCC interface (unnumbered):

add ppp-profile-111
add interface-ppp111 if-description "set for gcc0 of otuc2-
1/1/1" if-type ppp
add ppp-ppp111 ppp-type gcc0 ppp-pf-ref ppp-profile-111
pppresource-ref otuc2-1/1/1
add ipv4-ppp111
add ip-unnumbered-ppp111
set ip-unnumbered-ppp111 unnum-enabled true parent-interface
interface-loopback
#Configure IP address on Ethernet port:

#Configuration OSPF
add ospf-interface-ospfv2/ospfv2-route/0.0.0.0/ppp123
ospflinkpf default
add ospf-interface-ospfv2/ospfv2-route/0.0.0.0/eth2
ospflinkpf default
set ospf-ospfv2/ospfv2-route router-id 10.168.101.128 admin-
status up
On NE129 side:

#Configure loopback interface:

add interface-loopback if-description "loopback" if-type
softwareLoopback
add ipv4-loopback
add ip-address-loopback ip 10.168.101.129 prefix-length 32
#Create GCC interface (unnumbered):

add ppp-profile-111
add interface-ppp111 if-description "set for gcc0 of otuc2-
1/1/1" if-type ppp
add ppp-ppp111 ppp-type gcc0 ppp-pf-ref ppp-profile-111
pppresource-ref otuc2-1/1/1
add ipv4-ppp111
add ip-unnumbered-ppp111
set ip-unnumbered-ppp111 unnum-enabled true parent-interface
interface-loopback
#Configure IP address on Ethernet port:

#Configuration OSPF
add ospf-interface-ospfv2/ospfv2-route/0.0.0.0/ppp123
ospflinkpf default
add ospf-interface-ospfv2/ospfv2-route/0.0.0.0/eth2
ospflinkpf default
set ospf-ospfv2/ospfv2-route router-id 10.168.101.129 admin-
status up
5.1.6 TCP/IP port information

The information of the TCP/IP ports that Groove listens to is listed in the following table.
Northbound Interface Allowed port Note

CLI 22,4183 Over SSH
NETCONF 830 Over SSH
Web gUI 443 Over HTTPS
Table 56 Information of TCP/IP port Groove listens to

Northbound Interface Allowed port Note

Restconf 8181 Over HTTPS
8080 Over HTTP, disabled by
default
SNMP get 161 161 for GET access
gNMI 50051 For telemetry
Table 56 Information of TCP/IP port Groove listens to
The information of the TCP/IP ports that Groove device connects to remotely is listed in
the following table.
Protocol Allowed port Default port Note

SFTP All ports 22 -
SCP All ports 22 -
SNMP trap - 162 Uses an ephemeral
port provided by the
OS. Only used for
outgoing connec-
tions.
TACACS Provisionable 49 Configurable in
server MO, as per
TACACS server
used.
Default is ‘49’.
Syslog All ports 514(UDP), 601 Msg are sent out
(TCP) from Groove to
remote server. Des-
tination port is spec-
ified by customer,
and source port is
ephemeral.
HTTP All ports 80 -
Table 57 Information of the TCP/IP ports Groove device connects to remotely
5.1.7 FIPS Compliance Mode

The Federal Information Processing Standard (FIPS) is a set of standards describing
document processing, encryption algorithm and other information standards which are
used between non-military government agencies and government contractors/suppliers
cooperating with these government agencies.
When system FIPS is enabled, the following actions will be denied:
• Generating ssh key(by ssh-keygen RPC) with length = = 512 bits and type = = DSA
will be denied.

• Enabling http-support will be denied.

• Setting snmpv3 priv-protocol to DES will be denied.
• Setting auth-protocol to MD5 will be denied.
To set FIPS enabled, use the following command:
set system security system-fips enabled
g When changing aaa-authentication-method to a value other than ‘local-only’, system-

fips must be set as ‘disabled’.
5.2 Transponder/Muxponder
The G30 supports the following traffic functions for transponder/muxponder functions:
• OTN
• 100GBE client mapping into ODU4/40GBE client mapping into ODU3 or 4xO-
DU2e/10GBE client mapping into ODU2 or ODU2e/FC8G/FC16G client
mapping into ODUflex/OC192 mapping into ODU2
• Multiplexing ODU4 into ODUCn/OTUCn (n=2, 3) or OTU4, and de-multiplexing
ODU4s from ODUCn/OTUCn (n=2, 3) or OTU4
• Multiplexing ODU2/2e/3 into ODU4, and de-multiplexing ODU2/2e/3 from ODU4
• Multiplexing ODU-flex into ODU2/2e/3, and de-multiplexing ODU2/2e/3 from
ODU-flex
• Multiplexing up to 20x10G clients into to 2x100G non-coherent ports on XTM2
• Transponder 10GBE/OTU2/OTU2e client ports into to nearby transponder
OCHOS_OTU2/2e line ports on XTM2
• Enhanced coherent line side FEC using SDFEC15, SDFEC25, STAIRCASE7,
SDFEC15ND, SDFEC27ND, SDFEC15ND2
• OTU4 transparent mode between client OTU4 (OTU4_TRANSPARENT port-
mode) and QPSK 100G (QPSK_100G_TRANSPARENT port-mode) with fixed
FEC mode
• OTU4 client side FEC using G709 or no-FEC FEC modes
• OTU2/OTU2e client side FEC using G709, I4, I7, or no-FEC FEC modes
• Delay measurement on terminated ODUk towards line side
• ODU4/3/2/2e/ODU-flex level cross-connections
• Performance monitoring on OCH-OS, OTUCn, OTU4, ODUCn, ODU4, ODU3,
ODU2, ODU2e, Optical layer, and FEC
• Alarm reporting on layers of OCH-OS, OTUCn, ODUCn (limited), ODU4, ODU4,
ODU3, ODU2, and ODU2e
• 100GBE/10GBE/40GBE
• Performance monitoring on PCS/MAC layers, and FEC
• Alarm reporting on layers of 100/40/10GBE PHY/PCS and optical signal
• Supporting IEEE 802.3bj FEC on 100GBE client
• Client side auto laser shutdown for fault propagation
• LLDP (Link Layer Discovery Protocol)
• FC8G/FC16G
• Performance monitoring for LOSS and Symbol Errors
• Alarm reporting on PHY and Optical signal
• Client side auto laser shutdown for fault propagation

• OC192/STM64
• Alarm reporting on Region/Line and Optical signal
• Client side ALS (Auto Laser Shutdown) for fault propagation
• AMP (Asynchronous Mapping Procedure)/BMP mapping into ODU2 on all sub-
ports
• Pseudo random bit sequence (PRBS) testing
• Support J0 label trace monitor
• Diagnosis and testing
• Terminal and facility loopback on line/client ports
• Ethernet PCS idle on 100GBE interface for testing
• OPUk PRBS on terminated ODUkd
5.2.1 Service configuration references

Before configuring service, please refer to the following reference information.
5.2.1.1 Card configuration references

References and parameter descriptions of card configuration are listed in Table 58.
Attributes Type Value Description

equipment name Read and Write Default A string that identifies the
value is N/A module.
required type Read and Write CHM1/CHM A string that indicates the
Can be set only 1LH/CHM1 module type.
when adding the G
card CHM2/CHM
2LH
CHM2T
XTM2
OMD96/48/
64
OCC2
PSU
FAN
admin-status Read and Write up The resource is administra-
tively permitted to perform ser-
vices.
down The resource is administra-
tively prohibited from perform-
ing services.
Table 58 G30 card configuration references

Attributes Type Value Description

oper-status Read-only up The resource is partially or
fully operable and available for
use.
down The resource is totally inoper-
able and unable to provide
service.
avail-status Read-only failed Card is failed for some reason.
g When the card is mismatch The requested card type is not

in normal status, synchronized with actual card
this value is type.
blank. lower-layer- Indicating server layer failure.
down
not-present The card has been removed.
shutdown The card has been shutdown.
degraded Card is degraded.
hibernation The card is set to be hiberna-
tion.
software- Software is in upgrade proce-
upgrade dure.
initializing Card is initializing.
Table 58 G30 card configuration (Cont.)references
5.2.1.2 Port configuration references

This section describes the port configuration references on CHM1/CHM1LH and
CHM2/CHM2LH, CHM2T, XTM2, CHM1G modules.
The port configuration value and description are listed in Table 59.
Port type Configuration Value Description

CHM1/CHM port mode 100GBE Default value. 100GBE service is
1LH/CHM1 provisioned on the subport with
G client port default mapping GMP.
OTU4 Applicable to port.
not applicable No service on the port.
Table 59 Port configuration on

CHM1/CHM1LH/CHM1G/CHM2/CHM2LH/CHM2T/XTM2


CHM2/CHM port mode1) 100GBE Default value. 100GBE service is
2LH client provisioned on client port with
port / default mapping GMP.
subport 40GBE 40GBE service are created on
client port with default mapping
GMP.
subport2) 4 subports under the port are
created to support 4x10G when
the port mode is set to subport,
each subport can support one
10G service.
10GBE Applicable to the subports only.
10GBE service is provisioned on
the subport with default mapping
BMP with fixed stuff.
FC16G Applicable to the subports only.
FC16G service is provisioned on
the subport with BMP mapping.
FC8G Applicable to the subports only.
FC8G service is provisioned on
the subport with BMP mapping.
OC192 Applicable to the subports only.
OC192 service is provisioned on
the subport with default mapping
BMP with fixed stuff.
OTU2 Applicable to subport only.
OTU2e Applicable to subport only.
STM64 Applicable to subport only.
Not applicable No service on the port or subport.

CHM1/CHM1LH/CHM1G/CHM2/CHM2LH/CHM2T/XTM2 (Cont.)


CHM1/CHM port mode QPSK_100G 100G OTU4 service with DP-
1G/CHM2 QPSK coherent modulation
line port format provisioned on the port.
16QAM_200G Default value for CHM1/CHM2
line port. 200G OTUC2 service
with DP-16QAM coherent modu-
lation format is provisioned on
the port.
8QAM_300G 300G OTUC3 service with DP-
8QAM coherent modulation
format is provisioned as 2 x 150G
using both line ports.
Not applicable No service on the port.
CHM2T port mode 100GBE Default value. 100GBE service is
client port provisioned on the port with
default mapping GMP.
XTM2 Mux- port mode OTU4 Applicable to port.
ponder port Not applicable No service on the port.
XTM2 Tran- port mode 10GBE 10GBE service is provisioned on

sponder port transponder port with default
mapping BMP with fixed stuff.
OTU2 Applicable to transponder port.
OTU2e Applicable to transponder port.
OCHOS_O- Applicable to transponder port.
TU2
g Default types of all ports are
OCHOS_O- client, when port mode is set
TU2e to OCHOS_OTU2/2e the
port type will be set to line.

All ports admin-status up The resource is administratively
permitted to perform services.
down The resource is administratively
prohibited from performing ser-
vices.



possible plugga- QSFP or CFP2 A string that defines the sup-
ble type or SFP+ ported pluggable types on the
port.
actual pluggable A string that displays the plugga-
type ble type according to the actual
equipping.
oper-status Up The resource is partially or fully
operable and available for use.
Down The resource is totally inoperable
and unable to provide service.

1) You can only modify the port mode when the impacted port or subport has no cross-
connection created associated with the ODU on the port.
2) You can only modify the port mode of a subport when all the subports under the port
are Not Applicable.
5.2.1.3 Addressing transport layers

The G30 transport layers are created under the port layer, when configuring transport
layers, refer to below indexing syntax for detailed configurations.
Line side indexing syntax

Table 60 shows the line side indexing syntax used to identify the unique layer of the facil-
ity.
Line Mode Created

Transport Type Container index
(port.port-mode) Transport Layer
QPSK_100G OCh-OS och-os-<shelf>/<slot>/<port>
QPSK_100G_TR OTU4 OTU4 otu4-<shelf>/<slot>/<port>

ANSPARENT ODU4 x 1 odu-<shelf>/<slot>/<port>/odu4-1
OCh-OS och-os-<shelf>/<slot>/<port>
16QAM_200G
OTUC2 otuc2-<shelf>/<slot>/<port>
QPSK_200G
OTUC2 ODUC2 odu-<shelf>/<slot>/<port>/oduc2-1
QPSK_SP16QA-
M_200G odu-<shelf>/<slot>/<port>/oduc2-1/odu4-<n>
ODU4 x 2
(where n=1...2)
Table 60 Line side indexing syntax

Line Mode Created

Transport Type Container index
(port.port-mode) Transport Layer
8QAM_300G OTUC3 ODUC3 odu-<shelf>/<slot>/<port>/oduc3-1
odu-<shelf>/<slot>/<port>/oduc3-1/odu4-<n>
ODU4 x 3
(where n=1...3)
16QAM_400G
OTUC4 ODUC4 odu-<shelf>/<slot>/<port>/oduc4-1
64QAM_400G
ODU4 x 4
(where n=1...4)
64QAM_600G OTUC6 ODUC6 odu-<shelf>/<slot>/<port>/oduc6-1
ODU4 x 6
(where n=1...6)
OCHOS_OTU2 OTU2 OTU2 otu2-<shelf>/<slot>/<port>
ODU2 odu-<shelf>/<slot>/<port>/odu2-1
OCHOS_OTU2e OTU2e OTU2e otu2e-<shelf>/<slot>/<port>
ODU2e odu-<shelf>/<slot>/<port>/odu2e-1
Table 60 Line side indexing syntax
Client side indexing syntax

Table 61 shows the client side indexing syntax which uses a similar syntax.
Client Mode Conceptual Created VC

Container index
(port.port-mode) Facility Type (Transport Layer)
100GBE 100gbe-<shelf>/<slot>/<port>
100GbE 100GbE
40GBE 40gbe-<shelf>/<slot>/<port>
40GbE 40GbE ODU3 odu-<shelf>/<slot>/<port>/odu3-1
ODU2e odu-<shelf>/<slot>/<port>/odu2e-1~4 (*)
Table 61 Client side indexing syntax

Client Mode Conceptual Created VC

Container index
(port.port-mode) Facility Type (Transport Layer)
10gbe-<shelf>/<slot>/<port>
10GBE
10gbe-<shelf>/<slot>/<port>.<subport>
odu-<shelf>/<slot>/<port>/odu2-1
10GbE 10GbE ODU2
odu-<shelf>/<slot>/<port>.<subport>/odu2-1
odu-<shelf>/<slot>/<port>/odu2e-1
ODU2e
odu-<shelf>/<slot>/<port>.<subport>/odu2e-1
OTU4 otu4-<shelf>/<slot>/<port>
OTU4 OTU4
otu2-<shelf>/<slot>/<port>
OTU2
otu2-<shelf>/<slot>/<port>.<subport>
OTU2 OTU2
odu-<shelf>/<slot>/<port>.<subport>/odu2-1
otu2e-<shelf>/<slot>/<port>
OTU2e
otu2e-<shelf>/<slot>/<port>.<subport>
OTU2e OTU2e
odu-<shelf>/<slot>/<port>/odu2e-1
ODU2e
odu-<shelf>/<slot>/<port>.<subport>/odu2e-1
OC192 oc192-<shelf>/<slot>/<port>.<subport>
OC192 OC192
ODU2 odu-<shelf>/<slot>/<port>.<subport>/odu2-1
STM64 stm64-<shelf>/<slot>/<port>.<subport>
STM-64 STM-64
ODU2 odu-<shelf>/<slot>/<port>.<subport>/odu2-1
FC8 fc8g-<shelf>/<slot>/<port>.<subport>
FC8G FC8G
ODUflex odu-<shelf>/<slot>/<port>.<subport>/oduflex-1
FC16G fc16g-<shelf>/<slot>/<port>.<subport>
FC16G FC16G
ODUflex odu-<shelf>/<slot>/<port>.<subport>/oduflex-1
(*) Only applicable for only for “40GBMP-ODU2E” port mode.
Table 61 Client side indexing syntax
ODU multiplexing indexing syntax

After mapping the client into the ODUj, the system can transport this ODUj client by mul-
tiplexing it into a high-order ODUk.
Table 62 shows the hierarchical indexing scheme used to represent the multiplexing
relation.

Client Implicitly line side indexing syntax Line Implicitly client side indexing syntax
OTU4
odu-<shelf>/<slot>/<port>/odu4-1
(direct mapping)
OTUC2
(client ODU4 Mux
into one of the 2
(where n=1...2)
ODU4 of the
ODUC2)
OTUC3
(client ODU4 Mux
into one of the 3
100GbE (where n=1...3)
Odu-<shelf>/<slot>/<port>/odu4-1 ODU4 of the
OTU4
ODUC3)
OTUC4
(client ODU4 Mux
into one of the 4
(where n=1...4)
ODU4 of the
ODUC4)
OTUC6 odu-<shelf>/<slot>/<port>/oduc6-1/odu4-<n>
(where n=1...6)
(client ODU4 Mux
into one of the 6
ODU4 of the
ODUC6)
OTU4
odu-<shelf>/<slot>/<port>/odu4-1/odu3-<tp>
(client ODU3 Mux
(where tp=1...80 is the tributary port number of the ODTUG4)
into ODU4)
OTUC2
(client ODU3 Mux odu-<shelf>/<slot>/<port>/oduc2-1/odu4-<n>/odu3-<tp>
into one of the 2 (where n=1...2 and tp=1...80 is the tributary port number of the
ODU4 of the ODTUG4)
ODUC2)
40GbE Odu-<shelf>/<slot>/<port>/odu3-1 OTUC3

(client ODU3 Mux odu-<shelf>/<slot>/<port>/oduc2-1/odu4-<n>/<odu3-tp>
ODU4 of the ODTUG4)
ODUC3)
OTUC4
ODU4 of the ODTUG4)
ODUC4)
Table 62 ODU multiplexing indexing syntax

Client Implicitly line side indexing syntax Line Implicitly client side indexing syntax
OTU4
odu-<shelf>/<slot>/<port>/odu4-1/odu2-<tp>
(client ODU2 Mux
into ODU4)
OTUC2
ODU4 of the ODTUG4)
10GbE ODUC2)
OTU2
OTU2e Odu-<shelf>/<slot>/<port>/odu2-1 OTUC3
OC192 (client ODU2 Mux odu-<shelf>/<slot>/<port>/oduc2-1/odu4-<n>/odu2-<tp>
STM64 into one of the 3 (where n=1...3 and tp=1...80 is the tributary port number of the
ODU4 of the ODTUG4)
ODUC3)
OTUC4
ODU4 of the ODTUG4)
ODUC4)
OTU4
odu-<shelf>/<slot>/<port>/odu4-1/oduflex-<tp>
(client ODU2 Mux
into ODU4)
OTUC2
(client ODU2 Mux odu-<shelf>/<slot>/<port>/oduc2-1/odu4-<n>/oduflex-<tp>
FC8G
Odu-<shelf>/<slot>/<port>/oduflex-1 ODU4 of the ODTUG4)
FC16G
ODUC2)
OTUC3
(client ODU2 Mux odu-<shelf>/<slot>/<port>/oduc2-1/odu4-<n>/oduflex-<tp>
ODU4 of the ODTUG4)
ODUC3)
Table 62 ODU multiplexing indexing syntax
t The ODU indexing syntax of Table 62 is used while creating cross-connections.
5.2.1.4 Facility configuration notifications

When doing facility configuration, please note the following:
• Ethernet inside FEC configuration & FEC Type
Forward error correction (FEC) function is supported on 100GBE client. The FEC
type supports IEEE standard defined FEC.
• Client side port shutdown
Manually shutdown the output laser of current client port.
• Configurable switching of Signal Degrade triggering ALS (SD-ALS) on client port
When SD-ALS switching and ALS are enabled, the port will be shut down if egress
ODU reports defect BERSD-ODU.

• Near end ALS

Near End Automatic Laser Shutdown (ALS) is supported on 10/40/100GBE mode
client port. It will shut down the output laser on the client port which has not received
signal input.
To enable ALS function on each traffic facility, perform the following commands.
Here take 100GBE-1/1/5 traffic facility for example:
set 100GBE-1/1/5 near-end-als yes
#To enable 100GBE-1/1/5 client side ALS. Replace ‘yes’ with
‘no’ to disable 100GBE-1/1/5 client side ALS,
#To enable line side ALS. Replace ‘yes’ with ‘no’ to disable
line side ALS
• UPI - User Payload Identifier
User Payload Identifier (UPI) is supported to set G709 and Gsupp43 on 10GBE
client port.
• Required TX optical power
Required TX optical power is supported on several och-os for adjusting transmitted
power value.
• FEC on OCH-OS
Forward error correction (FEC) function is supported on all line port modes. The
25% FEC type is supported on all line port modes, and the 15% FEC type is only
supported on QPSK port mode.
g Client FEC is enabled by default on 100GE SR4, PSM4, CWDM4 pluggable

modules, for other pluggable modules the user needs to enable the FEC by them-
selves.
• Frequency on OCH-OS
Supports flexible frequency with the tuning interval 1 MHz.
• Frequency for CFP2-ACO
The user needs to take care of the actual operating frequency after the frequency is
provisioned, if the actual operating frequency is out of required range, the user
needs to provision it again according to the actual frequency range of the module.
g TX and RX frequency values of CHP/GHP CFP2-ACO are provisioned through

parameter ‘Frequency’.
• Add service label to port level and cross connections/facilities under port level
Use the following command to set service label, for example, to set service label for
odu-1/3/4/odu4-1 as "S1 to M4":
set odu-1/3/4/odu4-1 service-label "S1 to M4"
Use show command to verify whether the service label has been added success-
fully:
show odu-1/1/3/odu4-1
The following results is displayed:

Figure 85 Show ODU4
5.2.2 Service configuration via CLI

The G30 supports to provision service either through single command step by step or
through one command to create all possible services to the target cards with full provi-
sion.
For one command to create/delete services to the target cards, the user can use the fol-
lowing commands:
create-card-services <card-instance> <line-mode> <client-mode>
delete-card-services <card-instance> <line-mode> <client-mode>
This command allows to create multiple services in a card according with the line and
client side modes. Please note that the client type and line mode are forced to be the
same for all ports after this command is performed. This command will create all neces-
sary intermediate entities automatically for Cross Connections.
g • One command to create card service currently can support to create

services for all client types except under CHM1/CHM1LH regeneration mode.

For provision through single command step by step please refer to the following sub-
chapters in this section.
5.2.2.1 CHM1/CHM1G service provision step by step

By default, 100 GBE entity and client ODU4 are provisioned automatically on a
CHM1/CHM1G module once it’s installed.
In the following is an example showing how to configure 100 GBE service on CHM1 via
CLI. The provision on CHM1G is same with CHM1 except the card type.
1 To add CHM1 and set the line side frequency as 192000000. The default port mode
of line side is 16QAM.
add card-1/1 required-type chm1

# create card CHM1 in Shelf 1/Slot 1.

# set the admin status of line port Shelf 1/Slot 1/Port 1 to
up.
set och-os-1/1/1 frequency 192000000 laser-enable enabled

# set laser frequency to 192000000 and then enable laser on
och-os of Shelf 1/Slot 1/Port 1.
g •
•
For CHM1G, the required card type should be chm1g.
If CHM1 has been inserted, it is not necessary to perform the command ‘add
card-1/1 required-type chm1’.
• The actual configurable value of frequency is based on the optical pluggable
modules which can be accurate to 1M Hz. Supported settable configuration of
frequency is between 191300000 MHz and 196111250 MHz.
2 To set the client port mode of Shelf 1/ Slot 1/ Port 3:

set port-1/1/3 port-mode 100gbe
In the following is an example showing how to configure OTU4 service on CHM1 via CLI:

# create card CHM1 in Shelf 1/Slot 3

up.

#set laser frequency to 192000000 and then enable laser on

2 To change the line port mode of Shelf 1/ Slot 3/ Port 4:
set port-1/3/4 port-mode OTU4

# set the port mode of Shelf 1/Slot 3/Port 4 to OTU4

#set the admin status of Shelf 1/Slot 3/Port 4 to up.
3 To add cross-connection between line side and client side:
add CRS odu-1/3/1/oduc2-1/odu4-1,odu-1/3/4/odu4-1

#add cross-connection between line side and client side
g CHM1G Rev C supports OTU4 QPSK Transparent Mode via the provision on transpar-
ent mode on both client and line side, in the following is an example:
set port-1/3/1 port-mode QPSK_100G_TRANSPARENT
set port-1/3/3 port-mode OTU4_TRANSPARENT
5.2.2.2 CHM2 service provision step by step

To configure services on CHM2 module, modify the port mode based on the service type
you required, then create ODU cross-connection.
When the client port mode is subport, four ODU2 or ODU2e are provisioned on the client
interface.
When the line port mode is QPSK_100G, OTU4 is provisioned on the line port.
When the line port mode is 16QAM_200G, OTUC2 is provisioned on the line port.
To complete the service configuration, provision the line side frequency and enable the
laser. To delete the provisioned services, disable the laser and change the port mode to
Not applicable. Refer to 5.2.1.2 Port configuration references for detailed information
about port mode. Examples of how to configure each client type services are listed in
the following:
• Example of how to configure 100GBE service on CHM2 via CLI
• Example of how to configure 10GBE service on CHM2 via CLI
• Example of how to configure OTU4 service on CHM2 via CLI
• Example of how to configure OTU2/OTU2e service on CHM2 via CLI
• Example of how to configure FC16G service on CHM2 via CLI
• Example of how to configure OC192 service on CHM2 via CLI
• Example of how to configure 5 x 40GBE ports on CHM2 via CLI (with special con-
sideration for the fifth 40GBE interface)
Example of how to configure 100GBE service on CHM2 via CLI

1 To set client port5 port mode as 100GBE:

2 To set admin-status of line port1 and client port5 to ‘up’:

3 To create cross-connections between line side and client side:
add crs odu-1/1/5/odu4-1,odu-1/1/1/oduc2-1/odu4-1
4 Set the laser frequency as 192000000 and enable the laser:

g The actual configurable value of frequency is based on the optical pluggable

modules which can be accurate to 1M Hz. Supported settable configuration of fre-
quency is between 191300000 MHz and 196111250 MHz.
Example of how to configure 10GBE service on CHM2 via CLI



up.

och-os of Shelf 1/Slot3/Port 1

g If CHM2 has been inserted, do not need to perform the command ‘add card-1/3
required-type chm2’.
2 To change the line port mode and sub-port mode of Shelf 1/ Slot 3/ Port 3:

set port-1/3/3 port-mode subport

# set the port mode of Shelf 1/Slot 3/Port 3 to subport

# set the admin status of Shelf 1/Slot 3/Port 3 to up. Stop
the maintenance signal insert into traffic;
set subport-1/3/3.1 port-mode 10GBE

# set the port mode of Shelf 1/Slot 3/Port 3/Subport 1 to
10GBE.
set subport-1/3/3.1 admin-status up

# set the admin status of Shelf 1/Slot 3/Port 3/Subport 1 to
up. Set the subport back to up;

10GBE.

up. Set the subport back to up;

10GBE

up. Stop the maintenance signal insert into traffic;

10GBE.

up. Stop the maintenance signal insert into traffic;
3 To modify mapping mode to BMP-FixedStuff for Shelf 1/ Slot 3/ Port 3:
g Three modes can be set for mapping mode: BMP-FixedStuff, Preamble, and GFP-F.

set 10GBE-1/3/3.1 mapping-mode BMP-FixedStuff

# set the ODU mapping mode of Shelf 1/Slot 3/Port 3/Subport
1 to BMP-FixedStuff

2 to BMP-FixedStuff.

3 to BMP-FixedStuff

#set the ODU mapping mode of Shelf 1/Slot 3/Port 3/Subport
4 to BMP-FixedStuff.
4 To create odu in line side of same-rate with client side for Shelf 1/ Slot 3/ Port 1:
g For BMP-Fixed Stuff mode, set oduc2 as odu2e, for Preamble and GFP-F modes,
set oduc2 as odu2.
add odu-1/3/1/oduc2-1/odu4-1/odu2e-1 trib-slot 1..8

# create first odu2e in tributary slot 1 to 8 of Shelf 1/Slot
3/Port 1/ODUC2 1/ODU4 1

# create second odu2e in tributary slot 9 to 16 of Shelf
1/Slot 3/Port 1/ODUC2 1/ODU4 1

# create third odu2e in tributary slot 17 to 24 of Shelf

# create fouth odu2e in tributary slot 25 to 32 of Shelf
1/Slot3
/Port 1/ODUC2 1/ODU4 1
5 To create cross connections between line side and client side:

add crs odu-1/3/1/oduc2-1/odu4-1/odu2e-1,odu-1/3/3.1/odu2e-1

#create ODU cross connection between line side and client
side ODU2e for subport 1



g This is only an example of how to create 10GBE service on CHM2 card between line
card Shelf 1/ Slot 3/ Port 1 and client card Shelf 1/ Slot 3/ Port 3, if service is desired on
other ports, modify the relevant port numbers.
Example of how to configure OTU4 service on CHM2 via CLI



up.

The actual configurable value of frequency is based on the optical pluggable

# set the port mode of Shelf 1/Slot 3/Port 4 to OTU4


add CRS odu-1/3/1/oduc2-1/odu4-1,odu-1/3/4/odu4-1

Example of how to configure OTU2/OTU2e service on CHM2 via CLI



up.

set port-1/3/4.1 port-mode OTU2

# set the port mode of Shelf 1/Slot 3/Port 4/Subport1 to
subport
set port-1/3/4.1 admin-status up

#set the admin status of Shelf 1/Slot 3/Port 4/Subport1 to up.

3 To add tributary slots for line side odu2-1:
add odu-1/3/1/oduc2-1/odu4-1/odu2-1 trib-slot 1..8

#add tributary slots for line side odu2-1
add crs odu-1/3/1/oduc2-1/odu4-1/odu2-1,odu-1/3/4.1/odu2-1


g • This is only an example of how to create OTU2 service on CHM2 card between line
card Shelf 1/ Slot 3/ Port 1 and client card Shelf 1/ Slot 3/ Port 4, if service is desired
on other ports, modify the relevant port numbers.
• For OTU2e, the steps are similar, the only difference is the client signal type.
Example of how to configure FC16G service on CHM2 via CLI


# create card CHM2 in Shelf 1/Slot 3;

och-os of Shelf 1/Slot 3/Port 1;
2 To set port mode and subport mode of Shelf 1/ Slot 3/ Port 3:

# set the port mode of Shelf 1/Slot 3/Port 3 to subport;
set subport-1/3/3.1 port-mode FC16G

FC16G mode;

up;

3 To add client-signal-type for line side oduflex-1 tributary slot:
add odu-1/3/1/oduc2-1/odu4-1/oduflex-1 trib-slot 1..11

client-signal-type FC16G
#add client-signal-type of line side odu-1/3/1/oduc2-1/odu4-
1/oduflex-1 tributary slot 1..11 with FC16G mode;

add CRS odu-1/3/1/oduc2-1/odu4-1/oduflex-1,odu-

1/3/3.1/oduflex-1
g • This is only an example of how to create FC16G service on CHM2 card between line
card Shelf 1/ Slot 3/ Port 1 and client card Shelf 1/ Slot 3/ Port 3, if service is desired
• For FC8G, the steps are similar, the only difference is, for FC8G, the tributary slot
number of line side odu-1/3/1/oduc2-1/odu4-1/oduflex-1 is from 1 to 7.
Example of how to configure OC192 service on CHM2 via CLI


# create card CHM2 in Shelf 1/Slot 3;
set ocset port-1/3/1 admin-status up

up.
-os-1/3/1 frequency 192000000 laser-enable enabled

och-os of Shelf 1/Slot 3/Port 1;


# set the port mode of Shelf 1/Slot 3/Port 3 to subport;
set subport-1/3/3.1 port-mode OC192

OC192 mode;
set subport-1/3/3.1 port-mode OC192

#set the port mode of Shelf 1/Slot 3/Port 3/Subport 1 to OC192

up;

# set the admin status of Shelf 1/Slot 3/Port 3to up. Stop
3 To add line side tributary slot:

#add tributary slot 1..8 for line side odu-1/3/1/oduc2-
1/odu4-1/odu2-1;
add CRS odu-1/3/1/oduc2-1/odu4-1/odu2-1,odu-1/3/3.1/odu2-1

g This is only an example of how to create OC192 service on CHM2 card between line
card Shelf 1/ Slot 3/ Port 1 and client card Shelf 1/ Slot 3/ Port 3, if service is desired on
other ports, modify the relevant port numbers.
Example of how to configure 5 x 40GBE ports on CHM2 via CLI (with special consider-
ation for the fifth 40GBE interface)

1 To set line side Port 1 to 16QAM, set the frequency as 192000000:


# set the port mode of Shelf 1/Slot 1/Port 1 to 16QAM


g If CHM2 has been inserted, it is not required to perform command ‘add card-1/1
g Configuration of line side is the same with CHM1, the only difference being the con-
figuration of 10GBE/40GBE Tributary Slots.
2 To set client side Port 3 to 40GBE, set Port Mode as GMP:

# set the port mode of Shelf 1/Slot 1/Port 3 to 40GBE
# set the admin status of Shelf 1/Slot 1/Port 3 to up. Set
the port back to up;
set 40GBE-1/1/3 mapping-mode GMP

#set the ODU mapping mode of Shelf 1/Slot 1/Port 3 to GMP.

# create first odu3 in tributary slot 1 to 31 of Shelf 1/Slot
1/Port 1/ODUC2 1/ODU4 1
add crs odu-1/1/1/oduc2-1/odu4-1/odu3-1,odu-1/1/3/odu3-1

#create ODU cross connection between the line side and client
side ODU3
3 To set client side Port 4/5/6 to 40GBE, set Port Mode as GMP, repeat step 3.

4 The fifth port Port 7 needs to be paid special consideration, need to cross-connect
two odu2es on client side with the last two odu2es (odu2e-9 and odu2e-10 of both
odu4-1 and odu4-2) on line side separately. Set the mapping mode and create cross
connections:

# set the port mode of Shelf 1/Slot 1/Port 7 to 40GBE

set 40GBE-1/1/7 mapping-mode 40GBMP-ODU2E

#set the ODU mapping mode of Shelf 1/Slot 1/Port 7 to 40GBMP-
ODU2E.

# create ninth odu2e in tributary slot 65 to 72 of Shelf

# create tenth odu2e in tributary slot 73 to 80 of Shelf

# create ninth odu2e in tributary slot 65 to 72 of Shelf

# create tenth odu2e in tributary slot 73 to 80 of Shelf
add crs odu-1/1/1/oduc2-1/odu4-1/odu2e-9,odu-1/1/7/odu2e-1

slide for the first ODU2e of the 40GBE

slide for the second ODU2e of the 40GBE

slide for the third ODU2e of the 40GBE
slide for the fourth ODU2e of the 40GBE
5 Repeat above steps for the other ports:



set 40GBE-1/1/12 mapping-mode 40GBMP-ODU2E
5.2.2.3 CHM2T service provision step by step

To configure services on CHM2T module, modify the port mode based on the service
type you required, then create ODU cross-connection.
Refer to 5.2.1.2 Port configuration references for detailed information about port mode
before provision. Examples of how to provision services via CLI is listed in the following:
• Example of how to configure 100GBE service on CHM2T via CLI
• Example of how to configure OTU4 service on CHM2T via CLI
Example of how to configure 100GBE service on CHM2T via CLI

1 Set client port7 port mode as 100GBE:

set 100gbe-1/3/7 eth-fec-type disabled
2 Set admin-status of client port to ‘up’ and set alarm report control as ‘alm’:
set port-1/3/7 admin-status up arc-config alm
3 Set admin-status of line port1 to ‘up’ and set port mode as SPQPSK_100G:
set port-1/3/1 admin-status up port-mode SPQPSK_100G
4 Set line port OCH-OS FEC type, frequency and enable laser:
set och-os-1/3/1 fec-type SDFEC27ND frequency 195690795

laser-enable enabled
5 Create cross-connections will be established automatically. If the user has deleted

the cross-connection, the user can add a new one with the following command.
add CRS odu-1/3/1/odu4-1,odu-1/3/6/odu4-1
Example of how to configure OTU4 service on CHM2T via CLI

1 Set client port7 port mode as otu4:
set port-1/3/7 port-mode otu4

set 100gbe-1/3/7 eth-fec-type disabled
2 Set admin-status of client port to ‘up’ and set alarm report control as ‘alm’:
set port-1/3/7 admin-status up arc-config alm
3 Set admin-status of line port1 to ‘up’ and set port mode as SPQPSK_100G:
set port-1/3/1 admin-status up port-mode SPQPSK_100G
4 Set line port OCH-OS FEC type, frequency and enable laser:
set och-os-1/3/1 fec-type SDFEC27ND frequency 195690795

laser-enable enabled
5 Create cross-connections will be established automatically. If the user has deleted

the cross-connection, the user can add a new one with the following command.

add CRS odu-1/3/1/odu4-1,odu-1/3/6/odu4-1
5.2.2.4 XTM2 service provision step by step

To configure services on XTM2 module, modify the port mode based on the service type
you required, then create ODU cross-connection.
Refer to 5.2.1.2 Port configuration references for detailed information about port mode
before provision. Examples of how to provision services via CLI is listed in the following:
• Example of how to configure 10GBE muxponder service on XTM2 via CLI
• Example of how to configure OC192 muxponder service on XTM2 via CLI
• Example of how to configure STM-64 muxponder service on XTM2 via CLI
Example of how to configure 10GBE muxponder service on XTM2 via CLI
1 To set port mode of port1 as OTU4:
2 To set port mode of port2 as 10GBE:
3 To set admin-status of port1 and port2 to ‘up’:

4 To create odu2e in tributary slot 1 to 8 of Shelf 1/Slot 1/Port 1/ODU4-1:
add odu-1/1/1/odu4-1/odu2e-1 trib-slot 1..8
5 To create cross-connections between Access Interface side and Muxponder side:
add crs odu-1/1/2/odu2e-1,odu-1/1/1/odu4-1/odu2e-1
Example of how to configure OC192 muxponder service on XTM2 via CLI

2 To set port mode of port2 as OC192:
set port-1/1/2 port-mode OC192


4 To create odu2 in tributary slot 1 to 8 of Shelf 1/Slot 1/Port 1/ODU4-1:
add odu-1/1/1/odu4-1/odu2-1 trib-slot 1..8
add crs odu-1/1/2/odu2-1,odu-1/1/1/odu4-1/odu2-1
Example of how to configure STM-64 muxponder service on XTM2 via CLI

2 To set port mode of port2 as STM-64:
set port-1/1/2 port-mode STM64

4 To create odu2 in tributary slot 1 to 8 of Shelf 1/Slot 1/Port 1/ODU4-1:
add odu-1/1/1/odu4-1/odu2-1 trib-slot 1..8
add crs odu-1/1/2/odu2-1,odu-1/1/1/odu4-1/odu2-1
g Here we only introduces examples of how to create OC192/STM64/10GBE service on

XTM2 card between Muxponder/Transponder side card Shelf 1/ Slot 1/ Port 1, Shelf 1/
Slot 1/ Port 3 and Access Interface side card Shelf 1/ Slot 1/ Port 2, if service is desired

5.2.3 Service configuration via TNMS
5.2.3.1 Connecting to an NE via TNMS
g If the user uses Netconf client to perform a download operation, note that the download
time requires over 90s and if the timeout of Netconf client is set to 10s, it can't receive
reply.
This procedure provides the necessary steps to establish a connection to an NE via

TNMS.
In case of TNMS connections for continuous NE supervision using NE internal users, to
avoid connectivity problems please take consideration of the following:
• It is advisable to disable all security features otherwise connectivity problems may
occur.
• The forced password change and inactivity time enabled function must be disabled.
Before establishing the connection to the NE, it’s required to provision user account
information via CLI or Web GUI. TNMS does not support creating user account cur-
rently. The default User name and Password are:
User name: administrator
Password: e2e!Net4u#
To establish a connection to an NE via TNMS, complete the following sections in the dis-
played order:
• Adding a DCN Mediator and DCN Channel to TNMS
• Adding a NE to a Multi-Vendor Channel
• Connecting to the Network Element
Adding a DCN Mediator and DCN Channel to TNMS

To add a DCN channel to TNMS, complete the following steps:
1 Start TNMS via Start > Programs > TNMS or double-click on the TNMS desktop
icon.
2 After the TNMS start screen window a blank TNMS window is displayed. Click
Login in the TNMS tool bar to open the “TNMS login” window.
3 Log into the TNMS screen.
4 In the TNMS main tool bar, click Adding a NE to a Multi-Vendor Channelon the DCN
Management icon to open the DCN Management window.
5 In DCN Management, right-click on the TNMS tree and select the New menu item.
The New Mediator window opens.
6 Select Multi-Vendor Mediator as the required Mediator Type and click OK to open
the new Multi-Vendor Mediator properties window.
7 In the General tab, enter an ID Name (for example, the network name) and the
Primary IP of the new Netserver and click OK.
The new icon representing the EM Object will be displayed under the TNMS icon.
The Multi-Vendor Mediator is added to TNMS. Continue to the next section to add a new
Network Element.

Adding a NE to a Multi-Vendor Channel

To add a Multi-Vendor Channel, complete the following steps:
1 Right-click on the Multi-Vendor Channel created in the previous section, and select
the New NE... menu to open the New Network Element window.
2 Select the appropriate version of Groove from the list and then click OK to open the
<NE ID name> properties window.
3 In the General tab, enter an ID Name for the new NE (for example, Groove-location-
1).
4 In the Settings tab, enter the IP address of the remote NE in the Network element
IP field.
5 In the Security area, enter the following settings:
User Name: Enter the NE user account/login name (use the

TNMS-NEC created above).
Password: Enter the password for the encryption protocol.
6 In the SFTP Settings tab, configure the following settings:
Upload path: Enter the location path to upload the file.

User name: Enter user name to access the SFTP server.
Password: Enter password to access the SFTP server.
Click OK to confirm all settings.
The new Network Element is created. Continue with the next section to complete estab-
lishing the connection to the NE.
Connecting to the Network Element

To complete establishing the connection to the new Network Element, complete the fol-
lowing steps:
1 In the DCN Management window select the check boxes of the created Multi-
Vendor Mediator Channel and the created NE (all in the same tree).
2 Verify that the communication is established with the NE via the object icon state or
if Active is displayed in the Activation State column.
3 Right click an NE icon to execute functions directly:
a Click Open NE Command Line console to use Command Line to configure NE.
b Click Performance and Alarm list to view performance and alarms list, and
restoring/backing up configuration or other data.
c Click on Path Management to manage paths.
Your assigned user rights may prevent access to some functions.
t If complete data is not available for certain network elements, these are shown as
unavailable on the user interface (box containing three question marks).
The connection to the new Network Element is established.

5.2.3.2 Operate an NE via TNMS

How to operate an NE via TNMS, please refer to TNMS documentation.
5.2.4 3R regenaration
Groove™ G30 supports re-amplification, re-shaping, and re-timing on CHM1 line side,
which can re-amplify, re-shape, re-time the degraded signals.
To provision a CHM1 card as regeneration mode can set it as a card with 3R function.
The following command is an example to set CHM1 card-1/1 as regeneration mode:
1 Set the card mode as regeneration mode:
set card-1/1 card-mode regen
2 Enable OCH-OS propagate-shutdown from no to yes to forward loss:
set och-os-1/1/1 propagate-shutdown yes
Provisioning CHM1 to be regeneration mode will automatically remove all service on the
card then create regeneration of 16QAM_200G in default between two line ports. The
user can change the line port mode to other supported ones after creating regeneration
mode. After the regeneration mode has been set, client side service cannot be provi-
sioned anymore. The typical scenario of 3R application is as in the following:
Figure 86 Typical scenario 3R application
g Currently G30 CHM1 supports 3R regeneration for the following 3 line modes:
• QPSK_100G, SDFEC15
• QPSK_100G, SDFEC25
• 16QAM_200G, SDFEC25
5.2.5 Encryption
The Groove™ G30 supports OTN encryption on CHM2/CHM1G/CHM2T between
Groove NEs and encrypted ODU channels connecting with multiple Groove NEs inde-
pendently at a time. The Groove™ G30 supports encryption on line side
ODU4/ODU2/ODU2e/ODUflex for CHM1G/CHM2.

g The part number of CHM2/CHM1G which support encryption function are GLS-
G30CHM2Z-00 and GLS-G30CHM1G-00 separately.The part number of CHM2T which
support encryption function is GLS-G30CHM2T-00.
G30 supports to independently enable or disable encryption on each ODU channel. It

supports the following encryption capabilities:
• Support up to 4 ODU4 or 40 ODU2/2e/ODUflex encryption channels on one
CHM2/CHM1G
• Each ODU4 supports maximum 10 ODU2/2e/ODUflex encryption channels
ODU channel session key
ODU Channel Session Key is used to encrypt ODU data, and each ODU Channel
Session Key is created independently according with AES256. Key Synchronization
Session needs to be setup between NEs to synchronize the Synchronization Session
Key.
Key Synchronization between Tx and Rx through TLS session
When key for ODU channel encryption is generated, system will configure the key spe-
cially for OTN encryption key configuration.
The key needs to be derived in both Tx and Rx sides of an ODU channel service:
• Key will be generated at Tx side of an ODU service (the service defined from Tx to
Rx of one direction).
• Tx side will need to synchronize the keys to Rx side to decrypt the ODU channel.
g Note that to avoid directly transferring key, only master secret is sent over TLS
session which is random number, key will be computed from it.
Two options for key transmission:

• TLS session over DCN network for key transmission which is independent from the
ODU channel.
• Using GCC channel of the ODU channel which are physically bounded for key trans-
missions, TLS session will be setup through the GCC channel.
TLS session for key synchronization
• TLS session can be setup over DCN network which is independent from the ODU
channel.
• TLS session can be setup over GCC channel
TLS session authentication
When creating TLS session, the NE receiving incoming TLS connection will use
source IP address in the IP packets to lookup corresponding PSK from PSK list to
do the authentication. If the PSK can be found, authentication succeeds, else fails.
TLS session authentication is based on the Pre-Shared Key (PSK), and the PSK on both
TLS session should be the same, at the same time the far-end IP address should be
stated as PSK-identity to specify who uses the key.
Key-sync channel
Two things need to be done when creating Key-sync Channel:
• Identify which TLS session is used for key synchronization.
• Allocate a network element unique channel ID and make sure the IDs on both end

are the same, which are used to recognize an encryption channel. At the same
time the ODU interval should be the same on both sides to make sure key synchro-
nization.
Provisioning requirement
Only the users with ‘cryptofficer’ class have the privilege to provision Encryption related
functions.
Parameters
Make sure the following values within the following ranges when provisioning encryp-
tion:
• Hex string length of Key: 64-256 bits
• Interval: 10-1440 minutes
Block cipher mode
Two modes can be chose: GCM (Galois Counter Mode) or CTR (Counter)
Provision example
The following gives an example to show how to configure Encryption function via CLI.
g • Before provisioning encryption service, make sure ODU service does not have
alarms.
• Please make sure to provision the following steps on Groove™ G30 of both sides.
• Please login CLI with user class Crypto-officer to provision encryption related func-
tions.
• When remote Groove's psk-map is provisioned with the loopback IP, source-
address-from of key-sync-session of this side must be provisioned as the loopback
interface.
Figure 87 Encryption scenario example

Here gives an example to provision encryption on side A, the user needs to provision
totally the same way on side B.
1 To provision PSK:
add psk-map-123.1.1.211 key 01:02:03:04:05:06:07:08:09

#Add PSK 01:02:03:04:05:06:07:08:09 to associate with peer NE
whose IP address is 123.1.1.211.
2 To create TLS session (key sync session):

add key-sync-session-10 remote-ip 123.1.1.211

#Add a key sync session with session ID ‘key-sync-session-10’
and remote IP address 123.1.1.211
3 To set parameters for ODU encryption created, including encryption interval, block
cipher mode, odu key sync session, encryption TX channel ID, and enable ODU
encryption created.
set -f odu-encryption-1/3/1/odu4-1 encryption-interval 10

#set encryption interval of ODU encryption created as 10
minutes
set -f odu-encryption-1/3/1/odu4-1 block-cipher-mode GCM
#set block cipher mode as GCM
set -f odu-encryption-1/3/1/odu4-1 odu-key-sync-session key-
sync-session-10
#set encryption session ID as ‘key-sync-session-10’
set -f odu-encryption-1/3/1/odu4-1 encryption-tx-channel-id
"EcpHGE"
#set encryption TX channel ID as ‘EcpHGE’
set -f odu-encryption-1/3/1/odu4-1 encryption-enable enabled
#Enable ODU encryption created
g The user needs to make sure the parameters encryption-interval, encryption-tx-

channel-id and block cipher mode on both sides are provisioned as the same value
to make sure encryption can work normally.
4 To show property of ODU encryption created:
show odu-encryption-1/3/1/odu4-1
The following result comes up:
odu-encryption-1/3/1/odu4-1
encryption-enable enabled
block-cipher-mode GCM
encryption-interval 10 minutes
encryption-tx-status 'key-
in-sync'
encryption-rx-status 'key-
in-sync'
odu-key-sync-session key-
sync-session-10
encryption-tx-channel-id 'EcpHGE'

g Refer to CLI User Manual (UMN) for detailed information.
PSK dynamic update

G30 supports dynamically update PSK-MAP for ODU encryption. Once one side of NE
triggers the PSK-MAP update, it will wait for peer NE to update the PSK-MAP and peer
side NE is expected to trigger the update in customer defined time intervals, which are
defined in the following as T1, T2 and T3. If both of the new PSKs that have been
updated for two NEs pass authentication, after existing encryption keys in HW expired,
new PSK will take effect to derive new encryption key.
Authentication failure (PSK mismatch) or failure to trigger the update PSK-MAP
command in 30 minutes in peer NE will cause PSK update failure and UPDATE-PSK-
FAIL event will be reported. If previous PSK-MAP update failed, re-send the command.
Support the following 3 timers when changing the new PSK key
• T1: Raise PSK Fail Alarm (minor) after T1 is timeout
• T2: Raise PSK Fail Alarm (Major) after T2 is timeout
• T3: After T3 is timeout, PSK updating FSM will go to “fail” state and then Encryption
Traffic Squelch Alarm will be raised and the corresponding ODUs are squelched
g By default, the time for T1 timer is 5 minutes, time for T2 timer is 30 minutes, time
for T3 timer is 24 hours. The user can provision the timer by themselves.
Support new attribute effective-timestamp to psk-map with the format of

date/time, to show the time-stamp when the current PSK turning to active.
Support new attribute psk-info to psk-map, to mark out the information of the psk-
map.
Here gives an example to update the PSK:

update-psk-map psk-map-123.1.1.211 update candidate-
key=CC:CC:CC:CC:CC:CC:CC:CC
To cancel the update:

update-psk-map psk-map-123.1.1.211 cancel
Related alarms
• A minor UPDATE-PSK-FAIL will be reported if PSK still not updated after T1
timeout.
• A major UPDATE-PSK-FAIL will be reported if PSK still not updated after T2
timeout.
• An ENC-TRAFFIC-SQUELCH will be reported if PSK still not updated after T3
timeout encryption traffic squelched.
Related events
• UPDATE-PSK-COMPLD: System will notify an UPDATE-PSK-COMPLD event after
psk-map update is completed.

• CANDIDATE-PSK-MISMATCH: System will notify an CANDIDATE-PSK-

MISMATCH event if candidate-key mismatches with peer NE or update-psk-map
operation timeout.
• CANDIDATE-PSK-AUTHENTICATED: System will notify an CANDIDATE-PSK-
AUTHENTICATED event after candidate-key is authenticated by peer NE.
Non-Revertive encryption mode
To prevent other users from editing encrypted ODU, Groove G30 introduces Non-
Revertive encryption mode. Once encryption-enable parameter is set to enabled-non-
revertive, the encryption cannot be deleted, disabled or edited, only if the database has
been cleared the user can set the encryption mode to the default mode.
g Once encryption-enable of one encrypted ODU is set to enabled-non-revertive, the

parameter encryption-enable cannot be set to the other values (enabled,
disabled), at the same time the encrypted ODU cannot be deleted, disabled or edited.
Support PM statistics to count failed encrypted frames

Support a new attribute Encryption-failure-frame to count failed encrypted
frames, which can also be counted based on bin point 15 minutes, 1 hour, or 24 hours.
Time to next key can be visible
Add a new read-only attribute time-to-next-key which is used to show the time left
to rotate the ODU encryption key on TX end of each ODU encryption entity.
g Please pay attention that ONLY crypto-administrator can have privileges to the following
operations:
• Add/delete/change psk-map
• Add/delete/change key-sync-session
• Set/delete/change odu-encryption
But administrator have privileges to VIEW:
• ALL Alarms - including encryption related alarms
• psk-map (not the actual key) - even crypto users cannot view the actual key
• key-sync-session
• odu-encryption
5.2.6 Protocol LLDP (Link Layer Discovery Protocol)

System supports LLDP (Link Layer Discovery Protocol) at Ethernet client side of CHM2
card.
• Support Rx-Only LLDP mode on all Ethernet interfaces of any kind of mapping
mode:
• Per port enable/disable lldp (default disable)
• Global lldp enable/disable (default disable)
• LLDP Rx supports behavior defined in 802.1AB and the defined Rx state machine.
• Support to display LLDP neighbor for each Ethernet interface with LLDP function
enabled.
To enable system LDDP:
set system lldp lldp-status-ne enabled
To enable LLDP on pluggable modules, for example:

set 100gbe-1/1/4 lldp-status-if rxonly

The user can use show command to show LLDP information under port level.
5.2.7 Diagnosis and testing
5.2.7.1 Loopback
Loopback function is to loop the channel on an incoming facility back on itself in the
outgoing direction for monitoring purposes.
There are four types of loopbacks:
• Facility loopback of a client signal (client-side)
• Facility loopback of a line facility (line-side)
• Terminal loopback of a client signal (port-side)
• Terminal loopback of a line facility (client-side)
Below in Figure 88 is the diagram of Loopback.
Figure 88 Diagram of Loopback
5.2.7.2 Test signal

The Transponder BER (Bit Error Rate) Test Signal Generation feature integrates the
transmit and receiving PRBS BER test signal on transponders. Using the PRBS test
signal in conjunction with loopbacks at various points in the network, faults can be better
isolated within the network. The integration of the BER feature eliminates the need for
expensive test equipment. The BER feature generates the PRBS pattern toward the
client-side or line-side via the corresponding facility.
When enabling the test signal on the 100GBE client, the test signal is sent with idle
frame not PRBS pattern.
5.2.7.3 Delay measurement

Delay measurement (DM) function support to measure the transfer delay between to
line ports.
In CHM1 it supports DM on terminated ODU4 level towards Line side.
In CHM2 it supports DM on terminated ODU4 and ODUj (j=2, 3, 2e) level towards Line
side.

Support PM parameter of DM on ODU supporting this function, run at least once every
minute.
Support disable/enable DM measurement for individual entity - DM Source.
• When disable, the terminated ODU shall loopback the DM bit.
• When enable, the terminated ODU shall initiate DM measurement by inverting the
DM bit.
DM_source = disabled DM_source = enabled

DM bit stream carrying measured DM value is
ODUk ODUk
inside OH of the ODUk supported as a PM
OTU4 OTU4 parameter of the ODUk
ODUk Or Or ODUk
… OTUCn OTUCn …
ODUk ODUk
Card - A Card - Z
Figure 89 Diagram of delay measurement

Example to provision the DM as in the following:
set pm-point-odu-1/1/2/odu2e-1/delay-measurement-odu/*
supervision-switch enabled thresholding-switch enabled
#Set the Supervision Switch and Threshold Switch of of odu-
1/1/2/odue-1 DM as enabled
set odu-1/1/2/odu2e-1 delay-measurement-enable enabled
#Set delay measurement of odu-1/1/2/odue-1 as enabled
g When provision end to end service, normally the user should not enable DM on both
sides. If the user enabled DM on both sides, the display of delay measurement value
should be N/A (‘9999999’ legally) on both sides, currently the situation is ‘9999999’ one
side and around ‘1000’ on another side, please ignore that, just for fear the user enabled
DM on both sides.
5.2.8 OTU deny behavior

Groove™ G30 has provision limits for several of its functions, for different functions the
conditions for provisions are different.
Table 63 lists related function behaviors according with different ODU termination
modes.
Related functions non-OTN facility OTN facility
Terminated Terminated Non-terminated
Table 63 Deny behavior for ODU terminated mode related functions

Related functions non-OTN facility OTN facility
nim Deny disable opera- Deny disabled oper- No Deny

tion ation; Auto set nim Nim of ODU under
to enable OTN facility shall
set to enabled when
CRS deleting
TX-TTI No Deny No Deny Deny input
Creating CRS must
be denied when TX-
TTI is not empty or
default
TIM-action No Deny No Deny No Deny (TIM-
action does not
work under Non-ter-
minated type)
Test signal (PRBS) No Deny No Deny Deny enable opera-
tion if the CRS could
be added/deleted
manually by cus-
tomer.
Creating CRS must
be denied when
Test-signal is
enabled.
Delay Measure- No Deny Deny enabled oper- Deny enabled oper-
ment ation ation
TX PT Deny input opera- No Deny Deny input opera-
tion tion
RX PT Read only, could Read only, could No value
read read
Table 63 Deny behavior for ODU terminated mode related functions
5.3 Open Line System (OLS)

Groove™ G30 supports Open Line System (OLS) which includes optical multiplex-
ing/de-multiplexing, optical power amplification, tunable dispersion compensation and
protection functions.
5.3.1 OCC2 Configuration

OCC2 (Optical Carrier Card) is the most compact amplifier solution for configurable
optical layer. Each G30 supports up to 2 OCC2 cards, each OCC2 card has 3 OFP2
cages. G30 supports two types of OFP2: PAOSCOFP2 and PABAOFP2.
In the following is an example to show how to configure OCC2 via CLI.

1 To add a OCC2 card on Shelf1/Card3:
add card-1/3 required-type OCC2

#create card OCC2 on Shelf 1/Slot 3
2 To add PABAOFP2 on Shelf 1/ Card 3/ Subcard 1:
add subcard-1/3.1 required-type PABAOFP2

#create subcard PABAOFP2 on Shelf 1/Card 3/Subcard 1
3 To add PAOSCOFP2 on Shelf 1/ Card 3/ Subcard 2:
add subcard-1/3.2 required-type PAOSCOFP2

#create subcard PAOSCOFP2 on Shelf 1/Card 3/Subcard 2
4 To enable amplifier:
Set amplifier amplifier-enable enabled

#To set all amplifiers enabled
5 To show amplifier on both Subcard1 and Subcard2:
show amplifier
amplifier supporting-input-port supporting-output-port admin-status oper-status avail-status

alias-name amplifier-enable input-los-shutdown control mode amplifier-mode
amplifier-1/3.1/ba port-1/3.1/2 port-1/3.1/1 up down not-
present lower-layer-down enabled enabled constant-gain
amplifier-1/3.1/pa port-1/3.1/1 port-1/3.1/2 up down not-
present lower-layer-down enabled enabled constant-gain
amplifier-1/3.2/pa port-1/3.2/1 port-1/3.2/2 up down lower-
layer-down mismatch enabled enabled constant-gain
amplifier-1/3.3/pa port-1/3.3/1 port-1/3.3/2 up up
enabled enabled auto constant-gain
amplifier amplifier-type target-gain operating-gain (dB) gain-adjustment (dB) gain-range-

min gain-range-max target-power output-power-mon output-power-mon-with-ase input-power-mon
amplifier-1/3.1/ba fixed-gain-EDFA 8.0 8.0 0.0 8.0
8.0 10.7 10.7 2.7
amplifier-1/3.1/pa variable-gain-EDFA 10.0 10.0 0.0 10.0
27.0 10.0 10.0
18.0 -99.0 -99.0 -44.4
18.0 -99.0 -99.0 -44.4
6 To set target-gain for PA.

set amplifier-1/3.1/pa target-gain 16

#Set target gain of amplifier-1/3.1/pa as 16
The user also can automatically set the target-gain for PA with the following
command. In auto mode, PA can adjust the target-gain value to compensate the
span loss.
set amplifier-1/3.1/pa control-mode auto
7 To set Generic Optical Section Interface Facility (GOPT)/Optical Multiplex Section

(OMS) for PABAOFP2 and PAOSCOFP2.
g GOPT/OMS cannot be created, it's created by default. The user can set the admin
status of GOPT/OMS with the following two commands.
For OMS and GOPT existing before upgrade to FP2.1, the entities will be allowed to
be explicitly deleted manually.
Since FP2.1, explicitly creating or deleting optical interfaces, e.g. OMS, GOPT (with
exception mentioned above), OSC and OTS, will not be supported.
Adding optical interfaces, e.g. OMS, OTS, OSC and GOPT, on the card needs to
recreate the card entity.
set gopt-1/3.1/2 admin-status down

#Set admin status of GOPT to down
set oms-1/3.1/2 admin-status down
#Set admin status of OMS to down
8 To show GOPT on both Subcard1 and Subcard2:

show gopt
gopt admin-status oper-status avail-status alias-name supporting-rx-port

supporting-tx-port rx-optical-power tx-optical-power
gopt-PABA-DWDM up up port-1/3.1/2 port-/3.1/2 -99.0 -99.0
9 To show OMS on both Subcard1 and Subcard2:
show oms
5.3.1.1 Multi-span OLS

G30 supports multi-span OLS scenarios starting from FP3.1, which uses Inline Amplifier
(herein after referred to ILA) to link Groove terminals at the ends with 48 or 96 channel
optical Mux/Demux.

The following graphic gives a typical application with two spans.
The terminal OLS nodes can be same terminal node configuration as single span appli-
cation supported previously:
• PAIR/LR/ER OFP2
• BAH OFP2
• OMD48-S
• OMD96
The ILA nodes are based on following amplifiers:
• PAIR/LR/ER OFP2
5.3.2 Optical Protection Switch (OPS) module

Groove™ G30 supports Optical Protection Switch (OPS) function with Optical Protec-
tion Switch Module which creates 1+1 protection group between working and protection
ports through O2OPS OFP2 modules working together with CHM/XTM2 modules.
g CHM2T only supports OMS protection in current release.
The key enabling module O2OPS OFP2 supports 1+1 protection. In the transmission
direction optical signal will be bridged to both working and protection directions, the
receiving end selects one way optical signal according to optical power level and
external command.
O2OPS OFP2 supports the following features:
• Support manual/force/lockout/clear external switch command
• Support revertive protection and non-revertive protection switch
• Support auto protection switch per SF (LOS) and SD (degrade power level)
• Hold off timer
The following optical protection types are supported by Groove™ G30 with O2OPS
card:
• O2OPS OTS (Optical Transmission Section) protection
• O2OPS OMS (Optical Multiplex Section) protection
• O2OPS OCH protection
• O2OPS Client protection
g CHM cards support all kinds of protection including OTS/OMS/OCH/Client protection

types, and XTM2 supports Client protection with STM64/OC192, OTU2/2e, and 10GE
services, at the same time XTM2 supports OTS protection with FC8G/16G.

Typical application diagrams of OTS/OMS/OCH/Client protection refer to Groove™

G30 POL manual.
5.3.2.1 OTS protection provision

After the O2OPS card are installed, OPS protection will be provisioned automatically.
To ensure that OTS protection works properly, the user still needs to provision the fol-
lowing steps:
1 Transponder client side
If necessary properly enable idle insertion and provision idle duration on transpon-
der card. Ensure that the client shutdown holdoff timer has been set, which hold off
the consequent actions during protection switch., for example:
set 100gbe-1/3/4 holdoff-signal yes client-shutdown-holdoff-
timer 100
Optionally the user can enable or disable client shutdown per application, which
share the same hold off time setting for maintenance signal. For example, here set
client shutdown as ‘no’:
set 100gbe-1/3/4 client-shutdown no
2 Transponder line side
Coherent CD search range will impact coherent interface re-sync time. Presetting
the CD search range value to properly cover actual working and protection CD value
could reduce the sync time.
set och-os-1/3/1 cd-range-low -2000 cd-range-high 2000
g The OSNR values of working and protection paths should meet the specification.
3 Amplifier card
Pre-amplifier shall be provisioned to disable pump shutdown:
set amplifier-1/1.2/pa input-los-shutdown disabled
g • To minimize interruption time, OTS measured span loss should be within the
gain variable range of pre-amplifier.
• To minimize interruption time, OTS span loss difference between working and
protection paths should be less than 2 dB.
4 Properly set wavelength band:

set ops-1/1.3/1 wavelength-band 1550
5 If there is no nested protection, properly set OPS hold-off timer according to appli-
cation. Here takes 0 as an example:
set ops-1/1.3/1 holdoff-timer 0
6 Properly set thresholds for working and protection paths:
set ops-1/1.3/1 working-switch-threshold -20 working-los-
threshold -30 protection-switch-threshold -20 protection-los-
threshold -30

5.3.2.2 OMS protection provision

After the O2OPS card are installed, OPS protection will be provisioned automatically.
To ensure that OMS protection works properly, the user still needs to provision the fol-
lowing steps:
the consequent actions during protection switch, for example:
timer 100
g The OSNR values of working and protection paths should meet the specification.
3 Amplifier card
Pre-amplifier must be provisioned to enable pump shutdown:
set amplifier-1/1.2/pa input-los-shutdown enabled
threshold -30
Power difference checking mechanism for OMS

Currently G30 can support to check the power difference between the working and pro-
tection paths for OMS protection, then to compare with the threshold/threshold hystere-
sis which the user set to switch and switch back. If the actual difference value after the
offset adjusted is larger than the working-protection-relative-threshold value, the path
will be switched to the backup path. If the actual difference value after the offset adjusted
is lower than the relative-threshold-hysteresis, the path will be switched back.
Here gives an example to provision the power difference checking mechanism:

cryptoadministrator@System_04:c0:9c:b1:5b:ab> set ops-1/1.3/1

working-protection-relative-threshold 5
**set the working-protection-relative-threshold as 5dB
relative-threshold-offset 1
**set the relative-threshold-offset as 1dB
relative-threshold-hysteresis 2
**set the relative-threshold-hysteresis as 2dB
5.3.2.3 OCH protection provision

After the O2OPS card are installed, OCH protection will be provisioned automatically,
for detailed provisions, refer to 5.3.2.5 OPS related principles.
To make sure OCH protection works properly, the user still needs to provision the fol-
lowing steps:
der card. Make sure the client shutdown holdoff timer has been set, which hold off
timer 100
could reduce the sync time:
g The OSNR values of working and protection paths should meet the spec.
3 Amplifier card
Pre-amplifier must be provisioned to enable pump shutdown per input LOS:


threshold -30
5.3.2.4 Client protection provision

After the O2OPS card are installed, Client protection will be provisioned automatically,
for detailed provisions, refer to 5.3.2.5 OPS related principles.
To make sure OCH protection works properly, the user still needs to provision the fol-
lowing steps:
timer 100
Ensure client shutdown is set as ‘yes’, if not set it as ‘yes’:
set 100gbe-1/3/4 client-shutdown yes
g Ensure that the client type of pluggable modules used on CHM cards is Dual Rate
type (ZXS-Q8L4PRDR-00) when provisioning client side protection.

g The OSNR values of working and protection paths should meet the spec.
3 Amplifier card
Pre-amplifier shall be provisioned to enable pump shutdown per input LOS:
threshold -30

5.3.2.5 OPS related principles
Revertive mode
G30 supports revertive mode to switch the normal traffic signal from the Protection
Channel back to the Working Channel when this Working Channel has recovered from
fault.
WTR (Wait to Restore Timer) is introduced to Revertive Mode. Upon the clearing of all
defect conditions on the Working Channel, a system in the revertive mode delays the
automatic revertive switch from the Protection Channel to the Working Channel for a
Wait to Restore (WTR) period. If a failed condition presents on the Protection Channel,
the automatic revertive switch will not be delayed.
A system provisioned with the Revertive Mode and being on the Protection Channel
should restart the WTR timer whenever a defect is detected and cleared on the Working
Channel.
Range of WTR: 0 to 60minutes with increments of 1 second and an accuracy of +/- 0.5
seconds
Default value: 300 seconds (5 minutes)
Holdoff timer
In normal case, when there has failure happened on working path, there should not have
failure signal detected on external client equipment in the duration of protection. To
avoid impact on client equipments during switching over on upstream protection
module, including Router, Switch and so on, at the same time to hold off software
inserted maintenance signal and client ALS (Auto Laser Shutdown), Groove™ G30
introduces Hold Off Timer which can be provisioned to hold off failure signal for the time
specified by the hold off timer.
Holdoff duration
From 0 to 1000ms with 50ms step.
Holdoff behavior
• When SF (Signal Failure)/SD (Signal Degrade) is detected from line to client direc-
tion (for ALS, it shall include client ingress LOS/LOSYNC if near-end-ALS is set to
be yes), client ALS or maintenance signal insertion shall be held for the time speci-
fied by the hold off timer.
• If the SF/SD is cleared before the timer timeout, the client ALS or maintenance
signal should not be inserted, traffic will recover once fault cleared.
• If the SF/SD is not cleared in the duration, client ALS or maintenance signal shall be
inserted.
Forcing IDLE ordered set insertion

Due to external Routers or Switches are not expected to be triggered by the transient
failure during duration of protection switching, G30 introduced Forcing IDLE Ordered
Set Insertion mechanism to avoid consequent action on the client router and switch to
the transient failure, the mechanism is configurable to force Idle ordered sets output for
a defined duration when line to client failure (SF/SD) happens, the IDLE duration shares
the same holdoff time setting for maintenance signal. Several configuration notifications:

• Applicable to CHM2/CHM2L, XTM2

• Only applicable to Ethernet client port
• Only applicable to GFP-F mapping mode
• Applicable to 10GE, 40GE, 100GE
Behavior
After client side enabling IDLE insertion, IDLE shall be inserted when failure detected
from line to client direction (egress of the client) for a duration defined by hold off timer.
Two circumstances:
• If the defect is cleared before the timeout, traffic shall recover once fault cleared.
• If defect is not cleared before timeout, the client shall work normally, e.g., insert
maintenance signal per the failure, pass traffic downstream if failure cleared.
CD search range configuration

Coherent CD (Chromatic Dispersion) search range can significantly impact coherent
interface re-synchronizing time, to extend CD search range can increase the interruption
time to be hundred millisecond. Groove™ G30 allows to configure the CD search range
per the interface connected link.
Two attributes are added under coherent OCH-OS entity:
+--rw cd-range-low? uint32
+--rw cd-range-high? uint32
3R regeneration without client

Line 3R regeneration implement OEO regeneration of coherent signal between two line
ports of one CHM1/CHM1L card without client transceiver on Non-Diff 25% FEC DP-
QPSK mode. OPUk PRBS is supported on ODU4 in re-generation mode.
Facility loopback is supported on two line ports independently in re-generation mode.
5.3.2.6 Basic configurations

In the following gives an example configuration for OPS configurations:
To show OPS configuration on ops-1/3.3/1:
show ops-1/3.3/1
Use set command to set relative parameters, for example:

set ops-1/3.3/1 revertive no wait-to-restore 25
set ops-1/3.3/1 revertive yes wait-to-restore 25
set ops-1/3.3/1 working-switch-threshold -18 working-los-threshold -23
Use the following commands to enable protection, lockout protection and release the
lock:
protection-switch ops-1/3.3/1 force protection
protection-switch ops-1/3.3/1 lockout

protection-switch ops-1/3.3/1 release

The switch priorities for above switch commands are listed in Table 64.
Switch command Priority

Lockout for Protection (LoP) 1 (highest priority)
Forced Switch (FS) 2
Signal Fail (SF) 3
Signal Degrade (SD) 4
Manual Switch (MS) 5
Wait-to-Restore (WTR) 6
Do Not Revert (DNR) 7
Not Request (NR) 8 (lowest priority)
Table 64 Switch priorities
5.3.3 PAM4 application

Coriant OLS system is capable to support Pulse Amplitude Modulation level-4 (PAM4)
DWDM transmission for Data Center Interconnections. The typical configuration
includes OMD48-S, TDCM, and high power EDFA.
5.3.3.1 TDCM modules

The TDCM (ZXS-O2TDCMZZ-00) is a tunable dispersion compensation module. It is
dedicated for the dispersion compensation for the ultra high power pre-amplifiers on the
G30. The current supported preamplifier is PAOULR (ZXS-O2PAOULR-00).
When the TDCM supports the PAOULR for the PAM4 applications, the maximum com-
pensation distance is up to 80 km. The achievable performance needs to be evaluated
against detailed optical link. For the implementation of the G30 PAM4 applications, refer
to POL manual.
5.3.3.2 High power EDFA

Groove™ G30 supports high power PA and BA amplifiers (>21.3dBm) for Pulse Ampli-
tude Modulation (PAM4) application, including PAULROPF2 (ZXS-O2PAOULR-00) and
BAUOFP2 (ZXS-O2BAUZZZ-00), their output saturated power can be as high as
24dBm and 25dBm separately.
5.3.3.3 Automatic Power Shutdown (APSD) for Laser Safety

Since the Groove™ G30 supports high power PA and BA amplifiers (>21.3dBm) for
Pulse Amplitude Modulation (PAM4) application, Laser Safety has been introduced to
Ensure that the product meet class 1M requirement.
If the C-band signal of optical detector has been detected open exposed, the system will
turn off amplifier’s C-band to prevent power of PA and BA amplifiers too high. If the

system detects the auto shutdown condition cleared it will automatically recover to turn
on the amplifier within 10s after the auto shutdown condition clears.
g The system does not support to recover without software control, so recovery will not be
done when the system in warm reboot. If fiber link fixed in warm reboot, recovery will be
completed within 10s after system boot up.
Affected modules and applications

• PAULROFP2 (connected with fiber port side)
The PA will launch one 1610 wavelength out of DWDM port, if the paired BA (for con-
figuration of PA+BA), or PA port side have not received loopback back 1610 wave-
length, the PA will turn off it pump.
• BAUOFP2 (connected with OMD side)
The laser safety will be triggered when OTS LOS is detected, which will turn off both
BAs of the fiber link.
The BA will not be turned on until both ends of the fiber link detecting the link fixed
at both directions.
Application scenarios
Laser safety has two application scenarios, one is Port Side scenario in which laser
safety optical modules connects with port side OMD ports to control the laser safety,
another is Line Side scenario in which safety optical modules connects with far end NE
with optical fiber.
The application diagram of port side laser safety scenario is as in the following:
Figure 90 Application diagram of port side laser safety

The application diagram of line side laser safety scenario is as in the following:

Figure 91 Application diagram of line side laser safety
5.3.4 Optical Time Domain Reflectometer (OTDR)

The OTDR 4-PORT (ZXS-O2OTDR4Z-00) has four OTDR ports. Each port conducts
one-direction OTDR measurement on a specific fiber optics link. Measurements among
different ports are taken sequentially.
Figure 92 illustrates the implementation of the OTDR measurement.
Figure 92 Implementation of the OTDR measurement

To configure an OTDR or view the measurement results, use the tool Web GUI. For
details, see Section Using the OTDR function, in Coriant GrooveTM G30 Web GUI User
Guide.
g The OTDR module does not support ultra high power amplifiers or PAM4 links, in which
1610 nm optical supervisory signals do not comply with the OTDR 1590 nm wavelength.
From FP4.0, G30 starts to support fiber connection for all optical ports. Fiber connec-
tions between all kinds of optical modules are listed in 5.3.6 OLS fiber connections on
page 168.

5.3.5 OCM (Optical Channel Monitoring)

G30 supports Optical Channel Monitoring (OCM) function which can monitor the power
of OMD/OFP2 cards to individual port level. OCM OFP2 is a common OFP2 Form
Factor with 4 single LC OCM ports, it can be supported on any OCC2 slot. OCM OFP2
supports the following features:
• Support 50G, 75G, 100G grid’s power monitoring
• Support optical power monitoring on individual wavelength
• Power monitoring for Coherent channel monitoring with all supported roll-off, DGE
• Power monitoring for offset grid PAM4 channels
• Power monitoring for NRZ channels, for example, 10G
• Power monitoring accuracy to +/-0.5dB
• Applicable to the power range of POL amplifiers/OMD supporting OCM ports
• Support OCH entity management on DWDM line degree interface
• Support fiber management association between OCM and amplifiers that has OCH
entity
• For port with OCH entity, able to calibrate power of amplifier’s DWDM line port
• For port without OCH entity, Support monitored channel list retrieval on OCM port
for those non-DWDM line ports
• Support LOS reporting on OCH level with OCM support
When monitoring Amplifier cards, OCH entity will be created to manage optical channel
on DWDM line port. The users can create and delete OCH entity. Usually an OCH entity
will specify one parent OMS entity.
Figure 93 illustrates the typical scenario of the OCM measurement.
Figure 93 Typical scenario of OCM measurement

Modules supporting OCH and OCM Monitoring are list in Table 65.

Modules OCH port Grid types Power Calibrated to OCM

ports Monitor
port
PAOSCOFP DWDM Line 50G 96ch, DWDM Line (in/out) ocm-line
2 100G 48ch in/out
PABAOFP2 DWDM Line 50G 96ch, DWDM Line (in/out) ocm-line

100G 48ch in/out
PAIROFP2 DWDM Line 50G 96ch, DWDM Line (in/out) ocm-line

100G 48ch in/out
PALROFP2 DWDM Line 50G 96ch, DWDM Line (in/out) ocm-line

100G 48ch in/out
PAEROFP2 DWDM Line 50G 96ch, DWDM Line (in/out) ocm-line

100G 48ch in/out
BAHOFP2 DWDM Line 50G 96ch, DWDM Line (in/out) ocm-

100G 48ch dwdmout
OMD96 - - - OCM
DWDM
in/out,
physical
fiber
connect
OMD48-S - - - OCM
DWDM
in/out,
physical
fiber
connect
OMD64 - - - OCM
DWDM
in/out,
physical
fiber
connect
BAUOFP2 - - - ocm-
dwdmout
PAUL- DWDM Line 50G 96ch, DWDM Line (in/out) ocm-line
ROFP2 100G 48ch in/out
Table 65 Modules supporting OCH and OCM Monitoring
LOS threshold of OCH entity

LOS threshold of OCH entity is listed in Table 66.

OFP2 Line in OCH LOS thresholds at

modules Line out OCH LOS thresholds output of PA
declared clear declared clear

PAOSC -22 -19 -22 -19
PABAOSC -6 -4 -22 -19
PAOHIR -22 -19 -22 -19
PAOHLR -22 -19 -21 -18
PAOHER -22 -19 -19 -16
PAOULR -22 -19 -10.5 -7.5
Table 66 LOS threshold of OCH entity
To configure OCM, perform the following steps:

1 Add fiber connection, for example:
add fiber-connection port-1/1.1/4,port-1/1.3/1 fiber-
connection-type one-way
2 Set grid mode of the Amplifier connected with monitored card, for example:
set oms-1/1.1/1 grid-mode fixed_50G_96ch
3 Enable OCM port:
set ocm-port ocm-port-enable enabled
5.3.6 OLS fiber connections

To support provision connections via Net Managers, Groove G30 starts to support fiber
connection provisions for all physical links from FP4.0.
Wiring diagrams of fiber connections can clearly state which fiber is connected with
which port of which module. For G30, the fiber connections are complicated due to
amount number of ports under different modules are supported. Figure 94 provides an
overview of fiber connections for OFP2 amplifier ports supported by G30.
Figure 94 Overview of fiber connections for pluggable modules

When provisioning fiber connections, the basic order should be:

• From degree to add/drop (from DWDM line side to transponder line side)
• From degree to degree (from express to express)
Fiber connections in Table 67 are supported by Groove G30.
Source Source Port Destina- Destina- Connec- Comments

module tion module tion Port tion Type
BAUOFP2 DWDM PAUL- DWDM One-way For laser
ROFP2 safety
BAHOFP2 DWDM PAI- DWDM One-way
ROFP2/PAL
ROFP2/PA
EROFP2/O
SC
PAULROFP2 DCM TDCM TDC Two-way For auto
TDC
PAOSCOFP2 ocm-line in OCMOFP2 OCM One-way -
,PABAOFP2, ocm-line out
PAIROFP2,
PALROFP2,
PAEROFP2,
PAULROFP2
OPSOFP2 Facility PAI- DWDM Line Two-way For fast OTS
ROFP2/PAL protection
ROFP2/PA
EROFP2
OMD48, Add/drop CHM1, Port 1, or 2 Two-way Wavelength
OMD96, subport CHM2, will need to
OMD8 CHM1LH, be checked
OMD64 Add/drop CHM2LH, and evalu-
CHM1G, ated
port
CHM2T
CAD8, Add/drop CHM1, Port 1, or 2 Two-way -
CAD8E subport CHM2,
CHM1LH,
CHM2LH,
CHM1G,
CHM2T
OMD48, Subport XTM2 SFP+ ports Two-way Wavelength
OMD96, will need to
OMD8 be checked
and evalu-
OMD64 Add/drop
ated
port
CAD8, Subport XTM2 SFP+ ports Two-way -
CAD8E
Table 67 Fiber connections supported by G30


PAIROFP2, DWDM OMD48, DWDM Two-way -
PALROFP2, OMD96,
OMD8,
PAEROFP2, CAD8,
PABAOFP2, OMD64
PAOSCOFP2
OMD48, DWDM BAHOFP2 DWDM One-way -
OMD96,
OMD8,
CAD8,
OMD64
OMD48 DWDM BAUOFP2 DWDM One-way -
PAIROFP2, DWDM OMD48, DWDM One-way -
PALROFP2, OMD96,
OMD8,
PAEROFP2,
CAD8,
PAOSCOFP2 OMD64
PAOSCOFP2 DWDM PABAOFP2 DWDM Line Two-way -
PAUOFP2 DWDM OMD48 DWDM One-way -
PAUOFP2 DWDM OMD48 DWDM One-way
OMD8 Express OMD8 DWDM Two-way For cascad-
ing
OMD8 Express OMD8 Express Two-way Pass
through
OMD8 Add/drop OMD8 Add/drop Two-way Pass
through,
same type of
OMD8
CAD8E Express CAD8 DWDM Two-way For cascad-
ing
through
through
through


PAIROFP2, DWDM OPSOFP2 Working or Two-way OMS protec-
PALROFP2, Protection tion
PAEROFP2,
PABAOFP2,
PAOSCOFP2
PAIROFP2, DWDM OPSOFP2 Working or One-way OMS protec-
PALROFP2, Protection tion
PAEROFP2,
PAOSCOFP2
PAI- DCM out PAI- DCM in One-way DCM con-
ROFP2/PAL- ROFP2/PAL nection,
ROFP2/PAE ROFP2/PA in/out port
ROFP2/PAO EROFP2/P shall be on
ULROFP2 AOUL- same PA
ROFP2 module
PAI- DWDM PAI- DWDM Two-way For ILA
ROFP2/PAL- ROFP2/PAL
ROFP2/PAE ROFP2/PA
ROFP2 EROFP2
OPSOFP2 Working or BAHOFP2 DWDM One-way OMS protec-
Protection tion
OPSOFP2, Facility CHM1, DWDM line Two-way OCH protec-
OPSPTOFP2 CHM2, port tion
CHM1LH,
CHM2LH,
CHM1G,
XTM2
OMD48, Subport OPSOFP2 Working or Two-way OCH protec-
OMD96, Protection tion
OMD8
OMD64 Add/drop
port
CAD8 Subport OPSP- Working or Two-way OCH protec-
TOFP2 Protection tion
g • If there is fiber associated with the card/subcard, deleting the card/subcard will be
denied.
• Connecting one transponder DWDM port with a colored port, e.g., fixed OMD port
will be denied unless its frequency is set as the corresponding value or not provi-
sioned.

• Provisioning frequency of a transponder tunable DWDM port will be denied if the

port frequency is provisioned, but does not match its connecting colored
Mux/Demux port frequency.
If the user needs to get the corresponding relations between ports and port names, the
user can use the following command or similar command to retrieve such information,
for example to retrieve information about port-1/1.*/*:
show port-1/1.*/* tx-optical-power rx-optical-power port-name
The following information will be retrieved after this command performed:
Figure 95 Show-port result
5.3.7 Full OLS Scenarios Provision

Here in this chapter gives an OLS provision example for all the OLS applications, includ-
ing OMD, OPS, multi-span, OTDR, TDCM, OCM, and so on. Two scenarios are put
here, one is with PA and BA amplifiers at the same time with client protection; another
one is only with only BA at the same time with OCH protection.
• OLS with PA and BA amplifiers at the same time with client protection
Figure 96 OLS with PA and BA amplifiers at the same time with client protection

• OLS with only BA at the same time with OCH protection
Figure 97 OLS with only BA at the same time with OCH protection
The provision steps for whole OLS scenarios is as in the following:

1 To provision OPS:
set ops-1/3.2/1 revertive
Value completion:
no* yes
set ops-1/3.2/1 revertive yes wait-to-restore 300
Value completion:
Number (range 0..3600, second)
2 To add and provision on amplifiers:
set amplifier-1/3.1/pa amplifier-enable enabled
set amplifier-1/3.1/pa control-mode manual
set amplifier-1/3.1/pa gain-adjustment ?
Value completion:
Number (range -12.0..12.0, dB)
[ ne ]
administrator@NE132> set amplifier-1/3.1/pa gain-adjustment 8
g Fix-target gain or set target gain, follow the range between gain-range-min (dB) and
gain-range-max (dB).
3 To provision OCM:
a To check on which port OCM has been provisioned on:
show ocm-port
ocm-port ocm-port-enable grid-mode optical-
power-offset (dB)

---------------- --------------- -------------- -------

------------------
ocm-port-1/3.3/1 enabled fixed_50G_96ch 0.0
ocm-port-1/3.3/2 enabled fixed_50G_96ch 0.0
ocm-port-1/3.3/3 disabled fixed_50G_96ch 0.0
ocm-port-1/3.3/4 enabled not-applicable 0.0
b To check the monitored-center-frequency of monitored channels:
show monitored-channels
monitored-channels monitored-center-
frequency (MHz) monitored-optical-power (dBm)
------------------------------------ --------------------
------------ -----------------------------
monitored-channels-1/3.3/1/193350000 193350624
-18.7
-18.7
-18.2
-18.7
-26.3
-26.2
-26.2
-27.2
c To check the detailed information of the nominated och channel, e.g., 193350:
show och-1/3.1/1/193350
och-1/3.1/1/193350
admin-status down
oper-status down
avail-status ''
alias-name 'och-1/3.1/1/193350'
supporting-rx-port port-1/3.1/1
supporting-tx-port port-1/3.1/1
parent-entity oms-1/3.1/1
och-frequency 193350000 MHz
och-wavelength 1550.517 nm
rx-optical-power -19.1 dBm

tx-optical-power -8.8 dBm

[ ne ]
4 To provision TDCM:
add fiber-connection port-1/3.1/3,port-1/3.2/1 fiber-
connection-type two-way
g If the TDCM function is not used for PAxR and PAOULR, the physical connection
between two DCM ports should be connected together.
5 TO provision OTDR:
administrator@NE119> upload otdr port-1/3.1/3 destination=?
Value completion:
destination= Destination of the upload
([sftp|scp]://user@hostname/directorypath/filename)
administrator@NE119> set port-1/3.3/2 external-connectivity
yes
5.4 Operation, Administration, Management and Provisioning

(OAMP)
5.4.1 Session management

To manage connected NE, the Groove™ G30 will create sessions through North Bound
Interfaces. The G30 supports up to 100 sessions simultaneously. The following session
information can be retrieved:
• session creation time
• source IP/port/type
• destination IP/port
• login user
Below are session operations currently supported:
• To specify the number of rows to be used for display before pausing the output. After
pausing, pressing <space bar> will resume display (default value is 40). For
example:
set system security session-10.130.19.172:60054 cli-config
cli-lines 30
• To specify the number of columns to be used for display (default value is 80). For
example:
cli-columns 70
• To specify the number of command history buffer entries stored for the current
session (default value is 500). For example:
max-history-size 300

• To specify if the CLI shall issue interactive prompt, e.g., for prompting additional
information, or for confirmation of user initiated actions (default is Enabled). For
example:
interactive-mode enabled
show command can also be used to show attribute of one session, for example:
show system security session-10.130.19.172:60054 cli-config cli-
lines
5.4.1.1 CLI session lock/unlock

G30 allows the user to lock/unlock CLI sessions to prevent others from modifying provi-
sions on this NE. The following commands are supported to lock/unlock opened CLI
sessions.
lock
unlock
5.4.2 User management

Table 68 outlines the G30 user groups and their access permissions.
User group Default user Default Access permissions

account Password
crypto-officer cryptoadmin- se&gr#i4Usl! The highest level of access privilege.
istrator Crypto-officer can do all of the oper-
ations related with MOs’ managing
that an administrator can do plus
configurations related with ODU
encryption. However, crypto-officer
users cannot manage non-crypto-
officer users.
administration administrator e2e!Net4u# The administrative users can
perform all management operation
backup-
including security.
admin
The level of default user ‘administra-
tor’ cannot be changed.
configuration - - Configuration level users can
support all management operations
except for security related manage-
ment operations.
supervision - - Supervision level users can only do
monitoring operation without the
access to all configuration change
operations.
Table 68 G30 user groups

User group Default user Default Access permissions

account Password
operation - - Operation level users' privilege is
between configuration and supervi-
sion level users’.
Table 68 G30 user groups (Cont.)
g • Each group level users can change password of itself and the password will work
during next login.
• All level users’ password can be set by administration level users.
The Groove™ G30 supports creating users via CLI (Command Line Interface), the fol-
lowing operations are also supported on CLI.
• To create a new user
add user-<user name> user-class <user class>
g Requests of setting user names are listed in the following:

• Allowed characters in the beginning: ‘a-z’, ‘_’
• Allowed characters for the second character: ‘a-z’,’0-9’, ‘_’,’\’,’-’:
• Allowed characters in the end: ‘a-z’,’0-9’, ‘_’,’\’,’-’,’$’

• No more than 20 characters
• Set password
Use password command to set or change password, including current users to
change password for themselves and administration level users to reset password
for other users.
g Requests of setting password are listed in the following:

• Password length must be 8 characters minimum, 32 characters maximum.
• The following character types must be present:
• numeric character
• lowercase alphabetical character
• uppercase alphabetical character
• special character - Special character consists of any of the following:
~!@#$%^&*_-+=`|\(){}[]:;<>,.?’/”
g If the password string includes #;|? '", the password needs to be quoted in double or
single quotation marks.
For example, if the user wants to set password as e2e#4U, the user can set the
password as ‘e2e#4U’ or “e2e#4U”:
add user-groove_g30 password ’e2e#4U’
or
add user-groove_g30 password ”e2e#4U”
For ' and “, an alternative to enclose with quotes is to escape the characters with \
(for example, abc\'def).

• Set maximum invalid login times - The maximum number of consecutive and invalid
login attempts before an account is suspended (locked out)
• Set max suspension-time - This attribute is the duration of UID suspension following
consecutive invalid login attempts. Setting the value to 0 will disable this attribute.
• Set user administrative status - The attribute allows the user to modify the user’
administration status.
• Set timeout - This attribute is the Session Timeout Interval. If there are no messages
between the user and the NE over the Timeout interval, the session is logged off.
Setting the value to 0 disables this attribute (meaning the session will not timeout).
• Set maximum sessions - This attribute specifies the maximum number of sessions
allowed for this user.
g Currently Groove™ G30 can support single command for adding user/setting password
and changing password besides using two separate commands to provision them. For
example:
Adding user/setting password for the user itself:
• Interactive mode:
add user-groove_g30 password !Coriant01
g When interactive mode is disabled, adding the user and setting password with inter-
active mode commands does not work, there will have operation-failed warning dis-
played.
• None-interactive mode:
add -f user-jack01 password !Coriant01
[ ne ]
Changing password for a given user itself:
password old-password=!Coriant01 new-password=!Coriant02
Please confirm the new password:
[ ne ]
played.
password -f old-password=!Coriant01 new-password=!Coriant02
[ ne ]
Changing password for others by a given user:
password user-name=jack01 password=!Coriant03
[ ne ]
played.

password -f user-name=jack01 password=!Coriant03
[ ne ]
In the following is an example of settings for the user:

add user-coriant1 user-class administration
#add the user with user name of coriant1 and user-class of
administration
set user-coriant1 max-invalid-login 3

#specifies the invalid login attempts before locking user for
Coriant1
set user-coriant1 suspension-time 20

#specifies the suspension time of a locked account due to invalid
login attempt
set user-coriant1 timeout 20

#specifies the interval of time for the user session to end
automatically
set user-coriant1 max-sessions 5

#specifies the maximum number of sessions that can be run at same
time by this user
set user-coriant1 password-aging-interval 1

#set the user’s password aging interval as 1 day
password
Please provide the old password:
Please provide the new password:
#used for current users to change password for themselves
password user-name=coriant1
#reset password for user coriant1 ; reset-password can only be
used by administration level users to change password for other
users
password user-name=coriant01 new-password=Coriant1!

#change password inline for user coriant1 without confirmation
g The maximum number of users that can be created is 50, the maximum number of
sessions that can be created is 100.
Detailed commands for each operation please refer to CLI User Manual.
5.4.2.1 TACACS+
Terminal Access Controller Access-Control System Plus (TACACS+) is a protocol
developed by Cisco and released as an open standard beginning in 1993. Although
derived from TACACS (A family of related protocols handling remote authentication and
related services for network access control through a centralized server), TACACS+ is
a separate protocol that handles authentication, authorization, and accounting (AAA)
services between server and login user. The default AAA server roles are authentication
and authorization.
The Groove™ G30 supports remote user management through TACACS+ server for
Centralized User Management purpose. Refer to Figure 98 for the TACACS+ diagram
between the Groove™ G30 and TACACS+ server.
Figure 98 TACACS+ diagram between the Groove™ G30 and TACACS+ server
The supported TACACS+ functions by Groove™ G30 are listed in the following:
• The Groove™ G30 are able to support at least 3 TACACS+ servers (currently 4 at
most), each TACACS+ server can be provisioned independently to support the role
of authentication, authorization, accounting or multiple of them.
• TACACS+ server can be provisioned with priority numbers (1-10), the Groove™
G30 will use 4 servers for AAA according to priorities, from high priority (smaller
number) to low priority (larger number).
• The connection between TACACS+ servers uses the encryption mechanism of
secrete key, it is referring to a shared secret value that is known to both the client
provisioned on the server, the server cannot be used for AAA.
g If connection to the higher priority TACACS+ server is failure due to shared secret
mismatch, G30 will try the next TACACS+ server.
• All messages for Authentication, Authorization and Accounting (AAA) are encrypted
per TACACS+ standard definition.
• The Groove™ G30 supports configurable timeout for an AAA server, which is the
interval that the client waiting for the TACACS+ server to reply.

• The Groove™ G30 supports configurable retry times for an AAA server, which indi-
cates how many attempted accesses the client is trying to log into the TACACS+
server before failed.
• The TACACS+ function of the Groove™ G30 also supports the user to change
password after Authentication.
The requirement of AAA for access permission of remote users on each port are listed
in the following.
Port AAA Requiring for remote

users
CLI(4183/22) Yes
NETCONF(830)/REST- Yes
CONF(8181/8080)
Console port Support administration level
local users only
Table 69 AAA Requirement for remote users
TACACS+ Session
The Groove™ G30 is able to support up to 100 TACACS+ sessions.
The privilege levels of AAA server on the customer side corresponds with the user
classes defined by the Groove™ G30, the corresponding relations between privilege
levels of AAA server and user classes of the Groove™ G30 are listed in the following
table.
Privilege level User class

15-12 Administration
11-8 Configuration
7-4 Operation
3-0 Supervision
Table 70 Corresponding relations between AAA server privilege levels and user
classes
Authentication
Following Authentication Methods are supported by the Groove™ G30:
• Local-only
All login request will be authenticated locally.
• Remote-unavailable-then-local
• Remote AAA server authentication will be tried firstly with defined priorities, if all
remote AAA servers fail to respond (no AAA server provisioned/enabled or all
AAA servers are unreachable), then authenticate it locally.
• If any user failed the remote authentication, it shall be rejected even the user has
been defined as a local user.

• Remote-first-then-local
Remote AAA server authentication will be tried firstly with defined priorities, if all
remote AAA servers do not accept the authentication including either failing to
respond or returning a reject response, then do authentication locally.
• Local-first-then-remote
Local authentication will be tried firstly, if local authentication is not accepted
because either the local user does not exist or the authentication is rejected, then
try authentication remotely.
During the Authentication AAA server will reply below messages which has relative indi-
cation:
• SUCCSS: Login Successfully
• AUTH_ERR: Login Failed
• AUTH_INFO_UNAVALABLE: AAA Server Unavailable
g • When changing system-fips to ’enabled’, aaa-authentication-method must be ‘local-

only’.
• On failed TACACS authentications, G30 currently can not generate relative Syslog
events. Will be improved in future releases.
Authorization
Authorization function will authorize relative services to the user. For the Groove™ G30,
remote authorization is only used for remotely authenticated user. It's not supported for
the user to be authenticated locally and authorized remotely.
The default Attributes Values and Supported Private Attributes Values for Remote Users
are listed in the following table.
Attribute Name Server Attribute Value- AV-Pair Value or Range

Pair Name
user-class Privilege-level 0-15
user-class 4 user classes, refer to
chapter 5.4.2 User man-
agement.
timeout timeout If not received within range
(0...300), server assign the
default value, default value
is 0.
max-sessions max-sessions If not received within
range(1-20), server assign
default value, default value
is 20.
Table 71 Attributes Values and Supported Private Attributes Values for Remote
Users
Accounting
The Groove™ G30 can support to account the start and stop time of remote user's login
session.

The following gives an example about how to provision TACACS+:

1. Add AAA server ‘SH_COE_AAA’ with IP address of ‘172.29.21.130’ and server-
priority ‘7’:
add aaa-server-SH_COE_AAA server-IP 172.29.21.130 server-
priority 7
g A TACCAS + server shall be provisioned with priority number, the system will use
the servers for AAA according to the priority from high priority (smaller number) to
low priority (larger number).
2. Set AAA server ‘SH_COE_AAA’ with 5 times’ retry and set the role to 'authentication
authorization accounting’:
set aaa-server-SH_COE_AAA retry 5 role-supported
'authentication authorization accounting’
3. Set AAA server port as ‘65535’:
set aaa-server-SH_COE_AAA server-port 65535
4. Set system security of ‘SH_COE_AAA’ to shared-secret and password with
‘e2eNete2eNet’:
set system security aaa-server-SH_COE_AAA shared-secret
e2eNete2eNet
5.4.3 Database Operation

Groove™ G30 supports two database operations: database backup and database
restore. Currently each software load of G30 supports 2 databases individually whose
versions are same with corresponding software load, displayed as in the following:
Figure 99 G30 Node Information
5.4.3.1 Database Backup

To protect against data loss, the Groove™ G30 provides database backup. This action
can be taken through all North Bound Interfaces.
The memory is automatically updated after data-affecting commands have been pro-
cessed. Copies of the NE software and NE database are stored in the SD card.
CLI commands allow files to be transferred from the system to an external backup
memory device. The system supports remote database backup and is capable of initiat-
ing memory backup to an external local backup memory device.

Backup activities, including the transfer of a file, do not interrupt or interfere with traffic
carried by the Groove™ G30. The system database can be backed up as a file and
restored using external means (download or upload).
To upload the database:
upload database sftp://username@<sftp IP address>/<filename>.zip
5.4.3.2 Database Restore

The Groove™ G30 supports restoring a database from a remote location. This action
can be taken using the management systems or with CLI commands. Backed up files
are transferred from an external backup memory source and restored on the operating
server. SFTP is used to transfer the database backup file to the shelf.
To download a database:
download database sftp://username@<sftp IP
address>/<filename>.zip
g Each software load of Groove™ G30 supports two latest versions of database, which
can be switched between each other according to customer’s need.
Groove™ G30 also supports switching SD card from one failed shelf to a new shelf, in
order to restore the configuration of the failed shelf to the new one. For detailed steps of
how to replace the SD card please refer to 7.2.7 Removing and replacing a failed SD
card.
To activate the database using the following command:

activate database
5.4.4 Software upgrade

The Groove™ G30 supports in-service upgrades.This action can be taken using CLI
commands or Web GUI. Detailed software upgrade procedures please refer to
Released Upgrade Procedure manual.
5.4.5 Provision rollback

Provision rollback function is supported by system to rollback commands to a predefined
point. A new attribute ‘rollback-point’ is supported here to define the rollback point. Two
rollback types are supported by system currently, normal rollback-point and backup
rollback-point.
Difference between normal rollback and backup rollback is listed in the following:
Normal rollback- Backup rollback-

point point
rollback-point type 'normal' 'backup'
attribute
Table 72 Difference between normal rollback and backup rollback

Normal rollback- Backup rollback-

point point
Max number of up to 10 1
instances
ID values 1 to 10 always 0
Automatic deletion yes no
after rollback
Manual deletion by yes yes
user
Creation parameters no parameters parameter backup =
true
Creation via CLI create-rollback-point create-rollback-point
[<description>] -b [<description>]
Table 72 Difference between normal rollback and backup rollback
The following gives an example of operation of both normal and backup rollback:
set ne-name 1
create-rollback-point -1
set ne-name 2
create-rollback-point -b
set ne-name 3
create-rollback-point -2
Here if the user rollback system’s provision to rollback-point 1, the current provision is
NE name equals to 1. At this time the user still can rollback provision to rollback-point-
b when the NE has been provisioned as ‘2’ even though the system has been rolled back
to previous rollback point, but the user cannot rollback provision to rollback-point-2
which is created later than rollback point-b.
Here rollback-point-b is a safeguard to make sure all provisions before the rollback-
point-b has been saved.
Perform the rollback with the following command:
rollback rollback-point-x
5.4.6 Certification Management

Groove™ G30 supports certification management for HTTPS protocol to encrypt data
to avoid sensitive information being acquired by third parties. The following introduces
three options of certificate update for Groove™ G30.
• Download and install certificate
Download PEM (Privacy Enhanced Mail) file from CA/Linux server via Groove CLI:
download [-h] <filetype> <source> [<destination-filename>] [–certpass <certificate-
password>]

• Upload and install certificate

Upload PEM (Privacy Enhanced Mail) file via stand-alone URL, for example:
upload [-h] <filetype> <destination> [<destination-filename>] [–certpass <certificate-
password>]
• Generate and install self-signed certificate on G30
cert-gen [-h] <days> <organization> <common-name>
For example: cert-gen days=365 common-name=coriant
g Only ‘Administration’ and ‘crypto-officer’ class users support the certificate genera-
tion and download.
Example of how to generate, download and install self-signed certificate:
1 Generate certificate and private key on server and convert them into one pem file.
1 Generate private key and certificate.
openssl req -new -newkey rsa:2048 -keyout server.key -out
server.csr -nodes
openssl x509 -req -days 7305 -in server.csr -signkey
server.key -out server.crt
2 Combine them to one pem file.
openssl pkcs12 -export -in server.crt -inkey server.key -
out all-certs.p12 -nodes -clcerts -passout pass
openssl pkcs12 -in all-certs.p12 -out final.pem -passin
pass: -nodes
g If the user wants private key encrypted in pem file, just use -passout ‘1234’
instead of nodes in openssl pkcs12 commands, and input this certificate
password when doing CLI certificate downloading as in the following:
openssl pkcs12 -in all-certs.p12 -out final.pem -passin
pass: -passout:1234
2 Download and install on Groove.

download httpscert
sftp://[email protected]:/home/lwang4/final.pem.
g Input the certificate password if using passout for pem file and just press ENTER if
there is no password. Wrong password would cause failed download.
Example of how to generate, download and install CA-signed certificate:

1 Generate CA-signed certificate and private key on server and convert them into one
pem file.
1 Generate CA certificate and private key.
openssl genrsa -out ca.key 2048
openssl req -new -x509 -days 7305 -key ca.key -out ca.crt -
config /usr/lib/ssl/openssl.cnf
2 Generate server certificate request and private key.
openssl genrsa -out server.key 2048
openssl req -new -days 7305 -key server.key -out server.csr
-config /usr/lib/ssl/openssl.cnf

3 Use CA key to signed server certificate.

openssl ca -days 7305 -in server.csr -out server.crt -cert
ca.crt -keyfile ca.key -config /usr/lib/ssl/openssl.cnf
4 Combine server and CA certificate to one file (optional).
cat server.crt ca.crt > all-certs.crt
5 Generate pem file.
openssl pkcs12 -export -in server.crt (or all-certs.crt) -
inkey server.key -
out all-certs.p12 -nodes
openssl pkcs12 -in all-certs.p12 -out final-ca.pem –nodes
2 Download and install on Groove.
download httpscert
sftp://[email protected]:/home/lwang4/final-ca.pem
5.4.7 Management Interface

The Groove™ G30 supports following managed interfaces:
• Command Line Interface (CLI)
• Web gUI
• NETCONF
• RESTCONF
• SNMP (SNMP Trap and SNNP Get)
The Groove™ G30 supports management access through the following ports for various
management protocols, for details please refer to 5.1.6 TCP/IP port information. The
access of all interfaces support the same user accounts. Refer to Section 5.74.2 for
default users.
The system supports management access using NETCONF defined in RFC 6241
standard and RESTCONF defined in IETF RESTCONF standard based on the Yang
data model. It provides the same function parity as CLI interface.
Both CLI and NETCONF/RESTFCONF access are supported with SSH2 as transport
layer security protocol. How to use RESTCONF please refer to Groove G30
RESTCONF Support manual.
g If the user uses independent client based on NETCONF protocol, when there is update
for Yang files, the user need to update the Yang files onto the Independent Client.
Here take Independent Client MG-SOFT NetConf Browser Professional Edition for
example to show how to update Yang files onto independent client.
1 Open the Independent Client MG-SOFT NetConf Browser Professional Edition.
2 Select Tools -> Get Schema.

Figure 100 Tools on MG-Soft
3 The Get Schema window pops up, select Download all and click on the Download
button.
Figure 101 Get Schema window
4 Open Module menu, click Unload All Modules to unload previous modules firstly.

Figure 102 Module window
5 Check the date of Yang files to make sure they are the latest files. Click Load
Module button, after Load Module window displays select all yang module files and
click Open, all yang files are downloaded onto the MG-SOFT.
Figure 103 Load Module window
For other type of Independent Clients, the procedures are similar but not exactly the
same.
5.4.7.1 SNMP
SNMP is supported to provide a mediation layer to support SNMP-based network man-
agement. This allows SNMP-based management systems to manage telecommunica-
tion equipment via an SNMP communication link.

The SNMP mediation layer converts SNMP requests into corresponding commands that
are forwarded to the NE. Responses from the NE are converted to SNMP format and
sent to the SNMP Manager. Alarms and events set on NEs are converted to SNMP noti-
fications and sent to the Northbound Interface.
G30 supports SNMP protocol versions v2c and v3.
SNMP trap
Adding, setting and deleting one SNMP trap target is supported. The corresponding
operation commands are listed in the following:
SNMP trap via SNMPv2c
The user needs to provision the following commands then starts to use NetManager
System using SNMP trap:
For example, to add one SNMP trap by naming the SNMP trap target name as “SNMP-
1” and IP address as 172.29.23.110:
add snmp-target-SNMP-1 target-ip 172.29.23.110
g It’s mandatory to set both name and IP address for SNMP trap else the SNMP trap
cannot be set correctly.
To show the existed SNMP trap SNMP-1:

show snmp-target-SNMP-1
The result is as in the following:
snmp-target-SNMP-1
target-ip '172.29.23.110'
target-port 162
target-transport udp
trap-community-string 'groove'
g The default target port is 162, which can be modified according to the user’s arrange-
ment.
To modify the target-ip of this SNMP trap:

set snmp-target-SNMP-1 target-ip 172.29.23.109
Check if the target-ip has been modified:
show snmp-target-SNMP-1
It should be displayed as in the following:
snmp-target-SNMP-1
target-ip '172.29.23.109'
target-port 162
target-transport udp
trap-community-string 'groove'

It’s the same for modifying other parameters of SNMP trap.Trap-community-string can
also be modified as the customer need.
To delete the SNMP trap created:
delete snmp-target-SNMP-1
When executing this command, the system will double-confirm with the user whether the
user is sure to delete this SNMP trap, click ‘y’ to delete and ‘n’ to cancel.
SNMP trap via SNMPv3
The user must provision the following commands then starts to use NetManager System
using SNMP v3 protocol, including adding SNMPv3 user, seting user level, authentica-
tion protocol, authentication passphrase, privacy protocol, privacy passphrase, then
adding SNMP target. Refer to Table 73 to provision attributes for SNMPv3.
The following gives an example to provision SNMPv3 information. To add one SNMPv3
user of ‘groove’ with the following user settings and add SNMP target by naming the
SNMP target name as “groove” and IP address as 172.29.23.110 at the same time asso-
ciate SNMP target with SNMPv3 user:
add user-groove password e2e!Net4u

add snmpv3-groove user-sec-level auth-priv auth-protocol SHA
auth-passphrase l1234567 priv-protocol AES priv-passphrase
l1234567
add snmp-target-groove snmp-version v3 snmpv3-user snmpv3-groove
target-ip 172.29.23.11
In the following lists configurable parameters for SNMP trap via SNMPv3.
Configu- Description Value Value

rable Description
Parameters
user-sec- Specifies the auth-priv -
level SNMPv3 user auth-no-priv
security level
no-auth-no-
priv
auth- Specifies the MD5 Default value. When system-fips
protocol authentication is set to “enabled”, the snmpv3-
protocol that the auth-protocol cannot be set as
SNMPv3 user MD5.
uses. SHA -
auth-pass- Specifies authenti- String with -
phrase cation pass length of 0 or
phrase of the length from 8 to
SNMPv3. 64.
Table 73 SNMPv3 configurations


rable Description
Parameters
priv-protocol Specifies the DES3 When system-fips is set to
privacy protocol “enabled”, the snmpv3-priv-
that the SNMPv3 protocol cannot be set as DES3.
user uses.
AES Default value.
If priv-protocol is
changed, the priv-
passphrase needs
to be provided
again.
priv-pass- Specifies the pass String with A string that defines the sup-
phrase phrase of length of 0 or ported pluggable types on the
SNMPv3 privacy. length from 8 to port.
64.
g The VACM (View Access Control Mode) of SNMPv3 is determined by the system user’s
privilege level.
Only after above configurations are provisioned, the user can start to use the NetMan-
ager System using SNMP v3 protocol successfully.
SNMP trap formats
Formats of alarm Entities (in the alarm trap) have been simplified if NE SW upgraded to
FP1.1.2, FP2.0.1, FP2.1 and later releases. Additional zeros were representing unused
indexes; these were removed. Same thing for the keyword 'unused' in ODUs. The fol-
lowing table lists the Service MO Identifiers for previously and now:
MO Previous Releases FP1.1.2

Shelf shelf[shelfID] shelf[shelfID]
Fan, PSU, CHMx card[shelfID, slotID] card[shelfID, slotID]
pluggable pluggable[shelfID, pluggable[shelfID, slotID, portID]
slotID, 0, portID]
och-os, otu4, otuc2, entity[shelfID, slotID, 0, entity[shelfID, slotID, portID]
otuc3 portID] Entity=och-os, otu4, otuc2, otuc3
Entity=och-os, otu4,
otuc2, otuc3
Table 74 Service MO Identifiers


odu4 Line port: odu[shelfID, Line port: odu[shelfID, slotID,
slotID, 0, portID, 0, portID, oducn, oducnID, odu4,
oducn, oducnID, odu4, odu4ID], n=2 or 3
odu4ID, Client port or line OTU4 port:
unused,0,unused,0], odu[shelfID, slotID, portID, odu4,
n=2 or 3 odu4ID]
Client port or line OTU4
port: odu [shelfID,
slotID, 0, portID, 0,
odu4, odu4ID,
unused,0, unused,0,
unused,0]
oduc2 odu[shelfID, slotID, 0, odu[shelfID, slotID, portID, oduc2,
portID, 0, oduc2, oduc2ID]
oduc2ID,unused,0,unu
sed,0, unused,0]
oduc3 odu[shelfID, slotID, 0, odu[shelfID, slotID, portID, oduc3,
portID, 0, oduc3, oduc3ID]
oduc3ID,
unused,0,unused,0,
unused,0]
odu2, odu2e, oduflex Line port: odu[shelfID, slotID,
Line port: odu[shelfID, portID, oducn, oducnID, odu4,
slotID, 0, portID, 0, odu4ID, oduj, odujID], n=2, 3; j= 2,
oducn, oducnID, odu4, 2e, flex
odu4ID, oduj, odu- Line port: odu[shelfID, slotID,
jID,unused,0], n=2, 3; j= portID, odu4, odu4ID, oduj,
2, 2e, flex odujID], j= 2, 2e, flex
Line port: odu[shelfID, Client port: odu[shelfID, slotID,
slotID, 0, portID, 0, portID, subportID, oduj, odujID],
odu4, odu4ID, oduj, odujID=1; j= 2, 2e, flex
odujID,unused,0,
unused,0], j= 2, 2e, flex
Client port: odu[shelfID,
slotID, 0, portID, sub-
portID, unused,0, oduj,
odujID,
unused,0,unused,0],
odujID=1; j= 2, 2e, flex


odu3 Line port: odu[shelfID, Line port: odu[shelfID, slotID,
slotID, 0, portID, 0, portID, oducn, oducnID, odu4,
oducn, oducnID, odu4, odu4ID, odu3, odu3ID], n=2, 3
odu4ID, odu3, odu3ID, Client port: odu[shelfID, slotID,
unused,0], n=2, 3 portID, odu3, odu3ID], odujID=1
Client port: odu[shelfID,
slotID, 0, portID, 0,
odu3, odu3ID,
unused,0,unused,0,unu
sed,0], odujID=1
OTU2, OTU2e, OC192, Client port: entity[shel- Client port: entity[shelfID, slotID,
STM64, FC8G, FC16G, fID, slotID, 0, portID, portID, subportID]
ETH10G subportID] Entity=OTU2, OTU2e, OC192,
Entity=OTU2, OTU2e, STM64, FC8G, FC16G, ETH10G
OC192, STM64, FC8G,
FC16G, ETH10G
OTU4, ETH100G, Client port: entity[shel- Client port: entity[shelfID, slotID,
ETH40G fID, slotID, 0, portID] portID]
Entity=OTU4, Entity=OTU4, ETH100G,
ETH100G, ETH40G ETH40G
port port[shelfID, slotID, 0, port[shelfID, slotID, portID]
portID]
subport subport[shelfID, slotID, subport[shelfID, slotID, portID,
0, portID, subportID] subportID]
MO FP2.0, FP2.0.x FP2.1 FP2.1.1 Groove™ G30

releases
Shelf shelf-shelfID shelf-shelfID
Fan, PSU, CHMx card-shelfID/slotID card-shelfID/slotID
pluggable pluggable-shel- pluggable-shelfID/slotID/portID
fID/slotID/portID
och-os, otu4, otuc2, Entity-shel- Entity-shelfID/slotID/portID
otuc3 fID/slotID/portID Entity=och-os, otu4, otuc2, otuc3
Entity=och-os, otu4,
otuc2, otuc3


releases
odu4 Line port: Line port:
odu-shelfID/slotID/por- odu-shelfID/slotID/portID/oducn-
tID/oducn- oducnID/odu4-odu4ID; n=2 or 3
oducnID/odu4- Client port or line OTU4 port:
odu4ID/unused-
odu-shelfID/slotID/portID/odu4-
0/unused-0; n=2 or 3
odu4ID
Client port or line OTU4
port:
odu-shelfID/slotID/por-
tID/odu4-
odu4ID/unused-
0/unused-0/unused-0
oduc2 odu-shelfID/slotID/por- odu-shelfID/slotID/portID/oduc2-
tID/oduc2- oduc2ID
oduc2ID/unused-
0/unused-0/unused-0
oduc3 odu-shelfID/slotID/por- odu-shelfID/slotID/portID/oduc3-
tID/oduc3- oduc3ID
oduc3ID/unused-
0/unused-0/unused-0


releases
odu2, odu2e, oduflex Line port: Line port:
tID/oducn- oducnID/odu4-odu4ID/oduj-
oducnID/odu4- odujID; n=2, 3; j= 2, 2e, flex
odu4ID/oduj-odu- Line port:
jID/unused-0; n=2, 3; j=
2, 2e, flex
odu4ID/oduj-odujID; j= 2, 2e, flex
Line port:
Client port:
odu-shelfID/slotID/portID.subpor-
tID/odu4-odu4ID/oduj-
tID/oduj-odujID,
odujID/unused-
0/unused-0; j= 2, 2e, odu-shelfID/slotID/portID/oduj-
flex odujID; odujID=1; j= 2, 2e, flex
Client port:
tID.subportID/oduj-odu-
jID/unused-0/unused-
0/unused-0,
tID/oduj-odu-
jID/unused-0/unused-
0/unused-0; odujID=1;
j= 2, 2e, flex
odu3 Line port: Line port:
tID/oducn- oducnID/odu4-odu4ID/odu3-
oducnID/odu4- odu3ID; n=2, 3
odu4ID/odu3- Client port:
odu3ID/unused-0; n=2,
3
odu3ID; odu3ID=1
Client port:
tID/odu3-
odu3ID/unused-
0/unused-0/unused-0;
odu3ID=1


releases
OTU2, OTU2e, OC192, Client port: Client port:
STM64, FC8G, FC16G, Entity-shel- Entity-shelfID/slotID/portID
ETH10G fID/slotID/portID Entity-shelfID/slotID/portID.sub-
Entity-shel- portID
fID/slotID/portID.sub- Entity=otu2, otu2e, oc192, stm64,
portID fc8G, fc16G, eth10g
Entity=otu2, otu2e,
oc192, stm64, fc8G,
fc16G, eth10g
OTU4, ETH100G, Client port: Client port:
ETH40G Entity-shel- Entity-shelfID/slotID/portID
fID/slotID/portID Entity=otu4, eth100g, eth40g
Entity=otu4, eth100g,
eth40g
port port-shelfID/slotID/por- port-shelfID/slotID/portID
tID
subport subport-shel- subport-shelfID/slotID/portID.sub-
fID/slotID/portID.sub- portID
portID
SNMP get
SNMP get is an SNMP application that uses the SNMP GET request to query for infor-
mation on a network entity. One or more object identifiers (OIDs) may be given as argu-
ments on the command line. Each variable name is given in the format specified in
variables. G30 supports SNMP get via SNMPv3 and SNMPv2c.
SNMP get via SNMPv2c
using SNMP v2c protocol:
add snmp-community-xxx
For example, to add one SNMP community of ‘groove_g30’:
add snmp-community-groove_g30
In the following lists configurable parameters for SNMP get via SNMPv2c.


rable Description
Parameters
snmp-com- maximum 10 com- - -
munity munity strings in
the list.
community- A string with - -

string length from 1 to 32
bytes. Only the fol-
lowing characters
are allowed: 0-9 A-
Z, a-z, -_: /.
community- Parameter to read-only Read-only is corresponding to
string- specify access SNMP get.
access right of the com-
munity string.
Table 76 SNMPv2c configurations
g Only the users of level ‘Configuration’ have the data access right to SNMPv2.
SNMP get via SNMPv3

using SNMP v3 protocol, including adding SNMPv3 user, seting user level, authentica-
tion protocol, authentication passphrase, privacy protocol, privacy passphrase, then
adding anmp target. Refer to Table 77 to provision attributes for SNMPv3.
The following gives an example to provision SNMPv3 information. To add one SNMPv3
user of ‘groove’ with the following user settings and add SNMP target by naming the
SNMP target name as “groove” and IP address as 172.29.23.110 at the same time asso-
ciate SNMP target with SNMPv3 user:
add user-groove password e2eNet4u#

add snmpv3-groove user-sec-level auth-priv auth-protocol SHA
auth-passphrase l1234567 priv-protocol AES priv-passphrase
l1234567
In the following lists configurable parameters for SNMP get via SNMPv3.


rable Description
Parameters
user-sec- Specifies the auth-priv -
level SNMPv3 user auth-no-priv
security level
no-auth-no-
priv
auth- Specifies the MD5 Default value. When system-fips
protocol authentication is set to “enabled”, the snmpv3-
protocol that the auth-protocol cannot be set as
SNMPv3 user MD5.
uses.
SHA -
auth-pass- Specifies authenti- String with -
phrase cation pass length of 0 or
phrase of the length from 8 to
SNMPv3. 64.
priv-protocol Specifies the DES3 When system-fips is set to
privacy protocol “enabled”, the snmpv3-priv-
that the SNMPv3 protocol cannot be set as DES3.
user uses. AES Default value.
If priv-protocol is
changed, the priv-
passphrase needs
to be provided
again.
priv-pass- Specifies the pass String with A string that defines the sup-
phrase phrase of length of 0 or ported pluggable types on the
SNMPv3 privacy. length from 8 to port.
64.
g The VACM (View Access Control Mode) of SNMPv3 is determined by the system user’s
privilege level.
Only after above configurations are provisioned, the user can start to use the NetMan-
ager System using SNMP v3 protocol successfully.
MIB (Management Information Base) of G30
g Because YANG has a more rich structural language than MIB, so some of the attributes
turn to invalid during mapping from YANG to MIB. There are multiple reasons for this,
the most common is the 'when' expression being false. In this case, no value is returned
to this attribute. All the data types defined by Yang which does not exist in the SMI
(Structure of Management Information), the user needs to use octect string instead.

The user can get MIB information through 3rd-party tools. In the following gives an
example of the MIB tree structure.
Figure 104 G30 MIB Tree Information

The user can get the Node information by double-clicking the node, detailed information
will be displayed like in the following.

Figure 105 G30 Node Information

The current rules of YANG-name converting to SMI-name is as the following:
• If eum name starts with an illegal character, add "t_" in front of the name (some eum
have number prefix);
• Lower case string in front of first '_' or '-';
• First char of upper case behind of every '_';
• Remove '' (SMI is not allowed '' or '-' in name);
• Add YANG List\Container name as prefix of MIB entries and scalars;
• Add a MIB group to separate nodes of YANG container name as ${group name}.
So if a YANG eum name is "GROOVE_G30", when converted to MIB it will be
"grooveG30".
5.4.7.2 Syslog
Currently the Groove™ G30 supports forwarding logs to the log server according to both
facility level and severity level. Currently the following logs can be forwarded to the log
server in time:
• alarm log
• configuration log
• event log
• security log
g Add Read-only right for non-crypto-officer class users for encryption service and its
alarms.
System log consists of two parts, Header and Log message, the format of system log
Header is as in the following:
<PRI>version Timestamp hostname Appname PROCID meta sequenceId

• Timestamp: [YYYY]-[MM]-[DD]T[hh]:[mm]:[ss] ("+" / "-") TIME-HOUR ":" TIME-

MINUTE
• Hostname: “[ne-name]@[shelf IP]”*
• Syslog packets length 480~2048
• Appname: Alarm/Event/Configuration/Security
• meta sequenceId: meta sequency=“<id>”]
The format of Log Message is as in the following, which is based on the log type:
• Alarm: “time-stamp”: <value>; “alarm-duration” : <value>; “entity”: <value>; “alarm-
type”: <value>; “location”: <value>; “direction”: <value>; “time-period”: <value>;
“service-affect”: <value>; “severity”: <value>;”description”:<value>; [“inven-
tory”:<value>;];”alarm-id”:<value>;
• Event: "time-stamp":<value>;"session-id":<value>;"user-
name":<value>;"id":<value>;"type":<value>;"entity":<value>;[“attributes":”<value>;
”]
• Configuration: "time-stamp":<value>;"duration":<value>;"user-
name":<value>;"nbi":<value>;"session-
id":<value>;"id":<value>;"result":<value>;"error-mes-
sage":<value>;"type":<value>;"entity":<value>;["attributes":”<value>;”]
• Security: "time-stamp":<value>;"session-id":<value>;"session-type":<value>;"user-
name":<value>;"event/action":<value>
Here is an example of a security log:
<85>1 2017-10-12T07:59:27+01:00 [email protected] SECURITY 1651
[meta sequenceId="486"] "time-stamp":2017-10-12T07:59:27+01:00;"session-
id":10.13.13.18:15956;"session-type":cli;"user-name":administra-
tor;"event/action":logged in
The corresponding relations between the Groove™ G30 facilities and Protocol Codes
are listed in the following table.
Code Facility Groove™ G30 log type

0 kernel messages -
1 user-level messages -
2 system daemons -
... ... ...
10 security/authorization security log
messages
... ... ...
16 local use 0 (local0) alarm log
17 local use 1 (local1) event log
18 local use 2 (local2) configuration log
... ... ...
Table 78 Corresponding relations between the Groove™ G30 facilities and Protocol
Codes

Code Facility Groove™ G30 log type

23 local use 7 (local7) -
Table 78 Corresponding relations between the Groove™ G30 facilities and Protocol
Codes
The corresponding relations between the Groove™ G30 severity levels of system logs
and the Protocol Codes are listed in the following.
Cod Severity of Alarm log Configura- Event log Security log

e the log tion Log
0 Emergency: - - - -
system is
unusable
1 Alert: action - - - -
must be taken
immediately
2 Critical: Critical alarm - - -
critical condi-
tions
3 Error: error Major/Minor - - -
conditions alarm
4 Warning: Cleared - Not-alarmed -
warning con-
ditions
5 Notice: - - Others all
normal but
significant
condition
6 Informational: - all - -
informational
messages
7 Debug: - - - -
debug-level
messages
Table 79 Corresponding relations between Groove™ G30 severity level and system
logs
The following example shows how to add a log-server named 'public' and create alarm
and event facilities.

add log-server-public log-server-ip-address 172.21.23.24

#add log server with log server name of 'public' and log
server IP address of 172.21.23.24
add log-facility-public/alarm
#add alarm facility to log server 'public'
add log-facility-public/event
#add event facility to log server 'public'
After the log-server named 'public' has been created successfully, show logs according
to alarm facility on log server 'public':
show log-facility-public/alarm
The following information will be displayed as in the following:
log-facility-public/alarm
log-selector-severity debug
compare-op equals-or-higher
To show detailed information about log-server 'public':
show log-server-public
The following information will be displayed.
log-server-public
log-forwarding-selector-public
log-server-ip-address '172.21.23.24'
log-server-transport udp
log-server-port 514
destination-facility-type disabled
destination-facility '23'
To show the log-forwarding-selectors of log server 'public':
show log-forwarding-selector-public
The following information will be displayed.
log-forwarding-selector-public
log-facility-public/alarm
log-facility-public/event
The following table lists the attributes of log server that can be modified.

Attributes Description Syntax examples

log-server-transport Specifies the trans- set log-server-
port of the server tester log-
server-transport
tcp
log-server-port Specifies the port of set log-server-
the transport tester log-
server-port 1428
Table 80 Log server attributes
5.4.8 Performance management

G30 allows the gathering of the following data to determine overall network health.
• current performance statistics
• historical performance statistics
• thresholds
Currently, G30 can support a maximum statistics of 7x24h, 7x96x15min, 7x24x1h, and
60*1min.
To use the performance management function, set the performance monitoring to
‘enabled’.
Enable/disable the supervision function:
set performance pm-point-<entity-pm-type> supervision-switch
enabled
Enabling/disabling the thresholding function:

set performance pm-point-<entity-pm-type> thresholding-switch
enabled
Enable/disable the history recording function:

set performance pm-point-<entity-pm-type> history-recording
enabled
Use the following commands to show all performance data on the 100GBE-1/4/5:
show pm 100GBE-1/4/5
g The ‘show’ command can also be used with multiple filters.
For example, to show all the PM information of a specific OTU2C instance:

show pm otuc2-1/1/2 otu-nend-ingress 15min
To show all attributes of every near-end ingress 15m parameter on a specific ODU4 PM
instance:
show pm odu-1/1/1/oduc2-1/odu4-1 15min
To show the PM of a specific ODU4 PM instance based on a start date/time:
show pm odu-1/1/1/oduc2-1/odu4-1/ 15m 2016-06-27T00:15:00+01:00

To show all PM history:

show pm history
To show PM history data starting in one specific time stamp, for example:
show -s=2016-06-06T10:00:00+01:00 pm history
To show PM history data between two timestamps, for example:
show -s=2016-06-06T10:00:00+01:00 -e=2016-06-06T18:00:00+01:00
pm history
To show PM history data from one bin point to another, for example, from bin 1 to bin 5
for 15min PM in otuc2-1/1/1:
show -sbin=1 -ebin=5 pm history 15min otuc2-1/1/1
To show a specific amount of PM history data, for example, 5000 records of15min PM
on otuc2-1/1/1:
show -n=5000 pm history 15min otuc2-1/1/1
G30 supports performance related TCA (Threshold Crossing Alert) alarms which will be
triggered if the performance value exceeds the threshold. Table 81 Default value of Low
Threshold/High Threshold and Threshold Range of TCA alarms lists the default value of
Low Threshold/High Threshold of TCA alarms, and Threshold Range of TCA alarms.
Relationship between TCA alarms and PM parameter/PM statistics/logical enti-
ties/applicable modules please refer to Table 82 Supported Performance Monitoring list.

CONDI- PM Condition Descrip- Default Value Threshold Range

TION Parame- tion 1- 15- 1- 1- 1- 15- 1- 1-
TYPE ter minu minu hour day minu minu hour day
te te te te
T-BE-FEC BER-FEC Bit Error OCH-OS 82,412 1,236, 4,944, 118,67 1 to 1 to 1 to 1 to
Forward BE- ,936,4 194,04 776,18 4,628, 92233 92233 92233 92233
Error Cor- FEC(OTU4 24 6,360 5,440 450,56 72036 72036 72036 72036
rection - 15% FEC, 0 85477 85477 85477 85477
120.579 5807 5807 5807 5807
Gbps, port-
mode=QPS
K_100G)
OCH-OS 82,412 1,236, 4,944, 118,67

BE- ,936,4 194,04 776,18 4,628,
FEC(OTU4 24 6,360 5,440 450,56
- 25% FEC, 0
137.355Gb
ps, port-
mode=QPS
K_100G)
OCH-OS 164,82 2,472, 9,889, 237,34

BE- 5,872, 388,09 552,37 9,256,
FEC(OTUC 848 2,720 0,880 901,12
2 - 25% 0
FEC,
274.71Gbp
s, port-
mode=16Q
AM_200G)
OCH-OS 123,62 1,854, 7,417, 178,01

BE- 0,962, 314,44 257,76 4,186,
FEC(OTUC 824 2,360 9,440 466,56
3 - 25% 0
FEC,
412.07Gbp
s, port-
mode=8QA
M_300G)
OTU BE- 67085 10062 40251 96603

FEC (G709 9841 89762 59048 81716
OTU4) 1 4 30
OTU BE- 8321 12482 49930 11983

FEC(G709/I 7 8 386
4/I7
OTU2/OTU
2e) **
Ethernet 30375 45562 18225 43740

BE-FEC 0000 50000 00000 00000
0 00
Table 81 Default value of Low Threshold/High Threshold and Threshold Range of TCA alarms


TION Parame- tion 1- 15- 1- 1- 1- 15- 1- 1-
te te te te
T-BER- BER- Bit Error OCH-OS 2.0E- 2.0E- 2.0E- 2.0E- 2.0E- 2.0E- 2.0E- 2.0E-
FEC-HT FEC Rate BER- 02 02 02 02 02 02 02 02
before FEC
Forward OTU 2.0E- 2.0E- 2.0E- 2.0E- 0 to 0 to 0 to 0 to
Error BER- 02 02 02 02 5.0E- 5.0E- 5.0E- 5.0E-
Correc- FEC 2 2 2 2
tion -
High Ethernet 3.0E- 3.0E- 3.0E- 3.0E- 1.9E- 1.9E- 1.9E- 1.9E-
Thresh- BER- 5 5 5 5 2 to 2 to 2 to 2 to
old FEC 2.3E- 2.3E- 2.3E- 2.3E-
11 11 11 11
and 0 and 0 and 0 and 0
T-CD-LT CD Chromatic Disper- - - - - - - - -
sion - Low Threshold 4000 4000 4000 4000 280,0 280,0 280,0 280,0
0 0 0 0 00 to 00 to 00 to 00 to
+280, +280, +280, +280,
T-CD-HT Chromatic Disper- 4000 4000 4000 4000 000 000 000 000
sion - High Threshold ps/n ps/n ps/n ps/n
m m m m
T- DELAY Delay measurement 0 0 0 0 0 to 0 to 0 to 0 to
DELAYO - Optical Data Unit - 2147 2147 2147 2147
DU-HT High Threshold 4836 4836 4836 4836
47 us 47 us 47 us 47 us
T- Delay measurement NA NA NA NA
DELAYO - Optical Data Unit -
DU-LT Low Threshold
T- Q-factor Quality factor - Low 0.0 0.0 0.0 0.0 0 to 0 to 0 to 0 to

QFACTO Threshold 60.0 60.0 60.0 60.0
R-LT dB dB dB dB
T-DGD- DGD Differential Group 100 100 100 100 0 to 0 to 0 to 0 to

HT Delay - High Thresh- 100 100 100 100
old ps ps ps ps


TION Parame- tion 1- 15- 1- 1- 1- 15- 1- 1-
te te te te
T-EB- EB-OTU Error Errored 49 738 2952 7087 1 to 1 to 1 to 1 to
OTU Block Block - 0 6148 9223 9223 9223
Count - EB-ODU 9146 3720 3720 3720
Optical (OTU2) 9123 3685 3685 3685
Trans- 6517 4775 4775 4775
Errored 51 765 3060 7342
port Unit 20 807 807 807
Block - 8
EB-ODU
(OTU2e)
Errored 128 1927 7708 1849
Block - 80
EB-ODU
(OTU4)
Errored 388 5829 2331 5596
Block - 6 22
EB-ODU
(OTUC3)
Errored 259 3886 1554 3730
Block - 4 81
EB-ODU
(OTUC2)


TION Parame- tion 1- 15- 1- 1- 1- 15- 1- 1-
te te te te
T-EB- EB-ODU Error Errored 128 1927 7708 1849 1 to 1 to 1 to 1 to
ODU Block Block - 80 6148 9223 9223 9223
Count - EB 9146 3720 3720 3720
Optical (ODU4) 9123 3685 3685 3685
Data Unit 6517 4775 4775 4775
Errored 49 741 2964 7117
20 807 807 807
Block - 0
EB
(ODU3)
Errored 259 3886 1554 3730
Block - 4 81
EB
(ODUc2)
Errored 388 5829 2331 5596
Block - 6 22
EB
(ODUc3)
Errored 49 738 2952 7087
Block - 0
EB
(ODU2)
Errored 51 765 3060 7342
Block - 8
EB
(ODU2e)
T-ES- ES Errored Second - 2 25 100 250 1 to 1 to 1 to 1 to
ODU Optical Data Unit 60 900 3600 8640
0
T-ES- Errored Second -
OTU Optical Transport
Unit
T-ES-S Errored Second of
SONET Section
T-ES-RS Errored Second of
SDH Regenerator
Section
T-LOSS LOSS Loss of Signal 2 2 4 8 1 to 1 to 1 to 1 to
Seconds count 60 900 3600 8640
0


TION Parame- tion 1- 15- 1- 1- 1- 15- 1- 1-
te te te te
T-OPR- OPR Optical Power -18 -18 -18 -18 -45 -45 -45 -45
HT Received level - High dBm dBm dBm dBm dBm dBm dBm dBm
Threshold to 20 to 20 to 20 to 20
dBm dBm dBm dBm
T-OPR- Optical Power +10 +10 +10 +10

LT Received level - Low dBm dBm dBm dBm
Threshold
T-OPT- OPT Optical Power Trans- +3 +3 +3 +3 -45 -45 -45 -45

HT mitted level - High dBm dBm dBm dBm dBm dBm dBm dBm
Threshold to 20 to 20 to 20 to 20
dBm dBm dBm dBm
T-OPT- Optical Power Trans- -5 -5 -5 -5
LT mitted level - Low dBm dBm dBm dBm
Threshold
T-OFR- OFR Optical Frequency 4811 4811 4811 4811 - - - -
HT Received - High 250 250 250 250 4811 4811 4811 4811
Threshold 250 250 250 250
Hz to Hz to Hz to Hz to
T-OFR- Optical Frequency
4811 4811 4811 4811
LT Received - Low
250 250 250 250
Threshold
Hz Hz Hz Hz
√ √
T-OFT- OFT Optical Frequency 4811 4811 4811 4811 - - - -
HT Transmitted - High 250 250 250 250 4811 4811 4811 4811
Threshold 250 250 250 250
T-OFT- Optical Frequency Hz to Hz to Hz to Hz to
LT Transmitted - Low 4811 4811 4811 4811
Threshold 250 250 250 250
Hz Hz Hz Hz
T-OSNR- OSNR Optical Signal to 0.0 0.0 0.0 0.0 0 to 0 to 0 to 0 to

LT Noise Ratio - Low 60.0 60.0 60.0 60.0
Threshold dB dB dB dB
T-SES- SES- Severely Errored 2 4 16 40 1 to 1 to 1 to 1 to
ODU ODU Second - Optical 60 900 3600 8640
Data Unit 0
T-SES- SES- Severely Errored 2 4 16 40 1 to 1 to 1 to 1 to
OTU OUT Second - Optical 60 900 3600 8640
Transport Unit 0


TION Parame- tion 1- 15- 1- 1- 1- 15- 1- 1-
te te te te
T-UAS- UAS- Unavailable Second - 10 10 10 10 1 to 1 to 1 to 1 to
ODU ODU Optical Data Unit 60 900 3600 8640
0
T-UAS- UAS- Unavailable Second - 10 10 10 10 1 to 1 to 1 to 1 to

OTU OTU Optical Transport 60 900 3600 8640
Unit 0
T-UBE- UBE- Uncorrectable Block 58 875 3500 8400 1 to 1 to 1 to 1 to
FEC FEC Error Forward Error 0 2147 2147 2147 2147
Correction 4836 4836 4836 4836
47 47 47 47
T-SE SE Symbol SE 7 113 452 1080 1 to 1 to 1 to 1 to
Error (10GBE) 0 1844 1844 1844 1844
During 6744 6744 6744 6744
SE 30 452 1808 4320
Carrier 0737 0737 0737 0737
(40GBE) 0
0955 0955 0955 0955
SE 75 1130 4520 1080
1615 1615 1615 1615
(100GBE 0
)
T- DropE- Drop Events 1844 1844 1844 1844 1 to 1 to 1 to 1 to
DROPE- vents 6744 6744 6744 6744 1844 1844 1844 1844
VENTS 0737 0737 0737 0737 6744 6744 6744 6744
0955 0955 0955 0955 0737 0737 0737 0737
T- Octets Octets
1615 1615 1615 1615 0955 0955 0955 0955
OCTETS
1615 1615 1615 1615
T-PKT Pkts Packets
T- Broad- Broadcast Packets
BROAD- castPkts
CASTPK
TS
T-MULTI- Multicast- Multicast Packets
CASTPK Pkts
TS


TION Parame- tion 1- 15- 1- 1- 1- 15- 1- 1-
te te te te
T- CRCAlig CRC Alignment 1844 1844 1844 1844 1 to 1 to 1 to 1 to
CRCALI nErrors Errors 6744 6744 6744 6744 1844 1844 1844 1844
GNERR 0737 0737 0737 0737 6744 6744 6744 6744
ORS 0955 0955 0955 0955 0737 0737 0737 0737
1615 1615 1615 1615 0955 0955 0955 0955
T- Under- Undersize Packets
UNDER- sizePkts 1615 1615 1615 1615
SIZEPKT
S
T-OVER- Over- Oversize Packets
SIZEPKT sizePkts
S
T-FRAG- Frag- Fragments
MENTS ments
T- Jabbers Jabbers
JABBER
S
T- Pkts64O Packets with 64
PKTS64 ctets octets in length
OCTETS
T- Pkts65- Packetes with
PKTS65- to127Oc- between 65 and 127
TO127O tets octets in length inclu-
CTETS sive
PKTS128 to255Oc- between 128 and 255
CTETS sive
PKTS256 to511Oc- between 256 and 511
CTETS sive
PKTS512 to1023O between 512 and
TO1023 ctets 1023 octets in length
OCTETS inclusive
T- Pkts1024 Packetes with
PKTS102 to1518O between 1024 and
4TO1518 ctets 1518 octets in length
OCTETS inclusive


TION Parame- tion 1- 15- 1- 1- 1- 15- 1- 1-
te te te te
T-CV-S CV Coding Violation of 597 8960 3584 8601 1 to 1 to 1 to 1 to
SONET Section 0 60 4800 5760 2304 2147
00 0000 0000 4836
0 47
T-BBE- BBE Background Block 597 8960 3584 8601 1 to 1 to 1 to 1 to
RS Error of SDH Regen- 0 60 4800 5760 2304 2147
erator Section 00 0000 0000 4836
0 47
T-SES- SES Severely Errored 2 4 16 40 1 to 1 to 1 to 1 to
RS Seconds of SDH 60 900 3600 8640
Regenerator Section 0
T-SES-S Severely Errored
Seconds of SONET
Section
T-OFS OFS Out of Frame 1 2 2 8 1 to 1 to 1 to 1 to
Seconds of SDH 60 900 3600 8640
0
T-SEFS SEFS Severely Errored 1 2 2 8 1 to 1 to 1 to 1 to
Frame Second 60 900 3600 8640
0
LOSS- LOSS-Tx Loss of Signal 1 2 2 8 1 to 1 to 1 to 1 to
TXRX Seconds count - 60 900 3600 8640
Transmit 0
LOSS- LOSS-Rx Loss of Signal 1 2 2 8 1 to 1 to 1 to 1 to

TXRX Seconds count - 60 900 3600 8640
Receive 0
The supported Performance Monitoring list and corresponding statistic of G30 is listed
in the following:

PMP PM Statis- odu otu otu och eth fc8 oc1 stm shel car port sub om
Group Para tics line clie -os 10g/ g/fc 92 -64 f d/ port s/g
met nt 40g/ 16g sub opt/
er 100 car osc
g d
odu- EB errored Y1)
nend- blocks
egress ES errored- Y1)
seconds
SES severely Y1)
-
errored-
seconds
UAS unavail- Y1)
able-
seconds
odu- EB errored- Y2)
nend- blocks
ingress ES errored- Y2)
seconds
SES severely Y2)
-
errored-
seconds
UAS unavail- Y2)
able-
seconds
delay- DEL odu- Y
measure- AY delay
ment-odu
otu-nend- EB errored- Y Y
ingress blocks
ES errored- Y Y
seconds
SES severely Y Y
-
errored-
seconds
UAS unavail- Y Y
able-
seconds
Table 82 Supported Performance Monitoring list

er 100 car osc
g d
coherent- DGD differen- Y
optical- tial-
interface group-
delay
CD chro- Y
matic-
disper-
sion
OSN osnr Y
R
Q- q-factor Y
facto
r
PDL polar- Y
ization-
depen-
dent-
loss
OFT in- Y
optical-
fre-
quency
OFR out- Y
optical-
fre-
quency
optical- OPR in- Y Y Y
power optical-
power
OPT out- Y Y Y
optical-
power
loss LOS loss-of- Y3) Y Y Y Y Y Y
S signal-
seconds

er 100 car osc
g d
ethernet- SE in- Y
nend- symbol-
ingress errors
Drop in-drop- Y
Even events
ts
Octe in- Y
ts octets
Pkts in- Y
packets
Broa in- Y
dcas broad-
tPkts cast-
packets
Mul- in-multi- Y
ticas cast-
tPkts packets
CRC in-crc- Y
Align align-
Error errors
s
Und in- Y
ersiz under-
ePkt size-
s packets
Over in- Y
size oversize
Pkts -
packets
Frag in-frag- Y
ment ments
s
Jabb in- Y
ers jabbers
Pkts in- Y
64O packets
ctets -
64octet
s
Pkts in- Y
65to packets
127 -
Octe 65to127
ts octets
er 100 car osc
g d
ethernet- SE out- Y
nend- symbol-
egress errors
Drop out- Y
Even drop-
ts events
Octe out- Y
ts octets
Pkts out- Y
packets
Broa out- Y
dcas broad-
tPkts cast-
packets
Mul- out-mul- Y
ticas ticast-
tPkts packets
CRC out-crc- Y
Align align-
Error errors
s
Und out- Y
ersiz under-
ePkt size-
s packets
Over out- Y
size oversize
Pkts -
packets
Frag out- Y
ment frag-
s ments
Jabb out- Y
ers jabbers
Pkts out- Y
64O packets
ctets -
64octet
s
Pkts out- Y
65to packets
127 -
Octe 65to127
ts octets
er 100 car osc
g d
fec BE- bit- Y3) Y Y Y
FEC error-
fec
UBE uncor- Y3) Y Y Y
- rected-
FEC block-
error-
fec
BER bit- Y3) Y Y Y
- error-
FEC rate-
before-
fec
POS bit- Y
T- error-
FEC rate-
post-fec
fc-nend- SE in- Y
ingress symbol-
errors

er 100 car osc
g d
sdh-rs- BBE in-back- Y
nend- ground-
ingress block-
error
ES in- Y
errored-
seconds
SES in- Y
severely
-
errored-
seconds
UAS in- Y
unavail-
able-
seconds
OFS in-out- Y
of-
frame-
seconds

er 100 car osc
g d
sonet-s- CV in- Y
nend- coding-
ingress violation
ES in- Y
errored-
seconds
SES in- Y
severely
-
errored-
seconds
UAS in- Y
unavail-
able-
seconds
SEF in- Y
S severely
-
errored-
frame-
second

er 100 car osc
g d
OPR in- Y
optical- - optical-
power- lane- power-
lane high lane-
high
OPR in- Y
- optical-
lane- power-
low lane-low
OPR in- Y
-total optical-
power-
lane-
total
OPT out- Y
- optical-
lane- power-
high lane-
high
OPT out- Y
- optical-
lane- power-
low lane-low
OPT out- Y
-total optical-
power-
lane-
total
equip- T- module- Y
ment- mod tem-
tempera- ule perature
ture
shelf- T- inlet- Y
tempera- inlet tem-
ture perature
T- outlet- Y
outle tem-
t perature

er 100 car osc
g d
loss-txrx LOS loss-tx Y4)
S-Tx
LOS loss-rx Y4)
S-Rx
protec- PSC protec- Y5)
tion- (Pro- tion-
switch tecti switch-
on count
Swit
ch
Cou
nt)
PSD protec- Y
(Pro- tion-
tecti switch-
on duration
Swit
ch
Dura
tion)
optical- OPR in- Y6)
power- optical-
ingress power
optical- OPT out- Y7)
power- optical-
egress power
1) For non-out client type.

2) For OCH-OS&OTU.
3) For otu4-1/*/[3...12].
4) loss-txrx only exists on port 1 of O2OPS module.
5) protection-switch only exists on port 2 and port 3 of O2OPS module.
6) 7)Two separate RX and TX GOPT ports only applicable on BAHOFP2 and
BAUOFP2.
5.4.9 Performance statistics

Besides through performance management, G30 supports to gather current perfor-
mance statistics/historical performance statistics/thresholds to determine overall
network health by performance statistics function.

The user can retrieve above data from the time when the command has been set till the
user set clear statistics command.
To show and clear statistics for the NE:
show stats
clear stats
To show and clear statistics for card, for example, card-1/1:
show stats card-1/1
clear stats card-1/1
To show and clear statistics for pluggable modules, for example, pluggable-1/1/1:
show stats card-1/1/1
clear stats card-1/1/1
g By default, performance statistics has been enabled. If not, perform the following
command to enable statistics:
set performance statistics enable
Relationship between TCA alarms and PM parameter/PM statistics/logical enti-

ties/applicable modules please refer to Table 82 Supported Performance Monitoring list.
5.4.10 Telemetry
Overview
Telemetry is an automated communications process by which measurements and other
data are collected at remote or inaccessible points and transmitted to receiving equip-
ment for monitoring.
gNMI interface
G30 supports Telemetry function to stream data via gNMI interface. gNMI is defined in
gRPC protocol. gRPC (RPC-Remote Procedure Calls) is an open source remote proce-
dure call (RPC) system initially developed at Google.
Currently G30 supports gNMI version of 0.3.1.
Main capabilities supported by G30
• Authentication
• Capability
• Subscription
g Currently G30 does not support Set and Get function.
Authentication
When establishing session, the user needs to do authentication during which need to
verify the user name and password. So the configuration file should follow the format as
in the following defined by gNMI. The configuration file should include server IP address,
port number, user name and password according with Coriant rule. For example:
server=10.13.12.216:8080
username=administrator
password=e2e!Net4u#

cert=ca.crt
altName=*.coriant.com
g About how to do the authentication, refer to 5.4.6 Certification Management on page

185.
Capability
A client MAY discover the capabilities of the target using the Capabilities RPC.
G30 supports the following capabilities:
• CapabilityRequest message
Sent by the client to request capability information from the target.
• CapabilityResponse message
supported_encodings - an enumeration field describing the data encodings sup-
ported by the target
gNMI_version - the semantic version of the gNMI service supported by the target
Subscription
Currently G30 only supports stream function of dynamic mode. The following stream
modes supported by G30 dynamic mode currently are:
• On change: data updates are only sent when the value of the data item changes.
• Sampled: data updates are sent per sample interval.
• Target Defined: Customer request path without any configuration, system will con-
figure these.
The following telemetry operations supported/not supported by G30 is listed in Table 83.
subscribe subscription - - Yes

mode once - Yes
stream On change Yes
Sampled Yes
Target Defined Yes
poll - No
prefix - - Yes
use_aliases - - No
qos - - No
allow_aggrega- - - No
tion
use_models - - No
poll - - - No
aliases - - - No
Table 83 Telemetry operations supported/not supported by G30
The following parameters are related with session operation:

• sample-interval - session sustainable interval, default value 10s, (can be modified

under non-Target Defined mode, the range is between 2s to 10s, step by 1s).
• suppress-redundant - to enable or disable the redundant suppress, when set as
'true' means the redundant suppress is enabled, default value is true.
• heartbeat-interval - a heartbeat timer to protect against the session becomes invalid
if time out, the default value is 20s(the range is between 2s to 1min, step by 1s). If
there is no packet sent during 20s, system will send out a packet to active the
session again.
Collection data scope
• PM (Recommend to use on change, sampled, and once)
g G30 can supports to stream data of PM, the path should indicate the statistics or
specific monitor point under related entities.
E.g., ne/shelf[shelf-id=1]/slot[slot-id=1]/card/statistics;
/ne/shelf[shelf-id=1]/slot[slot-id=1]/…/statistics/out-
octets
Entities that support event include shelf, card, subcard, port, subport, och-os, OTUk,
ODUk, eth10/40/100G, STM64, OC192, 10GWAN_SDH, 10GWAN_SONET,
FC8G, FC16G, GOPT, OSC.
• Alarm (Recommend to use on change and once)
g G30 can supports to stream data of current alarm, the path format should fol-
low:ne/fault/standing-condition
• Event (Recommend to use on change)
g G30 can supports to stream data of event, the path should indicate the entity on
which event is reported, e.g., ne/shelf[shelf-id=1]/slot[slot-
id=1]/card
Entities that support event include shelf, slot, card, subslot, subcard, port, subport,
pluggable, och-os, OTUk, ODUk, eth10/40/100G, STM64, OC192, 10GWAN_SDH,
10GWAN_SONET, FC8G, FC16G, OMS, GOPT, OSC, OCH, OPS, OCM.
g Currently G30 only supports to stream data via path based on Coriant OS model. The
user can refer to Coriant Groove™ G30 YANG Model Description Manual for the
detailed path.
Path format rules

The user usually needs to subscribe after logging into the Telemetry client. When doing
the subscription, the path format should follow the following rules:
The sensor path should be standard path following the tree;
The separator of MO in path use “/”;
The key of MO should be listed by the format: “<MO name>[<keyname1>=<keyval-
ue1>][ <keyname2>=<keyvalue2>][..]”
Support wildcard in the path

Support wildcard as the key of MO, e.g. “../slot[slot-id=*]/..”

Support wildcard “*” as the MO (not included the standard trace MO), e.g..
“../slot[slot-id=1]/card/*/eth40g/odu/..”;
Support wildcard “…” as the multi-layer MO (not include the standard trace MO), e.g.
“../slot[slot-id=1]/…/statistics”;
If the wildcard “*” is on the end of path, it means all child MO/attributes under current
MO, e.g..” ../slot[slot-id=1]/card/*”
If there is no key with a MO means target are this type MO with all available key, e.g..
“../slot[slot-id=1]/card/port/*/statistics”
Example: /ne/shelf[shelf-id=1]/slot[slot-id=3]/…/odu[odutype-L1=*
][oduid-L1=*][odutype-L2=odu2][oduid-L1=*]/statistics;
/ne/shelf[shelf-id=1]/slot[slot-id=1]/…/statistics/out-octets;
/ne/shelf[shelf-id=1]/slot[slot-id=1]/card/*/statistics;
g If the user get responded value “0000-00-00T00:00:00.000Z” for last-clear-time, it

consider the NE is invalid, it may result from the situation that the card is absent, MEA
alarm is raised, or statistics is disabled.
Script examples
Example of retrieving all current alarm with ONCE mode subscription on standing-con-
dition object:
19/03/07 17:08:31,43 Sending SubscribeRequest subscribe {
subscription {
path {
element: "ne"
element: "fault"
element: "standing-condition"
}
mode: SAMPLE
sample_interval: 3000000000
}
mode: ONCE
encoding: JSON_IETF
}
19/03/07 17:08:32,215 Update received

update {
timestamp: 1551949745122000000
prefix {
element: "ne"
element: "fault"
}
update {
path {
element: "standing-condition[fm-
entity=/ne:ne/ne:system/ne:networking/ne:interface[ne:if-name=\
'eth2\'\\]][condition-type=LINKDOWN][location=near-
end][direction=not-applicable][time-period=not-applicable]"
}
val {

json_ietf_val: "[{\n \"fm-entity\": \

"/ne:ne/system/networking/interface[if-name=\'eth2\']\",\n \
"condition-type\": \"LINKDOWN\",\n \"location\": \"near-end\
",\n \"direction\": \"not-applicable\",\n \"time-period\
": \"not-applicable\",\n \"service-affect\": \"NSA\",\n \
"severity-level\": \"major\",\n \"occurrence-date-time\": \
"2019-03-07T12:57:46+08:00\",\n \"condition-description\": \
"Link Down\",\n \"fm-entity-type\": \"MGTETH\",\n \"alarm-
id\": \"E742324B9975D43FBA6F37726C02201100111000\"\n }]"
}
}
update {
path {
element: "standing-condition[fm-
entity=/ne:ne/ne:system/ne:networking/ne:interface[ne:if-name=\
'eth3\'\\]][condition-type=LINKDOWN][location=near-
end][direction=not-applicable][time-period=not-applicable]"
}
val {
json_ietf_val: "[{\n \"fm-entity\": \
"/ne:ne/system/networking/interface[if-name=\'eth3\']\",\n \
"condition-type\": \"LINKDOWN\",\n \"location\": \"near-end\
",\n \"direction\": \"not-applicable\",\n \"time-period\
": \"not-applicable\",\n \"service-affect\": \"NSA\",\n \
"severity-level\": \"major\",\n \"occurrence-date-time\": \
"2019-03-07T12:57:44+08:00\",\n \"condition-description\": \
"Link Down\",\n \"fm-entity-type\": \"MGTETH\",\n \"alarm-
id\": \"2C74710A07E3514D668D05261717DA1B00111000\"\n }]"
}
}
}
19/03/07 17:08:32,215 Sync Response received
sync_response: true
19/03/07 17:08:32,215 2 updates and 1 messages within 0.00 seconds
19/03/07 17:08:32,215 Statistics: 3991 upd/sec, 1995 msg/sec
Examples of retrieving card statistics with sample stream mode subscription:
subscription {
path {
element: "ne"
element: "shelf[shelf-id=1]"
element: "slot[slot-id=3]"
element: "card"
element: "statistics"
}
mode: SAMPLE
sample_interval: 10000000000
}
encoding: JSON_IETF
}

19/03/07 17:15:32,59 Update received

update {
timestamp: 1551950165167000000
prefix {
element: "ne"
element: "card"
}
update {
path {
}
val {
json_ietf_val: "{\n \"last-clear\": \"2019-03-
07T12:59:40+08:00\",\n \"module-temperature\": {\n \
"instant\": \"38.000\",\n \"avg\": \"37.922\",\n \"min\
": \"35.000\",\n \"max\": \"40.000\"\n }\n}"
}
}
}

sync_response: true

19/03/07 17:15:42,85 Update received
update {
timestamp: 1551950175196000000
prefix {
element: "ne" element: "shelf[shelf-id=1]"
element: "card"
}
update {
path {
}
val {
": \"35.000\",\n \"max\": \"40.000\"\n }\n}"
}
}
}
19/03/07 17:15:52,85 Update received

update {
timestamp: 1551950185197000000

prefix {
element: "ne"
element: "card"
}
update {
path {
}
val {
": \"35.000\",\n \"max\": \"40.000\"\n }\n}"
}
}
}
19/03/07 17:16:02,80 Update received

update {
timestamp: 1551950195192000000
prefix {
element: "ne"
element: "card"
}
update {
path {
}
val {
": \"35.000\",\n \"max\": \"40.000\"\n }\n}"
}
}
}
Example of monitoring the first odu4 object groomed by another high order odu object
on port-1/1/1:
subscription {
path {
element: "ne"
element: "card"
element: "port[port-id=1]"

element: "och-os"
element: "otuc2"
element: "odu[odutype-L1=*][oduid-L1=*][odutype-L2=odu4][oduid-
L2=1][odutype-L3=unused][oduid-L3=0][odutype-L4=unused][oduid-
L4=0]"
}
mode: ON_CHANGE
}
encoding: JSON_IETF
}
19/03/07 17:41:33,756 Update received

update {
timestamp: 1551951727017000000
prefix {
element: "ne"
element: "card"
element: "och-os"
element: "otuc2"
element: "odu[odutype-L1=oduc2][oduid-L1=1][odutype-
L2=odu4][oduid-L2=1][odutype-L3=unused][oduid-L3=0][odutype-
L4=unused][oduid-L4=0]"
}
update {
path {
}
val {
json_ietf_val: "[{\n \"odutype-L1\": \"oduc2\",\n \"oduid-
L1\": 1,\n \"odutype-L2\": \"odu4\",\n \"oduid-L2\": 1,\
n \"odutype-L3\": \"unused\",\n \"oduid-L3\": 0,\n \
"odutype-L4\": \"unused\",\n \"oduid-L4\": 0,\n \
"statistics\": {\n \"last-clear\": \"2019-03-
07T12:59:56+08:00\",\n \"errored-blocks\": \"0\",\n \
"errored-seconds\": \"0\",\n \"severely-errored-seconds\":
\"0\",\n \"unavailable-seconds\": \"16929\"\n },\n \
"odu-type\": \"odu4\",\n \"admin-status\": \"up\",\n \
"oper-status\": \"down\",\n \"avail-status\": \"idle lower-
layer-down\",\n \"alias-name\": \"odu-1/1/1/oduc2-1/odu4-1\
",\n \"service-label\": \"\",\n \"trib-slot\": \"\",\n
\"rx-payload-type\": \"\",\n \"tx-payload-type\": \"\",\n
\"nim-enable\": \"enabled\",\n \"delay-measurement-enable\":
\"disabled\",\n \"opu-config-actual\": \"not-applicable\",\n
\"client-signal-type\": \"not-applicable\",\n \"odu-
termination-mode\": \"terminated\",\n \"exp-sapi\": \"\",\n
\"exp-dapi\": \"\",\n \"exp-operator\": \"\",\n \"tx-sapi\
": \"\",\n \"tx-dapi\": \"\",\n \"tx-operator\": \"\",\
n \"tim-defect-mode\": \"NONE\",\n \"tim-act\": \
"disabled\",\n \"rx-sapi\": \" \",\n \"rx-

dapi\": \" \",\n \"rx-operator\": \"

\",\n \"degrade-interval\": 7,\n \"degrade-threshold\":
128459,\n \"test-signal-type\": \"NONE\",\n \"test-signal-
enable\": \"NONE\",\n \"managed-by\": \"system\",\n \
"connected-interface\": \"/ne:ne/shelf[shelf-id=\'1\
']/slot[slot-id=\'1\']/card/port[port-id=\'1\']/och-
os/otuc2/odu[odutype-L1=\'oduc2\'][oduid-L1=\'1\'][odutype-L2=\
'unused\'][oduid-L2=\'0\'][odutype-L3=\'unused\'][oduid-L3=\'0\
'][odutype-L4=\'unused\'][oduid-L4=\'0\']\",\n \"odu-
encryption\": {\n \"encryption-enable\": \"disabled\",\n
\"block-cipher-mode\": \"CTR\",\n \"encryption-interval\":
30,\n \"time-to-next-key\": 0,\n \"encryption-tx-status\
": \"disabled\",\n \"encryption-rx-status\": \"disabled\
",\n \"odu-key-sync-session\": \"none\",\n \"encryption-
tx-channel-id\": \"\",\n \"encryption-termination-
direction\": \"physical-port\"\n },\n \"test-signal-status\
": {\n \"prbs-sync\": \"not-applicable\",\n \"test-
time-duration\": 0,\n \"prbs-bit-error-count\": \"0\"\n
}\n }]"
}
}
}

sync_response: true

19/03/07 17:41:34,779 Update received
update {
timestamp: 1551951728043000000
prefix {
element: "ne"
element: "card"
element: "och-os"
element: "otuc2"
}
update {
path {
}
val {

"statistics\": {\n \"unavailable-seconds\": \"16930\"\n

}\n }]"
}
}
}
19/03/07 17:41:35,778 Update received

update {
timestamp: 1551951729043000000
prefix {
element: "ne"
element: "card"
element: "och-os"
element: "otuc2"
}
update {
path {
}
val {
}\n }]"
}
}
}
19/03/07 17:41:36,780 Update received

update {
timestamp: 1551951730045000000
prefix {
element: "ne"
element: "card"
element: "och-os"
element: "otuc2"
}
update {

path {
}
val {
}\n }]"
}
}
}
Session close
Under the following 4 situation, session will be closed:
• Client sent ‘shutdown channel’ request
• Actively deleted the session by session management on G30
• TCP link shut down
• NE Reboot
g After reboot, all subscriptions will be cleared.
5.4.11 Fault management

Alarms and events provide information to help you to understand network activity and
troubleshooting problems. G30 supports the fault reporting on the following entities:
• equipment
• logical entities and other facility
• traffic
The Groove™ G30 has the following alarm severities:
• critical
• major
• minor
• not-alarmed
• not-reported
The Groove™ G30 system supports a configurable alarm profile at the NE level which
defines the severity of all alarmed events and not-alarmed events. User is also able to
configure the severity back to default value if necessary.
g Setting administrative status to ‘down’ on current odu facilities will suppress the alarms
on downstream lower layer entities, and the suppression will be terminated by cross-
connections.
Refer to 7.1 Alarms and Possible Recovery Procedures for complete alarm list.
The user can show the alarms in command line to display all the alarm related informa-
tion of the NE.
show alarm

g ‘show alarm’ command no longer displays 'not-reported' alarms, using show -a alarm
(from all) displays all alarms, even those 'not-reported'.
Below is an example of <alarm-profile-id>:

alarm-profile-entry-ztc-fail
To show alarm log:
show log alarm
To show only 5 alarm logs:
show -n=5 log alarm
5.4.11.1 Alarm Report Control (ARC)

Alarm Report Control typically defines the mechanism to control when the system shall
report alarms and TCAs. When ARC is enabled on an entity, the entity will go through a
hold-off period. If during this period no alarm condition is detected before the timer
expired, the entity will transition to the normal alarm-reported status (ALM-Alarm Report-
ing Allowed); if there is alarm condition detected during this period the alarm status will
stay in alarm-not-reported (NALM-QI - No Alarm Reporting Qualified Inhibit) status. This
ensures the entity is stable enough for normal alarm monitoring.
ARC function is limited on Client ports only.
The following figure demonstrates the ARC status switching mechanism:
Figure 106 ARC status switching mechanism
According to Figure 106, the ARC con figuration will be in NALM-QI (No Alarm Reporting
Qualified Inhibit) status by default, if there is qualified problem raised inside the Timer
expired period, the status will be shifted to NALM-NR (No Alarm Reporting Not Ready)
and if this problem is resolved, the status will be shifted to NALM-CD (No Alarm Report-
ing Countdown Inhibit) and the timer will start to countdown from the beginning. If during

this period no qualified problem is raised after Timer expired the ARC control mode will
be shifted to ALM.
The status switching between NALM and NALM-QI or ALM can only be performed when
there is management request.
g Set arc-config of port or subport as “alm” if the user wants alarms reported, otherwise
some alarms can’t be reported.
Attribute group of ARC control

Table 84 lists the attribute group of ARC control.

Attribute Description Privilege

arc-config ARC control mode. Read and Write.
Values: ALM, NALM-QI,
NALM, described as in
Figure 106.
Default value: NALM-QI
Managed by the user only.
arc-state Current state of the ARC Read only.
mode.
Values: ALM, NALM-QI,
NALM.
Default value: NALM-QI
Managed by the system
only.
arc-sub-states Substate of the ARC Read only.
NALM-QI mode.
Values: not-applicable,
NALM-CD, NALM-NR.
arc-timer The timer set for ARC Read and Write.

status switching, configu-
rable parameter for the
hold-off timer.
Default value: 1440
minutes (1 day).
Range: 0 to 10080 minutes
(7 days)
arc-remaining- Remained time of the Read only.
time holdoff timer.
Default value is ARC timer
value.
The value is re-initialized
whenever there is a NALM-
NR to NALM-CD transition
or a change of arc-timer
value.
Table 84 Attribute group of ARC control

5.4.11.2 TTI (Trail Trace Identifier (TTI))

These ODUk Trail Trace Identifier (TTI) are supported to set transmitted/expected value
and retrieve the SAPI (which can be up to 15 characters), DAPI (which can be up to 15
characters) and Operator Specific value (which can be up to 32 characters).
TIM function
The TTI monitor/not to monitor (TIM) operation is provisioned based on each ODUk. The
TIM-ODU alarm will report when the TTI monitor and the expected TTI are different from
the retrieved ones.
When a facility is provisioned to monitor ODUk Trail Trace Identifier for a terminated
ODUk, the user shall be able to provision the facility to insert or not to insert AIS down-
stream on TIM-ODU defect detection.
Automatic TTI on OTUk:
Support automatic TTI Operator specific value setting, which is constructed with NE ID,
shelf ID, slot ID and port ID of the OTU locates. This function provides the capability of
auto-discovery of line port connection topology across in optical network.
5.4.11.3 Alarm Monitor

• Non-intrusive Monitoring on ODU
Support Non-Intrusive Monitoring (NIM) Alarms Suppression on Non-terminated
ODU. When NIM is enabled, the ODU will operate normally to support all NIM
function alarms. When NIM is disabled, the NIM alarms will be suppressed.
g Disabling of NIM function will be denied if the ODU is terminated. If NIM function is
disabled, the ODU will not be provisioned to be terminated.
• Degrade threshold
For dDEG processing at the OTUk/ODUk level, the user is able to set the threshold
number of block errors at which a one-second interval will be considered degraded.
• Degrade interval
For dDEG processing at the OTUk/ODUk level, the user is able to set the consecu-
tive number of one-second intervals with the number of detected block errors
exceeding the block error threshold for each of those seconds between a value of 2
and 10.
5.4.12 Warm restart and cold restart

To warm restart a working NE, perform the following CLI command:
restart ne warm
To cold restart a working NE, perform the following CLI command:
restart ne cold
To restart a card, perform the following CLI command, for example, to restart card-1/1:

restart card-1/1 cold
To restart a pluggable, perform the following CLI command, for example, to restart plug-
gable-1/1/1:
restart pluggable-1/1/1 cold
After performing commands above, the NE will reboot. It may take some minutes to re-
establish the access to the NE after the warm or cold restart.
5.4.13 Log management

The NE Log File records all command requests and responses on all resources that are
accessible by a user, including creation, deletion, and modification of entities, software
and database management activities, and all security related events.
5.4.13.1 System logs

The following logs are visible to the customer via CLI or SFTP(SCP) upload:
• Configuration log - contains all requests performed via NBI.
• Alarm log - contains all alarm notifications with severity of critical, major, and minor.
• Security log - contains all user/session related operations; login/logout, user
creation and deletion, and so on.
• Event log - contains all DB changes, and not alarmed events.
• PM history logs - contains historical PM data.
• Diagnostics log - contains diagnostics information of system, which is free formatted
for diagnosis of support service.
• Summary log - A summary logging file including configuration log, alarm log and
event log.
The following commands can be used to show logs in different formats:
‘show log' displays the list of existing log files.
‘show log <logname>' displays the log content in table format.
‘show log <logname> <exclude=column>' displays the log content in table format,
but omits the column in the table with <column>. The last parameter can be provided
multiple times for multiple columns. Use '?' to get a list of columns to use here.
‘show -n=5 log <logname>' only displays 5 entries of the log in table format.
'show -w log <logname>' displays the log as it is, for example, in text, not in table
format. No header is provided in this case. It can be used together with -n.
For example, to show alarm log:
show log alarm
To show 5 entries of alarm logs:
show -n=5 log alarm
To show alarm log as it is:
show -w log alarm

The following logs can be cleared:

• alarm log
• configuration log
• event log
Use CLI command to clear the log, taking alarm log for example:
Clear log alarm
The following logs can be uploaded:
• diagnostics log
• pm history log
• security log
• summary log
Use CLI command to upload the log, taking summary log for example:
upload summarylog sftp://[email protected]:22/
5.4.14 File Transfer Operation

SFTP (Secure File Transfer Protocol) and SCP (Security Copy) are supported for file
transfer between the Groove™ G30 and the external file server.
5.4.14.1 SFTP (Secure File Transfer Protocol) Transfer Function

Groove™ G30 supports to transfer file by SFTP (Secure File Transfer Protocol), below
operations can be done through SFTP.
• Upload file (log, DB)
• Download file (DB, swimage)
g File destination/source is now capable of referencing both absolute or relative paths, the
commands are listed in the following separately:
• sftp://user@host/relative_path/file
• sftp://user@host//absolute_path/file
g Using Linux SFTP to download/upload files will fail because Linux cannot recognize a
relative path on windows SFTP server.
Thus, for software and database file transfer, paths should be provided in
sftp://[email protected]/path/filename. That’s because while using Windows SFTP
server, the ‘path’ is a relative path to the SFTP root path, which is provisioned on SFTP
server. While using Linux SFTP server, the ‘path’ is an absolute path in Linux file
system.
5.4.14.2 SCP (Security Copy) Transfer Function

Groove™ G30 supports to transfer file by SCP (security copy), below operations can be
done through SCP.
• Upload file (log, DB)

SCP will work over SSH, when performing SCP transfer, the user needs to input IPv4
address, user, password and port (default 22). In the following gives an example of how
to provision SCP through CLI:
administrator@G30_00:b0:c7:6f:ea:69> upload summarylog

scp://[email protected]:22/testlog/log-simulator/
PASSWORD:
g•
• The user can also specify the log file name after the command, for
example: upload summarylog scp://[email protected]:22/testlog/log-
simulator/<log file name>.
g File destination/source is now capable of referencing both absolute or relative paths, the
commands are listed in the following separately:
• scp://user@host/relative_path/file
• scp://user@host//absolute_path/file
5.4.14.3 HTTP (Hypertext Transfer Protocol) Transfer Function

Groove™ G30 supports to transfer file by HTTP (Hypertext Transfer Protocol), below
operations can be done through HTTP.
When performing HTTP transfer, the user needs to input IPv4 address and the port
number (default 80). In the following gives an example of how to provision HTTP through
CLI:
download swimage
http://172.29.132.68:80/G30_GROOVE_2.0.0_20170329
The user can enable HTTP support by using the following command:
set security http-support enabled
And disable it by using:
set security http-support disabled
g File transfer via HTTP is not supported when FIPS mode is enabled.
5.5 System Information
5.5.1 Equipment information

Groove™ G30 supports to display the current power consumption and the maximum
power consumption of current device at room temperature by using the following com-
mands.
show system

Groove™ G30 supports to display the rate of fan speed, and the temperature values
including inlet, outlet, and card/PSU modules by using the following commands. show
card - display the current rate of the fan speed and the SLED/PSU temperatures.
show shelf-1 - display the inlet and outlet temperature of the shelf.
Groove™ G30 supports CFP2-ACO Rx VOA (Variable Optical Attenuation) feature

which provides the capability to control the Rx power by applying a target amount of
attenuation to the CFP2-ACO receiver by the following commands.
set <och-os entity> rx-attenuation <value>
show <och-os entity> rx-attenuation
g Changing the system behavior without alarming unsupported pluggable modules

releases Coriant from warranty obligations for all issues that are resulting from the use
of 3rd party pluggable modules including the potential traffic loss or any other cata-
strophic failure.
5.5.2 Inventory management

The purpose of inventory list is to help the customers check the details of every item of
an equipment they ordered and can be kept for the future reference.
Inventory information for the following entities are available if they are physically present
in the system:
• shelf
• card
• pluggable
The user can show the inventory in the command line interface:
show inventory
The Groove™ G30 can also support to show the inventory of a specific element, for
example:
show inventory-shelf/<shelf-id>
show inventory-card/<shelf-id>/<slot-id>
Groove also supports to show equipment manufacture date under inventory MO for all
pluggable modules. The user can use the following command to show equipment man-
ufacture date:
show inventory manufacture-date
Results including equipment manufacture date pops up:
inventory manufacture-date
-------------------------- -------------
inventory-shelf/1 09/05/2016
inventory-card/1/1 01/18/2018

inventory-pluggable/1/1/1 10/12/2017
For detailed commands please refer to the CLI User Manual.
5.5.3 Third party pluggable modules

MEA alarm can be disabled for 3rd party pluggable modules. If the user chooses to use
3rd party pluggable modules and do not want to alarm MEA, the user can set MEA
disabled by using the following command.
set ne system unknown-pluggable-report disabled
The following warning will be displayed after performing this command.
Changing the system behavior not to alarm unsupported pluggables
releases Coriant from warranty obligations for all issues that
are resulting from the use of 3rd party pluggables including the
potential traffic loss or any other catastrophic failure.
Are you sure? [y/n] y
If the user choose tho enable MEA for 3rd party pluggable modules, perform the following
command.
set ne system unknown-pluggable-report enabled
g Changing the system behavior without alarming unsupported pluggable modules

releases Coriant from warranty obligations for all issues that are resulting from the use
of 3rd party pluggable modules including the potential traffic loss or any other cata-
strophic failure.
5.5.4 Temperature readout

G30 supports to readout temperature on shelf, card, pluggable modules including
CFP2-ACO, QSFP28, QSFP+.
Use show temperature details to show temperature for all of the inventory.

Figure 107 Show temperature details

For temperature on pluggable modules, use show temperature command to show the
temperature:
show pluggable temperature
pluggable temperature (Celsius)
pluggable-1/1/4 29.3
[ne]
---------------- ---------------------
The user can also use show pm command to retrieve temperature information for shelf,
card, and pluggable modules.
5.6 Interworking
Groove™ G30 supports inter-work with hiT7300, mTera UTP/ 7100 Nano/ 7100 Pico
systems.
5.6.1 Interworking with hiT7300

The transmission of Groove™ G30 wavelengths through hiT 7300 line system is sup-
ported.
Figure 108 gives one example of supported scenarios for Groove and hiT 7300 inter-
working. Assuming that all equipment is installed according with respective customer
documentation set. Figure 108 displays the interworking between Groove and hiT 7300
scenario for fixed point-to-point LH/ULH connection.

Figure 108 Groove and hiT 7300 DCI solution with fixed point-to-point LH/ULH con-
nection
In Figure 108 scenario, a basic DCI line system configuration is represented. The CFP2-
ACO line interface, equipped at Groove’s CHM1/CHM2 module, is physically connected
to one of the ports of hiT 7300 F40MDS/F48MDS fixed filter card and multiplexed to the
hiT 7300 line system.
To provision the service for Groove™ G30 wavelengths through hiT 7300 line system
complete the following tasks:
1. Set the CHM1/CHM2 CFP2-ACO line ports associated to the wavelength(s) coming
from hiT7300 (friendly wavelength(s)) as GPI end points. Perform this step at the
near and far end of the wavelength path.
2. Create the necessary cross connections at G30 NEs (for the OCH path between
hiT 7300 NEs).Perform this step at the near and far end of the wavelength path.
3. Create the necessary physical port connections between CFP2-ACO line port and
OMD filter port from Groove G30 NE, if not already performed.
Perform this step at the near and far end of the wavelength path.
4. Create the necessary service at CHM1/CHM2 module at Groove™ G30 NE (internal
cross connections) as described in 5.2.2 Service configuration via CLI. Perform this
step at the near and far end of the wavelength path.
g The Digital Pre-emphasis weight (DPE) (preemphasis value parameter) of the
Groove G30 wavelengths going through hiT 7300 line system must be set to 0.7.
Detailed refer to Figure 132.
5.6.2 Interworking with mTera/7100

The transmissions between Groove™ G30 and mTera/7100 through both Transponder
line side/client side and GCC are supported.
g Values for tx-filter-roll-off/preemphasis should be provisioned as the following accord-

ing with different line modes when interworking with mTera/7100:
Groove GHP 16QAM with mTera: tx-filter-roll-off 0.8, preemphasis 1
Groove CHP 16QAM with mTera: tx-filter-roll-off 0.8, preemphasis 0.7

Groove GHP QPSK with 7100/mTera: tx-filter-roll-off 0.8, preemphasis 1

Groove CHP QPSK with 7100/mTera: tx-filter-roll-off 0.8, preemphasis 0.9
Detailed refer to Figure 132.
Transponder line side interworking

Figure 109 gives the typical scenario for Groove and mTera/7100 interworking through
transponder line side.
Figure 109 Groove and mTera/7100 interworking solution through Transponder line
side
In Figure 109 scenario, the CFP2-ACO line interfaces, equipped at Groove’s
CHM1/CHM2 module, is physically connected to one of the line ports of mTera
OSM2C/OSM4C/OSM4F cards, or 7100 HGTMS/HGTMMS cards.
To provision the service on Groove™ G30 side to interwork with mTera/7100 line
system, complete the following tasks:
1. Provision the CHM1/CHM2 line and client side service.
2. Create the necessary cross connections between line service and client service
according to 5.2.2 Service configuration via CLI.
3. Create the service on mTera/7100 side, set the Baud Rate, Port Mode and FEC type
same with Groove side, detailed refer to mTera/7100 document set.
4. Create the necessary physical port connections between CFP2-ACO line ports of
Groove G30 NE and mTera/7100, if not already performed.
Transponder client side interworking
transponder client side.

Figure 110 Groove and mTera/7100 interworking solution through Transponder client
side
In Figure 110 scenario, the CFP2-ACO client interfaces, equipped at Groove’s
CHM1/CHM2 module, is physically connected to one of the client ports of mTera
g CHM1 doesn’t support OTU4 client with line side QPSK15%FEC, so CHM1 OTU4 can’t
interwork with other products if their module only supports QPSK 15%FEC.
To provision the service on Groove™ G30 client side to interwork with mTera/7100 client
side, complete the following tasks:
1. Provision the CHM1/CHM2 line and client side services, currently Groove only
supports to use 10GBE and 100GBE service to interwork with mTera/7100 client
side.
2. Create the necessary cross connections between line service and client service
according to 5.2.2 Service configuration via CLI.
3. Create the service on mTera/7100 side, set the Baud Rate, Port Mode and FEC type
same with Groove side, detailed refer to mTera/7100 document set.
4. Create the necessary physical port connections between CHM1/CHM2 client ports
of Groove G30 NE and mTera/7100, if not already performed.
GCC interworking
GCC. Take into consideration that the precondition of GCC interworking between
Groove and mTera/7100 is that interworking between both transponder sides works
already.

Figure 111 Groove and mTera/7100 interworking solution through GCC
In Figure 111 scenario, the CFP2-ACO line interfaces, equipped at Groove’s

CHM1/CHM2 module, is physically connected to one of the line ports of mTera
To provision the GCC on Groove™ G30 side to interwork with mTera/7100 line GCC,
complete the following tasks:
1. Provision the CHM1/CHM2 line side service, set line side port mode and admin up
line side port.
2. Provision GCC on Groove side, set numbered or unumberred IP address mode, IP
address, and static route IP.
3. Create line side service on mTera/7100 side, set the Baud Rate, Port Mode and FEC
type same with Groove, detailed refer to mTera/7100 document set.
4. Provision GCC on mTera/7100 side, set IP address mode same with Groove, set IP
address and static route IP.
5. Create the necessary physical port connections between CFP2-ACO line ports of
Groove G30 NE and mTera/7100, if not already performed.

User Guide (UG) Upgrade and maintenance tasks
6 Upgrade and maintenance tasks
6.1 Replacement and after-sale technical support

For information about Coriant services and to contact the Technical Assistance Center
(TAC), refer to the Coriant website at http://www.coriant.com.
Coriant will repair or replace Coriant products provided that the need for this repair or
replacement arises from the ordinary use of the products as intended by the manufac-
turer or otherwise stated in Coriant literature.
For more information about in-warranty and out-of-warranty repairs and returns, contact
Coriant Customer Service at http://www.coriant.com.
Contact the Coriant Technical Assistance Center to return a product for repair or
replacement. When you ship the product, you must use a Return Material Authorization
(RMA) number for tracking purposes.
Coriant strongly recommends that no internal (component-level) testing or repairs be
attempted on the equipment. Unauthorized testing or repairs may void the warranty.
Also, if the equipment is part of a registered system, unauthorized repairs result in non-
compliance with Parts 15 and/or 68 of the FCC Rules and Regulations.
Although repair service always includes an attempt to remove any permanent markings
made by customers on Coriant products, the success of such attempts cannot be guar-
anteed. Therefore, if equipment must be marked defective or bad, Coriant recommends
that it be done with non-permanent materials and, where appropriate, in a manner con-
sistent with the correct handling of electrostatically sensitive devices.
6.2 Fiber optic cleaning requirements

Fiber optic cleaning procedures should be performed only when a problem is suspected,
when new cables are installed or when existing connections are removed and replaced.
To perform the procedures in this section:
• Observe all electrostatic discharge (ESD) practices, equipment handling guidelines,
and power precautions. To prevent personal injury, before you perform a particular
cleaning task, ensure that you are familiar with 2.2.2 Safety precautions and
2.2.3 Optical fiber handling.
g This procedure is service affecting. Before servicing an in-service system, follow

your company's prescribed procedures for obtaining technical assistance, or contact
Coriant Customer Service at http://www.coriant.com/services_support, before con-
tinuing with this procedure. It is the responsibility of the customer to prevent a
service disruption.
• Take traffic into consideration before proceeding with any of the fiber optic cleaning
procedures.
f DANGER!
Laser emissions on the optical interface may be present. Even if traffic has been
removed when the fiber optic cable was disconnected, the laser associated with the
optical interface of the module may still be on. To avoid personal injury to the eyes
assume the laser is always on and never look into the optical interface on any
module.

• Before servicing an in-service system, ensure that traffic has been removed from the
optical interface. This will prevent a service disruption and ensure that direct
exposure to a laser beam is avoided.
• Inspect the connectors on all new optical interfaces such as fiber connectors, adapt-
ers, and bulkheads before they are used to complete a connection.
• Inspect the male and female ends of any connection that is going to be relocated or
reseated.
• Ensure that dust caps are used to cover all unused types of connectors including
fiber patch cables hanging off fiber racks, bulkheads on fiber patch panels, and
system modules. Keep connectors covered when not in use.
• Inspect and clean module (bulkhead) connectors and adapters only if contamination
is suspected.
• If connectors or adapters are damaged or cannot be cleaned, send them back to
Coriant for repair.
• Clean all new system interconnect connectors prior to insertion.
• Use new cleaning material for each connector. Never reuse cleaning materials,
unless directed to do so in a procedure.
• Always insert the receive cable into the channel first, and then insert the associated
transmit cable.
Observe the following admonishments before proceeding with any one of the cleaning
procedures:
f DANGER!
Do not examine fiber optic cables when there is a light source present. Before examining
fiber optic cables with unfiltered magnifying lenses or microscopes, perform the follow-
ing actions to prevent accidental exposure to optical radiation:
Perform the necessary steps to disable the laser source of the fiber to be examined.
Disconnect the optical path from all relevant optical modules.
Turning off a laser source disrupts traffic.
f DANGER!
Open ports and optical cable ends on the main and port shelves can have invisible laser
emissions greater than the class 1 limit and can cause eye damage if viewed directly.
Do not look into an open optical port or the end of a disconnected optical cable. Place
dust caps on any unused transmit or receive port, especially the transmit port.
f DANGER!
Module laser emissions. Place dust caps on any unused receive or transmit port, espe-
cially on the transmit port — even if the fiber optic cable is removed temporarily for ser-
vicing. Arrows on the module next to the ports indicate the direction of light emission.
Potential eye damage may result to anyone passing by who decides to look toward the
system or approach it.

f WARNING!
Electrostatic discharge (ESD) may damage sensitive electronic components resulting in
a traffic-affecting condition. Ensure that plug-in modules are stored in static preventive
material. Do not touch any components on the modules. Handle modules by the edges
or front panel. Always wear a properly grounded wrist strap when handling, removing,
or inserting a module and when touching the equipment shelves or cables. ESD protec-
tive flooring, used with proper ESD footwear, may be used as an alternative to a wrist
strap. ESD wrist straps and footwear must be checked daily to verify performance.
f WARNING!
Failure to disable the laser source of the fiber to be examined and disconnect the optical
path from all relevant optical modules can result in equipment damage. The laser can
burn components of the cleaning solutions and cause build-up of contaminants.
6.2.1 Fiber optic cleaning tools

The following tools are required to perform these procedures:
• Antistatic wrist strap or static-dissipating floor mat. If a static-dissipating floor mat is
used, the proper electrostatic discharge (ESD) footwear must be worn.
• Video inspection probe with adapters
6.2.2 Fiber optic cleaning materials

The following materials are required to perform the cleaning procedures:
• fiber optic cleaning dispenser
• MTP-type fiber optic cleaning dispenser
• 2.5 mm foam swabs
• 1.25 mm foam swabs
• lint-free optic preparations
• optic prep pads with alcohol
• lint-free foam swabs
• non-woven dry wipes
6.3 Fiber optic cleaning procedures

Coriant strongly recommends using a fiber optic cleaning procedure that is IPC 8497-1
compliant, or an equivalent company-approved procedure. The fiber optic cleaning pro-
cedure in this manual is compliant with IPC 8497-1. Observe and review all admonish-
ments and recommendations. Refer to 2.2.3 Optical fiber handling and 6.2 Fiber optic
cleaning requirements before proceeding with any of the cleaning procedures.
Fiber optic connectors should only be cleaned after inspecting them and determining
that they are dirty and actually require cleaning. The degree of cleanliness that can be
achieved in a manufacturing lab is greater than the cleanliness achieved in the field.
Cleaning connectors in the field, without prior inspection, may only make them worse.
Cleaning connectors should be attempted with dry pads before cleaning with wet pads.
Using cleaning solutions increase the chance of removing the initial dirt, however using

these liquids also introduces solution residue. Cleaning this residue requires additional
effort and if not done carefully can cause additional problems.
g Be sure to use only a portion of the prep that has not been touched. One prep may be
used on more than one connector as long as an unused, untouched area of the prep is
used for each connector.
6.3.1 Cleaning LC connectors

To clean LC connectors:
1. Observe 2.2 Fiber optic safety and 6.2 Fiber optic cleaning requirements.
2. Inspect the connector with the fiber scope to determine if there is any contamination
that requires cleaning.
3. Clean the connector end with a dry wipe. Place the dry wipe on a flat and stable
surface. Hold the ferrule end so that it is on top of the dry wipe. Clean the end by
moving the connector.
4. Inspect the connector with the fiber scope and determine if the dirt is still present. If
it is, continue to the next step.
5. For stubborn dirt, place a new optic prep on a flat and stable surface. Hold the ferrule
end so that it is on top of the optic prep. Clean the end by moving the connector.
6. Clean the connector end with a new dry wipe to help dry the ferrule end. Wipe away
any excess solution.
7. Inspect the ferrule end with the fiber scope. If the dirt is still present repeat steps 5.
through 7..
8. Insert the connector into the adapter.
6.3.2 Cleaning MPO connectors

To clean MPO connectors using optic prep:
2. Clean the connector face with an optic prep. Use a wiping motion in one direction
only.
g Be sure to use only a portion of the prep that has not been touched. One prep may
be used on more than one connector as long as an unused, untouched area of the
prep is used for each connector.
3. Clean the connector end with the fiber optic cleaner to help dry the ferrule end. Wipe
away any excess solution.
4. Inspect the ferrule end with the fiber scope. If dirt is still present, repeat steps 2.
through 4.
5. Insert the MPO connector into the adapter.
To clean MPO connectors using MPO/MTP connector cleaner:
2. Remove the dust cap from the MPO connector.
3. Open the cap of the MPO/MTP connector cleaner.
4. Insert the MPO connector end face into the MPO/MTP Connector cleaner.
5. Rotate the wheel until it clicks.
6. Insert the MPO connector into the adapter.

User Guide (UG) Troubleshooting
7 Troubleshooting
7.1 Alarms and Possible Recovery Procedures

This section describes the following alarms and relative possible recovery procedures.
Alarm Descriptions Potential Impact Possible Recovery Procedure

Items
IDP An ID PROM Failure Possible loss of MAC Verify there are no standing equipment alarms on
(IDP) alarm occurs addresses if it is on the NE. Correct any equipment alarms before
when either access to shelf. continuing.
the equipment Possibly not able to If the alarm still occurs, follow your company’s
EEPROM fails or the identify the equipment. prescribed procedures for obtaining technical
contents read are assistance.
invalid.
RUP- The NE generates a Service affecting: Long Verify the alarm description and card status for
DEG Replaceable Unit term, equipment indication to the problem. Contact the local tech-
Problem-Degraded damage could result if nician to troubleshoot the module.
(RUP-DEG) alarm the module does no t If not clear, warm restart to check if it is cleared.
when a module is phys- perform all of its funda-
ically present but is If not clear, perform a cold reset on the alarmed
mental services.
failed so that it supports module. Note that this will lose all traffic on it.
some, but not all, of its If not clear, unplug and then re-plug the power
fundamental services. connectors to the equipment.
If the alarm still occurs, follow your company’s
prescribed procedures for obtaining technical
assistance.
RUP- The NE generates a All traffic supported on a Verify the alarm description and card status for
FAIL Replaceable Unit module with a RUP- indication of the problem. Contact the local tech-
Problem-Failed (RUP- FAIL could be affected. nician to troubleshoot the module.
FAIL) alarm when a If the affected entity is a If not clear, warm restart to check if it is cleared.
module is physically Fan, equipment
If not clear, perform a cold reset on the alarmed
present in its slot, but is damage could occur.
module. Note that this will lose all traffic on it.
failed so that it cannot
support any of its funda- If not clear, unplug and then re-plug the power
mental services. The connectors to the equipment.
potential causes for this If the alarm still occurs, follow your company’s
alarm are: prescribed procedures for obtaining technical
• Power Fan failure assistance.
• No power input
• 12VSB abnormal
condition
Table 85 Alarms and Possible Recovery Procedures


Items
MEA The NE generates a All traffic supported on a Verify the supported module type for the slot.
Mismatch of Equipment module with an MEA Verify the provisioned module type for the slot.
and Attributes (MEA) could be affected.
Verify which module is present in the slot on the
alarm when a module is The potential impact port.
physically present in a depends on the type of
shelf slot but is not com- Delete the module, re-provision the necessary
module inserted in the
patible with the facilities and cross-connections on the module.
slot.
expected module type If not clear, perform a cold reset on the alarmed
based on the NE provi- g MEA alarm can be module. Note that this will lose all traffic on it.
sion or the module that disabled for 3rd
is currently provisioned party pluggable
in the slot, or when a modules. Changing
Coriant pluggable trans- the system behavior
ceiver is not compatible without alarming
with the provisioned unsupported plug-
facility type. gable modules
releases Coriant
An MEA alarm can
from warranty obli-
occur when you insert a
gations for all
replacement module
issues that are
that does not match the
resulting from the
previous module in the
use of 3rd party
slot.
pluggable modules
including the poten-
tial traffic loss or any
other catastrophic
failure.


Items
PWRA, The system generates a If one power feed fails, Examine the front panels of the on the affected
PWRB Power Feed A (PWRA) the module relies on a shelf. The Power LEDs should be amber, indicat-
or Power Feed B single power feed ing a power feed problem.
(PWRB) alarm when an because the redundant Examine the connectors on the power cable to
equipment detects a is lost. the
problem with one of its
shelf and power modules. Ensure the connec-
redundant power feeds.
tions are secure. Ensure that the modules are
PWRA indicates power firmly seated in the backplane.
problem from PSU on
Verify alarms on the corresponding PSU, try to
slot 5, PWRA indicates
clear it.
power problem from
PSU on slot 11. Verify the PSU is properly seated.
Determine if the voltage level is correct, trouble-
shoot to determine the reason for an incorrect
voltage.
If power is not present, check the power breaker
or fuse.
Physically re-seat the corresponding PSU
module.
RUP- The NE generates a All traffic supported on a Verify that the Active and Power LEDs on the
MISS Replaceable Unit- module with a module are lit steady
Missing (RUP-MISS) REPLUNIT-MISS could green and that the Fault LED is off.
alarm against a module be affected.
Physically re-seat the target module.
when a module has
been provisioned, but is Verify that the Fault LED on the newly inserted
not physically present in module flashes and
the system. then turns off.
Verify that the alarm clears.
SDF A Software Download If a software download Determine if there is a PROGFLT alarm.
Failure (SDF) defect fails, the traffic carried Verify that the Fault LED on the module front
occurs when an attempt on the affected module panel is red.
to distribute software to operates under the
If not clear, warm restart to check if it is cleared.
a module fails for a existing software,
duration of ten minutes. without additional If not clear, perform a cold reset on the alarmed
(“Software” refers to features of the new soft- module. Note that this will lose all traffic on it.
either an actual ware. If not clear, unplug and then re-plug the power
software load or the connectors to the equipment.
field programmable
If possible, move the affected module to another
gate array (FPGA) for a
slot.
module.)
If the alarm still occurs, follow your company’s
assistance.


Items
THERMA The Groove™ G30 UTP Overheating of the shelf Verify all that all slots are populated with a
L generates a Thermal could lead to equipment module or a filler module.
alarm when the ambient damage. No slots can be unassigned or unequipped. Insert
temperature where the A defective fan tem- filler modules into
shelf is installed perature sensor could any unpopulated slot.
exceeds acceptable trigger a false thermal
operating limits or when Check for a faulted fan and replace if faulted.
alarm.
not all slots are popu- Verify that proper air conditioning is present at the
lated with a module (or equipment location
a filler module).
and that the system is receiving proper air flow.
LOS The system generates a Potential traffic loss of Measure optical power received at module sup-
Loss Of Signal (LOS) the affected channel. porting alarmed facility.
alarm when the optical Measure optical power being transmitted at trans-
power received for a mitting module.
channel or port in the
Inspect and clean fiber connector on module.
system falls below the
threshold register that Re-seat affected module.
the NE maintains. Replace Coriant pluggable transceiver.
Replace affected module.
LOL The system generates a Potential traffic loss of Measure optical power received at module sup-
Loss Of lock (LOL) the affected channel. porting alarmed facility.
alarm when the optical Measure optical power being transmitted at trans-
signal received for a mitting module.
channel or port in the
Measure optical signal parameters received at
system falls to be
module supporting alarmed facility.
locked.
Inspect and clean fiber connector on module.
Inspect the optical power and signal quality at
upstream of the receiver
Verify the transmitter side provisioned to the
match signal to the receiver side
Re-seat affected module.
Replace Coriant pluggable transceiver.
Replace affected module.


Items
LOF The system generates a Service affecting: Remote:
Loss Of Frame (LOF) Potential traffic loss of
1. Locate module whose facility is in alarm.
defect if a Severely the channel carried on
2. Verify connected equipment facility type
Errored Frame (SEF) the alarmed facility.
matches.
condition persists. This Non-service affecting: 3. Measure port-side receive power of module
condition may be The use of the optical supporting alarmed facility.
caused by a mismatch supervisory channel
of signal types between 4. Perform warm reset on module supporting
(OSC), which handles
local and remote facili- alarmed facility.
monitoring and alarm
ties, by optical power 5. Perform cold reset on module supporting
signals between the
level problems, or by alarmed facility.
TL1, is lost. The traffic
the presence of a carried on the Local:
Generic AIS signal. OCn/STMn or E1 signal 1. Connect test equipment to alarmed module.
is degraded. Loss of 2. Clean port In interface and fiber of alarmed
single E1 timing refer- module.
ence. If
3. Measure signal received by alarmed module.
both E1 timing refer- 4. Perform warm reset on alarmed module.
ences have LOF, all 5. Perform cold reset on alarmed module.
modules provisioned for
6. Replace the Coriant pluggable transceiver.
E1 external timing
7. Replace alarmed module.
are in holdover timing 8. Verify integrity of newly installed module.
mode.
9. Troubleshoot source of low received power at
port In interface of alarmed module.


Items
LOF- The system generates a Potential traffic loss of Verify connected equipment facility type matches
OTU Loss of Frame-Optical the affected channel. Measure power of affected entity.
Transport Unit (LOF-
Measure power at transmitting module.
OTU) alarm if the frame
alignment process is in Verify integrity of transmitting equipment.
the out-of-frame (OOF) Verify fibers are clean.
state for three millisec-
Measure optical receive power at transponder.
onds.
Troubleshoot source of low received power at
port in interface of alarmed module
Replace fiber between affected module and
transmitting module.
Replace Coriant pluggable transceiver support-
ing the faulted facility.
Replace Coraint pluggable transceiver on trans-
mitting module.
Replace module.
Perform warm reset on module supporting
alarmed facility.
Perform cold reset on module supporting alarmed
facility.


Items
LOM- The system generates a Potential traffic loss of Verify that the payload provisioning matches at
OTU Loss of Multi-frame- the affected channel. each end.
Optical Transport Unit Verify that the FEC Type (FEC Type) settings
(LOM-OTU) alarm after match on both lines in the circuit.
detecting LOM-OTU
Perform a power measurement of the affected
defect. The LOM-OTU
entity.
defect is detected when
the OTUk multi-frame Measure power at the transmitting module.
alignment process is Record the value and verify that it is within speci-
persistently in the out- fication.
of-multi-frame (OOM) Perform warm reset on module supporting
state for 3 milliseconds. alarmed facility.
Perform warm reset on module supporting faulted
facility.
facility.
Verify integrity of transmitting equipment.
Examine the fiber and verify the integrity of the
transmitting equipment. Examine all connectors
and make sure they are secure.
Verify fibers are clean.
Manually measure the optical receive power at
the port module.
Replace the module.
TIM- Trace Identifier Mis-connection of the Examine the connections to the alarmed
OTU, Mismatch on ODU line facility on a tran- ODU/facility.
TIM-ODU (TIM-ODU)/OTU (TIM- sponder, potential mis- Examine the expected and transmitted TTI values
OTU) alarm when the connection of ODUk for any mis-provisions.
expected Trail Trace facility on a transpon-
Correct any errors by changing the TTI values or
does not match the der, or Provisioning
disable TIM alarm checking.
received Trail Trace. error for the transmitted
or expected Trail Trace
Identifier (TTI) values.


Items
BDI-OTU The Backward Defect No impact to system Verify that a valid OTU signal transmits from the
Indication-Optical traffic. The BDI-OTU NE that is declaring the BDI-OTU alarm by per-
Transport Unit (BDI- defect serves as a forming. If the measurement is within specifica-
OTU) condition occurs if signal to the NE that tions check the far-end NE by following step; If
the BDI bit in the there is a problem with the measurement is not within specifications,
Section Monitoring a downstream tran- troubleshoot the source of the power measure-
overhead field is “one” sponder. ment at the local NE.
for five consecutive Far-End:
frames. This condition
Check the remote card/port/och-os/OTU admin
indicates that an alarm
status. Set up if any of them is down
exists at the far-end NE.
Resolving the alarm at If not clear, check these alarm existed or not in
the far-end NE clears Far End: LOS, LOF-OTU, LOM-OTU. Clear these
the BDI-OTU condition alarm by Possible Recovery Procedure of these
at the local NE. alarms.
If not clear, cold reset on the receiving module.
If not clear, cold reset on the transmitting module
(the module with the BDI-OTU alarm).
If not clear, replace the transmitting module.
BERSD- A Bit Error Rate Signal Potential degradation of Measure optical power received at the interface
OTU Degrade-Optical Trans- the DWDM high speed and verify that the levels are correct per Coriant
port Unit (BERSD-OTU) signal carried by the pluggable transceiver type. Refer to the applica-
alarm is associated with transponder. ble module practice for Coriant pluggable trans-
the OTUk or line facility. ceiver power information.
The system generates a If the affected facility is an line, verify that the FEC
BERSD-OTU when the Type settings match on both lines in the circuit.
received bit error rate of
Perform a warm reset on the affected equipment
the OTUk exceeds the
if not clear.
Degrade threshold on
the port module. Perform a cold reset on the affected equipment if
not clear.
AIS-OTU The system generates Potential loss of OTU Check remote nodes for alarms and resolve any
an Optical Transport and facility on port alarms found.
Unit-Alarm Indication module. If the alarm does not clear, follow your company’s
Signal (AIS-OTU) alarm prescribed procedures for obtaining technical
when an upstream node assistance or contact Coriant Customer Service
detects a root cause at
problem at the OCH
http://www.coriant.com/services_support.
layer and inserts an
AIS-OTU as a mainte-
nance signal to indicate
that an alarm is present
upstream. Resolving
the upstream alarm
clears this alarm.


Items
AIS-OTU The system generates Potential loss of OTU Check remote nodes for alarms and resolve any
an Optical Transport and facility on port alarms found.
Unit-Alarm Indication module. If the alarm does not clear, follow your company’s
Signal (AIS-OTU) alarm prescribed procedures for obtaining technical
when an upstream node assistance or contact Coriant Customer Service
detects a root cause at
problem at the OCH
layer and inserts an
AIS-OTU as a mainte-
nance signal to indicate
that an alarm is present
upstream. Resolving
the upstream alarm
clears this alarm.
BERSD- A Bit Error Rate Signal Potential degradation of Examine the PM data in the line-to-port direction
ODU Degrade-Optical Data the DWDM high speed for any errors.
Unit (BERSD-ODU) signal carried by the If errors exist use PM function on each upstream
alarm is associated with transponder. node to find the error beginning port.
the ODU facility that is
connected to the port Use following steps on the error beginning
module. The system port/link.
generates a BERSD- Verify integrity of transmitting equipment.
ODU when the received Verify fibers are clean.
bit error rate exceeds
Measure optical receive power at transponder.
the Degrade threshold.
Replace Coriant pluggable transceiver support-
ing the faulted facility.
Replace Coraint pluggable transceiver on trans-
mitting module.
Cold reset on the affected equipment
Replace module.


Items
LCK- A Lock-Optical Data When an ODU facility Query the ODU trace to determine the upstream
ODU Unit condition is a con- on a port module is module or invoke circuit discovery from the man-
dition that a user initi- locked (out-of-service), agement system.
ates. It appears when the system sends a Determine if the ODU facility of upstream module
an ODU is locked LCK-ODU condition to is set to locked for a valid reason, such as work
(taken out-of-service). notify downstream being performed by other personnel.
As part of the ODU equipment that no
If the ODU facility is set to locked for a valid
maintenance signal, a signal is passing
reason, do not unlock the facility until the work is
locked ODU (LCK- through the facility.
finished.
ODU) signal is sent
downstream as an indi- If the ODU facility is set to locked, but it should be
cation that upstream the set to the unlocked state.
connection is “locked”
and no signal passes
through.
OCI- An Open Connection Traffic is not present Check upstream nodes for ODU entities that are
ODU Indication-Optical Data due to the open connec- provisioned but not cross-connected.
Unit (OCI-ODU) condition upstream.
tion is an indication that
there is an open con-
nection upstream for
the ODU path. An open
connection is most
often the result of a
missing ODU cross-
connection at the
upstream node.
AIS-ODU The NE generates an Traffic has been Determine if there are any alarms declared on the
Optical Data Unit-Alarm replaced with the AIS connected equipment. If necessary, clear the
Indication Signal (ODU- maintenance signal due alarms on the connected equipment.
AIS) is a signal sent to an upstream alarm. Examine PM Data in Line-to-Port Direction
downstream as an indi-
Warm Reset Connected Module
cation that an upstream
defect has been Warm Reset Module Supporting Faulted Facility
detected. Cold Reset Connected Module
Cold Reset Module Supporting Faulted Facility
Examine Fiber
Replace Module


Items
BDI-ODU A Backward Defect Indi- No impact to system Verify that a valid ODU signal is being transmitted
cation-Optical Data Unit traffic. The BDI-ODU from the NE that is declaring the BDI-ODU alarm.
(BDI-ODU) condition defect serves as a Check the remote card/port/och-os/OTU/ODU
occurs if the BDI bit in signal to the NE that admin-status. Set up if any of them is down.
the Path Monitoring there is a problem with
If not clear, check these alarm existed or not in
overhead field is “one” a downstream port
Far End: LOS, LOF-OTU, LOM-OTU,AIS-
for five consecutive module.
OTU,TIM-OTU,TIM-ODU,LCK-ODU,LOF-
frames. This condition
LOM,AIS-ODU. Clear these alarm by Possible
indicates that an alarm
Recovery Procedure of these alarms.
exists at the far-end NE.
Resolving the alarm at If not clear, cold reset on the receiving module.
the far-end NE clears If not clear cold reset on the transmitting module
the BDI-ODU condition (the module with the BDI-ODU alarm).
at the local NE.
If not clear, replace the transmitting module.
PLM- The Payload Label Potentil mis-connection Examine the connections to the alarmed ODU.
ODU Mismatch-Optical Data in the network where Examine the expected and sent payload label
Unit (PLM-ODU) alarm the client type mapped values for any mis-provisions.
indicates that: the into the ODUk at one
Verify that the ODUk/j on both ends of the circuit
received payload label end of the network does
has the same payload provisioning.
does not match the not match the client
expected payload label type de-mapped from This could mean that the same client type is
based on the type of the ODUk at the other mapped into the ODUk/j or in the OTN multiplex-
payload and mapping end. There could also ing case, that the same tributary slot structure is
or, the FEC (Forward be a difference in the set on both ends of the ODUk/j circuit. The
Error Correction) type assigned payload label payload provisioning indirectly sets the PT
does not match on a value based on provi- (Payload Type) value that is used in the Payload
circuit that has been sioning errors or inter- Label Mismatch comparison.
provisioned between an operation problems Check the FEC type on the och-os level facility at
OTUk and line facility. based on mismatched both ends of the circuit.
payload values.
If the FEC types do not match, change the FEC
Or, there could be a type on the appropriate facility.
FEC mismatch.


Items
LOOMFI The system generates a Traffic loss of the Verify ODUj to ODU4 Multiplexing Provisioned at
Loss of OPU Multiframe affected channel. Far-end.
Identifier (LOOMFI) Perform a power measurement of the affected
alarm when alignment entity.
to the OPU Multiframe
Measure power at the transmitting module.
Identifier is lost for an
Record the value and verify that it is within speci-
OPU4 supporting multi-
fication.
plexed ODUj.
alarmed facility.
facility.
Verify integrity of transmitting equipment.Exam-
ine the fiber and verify the integrity of the trans-
mitting equipment. Examine all connectors and
make sure they are secure.
the port module. If the optical receive power is too
high Bring the power level into range using atten-
uation; If the reading is too low go to next step.
Replace the module.
Replace Fiber Between Affected Module and
Transmitting Module.
MSIM The NE generates a All of the ODUjs on an Find the ODUk/j entity into which the ODUj with
Multiplex Structure unprotected circuit are the MSIM-ODU alarm is being mapped. Trace
Identifier Mismatch- replaced with ODUj-AIS this ODUk/j circuit through the network to the far
Optical Data Unit in the forward direction end where the ODUk/j is generated.
(MSIM) alarm when the and ODUj-BDI is Check the multiplexing provisioning and verify
received MSI does not inserted in the reverse that the same tributary slot(s) are being used for
match the expected direction. the ODUj within the ODUk/j and verify that the
MSI. same tributary port number is being used for the
The values for the ODU given tributary slot(s).
type and Tributary Port If there are any differences, re-provision one or
(defined by its identifier both ends of the ODU circuit so that the two ends
of the ODU) within each have matching multiplexing structures.
Tributary Slot must
match at both ends of
the ODUj circuit.


Items
LOFLOM The system generates a All of the ODUjs on an Check the system response to verify that the far-
Loss of Frame Loss of unprotected circuit are end provisioning matches the near-end provision-
Multi-frame (LOFLOM) replaced with ODUj-AIS ing for the TRIBSLOT and the Supporting ODU
alarm when an ODUj in the forward direction Tributary Port size and position of each ODUj
within an ODUj-ODUk and ODUj-BDI is within the ODUk.
multiplex has lost frame inserted in the reverse If necessary, change the provisioning so that it
or multi-frame align- direction. matches.
ment.
Where an ODUj is multi-
plexed into an ODUk, j
may be 0, 1, 2, 2e, 3, or
F depending on the
level of multiplexing
supported on the
module. j must be less
than k and k may be 1,
2, 3, or 4.
CSF- The NE generates a Loss of client facility at Examine the client facility at the far end of the
OPU Client Signal Fail- upstream node. circuit and clear any alarms to clear the CSF-
Optical Payload Unit OPU at the local end.
(CSF-OPU) defect If the adaption node has an LOS defect, an
when an client encoun- LOSYNC defect, or an LF defect on the client
ters defects such as facility, use the applicable troubleshooting proce-
LOS on an upstream dures in this manual for the specific alarm.
node. When the defect
is declared on themod-
ule, a CSF-OPU main-
tenance signal is sent
downstream. When the
defect is declared at a
downstream node, the
NE generates a CSF-
OPU alarm.


Items
LOSYNC The system generates a Potential traffic loss of Verify Connected Equipment Facility Type
Loss of Synchronization the affected facility. Matches.
(LOSYNC) alarm when Perform a power measurement of the affected
frame synchronization entity.
is lost on the facility.
fication. For more information about power levels,
refer to the applicable module practice.
alarmed facility.
facility.
Replace the module.
LF The Local Fault (LF) Traffic is affected due to Examine the connected equipment for alarms.
status message is sent a failure at the Resolve the local alarm to clear the LF event.
from a connected Switch/Router. Refer to the appropriate procedure in this manual
Ethernet Switch/Router for any additional troubleshooting steps to take.
to indicate to down-
stream elements that a
local fault has been
detected at the
Switch/Router.
RF The Remote Fault (RF) Traffic is affected due to Examine the far end equipment for alarms.
status message is sent a failure at the Resolve the alarm to clear the RF event. Refer to
from a far end Ethernet Switch/Router. the appropriate procedure in this manual for any
Switch/Router indicat- additional troubleshooting steps to take.
ing that a fault was
received on the corre-
sponding interface in
the opposite direction.


Items
CSF- The Client Signal Fail- Loss of signal at client Locate the upstream module and examine the
LOS- Loss of Signal-Generic facility at upstream port for an LOS alarm. If an alarm exists, refer to
GFP Framing Procedure node. LOS for troubleshooting steps.
(CSF-LOS-GFP) defect If alarm is nor clear. Performing a cold reset on a
indicates an upstream module results in the loss of all traffic passing
module has an LOS through that module. If local procedures require
port facility alarm. additional troubleshooting before performing a
cold reset on a module, contact your local techni-
cian.
If alarm is nor clear. Perform a cold reset on the
module supporting the alarmed facility.
If alarm is nor clear. Replace the Coriant plugga-
ble transceiver on the module.
If alarm is nor clear. Replace the module support-
ing the alarmed facility.
CSF- The Client Signal Fail- Loss of Sync of client Locate the upstream module and examine the
LOSYNC Loss of Synchroniza- signal at upstream port for an LOSYNC alarm. If an alarm exists,
-GFP tion-Generic Framing node. refer to LOSYNC for troubleshooting steps. If no
Procedure (CSF- alarm exists, go to following steps
LOSYNC-GFP) defect Perform a cold reset on a module results in the
indicates an upstream loss of all traffic passing through that module. If
module has an local procedures require additional troubleshoot-
LOSYNC port facility ing before performing a cold reset on a module,
alarm. contact your local technician.
If alarm is not clear. Perform a cold reset on the
module supporting the alarmed facility.
If alarm is not clear. Replace the Coriant plugga-
ble transceiver on the module.
Replace the module supporting the alarmed facil-
ity.


Items
CSF-FDI- The NE generates a If CSF-FDI-GFP is Determine source node of CSF-FDI-GFP inser-
GFP Client Signal Failure- received on the 10GBE, tion.
Forward Defect Indica- 40GBE or 100GBE port At the source node of the CSF-FDI-GFP inser-
tion (CSF-FDI-GFP) at the egress direction, tion, the client port displays an LF failure indicat-
alarm when a module 10GBE, 40GBE or ing that the 10GBE, 40GBE or 100GBE port is
receives client manage- 100GBE signaling is receiving an LF signal from the connected
ment frames (CMF) inserted out the port if 10GBE/40GBE/100GBE equipment.
indicating that CSF-FDI client laser shutdown is
signal has been Resolve the far-end failure.
not enabled. If client
received (occurs when laser shutdown has
CMF frames are been enabled on the
received with a User port, the module turn
Payload Indication of the port transmit laser
0x08). off.
This signal indicates
that the far-end con-
nected device is insert-
ing CSF-FDI based on
receiving LF (Local
Fault) on 10GBE,
40GBE or 100GBE
signal.
CSF- The NE generates a If CSF-RDI-GFP is Determine source node of CSF-RDI insertion.
RDI-GFP Client Signal Failure- received on the 10GBE, At the source node of the CSF-RDI-GFP inser-
Remote Defect Indica- 40GBE or 100GBE port tion, the client port displays an RF failure indicat-
tion (CSF-RDI-GFP) at the egress direction, ing that the 10GBE, 40GBE or 100GBE port is
alarm when module 10GBE, 40GBE or receiving an RF signal from the connected
receives client manage- 100GBE RF signaling is 10GBE/40GBE/100GBE equipment.
ment frames (CMF) inserted out the port.
Resolve the far-end failure to stop RF frames
indicating the CSF-RDI
from being inserted at the connected device.
signal has been
received (occurs when
CMF frames are
received with a User
Payload Indication of
0x05).
This signal indicates
that the far-end con-
nected device is insert-
ing CSF-RDI based on
receiving RF (Remote
Fault) on 10GBE,
40GBE or 100GBE
signal.


Items
LOFD- The system generates a Potential loss of the Verify Connected Equipment Facility Type
GFP Loss of Frame Delinea- client. Matches
tion-Generic Framing Perform a power measurement of the affected
Procedure (LOFD-GFP) entity.
defect when the GFP
process is out of the
SYNC state. An LOFD-
fication. For more information about power levels,
GFP occurs if the trans-
refer to the applicable module practice.
mitting module cannot
generate the GFP layer, Perform warm reset on module supporting
or the detecting module alarmed facility.
cannot read the signal. Perform cold reset on module supporting alarmed
facility.
Replace the module.
PLM- The Payload Label Failed client signal at Verify the client type, mapping mode, and UPI
GFP Mismatch-Generic line to client direction. values at both ends of the circuit match.
Framing Procedure When PLM-GFP is Determine whether the same client mapping
Failure (PLM-GFP) detected, the Local mode is provisioned at both ends.
alarm annunciates Fault Ordered Set will
Determine whether the same UPI value is provi-
against an client facility be sent out of the client
sioned at both ends. The UPI value is provision-
when the accepted port or if auto client
able when mapping mode is PREAMBLE.
User Payload Identifier laser shutdown is
(UPI) in the received enabled, the laser will
GFP client frames is not shut down.
equal to the expected
payload type.
LPBKFA- The NE issues a No impact to system No recovery necessary.
CILITY Loopback Facility traffic. The LPBKFA- The LPBKFACILITY condition clears when you
autonomous message CILITY condition indi- release the loopback. When the loopback is no
when an Facility cates that a port has longer needed in the system, release the
Loopback command set been successfully loopback on this facility.
on a specific port suc- placed in a facility loop-
cessfully. back.


Items
LPBK- The NE issues a No impact to system No recovery necessary.
FTERM Loopback Terminal traffic. The LPBK- The LPBKFTERM condition clears when you
autonomous message FTERM condition indi- release the loopback. When theloopback is no
when an Facility cates that a port has longer needed in the system, release the
Loopback command set been successfully loopback on this facility.
on a specific port suc- placed in a terminal
cessfully. loopback.
T-BE- The Bit Error-Forward Depending on specific Verify that the TCA and threshold is set properly.
FEC Error Correction (T-BE- provisions and use of If there is configuring issue, try to enable/disable
FEC) threshold this threshold crossing the TCA report of this PM point to clear the alarm.
crossing alert (TCA), traffic may Note that this operation will clear all TCA alarm of
alert is an indication that be degraded. the same PM point.
the number of correct- Verify if the TCA alarm will still report after clear in
able errors detected at this PM period and next.
the FEC layer of the
Verify that there are no other alarms raised
incoming signal is
against the module that
above the provisioned
threshold. Correctable would indicate a traffic-affecting situation.
FEC errors are to be Measure optical signal parameters received at
expected even in an module supporting alarmed facility.
signal path with no
Inspect fiber connection on module.
problems, especially for
beyond 100G signals. Inspect the optical power and signal quality
An extremely high upstream.
number of correctable
FEC errors could be an
early indicator of poten-
tial problems with the
signal path that could
escalate into uncorrect-
able FEC errors and
traffic impact.


Items
T-BER- The Bit Error Rate- If the bit error rate on Verify that the TCA and threshold is set properly.
FEC-HT before Forward Error the signal before error If there is configuring issue, try to enable/disable
Correction-High correction continues to the TCA report of this PM point to clear the alarm.
Threshold (T-BER- increase after the Note that this operation will clear all TCA alarm of
FEC-HT) is a warning warning, the corrected the same PM point.
that the bit error rate signal could contain a
Verify if the TCA alarm will still report after clear in
present on the signal large number of bit
this PM period and next.
before errors are cor- errors. The signal could
rected by the forward degrade quickly to the Verify that there are no other alarms raised
error correction process point where traffic is against the module that
has increased to a level completely lost for that would indicate a traffic-affecting situation.
which is approaching particular signal.
the limits of the forward
error correction capabil-
ities. Inspect fiber connection on module.
Inspect the optical power and signal quality
upstream.
T-CD-LT The Chromatic-Disper- Depending on specific Verify that the TCA and threshold is set properly.
sion-Low Threshold (T- provisions and use of If there is configuring issue, try to enable/disable
CD-LT) is a warning this threshold crossing the TCA report of this PM point to clear the alarm.
that the measured chro- alert (TCA), traffic may Note that this operation will clear all TCA alarm of
matic dispersion on the be degraded due to the same PM point.
signal is out of the provi- more penalty from the
sioned limit. experienced chromatic
dispersion.
Verify the measured CD value if it is within the
expectation of the transmission path.
would indicate a traffic-affecting situation.
T-CD-HT The Chromatic-Disper- Depending on specific Verify that the TCA and threshold is set properly.
sion-High Threshold (T- provisions and use of If there is configuring issue, try to enable/disable
CD-HT) is a warning this threshold crossing the TCA report of this PM point to clear the alarm.
that the measured chro- alert (TCA), traffic may Note that this operation will clear all TCA alarm of
matic dispersion on the be degraded due to the same PM point.
signal is out of the provi- more penalty from the
sioned limit. experienced chromatic
dispersion.
Verify the measured CD value if it is within the


Items
T- The Delay Measure- Traffic has higher Verify that the TCA and threshold is set properly.
DELAY- ment-Optical Data Unit- latency than expected. If there is configuring issue, try to enable/disable
ODU-HT High Threshold (T- the TCA report of this PM point to clear the alarm.
DELAY-ODU-HT) Note that this operation will clear all TCA alarm of
threshold crossing alert the same PM point.
at the ODUk level indi-
cates that the measured Verify if the TCA alarm will still report after clear in
round-trip delay this PM period and next.
(latency) for the end-to- Verify the measured CD value if it is within the
end ODU circuit is expectation of the transmission fiber.
higher than the Verify that there are no other alarms raised
maximum value (micro- against the module that
seconds). The most
likely causes for an
increase in delay would
be a change to the
network provision such
as the insertion of a new
node, the splicing of an
optical fiber, or the
creation of a new end-
to-end ODU route.


Items
T- The Delay Measure- Traffic has lower Verify that the TCA and threshold is set properly.
DELAY- ment-Optical Data Unit- latency than expected. If there is configuring issue, try to enable/disable
ODU-LT Low Threshold (T- the TCA report of this PM point to clear the alarm.
DELAY-ODU-LT) Note that this operation will clear all TCA alarm of
threshold crossing alert the same PM point.
at the ODUk level indi-
cates that the measured Verify if the TCA alarm will still report after clear in
round-trip delay this PM period and next.
(latency) for the end-to- Verify that there are no other alarms raised
end ODU circuit is lower against the module that would indicate a traffic-
than the minimum value affecting situation.
(microseconds). The
most likely causes for
too low of a delay would
be an unexpected
change to the network
provision such as the
removal of a node or
change in an end-to-
end ODU route.
Another possibility is
that there is a mis-con-
nection in the ODU path
which results in a delay
that is much lower than
anticipated.
T- The Quality factor - Low Depending on specific Verify that the TCA and threshold is set properly.
QFACTO Threshold (T- provisions and use of If there is configuring issue, try to enable/disable
R-LT QFACTOR-LT) is a this threshold crossing the TCA report of this PM point to clear the alarm.
warning that the alert (TCA), traffic may Note that this operation will clear all TCA alarm of
measured Q-factor on be degraded. the same PM point.
the signal is lower than
limit.
Inspect fiber connection on module.
Inspect the optical power and signal quality
upstream.
against the module that would indicate a traffic-
affecting situation.


Items
T-PDL- The Polarization Depending on specific Verify that the TCA and threshold is set properly.
HT Dependent Loss - High provisions and use of If there is configuring issue, try to enable/disable
Threshold (T-PDL-HT) this threshold crossing the TCA report of this PM point to clear the alarm.
is a warning that the alert (TCA), traffic may Note that this operation will clear all TCA alarm of
measured PDL on the be degraded due to the same PM point.
signal is higher than more penalty from the
limit. experienced PDL.
Verify the measured PDL value if it is within the
T-DGD- The Differential Group Depending on specific Verify that the TCA and threshold is set properly.
HT Delay - High Threshold provisions and use of If there is configuring issue, try to enable/disable
(T-DGD-HT) is a this threshold crossing the TCA report of this PM point to clear the alarm.
warning that the alert (TCA), traffic may Note that this operation will clear all TCA alarm of
measured DGD on the be degraded due to the same PM point.
signal is higher than more penalty from the
limit. Verify if the TCA alarm will still report after clear in
experienced DGD.
Verify the measured DGD value if it is within the
T-EB- The Error Block Count- Depending on specific Verify that the TCA and threshold is set properly.
OTU Optical Transport Unit provisions and use of If there is configuring issue, try to enable/disable
(T-EB-OTU) threshold this threshold crossing the TCA report of this PM point to clear the alarm.
crossing alert (TCA) is a alert (TCA), traffic may Note that this operation will clear all TCA alarm of
count of errored blocks be degraded. the same PM point.
on the OTU based on
the results of the BIP8
processing at the OTUk
level. Verify there is not uncorrectable error on the FEC
of the server layer. Following the procedure solve
the problem of incorrect errors.
Conduct BER testing on the port module to
isolate the source of the errors.


Items
T-EB- The Errored Block- The signal may be Verify that the TCA and threshold is set properly.
ODU Optical Data Unit (T- degraded and have a If there is configuring issue, try to enable/disable
EB-ODU) threshold higher number of block the TCA report of this PM point to clear the alarm.
crossing alert (TCA) is a errors than was Note that this operation will clear all TCA alarm of
count of errored blocks deemed acceptable by the same PM point.
on the ODU based on the threshold setting.
the results of the BIP8
processing at the ODUk
level. Verify there is not uncorrectable error on the FEC
or Errored block counters of the server layer. Fol-
lowing the procedure solve the problem of incor-
rect errors.
Verify the transmitter side if there is error block in
regeneration place of the layer.
Conduct BER testing on the port module to
isolate the source of the errors.
T-ES- The Errored Seconds- Depending on specific Verify that the TCA and threshold is set properly.
ODU, T- Optical Data Unit (T- provisions and use of If there is configuring issue, try to enable/disable
ES-OTU ES-ODU). Errored this threshold crossing the TCA report of this PM point to clear the alarm.
Seconds-Optical Trans- alert (TCA), traffic may Note that this operation will clear all TCA alarm of
port Unit (T-ES-OTU) be degraded or failed. the same PM point.
threshold crossing alert
(TCA) is a count of
errored seconds on the
ODU. An Errored Verify the errored block counters.
Second is detected Verify that there are no other alarms raised
during a second in against the module that would indicate a traffic-
which there was at least affecting situation.
one Errored Block (EB)
or one or more of the
following defects were
present: Supporting
layer is failed, OCI, AIS,
LCK, TIM, LOF, LOM,
LOFLOM, LOS.


Items
T-LOSS The Loss of Signal Depending on specific Verify that the TCA and threshold is set properly.
Seconds (T-LOSS) provisions and use of If there is configuring issue, try to enable/disable
parameter is a count of this threshold crossing the TCA report of this PM point to clear the alarm.
one-second intervals alert (TCA), traffic may Note that this operation will clear all TCA alarm of
containing one or more be degraded. the same PM point.
loss of signal (LOS)
defects.
Measure Received optical power if it is well inside
the threshold of loss.
Verify upper-stream optical power level and
optical power monitoring.
T-OPR- The Optical Power Depending on specific Verify that the TCA and threshold is set properly.
HT Received Level-High provisions and use of If there is configuring issue, try to enable/disable
Threshold (T-OPR-HT) this threshold crossing the TCA report of this PM point to clear the alarm.
TCA is a measure of the alert (TCA), traffic may Note that this operation will clear all TCA alarm of
optical output power of be degraded. the same PM point.
the received signal in
dBm. Verify if the TCA alarm will still report after clear in
the threshold.
T-OPR- The Optical Power Depending on specific Verify that the TCA and threshold is set properly.
LT Received Level-Low provisions and use of If there is configuring issue, try to enable/disable
Threshold (T-OPR-LT) this threshold crossing the TCA report of this PM point to clear the alarm.
threshold crossing alert alert (TCA), traffic may Note that this operation will clear all TCA alarm of
is a measure of the be degraded. the same PM point.
optical output power of
the received signal in
dBm.
the threshold.


Items
T-OPT- The Optical Power Depending on specific Verify that the TCA and threshold is set properly.
HT Transmission Level- provisions and use of If there is configuring issue, try to enable/disable
High Threshold (T- this threshold crossing the TCA report of this PM point to clear the alarm.
OPT-HT) TCA is a alert (TCA), traffic may Note that this operation will clear all TCA alarm of
measure of the optical be degraded. the same PM point.
output power of the
transmitter in dBm.
Measure Transmitted optical power if it is well
inside the threshold.
T-OPT- The Optical Power Depending on specific Verify that the TCA and threshold is set properly.
LT Transmission Level- provisions and use of If there is configuring issue, try to enable/disable
Low Threshold (T-OPT- this threshold crossing the TCA report of this PM point to clear the alarm.
LT) TCA is a measure alert (TCA), traffic may Note that this operation will clear all TCA alarm of
of the optical output be degraded. the same PM point.
power of the transmitter
in dBm. Verify if the TCA alarm will still report after clear in
Measure Transmitted optical power if it is well
inside the threshold.
T-OSNR- The Optical Signal to Depending on specific Verify that the TCA and threshold is set properly.
LT Noise Ratio - Low provisions and use of If there is configuring issue, try to enable/disable
Threshold (T-OSNR- this threshold crossing the TCA report of this PM point to clear the alarm.
LT) is a warning that the alert (TCA), traffic may Note that this operation will clear all TCA alarm of
measured Q-factor on be degraded. the same PM point.
the signal is lower than
limit.
Measure OSNR if it is well inside the threshold.
Verify upper-stream optical signal quality.
Verify the optical signal level to make sure it is in
the range with measurement range.


Items
T-SES- The Severely Errored Depending on specific Verify that the TCA and threshold is set properly.
ODU, T- Seconds-Optical Data provisions and use of If there is configuring issue, try to enable/disable
SES- Unit (T-SES-ODU), this threshold crossing the TCA report of this PM point to clear the alarm.
OTU Errored Seconds- alert (TCA), traffic may Note that this operation will clear all TCA alarm of
Optical Transport Unit be degraded or failed. the same PM point.
(T-SES-OTU) thresh-
old crossing alert (TCA) Verify if the TCA alarm will still report after clear in
is a count of severely this PM period and next.
errored seconds on the Verify errored block threshold setting reporting as
ODU. Severely errored SES.
seconds are detected Verify that there are no other alarms raised
during a second in against the module that would indicate a traffic-
which there were affecting situation.
errored blocks (EBs)
over a rate dependent
threshold or one or
more of the following
defects were present:
Supporting entity is
failed, OCI, AIS, LCK,
TIM, LOM, LOF,
LOFLOM, LOS


Items
T-UAS- The Unavailable Depending on specific Verify that the TCA and threshold is set properly.
OTU, T- Seconds-Optical Data provisions and use of If there is configuring issue, try to enable/disable
UAS- Unit (T-UAS-ODU), this threshold crossing the TCA report of this PM point to clear the alarm.
ODU Unavailable Seconds- alert (TCA), traffic may Note that this operation will clear all TCA alarm of
Optical Transport Unit be degraded or failed. the same PM point.
(T-UAS-OTU) threshold
crossing alert (TCA) is a
count of unavailable
seconds on the ODU. Verify FEC, EB, ES, SES of server layers.
An unavailable second Verify that there are no other alarms raised
is detected during a against the module that would indicate a traffic-
second that is part of affecting situation.
unavailable time. A
period of unavailable
time begins at the onset
of ten consecutive
Severely Errored
Seconds (SESs)
events. These ten
seconds are considered
to be part of unavailable
time.
A new period of avail-
able time begins at the
onset of 10 consecutive
non-SES events. These
ten seconds are consid-
ered to be part of avail-
able time.


Items
T-UBE- The Uncorrectable Depending on specific Verify that the TCA and threshold is set properly.
FEC Block Errors-Forward provisions and use of If there is configuring issue, try to enable/disable
Error Correction (T- this threshold crossing the TCA report of this PM point to clear the alarm.
UBE-FEC) threshold alert (TCA), traffic may Note that this operation will clear all TCA alarm of
crossing alert is a count be degraded. the same PM point.
of block errors that
cannot be corrected at
the FEC layer of the
incoming signal. Verify the procedure of T-BE-FEC also.
Obtain the Fiber Characterization documentation
for all fibers between the port modules.
Calculate the cumulative Chromatic Dispersion
using the fiber
characterization data.
Using the applicable module practice for the port
modules, determine if the value of the remaining
Chromatic Dispersion is within the tolerance of
the modules being used.
If the remaining Chromatic Dispersion is not
within the tolerance of the modules being used,
consult your company’s DWDM network design
department. Any changes to the network (that is,
changing DCM values or types) will affect other
wavelengths in the DWDM span.
T-SE The Symbol Error Depending on specific Verify that the TCA and threshold is set properly.
During Carrier (T-SE) provisions and use of If there is configuring issue, try to enable/disable
threshold crossing alert this threshold crossing the TCA report of this PM point to clear the alarm.
is a count of the number alert (TCA), traffic may Note that this operation will clear all TCA alarm of
of times the receiving be degraded. the same PM point.
media is non-idle (a
carrier event) for a
period of time equal to
or greater than the Measure optical power level to ensure it is well
minimum frame size within specification.
(512 bits), and during Verify the signal quality of the connection.
which there was at least
one occurrence of an
event that causes the
physical layer (PHY) to
indicate “Data reception
error”.


Items
T- he CRC Alignment Depending on specific Verify that the TCA and threshold is set properly.
CRCALI Errors (T-CRCALIGN- provisions and use of If there is configuring issue, try to enable/disable
GNERR ERRORS) threshold this threshold crossing the TCA report of this PM point to clear the alarm.
ORS crossing alert (TCA) is a alert (TCA), traffic may Note that this operation will clear all TCA alarm of
count of CRC alignment be degraded. the same PM point.
errors on an Ethernet
facility. A CRC error
occurs when the
checksum of an Measure optical power level to ensure it is well
Ethernet frame is not within specification.
valid. Depending on the Verify the signal quality of the connection.
use and provision of this
TCA, T-CRCALIGN-
ERRORS can signal
degradation of the
Ethernet facility.
T- The Drop Events (T- Depending on specific Verify that the TCA and threshold is set properly.
DROPE- DROPEVENTS) thresh- provisions and use of If there is configuring issue, try to enable/disable
VENTS old crossing alert is a this threshold crossing the TCA report of this PM point to clear the alarm.
count of packets of data alert (TCA), traffic may Note that this operation will clear all TCA alarm of
dropped on an Ethernet be degraded. the same PM point.
facility.


Items
T- Octets No impact to system No service impact at all, May no recovery neces-
OCTETS Packets traffic. sary.
, T-PKT, Verify that the TCA and threshold is set properly.
Broadcast Packets
T-
Multi-cast Packets If there is configuring issue, try to enable/disable
BROAD-
Packets with 64 octets the TCA report of this PM point to clear the alarm.
CASTP-
in length Packets with Note that this operation will clear all TCA alarm of
KTS, T-
between 65 and 127 the same PM point.
MULTI-
octets in length inclu-
CASTP-
sive
KTS, T-
PKTS64 Packets with between
OCTETS 128 and 255 octets in
, T- length inclusive
PKTS65- Packets with between
TO127O 256 and 511 octets in
CTETS, length inclusive
T- Packets with between
PKTS128 512 and 1023 octets in
TO255O length inclusive
CTETS,
Packets with between
T- 1024 and 1518 octets in
PKTS256 length inclusive
TO511O
threshold crossing alert
CTETS,
(TCA) are count ofs
T- data
PKTS512
packets sent on an
TO1023
Ethernet facility.
OCTETS
,
T-
PKTS102
4TO1518
OCTETS
,


Items
T- The under-size Packets Depending on the provi- Verify that the TCA and threshold is set properly.
UNDER- (T-UNDERSIZEPKTS) sion and use of this If there is configuring issue, try to enable/disable
SIZEPKT threshold crossing alert TCA, a T-UNDER- the TCA report of this PM point to clear the alarm.
S (TCA) is a count of SIZEPKTS TCA can Note that this operation will clear all TCA alarm of
undersized packets signal degradation of an the same PM point.
sent on an Ethernet Ethernet facility.
facility.
Verify upstream for the the performance monitor-
ing.
T-OVER- The under-size Packets Depending on the provi- Verify that the TCA and threshold is set properly.
SIZEPKT (T-OVERSIZEPKTS) sion and use of this If there is configuring issue, try to enable/disable
S threshold crossing alert TCA, a T-OVERSIZEP- the TCA report of this PM point to clear the alarm.
(TCA) is a count of KTS TCA can signal Note that this operation will clear all TCA alarm of
oversized packets sent degradation of an the same PM point.
on an Ethernet facility. Ethernet facility.
Verify upstream for the performance monitoring.
T-FRAG- The Fragments (T- Depending on specific Verify that the TCA and threshold is set properly.
MENTS FRAGMENTS) thresh- provisions and use of If thee is configuring issue, try to enable/disable
old crossing alert (TCA) this threshold crossing the TCA report of this PM point to clear the alarm.
is a count of fragments alert (TCA), traffic may Note that this operation will clear all TCA alarm of
of data packets sent on be degraded. the same PM point.
an Ethernet facility. A
fragment is a frame that
is less than 64 bytes in
length and has a faulty Verify upstream for the the performance monitor-
frame check sequence ing.
field. Verify that there are no other alarms raised
Depending on the use against the module that would indicate a traffic-
and provision of this affecting situation.
TCA, T-FRAGMENTS
can indicate signal deg-
radation.


Items
T- The Jabbers (T- Depending on specific Verify that the TCA and threshold is set properly.
JABBER JABBERS) threshold provisions and use of If there is configuring issue, try to enable/disable
S crossing alert is a count this threshold crossing the TCA report of this PM point to clear the alarm.
of jabbers an Ethernet alert (TCA), traffic may Note that this operation will clear all TCA alarm of
facility sends. be degraded. the same PM point.
T-UTIL- The Utilization-High Depending on specific Verify that the TCA and threshold is set properly.
HT Threshold (T-UTIL-HT) provisions and use of If there is configuring issue, try to enable/disable
threshold crossing alert this threshold crossing the TCA report of this PM point to clear the alarm.
(TCA) is an indication to alert (TCA), traffic may Note that this operation will clear all TCA alarm of
the extent to which an be degraded. the same PM point.
Ethernet facility is used.
Verify if the TCA alarm will still be reported after
cleared in this PM period and next.
It may be necessary to allocate more bandwidth
to the facility or add more capacity (add a LAG).
Check connected equipment and traffic patterns
to determine the optimal solution.
DBACT- The Database Activa- No impact to system Verity the database version and detailed informa-
FAIL tion Failure (DBACT- traffic. tion if it is as expectation.
FAIL) is raised when the Failed to restore data- Verify the received events if it indicate the issue
database restore base. during activation process.
process fails during If no issue found, try activate the database again.
database validation and
If still failed, try download the database again
activation.
from server, then activate it again.


Items
NTPPU NTP Peer Unreachable System time will not be Verify the NTP server is set properly on the NE.
alarm will be raised by synchronized with the Verify the management networking is provisioned
the NE when the con- NTP server. properly on the NE.
nection between NE
Verify the customer DCN provision is provisioned
and the NTP server is
properly.
broken.
Verify the customer's NTP server is set properly.
Verify the IP routing between NE and NTP server
is available.
Verify the NTP protocol is allowed by routers and
firewalls between NTP server and the NE.
Ping and traceroute CLI commands could be
used to check the connectivity.
LINKDO Management interface Management connec- Verify the Ethernet cable is attached properly.
WN Link Down alarm will be tions via the corre- Verify the peer device is working properly.
raised when the system sponding interface will
detect the Ethernet Verify the Interface provision is set properly and
be lost.
interface is down. make sure the admin-status is up.
And then pull and plug the Ethernet cable.
ZTC- Zero Touch Commis- System is not automati- Verify the DHCP item associated with the NE on
FAIL sioning Failed alarm will cally provisioned by the DHCP server.
be raised if the whole ZTC. Verify the file server provision and make sure the
ZTC process is not suc- FTP/SFTP service on the file server starts succe-
cessfully com- sully.
pleted.This could be
Verify the image and provision files for the NE are
caused by the interac-
located in the correct directory on the file server.
tion between NE and
the DHCP server and/or Verify ZTC is enabled on the NE.
file server, or caused by And then restart ZTC process.
the wrong DHCP provi-
sion or FTP/SFTP pro-
vision on the servers.
ZTC- This alarm will be raised No impact to system No recovery necessary.
COMPLE when Zero Touch Com- traffic.
TE missioning Completes
Successfully.


Items
LOGROL Log Roll Over (LOG- No impact to system No recovery necessary.
L ROLL) event generates traffic. Recommend to upload history logging files if
whenever the log file needed.
within the NE is full. The
NE has a circular log file
of more than 5000
records. When the more
record fill, the next
record will be overwrit-
ing the previous record.
SWUPG- The Software Upgrade No impact to system No recovery necessary.
COMPL Complete (SWUPG- traffic.
COMPL) condition
raises when an
software upgrade of the
NE is successfully com-
pleted.
SWUPG- The Software Upgrade No impact to system No recovery necessary.
IP In-Progress (SWUPG- traffic.
IP) condition raises
when an software load
activation command is
successfully completed.
SWUPG- The Software upgrade- No impact to system Verity the software load version and detailed
FAIL Failed (SWUPG-FAIL) traffic. information if it is as expectation.
condition raises when Failed to upgrade soft- Verify the received events if it indicate the issue
the software upgrade ware. during upgrade process.
process fails during
If no issue found, try activate the software load
software load valida-
again.
tion, software load acti-
vation. If still failed, try download the software load again
from server, then upgrade again.
SWUPG- The Software Upgrade- No impact to system Verity the software load version and detailed
ROLLBA ROLLBACK traffic. information if it is as expectation.
CK (SWUPGRD-ROLL- Failed to upgrade soft- Verify the received events if it indicate the issue
BACK) condition raises ware. during upgrade process.
when the software
upgrade process has
again.
been roll back to
original software load If still failed, try download the software load again
because some reason from server, then upgrade again.
the upgrade process
failed to load the newly
installed software load.


Items
INTRU- An INTRUSION event No impact to system No recovery necessary.
SION reports as an autono- traffic. If, during INTRUSION is a transient condition. The invalid
mous event message attempts to establish a account counter clears with the successful login
and also appears in the session, the unknown on any account.
Event Window of the account counter
management system. exceeds a specified
This event indicates an threshold, the NE raises
authentication failure on the INTRUSION event.
an unknown account.
USERLO USERLOCK will be User cannot login for Wait for the suspension-time, which is set by the
CK raised after maximum the suspension-time. operators and the default value is 60 seconds.
number of consecutive After that, re-login with correct user name and
and invalid login password.
attempts for an user is
reached. When the
USERLOCK is raised,
the user account will be
locked out for a dura-
tion, which is called sus-
pension-time.
INIT The NE generates an No impact to system No recovery necessary.
Initialization (INIT) traffic.
alarm after the system
re-initializes either
manually or automati-
cally (warm or cold
reset), and the reset is
complete.
UPG- The Upgrade Complete No impact to system No recovery necessary.
COMPLD (UPG-COMPLD) condi- traffic.
tion raises when a
software upgrade on an
module is successfully
completed, e.g. card
upgrade to new firm
after cold reboot which
is included in the new
software load.


Items
UPG- The Upgrade Failed Failed to upgrade to Verity the software load version and detailed
FAIL (UPG-FAIL) condition new load on the information if it is as expectation.
raises when a software module. Verify the received events if it indicate the issue
upgrade on an module during upgrade process.
is failed, e.g. card fails
to upgrade to new firm
again.
which included in the
new software load. If still failed, try download the software load again
from server, then upgrade again.
MEA- The NE generates a All traffic supported on a Verify the supported SW version for the shelf.
HWVM Mismatch of Equipment module with a MEA- Verify the supported HW version of module in
and Attributes- HWVM alarm could be current SW version, replace the module with the
Hardware Version Mis- affected. The potential supported version for current SW.
match (MEA-HWVM) impact depends on the
alarm when a shelf is type/version of the
physically present or a module inserted in the
module is physically slot.
installed but the current
shelf or module
hardware version not
compatible with the
supported shelf or
module hardware
version in current SW
package release
respectively; or if a shelf
or module is physically
present but the version
of shelf or module
cannot be correctly
identified.


Items
CABS PPP connection carried 1. Path of GCC routing 1. Check the signal quality between GCC path
by GCC channel is link is defected through ports, make sure the signal quality
down • traffic defected which equipped with GCC channel is error
causes OTU- free.
LOS/LOF/AIS 2. Check the provision of GCC mode and
reported protocol between two GCC connection ports,
• traffic defected confirm the provisions are the same type.
causes error
bits
2. Protocol of GCC
channel is mis-
matched.
3. GCC mode
between two side is
mismatched.
LATCH- The NE generates a If the LATCH-OPEN Check the hardware of the module:
OPEN LATCH-OPEN alarm raised during
1. If the hardware latch is opened, close the
module initialization,
alarm against a module latch.
this module will hold on
when the latch of this 2. If the alarm is still existed after step 1, pull out
this status and couldn’t
module is opened. this module and insert it back again, make
be active.
sure the latch is closed.
If the LATCH-OPEN 3. If the alarm is still existed after step 2, return
alarm raised when the to vendor for repairing.
module is working, it
won’t affect the traffic
but will suppress the
lower layer equipment
alarms/event and
service layer
alarms/event/PM. If
accidentally lifting the
left latch which causes
the Active LED flashing,
the provision of the
SLED will be blocked.
When releasing the left

latch down the Active
LED will become solid
and the operation of the
SLED will be automati-
cally recover.


Items
AIS-L Alarm Indication Signal- No impact to system Remote:
Line (AIS-L) is a mainte- traffic. The alarm
1. Measure transmit power of port module.
nance signal in the notifies the NE that a
2. If possible, measure received power of con-
digital network to alert defect or equipment
nected equipment.
downstream equipment failure has occurred
3. Perform warm reset on port module.
of a failure detected upstream.
upstream. In most 4. Perform warm reset on connected equip-
cases, equipment gen- ment.
erates the AIS defined 5. Perform cold reset on port module.
for the next higher layer 6. Perform cold reset on connected equipment.
when it detects a defect Local:
on the signal that it is
terminating. For 1. • Locate alarmed port module and connected
example, section equipment.
2. Inspect cables and connections between port
terminating equipment
module and connected
(STE) generates when
equipment.
it detects an LOS or
3. Inspect and clean fiber connections of port
LOF defect on its
module.
incoming signal.
4. Measure port module transmit optical power.
5. Measure power being transmitted through
cable.
6. Replace cable.
7. Measure receive power of connected equip-
ment.
8. Perform warm reset on connected equip-
ment.
9. Perform cold reset on connected equipment.
10. Replace connected equipment.
11. Verify integrity of newly installed connected
equipment.
13. Perform cold reset on port module.
14. Replace Coriant pluggable transceiver.
15. Replace port module.
16. Verify integrity of newly installed port module.


Items
MS-AIS Multiplex Section-Alarm No impact to system Remote:
Indication Signal (MS- traffic. The alarm
1. Measure transmit power of port module.
AIS) is a maintenance notifies the NE that a
2. If possible, measure received power of con-
signal in the digital defect or equipment
nected equipment.
network to alert down- failure has occurred
stream equipment of a upstream.
failure detected
ment.
upstream. In most 5. Perform cold reset on port module.
cases, equipment gen- 6. Perform cold reset on connected equipment.
erates the AIS defined
Local:
for the next higher
layer when it detects a 1. Locate alarmed port module and connected
defect on the signal that equipment.
it is terminating. For 2. Inspect cables and connections between port
example, module and connected
equipment.
section terminating
3. Inspect and clean fiber connections of port
equipment (STE) gen-
module.
erates when it detects
an LOS or LOF 4. Measure port module transmit optical power.
5. Measure power being transmitted through
defect on its incoming
cable.
signal.
6. Replace cable.
7. Measure receive power of connected equip-
ment.
ment.
9. Perform cold reset on connected equipment.
10. Replace connected equipment.
11. Verify integrity of newly installed connected
equipment.
13. Perform cold reset on port module.
14. Replace Coriant pluggable transceiver.
15. Replace port module.
16. Verify integrity of newly installed port module.


Items
TIM-R The system generates a MONTRC is set to Remote:
Trace Identifier ENABLED-NOAIS.
1. Using the Web GUI, highlight the alarm in the
Mismatch-R alarm (J0
Alarm Window. Note the site and module
Trace
affected.
Identifier Mismatch) 2. From the Navigation Window, navigate from
when the trail trace the site level to the
message of the J0 byte target facility.
that identifies the 3. Right-click the facility to view the shortcut
SONET trace is not the menu, then click Properties.
expected trace. The 4. Click the Alarms tab and verify the alarm.
expected trace is set on 5. Click the General tab. Locate the Received
the port-side J0 Trace text box. Click Query Trace.
of the port module to 6. Verify that the port fiber is connected to the
verify the J0 trace sent correct port. If it is not, correct the miscabling.
by the client signal. If the alarm does not clear, go to step 7.
If the alarm clears, go to step 9.
7. Determine if the received J0 trace optical
trace matches the expected J0 trace.
8. Click the Enable Trace Monitoring box and
type the correct information in the Expected
J0 trace text box. Or, modify the J0 trace sent
by the external equipment.
9. Verify that the alarm clears in the Alarm
Window.
10. Contact your alarm center when done.
If the alarm does not clear, follow your company’s
assistance or contact Coriant Customer Service
at


Items
RS-TIM The system generates a Service affecting: Remote:
Trace Identifier MONTRC is set to
Mismatch-R alarm (J0 ENABLED-AIS or the
Alarm Window. Note the site and module
Trace “Insert AIS on trace-id
affected.
Identifier Mismatch) mismatch” box is 2. From the Navigation Window, navigate from
when the trail trace checked in the manage- the site level to the target facility.
message of the J0 byte ment system. 3. Right-click the facility to view the shortcut
that identifies the Non-service affecting: menu, then click Properties.
SDH trace is not the MONTRC is set to 4. Click the Alarms tab and verify the alarm.
expected trace. The ENABLED-NOAIS. 5. Click the General tab. Locate the Received
expected trace is set on J0 Trace text box. Click Query Trace.
the port-side of 6. Verify that the port fiber is connected to the
the port module to verify correct port. If it is not, correct the miscabling.
the J0 trace sent by the If the alarm does not clear, go to step 7.
client signal. If the alarm clears, go to step 9.
7. Determine if the received J0 trace optical
trace matches the expected J0 trace.
8. Click the Enable Trace Monitoring box and
type the correct information in the Expected
J0 trace text box. Or, modify the J0 trace sent
by the external equipment.
Window.
at


Items
RFI-L The NE generates a No impact to system Remote:
Remote Failure Indica- traffic. The RFI-L defect
tion-Line (RFI-L) defect serves as a signal to the
Event Window. Note the site and module
when bits 6, 7, and 8 of NE that there
affected.
the K2 byte contain the is a problem with far- 2. Clear the alarm on the connected node
’110’ pattern in five con- end equipment. causing it to send RFI-L to the target NE.
secutive frames.
3. Verify that the RFI-L condition clears using
This problem does not the RTRV-COND-ALL command.
affect traffic on the NE
where RFI-L reports.
RFI-L
is generated when the at
far-end NE detects a
problem at the SONET
Line layer
(LOS, LOF, TIM-R).
MS-RFI The NE generates a No impact to system Remote:
Multiplex Section- traffic. The MS-RFI
Remote Fault Indication defect serves as a
Event Window. Note the site and module
(MS-RFI) defect when signal to the NE that
affected.
bits 6, 7, and 8 of the K2 there is a problem with 2. Clear the alarm on the connected node
byte contain the ’110’ far-end equipment. causing it to send MS-RFI to the target NE.
pattern in five consecu-
3. Verify that the MS-RFI condition clears using
tive frames.
the RTRV-COND-ALL command.
This problem does not
affect traffic on the NE
where MS-RFI reports.
MS-RFI indicates a at
problem detected at the
far-end NE. MS-RFI is
generated when
the far-end NE detects
a problem at the SDH
Line layer (RS-TIM and
MS-AIS).


Items
OOG The NE generates an cannot reach the gain Remote:
Out of Gain (OOG) as being set for certain
• Ensure power levels are balanced.
condition for the follow- wavelength.
• Verify previous node is transmitting properly.
ing reasons: • Calculate span loss.
• a hardware failure • Perform cold reset on module.
exists in the AGC Local:
circuit
• Locate alarmed module and transmitting
• a gain setting, when
module.
taken in combina-
tion with the aggre- • Inspect cables and connections on transmit-
gate input power to ting module.
a module, yields an • Measure input signal of alarmed module.
aggregate output • Clean line interface on alarmed input module.
power that is too • Measure power at transmitting module.
high or too low • Measure power being transmitted through
An OOG can be cable.
detected at the output of • Replace cable.
the input amplifier and • Verify integrity of newly installed cable.
also at the output of the • Perform cold reset on transmitting module.
output amplifier. • Replace transmitting module.
• Verify integrity of newly installed transmitting
module.
• Perform cold reset on input module.
• Replace input module.
• Verify integrity of newly installed input
module.


Items
CONNE Key sync session of Connect-fail impacts Check the session-status of the associated key
CT-FAIL encryption key synchro- traffic. synchronization session:
nization is failed. During the key session • Unreachable indicates the remote IP address
initial setup phase, if unreachable, check the communication
there is CONNECT- network, the remote end needs to be routing
FAIL, encryption traffic reachable.
will not be setup suc- • Failed-auth indicates the authentication failed
cessfully; for the session. Checking if PSK in psk-
If CONNECT-FAIL mapping list associated with IP addresses of
happens due to net- the session at both ends are correctly provi-
working issue after sioned and matched.
encryption channel has • Disabled indicates the session is provisioned
been working, encryp- as administratively down. (if not, configuring
tion traffic will sustain the session to be administratively up.)
for about 10*encryption If the alarm does not clear, follow your company’s
interval time. After that, prescribed procedures for obtaining technical
encryption traffic will be assistance or contact Coriant Customer Service
broken. at
ENCRYP ODU channel encryp- Encryption failure Check if the ODU encryption status is encryption-
T-FAIL tion failed. impacts traffic and it failed. If yes, check following provisions:
indicates the failure of Check if there is KEYEX-FAIL alarm associated
ODU encryp- with the ODU, if yes, following instruction of
tion/decryption. KEYEX-FAIL to clear it first.
Check if odu-encryption of the ODU channel at
both ends are matched, if not, correct the provi-
sions.
Check the fiber connection and ODU connection
along the ODU channel if they are connecting
correctly.
Try to disable and enable the encryption again to
see if the problem is solved.
at


Items
KEYEX- Connection for key Encryption failure Check if the ODU encryption status is encryption-
FAIL exchange of the ODU impacts traffic. Receiv- failed. If yes, check following provisions:
channel is failed. ing side cannot get the Check if the associated key-sync-session is pro-
same ODU encryption visioned and if the key-sync-session connecting
key as transmission to the correct remote end, if not complete and
side. correct the provisions.
Check if there is CONNECT-FAIL on the associ-
ated key-sync-session, if yes, follow the instruc-
tion of CONNECT-FAIL to clear the alarm.
Check the value of encryption-status with same
direction of KEYEX-FAIL, if the encryption status
is not Key-in-sync, check both ends of provisions
to make them consistent, and if there is
CONNECT-FAIL for the session on either side of
the ODU channel, follow the instruction to clear
the alarm.
Check if encryption-tx-channel-id is provisioned,
and if the value match the one of remote end.
Check if both ends of the odu-encryption provi-
sions match at both ends of the odu channel on
encryption-interval and encryption-enable, if not,
correct the provisions to have them matched.
Try to disable and enable the encryption again to
see if the problem is solved.
at


Items
BDI The NE declares a The BDI condition Remote:
Backward Defect Indi- serves as a signal to the 1. Using the Web GUI, highlight the alarm in the Alarm Window.
Note the site and module affected.
cation (BDI) condition ifNE that there is a poten-
2. From the Navigation Window, navigate from the site level to the
BDI-P-OTS and BDI-O- tial problem with module supporting the alarmed facility.
OTS defects persist on downstream equip- 3. Verify that a valid OSC signal is being transmitted from the NE
that is declaring the BDI alarm by performing the following steps:
the incoming OSC ment. The alarm
3.1 Right-click the alarmed module to view the shortcut menu,
signal for triggers the 7100 then click Optical Power Measurement.
2.5 (± 0.5) seconds. OTS/7100 Nano to shut 3.2 From the Measurement Type group box, click OSC.
This condition indicates down 3.3 From the Direction drop-down box, click Line Side
Transmit.
that an alarm exists at its output power trans-
3.4 Click Test. Record the value and verify it is within specifica-
the far-end NE. mitting towards the tions. Value = ________. If the measurement is within spec-
Resolving the alarm at equipment with the ifications, go to step 4. If the measurement is not within
specifications, troubleshoot the source of the power mea-
the far-end NE clears defect, if ATPS is surement at
the local NE.
the BDI condition at the enabled.
4. Verify that a valid OSC signal is received by the far-end NE by
local NE. performing the following steps:
4.1
g BDI-P-OTS and 4.2
From the Measurement Type group box, click OSC.
From the Direction drop-down box, click Line Side Receive.
BDI-O-OTS failures
4.3 Click Test. Record the value and verify it is within specifica-
cannot both be tions.
active at the same If the measurement is within specifications, go to step 5.
If the measurement is not within specifications, troubleshoot
time. If there is the source of the power measurement at the local NE.
already an existing 5. Clear the alarm on the connected node causing it to send BDI-O
and BDI-P to the target NE.
BDI-P failure
Local:
declared and then a
1 Using proper fiber handling techniques, use an Optical Time-
BDI-O-OTS defect Domain Reflectometer (OTDR) to check the span fiber and verify
all fiber connections from the NE to the outside plant.
persists for 2.5 (±
0.5) seconds, BDI- 2 Verify that the alarm clears in the Alarm Window.
P-OTS should 3 Contact your alarm center when done.

If the alarm does not clear, follow your company’s prescribed proce-
clear and a BDI-O- dures for
OTS will be obtaining technical assistance or contact Coriant Customer Service at
declared.


Items
BDI-O The OTS layer detects The BDI-O defect Remote:
a Backward Defect Indi- serves as a signal to the 1. Using the , highlight the alarm in the Alarm Window. Note the site and
module affected.
cation-Overhead (BDI- NE that there is a poten- 2. From the Navigation Window, navigate from the site level to the module
supporting the alarmed facility.
O) defect on the tial problem with the
3. Verify that a valid OSC signal is being transmitted from the NE that is declar-
incoming OSC signal if received OSC signal. ing the BDI alarm by performing the following steps:
the BDI-O bit in the OTS 3.1 Right-click the alarmed module to view the shortcut menu, then click
Optical Power Measurement.
control channel byte 3.2 From the Measurement Type group box, click OSC.
is set to “one” for a 3.3 From the Direction drop-down box, click Line Side
Transmit.
period of time greater 3.4 Click Test. Record the value and verify it is within specifications.
Value = ________. If the measurement is within specifications, go to
than or equal to three step 4. If the measurement is not within specifications, troubleshoot
consecutive frames. the source of the power measurement at
the local NE.
This condition indicates 4. Perform a cold reset on the alarmed module by performing the
following steps:
that an alarm exists at 4.1 From the Navigation Window, right-click the alarmed module to view
the far-end NE. Resolv- the shortcut menu, point to Module, then click Edit Out-of-Service
(OOS-MA). A Confirmation box displays.
ing the alarm at the far- 4.2 Click Normal or Forced.
end NE clears the BDI- 4.3 Click OK.
O condition at the local 4.4 In the Navigation Window, right-click the module icon to view the
shortcut menu, point to Module, point to Reset, then click Cold Start.
NE. A Confirmation box displays stating that the operation may result in a
loss of network traffic.
4.5 Click OK.
4.6 To place the module in-service, right-click the module icon to view the
shortcut menu, point to Module, then click Edit In-Service (IS from
OOS-MA). A
Confirmation box displays.
4.7 Click OK.
5. Repeat step 3.1 through step 3.4.
6. Verify that the measurement is within specifications. If the measurement is
within specifications, go to step 8, if the measurement is not within specifi-
cations, go to step 7.
7. Replace the transmitting module by following the procedure in chapter 7.2.
8. Verify that a valid OSC signal is received by the far-end NE by performing
the following steps:
8.1 From the Measurement Type group box, click OSC.
8.2 From the Direction drop-down box, click Line Side Receive.
8.3 Click Test. Record the value and verify it is within specifications.
If the measurement is within specifications, go to step 5.
If the measurement is not within specifications, troubleshoot the
source of the power measurement at the local NE.
Clear the alarm on the connected node causing it to send BDI-O and
BDI-P to the target NE.
9. Verify that the alarm clears in the Alarm Window.
Local: Using proper fiber handling techniques, use an Optical Time-Domain
Reflectometer (OTDR) to check the span fiber and verify all fiber connections from
the NE to the outside plant.


Items
BDI-P The OTS layer detects The BDI-P defect 1. Using the Web GUI, highlight the alarm in the Alarm Window.
a Backward Defect Indi- serves as a signal to the Note the site and module affected.
cation-Payload (BDI-P) NE that there is a poten- 2. Verify that a valid OMS signal is being transmitted from the NE
that is declaring the BDI-P alarm by performing the following
defect on the incoming tial problem with steps:
OSC signal when a the received OMS 2.1 Right-click the alarmed module to view the shortcut menu,
then click Optical Power Measurement.
“one” is received in the signal.
2.2 From the Measurement Type group box, click Aggregate
BDI-P bit of the OTS (OMS).
control channel byte for 2.3 From the Direction drop-down box, click Line Side Trans-
three consecutive mit.
frames. This condition 2.4 Click Test. Record the value and verify it is within specifica-
tions. Value = ________. If the measurement is within spec-
indicates that an alarm ifications, go to step 4. If the measurement is not within
exists at the far-end NE. specifications, troubleshoot the source of the power mea-
surement at
Resolving the alarm at the local NE.
the far-end NE clears 3. Verify that a valid OMS signal is received by the far-end NE by
performing the following steps:
the BDI-P condition at
3.1 Right-click the amplifier or core module receiving from the
the local NE. alarmed module to view the shortcut menu, then click
Optical Power Measurement..
3.2 From the Measurement Type group box, click Aggregate
(OMS).
3.3 From the Direction drop-down box, click Line Side
Receive.
4. Click Test. Record the value and verify it is within specifications.
For more information on power measurements. Value =
________. If the measurement is within specifications, go to step
4. If the measurement is not within specifications, troubleshoot
the source of the power measurement at the local NE.
Window.
dures for
obtaining technical assistance or contact Coriant Customer Service at


Items
LOS- The system generates a Traffic loss of all Remote:
MSA LOS of Mid-Stage channels through the 1. Using the Web GUI, highlight the alarm in the Alarm Window. Note the site
and module affected.
Access (LOS_MSA) alarmed amplifier. 2. From the Navigation Window, navigate from the site level to the target
module.
alarm when a Loss of 3. Right-click the module icon to view the shortcut menu, then click View
Alarms.
Signal is detected on
4. If there is also an OOG declared on the input amplifier, refer to OOG alarm
the mid-stage of the to troubleshoot the alarm.
input amplifier 5. Verify the alarm. Click Cancel to close the window.
Local:
(cable between the first 1. Verify that the Fault LED on the module in question is red.
stage and the second 2. Place the alarmed module out-of-service using admin-down command.
stage) and the defect is 3. From step 4 to step 22, if there are fiber disconnect operation, shut down the
laser source firstly for laser safety.
isolated between two 4. Using proper fiber handling techniques, disconnect the cables at the
alarmed module MSA/DCM In and MSA/DCM Out ports.
stages with the assur-
5. Inspect the MSA/DCM In and MSA/DCM Out interface using an optical
ance that the upstream scope.
signal is valid with an 6. If necessary, using proper fiber handling techniques, clean the MSA/DCM In
and MSA/DCM Out interface.
LOS detector or valid 7. Place the alarmed module in-service using the admin-up command.
Optical Trace ID. The 8. Measure the power at the MSA/DCM Out interface using an optical power
meter.
system generates a If the power level is too low or is not present, go to step 9.
If the power level is within specifications, go to step 19.
LOS_MSA alarm when 9. Place the alarmed module out-of-service using the admin-down command.
it is determined that the 10. Perform a cold reset on the alarmed module using the cold restart
command. Allow five minutes for the module to reboot.
attenuation is not as
11. Place the alarmed module in-service using the admin up command.
high as expected, such 12. Measure power at the MSA/DCM Out interface using an optical power
meter.
as a non-DCF fiber If the output is greater than the line-side receive, go to step 19.
If the output is less than or equal to the line-side receive, go to step 18.
being connected to the
13. Place the alarmed module out-of-service using the admin-down command.
mid-stage. 14. Physically re-seat the alarmed module.
15. Place the alarmed module in-service using the admin-up command.
16. Measure power at the MSA/DCM Out interface using an optical power
meter. If the output is greater than the line-side receive, go to step 19.If the
output is less than or equal to the line-side receive, go to step 18.
17. Replace the alarmed module by following the procedure in chapter 7.2.
18. Then, go to step 8 to re-run the optical power measurements and verify that
the new module is within specifications.
19. Check the optical power of relative node inside the chain whether there have
optical loss, if there have, clean the fiber connector.
20. Replace the DCM by following the procedure in chapter 7.2 and verify that
the insertion loss is within specifications.
21. Inspect the MSA In interface. If necessary, using proper fiber handling tech-
niques, clean the cable.
22. Reconnect the MSA/DCM In cable. Determine if the alarm clears using the
show alarm command. If the alarm does not clear, follow your company’s
prescribed procedures for obtaining technical assistance or contact Coriant
Customer Service at http://www.coriant.com/services_support.If the alarm
clears, go to step 23.

at http://www.coriant.com/services_support.


Items
AUTHN- Authentication failed User login fails due to 1. Check user name and password and ensure
FAILED authentication failure. they are correct. Using correct user name and
password, try it again.
2. Check user name and password and ensure
they are correct. Using correct user name and
password, try it again.
3. Check if the user account is in active status. If
not, contact your NE or AAA server adminis-
trator.
LOGIN- Login failed User fails to login to the 1. If remote authentication is used, check if AAA
FAILED network element. server is reachable from the NE. If not, check
the networking issue to get the server reach-
able first.
2. Check local or remote user account if it is in
active status. If not, contact your NE or AAA
server administrator.
3. Check if connected sessions reaches the
maximum number. If not, reduce the session
number first.
LOSYNC Loss of Synchronization The signals used for 1. Check input power of OSC channel on the
-CD - Chromatic Dispersion fiber CD measurement preamplifier, if it is lower than supported
Measurement is out of synchroniza- range, clean fiber connectors to solve the
tion. Automatic CD problem.
measurement cannot 2. Check remotely connected preamplifier if
function, or the CD there is equipment issue. Solve it issue first.
value cannot be 3. Check span loss of receiver direction of the
updated to track CD preamplifier reporting this alarm, if the span
change in the fiber. loss is out of the range the link can support,
try to clean the fiber connectors to reduce the
span loss to the supported range. If use the
amplifier in the environmental with large span
loss is the intention, change automatic CD
compensation of TDCM to be manual mode.
UPDATE Updating an existing Updating PSK fails due 1. Make sure both side provide the same candi-
-PSK- psk-map failed to candidate-key mis- date-key in update-psk-map RPC or
FAIL matches with peer NE command.
or timeout. 2. Make sure the execution of update-psk-map
command is no more than 30 minutes after
the peer NE issues the same command.
UPDATE Updating an existing Updating PSK is suc- None
-PSK- psk-map completed cessfully completed.
COMPLD


Items
CANDI- The candidate psk has NE has authenticated Wait until UPDATE-PSK-COMPLD reported.
DATE- been authenticated with the candidate PSK from
PSK- peer NE. peer NE.
AUTHEN
TICATED
WTR The Wait To Restore No impact to system No recovery necessary.
(WTR) condition traffic. WTR is a non-alarmed notification.
displays to inform the
user a
protection switch has
occurred in the past and
both facilities are error
free. This
condition displays when
the revertive time starts
to decrement.
DNR The Do Not Revert No impact to system Remote:
(DNR) event indicates traffic. The DNR serves 1. Using the Web GUI, highlight the alarm in the
that the secondary state as a signal that a facility Event Window. Note the site and module
of a fiber affected.
facility fiber protection protection group has 2. Optional: Manually acknowledge the TCA in
group is configured for been configured for a the Event Window. Right-click the TCA to
non-revertive switching secondary state of non- view the shortcut menu, then click
and a revertive Acknowledge.
protection switch switching, and a protec- 3. Verify that the most current avail-status of the
occurred. tion switch has affected protection switch is DNR. If the sec-
occurred. ondary state is correctly configured for DNR,
the procedure is complete.If the secondary
state changes, refer to the appropriate proce-
dure for any additional troubleshooting steps
to take.
If the event has reoccurred, or the secondary
state of the protection switch has not changed,
follow your company’s prescribed procedures for
obtaining technical assistance or contact Coriant
Customer Service at http://www.coriant.com/sup-
port/.


Items
PROTNA The NE generates a Protection No impact to system traffic. Remote:
Not Available (PROTNA) alarm 1. Using the Web GUI, highlight the alarm in the Alarm Window. Note
against the active module when the site and module affected.
the standby module is in an out-of- 2. From the Navigation Window, navigate from the site level to the
service or SWDL state. This is target module.
normal if you re-seat, replace, or 3. Right-click the module icon to view the shortcut menu, then click
upgrade software on the standby View Alarms.
module. 4. Verify the alarm. Determine if any other alarms exist that indicate a
communication problem with the active OFP2s, such as RUP-DEGR or
RUP-FAIL. If these alarms exist, troubleshoot the alarm before continu-
ing. Click Cancel to close the window.
5. Right-click the standby to view the shortcut menu, then click State.
Verify that the module is in the Admin-down state. Click Cancel to close
the window.
6. Verify that no maintenance work is being performed on the standby
module.
If maintenance work is being performed, wait until it is complete and
then go to step 9.
If maintenance work is not being performed, go to step 7.
7. Right-click the standby module to view the shortcut menu, point to
Module, then click Edit In-Service.
8. Right-click the standby module to view the shortcut menu, click Prop-
erties, then click State tab. Verify the primary state of the module.
If the primary state of the module is Admin-down, place the module in-
service.
9. Right-click the standby module to view the shortcut menu, point to
Module, then click Admin-up. If the upgrade state
is execution completed, PROTNA remains until the software commits.
dures for
http://www.coriant.com/support/.


Items
SWITCH- The Groove OTS maintains a Loss of traffic on the GOPT on Remote:
THRES separate Switching Threshold working and protection facilities. 1. Using the Web GUI, highlight the alarm in the Alarm Window. Note
(SWITCH-THRES) register for the site and module affected.
both O2OPS line-side facilities 2. From the Navigation Window, navigate from the site level to the
(working and protection). The target facility.
value for the Switching Threshold
3. Right-click the facility to view the shortcut menu, then click View
is user configurable between 0
Alarms.
dBm and -35 dBm; the default is -
16 dBm for line-side facilities. The 4. Verify the alarm. Click Cancel to close the window.
NE detects a SWITCH-THRES 5. From the Navigation Window, right-click the Protection Switch - x
defect when the total optical power entity (which is located above the GOPT facilities) to view the shortcut
received falls below the switching menu, then click Properties.
threshold for any optical line inter- 6. From the Facility Thresholds and Connections area for the Working
face. GOPT Facility or the Protection GOPT Facility, locate the Switching
The system generates a service Threshold drop-down box and note the value.
affecting SWITCH-THRES if the 7. Verify that the switching threshold is configured correctly per local
alarm is on a facility and the alter- specifications.
nate facility also has an alarm
If the switching threshold value is incorrect, go to step 8. If the switching
(either LOS or SWITCH-THRES).
threshold value is correct, go to step 10.
The system generates a non-
service affecting SWITCH-THRES 8. From the Switching Threshold drop-down box, select the appropriate
if the alarm is on only one facility, value for the Protection Switch.
but the other facility is functional. 9. Determine if the alarm clears. From the Navigation Window,
right-click the affected facility to view the shortcut menu, then click
View Alarms. If the alarm does not clear, go to step 10. If the alarm
clears, go to step 36.
10. Right-click the module icon to view the shortcut menu, then click
Optical Power Measurement.
11. From the Measurement Type group box, select Channel (OCH) or
Port. From the Facility drop-down box, select the appropriate facility:
working GOPT or protection GOPT.
12. Click Test. Compare the optical power measurement with the
switching threshold value.
13. Contact the local technician to perform the local steps.

Local:
14. Comply with the guidelines in Electrostatic Discharge Precautions.
On the module front panel, locate the LED for the affected Protection
Switch. Verify that the O2OPS-x LED is red, indicating a traffic-affect-
ing condition where traffic is unavailable on the port interface, or traffic
is unavailable on both the working GOPT and protection GOPT facili-
ties.
Note: If the LED is amber or flashing amber, this indicates a non-
service affecting condition where either the working GOPT or the pro-
tection GOPT facility is unavailable.
15. Examine the fiber cable that is connected to the O2OPS 1, 2, 3 port
of the O2OPS and either the Line Out interface of the transponder, or
the source port of the working GOPT signal. Check for fiber bends, and
make sure the connections are secure.
If the cable is not broken, go to step 16.
If the cable is broken, go to step 34.
Caution: Placing a module out-of-service results in a loss of traffic.
16. Place the transponder module or source port of the
working GOPT signal out-of-service.
Disconnect the common port receive fiber from the customer
equipment.
17. Comply with the safety precautions in Fiber Optic Safety. Using
proper fiber handling techniques, disconnect the cable connected to
the O2OPS 1, 2, or 3 port of the O2OPS.


Items
18. Inspect the O2OPS 1, 2, or 3 port using a fiber scope. Using proper
fiber handling techniques, clean the cable.
19. Using proper fiber handling techniques, reconnect the cable at the
port of the O2OPS.
20. Place the transponder or source port of the working GOPT signal
in-service.
21. Determine if the alarm clears using relative command.
If the alarm does not clear, go to step 22.
22. Locate the transponder or source port of the working GOPT signal
for the O2OPS. Place the transponder or source port Admin-down
using
the relative command.
23. Using proper fiber handling techniques, disconnect the cable
connected to the Port Out interface of the transponder or the source
port.
24. Inspect the Port Out interface on the transponder, or the source
port, using a fiber scope. Using proper fiber handling techniques, clean
the cable.
25. Using proper fiber handling techniques, reconnect the cable at the
Port Out port of the transponder or the source port.
26. Inspect and clean any other fiber connections between the
transponder Port Out and the O2OPS-x port.
27. Place the transponder in-service using relative command.
28. Determine if the alarm clears using relative command.
If the alarm does not clear, go to step 29.
29. Using proper fiber handling techniques, replace the cable con-
nected to the O2OPS 1, 2, or 3 port and the Port Out port of the tran-
sponder.
30. Determine if the alarm using relative command.
If the alarm does not clear, follow your company’s prescribed
procedures for obtaining technical assistance or contact Coriant
Customer Service at http://www.coriant.com/support/.
dures for obtaining technical assistance or contact Coriant Customer
Service at http://www.coriant.com/support/.


Items
FSTOPROT The Forced Switch to Protection No impact to system traffic. The Remote:
(FSTOPROT) event indicates that FSTOPROT event indicates that a 1. Using the Web GUI, highlight the alarm in the Event
a forced protection switch has forced switch
Window. Note the site and module affected.
occurred from the working facility from the working facility to protec-
to the protection facility. 2. Optional: Manually acknowledge the transient condition in the Event
tion facility of a facility fiber protec-
tion group has Window. Right-click the transient condition to view the shortcut menu,
been configured. then click Acknowledge.

3. Verify that the most current avail-status of the affected
protection switch is FSTOPROT using relative command.
If the most current secondary state is FSTOPROT, go to step 4.
If the secondary state has changed, go to the secondary state
message in this manual for any additional troubleshooting steps to
take.
4. Determine if you are performing any maintenance work on the fiber
protection group that required a forced switch from the working facility
to the protection facility.
If you are performing maintenance work and the secondary state of
FSTOPROT is correct, no further action is necessary. The procedure
is complete.
If you are performing maintenance work and you would like to release
e protection switch, go to step 5.
5. Release the protection switch using relative command.
protection switch is no longer FSTOPROT using relative command.
7. Verify that the FSTOPROT event has not reoccurred in the Event
Window of the Web GUI.
If the event reoccurs, or the secondary state of the protection switch
has not changed, follow your company’s prescribed procedures for


Items
FSTOWKG The Forced Switch to Working No impact to system traffic. The Remote:
(FSTOWKG) event indicates that FSTOWKG event indicates that a 1. Highlight the transient condition in the Event Window. Note the site
a forced protection switch has forced switch from the protection and module affected.
occurred from the protection facility to working facility of a
2. Optional: Manually acknowledge the transient condition in the Event
facility to the working facility. facility fiber protection group has
Window. Right-click the transient condition to view the shortcut menu,
been configured.
then click Acknowledge.
3. Verify that the most current avail-status of the affected protection
switch is FSTOWKG.
If the most current secondary state is FSTOWKG, go to step 4.
If the secondary state has changed, go to the secondary state
message in this manual for any additional troubleshooting steps to
take.
protection group that requires a forced switch from the protection
facility to the working facility.
FSTOWKG is correct, no further action is necessary. The procedure is
complete.
If you are not performing maintenance work and you would like to
release the protection switch, go to step 5.
5. Release the protection switch.
6. Verify that the most current avail-status of the affected protection
switch is no longer FSTOWKG.
7. Verify that the FSTOWKG event does not reoccur in the Event
If the event has reoccurred, or the secondary state of the protection
switch has not changed, follow your company’s prescribed procedures
for obtaining technical assistance or contact Coriant Customer Service
at http://www.coriant.com/support/.
LOCKOUT The LOCKOUT event indicates No impact to system traffic. Remote:

that a user has configured lockout 1. Using the Web GUI, highlight the alarm in the Event
of protection for a facility fiber pro-
tection switch.
protection switch is LOCKOUT using relative command.
If the most current secondary state is LOCKOUT, go to step 4.
If the secondary state has changed, refer to the appropriate procedure
in this manual for any additional troubleshooting steps to take.
protection group that required a lockout of protection.
LOCKOUT is correct, no further action is necessary. The procedure is
complete.
If you are not performing maintenance work and you would like to
protection switch is no longer LOCKOUT using the relative command.
7. Verify that the LOCKOUT event does not reoccur in the Event


Items
MANTO- The Manual Switch to Protection No impact to system traffic. Remote:
PROT (MANTOPROT) event indicates 1. Using the Web GUI, highlight the alarm in the Event
that a
manual protection switch has
occurred from the working facility
to the protection Window. Right-click the transient condition to view the shortcut menu,
facility. then click Acknowledge.

protection switch is MANTOPROT using relative command.
If the most current secondary state is MANTOPROT, go to step 4.
4. Determine if anyone is performing any maintenance work on the
fiber protection group that required a manual switch from the working
facility to the protection facility.
If someone is performing maintenance work and the secondary state
of MANTOPROT is correct, no further action is necessary. The proce-
dure is complete.
If no one is performing maintenance work and you would like to
protection switch is no longer MANTOPROT using relative command.
7. Verify that the MANTOPROT does not reoccur in the Event Window
of the Web GUI.
MANTOWKG The Manual Switch to Working No impact to system traffic. Remote:

(MANTOWKG) event indicates 1. Using the Web GUI, highlight the alarm in the Event
that a
manual protection switch has
occurred from the protection
facility to the working Window. Right-click the transient condition to view the shortcut menu,
facility. then click Acknowledge.

protection switch is MANTOWKG using relative command.
If the most current secondary state is MANTOWKG, go to step 4.
4. Determine if anyone is performing maintenance work on the fiber
protection group that required a manual switch from the protection
facility to the working facility.
If someone is performing maintenance work and the secondary state
of MANTOWKG is correct, no further action is necessary. The proce-
dure is complete.
If no one is performing maintenance work and you would like to
6. Verify that the MANTOWKG does not reoccur in the Event Window
of the Web GUI.
protection switch is no longer MANTOWKG using relative command.


Items
NOREQ The No Request (NOREQ) event No impact to system traffic. No recovery necessary.
appears during revertive protec- NOREQ is a non-alarmed trouble notification and does not require
tion switching and indicates the action.
facility switched back to the
working path.
SDONPROT The Signal Degrade on Protection No impact to system traffic. Remote:

(SDONPROT) event indicates that 1. Using the Web GUI, highlight the alarm in the Event
an automatic protection switch has
occurred because the signal on
the protection 2. Optional: Manually acknowledge the transient condition in the Event
facility has degraded and that an Window. Right-click the transient condition to view the shortcut menu,
automatic switch from the protec- then click Acknowledge.
tion to the working facility of a 3. Verify that the most current avail-status of the affected
facility fiber protection group has protection switch is SDONPROT using relative command.
occurred.
If the most current secondary state is SDONPROT, go to step 4.
4. From the Navigation Window, navigate to the affected module.
View Alarms. Determine if any service affecting alarms exist on the
affected facility.
If alarms exist, resolve the alarms. Then, go to step 6.
If there are no alarms, go to step 7.
protection switch is SDONPROT using the relative command.
If the secondary state is no longer SDONPROT, the procedure is
complete.
If the secondary state is still SDONPROT, go to step 7.
7. Determine if any threshold crossing alerts (TCAs) have occurred on
the affected facility by performing the following steps:
7.1 Right-click the affected facility to view the shortcut
menu, point to Performance Monitoring, then click View PM Point.
7.2 Determine if any TCAs, such as T-ES or LOSS, have occurred.
If TCAs have occurred on the facility, resolve them.Then, go to step 8.
If no TCAs have occurred, go to step 9.
protection switch is SDONPROT using relative command.
If the secondary state is no longer SDONPROT, the procedure is
complete. If the secondary state is still SDONPROT, go to step 9.
9. Depending on the configuration of the system, measure the transmit
and receive power of the module supporting the affected facility. Also,
measure the transmit and receive power of the next upstream module.
Determine if the measurements are within specification.
10. Contact the local technician with the power measurement informa-
tion from step 9.
Local:
11. Correct the signal failure on the protection facility of the protection
switch.


Items
Remote:
13. Verify that the SDONPROT does not reoccur in the Event Window
of the Web GUI.
protection switch is no longer SDONPROT using relative command.
If the event has reoccurred, or the secondary state of the protection
switch has not changed, follow your company’s prescribed procedures
for obtaining technical assistance or contact Coriant Customer Service
at http://www.coriant.com/support/.


Items
SDONWKG The Signal Degrade on Working No impact to system traffic. Remote:
(SDONWKG) event indicates that Affected Facilities ETH, FC8G, 1. Using the Web GUI, highlight the alarm in the Event
a FGE, GBEP, GOPT Window. Note the site and module affected.
protection switch has occurred
because the signal on the working
facility has Window. Right-click the transient condition to view the shortcut menu,
degraded and that an automatic then click Acknowledge.

switch from the working to the pro- 3. Verify that the most current avail-status of the affected
tection facility of protection switch is SDONWKG using relative command.
a facility fiber protection group has If the most current secondary state is SDONWKG, go to step 4.
occurred. If the secondary state has changed, refer to the appropriate procedure
affected facility.
protection switch is SDONWKG using relative command.
If the secondary state is no longer SDONWKG, the procedure is
complete.
If the secondary state is still SDONWKG, go to step 7.
7. Determine if any threshold crossing alerts (TCAs) occurs on the
affected facility by performing the following steps:
7.2 Determine if any TCAs, such as ES-S or LOSS, have occurred.
If TCAs occur on the facility, resolve them. Then, go to step 8.
If no TCAs occur, go to step 9.
protection switch is SDONWKG using relative command.
If the secondary state is no longer SDONWKG, the procedure is
complete.
If the secondary state is still SDONWKG, go to step 9.
tion from step 9.
Local:
switch.
Remote:
13. Verify that the SDONWKG has not reoccurred in the Event Window
of the Web GUI.
protection switch is no longer SDONWKG using the relative
command.


Items
SFONPROT The Signal Fail on Protection No impact to system traffic. Remote:
(SFONPROT) event indicates that 1. Using the Web GUI, highlight the alarm in the Event
an
automatic protection switch has
occurred because the signal on
the protection
facility has failed and that an auto-
matic switch from the protection to
the working protection switch is SFONPROT using the RTRV-FFP-x command.
facility of a facility fiber protection If the most current secondary state is SFONPROT, go to step 4.
group has occurred. If the secondary state has changed, refer to the appropriate procedure
affected facility.
protection switch is SFONPROT using relative command.
If the secondary state is no longer SFONPROT, the procedure is
complete.
If the secondary state is still SFONPROT, go to step 7.
7. Determine if any threshold crossing alerts (TCAs) have occurred on
the affected facility by performing the following steps:
7.1 Right-click the affected facility to view the shortcut menu, point to
Performance Monitoring, then click View PM Point.
If TCAs have occurred on the facility, resolve them.
Then, go to step 8.
protection switch is SFONPROT using relative command.
If the secondary state is no longer SFONPROT, the procedure is
complete.
If the secondary state is still SFONPROT, go to step 9.
tion from step 9.
Local:
switch.
Remote:
13. Verify that the SFONPROT does not reoccur in the Event Window
of the Web GUI.
protection switch is no longer SFONPROT using relative command.
does not change, follow your company’s prescribed procedures for


Items
SFONWKG The Signal Fail on Working No impact to system traffic. Remote:
(SFONWKG) event indicates that 1. Using the 7191 Craft Station, highlight the alarm in the Event
a protection switch has occurred
because the signal on the working
facility has failed and that an auto- 2. Optional: Manually acknowledge the transient condition in the Event
matic switch from the working to Window. Right-click the transient condition to view the shortcut menu,
the protection facility of a facility then click Acknowledge.
fiber protection group has 3. Verify that the most current avail-status of the affected
occurred.
protection switch is SFONWKG using relative command.
If the most current secondary state is SFONWKG, go to step 4.
affected facility.
If the secondary state is no longer SFONWKG, the procedure is
complete.
If the secondary state is still SFONWKG, go to step 7.
7. Determine if any threshold crossing alerts (TCAs) occur on the
affected facility by performing the following steps:
If TCAs have occurred on the facility, resolve them.
Then, go to step 8.
If the secondary state is no longer SFONWKG, the procedure is
complete.
If the secondary state is still SFONWKG, go to step 9.
tion from step 9.
Local:
switch.
Remote:
13. Verify that the SFONWKG does not reoccur in the Event Window of
the 7191 Craft Station.
protection switch is no longer SFONWKG using relative command.


Items
WKSWP The Working Switch to No impact to system No recovery necessary.
R Protect (WKSWPR) traffic. If you need additional information, follow your
event indicates that a company’s prescribed procedures for obtaining
protection switch has technical assistance or contact Coriant Customer
taken place from the Service at http://www.coriant.com/support/.
working facility to the
protect facility.
PRSWW The Protect Switch to No impact to system No recovery necessary.
K Working (PRSWWK) traffic. If you need additional information, follow your
event indicates that a company’s prescribed procedures for obtaining
protection switch has technical assistance or contact Coriant Customer
taken place from the Service at http://www.coriant.com/support/.
protect facility to the
working facility.
CANDI- The candidate psk mis- Update-psk procedure 1 Cancel update-psk procedure on both sides.
DATE- matched with peer NE. cannot complete.
2 Re-check the new PSK value on both sides to
PSK-
make sure they are the same, and then re-
MISMAT
send update-psk command.
CH
ENC- Encryption Traffic Traffic is broken. Re-check the new PSK value on both sides to
TRAFFIC Squelched. make sure they are the same, and then re-send
- update-psk command.
SQUELC
H
PSK- The PSK is mismatched TLS session cannot be Update the PSK associated with the key-sync-
MISMAT with peer NE when TLS established. session, make sure the PSK is the same as peer
CH session is being estab- NE.
lished.
OPTPW The optical power of the OPTPWR-DIFF-HIGH 1 Measure optical power received in this inter-
R-DIFF- interface which was will cause the protection face.
HIGH working channel of switch to protection
2 Measure optical power being transmitted at
OPS, is lower than the channel.
transmitting interface.
protection channel and
over the threshold of 3 Inspect and clean fiber connector on module.
working-protection- 4 Adjust the transmitted amplifier output power
relative-threshold. of this channel.
5 Re-seat affected module.
6 Replace affected module.
7 Replace transmitted module.


Items
PULLOU For FRCU shelf, when The Pull button has User can safely pull out FRCU when active LED
T-TRIG- Pull button is pressed, been pressed for more becomes solid red; the FRCU will automatically
GERED the system will generate than 5s, active LED of warm reboot and return to normal operation if the
transient event of FRCU will be flashing FRCU is not pulled out within 10 minutes.
PULLOUT-TRIG- green indicating SW
GERED before preparation is ongoing
shutdown software for and active LED will be
pullout preparation. RED when the SW
preparation completed
and SW ready for
hitless hot pull out.
7.2 How to replace failed components

This section describes the procedures to replace failed components.
• Removing and replacing a power module
• Removing and replacing a fan module
• Removing and replacing a pluggable module
• Removing and replacing an optical module
• Removing and replacing a failed shelf controller
7.2.1 Removing and replacing a power module

To remove and replace an AC power module:
f Disconnect the power cord before removing the AC power unit.
1. Move the latch to the right side and pull the handle to remove the failed AC power
module.
2. Hold the handle and push the AC power module to the slot.
Figure 112 Remove the AC power module

Insert a new power module according to procedure 4.2.4 Installing the AC/DC power
modules.
Connect the power cord according to procedure 4.2.5 Connecting AC/DC power cords
to the G30.

Check the LED according to procedure 4.2.6 Checking power LED status.
g Replacement of failed power module should be completed within 20 seconds (not

including the power cord operations) to avoid that opening of power module slot affects
the cooing air flow.
To remove and replace an DC power module:
f Disconnect the power cord before removing the power unit.
1. Move the latch to the right side and pull the handle to remove the failed DC power
module.
2. Hold the handle and push the DC power module to the slot.
Figure 113 Remove the DC power module

Insert a new power module according to procedure 4.2.4 Installing the AC/DC power
modules.
Connect the power cord according to procedure 4.2.5 Connecting AC/DC power cords
to the G30.
Check the LED according to procedure 4.2.6 Checking power LED status.
g Replacement of failed power module should be completed within 20 seconds (not

including the power cord operations) to avoid that opening of power module slot affects
the cooing air flow.
7.2.2 Removing and replacing an FRCU controller module

To remove the FRCU controller:
1. Push the left button which marked “Pull” for at least 5 seconds, the Active LED will
become flashing green and the software is preparing for shutdown, when Active
LED becomes red, FRCU is ready for pull out.
2. Lift the latch upside and hold it.
3. Pull the FRCU controller out.

Figure 114 To remove the FRCU controller

To replace an FRCU controller, insert the new FRCU controller toward the chassis
until the module is securely engaged with the back plane:
Figure 115 Install FRCU controller
7.2.3 Removing and replacing a fan module

G30 has a fan redundancy protection mechanism to protect against a single fan failure.
If one fan fails and the failed fan is not removed, G30 can work indefinitely without any
loss in performance.
To remove and replace a fan module:
1. Move the latch to the right side and pull the handle to remove the failed fan.
2. Hold the handle and remove the fan from the slot.

Figure 116 Remove the fan module

Insert a new fan module according to procedure 4.2.7 Installing the fan modules.
g If the user choose to replace the failed fan, fan module’s replacement should be com-
pleted within 20 seconds to avoid that opening of fan module slot affects the cooing air
flow.
7.2.4 Removing and replacing a pluggable module

To remove and replace a pluggable module:
1 When Active LED is flashing, it is not allowed to plug out the SLED.
2 Check if the card is not in ‘initializing’ status by performing the command ‘show
card-1/1 avail-status’. The printed avail-status must not be 'initializing'.
3 Lift the left latch until the Active LED changes from flashing to solid red.
4 Pull out the module using the handle.
g If accidentally lifting the left latch which causes the Active LED flashing, the provision of
the SLED will be blocked. When releasing the left latch down the Active LED will become
solid and the operation of the SLED will be automatically recover.
Figure 117 Remove a pluggable module

Insert the replaced pluggable module according to procedure 4.2.8 Installing pluggable
modules.

7.2.5 Removing and replacing an optical module

To remove and replace an optical module, slide out the module out of the slot.
g Release the locking brackets before removing the CFP2 modules.
Figure 118 Release locking brackets of CFP2 modules
g Insert the new optical module according to procedure 4.2.10 Installing the optical
modules into the pluggable modules.
7.2.6 Removing and replacing a failed shelf controller

1 To remove and replace a failed shelf controller, power down and disconnect all
power cords.
Figure 119 Disconnect the power cords
2 Unplug all power units and fan units.

Figure 120 Unplug PSUs and fan units
3 Disconnect all the fibers and cables from the front side (including grounding cable).
Figure 121 Disconnect all the fibers/cables from the front side
4 Unplug all modules on the front side.
Figure 122 Plug out modules on the front side
5 Unfasten the rack screw from rear side to take off the rear mounting brackets if
present.

Figure 123 Take off the rear mounting brackets (optional)
6 Unfasten the rack screws from the front side to remove from the shelf.
Figure 124 Take off the front mounting brackets
7 Mount the new shelf to the rack and startup the NE. For details, refer to
4.2 Installation procedures and 4.3 Startup procedures.
8 Recover the database. There are two options for database recovery, one is through
remote download, the second option is by replacing the SD card.
For database recovery through remote download, there are two steps:
1 Download database
Here is an example for the user to download database using command line:
download database
sftp://[email protected]:21/208_628_test.zip
2 Activate database
Here is an example for the user to activate database using command line:

activate database
g Activate the database which will lead to cold reboot. After executing activate
command, the database in inactive status will be activated.
g SW will check the version of the downloaded database, if it is not compatible with
existing software, or the database is corrupted, the download will fail.
For database recovery by replacing the SD card, please refer to 7.2.7 Removing and
replacing a failed SD card.
9 Configuration is restored and all traffic is up and running.
7.2.7 Removing and replacing a failed SD card

1 To remove and replace a failed SD card, power down and disconnect all power
cords.
Figure 125 Disconnect the power cords
2 Unfasten the two screws fixing the cover, then remove the small cover.
Figure 126 Plug out PSUs and fan units
3 Pull out the existing SD card and let it rebound automatically.

Figure 127 Disconnect all the fibers/cables from front side
4 Insert the new SD card.

5 Replace the small cover and secure using the two screws.
g Coriant qualified SD cards include SG9SD8GPHDCI01TEL and SH9SD008GPHDCI03

from SMART MODULAR TECHNOLOGIES IN.
7.3 LED Behavior

LEDs on both panels of G30 provide information useful for operation and troubleshoot-
ing purposes.
Figure 128 Chassis LEDs

The chassis LED status are described in Table 86.
LED type Status Description

Power Green Indicates that both power modules are operational.
Amber (for AC Indicates that only one of the power modules is
only) operational.
Off Indicates that no power module is operational.
Table 86 Chassis LED description

LED type Status Description

Fault Amber Indicates that a Major/Minor alarm is detected on
G30.
Red Indicates that a Critical alarm is detected on G30.
Off Indicates that G30 is power off or administrative
down, or no alarm is detected.
Active Green Indicates that G30 is in service and active.
Flashing green Indicates that G30 is booting.
Off Indicates that G30 is power off.
Red Indicates that ZTC status is in state of failed.
LOC Flashing blue Indicates that the target chassis is located by user
from management system.
Off Indicates that the LED is off.
Table 86 Chassis LED description (Cont.)
Each module has a port LED and a fault LED/active LED on the front panel except OMD
modules which is passive modules so do not have status LED.
Figure 129 CHM Module LEDs on the front panel
Figure 130 OCC2 Module LEDs on the front panel

The CHM/XTM2 module LED status are described in Table 87.

LED type LED status Description

Port Green Indicates that a port or any 10G sub-port within a QSFP+
is active and in service.
Red Indicates that a RUP-MISS/LOS/LOL/LOSYNC/LOF is
detected on a port or any 10G sub-port within a QSFP+.
Off Indicates that a port or all 10G sub-port within a QSFP+
are not provisioned or administrative down.
Fault Amber Indicates that a Major/Minor alarm is detected on a port
or any 10G sub-port within a QSFP+.
Red Indicates that a Critical alarm is detected on a port or any
10G sub-port within a QSFP+.
Off Indicates that the port is power off or administrative
Active Green Indicates that the sled is in service and active.
Flashing Indicates that the sled is booting.
green
Amber Indicates that the sled is in hibernation mode.
Red Indicates that the latch is open and sled is fully down, or
the sled is powered without software provision.
Table 87 CHM/XTM2 Module LED description
The OCC2 module LED status are described in Table 88.

Subslot Green Indicates that a port within the corresponding OFP2 is
active and in service.
Red Indicates that the corresponding OFPs has a RUP_FAIL,
RUP_DEGR, REPLUNIT_MISS, or MEA present.
Flashing Indicates that the corresponding OFP2 on the module is
green booting.
Off Indicates that the corresponding OFP2 is not provi-
sioned or administrative down.
Fault Amber Indicates that a Major/Minor alarm is detected on the cor-
responding OFP2.
Red Indicates that a Critical alarm is detected on the corre-
sponding OFP2.
Off Indicates that the port is powered off or administrative
Table 88 OCC2 Module LED description


Active Green Indicates that the sled is in service and active.
Flashing Indicates that the sled is booting.
green
Amber Indicates that the sled is in hibernation mode.
Red Indicates that the latch is open and sled is fully down, or
the sled is powered without software provision.
Table 88 OCC2 Module LED description (Cont.)
The user can observe the LED status for power modules, fan modules, and RJ45 con-
nections on the back panel.
Figure 131 LEDs on the back panel

The status for the LEDs on the back panel are described in Table 89.


Power Green Indicates that the power output is on and OK.
0.5 Hz blinking Indicates that AC present only 12VSB on or PS in
green smart redundant state.
2 Hz blinking Indicates that the firmware is updating.
green
Amber Indicates that one of the following situation occurs:
• The AC cord is unplugged.
• A power supply critical event is causing a
shutdown.
• A failure, OCP, OVP, Fan Fail, OTP, or UVP
occurs.
0.5 Hz blinking Indicates that one of the following situation occurs:
amber
• The power supply is operating with a warning
event.
• High temperature (PMBus reading inlet
temperature > 54 deg)
• Hot spot temperature (PMBus reading > 105
deg)
• High power or high current
• Slow fan (< 1200 rpm)
Off Indicates that there is no AC power.
Fan Green Indicates that no alarm is detected on fan.
Red Indicates that an alarm is detected on fan.
Off Indicates that the fan is power off.
RJ45 link Green Indicates that a valid connection.
Off Indicates that there is no valid connection.
RJ45 con- Illuminated Indicates that the Ethernet link is up.
nectivity Flashing Indicates that the Ethernet connection is
green/off active/inactive on the common board.
Off Indicates that there is no valid connection.
Table 89 Back panel LED description

User Guide (UG) Appendix A: Ordering guide
8 Appendix A: Ordering guide

This section provides a product list with part numbers and corresponding descriptions.
A space has been provided for order quantity so that you can use this portion of the
document as an ordering guide.
Quantity Part number Product description

Bundle-code Chassis that can be ordered
PSUS GQK-G30FRUDC G30 FRCU CHASSIS with FANs
AND DC PSU
GQK-G30FRUAC G30 FRCU CHASSIS with FANs
AND AC PSU
GQK-G30CRFAC G30 CHASSIS WITH RAILs,
FANs, AND AC PSU
Chassis and required modules
GQS-G30CHASZ-00 G30 chassis
GQS-G30CHASR-00 G30 chassis with sliding rails
(*) GQS-G30CHASF-00 G30 field replaceable controller
unit (FRCU) chassis
(*) GCS-G30FRCUZ-00 G30 field replaceable controller
unit (FRCU)
GPS-G30PSUAC-00 G30 220V AC power module
GPS-G30PSUDC-00 G30 48V DC power module
GPS-G30PSUHV-00 G30 240V DC power module
GFS-G30FANZZ-00 G30 fan module
Coherent modules
GLS-G30CHM1Z-00 G30 CHM1 (4x100G)
GLS-G30CHM2Z-00 G30 CHM2 (40x10G, 10x40G,
4x100G)
GLS-G30CHM2Z-NC G30 CHM2
(40x10G,10x40G,4x100G, no
enc)
GLS-G30CHM1L-00 G30 CHM1LH (4x100G)
GLS-G30CHM2L-00 G30 CHM2L (40x10G, 10x40G,
4x100G)
GLS-G30CHM1G-00 G30 CHM1G (4x100G)
GLS-G30CHM1G-NC G30 CHM1G (4x100G, no enc)
(*) GLS-G30CHM2T-00 G30 CHM2T (12x100G)
GLS-G30OCC2Z-00 G30 OCC2
Table 90 G30 part numbers


GLS-G30CHMFI-00 G30 CHM filter plate
Software
(*) GSS-G3004010-BZ G30 SW FP4.0
Line side pluggable
ZXS-C20TSTZZ-00 CFP2-ACO GHP
ZXS-C2ACOTZZ-00 CFP2-ACO CHP
Client side pluggable 100G
ZXS-Q8S4ZZZZ-00 QSFP28 100G SR4
ZXS-Q8L4ZZZZ-00 QSFP28 100G LR4
ZXS-Q8CWDM4Z-00 QSFP28 100G CWDM4/CLR4
ZXS-Q8PSM4ZZ-00 QSFP28, 100G PSM4
ZXS-Q8L4ZZDR-00 QSFP28 100GBASE-LR4 and
OTU4 Dual Rate
ZXS-Q8S4ZZMR-00 QSFP28 SR4 Multirate(100GbE,
OTU4, 32GFC)
ZXS-Q8FCPSMZ-00 QSFP28 4x8/16GFC, PSM
ZXS-Q8AOCZZZ-03 QSFP28 Active Optical Cable 3m
ZXS-Q8AOCZZZ-10 QSFP28 Active Optical Cable
10m
ZXS-Q8ER4ZZZ-00 QSFP28 ER4 (30km). SMF fiber.
LC connector
ZXS-Q8L4PRDR-00 QSFP28 LR4 DR FPS
ZXS-Q8AOCZDR-01 QSFP28 Active Optical Cable DR
1m
ZXS-Q8AOCZDR-05 QSFP28 Active Optical Cable DR
5m
Client side pluggable 10G/40G
81.71T-Q40GSR4-R6 QSFP+ 40GBE INTERFACE -
100m, 10GBE SR 100m
ZXS-QPL4ZZZZ-00 QSFP+ 40GBE LR 4
ZXS-QPQ10GLW-00 QSFP+ 4x10GBE LR/W PSM
ZXS-QPS4EZZZ-00 QSFP+, 40G eSR4, 10GBase-SR
ZXS-QPI4ZZZZ-00 QSFP+, 40G IR4
81.71T-Q40GLR4-R6 QSFP+, 40GBase-LR4(DR),
OTU3/OTU2/OTU2e/OC192
ZXS-QPE4ZZZZ-00 QSFP+, 40GBase-ER4
Table 90 G30 part numbers (Cont.)


ZXS-QPFCZZMR-00 QSFP+, 4x FC8G, 4x FC16G
81.71T-SP10GLR-R6 SFP+, 10GBASE/8G FC/10G FC-
LR/LW 1310 SM 10KM
81.71T-SP10GSR-R6 SFP+ 10GBASE/8G FC/10G FC-
SR/SW 850 MM 300M
81.71T-SPMRSR1-R6 SFP+, 1310 SM MULTIRATE
SR1 7KM
81.71T-SPDWDM-R6 SFP+, DWDM TUNABLE 88 CH
LR2 80KM
81.71T-SPMRIR1-R6 SFP+, 1310 SM MULTIRATE IR1
20KM
81.71T-SPMRIR2-R6 SFP+, 1550 SM MULTIRATE IR2
40KM
81.71T-SPMRLR2-R6 SFP+, 1550 SM MULTIRATE
LR2 80KM
81.71.SPDWDMHP-R6 SFP+, HIGH POWER SFP+
DWDM TUNABLE 88 CH
ZXS-SP16GFSI-00 4G-8G-16G FC, 125M, MMF
(850NM)
ZXS-SP16GFSL-00 4G-8G-16G FC, 10KM, SMF
(1310NM)
Optical Line System
GLS-G30OMD96-00 G30 OMD96
GLS-G30OMD48-SG G30 OMD48 (standard grid)
GLS-G30XTM2Z-00 G30 XTM2
(*) GQS-OMD64ZZZ-00 OMD64 (2RU)
Optical Line System
81.71T-O2PAOSC-R6 OFP2 PREAMP WITH OSC
81.71T-O2PABA-R6 OFP2 PRE-AMP AND BOOSTER
AMP
81.71T-O2PAOHIR-R6 IR Preamp + OSC Add/Drop,
81.71T-O2PAOHLR-R6 LR Preamp + OSC Add/Drop,
81.71T-O2PAOHER-R6 ER Preamp + OSC Add/Drop,
81.71T-O2BAH-R6 Booster Amplifier OFP2 (BA
OFP2), High Channel Count


ZXS-O2OPS1ZZ-00 Optical Protection Switch Module
O2OPS OFP2
ZXS-O2OMD8B1-00 OFP2 OMD8 Band 1
ZXS-O2OMD8B2-00 OFP2 OMD8 Band 2
ZXS-O2TDCMZZ-00 TDCM (Tunable Dispersion Com-
pensation Module) OFP2
ZXS-O2BAUZZZ-00 OFP2 BOOSTER AMP ULTRA
HIGH POWER
ZXS-O2PAOULR-00 OFP2 PREAMP ULTRA HIGH
POWER LONGER REAC
ZXS-O2OPS1ZZ-00 OFP2 1CH OPS MODULE
ZXS-O2OTDR4Z-00 OFP2 OTDR 4-PORT

(*) ZXS-O2OCMZZZ-00 OFP2 OPTICAL CHANNEL
MONITOR
(*) ZXS-O2CAD8ZZ-00 OFP2 CAD8 Colorless Add/Drop
(*) ZXS-O2CAD8EZ-00 OFP2 CAD8E Colorless
Add/Drop Expandable
Cables
GVS-M8LCOM3Z-03 Breakout cable OM3
MPO(12p)fem to 8LC 3m
GVS-M8LCOM4Z-03 Breakout cable OM4
MPO(12p)fem to 8LC 3m
GVS-M8LCSMZZ-03 Breakout cable SM MPO(12p)fem
to 8LC 3m
GVS-PDCDOZZZ-03 DC power cable spare 14AWG
3M (D-SUB, OE)
ZXS-Q8DACZZZ -03 QSFP28 Direct Attached Cable
3m
GVS-MT8LCSMZ-03 Breakout cable SM MTP(12p)fem
to 8LC 3m
GVS-PC13C14C-03 16 AWG AC Power cable
Installation kit
GKS-G30INKIT-23 G30 Installation Kit (21”/23")1)
GKS-G30INKIT-ET G30 Installation Kit (ETSI)
(*) GKS-G30FRKIT-ET G30 FRCU 19" RACK/CABINET
MOUNTING KIT


(*) GKS-G30FRKIT-23 G30 FRCU 23" RACK/CABINET
MOUNTING KIT
AC power cords
PS402838117246A AC PWR Cable: Type G (Great
Britain), 5 A, 250 V AC
PS402838117253A AC PWR Cable: Type AS3112,
IRAM 2073
(Australia, Argentina, China
10A/240v), 10 A, 250 V AC
PS402839MSK310 AC PWR Cable: Type CEE 7/7
(Europe), 10 A, 250 V AC
PS402839SVT3US AC PWR Cable: Type C13 (CBL
PWR AC US
B C13 2.5M) (North America), 13
A, 125 V AC
PS402838117408 AC PWR Cable: Type I (Italy), 10
A, 250 V AC

1) To install the G30 to a 21-inch equipment rack, use one bracket from the kit 23”
and another bracket from kit 19”.
Modules marked with (*) are newly introduced in this release.
8.1 Basic Commissioning

Basic is used in particular cases like when normal upgrade procedure does not work, it
provides an optional way to install a software load for Groove™ G30.
Preconditions:
• A serial cable (RS232 compliant) connecting from Groove™ G30 to serial terminal.
• A CAT5 Ethernet cable connecting from Groove™ G30 LCI interface to customer
network.
• A FTP server which could be accessed from Groove™ G30’s LCI interface to
download the software image.
g Refer to 4.3.1 Connecting cables for commissioning port for the PIN definition of
serial cable and CAT5 cable.
Steps:
1 Type ‘uboot’ in console terminal to stop the auto-boot. Use the default baud-rate
9600 for serial interface baud-rate.
g If the user needs to perform BC procedure on FP1.0 Groove chassis, the user needs
to use the baud-rate 38400. After BC, the baud-rate of Groove will be changed to
9600 automatically.

2 Enter ‘run bcmode’ in the prompted uboot window, the system will reset to a linux
prompt.
If the subcard is already loaded with a G3.0 or higher release, then:
1. In bcmode, run:
/sbin/mkfs.ext4 /dev/mmcblk0p1
g For FRCU shelf, mmcblk0p1 should be changed to sda1.
2. Reboot by running:
2.1 mkdir /mnt/flashdisk
2.2 mount -t jffs2 -o ro,noatime /dev/mtdblock1
/mnt/flashdisk
2.3 /mnt/flashdisk/init_sys
3. Now the system restarted, do all the things again from step 1 (type "uboot" in
time). Only at this time the sdcard is blanked and you should avoid these 2.x
steps.
3 From the Linux prompt, enter the following commands:

1. mkdir /mnt/flashdisk
2. mount -t jffs2 -o ro,noatime /dev/mtdblock1 /mnt/flashdisk
3. cd /mnt/flashdisk
4 From the /mnt/flashdisk# prompt, enter the following commands to copy the SW
image and execute:
1. /sbin/mkfs.ext4 /dev/mmcblk0p1
2. ./bcm.init
3. ./ed_ip <NE ip address> <NE netmask> LCI <Gateway ip
address>, example of command: ./ed_ip 169.254.0.1 255.255.0.0
LCI 169.254.0.52
4. ./copy_rfile_ext4 <Remote FTP server ip address> 21 <FTP
user name> <FTP password> <SW load path> <SW load name>,
example of command: ./copy_rfile_ext4 169.254.132.138 21 name1
passwd1 dc-GROOVE_G30_3.0.0_20180705
5. ./install_sw
6. rm -f /mnt/sdcard/storage.img; sync
7. ./init_sys
After system restarted, new software image starts to run.

User Guide (UG) Appendix B: Specifications for Optical Pluggable Modules
9 Appendix B: Specifications for Optical Plug-

gable Modules
This section provides the specification tables for each OFP2 pluggable module, and cor-
responding descriptions. The list of table of all Optical Pluggable Modules are as in the
following, the user can click on the name list to link to each table.
• Table 91 Specifications of client side optical pluggable modules
• Table 92 Specifications of line interface with optical pluggable modules GHP and
CHP CFP2-ACO with CHM1/CHM2
• Table 93 Specifications of line interface with optical pluggable modules GHP CFP2-
ACO with CHM1L/CHM2L
• Table 94 Specifications of line interface with optical pluggable modules CHP CFP2-
ACO with CHM1/CHM2
• Table 95 Specifications of line interface with optical pluggable modules GHP CFP2-
ACO with CHM1G
• Table 96 Specifications of line interface with CHM2T part1 (100G-300G)
• Table 97 Specifications of line interface with CHM2T part2 (400G-600G)
• Table 98 Specifications of PAOSC OFP2 amplifier
• Table 99 Specifications of PABA OFP2 amplifier
• Table 100 Specifications of PAIROFP2 amplifier
• Table 101 Specifications of PALROFP2 amplifier
• Table 102 Specifications of PAEROFP2 amplifier
• Table 103 Specifications of BAHOFP2 amplifier
• Table 104 Specifications of PAULROFP2 amplifier
• Table 105 Specifications of BAUOFP2 amplifier
• Table 106 Specifications of TDCM OFP2
• Table 107 Specifications of OTDR OFP2
• Table 108 Specifications of OMD8B1/B2 DWDM filters
• Table 109 Optical channel map of OMD8B1/B2 OFP2 DWDM filters
• Figure 133 Port frequency information of OMD8
• Table 110 Specification of CAD8 OFP2
• Table 111 Specification of CAD8E OFP2
• Table 112 Specification of OCM OFP2
• Table 113 Optical channel map of OCM OFP2
Name Tx (dBm)/ Rx(dBm)/ Wavelength Extinc- Encodi Optical Con- P/N

Per lane Per lane (nm) tion ng Fiber nector Numbe
Ratio Metho Type r
(dB) d
QSFP+, -7.6, +2.4 -9.5, +2.4 850 3 NRZ OM3/O MPO 81.71T-
40GBase- M4 Q40GS
SR4 R4-R6


Ratio Metho Type r
(dB) d
QSFP+, -7, +2.3 -13.7, 1271 3.5 NRZ SMF LC ZXS-
40GBase- +2.3 1291 QPL4Z
LR4 ZZZ-00
1311
1331
QSFP+, -8.2, +0.5 -14.4, 1310 3.5 NRZ SMF MPO ZXS-
4x10GBAS +0.5 QPQ10
E-LR, PSM GLW-
00
QSFP28, -8.4, +2.4 -10.3, 850 2 NRZ OM3/O MPO ZXS-
100GBase- +2.4 M4 Q8S4Z
SR4 ZZZ-00
QSFP28, -4.3, +4.5 -10.6, 1295.56 4 NRZ SMF LC ZXS-
100GBase- +4.5 (231.4TH) Q8L4Z
LR4 1300.05 ZZZ-00
(230.6TH)
1304.58
(229.8TH)
1309.14
(229.0TH)
QSFP28, -2.9, +2.9 -22.1, -4.9 1295.56, 8 NRZ SMF LC ZXS-
100GBase- 1299.02, Q8ER4
ER4 ZZZ-00
1303.54,
1308.09
QSFP28, -9.4, +2.0 -12.66, 1310 3.5 NRZ PSM MPO ZXS-
100G +2.0 Q8PS
PSM4 M4ZZ-
00
QSFP28, -6.5, +2.5 -11.5, 1271 3.5 NRZ SMF LC ZXS-
100G +2.5 1291 Q8CW
CWDM4 DM4Z-
1311 00
1331
QSFP+, -7.3, +1.0 -9.9, -1.0 850 3 NRZ PMM MPO ZXS-
40G eSR4 QPS4E
ZZZ-00
QSFP+, -7.0, +2.3 -11.7, 1271 3.5 NRZ SMF LC ZXS-
40G IR4 +2.3 1291 QPI4Z
ZZZ-00
1311
1331


Ratio Metho Type r
(dB) d
QSFP+, -2.3, +2.3 ETH: 1271 4.5 NRZ SMF LC 81.71T-
40GBase- '-13.7, 1291 Q40GL
LR4, OTU3 +2.3 R4-R6
1311
OTN: 1331
'-10.8,
+2.3
QSFP+, -2.7, +4.5 -21.2, -4.5 1271 5.5 NRZ SMF LC ZXS-
40GBase- 1291 QPE4Z
ER4 ZZZ-00
1311
1331
QSFP+, -3.6, +2.4 -5.6, 0 850 3 NRZ PMM MPO ZXS-
4x8GFC,M QPFCZ
M ZMR-
00
QSFP+, -3.6, +2.4 -8.7, 0 850 3 NRZ PMM MPO ZXS-
4x16GFC, QPFCZ
MM ZMR-
00
QSFP28 ETH: ETH: 1295.56 4 NRZ SMF LC ZXS-
100GBASE '-4.3, +4.5 '-10.6, 1300.05 Q8L4Z
-LR4 and +4.5 1304.58 ZDR-
OTN:
OTU4 Dual 1309.14 00
Rate '-0.6, +4.5 OTN:
'-6.9, +4.0
QSFP28 ETH: ETH: 1295.56 4 NRZ SMF LC ZXS-
LR4 DR '-4.3, +4.5 '-10.6, 1300.05 Q8L4Z
FPS1) +4.5 1304.58 ZDR-
OTN: 1309.14 00
'-0.6, +4.5 OTN:
'-6.9, +4.0
QSFP28 -8.4~+2.4 - 840 100GB NRZ MMF MPO ZXS-
SR4 Multi- 10.3~_2.4 860 E: 2 Q8S4Z
rate(100Gb OTU4: ZMR-
E, OTU4, 3 00
32GFC)


Ratio Metho Type r
(dB) d
QSFP28 -8.4, +1 -13.8, 1260 3.5 NRZ SMF MPO ZXS-
4x8/16GFC +0.5 1360 Q8FCP
, PSM SMZ-
1370
(FC8G) 00
QSFP28 -5,+1 -12, +2 1260
4x8/16GFC 1295
, PSM
1325
(FC16G)
1370
QSFP28 - - - - - - - ZXS-
Active Q8AO
Optical CZZZ-
Cable 3m 03
QSFP28 - - - - - - - ZXS-
Active Q8AO
Optical CZZZ-
Cable 10m 10
QSFP28 - - - - - - - ZXS-
Active Q8AO
Optical CZDR-
Cable DR 01
1m
QSFP28 - - - - - - - ZXS-
Active Q8AO
Optical CZDR-
Cable DR 05
5m
SFP+, -8.2, 0.5 -14.4, - 1260 3.5 NRZ SMF LC 81.71T-
10GBASE/ 12.6 1355 SP10G
8G FC/10G LR-R6
FC-LR/LW
1310 SM
10KM
SFP+, -7.3, -1 -9.9, -11.1 840 3 NRZ MMF LC 81.71T-
10GBASE/ 860 SP10G
8G FC/10G SR-R6
FC-SR/SW
850 MM
300M


Ratio Metho Type r
(dB) d
SFP+, 1310 -6, -1 ETH: 1260 6 NRZ SMF LC 81.71T-
SM MULTI- -14.4 1565 SPMR
RATE SR1 SR1-
OTN:
7KM R6
-11
1) Specification of QSFP28 LR4 DR FPS is similar with QSFP28 100GBASE-LR4 and OTU4 Dual
Rate, the difference is, QSFP28 LR4 DR FPS supports OPS function, while QSFP28 100GBASE-
LR4 and OTU4 Dual Rate does not.
Table 91 Specifications of client side optical pluggable modules

DWDM 100G QPSK 150G 8QAM 200G 16QAM

Laser Class 1 (10mW)
Data rate 15% SD-FEC 120.58 Gbit/s NA NA
Differential
25% SD-FEC 137.36 Gbit/s 206.04 Gbit/s 274.71 Gbit/s
Non-Differen-
tial
Framing OTU4V acc. to OTUC3 (2x OTUC2 (propri-
G.709 150Gbs, pro- etary)
prietary)
Pulse shaping non return-to-zero (NRZ)
Wavelength range 191.30….196.11 THz, tunable
Frequency tuning granularity 100 MHz
Wavelength tuning time Locked operation from any to any wavelength
within 60s
• Transmitter laser turn on: 30s
• Tx off: 150 ms
Absolute wavelength stability 1.8 GHz
(over life & temperature)
ASE contribution at output <38 dB @ 0.1 nm
Side mode suppression ratio > 38 dB reduced relative to carrier
Tx power (settable) min: -2 dBm
typical: 0 dBm
max: 1 dBm
output power stability: ± 1 dB
output polarization state: Pol mux
SBS suppression Not available
Jitter perfor- Acc. ITU
mance G.8251
Polarization tracking perfor- 100 krad/s 50 krad/s 20 krad/s
mance @ 0.2 dB max. OSNR
penalty, max CD, max PMD and
max. PDL
Chromatic dispersion tolerance 280 ns/nm 45 ns/nm 45 ns/nm
Rx input power range -18.0 dBm ….0dBm (1 channel)

-18.0 dBm … +7dBm (multiple channels)
Max input power (non damaging) +17dBm
Receiver reflectance at RS -27 dB


Receiver sync time Electrical power up of receiver: 61 s
Incoming wavelength change: 30 sec
LO frequency offset <2GHz: 10ms
Clock recovery: 30 ms
Dispersion of link & opt. power: 10 ms
Transient performance Power variations of ±10 dB
(50 µs 10/90% rise/fall time)
BER / error floor (post-FEC) < 1e-15
Table 92 Specifications of line interface with optical pluggable modules GHP and
CHP CFP2-ACO with CHM1/CHM2


Laser Class 1M (10mW)
Data rate 25% SD-FEC 137.36 Gbit/s 206.04 Gbit/s 274.71 Gbit/s
Non-Differen-
tial
prietary)
within 60s
• Tx off: 150 ms
typical: 0 dBm
max: 1 dBm
Jitter perfor- Acc. ITU
mance G.8251
max. PDL



Table 93 Specifications of line interface with optical pluggable modules GHP CFP2-
ACO with CHM1L/CHM2L


Data rate 15% SD-FEC 120.58 Gbit/s NA NA
Differential
Non-Differen-
tial
prietary)
Wavelength tunning time Locked operation from any to any wavelength

within 80s
• Tx off: 150 ms
Side mode suppression ratio > 42dB reduced relative to carrier
Tx power (settable) min: 1 dBm min: -1 dBm
typical: 3 dBm typical: 0dBm
max: 4 dBm max: 1 dBm
output power stability: ± 0.5 dB
Jitter performance Acc. ITU G.8251
penalty, CD, max PMD and max.
PDL


Receiver sync time Electrical power up of receiver: 61s
LO frequency offset <2GHz:10ms
Incoming wavelength change:70 sec
Clock recovery:30 ms
Dispersion of link & opt. power:10 ms
Channel power disparity at ≤ 6 dB @ 0 dB penalty
receiver, one adjacent channel
Channel power disparity at ≤ 21 dB @ 2 dB penalty
receiver, all channels
Table 94 Specifications of line interface with optical pluggable modules CHP CFP2-
ACO with CHM1/CHM2
g Values for tx-filter-roll-off/preemphasis should be provisioned as the following accord-

ing with different line modes:
16QAM tx-filter-roll-off 0.8, preemphasis 0.7
8QAM tx-filter-roll-off 0.8, preemphasis 0.9
QPSK tx-filter-roll-off 0.8, preemphasis 0.9
That means, if CHM1/2 port-mode is set as 16QAM, preemphasis should be provi-
sioned as 0.7, and tx-filter-roll-off should be provisioned as 0.8.
If CHM1/2 port-mode is set as 8QAM or QPSK, preemphasis value should be provi-
sioned as 0.9, and tx-filter-roll-off should be provisioned as 0.8. Detailed refer to Figure
132.
Figure 132 DEP-RRC provision value

DWDM 100G QPSK 200G 16QAM

Data rate 15% SD-FEC 120.58 Gbit/s NA
differential
15% SD-FEC 125.52 254.72
Non- Differen- Gbit/s Gbit/s
tial
7% Staircase 111.81 Gbit/s NA
HD-FEC
Differential
7% G.709 111.81 Gbit/s NA
HD-FEC
Differential
Framing OTU4V acc. to G.709 OTUC2 (proprietary)
within 60s
• Tx off: 150 ms
typical: 0 dBm
max: 3 dBm
Polarization tracking perfor- 150 krad/s 25 krad/s
penalty, CD, max PMD and max.
PDL
Chromatic dispersion tolerance 45 ns/nm 27 ns/nm

DWDM 100G QPSK 200G 16QAM

-18.0 dBm … +10 dBm (multiple channels)
Table 95 Specifications of line interface with optical pluggable modules GHP CFP2-
ACO with CHM1G
DWDM 1) 100G QPSK 200G 16QAM 300G SP-

16QAM
Data rate 15% SD-FEC 126.6 Gbit/s 252.8 Gbit/s 378.6 Gbit/s
differential
27% SD-FEC 138.8 Gbit/s 277.6 Gbit/s -
Non- Differen-
tial
Framing OTU4V acc. to OTUC2 (propri- -
G.709 etary)
Tx power (settable in steps of 0.1 min: 3dBm
dB) max: 6dBm
In-band OSNR @0.1 nm
45dB
Out-of-band OSNR @0.1 nm >50dB

output power stability: 1 dB

DWDM 1) 100G QPSK 200G 16QAM 300G SP-

16QAM

(up to 24 channels)
Polarization tracking perfor- 800 krad/s
max. PDL
Receiver sync time 50ms
Channel power disparity at t.b.d
1) There are more combinations of line rate and modulation modes available, which vary in
bandwidth and reach. For a proper network planning CHM2T is covered by our planning
tools.
Table 96 Specifications of line interface with CHM2T part1 (100G-300G)
DWDM 1) 400G 16QAM 500G 32QAM 600G 64QAM

Data rate 15% SD-FEC 504.8 Gbit/s 531.4 Gbit/s -
differential
Non- Differen-
tial
Framing OTUC4 (propri- OTUC5 (propri- OTUC6 (propri-
etary) etary) etary)

DWDM 1) 400G 16QAM 500G 32QAM 600G 64QAM

Tx power (settable in steps of 0.1 min: 3dBm
dB) max: 6dBm
In-band OSNR @0.1 nm
45dB
Out-of-band OSNR @0.1 nm 50dB

output power stability: 1 dB
Rx input power range (up to 24 -18.0 dBm -12.0 dBm -6.0 dBm
channels) ….0dBm (1 ….0dBm (1 ….0dBm (1
channel) channel) channel)
max. PDL
Receiver sync time 50ms t.b.d. t.b.d.
1) There are more combinations of line rate and modulation modes available, which vary in
bandwidth and reach. For a proper network planning CHM2T is covered by our planning
tools.
Table 97 Specifications of line interface with CHM2T part2 (400G-600G)

Parameter Min Max Unit Notes

Operating Frequency 191.325 196.125 THz Exclude Cable ID
Range
Number of Channels 1 96 - -
Total Input Power Range -23 15 dBm Line In
with Gain Flattened Specs
a1)
Total Input Power Range -20 18 dBm Port In

Saturated Output Power c2) 15 16 dBm Measured at Port
Out
Gain Range b 0 18 dBm Measured between
Line In and
Settable Gain Range 0 18 dBm
Port Out
Gain Flatness b3) - +/-0.75 dBm
Noise Figure Gain=18 - 6.0 dBm
b,d4)
Gain=9 - 10.5 dBm
Gain=0 - 21.5 dBm
Steady State Gain Error - +/- 0.5 dBm Includes gain setting
Band accuracy
Gain Stability Band - +/- 0.2 dBm -
Max Excursion - +/- 1.0 dBm -
Max Swing - 1.55 dBm -
Settling Time at 90us Tran- - 1500 us -
sient
Polarization Dependent - 0.3 dBm -
Gain
Table 98 Specifications of PAOSC OFP2 amplifier

1) Items marked as a) are measured at Line In.
2) Items marked as c) are measured at Port Out/Line Out.
3) Items marked as b) are measured between Line In and Port Out.
4) Items marked as d) are defined for settable gain values.

Range
Table 99 Specifications of PABA OFP2 amplifier


Number of Channels 1 96 - Pre-amplifier
1 16 - Booster
Total Input Power Range -33 4 dBm Pre-amplifier
with Gain Flattened Specs -6 9 dBm Booster
a1)
Saturated Output Power c2) 14 15 dBm Pre-amplifier

17 18 dBm Booster
Pre-amplifier Gain Range 10 27 dB Measured between
b3) Line In and
Pre-amplifier Settable Gain 10 27 dB Port Out
Range
Gain Flatness b - +/-0.75 dB
Noise Figure Gain=27 - 6.0 dB
b,d4)
Gain=21 - 8 dB
Gain=15 - 10 dB
Gain=10 - 13 dB
Booster Gain b 8 - dB -
Booster Noise Figure - 6.5 dB -
Steady State Gain Error - +/- 0.5 dB Includes gain setting
Band accuracy
Gain Flatness b - +/-0.75 dB -
Gain Stability Band - +/- 0.2 dB -
Max Excursion - +/- 1.0 dB -
Max Swing - 2 dB -
sient
Polarization Dependent - 0.3 dB -
Gain
Table 99 Specifications of PABA OFP2 amplifier

2) Items marked as c) are measured at Port Out/Line Out.


Range

Total Input Power Range -21 19.8 dBm Line In
a1)

Saturated Output Power c2) 19.8 21.3 dBm Measured at Port
Out
Gain Range b3) 0 18 dB Measured between
Settable Gain Rangee4) 0 18 dB Line In and
Port Out
Noise Figure Gain=18 - 7 dB
b,d5)
Gain=9 - 13.8 dB
Gain=0 - 23 dB
Mid Stage Loss 0 7.5 dB -
Max Power Level at MSA - -6 dB Per channel
Out
Linear tilt correction -3 1 dB Linear tilt correction
Steady State Gain Error - +/-0.5 dBm Includes gain setting
Band accuracy
Max Swing - 1.55 dB -
sient
Gain
Table 100 Specifications of PAIROFP2 amplifier

2) Items marked as c) are measured at Port Out.
4) Items marked as e) includes DCM loss.


Operating Frequency 191.325 196.125 THz Exclude Cable
Range ID

Total Input Power Range -29 5.8 dBm Line In
a1)

Saturated Output Power c2) 19.8 21.3 dBm Measured at
Port Out
Gain Range b3) 14 28 dB Measured
Settable Gain Rangee4) 14 28 dB between Line In
and
Port Out
b,d5)
Gain=20 - 9.0 dB
Gain=14 - 12.0 dB
Out
Linear tilt correction -3 1 dB Full gain range
Steady State Gain Error - +/-0.5 dBm Includes gain
Band setting accuracy
sient
Gain
Table 101 Specifications of PALROFP2 amplifier



Range

Total Input Power Range -38 -5.2 dBm Line In
with Gain Flattened
Specsa1)
Saturated Output Powerc2) 19.8 21.3 dBm Measured at Port Out
Gain Range b3) 25 35 dB Measured between Line
Settable Gain Rangee4) 25 35 dB In and
Port Out
b, d5)
Gain=30 - 7.0 dB
Gain=25 - 8.0 dB
Out
Linear tilt correction -3 0 dB Full gain range
Steady State Gain Error - +/-0.5 dBm Includes gain setting
Band accuracy
sient
Gain
Table 102 Specifications of PAEROFP2 amplifier



Operating Frequency 191.325 196.125 THz Exclude
Range Cable ID
Number of Channels 1 96 - Pre-ampli-

fier
Total Input Power Range -16 16.8 dBm
a1)
Saturated Output Power c2) 20.8 21.3 dBm Line In

Settable Gain Rangeh3) 4 16 dB -
Gain Flatness b4) - +/-0.75 dB -
b,d
Gain=10 - 8.0 dB
Gain=4 - 12.0 dB
Out
Linear tilt correction -3 0 dB Full gain
range
Steady State Gain Error - +/-0.5 dBm Includes
Band gain setting
accuracy
sient
Gain
Table 103 Specifications of BAHOFP2 amplifier

1) Items marked as a) are measured at Port In.
2) Items marked as c) are measured at Line Out.
3) Items marked as h) are measured between Port In and Port PD5 (Line Out assuming
EVOA2=0).
4) Items marked as b) are measured between Port In and Line Out.


Operating Frequency 191.275 196.125 THz Exclude
Range Cable ID
Number of Channels 1 96 - Pre-ampli-

fier
a1)
Total Input Power Rangeb -17 25 dBm Port In

2)
Saturated Output Power c 23 24 dBm Measured at

3) Port Out
Settable Gain Ranged 11.5 19 dB Measured

4) between
Line In and
Gain Flatness(p2p)d - 2 dB
Port Out
d
Gain=15.5 - 11.5 dB
Gain=11.5 - 17.8 dB
Mid Stage Loss 0 5 dB -
Max Power Level at MSA - 8.5 dB Per channel
Out
Steady State Gain Error - +/-0.5 dBm Includes
Band gain setting
accuracy
Max Swing - 2 dB -
sient
Gain
LOS activation time - 300 msec PD16, OSC
Rx
1610nm Input power level -30 3 dBm PD16
1610nm Isolation 60 - dB -
1610nm LOS assert -30 - dBm PD16
Table 104 Specifications of PAULROFP2 amplifier


1610nm LOS de-assert - -27 dBm PD16
Table 104 Specifications of PAULROFP2 amplifier

2) Items marked as b) are measured at Port In.
4) Items marked as d) are between Line In and Port Out.

Operating Frequency 191.325 196.125 THz -
Range
Number of Channels 1 96 -
a1)
Saturated Output Power c2) 24 25 dBm Measured at

Line Out
Settable Gain Rangeh3) 10 22 dB Between
Port In and
PD5 (Line
Out
assuming
EVOA2=0)
Gain Flatness b4) - 2 dB Measured
between
b,g Port In and
Gain=15.5 - 8.8 dB Line Out
Gain=11.5 - 14.7 dB
Steady State Gain Error - +/-0.5 dB Includes
Band gain setting
accuracy
EVOA IL 0.8 dB -
EVOA range 20 dB -
Max Swing - 2 dB -
sient
Table 105 Specifications of BAUOFP2 amplifier


Gain
1610nm Input power level -30 3 dBm PD18
1610nm Isolation 60 - dB -
1610nm LOS assert -30 - dBm PD18
1610nm LOS deassert - -27 dBm PD18
LOS activation time - 300 msec PD18
Table 105 Specifications of BAUOFP2 amplifier

1) Items marked as a) are measured at Port In.
2) Items marked as c) are measured at Line Out.
3) Items marked as h) are measured between Port In and PD5 (Line Out assuming
EVOA2=0).
4) Items marked as b) are measured between Port In and Line Out.
Parameter Value Unit Notes

Wavelength first channel 1529.553 nm -
196.000 THz -
Wavelength last channel 1567.542 nm -
191.250 THz -
Channel spacing 50 GHz -
Number of channels 96 -
Channel grid tuning range ±30 GHz -
Standard dispersion tuning range 0, -40 Km -
Operation bandwidth for standard range ITU ± 13 GHz -
Typical -3 dB Operation bandwidth for 34 GHz -
standard range
Dispersion setting accuracy (standard <2 Km -
range)
G652 Slope Matching Error (standard < 25 ps/nm -
range)
Phase Ripple (standard deviation) (stan- <0.10 rad -
dard range)
Extended dispersion tuning range +5, -80 Km -
Operation bandwidth for extended range C GHz -
Table 106 Specifications of TDCM OFP2

Parameter Value Unit Notes

Typical -3 dB Operation bandwidth for 30 GHz -
extended range
Dispersion setting accuracy (extended <2.5 Km -
range)
G652 Slope Matching Error (extended < 35 ps/nm -
range)
Phase Ripple (standard deviation) <0.13 rad -
(extended range)
Dispersion setting resolution <0.5 Km -
Insertion loss <6 dB -
Insertion loss ripple <1.5 dB -
Inter-channel IL variation <1.5 dB -
PDL <0.3 dB -
PMD <1 ps -
Power Consumption Typical 5, Max 9 W -
Table 106 Specifications of TDCM OFP2
Parameter Value Notes

Wavelength 1591 nm ± 6.5 nm
Pulse width 8 ns to 100 us
Tx peak optical power 2.3 dBm to 10 dBm
Dynamic Range 22.3 dB Measured at:
• Pulse width: 28 us
• Precision measure-
ment speed
• SNR = 1
Event dead zone 3m Event location < 1 km
Attenuation dead zone 6m Event location < 1km
Minimum data resolution 0.4 m The resolution ranges
from 0.4 m to 100 m.
Acquisition time 10 s - 180s The acquisition time
varies upon fiber
lengths and settings of
the measurement
speed.
Table 107 Specifications of OTDR OFP2

Parameter Min Typic Max Units Notes

al
Add/Drop Insertion Loss - 3.2 3.6 dB Within all bands
(IL)
Add/Drop Insertion Loss - - 1.0 - Between eight channels
Flatness
Add/Drop Effective -14 - 14 GHz 0.5dB down, Referenced
Bandwidth to ITU channel center
Add/Drop Adjacent 30 - - dB Referenced to 100GHz
Channel Crosstalk channel spacing
Add/Drop Total Channel 25 - - dB Assuming 8 100GHz
Crosstalk DWDM channels
Out-of-band Suppres- 40 - - dB Assuming out-of-band 32
sion 100GHz channels
Express Insertion Loss - - 0.7 dB -
Express Insertion Loss - - 0.25 - -
Flatness
Express Effective Band- -34 - 34 GHz 0.5dB, referenced to the
width nearest ITU channel
center
Express Adjacent 15 - - dB Referenced to 100GHz
Channel Crosstalk channel
PDL - - 0.2 dB -
Insertion loss at 1510nm - - 1.0 dB -
PMD - - 0.2 ps -
Group delay ripple 30 Any deviation from linear,
Add/Drop ports
5 Express ports
Chromatic dispersion -45 - 45 ps/nm Linear fit, Add/Drop ports

-5 - 5 Express ports
Max input power - - 25 dBm Without damage
Optical Return Loss 30 - - dB Includes Raliegh Back-
scattering
Directivity 50 - - dB -
Table 108 Specifications of OMD8B1/B2 DWDM filters

Parameter Min Max Units Notes

Channel spacing - 3.6 dB Within all bands
Band provision - 1.0 - Between eight channels
Channels per band -14 14 GHz 0.5dB down, Refer-
enced to ITU channel
center
Bands 30 - dB Referenced to 100GHz
channel spacing
Band 1channel centers 25 - dB Assuming 8 100GHz
DWDM channels
Express channels band 40 - dB Assuming out-of-band
1 32 100GHz channels
Band 2 channel centers - 0.7 dB -
Express channels band - 0.25 - -
2 -34 34 GHz 0.5dB, referenced to the
nearest ITU channel
center
Table 109 Optical channel map of OMD8B1/B2 OFP2 DWDM filters
Parameter Typical Max Units Notes

Add/Drop Insertion 9.5 10.7 dB Within all bands.
Loss (IL)
Add/Drop Insertion - 1.0 - Between eight chan-
Loss Flatness nels.
PDL - 0.2 dB -
Table 110 Specification of CAD8 OFP2
Parameter Typical Max Units Notes

Add/Drop Insertion 13 14.2 dB Within all bands.
Loss (IL)
Add/Drop Insertion - 1.0 - Between eight chan-
Loss Flatness nels.
PDL - 0.2 dB -
Table 111 Specification of CAD8E OFP2

Parameter Min Typical Max Units Notes

Port Insertion Loss 1.0 1.2 dB Input to
OCM Input
Insertion Loss Flatness 0.3 0.5 - Across C-

band,
across
four ports
PDL 0.2 dB
Max input power - - 26 dBm
Optical Return Loss - - 30 dB
Directivity - - 50 dB
Input Total 16.3 - -40 dBm
signal power
power
Per 1 - -40
range
channel
power
Table 112 Specification of OCM OFP2

Fixed grid applications
Channel spacing 50 96 channels
First channel center 191.35 THz
Last channel center 196.1 THz
Flex grid applications
Start frequency 191.325 THz
Stop frequency - 196.125 THz
Frequency step 6.25 GHz
Bandwidth resolution 12.5 GHz
Cable ID
Frequency 191.25 THz
Channel bandwidth 100 GHz
Frequency Measurement Accuracy
Table 113 Optical channel map of OCM OFP2


Frequency Measurement -3 3 GHz This defines
Accuracy OCM peak
frequency
measure-
ment accu-
racy, it can be
tested
through
unmodulated
laser with
narrow line-
width
Table 113 Optical channel map of OCM OFP2
Figure 133 Port frequency information of OMD8

User Guide (UG) Glossary
10 Glossary
Alarm An alarm is a management mechanism intended to inform the user that there is a
standing fault condition in the system.
Alarm log An alarm log provides a list of the alarms associated with a managed object, and
provides the following information about each of the alarms:
• the identification of the affected object
• the identification of the failed NE or the NE in which the failed unit resides
• the alarm severity
• the time the event occurred
• the indication whether the alarmed event is service affecting or not
• the location and the affected traffic
Alarm severity Each failure is assigned a severity. The following values are used:
• critical
• major
• minor
• not alarmed
• not reported
Element Manager (EM) can configure the severity which is assigned to each fault cause
by an alarm severity assignment profile. In addition, EM can specify that a fault cause
shall not be alarmed. These fault causes will be blocked, hence do not lead to any LED
alarm indications, log entries or alarm reporting.
Card A card is a plug-in unit that occupies one (or multiple) shelf slots. In G30 there are five
types of cards CHM1/CHM1G, CHM2, XTM2, OMD96/48, and OCC2. These cards
perform specific electrical and/or optical functions within an NE.
Each card has a faceplate with information LEDs and, in most cases, several ports for
interconnection of optical fibers and/or optical interfaces (for example, CFP).
Sub-card A sub-card is a plug-in unit of a card. In G30 there are three types of sub-card, amplifier
OFP2 pluggable modules, protection sub-card O2OPS, DWDM filters OMD8 OFP2
pluggable modules.
Carrier card, e.g. OCC2, has specific LED indicating equipment status for each sub-
card.
Card faceplate All cards are equipped with individual faceplates in order to meet EMI requirements, and
ensure heat dissipation. The card faceplate contains LEDs, and in some cases optical
or electrical interfaces.
Card LEDs Card Light Emitting Diodes (LEDs) are luminous signals that can alert the user to:
• The state of the power supply.
• A card problem that requires card replacement.
• The existence of communication or equipment alarms.
• The presence or absence of traffic in the card.
Card slot A card slot is the insertion facility for a card in a shelf. Each card slot is designed for one
or several particular card types.

C Form-factor Plug- A CFP module is a swappable component mounted at the faceplate of the cards. It acts
gable (CFP) as a boundary interface between the client signal and the DWDM line signal by perform-
ing the bidirectional optical/electrical traffic conversion.
Client interface A client interface is a transponder interface that faces the client side of the link. Contrast
with “line interface” which faces the transmission (line) side of the link.
Ethernet Ethernet is a family of frame-based computer networking technologies for LANs. It

defines a number of wiring and signaling standards for the physical layer, through
means of network access at the MAC/Data Link Layer, and a common addressing
format.
Fan unit Each shelf is equipped 5 fan units that provide cooling airflow for the cards.
Fault management Fault management reports all hardware and software malfunctions within an NE, and
monitors the integrity of all incoming and outgoing digital signals.
Forward Error Cor- FEC is a technique that optimizes signal performance by providing a better Optical
rection (FEC) Signal-to-Noise Ratio (OSNR) tolerance at the transponders, that is, FEC enables the
system to withstand more signal noise.
FEC is a coding algorithm that enables bit error detection and correction. FEC is a "for-
ward" scheme, that is, the receiver receives only the information needed to detect and
correct bit errors and never requests a re-transmission.
Laser safety Laser safety rules are a group of mechanisms and actions necessary to protect all users
from harmful laser light emissions.
Line interface A line interface is a transponder interface that faces the line side of the link. Contrast
with “client interface” which faces the client equipment side of the link.
Network Element An NE is a self-contained logical unit within the network. The NE can be uniquely
(NE) addressed and individually managed via software.
Each NE consists of hardware and software components to perform given electrical and
optical functions within the network.
Optical Signal to OSNR is the ratio of an optical signal power to the noise power in the signal.
Noise Ratio (OSNR)
Performance man- Performance monitoring and signal quality analysis provide information for detecting
agement and alerting, a cause that could lead to a degraded performance before a failure is
declared.
Pluggable Module A pluggable module is a swappable component mounted at the front panel of the cards.
In G30 a pluggable module can be either a CFP or QSFP module.
Power Supply Unit The PSU provides the shelf the necessary electrical power. It converts mains AC to a
(PSU) low-voltage regulated DC power for the shelf internal components.
Quad Small Form- A QSFP module is a swappable component mounted at the front panel of the cards. It
Factor Pluggable acts as a boundary interface between the client signal and the DWDM line signal by per-
(QSFP) forming bidirectional optical/electrical traffic conversion.
Rack A rack is the main unit of the G30, it carries all system devices in a specific arrangement.
The most important elements placed in the rack are the shelves.

Security manage- Security Management controls the individual access to particular NE functions via the
ment network management system and/or via a craft terminal, using a hierarchical security
management user ID, and password concept.
Shelf The rack-mountable housing into which cards are installed. Major components of each
shelf are, power modules, card slots, fan modules, and interface connectors.
TNMS TNMS is an integrated solution designed for large, medium and small size networks. It
supports NEs with DWDM, OTH, SDH, PDH, Ethernet in line, star, ring and mesh
network provisions. TNMS can be used to manage networks in the access, edge, metro,
core and backbone levels.
Wavelength Wavelength is a physical attribute of a wave (for example, an optical wave), defined as
the distance between corresponding points of two consecutive wave cycles.
The wavelength is directly related to the frequency of the wave.
Wrist strap A grounded anti-static strap worn on the wrist to prevent electrostatic discharge that may
damage electronic equipment.

User Guide (UG) Abbreviations
11 Abbreviations
10GBE 10 Gigabit Ethernet
8QAM 8 Quadrature Amplitude Modulation
16QAM 16 Quadrature Amplitude Modulation
AAA Authentication, Authorization, and Accounting
AC Alternating Current
AMP Asynchronous Mapping Procedure
ANSI American National Standards Institute
Bps Bytes per second
bps Bits per second
BMP Bit-synchronous Mapping Procedure
CD Chromatic Dispersion
CE Communauté Européenne
CFP C Form-factor Pluggable
CHP Coriant High-performance Pluggable
CLI Command Line Interface
CRS Cross Connection
DAPI Destination Access Point Identifier
DC Direct Current
DCI Data Center Interconnect
DCN Data Communication Network
DWDM Dense Wavelength Division Multiplexing
EB Error Block
EMC Electromagnetic Compatibility
EMI Electromagnetic Interference
ES Errored Seconds
ESD (1) Eletrostatic Discharge

(2) Electrostatically Sensitive Device
ETSI European Telecommunications Standards Institute

FC Fiber Channel
FEC Forward Error Correction
FIPS Federal Information Processing Standards
FTP File Transfer Protocol
SFTP SSH File Transfer Protocol
GB Gigabyte
Gb Gigabit
GbE Gigabit Ethernet
GBps Gigabytes per second
Gbps Gigabits per second
GCC General Communication Channel
GCM Galois Counter Mode
GFP Generic Framing Procedure
GHP Generic High-performance Pluggable
GMT Greenwich Mean Time
GMP Generic Mapping Procedure
GOPT Generic Optical Section Interface Facility
HTTP Hypertext Transfer Protocol
HU Height Unit
HW Hardware
ICMP Internet Control Message Protocol
ID Identifier
IP Internet Protocol
KB Kilobyte
Kb Kilobit
KBps Kilobytes per second
Kbps Kilobits per second
LAN Local Area Network
LC Line connector
LED Light Emitting Diode
LLDP Link Layer Discovery Protocol
MB Megabyte

Mb Megabit
MBps Megabytes per second
Mbps Megabits per second
NE Network Element
OCh-OS Optical Channel - Optical Signal
OCM Optical channel monitor
ODUk Optical channel Data Unit-k
ODUCn Optical channel Data Unit @ bit rate n x 239/226 x 99532800 Kbit/s
OEM Original Equipment Manufacturer
OEO Optical Electrical Optical
OFP2 Optical Form Factor Pluggable 2
OMD Optical Multiplex/Demultiplex
OMS Optical Multiplex Section
OOS Out of Service
OPSM Optical Protection Switch Module
OS Operating System
OSC Optical supervisory channel
OSNR Optical Signal-to-Noise Ratio
OSPF Open Shortest Path First
OTDR Optical Timer Domain Reflectometer
OTN Optical Transport Network
OTUk Optical Transport Unit-k
PAM Pulse amplitude modulation
PAM4 PAM4 Modulation
PC Personal Computer
PCS Physical Coding Sublayer
PM Performance Management
PSU Power Supply Unit
PSK Pre-shared Key
QSFP Quad Small Form-factor Pluggable
QPSK Quadrature Phase Shift Keying
RAM Random Access Memory

SAPI Source Access Point Identifier
SD Signal Degrade
SF Signal Failure
S-FEC Super Forward Error Correction
SD-FEC Soft Decision Forward Error Correction
SCP Secure Copy Protocol
SES Severely Errored Seconds
SFP Small Form-factor Pluggable
SFTP SSH File Transfer Protocol
SSH Secure Shell
SNMP Simple Network Management Protocol
SU System Unit
SW Software
TB Terabyte
Tb Terabit
TBps Terabytes per second
Tbps Terabits per second
TCA Threshold Crossing Alert
TCP Transmission Control Protocol
TLS Transport Layer Security
TMN Telecommunications Management Network
TNMS Telecommunications Network Management System
TP Termination Point
UAS Unavailable Seconds
VOA Variable Optical Attenuation
WAN Wide Area Network
WDM Wavelength Division Multiplexing
WEEE Waste Electrical and Electronic Equipment
ZTC Zero Touch Configuration

GDM G30fp040!02!0a User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GDM G30fp040!02!0a User Guide

Uploaded by

Copyright:

Available Formats

User Guide (UG)

Revision A, April 2019

Coriant is continually striving to reduce the adverse environmental effects of

Copyright © Coriant 2019. All rights reserved.

GDM-G30FP040-02-0A Page 2 Rev A, April 2019

2 Safety and compliances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 Introduction to the Groove™ G30 DCI Platform . . . . . . . . . . . . . . . . . . 18

4 Hardware installation and startup procedures . . . . . . . . . . . . . . . . . . . . 71

GDM-G30FP040-02-0A Page 3 Rev A, April 2019

4.2.1 Mounting brackets (Applicable only to normal chassis) . . . . . . . . . . . . . 73

5 G30 system configuration and management . . . . . . . . . . . . . . . . . . . . 103

GDM-G30FP040-02-0A Page 4 Rev A, April 2019

5.2.5 Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

GDM-G30FP040-02-0A Page 5 Rev A, April 2019

5.4.13 Log management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

6 Upgrade and maintenance tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

8 Appendix A: Ordering guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

9 Appendix B: Specifications for Optical Pluggable Modules . . . . . . . . . 335

GDM-G30FP040-02-0A Page 6 Rev A, April 2019

1.1 Intended audience

1.2 Structure of this document

Chapter Title Subject

Table 1 Structure of the document

GDM-G30FP040-02-0A Page 7 Rev A, April 2019

1.3 Symbols and conventions

fDANGER! A safety message indicates a dangerous situation where

w NOTICE: A property damage message indicates a hazard that may result

g A note provides important information related to the topic, for

t A tip provides additional information related to the topic which is

Table 2 List of symbols and conventions

GDM-G30FP040-02-0A Page 8 Rev A, April 2019

Table 2 List of symbols and conventions (Cont.)

1.4 History of changes

Issue Issue date Remarks

Table 3 History of change

GDM-G30FP040-02-0A Page 9 Rev A, April 2019

2 Safety and compliances

2.1 Electrostatic discharge precautions

2.2 Fiber optic safety

2.2.1 Laser safety

GDM-G30FP040-02-0A Page 10 Rev A, April 2019

2.2.2 Safety precautions

GDM-G30FP040-02-0A Page 11 Rev A, April 2019

disconnect the optical path from all relevant optical modules

2.2.3 Optical fiber handling

GDM-G30FP040-02-0A Page 12 Rev A, April 2019

• Wash your hands after handling optical fibers.

2.3 Environmental specification

NEBS environment standard Description

Table 4 Environmental Operational Range - AC Groove™ G30

1) Detailed refer to 3.3.4.

GDM-G30FP040-02-0A Page 13 Rev A, April 2019

NEBS environment standard ETSI Environment standard

- GR-63-CORE, 4.1.1 transportation ETSI 300 019-2-1, T1.1, weather

Table 5 Environmental Operational Range - DC Groove™ G30

1) Detailed refer to 3.3.4.

North American Standard GR-3160- European Standard EN 300 386

Table 6 Electromagnetic Compatibility - AC Groove™ G30(EMC)

GDM-G30FP040-02-0A Page 14 Rev A, April 2019

North American Standard GR-3160- European Standard EN 300 386

Table 6 Electromagnetic Compatibility - AC Groove™ G30(EMC) (Cont.)

Description North America standard European standard

Table 7 Health and safety - AC Groove™ G30