Infinera

Infinera DTN and DTN-X
Turn-up and Test Guide
Release 10.0
Version 001
Document ID 1900-001267
V001
Infinera Corporation
140 Caspian Court
Sunnyvale, CA 94089
www.infinera.com
+ 1-408-572-5200
- Please refer to the Infinera Customer Web Portal for the most recent version of this document -
Copyright
© Copyright 2014 Infinera Corporation. All rights reserved.
This Manual is the property of Infinera Corporation and is confidential. No part of this Manual may be reproduced for any purposes or
transmitted in any form to any third party without the express written consent of Infinera.
Infinera makes no warranties or representations, expressed or implied, of any kind relative to the information or any portion thereof
contained in this Manual or its adaptation or use, and assumes no responsibility or liability of any kind, including, but not limited to,
indirect, special, consequential or incidental damages, (1) for any errors or inaccuracies contained in the information or (2) arising
from the adaptation or use of the information or any portion thereof including any application of software referenced or utilized in the
Manual. The information in this Manual is subject to change without notice.
Trademarks
Infinera, Infinera Intelligent Transport Networks, I-PIC, IQ NOS, FlexILS, DTN-X, DTN, ATN and logos that contain Infinera are
trademarks or registered trademarks of Infinera Corporation in the United States and other countries.
All other trademarks in this Manual are the property of their respective owners.
Infinera DTN-X, DTN, and ATN Regulatory Compliance

FCC Class A
This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this device may not cause
harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired
operation. Modifying the equipment without Infinera's written authorization may result in the equipment no longer complying with FCC
requirements for Class A digital devices. In that event, your right to use the equipment may be limited by FCC regulations, and you
may be required to correct any interference to radio or television communications at your own expense.
DOC Class A
This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus as set out in the
interference-causing equipment standard titled “Digital Apparatus," ICES-003 of the Department of Communications.
Cet appareil numérique respecte les limites de bruits radioélectriques applicables aux appareils numériques de Classe A prescrites
dans la norme sur le matériel brouilleur: "Appareils Numériques," NMB-003 édictée par le Ministère des Communications.
Class A ITE
This is a Class A product based on the standard of the VCCI Council. If this equipment is used in a domestic environment, radio
interference may occur, in which case, the user may be required to take corrective actions.
Warning
This is a class A product. In a domestic environment this product may cause radio interference in which case the user may be
required to take adequate measures.
FDA
This product complies with the DHHS Rules 21CFR 1040.10 and 1040.11, except for deviations pursuant to Laser Notice No. 50,
dated June 24, 2007.
Contents
About this Document

Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lv
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lvi
Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lvi
Documents for Release 10.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lix
Release 10.0 New and Updated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxi
Technical Assistance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxvii
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxxi
Chapter 1 - Observing Safety Procedures

Notational Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Safety Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Safety Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
General Safety Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Intra-Building Port Connectivity Warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Jewelry Removal Warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Electrical Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Lifting Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
ESD Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Laser Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Handling Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Chapter 2 - Preparing for Turn-up and Test

Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Infinera Corporation Infinera DTN and DTN-X Turn-up and Test Guide Release 10.0 V001
Infinera Proprietary and Confidential

Page ii Contents
Required Tools and Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
GNM Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Java Web Start Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Installing JRE when internet connectivity is not available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Commissioning Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
IP Address Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Chapter 3 - Turning up a DTN-X as a GNE

DTN-X Main Chassis Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Making a Serial Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Connecting the GNM Terminal to a Craft Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Configuring the GNM Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Verifying Power to the XTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
XTC-10 PEM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
XTC-4 PEM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Powering up the XTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Initial Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Initial Commissioning for the XTC Main Chassis Gateway Network Element (GNE) . . . . . . . . . . . . . . . . . 3-18
Verifying XCM Craft Ethernet Port IP Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Verifying DCN IP Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Launching Infinera GNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Verifying Software Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Setting Up User Accounts with Turn-up and Test Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Configuring Tunable Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Interconnecting the Line Module to BMM OCG Fibers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Verifying Line Module Auto-discovery Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Verifying Optical Carrier Group (OCG) Loss Threshold for Line Modules. . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
Configuring Tunable Line Modules for Open Wave Line System Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Interconnecting the Line Module-to-Line Module OCG Fibers for Open Wave Line System Mode . . . . . . 3-50
Configuring Tunable Line Modules for IGCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
Provisioning the Primary and Secondary GNE IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
Provisioning a Cross-connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55
Verifying OPR and OPT on a Trib Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
Installing the Standby XCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62
Verifying Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63
Testing XTC Circuit Packs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64
Testing TOMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64
Testing TIMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
Testing XICMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
Infinera DTN and DTN-X Turn-up and Test Guide Release 10.0 V001 Infinera Corporation

Contents Page iii
Testing Line Module/OTM-500/OTM2-500s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66

Testing OXMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
Testing TSMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
Testing XCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
Verifying Network Element Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69
Verifying Alarm Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
Configuring Alarm Input/Output Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
Alarm Cutoff (ACO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
Testing an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75
Datawire Service Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
Chapter 4 - Turning up a DTN-X as an SNE

Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Initial Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Initial Commissioning for the XTC Main Chassis Subtending Network Element (SNE) . . . . . . . . . . . . . . . 4-18
Testing TOMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61
Testing TIMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62
Testing XICMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62

Page iv Contents

Testing OXMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63
Testing TSMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
Testing XCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
Alarm Cutoff (ACO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71
Testing an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
Chapter 5 - Turning up an XTC as an Expansion Chassis

XTC Expansion Chassis Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Verifying Power to the XTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
XTC-4 PEM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Initial Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Initial Commissioning for the XTC Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Installing XTC Multi-chassis NC Ethernet Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Dual-chassis Configuration NC Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Multi-chassis Configuration NC Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Creating an Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Configuring DTN-Xs for Preamplifier Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
Minimum Equipment Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62
Testing TOMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
Testing TIMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72
Testing XICMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72

Contents Page v
Testing OXMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73

Testing TSMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74
Testing XCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74
Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76
Alarm Cutoff (ACO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-81
Testing an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82
Chapter 6 - Turning up a DTN-X ROADM Multi-chassis Network Element

DTN-X ROADM Turn-up and Test Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
DTN-X CDC ROADM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Minimum Equipment Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
DTN-X Colorless ROADM Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Minimum Equipment Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Making a Serial Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Connecting the GNM Terminal to a Craft Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Initial Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Initial Commissioning for the XTC Main Chassis Gateway Network Element (GNE) . . . . . . . . . . . . . . . . . 6-21
Initial Commissioning for the XTC Main Chassis Subtending Network Element (SNE) . . . . . . . . . . . . . . . 6-30
Installing XTC Multi-chassis NC Ethernet Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39
Dual-chassis Configuration NC Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40
Configuring Tunable FlexChannel Line Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-66
Interconnecting the Tunable FlexChannel Line Module to FRM/FSM SCh Fibers . . . . . . . . . . . . . . . . . . . 6-69
Creating a Fiber Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-70
Interconnecting the FSP/FMP Fibers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-71

Page vi Contents
Associating the FRM and FSM Ports on the Fiber Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-72
Associating the FRM Ports on the Fiber Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-73
Provisioning an Optical Cross-connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-74
Testing TOMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-84
Testing TIMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-85
Testing XICMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-85
Testing OXMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86
Testing TSMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-87
Testing XCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-87
Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-89
Alarm Cutoff (ACO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-94
Testing an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-95
Chapter 7 - Turning up a FlexILS as a GNE

FlexILS Main Chassis Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Configuring the GNM Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Verifying Power to the MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Powering up the MTC-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Initial Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Initial Commissioning for the MTC-9 Main Chassis Gateway Network Element (GNE) . . . . . . . . . . . . . . . 7-13
Verifying IMM Craft Ethernet Port IP Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Interconnecting Line Side Fibers between Two Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Configuring the Optical Supervisory Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
Verifying the Optical Supervisory Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
Provisioning Fiber Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Verifying Span Loss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35
Installing the Standby IMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
Testing MTC-9 Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40

Contents Page vii
Testing IAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40

Testing IRMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Testing FRMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Testing FSMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
Testing IMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44
Alarm Cutoff (ACO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48
Testing an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49
Chapter 8 - Turning up a FlexILS as an SNE

FlexILS Main Chassis Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Configuring the GNM Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Verifying Power to the MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Powering up the MTC-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Initial Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Initial Commissioning for the MTC-9 Main Chassis Subtending Network Element (SNE) . . . . . . . . . . . . . 8-13
Verifying IMM Craft Ethernet Port IP Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
Testing IAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37
Testing IRMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38
Testing FRMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38
Testing FSMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39
Testing IMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39
Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41

Page viii Contents

Alarm Cutoff (ACO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-45
Testing an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-46
Chapter 9 - Turning up an MTC-9 as an Expansion Chassis

MTC-9 Expansion Chassis Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Verifying Power to the MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Powering up the MTC-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Initial Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Initial Commissioning for the MTC-9 Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Installing MTC-9 Multi-chassis NC Ethernet Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Creating an Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Testing IAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37
Testing IRMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
Testing FRMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
Testing FSMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39
Testing IMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39
Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-41
Alarm Cutoff (ACO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-45
Testing an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-46
Chapter 10 - Turning up a FlexILS ROADM Multi-chassis Network Element

FlexILS ROADM Turn-up and Test Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
FlexILS Colorless ROADM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
FlexILS Main Chassis Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

Contents Page ix
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Configuring the GNM Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
Verifying Power to the MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Powering up the MTC-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
Initial Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
Initial Commissioning for the MTC-9 Main Chassis Gateway Network Element (GNE) . . . . . . . . . . . . . . 10-15
Initial Commissioning for the MTC-9 Main Chassis Subtending Network Element (SNE) . . . . . . . . . . . . 10-24
Verifying IMM Craft Ethernet Port IP Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31
Verifying DCN IP Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
Installing MTC-9 Multi-chassis NC Ethernet Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
Multi-chassis Configuration NC Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
Launching Infinera GNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-46
Verifying Software Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-48
Setting Up User Accounts with Turn-up and Test Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-49
Provisioning the Primary and Secondary GNE IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-51
Installing the Standby IMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-53
Verifying Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-54
Creating a Fiber Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-55
Interconnecting the FSP-E Fibers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-56
Associating the FRM Ports on the Fiber Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-57
Provisioning an Optical Cross-connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-58
Testing MTC-9 Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-63
Testing IAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-63
Testing IRMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-64
Testing FRMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-64
Testing FSMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-65
Testing IMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-65
Verifying Network Element Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-66
Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-67
Verifying Alarm Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-68
Configuring Alarm Input/Output Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-69
Alarm Cutoff (ACO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-71
Testing an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-72
Datawire Service Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-73
Chapter 11 - Turning up a DTN as a GNE

DTN Main Chassis Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Connecting the GNM Terminal to a Craft Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Verifying Power to the DTC/MTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14

Page x Contents
Powering up the DTC/MTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17

Initial Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17
Initial Commissioning for the DTC/MTC Main Chassis Gateway Network Element (GNE). . . . . . . . . . . . 11-18
Verifying MCM Craft Ethernet Port IP Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-27
Verifying DCN IP Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-28
Configuring the Chassis for Mesh Switching Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-36
Entering Expansion BMM Information on a Base BMM2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-39
Interconnecting Line Side Fibers between Two Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-42
Configuring the Optical Supervisory Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-44
Verifying the Optical Supervisory Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-46
Interconnecting Line Module to BMM OCG Fibers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-47
Interconnecting Expansion Fibers between Base and Expansion BMMs . . . . . . . . . . . . . . . . . . . . . . . . . 11-48
Verifying Line Module Auto-discovery Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-49
Configuring Tunable Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-50
Verifying Optical Carrier Group (OCG) Loss Threshold for Line Modules. . . . . . . . . . . . . . . . . . . . . . . . . 11-52
Interconnecting LM-80 to CMM and CMM to BMM OCH/OCG Fibers . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-72
Configuring LM-80 OCH Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-73
Configuring CMM OCG and OCH Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-75
Verifying Optical Carrier Group (OCG) Loss Threshold for CMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-78
Verifying Optical Channel (OCH) Loss Threshold for CMMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-81
Configuring BMM Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-84
Entering DCM/DSE Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-86
Provisioning Fiber Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-87
Entering Span Loss between Adjacent Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-89
Provisioning a Cross-connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-92
Verifying OPR and OPT on a Trib Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-99
Installing the Standby MCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-100
Verifying Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-101
Testing DTC/MTC Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-102
Testing TOMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-102
Testing TAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-103
Testing DICMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-103
Testing GAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-104
Testing BMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-104
Testing CMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-105
Testing Line Module/LM-80/TEMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-105
Testing MCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-106
Verifying Network Element Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-107
Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-108
Verifying Alarm Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-109

Contents Page xi
Configuring Alarm Input Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-109

Configuring Alarm Output Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-113
Alarm Cutoff (ACO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-122
Testing an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-123
Datawire Service Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-124
Chapter 12 - Turning up a DTN as an SNE

DTN Main Chassis Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Initial Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
Initial Commissioning for the DTC/MTC Main Chassis Subtending Network Element (SNE) . . . . . . . . . . 12-17
Verifying MCM Craft Ethernet Port IP Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
Verifying Optical Carrier Group (OCG) Loss Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-48
Installing the Standby MCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-96

Page xii Contents
Testing DTC/MTC Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-98

Testing TOMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-98
Testing TAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-99
Testing DICMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-99
Testing GAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-100
Testing BMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-100
Testing CMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-101
Testing MCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-102
Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-104
Alarm Cutoff (ACO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-118
Testing an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-119
Datawire Service Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-120
Chapter 13 - Turning up a DTC/MTC as an Expansion Chassis

DTC/MTC Expansion Chassis Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Installing DTC/MTC Multi-chassis NCT Ethernet Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Dual-chassis Configuration NCT Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
Multi-chassis Configuration NCT Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
Initial Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
Creating an Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-24
Initial Commissioning for the DTC/MTC Expansion Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26
Verifying Optical Carrier Group (OCG) Loss Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-46

Contents Page xiii

Installing the Standby MCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-92
Configuring DTNs for Preamplifier Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-93
Minimum Equipment Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-94
Testing DTC/MTC Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-112
Testing TOMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-112
Testing TAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-113
Testing DICMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-113
Testing GAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-114
Testing BMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-114
Testing CMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-115
Testing MCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-116
Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-118
Alarm Cutoff (ACO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-132
Testing an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-133
Chapter 14 - Turning up a Network Element for Optical Express

Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Optical Express Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
General Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Optical Express Turn-up and Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
Optical Express Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-20
Power Control Loop Mode for Optical Express OCGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-22
Chapter 15 - Turning up an Optical Amplifier as an SNE

Optical Amplifier Main Chassis Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
Verifying Power to the OTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10
Powering up the OTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12

Page xiv Contents
Initial Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12

Initial Commissioning for the OTC as a Subtending Network Element (SNE). . . . . . . . . . . . . . . . . . . . . . 15-13
Verifying OMM Craft Ethernet Port IP Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-20
Entering DCM/PSE/DSE Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-31
Verifying Span Loss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-34
Installing the Standby OMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-37
Testing OTC Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-39
Testing OMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-39
Testing OAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-40
Testing ORMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-40
Configuring Alarm Input Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-43
Configuring Alarm Output Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-46
Alarm Cutoff (ACO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-50
Testing an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-51
Datawire Service Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-52
Chapter 16 - Turning up an OTC as an Expansion Chassis

OTC Expansion Chassis Turn-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Installing OTC Multi-chassis NCT Ethernet Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4
Multi-chassis Configuration NCT Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Verifying Power to the OTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-11
Powering up the OTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-13
Initial Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-13
Initial Commissioning for the OTC Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-14
Creating an Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-20
Entering DCM/PSE/DSE Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-24
Installing the Standby OMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-25
Configuring Optical Amplifiers for Booster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-26

Contents Page xv
Configuring an OTC with BMM2C and Preamplifier Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-31

Testing OTC Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-37
Testing OMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-37
Testing OAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-38
Testing BMM2Cs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-38
Testing ORMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-39
Testing SCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-39
Testing DSEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-40
Configuring Alarm Input Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-43
Configuring Alarm Output Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-46
Alarm Cutoff (ACO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-50
Testing an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-51
Chapter 17 - Turning up a Multi-chassis Network Element with Raman Amplification (OTC based)
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
Raman Turn-up and Test Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
Tools, Test Equipment, and Fiber Cleaning Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
Fiber Plant Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
Initial Commissioning of Network Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9
Connecting DCM/DSEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9
External Indicators and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
Raman Connector to Software Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
Raman Gain for RAM-1/RAM-2-OR/REM-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
Raman/EDFA Gain and Span Loss Support for ORM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
ORM Maximum Raman Gain vs. Point Loss Offset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-17
Raman Target Gain Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19
Raman Maximum Point Loss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
RAM-1 Turn-up and Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22
RAM-2-OR Turn-up and Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-32
REM-2 Turn-up and Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-41
ORM Turn-up and Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-57
Setting the Point Loss Offset for Raman Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-62
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-63
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-64
Crash Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-65
Additional Abort Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-74
Error and Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-75

Page xvi Contents
Setting the Point Loss Offset for ORM Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-77

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-78
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-79
Setting the Target Gain Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-87
Chapter 18 - Turning up a Multi-chassis Network Element with Raman Amplification (MTC-9 based)
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
IRM Turn-up and Test Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4
Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4
Tools, Test Equipment, and Fiber Cleaning Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
Fiber Plant Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
Initial Commissioning of Network Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
External Indicators and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
Raman/EDFA Gain and Span Loss Support for IRM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
IRM Turn-up and Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9
Setting the Point Loss Offset for IRM Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-16
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-17
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-18
Additional Abort Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-28
Appendix A - Optional Configuration

Configuring the Alarm Severity Assignment Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Configuring the Network Element Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Configuring the Security Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Changing Password at Initial Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Changing Your Account Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Changing the Account Password to the Network Element Default Password . . . . . . . . . . . . . . . . . . . . . A-8
Changing the Password Expiry Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Changing the Maximum Number of Invalid Login Attempts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
Changing the Password History Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Changing the Network Element’s Default Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Changing the Login Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
Configuring the PM Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
Configuring the Enhanced Security Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16
Configuring the Launch Power Offset for BMM/OAM/ORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17
Appendix B - XCM/IMM/MCM/OMM Rebranding Flow

XCM/IMM/MCM/OMM Rebranding Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Contents Page xvii
Appendix C - Connecting and Routing Fiber Optic and BNC Video Cables
Connect and Route XTC Fiber Optic Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Connect and Route MTC-9 Fiber Optic Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-42
Connect and Route FSP/FMP Fiber Optic Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-44
Connect and Route DTC/MTC Fiber Optic and BNC Video Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-51
Connect and Route OTC Fiber Optic Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-91
Appendix D - Raman Fiber Connector Cleaning

Optical Connector Inspection Standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Removing the RAM/ORM/IRM and Identifying Fiber Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Cleaning the Removable Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-9
Cleaning the Non-removable Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12
Cleaning the Client Fiber Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13
Installing the RAM/ORM/IRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-14
Appendix E - Acronyms
List of Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Page xviii Contents

Figures
Figure 1-1 XTC Power Entry Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9

Figure 1-2 MTC-9 Power Entry Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10
Figure 1-3 DTC/MTC Power Entry Module (PEM-70) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10
Figure 1-4 DTC/MTC Power Entry Module (PEM-35) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
Figure 1-5 Warning Labels on Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-15
Figure 3-1 XTC-10 Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
Figure 3-2 XTC-4 Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4
Figure 3-3 Connection Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7
Figure 3-4 Connect To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7
Figure 3-5 COM1 Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8
Figure 3-6 Ethernet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9
Figure 3-7 Local Area Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10
Figure 3-8 TCP/IP Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11
Figure 3-9 Measuring DC Voltage at the PEMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-15
Figure 3-10 Login Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-29
Figure 3-11 Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30
Figure 3-12 Infinera GNM Main View of XTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-31
Figure 3-13 Quick View Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-32
Figure 3-14 About Graphical Node Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-32
Figure 3-15 NE Security Administration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-33
Figure 3-16 Configuring Tunable Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-36
Figure 3-17 Verifying Line Module Auto-discovery Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-39
Figure 3-18 Manually Initiating Line Module Auto-discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-40
Figure 3-19 BMM OCG Port Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-42
Figure 3-20 OLM OCG Port Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-43
Figure 3-21 BMM OCG Port Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-44

Page xx Figures
Figure 3-22 OLM OCG Port Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45

Figure 3-23 Configuring Line System Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Figure 3-24 Provisioned Remote TP Selection Dialog - Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Figure 3-26 Provisioning Peer TP, Target Tx OCG Power, and Channel Count. . . . . . . . . . . . . . . . . . . . . . 3-48
Figure 3-27 Create IGCC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52
Figure 3-28 OLM Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52
Figure 3-29 GNE Network Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Figure 3-30 Create Cross-connect (Home Screen) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Figure 3-31 Create Cross-connect Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57
Figure 3-32 Create Cross-connect: Payload Type Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Figure 3-33 Endpoint Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59
Figure 3-34 Cross-connect Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60
Figure 3-35 Alarm Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
Figure 3-36 Alarm Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69
Figure 3-37 Configure Alarm Input Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
Figure 3-38 Configure Alarm Output Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
Figure 3-39 Network Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Figure 4-1 XTC-10 Front View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Figure 4-2 XTC-4 Front View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Figure 4-3 Connection Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Figure 4-4 Connect To. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Figure 4-5 COM1 Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Figure 4-6 Ethernet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Figure 4-7 Local Area Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Figure 4-8 TCP/IP Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Figure 4-9 Measuring DC Voltage at the PEMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Figure 4-10 Login Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Figure 4-11 Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Figure 4-12 Infinera GNM Main View of XTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Figure 4-13 Quick View Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Figure 4-14 About Graphical Node Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Figure 4-15 NE Security Administration Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Figure 4-16 Configuring Tunable Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Figure 4-17 Verifying Line Module Auto-discovery Completion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Figure 4-18 Manually Initiating Line Module Auto-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Figure 4-19 BMM OCG Port Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39

Figures Page xxi

Figure 5-3 Measuring DC Voltage at the PEMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Figure 5-4 NC Connectivity for Dual-chassis (XTC-to-XTC.MTC-9) with Full XCM Redundancy . . . . . . . . 5-16
Figure 5-5 NC Connectivity for Dual-chassis (XTC-to-DTC/MTC/OTC) with Full XCM Redundancy . . . . . 5-17
Figure 5-6 NC Connectivity for Dual-chassis (XTC-to-XTC/MTC-9) with XCM Redundancy only on
Main Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Figure 5-7 NC Connectivity for Dual-chassis (XTC-to-DTC/MTC/OTC) with XCM Redundancy only on
Main Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Figure 5-8 NC Connectivity for Dual-chassis (XTC-to-XTC/MTC-9) Non-redundant XCMs . . . . . . . . . . . . 5-20
Figure 5-9 NC Connectivity for Dual-chassis (XTC-to-DTC/MTC/OTC) Non-redundant XCMs . . . . . . . . . 5-21
Figure 5-10 NC Connectivity for Multi-chassis (XTC-to-XTC/MTC-9) with Full XCM Redundancy . . . . . . . . 5-23
Figure 5-11 NC Connectivity for Multi-chassis (XTC-to-XTC/MTC-9/DTC/MTC/OTC) with Full XCM
Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Figure 5-12 NC Connectivity for Multi-chassis (XTC-to-XTC/MTC-9) with XCM Redundancy only on
Main Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Figure 5-13 NC Connectivity for Multi-chassis (XTC-to-XTC/MTC-9/DTC/MTC/OTC) with XCM
Redundancy only on Main Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Figure 5-17 Create Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Figure 5-18 Select Chassis Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Figure 5-19 Configuring Tunable Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Figure 5-20 Verifying Line Module Auto-discovery Completion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
Figure 5-21 Manually Initiating Line Module Auto-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40

Page xxii Figures

Figure 5-37 Example Configuration of a DTN-X with an OAM-CXH1-MS Preamplifier and RAM-2-OR . . . . 5-63
Figure 5-38 Setting the DTN-X with OAM-CXH1-MS Preamplifier Association. . . . . . . . . . . . . . . . . . . . . . . 5-64
Figure 5-39 Verifying the DTN-X with OAM-CXH1-MS Preamplifier Association . . . . . . . . . . . . . . . . . . . . . 5-65
Figure 5-40 Setting the RAM-2-OR L1 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67
Figure 5-41 Setting the RAM-2-OR L2 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68
Figure 5-42 Verifying the RAM-2-OR L1 and L2 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69
Figure 6-1 Example Configuration of a DTN-X CDC ROADM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Figure 6-2 Example Configuration of a DTN-X Colorless ROADM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Figure 6-5 Connection Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Figure 6-6 Connect To. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Figure 6-7 COM1 Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Figure 6-8 Ethernet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Figure 6-11 Measuring DC Voltage at the PEMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
Figure 6-12 NC Connectivity for Dual-chassis (XTC-to-XTC.MTC-9) with Full XCM Redundancy . . . . . . . . 6-41
Figure 6-13 NC Connectivity for Dual-chassis (XTC-to-DTC/MTC/OTC) with Full XCM Redundancy . . . . . 6-42
Main Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-43
Main Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44
Figure 6-16 NC Connectivity for Dual-chassis (XTC-to-XTC/MTC-9) Non-redundant XCMs . . . . . . . . . . . . 6-45
Figure 6-17 NC Connectivity for Dual-chassis (XTC-to-DTC/MTC/OTC) Non-redundant XCMs . . . . . . . . . 6-46
Figure 6-18 NC Connectivity for Multi-chassis (XTC-to-XTC/MTC-9) with Full XCM Redundancy . . . . . . . . 6-48
Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-50
Main Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52
Redundancy only on Main Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54

Figures Page xxiii

Figure 6-29 Configuring Tunable FlexChannel Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-68
Figure 6-30 Configuring Encoding Mode and/or Line System Mode on Tunable FlexChannel
Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-68
Figure 6-31 Creating a Fiber Panel (FSP-S) for a DTN-X CDC ROADM Configuration . . . . . . . . . . . . . . . . 6-70
Figure 6-32 Creating a Fiber Panel (FSP-C) for a DTN-X Colorless ROADM Configuration . . . . . . . . . . . . 6-70
Figure 6-33 Associating the FRM and FSM Ports on the Fiber Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-72
Figure 6-34 Associating the FRM Ports on the Fiber Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-73
Figure 6-35 Create Optical Cross-connect (Home Screen). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-74
Figure 6-36 Create Optical Cross-connect (Entering Circuit ID, Label, Source and Destination Endpoints) 6-75
Figure 6-38 Endpoint Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-76
Figure 6-39 Create Optical Cross-connect (Create) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-77
Figure 6-40 Create Optical Cross-connect (Successful Dialog) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-77
Figure 6-41 Cross-connect Manager (Optical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-78
Figure 6-42 Create Optical Cross-connect (Home Screen). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-79
Figure 6-45 Endpoint Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-81
Figure 6-46 Create Optical Cross-connect (Create) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-82
Figure 6-47 Create Optical Cross-connect (Successful Dialog) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-82
Figure 6-48 Cross-connect Manager (Optical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-83
Figure 7-1 MTC-9 Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Figure 7-6 Local Area Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Figure 7-7 TCP/IP Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Figure 7-8 Measuring DC Voltage at MTC-9 PEMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Figure 7-11 Infinera GNM Main View of MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25

Page xxiv Figures

Figure 7-15 OSC Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
Figure 7-16 Connectivity Verification Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
Figure 7-17 Span Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
Figure 8-6 Local Area Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Figure 8-7 TCP/IP Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Figure 8-8 Measuring DC Voltage at MTC-9 PEMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Figure 9-2 Measuring DC Voltage at MTC-9 PEMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Figure 9-3 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9) with Full IMM Redundancy . . . . . . . . . . 9-11
Figure 9-4 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9/OTC) with Full IMM Redundancy . . . . . . 9-13
Figure 9-5 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9) with IMM Redundancy only on
Main Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Figure 9-6 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9/OTC) with IMM Redundancy only on
Main Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Figure 9-7 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9) Non-redundant IMMs . . . . . . . . . . . . . . . 9-19

Figures Page xxv
Figure 9-8 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9/OTC) Non-redundant IMMs . . . . . . . . . . 9-21

Figure 9-12 Create Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Figure 9-13 Select Chassis Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Figure 10-1 Example Configuration of a FlexILS Colorless ROADM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Figure 10-2 MTC-9 Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Figure 10-7 Local Area Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
Figure 10-8 TCP/IP Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
Figure 10-9 Measuring DC Voltage at MTC-9 PEMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Figure 10-10 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9) with Full IMM Redundancy . . . . . . . . . 10-35
Figure 10-11 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9/OTC) with Full IMM Redundancy . . . . . 10-37
Main Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-39
Main Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-41
Figure 10-14 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9) Non-redundant IMMs . . . . . . . . . . . . . . 10-43
Figure 10-15 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9/OTC) Non-redundant IMMs . . . . . . . . . 10-45
Figure 10-16 Login Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-46
Figure 10-17 Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-47
Figure 10-18 Infinera GNM Main View of MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-47
Figure 10-19 Quick View Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-48
Figure 10-20 About Graphical Node Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-48
Figure 10-21 NE Security Administration Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-49
Figure 10-22 GNE Network Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-52
Figure 10-23 Creating a Fiber Panel (FSP-E) for a FlexILS ROADM Configuration . . . . . . . . . . . . . . . . . . . 10-55
Figure 10-24 Associating the FRM Express Ports on the Fiber Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-57
Figure 10-25 Create Optical Cross-connect (Home Screen). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-58
Figure 10-27 Endpoint Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-60
Figure 10-28 Endpoint Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-60

Page xxvi Figures
Figure 10-29 Create Optical Cross-connect (Create) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-61

Figure 10-30 Create Optical Cross-connect (Successful Dialog) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-61
Figure 10-31 Cross-connect Manager (Optical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-62
Figure 10-32 Alarm Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-66
Figure 10-33 Alarm Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-67
Figure 10-34 Configure Alarm Input Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-70
Figure 10-35 Configure Alarm Output Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-71
Figure 10-36 Network Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-73
Figure 11-1 DTC Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Figure 11-2 MTC Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Figure 11-6 Ethernet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Figure 11-9 Measuring DC Voltage at DTC/MTC PEMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-16
Figure 11-12 Infinera GNM Main View of DTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-31
Figure 11-13 Infinera GNM Main View of MTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-32
Figure 11-17 Equipment Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-37
Figure 11-18 Chassis Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-38
Figure 11-19 BMM Properties: Expansion BMM (viewed from base BMM2/BMM2P/BMM2H). . . . . . . . . . . 11-40
Figure 11-20 BMM Properties: Expansion BMM (viewed from expansion BMM2/BMM2P/BMM2H) . . . . . . 11-41
Figure 11-21 OSC Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-44
Figure 11-22 GMPLS Link Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-45
Figure 11-23 Connectivity Verification Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-46
Figure 11-24 Verifying Line Module Auto-discovery Completion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-49
Figure 11-25 Configuring Tunable Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-51
Figure 11-26 BMM OCG Port Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-54
Figure 11-27 DLM OCG Port Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-55
Figure 11-29 GAM OCG Port Properties: BMM-to-GAM (OPT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-57
Figure 11-30 GAM OCG Port Properties: GAM-to-DLM/XLM (OPR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-58

Figures Page xxvii

Figure 11-38 GAM OCG Port Properties: GAM-to-ADLM/AXLM (OPR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-66
Figure 11-44 Locking LM-80 OCH Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-73
Figure 11-45 LM-80 OCH Port Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-74
Figure 11-46 Locking CMM OCG Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-75
Figure 11-47 CMM OCG Port Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-76
Figure 11-48 Locking CMM OCH Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-76
Figure 11-49 CMM OCH Port Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-77
Figure 11-54 BMM Properties: Number of Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-85
Figure 11-55 BMM Properties: Mid Stage Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-86
Figure 11-56 Span Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-88
Figure 11-58 Create Cross-connect (Home Screen) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-93
Figure 11-59 Create Cross-connect Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-95
Figure 11-60 Create Cross-connect: Payload Type Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-96
Figure 11-62 Cross-connect Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-98
Figure 11-63 Alarm Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-107
Figure 11-64 Alarm Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-108
Figure 11-65 Configure Alarm Input Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-113
Figure 11-66 Configure Alarm Output Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-122
Figure 11-67 Network Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-125

Page xxviii Figures

Figure 12-24 Line Module Auto-discovery Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-45

Figures Page xxix

Figure 12-67 Network Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-120
Figure 13-3 NCT Connectivity for Dual-chassis with Full MCM Redundancy . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Figure 13-4 NCT Connectivity for Dual-chassis with MCM Redundancy only on Main Chassis . . . . . . . . . 13-10
Figure 13-5 NCT Connectivity for Dual-chassis Non-redundant MCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11
Figure 13-6 NCT Connectivity for Multi-chassis with Full MCM Redundancy . . . . . . . . . . . . . . . . . . . . . . . 13-13
Figure 13-7 NCT Connectivity for Multi-chassis with MCM Redundancy only on Main Chassis . . . . . . . . . 13-15
Figure 13-13 Create Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-24
Figure 13-14 Select Chassis Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25
Figure 13-15 Expansion Chassis Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-27
Figure 13-23 Line Module Auto-discovery Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-43

Page xxx Figures

Figure 13-61 Example Configuration of a DTN with an OAM Preamplifier . . . . . . . . . . . . . . . . . . . . . . . . . . 13-95
Figure 13-62 Setting the DTN with OAM Preamplifier Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-96
Figure 13-63 Verifying the DTN with OAM Preamplifier Association. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-97
Figure 13-64 Example Configuration of a DTN with an ORM Preamplifier . . . . . . . . . . . . . . . . . . . . . . . . . . 13-99
Figure 13-65 Setting the DTN with ORM Preamplifier Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-101
Figure 13-66 Verifying the DTN with ORM Preamplifier Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-102
Figure 13-67 Example Configuration of a DTN with an OAM-CXH1-MS Preamplifier and RAM-2-OR. . . . 13-103
Figure 13-68 Setting the DTN with OAM-CXH1-MS Preamplifier Association . . . . . . . . . . . . . . . . . . . . . . 13-105
Figure 13-69 Verifying the DTN with OAM-CXH1-MS Preamplifier Association . . . . . . . . . . . . . . . . . . . . . 13-106
Figure 13-70 Setting the RAM-2-OR L1 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-108
Figure 13-71 Setting the RAM-2-OR L2 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-109
Figure 13-72 Verifying the RAM-2-OR L1 and L2 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-110
Figure 14-1 Optical Express in an Intelligent Transport Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
Figure 14-2 Optical Express Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9

Figures Page xxxi
Figure 14-3 Lock BMM OCG Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10

Figure 14-4 Create Optical Express Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-11
Figure 14-5 Verify Optical Express Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-12
Figure 14-6 Verify Optical Express Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13
Figure 14-7 Error Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-16
Figure 14-8 Delete Optical Express Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17
Figure 14-9 Error Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-18
Figure 14-10 Delete Optical Express Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-19
Figure 14-11 Example Configuration of an Optical Express Loop in the Network. . . . . . . . . . . . . . . . . . . . . 14-20
Figure 14-12 Enable Optical Express Route (OER) Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-21
Figure 15-1 Front View OTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Figure 15-7 Measuring DC Voltage at OTC PEMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-11
Figure 15-10 Infinera GNM Main View of OTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-23
Figure 15-16 OAM/ORM Properties: Mid Stage Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-31
Figure 15-22 Configure Alarm Output Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-50
Figure 15-23 Network Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-52
Figure 16-2 NCT Connectivity for Multi-chassis with Full OMM Redundancy . . . . . . . . . . . . . . . . . . . . . . . . 16-6
Figure 16-3 NCT Connectivity for Multi-chassis with OMM Redundancy only on Main Chassis. . . . . . . . . . 16-8
Figure 16-4 NCT Connectivity for Multi-chassis Non-redundant OMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10
Figure 16-5 Measuring DC Voltage at OTC PEMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-12
Figure 16-6 Chassis Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-15
Figure 16-9 Infinera GNM Main View of OTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-19
Figure 16-10 Create Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-20
Figure 16-11 Select Chassis Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-21

Page xxxii Figures

Figure 16-13 OAM/ORM Properties: Mid Stage Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-24
Figure 16-14 Example Configuration of an Optical Amplifier with an OAM Booster . . . . . . . . . . . . . . . . . . . 16-27
Figure 16-15 Setting the Optical Amplifier with an OAM Booster Association . . . . . . . . . . . . . . . . . . . . . . . 16-28
Figure 16-16 Verifying the Optical Amplifier with an OAM Booster Association . . . . . . . . . . . . . . . . . . . . . . 16-29
Figure 16-17 Example Configuration of an OTC with BMM2C and Preamplifier. . . . . . . . . . . . . . . . . . . . . . 16-32
Figure 16-18 Setting the BMM2C with an OAM/ORM Preamplifier Association . . . . . . . . . . . . . . . . . . . . . . 16-34
Figure 16-19 Verifying the BMM2C with an OAM/ORM Preamplifier Association. . . . . . . . . . . . . . . . . . . . . 16-35
Figure 16-23 Configure Alarm Output Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-50
Figure 17-2 Raman Turn-up Order using RAM-1 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Figure 17-3 Raman Turn-up Order using RAM-2-OR Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Figure 17-4 Raman Turn-up Order using RAM-2-OR and REM-2 Modules . . . . . . . . . . . . . . . . . . . . . . . . . 17-6
Figure 17-5 RAM-1 Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
Figure 17-6 RAM-2-OR Faceplate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-11
Figure 17-7 REM-2 Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12
Figure 17-8 ORM-CXH1-MS Faceplate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-13
Figure 17-9 ORM-CXH1 Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
Figure 17-10 ORM-CXH1-MS Maximum Raman Gain vs. Point Loss Offset . . . . . . . . . . . . . . . . . . . . . . . . 17-17
Figure 17-11 ORM-CXH1 Maximum Raman Gain vs. Point Loss Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18
Figure 17-12 Raman Deployment using RAM-1 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22
Figure 17-13 Setting the RAM-1 L1 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-24
Figure 17-14 Setting the RAM-1 L2 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-25
Figure 17-15 Verifying the RAM-1 L1 and L2 Association. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-26
Figure 17-16 Verifying the OSCT Power for RAM-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-28
Figure 17-17 Verifying the ALS Pilot Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-29
Figure 17-18 Raman Deployment using RAM-2-OR Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-32
Figure 17-19 Setting the RAM-2-OR L1 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-34
Figure 17-21 Verifying the RAM-2-OR L1 and L2 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-36
Figure 17-22 Verifying the OSCT Power for RAM-2-OR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-38
Figure 17-24 Raman Deployment using REM-2 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-41
Figure 17-27 Verifying the RAM-2-OR L1 and L2 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-45
Figure 17-28 Selecting the Number of Channels for BMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-46
Figure 17-29 Selecting the Number of Channels for RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-47
Figure 17-30 Setting the REM-2 L1 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-48
Figure 17-31 Verifying the REM-2 L2 Association. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-49
Figure 17-32 Verifying the OSCT Power for RAM-2-OR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-51

Figures Page xxxiii

Figure 17-34 Verifying the Fiber Type for RAM-2-OR L1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-53
Figure 17-35 Verifying the Fiber Type for RAM-2-OR L2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-54
Figure 17-36 Verifying the Fiber Type for REM-2 L1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-55
Figure 17-37 Raman Deployment using ORM Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-57
Figure 17-39 Verifying Neighbor Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-61
Figure 17-40 Example Raman Turn-up Reference Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-66
Figure 17-41 Raman Point Loss Offset (PLO) Adjustment - Initiated through Infinera GNM . . . . . . . . . . . . 17-67
Figure 17-42 Raman Turn-up Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-68
Figure 17-43 RamanPLO.jar File Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-68
Figure 17-44 Warning Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-69
Figure 17-45 Raman Turn-up Tool Introduction Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-69
Figure 17-46 Configuration Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-70
Figure 17-47 Config User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-70
Figure 17-48 Config User - Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-70
Figure 17-49 Configuration Details - Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-71
Figure 17-50 Confirmation Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-71
Figure 17-51 Configuration Details - Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-72
Figure 17-52 Configuration Details - User Abort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-72
Figure 17-53 Configuration Details - Configure User Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-73
Figure 17-54 Confirmation Message - Abrupt Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-74
Figure 17-55 Confirmation Message - Abrupt Close, Start Next Execution . . . . . . . . . . . . . . . . . . . . . . . . . 17-74
Figure 17-56 Example ORM Turn-up Reference Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-80
Figure 17-57 ORM Turnup Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-81
Figure 17-58 Login Details Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-82
Figure 17-61 ORM PLO Adjustment Utility Console Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-83
Figure 17-62 Setting the RAM Target Gain Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-87
Figure 18-1 Front View MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Figure 18-2 IRM-B-ECXH1 Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
Figure 18-3 Raman Deployment using IRM Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9
Figure 18-4 Setting the OSC IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-11
Figure 18-5 Setting the FRM-to-IRM Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12
Figure 18-6 Setting the IRM-to-IRM Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-13
Figure 18-7 Verifying Neighbor Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-15
Figure 18-8 Example IRM Turn-up Reference Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19
Figure 18-9 IRM Point Loss Offset (PLO) Adjustment - Initiated through Infinera GNM . . . . . . . . . . . . . . . 18-20
Figure 18-10 IRM Turn-up Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-21
Figure 18-11 IRMPLO.jar File Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-21
Figure 18-13 IRM Turn-up Tool Introduction Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-22
Figure 18-14 Configuration Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-23

Page xxxiv Figures
Figure 18-15 Config User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-23

Figure 18-16 Config User - Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-24
Figure 18-17 Configuration Details - Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-24
Figure 18-18 Confirmation Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-25
Figure 18-19 Configuration Details - Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-25
Figure 18-20 Configuration Details - User Abort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-26
Figure 18-21 Configuration Details - Configure User Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-27
Figure 18-22 Confirmation Message - Abrupt Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-28
Figure 18-23 Confirmation Message - Abrupt Close, Start Next Execution . . . . . . . . . . . . . . . . . . . . . . . . . 18-28
Figure A-1 Alarm Severity Assignment Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Figure A-2 Password Configurator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Figure A-3 Change Password Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Figure A-4 Reset Password to Default. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Figure A-5 NE Security Administration - Password Expiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Figure A-6 Network Element Wide Security Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
Figure A-7 Change Default Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Figure A-8 Informational Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
Figure A-9 Optical Channel Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Figure A-10 DTF Path: PM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
Figure A-11 NE-Wide Security Settings Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16
Figure A-12 BMM Properties: Configuring the Launch Power Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18
Figure A-13 Warning Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18
Figure B-1 XCM/IMM/MCM/OMM Rebranding Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Figure C-1 Connecting the Fiber Optic Cables to the Optical TOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Figure C-2 Fiber Connections between XTC-10 Line Modules and DTC/MTC BMM/BMM2/BMM2P/
BMM2Hs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11
BMM2Hs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-12
Figure C-4 Fiber Connections between XTC-10 SOLM-500/SOLX-500s and DTC BMM2/BMM2Ps . . . . . C-16
Figure C-5 Fiber Connections between XTC-4 SOLM-500/SOLX-500s and DTC BMM2/BMM2Ps . . . . . . C-17
Figure C-6 Fiber Connections between XTC-10 Line Modules and DTC BMM2/BMM2Ps . . . . . . . . . . . . . C-24
Figure C-7 Fiber Connections between XTC-4 Line Modules and DTC BMM2/BMM2Ps . . . . . . . . . . . . . . C-25
Figure C-8 Fiber Connections between XTC Line Modules Configured for Open Wave Line System
Mode over a Third-party Line System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-27
Mode over a Back-to-Back (Inter-Chassis) Line Module Configuration . . . . . . . . . . . . . . . . . . . C-28
Mode over a Back-to-Back (Intra-Chassis) Line Module Configuration . . . . . . . . . . . . . . . . . . . C-29
Figure C-11 Fiber Connections between XTC FlexChannel Line Modules and MTC-9 FSMs . . . . . . . . . . . C-31
Figure C-12 Fiber Connections between XTC FlexChannel Line Modules and FPC FSP/FMPs . . . . . . . . . C-33
Figure C-13 Example of OTM-500/OTM2-500 Fiber Optic Cable Routing through Fiber Guides . . . . . . . . . C-36
Figure C-14 Example of OTM-500/OTM2-500 Fiber Optic Cable Routing from TIM Sub-slot #4 . . . . . . . . . C-37
Figure C-17 Example of XTC-10 Fiber Optic Cable Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-40

Figures Page xxxv
Figure C-18 Example of XTC-4 Fiber Optic Cable Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-41

Figure C-19 Physically Connecting the Fiber Optic Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-43
Figure C-20 Connecting the Fiber Optic Cables to the FSP/FMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-45
Figure C-21 FSP-E Express Connectivity with FRM-9Ds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-47
Figure C-22 FSP-C Connectivity with FRM-9Ds (for Colorless Add/Drop Configuration) . . . . . . . . . . . . . . . C-48
Figure C-23 FSP-S Connectivity between FRM-9Ds and FSM-8Ds (for CDC Add/Drop Configuration) . . . . C-49
Figure C-24 FMP-C Connectivity with FRM-9Ds (for Colorless Add/Drop Configuration) . . . . . . . . . . . . . . . C-50
Figure C-25 Connecting the Fiber Optic Cables to the Optical TOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-53
Figure C-26 Connecting the BNC Video Cables to the Video TOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-54
Figure C-27 Fiber Connections between DLM/XLMs and BMM/BMM1Hs . . . . . . . . . . . . . . . . . . . . . . . . . . C-57
Figure C-28 Interconnecting the GAM-1 with DLM/XLMs and BMM2/BMM2Hs . . . . . . . . . . . . . . . . . . . . . . C-58
Figure C-29 Fiber Connections between DLM/XLMs and BMM2/BMM2Hs via GAM-1s. . . . . . . . . . . . . . . . C-61
Figure C-30 Fiber Connections between ADLM/AXLMs and BMM/BMM1H/BMM2/BMM2Hs . . . . . . . . . . . C-66
Figure C-31 Interconnecting the GAM-1 with ADLM/AXLMs and BMM2/BMM2Hs . . . . . . . . . . . . . . . . . . . . C-68
Figure C-32 Fiber Connections between ADLM/AXLMs and BMM2/BMM2Hs via GAM-1s . . . . . . . . . . . . . C-72
Figure C-33 Fiber Connections between SLMs and BMM2s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-76
Figure C-34 Interconnecting the GAM-2 with BMM2Ps and ADLM/AXLMs. . . . . . . . . . . . . . . . . . . . . . . . . . C-78
Figure C-35 Fiber Connections between ADLM/AXLMs and BMM2Ps via GAM-2s . . . . . . . . . . . . . . . . . . . C-79
Figure C-36 Fiber Connections between ADLM-80/AXLM-80/SLM-80s, CMMs, and BMMs . . . . . . . . . . . . C-84
Figure C-37 Route the Line Module Fiber Optic Cables through the Fiber Guides . . . . . . . . . . . . . . . . . . . . C-86
Figure C-38 Routing the Fiber Optic Cables through the Bottom Fiber Guide Tray . . . . . . . . . . . . . . . . . . . C-87
Figure C-39 Physically Connecting the Fiber Optic Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-92
Figure C-40 Fiber Connections between XTC-10/XTC-4 Line Modules and OTC BMM2Cs . . . . . . . . . . . . C-103
Figure D-1 Optical Connector End-face Quality Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Figure D-2 RAM-1/RAM-2-OR Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
Figure D-3 REM-2 Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5
Figure D-4 ORM-CXH1-MS Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6
Figure D-5 ORM-CXH1 Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
Figure D-6 IRM-B-ECXH1 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-8
Figure D-7 RAM/ORM/IRM Removable Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-10

Page xxxvi Figures

Tables
Table i New and Updated Features for DTN-X, DTN, Optical Amplifier, and FlexILS Nodes . . . . . . . . . . lxi
Table 1-1 XTC Hardware Compliancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Table 1-2 MTC-9 Hardware Compliancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Table 1-3 DTC/MTC/OTC Hardware Compliancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Table 2-1 Preparation Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Table 2-2 GNM Terminal Hardware Requirements for Oracle Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Table 2-3 GNM Terminal Hardware Requirements for Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Table 2-6 GNM Terminal Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Table 2-4 GNM Terminal Hardware Requirements for Red Hat Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Table 2-5 GNM Terminal Hardware Requirements for Apple Macintosh . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Table 2-7 GNM Terminal Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Table 3-1 DTN-X Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Table 3-2 Supported OCG Loss Threshold between a Line Module and BMM . . . . . . . . . . . . . . . . . . . . 3-41
Table 3-3 Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69
Table 3-4 Expected XTC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
Table 3-5 XTC Alarm Input/Output Connector Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
Table 4-1 DTN-X Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Table 5-1 XTC Expansion Chassis Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Table 5-3 DTN-X Preamplifier Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62

Page xxxviii Tables

Table 6-1 DTN-X Main Chassis Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Table 7-1 FlexILS Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Table 7-3 Expected MTC-9 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
Table 7-4 MTC-9 Alarm Input Contact Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
Table 7-5 MTC-9 Alarm Output Contact Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
Table 8-1 FlexILS Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Table 9-1 MTC-9 Expansion Chassis Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Table 10-1 DTN-X Main Chassis Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Table 10-2 Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-67
Table 10-3 Expected MTC-9 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-68
Table 10-4 MTC-9 Alarm Input Contact Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-69
Table 10-5 MTC-9 Alarm Output Contact Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-69
Table 11-1 DTN Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Table 11-2 BMM Optical Attenuator Pad Requirement for TW-C Fiber Type . . . . . . . . . . . . . . . . . . . . . . 11-43
Table 11-3 Supported OCG Loss Threshold between a Line Module, GAM, and BMM . . . . . . . . . . . . . . 11-53
Table 11-4 Supported OCG Loss Threshold between a CMM and BMM . . . . . . . . . . . . . . . . . . . . . . . . . 11-78
Table 11-5 Supported OCH Loss Threshold between an LM-80 and CMM . . . . . . . . . . . . . . . . . . . . . . . 11-81
Table 11-6 Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-108
Table 11-7 Expected DTC/MTC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-109
Table 11-8 DTC Alarm Input Contact Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-110
Table 11-9 MTC Alarm Input Contact Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-111
Table 11-10 DTC Alarm Output Contact Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-114
Table 11-11 MTC Alarm Output Contact Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-118
Table 12-1 DTN Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

Tables Page xxxix

Table 13-1 DTC/MTC Expansion Chassis Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . 13-5
Table 13-6 DTN Preamplifier Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-94
Table 14-1 Optical Express Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Table 14-2 BMM2C OCG Port Pairing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Table 15-1 Optical Amplifier Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
Table 15-2 Expected OTC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-42
Table 15-3 OTC Alarm Input Contact Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-43
Table 15-4 OTC Alarm Output Contact Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-46
Table 16-1 OTC Expansion Chassis Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Table 16-2 Optical Amplifier Booster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-26
Table 16-3 OTC with BMM2C and Preamplifier Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-31
Table 16-4 Expected OTC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-42
Table 16-5 OTC Alarm Input Contact Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-43
Table 16-6 OTC Alarm Output Contact Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-46
Table 17-1 Raman Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
Table 17-2 RAM-1/RAM-2-OR Connector to Software Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
Table 17-3 REM-2 Connector to Software Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
Table 17-4 RAM Maximum Gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
Table 17-5 ORM Maximum Gain and Span Loss Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
Table 17-6 RAM-1 Target Gain Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19
Table 17-7 RAM-2-OR Target Gain Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Table 17-8 REM-2 Target Gain Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Table 17-9 RAM-1 Maximum Point Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
Table 17-10 RAM-2-OR Maximum Point Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
Table 17-11 REM-2 Maximum Point Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
Table 17-12 Error and Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-75
Table 18-1 Raman Turn-up Checklist and Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
Table 18-2 IRM Maximum Gain and Span Loss Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
Table 18-3 Error and Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-29
Table C-1 XTC Line Module to DTC/MTC BMM/BMM2/BMM2P/BMM2H OCG Port Association . . . . . . . . C-7
Table C-2 XTC SOLM-500/SOLX-500 to DTC BMM2/BMM2P OCG Port Association . . . . . . . . . . . . . . . C-14

Page xl Tables
Table C-3 XTC Line Module to DTC BMM2/BMM2P OCG Port Association . . . . . . . . . . . . . . . . . . . . . . . C-19
Table C-4 FSP/FMP Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-46
Table C-5 DLM/XLM to BMM/BMM1H OCG Port Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-55
Table C-6 DLM/XLM to BMM2/BMM2H via GAM-1 OCG Port Association . . . . . . . . . . . . . . . . . . . . . . . . C-59
Table C-7 ADLM/AXLM to BMM/BMM1H/BMM2/BMM2H OCG Port Association . . . . . . . . . . . . . . . . . . . C-63
Table C-8 ADLM/AXLM to BMM2/BMM2H via GAM-1 OCG Port Association . . . . . . . . . . . . . . . . . . . . . C-69
Table C-9 SLM to BMM2 OCG Port Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-74
Table C-10 CMM to BMM OCG Port Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-81
Table C-11 XTC Line Module to OTC BMM2C OCG Port Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-94
Table D-1 Allowable Defects per Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Procedures
To install JRE on a Microsoft Windows PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

To install JRE on a 64-bit Oracle Solaris platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
To install JRE on a Red Hat Linux platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
To make a serial connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
To connect the Ethernet cable from the craft computer to the target network element . . . . . . . . . . . . . . . . . . . . . . 3-9
To configure the GNM terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
To verify power supply to the XTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
To startup the XTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
To initially commission the Main Chassis of a GNE if the XCM was not commissioned previously . . . . . . . . . . . 3-18
To initially commission the Main Chassis of a GNE if the XCM was commissioned previously . . . . . . . . . . . . . . 3-22
To ping the XCM craft Ethernet port IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
To test the XCM craft Ethernet port IP connection of the target XTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
To ping the DCN IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
To test the DCN IP connection of the target XTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
To launch Infinera GNM using Internet Explorer or Mozilla browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
To verify the software version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
To setup user accounts with turn-up and test privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
To verify and/or configure tunable line modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
To verify line module Auto-discovery completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
To manually initiate line module Auto-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
To verify OCG loss threshold for a line module to BMM (set to Gen 1 mode) interconnection . . . . . . . . . . . . . . . 3-42
To verify OCG loss threshold for a line module to BMM2/BMM2P/BMM2H/BMM2C interconnection . . . . . . . . . 3-44
To configure tunable line modules for Open Wave line system mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
To configure tunable line modules for IGCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
To provision a cross-connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55
To verify OPR and OPT on a Trib port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61

Page xlii Procedures
To install the standby XCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62

To verify equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63
To verify termination points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63
To test a TOM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64
To test a TIM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
To test an XICM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
To test a line module/OTM-500/OTM2-500 with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
To test an OXM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
To test a TSM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
To test an XCM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
To view Network Element Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
To configure Alarm Input Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
To configure Alarm Output Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
To enable an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75
To test an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75
To turn up Datawire Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
To startup the XTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
To initially commission the Main Chassis of an SNE if the XCM was not commissioned previously . . . . . . . . . . . 4-19
To initially commission the Main Chassis of an SNE if the XCM was commissioned previously . . . . . . . . . . . . . . 4-21
To verify line module Auto-discovery completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
To verify OCG loss threshold for a line module to BMM2/BMM2P/BMM2H/BMM2C interconnection . . . . . . . . . . 4-41
To verify OPR and OPT on a Trib port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58

Procedures Page xliii

To enable an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
To test an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
To verify power supply to the XTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
To initially commission the Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) with full XCM redundancy . . . . . . . . . . . . . . . . . . . 5-15
To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) with full XCM redundancy . . . . . . . . . . . . . . . . 5-17
To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) with XCM redundancy only on Main Chassis . . . . 5-18
To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) with XCM redundancy only on Main Chassis . 5-19
To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) non-redundant XCMs . . . . . . . . . . . . . . . . . . . . . . 5-20
To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) non-redundant XCMs . . . . . . . . . . . . . . . . . . . 5-21
To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9) with full XCM redundancy . . . . . . . . . . . . . . . . . . 5-22
To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9/DTC/MTC/OTC) with full XCM redundancy . . . . . 5-24
To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9) with XCM redundancy only on Main Chassis . . . 5-26
To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9/DTC/MTC/OTC) with XCM redundancy only on
Main Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
To create an Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
To verify line module Auto-discovery completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
To verify OCG loss threshold for a line module to BMM2/BMM2P/BMM2H/BMM2C interconnection . . . . . . . . . . 5-44
To turn up a DTN-X with an OAM-CXH1-MS preamplifier and RAM-2-OR configuration . . . . . . . . . . . . . . . . . . . 5-62

Page xliv Procedures

To enable an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82
To test an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82
To make a serial connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
To connect the Ethernet cable from the craft computer to the target network element . . . . . . . . . . . . . . . . . . . . . 6-12
To initially commission the Main Chassis of a GNE if the XCM was not commissioned previously . . . . . . . . . . . 6-21
To initially commission the Main Chassis of a GNE if the XCM was commissioned previously . . . . . . . . . . . . . . 6-25
To initially commission the Main Chassis of an SNE if the XCM was not commissioned previously . . . . . . . . . . . 6-31
To initially commission the Main Chassis of an SNE if the XCM was commissioned previously . . . . . . . . . . . . . . 6-33
To test the DCN IP connection of the target XTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38
To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) with full XCM redundancy . . . . . . . . . . . . . . . . . . . 6-40
To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) with full XCM redundancy . . . . . . . . . . . . . . . . 6-42
To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) with XCM redundancy only on Main Chassis . . . . 6-43
To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) with XCM redundancy only on Main Chassis . 6-44
To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) non-redundant XCMs . . . . . . . . . . . . . . . . . . . . . . 6-45
To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) non-redundant XCMs . . . . . . . . . . . . . . . . . . . 6-46
To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9) with full XCM redundancy . . . . . . . . . . . . . . . . . . 6-47
To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9/DTC/MTC/OTC) with full XCM redundancy . . . . . 6-49
To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9) with XCM redundancy only on Main Chassis . . . 6-51
To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9/DTC/MTC/OTC) with XCM redundancy only on
Main Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-53
To verify and/or configure tunable FlexChannel line modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-66
To associate the FRM add/drop (system) and FSM (line) ports on the Fiber Panel . . . . . . . . . . . . . . . . . . . . . . . 6-72
To associate the FRM add/drop ports on the Fiber Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-73
To provision an optical cross-connect from an FSM tributary port to an FRM line port . . . . . . . . . . . . . . . . . . . . . 6-74
To provision an optical cross-connect from an FRM system port to an FRM line port . . . . . . . . . . . . . . . . . . . . . 6-79

Procedures Page xlv

To enable an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-95
To test an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-95
To configure the GNM terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
To verify power supply to the MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
To startup the MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
To initially commission the Main Chassis of a GNE if the IMM was not commissioned previously . . . . . . . . . . . . 7-13
To initially commission the Main Chassis of a GNE if the IMM was commissioned previously . . . . . . . . . . . . . . . 7-17
To ping the IMM craft Ethernet port IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
To test the IMM craft Ethernet port IP connection of the target MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
To test the DCN IP connection of the target MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
To connect Nodes A and B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
To configure the OSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
To verify OSC connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
To provision fiber information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
To verify span loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35
To install the standby IMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
To test an IAM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
To test an IRM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
To test an FRM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
To test an FSM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
To test an IMM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
To enable an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49
To test an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49

Page xlvi Procedures
To configure the GNM terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8

To verify power supply to the MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
To startup the MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
To initially commission the Main Chassis of an SNE if the IMM was not commissioned previously . . . . . . . . . . . 8-14
To initially commission the Main Chassis of an SNE if the IMM was commissioned previously . . . . . . . . . . . . . . 8-16
To ping the IMM craft Ethernet port IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
To test the IMM craft Ethernet port IP connection of the target MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
To enable an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-46
To test an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-46
To verify power supply to the MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
To startup the MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
To initially commission the Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
To connect NC cables for multi-chassis (MTC-9-to-MTC-9) with full IMM redundancy . . . . . . . . . . . . . . . . . . . . . 9-10
To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) with full IMM redundancy . . . . . . . . . . . . . . . . . 9-12
To connect NC cables for multi-chassis (MTC-9-to-MTC-9) with IMM redundancy only on Main Chassis . . . . . . 9-14
To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) with IMM redundancy only on Main Chassis . . 9-16
To connect NC cables for multi-chassis (MTC-9-to-MTC-9) non-redundant IMMs . . . . . . . . . . . . . . . . . . . . . . . . 9-18
To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) non-redundant IMMs . . . . . . . . . . . . . . . . . . . . 9-20
To create an Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24

Procedures Page xlvii

To enable an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-46
To test an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-46
To configure the GNM terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
To verify power supply to the MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
To startup the MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
To initially commission the Main Chassis of a GNE if the IMM was not commissioned previously . . . . . . . . . . . 10-15
To initially commission the Main Chassis of a GNE if the IMM was commissioned previously . . . . . . . . . . . . . . 10-19
To initially commission the Main Chassis of an SNE if the IMM was not commissioned previously . . . . . . . . . . 10-25
To initially commission the Main Chassis of an SNE if the IMM was commissioned previously . . . . . . . . . . . . . 10-27
To ping the IMM craft Ethernet port IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31
To test the IMM craft Ethernet port IP connection of the target MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31
To ping the DCN IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
To test the DCN IP connection of the target MTC-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
To connect NC cables for multi-chassis (MTC-9-to-MTC-9) with full IMM redundancy . . . . . . . . . . . . . . . . . . . . 10-34
To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) with full IMM redundancy . . . . . . . . . . . . . . . . 10-36
To connect NC cables for multi-chassis (MTC-9-to-MTC-9) with IMM redundancy only on Main Chassis . . . . . 10-38
To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) with IMM redundancy only on Main Chassis . 10-40
To connect NC cables for multi-chassis (MTC-9-to-MTC-9) non-redundant IMMs . . . . . . . . . . . . . . . . . . . . . . . 10-42
To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) non-redundant IMMs . . . . . . . . . . . . . . . . . . . 10-44
To launch Infinera GNM using Internet Explorer or Mozilla browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-46
To verify the software version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-48
To setup user accounts with turn-up and test privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-49
To install the standby IMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-53
To verify equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-54
To verify termination points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-54
To associate the FRM express ports on the Fiber Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-57
To provision an optical cross-connect from an FRM line port to an FRM line port . . . . . . . . . . . . . . . . . . . . . . . 10-58
To test an IAM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-63
To test an IRM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-64
To test an FRM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-64

Page xlviii Procedures
To test an FSM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-65

To test an IMM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-65
To view Network Element Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-66
To configure Alarm Input Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-70
To configure Alarm Output Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-71
To enable an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-72
To test an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-72
To turn up Datawire Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-73
To connect the Ethernet cable from the craft computer to the target network element . . . . . . . . . . . . . . . . . . . . 11-11
To verify power supply to the DTC/MTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14
To startup the DTC/MTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17
To initially commission the Main Chassis of a GNE if the MCM was not commissioned previously . . . . . . . . . . 11-18
To initially commission the Main Chassis of a GNE if the MCM was commissioned previously . . . . . . . . . . . . . 11-22
To ping the MCM craft Ethernet port IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-27
To test the MCM craft Ethernet port IP connection of the target DTC/MTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-27
To ping the DCN IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-28
To test the DCN IP connection of the target DTC/MTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-28
To configure the chassis for Mesh switching mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-36
To enter the expansion BMM information on a base BMM2/BMM2P/BMM2H . . . . . . . . . . . . . . . . . . . . . . . . . . 11-39
To connect Nodes A and B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-42
To configure the OSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-44
To verify OSC connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-46
To verify and/or configure tunable line modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-50
To verify OCG loss threshold for a Gen 1 system (DLM/XLM to BMM/BMM1H) . . . . . . . . . . . . . . . . . . . . . . . . . 11-54
To verify OCG loss threshold for a Gen 1 system (DLM/XLM to BMM2/BMM2H via GAM-1) . . . . . . . . . . . . . . . 11-56
To verify OCG loss threshold for a Gen 1 system (ADLM/AXLM [Gen 1 mode] to BMM/BMM1H) . . . . . . . . . . . 11-60
To verify OCG loss threshold for a Gen 2 system (ADLM/AXLM [Gen 2 mode] to BMM2/BMM2H) . . . . . . . . . . 11-62
To verify OCG loss threshold for a Gen 2 system (ADLM/AXLM [Gen 1 mode] to BMM2/BMM2H via GAM-1) . 11-64
To verify OCG loss threshold for a Gen 2 system (ADLM/AXLM [Gen 2 mode] to BMM2P via GAM-2) . . . . . . . 11-68
To verify and/or configure LM-80 OCH ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-73
To verify and/or configure CMM OCG and OCH ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-75
To verify OCG loss threshold between a CMM and BMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-79
To verify OCH loss threshold between an LM-80 and CMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-82
To configure the channels on a BMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-84
To enter DCM/DSE information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-86
To provision fiber information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-87
To enter Span Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-89
To provision a cross-connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-92

Procedures Page xlix

To install the standby MCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-100
To verify equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-101
To verify termination points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-101
To test a TOM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-102
To test a TAM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-103
To test a DICM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-103
To test a GAM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-104
To test a BMM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-104
To test a CMM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-105
To test a line module/LM-80/TEM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-105
To test an MCM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-106
To view Network Element Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-107
To configure Alarm Input Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-113
To configure Alarm Output Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-122
To enable an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-123
To test an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-123
To turn up Datawire Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-124
To connect the Ethernet cable from the craft computer to the target network element . . . . . . . . . . . . . . . . . . . . 12-10
To initially commission the Main Chassis of an SNE if the MCM was not commissioned previously . . . . . . . . . 12-18
To initially commission the Main Chassis of an SNE if the MCM was commissioned previously . . . . . . . . . . . . 12-20
To ping the MCM craft Ethernet port IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
To test the MCM craft Ethernet port IP connection of the target DTC/MTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24

Page l Procedures

To install the standby MCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-96
To verify termination points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-97
To test a TOM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-98
To test a TAM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-99
To test a DICM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-99
To enable an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-119
To test an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-119
To turn up Datawire Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-120
To connect NCT cables for dual-chassis with full MCM redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
To connect NCT cables for dual-chassis with MCM redundancy only on Main Chassis . . . . . . . . . . . . . . . . . . . 13-10
To connect NCT cables for dual-chassis non-redundant MCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11
To connect NCT cables for multi-chassis with full MCM redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
To connect NCT cables for multi-chassis with MCM redundancy only on Main Chassis . . . . . . . . . . . . . . . . . . 13-14
To create an Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-24
To initially commission the Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26

Procedures Page li
To install the standby MCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-92
To turn up a DTN with an OAM preamplifier configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-94
To turn up a DTN with an ORM preamplifier configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-99
To turn up a DTN with an OAM-CXH1-MS preamplifier and RAM-2-OR configuration . . . . . . . . . . . . . . . . . . . 13-103
To test a TOM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-112
To test a TAM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-113
To test a DICM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-113
To enable an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-133
To test an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-133
To create a Gen 1 BMM-to-BMM Optical Express connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10
To create a Gen 2 BMM-to-BMM Optical Express connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13
To connect fiber optic cables for a Gen 1/Gen 2 Optical Express connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15
To remove a Gen 1 BMM-to-BMM Optical Express connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-16
To remove a Gen 2 BMM-to-BMM Optical Express connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-18
To enable Optical Express route loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-20
To verify power supply to the OTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10
To startup the OTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
To initially commission the chassis as an SNE if the OMM was not commissioned previously . . . . . . . . . . . . . . 15-14

Page lii Procedures
To initially commission the chassis as an SNE if the OMM was commissioned previously . . . . . . . . . . . . . . . . . 15-16
To ping the OMM craft Ethernet port IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-20
To test the OMM craft Ethernet port IP connection of the target OTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-20
To enter DCM/PSE/DSE information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-31
To verify span loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-34
To install the standby OMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-37
To test an OMM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-39
To test an OAM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-40
To test an ORM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-40
To enable an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-50
To test an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-51
To turn up Datawire Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-52
To connect NCT cables for multi-chassis with full OMM redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
To connect NCT cables for multi-chassis with OMM redundancy only on Main Chassis . . . . . . . . . . . . . . . . . . . 16-7
To connect NCT cables for multi-chassis non-redundant OMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9
To verify power supply to the OTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-11
To startup the OTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-13
To initially commission the Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-14
To create an Expansion Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-20
To enter DCM/PSE/DSE information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-24
To install the standby OMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-25
To turn up an Optical Amplifier with an OAM booster configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-27
To turn up an OTC with a BMM2C and OAM/ORM preamplifier configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 16-32
To test an OMM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-37
To test an OAM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-38
To test a BMM2C with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-38
To test an ORM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-39
To test an SCM with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-39
To test a DSE with an equipment failure alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-40

Procedures Page liii

To enable an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-50
To test an ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-51
To turn up a RAM-1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-23
To turn up a RAM-2-OR configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-33
To turn up a REM-2 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-42
To turn up an ORM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-58
To set the point loss offset for Raman modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-66
To set the point loss offset for ORM modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-80
To turn up an IRM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10
To set the point loss offset for IRM modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19
To edit the Alarm Severity Assignment Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
To set the date and time using the external NTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
To configure the date and time manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
To change the password at initial login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
To change your own password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
To change the user password to the default password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
To change the expiry period of the password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
To change the count of maximum number of login attempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
To change the password history count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
To reset network element password to the default password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
To edit the login banner text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
To change the threshold values for a line module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
To change the threshold values for a TOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
To enable SSHv2-based security for the network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16
To configure the launch power offset for a BMM, OAM, and/or ORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17
To connect the TOM port fiber optic cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
To connect OCG cables between XTC line modules and DTC/MTC BMM/BMM2/BMM2P/BMM2Hs . . . . . . . . . . C-6
To connect OCG cables between XTC SOLM-500/SOLX-500s and DTC BMM2/BMM2Ps . . . . . . . . . . . . . . . . . C-13
To connect OCG cables between XTC line modules and DTC BMM2/BMM2Ps . . . . . . . . . . . . . . . . . . . . . . . . . C-18
To connect OCG cables between XTC line modules configured for Open Wave line system mode . . . . . . . . . . . C-26
To connect SCh cables between XTC FlexChannel line modules and MTC-9 FSMs . . . . . . . . . . . . . . . . . . . . . . C-30
To connect SCh cables between XTC FlexChannel line modules and FPC FSP/FMPs . . . . . . . . . . . . . . . . . . . . C-32
To route the OCG/SCh and tributary port fiber optic cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-34
To connect and route the fiber optic cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-42
To connect the fiber optic cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-44
To connect the line module/TEM tributary port fiber optic cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-52
To connect the line module/TEM tributary port BNC video cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-54
To connect OCG cables between DLM/XLMs and BMM/BMM1Hs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-55
To connect OCG cables between DLM/XLMs and BMM2/BMM2Hs (with GAM-1s) . . . . . . . . . . . . . . . . . . . . . . . C-58
To connect OCG cables between ADLM/AXLMs and BMM/BMM1H/BMM2/BMM2Hs (without GAMs) . . . . . . . . C-62
To connect OCG cables between ADLM/AXLMs and BMM2/BMM2Hs (with GAM-1s) . . . . . . . . . . . . . . . . . . . . C-67
To connect OCG cables between SLMs and BMM2s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-73
To connect OCG cables between ADLM/AXLMs and BMM2Ps (with GAM-2s) . . . . . . . . . . . . . . . . . . . . . . . . . . C-77

Page liv Procedures
To connect OCH and OCG cables between ADLM-80/AXLM-80/SLM-80s, CMMs, and BMMs . . . . . . . . . . . . . . C-80
To route the OCG and tributary port fiber optic cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-85
To connect expansion fiber cables between a base and expansion BMM2 (160-channel systems) . . . . . . . . . . . C-88
To connect expansion fiber cables between a base and expansion BMM2P (160-channel systems) . . . . . . . . . C-88
To connect expansion fiber cables between a base and expansion BMM2H (80-channel systems) . . . . . . . . . . C-89
To connect line side fiber cables to the DTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-89
To connect line side fiber cables between two DTNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-90
To connect line side fiber cables from the DTN to an Optical Amplifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-90
To connect and route the OAM/ORM fiber optic cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-91
To connect the OSC jumper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-92
To connect OCG cables between XTC line modules and OTC BMM2Cs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-93
To remove the RAM/ORM/IRM and identify the fiber connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
To clean the removable connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-9
To clean the non-removable connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12
To clean the client fiber connector(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13
To install the RAM/ORM/IRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-14

About this Document
This chapter provides an overview of the Infinera DTN and DTN-X Turn-up and Test Guide in the following
sections:
“Objective” on page lv
“Audience” on page lvi
“Document Organization” on page lvi
“Documents for Release 10.0” on page lix
“Release 10.0 New and Updated Features” on page lxi
“Technical Assistance” on page lxvii
“Documentation Feedback” on page lxxi
Objective
This guide provides the turn up and test procedures for a newly installed Infinera Intelligent Transport
Network™. The Infinera Intelligent Transport Network is comprised of the Infinera® DTN-X™, Infinera
FlexILS™, Infinera DTN®, and Infinera Optical Amplifier network elements.
Note: This guide assumes that the network elements being turned up are not part of a live net-
work. Refer to the Infinera DTN and DTN-X Task Oriented Procedures Guide for routine
tasks involving previously installed and turned up network elements.

Page lvi About this Document
Audience
This guide is written for field installation personnel responsible for turning up and testing the Infinera
DTN-X, FlexILS, DTN, and Optical Amplifier network elements. This guide assumes that the reader is
familiar with:
 Basic internet and networking terminology and concepts, and DWDM technology and concepts
 Electrostatic Discharge (ESD) and the effect it has on electronic components and circuitry
 Basic safety procedures while working with electrical, electronic, and optical systems and equipment
 Test equipment used to turn up the DWDM systems
Document Organization
The following table lists and describes the chapters and appendices within this guide.
Chapter Description
CHAPTER 1: Provides safety information that must be followed while turning up the
Infinera DTN-X, FlexILS, DTN, and Optical Amplifier network elements.
“Observing Safety Procedures“
CHAPTER 2: Lists the necessary tools and equipment used to turn up and test the
Infinera DTN-X, FlexILS, DTN, and Optical Amplifier network elements.
“Preparing for Turn-up and Test“
CHAPTER 3: Provides procedures to turn up and test the Infinera DTN-X as a
Gateway Network Element (GNE).
“Turning up a DTN-X as a GNE“
Subtending Network Element (SNE).
“Turning up a DTN-X as an SNE“
CHAPTER 5: Provides procedures to turn up and test the XTC as an Expansion
Chassis.
“Turning up an XTC as an Expan-
sion Chassis“
colorless, directionless, and contentionless (CDC) or colorless
“Turning up a DTN-X ROADM
Reconfigurable Optical Add/Drop Multiplexer (ROADM) multi-chassis
Multi-chassis Network Element“ network element.
CHAPTER 7: Provides procedures to turn up and test the Infinera FlexILS as a GNE.
“Turning up a FlexILS as a GNE“
CHAPTER 8: Provides procedures to turn up and test the Infinera FlexILS as an SNE.
“Turning up a FlexILS as an SNE“

Document Organization Page lvii
Chapter Description
CHAPTER 9: Provides procedures to turn up and test the Modular Transport Chassis
(MTC-9) as an Expansion Chassis.
“Turning up an MTC-9 as an
Expansion Chassis“
CHAPTER 10: Provides procedures to turn up and test the Infinera FlexILS ROADM
multi-chassis network element.
“Turning up a FlexILS ROADM
Multi-chassis Network Element“
CHAPTER 11: Provides procedures to turn up and test the Infinera DTN as a GNE.
“Turning up a DTN as a GNE“
CHAPTER 12: Provides procedures to turn up and test the Infinera DTN as an SNE.
“Turning up a DTN as an SNE“
CHAPTER 13: Provides procedures to turn up and test the DTC/MTC as an Expansion
Chassis.
“Turning up a DTC/MTC as an
Expansion Chassis“
CHAPTER 14: Provides procedures to turn up and test a multi-chassis network element
for Optical Express.
“Turning up a Network Element for
Optical Express“
CHAPTER 15: Provides procedures to turn up and test the Infinera Optical Amplifier as
an SNE.
“Turning up an Optical Amplifier as
an SNE“
CHAPTER 16: Provides procedures to turn up and test the Optical Transport Chassis
(OTC) as an Expansion Chassis.
“Turning up an OTC as an Expan-
sion Chassis“
configured for Raman amplification (OTC based).
“Turning up a Multi-chassis Net-
work Element with Raman Amplifi-
cation (OTC based)“
configured for Raman amplification (MTC-9 based).
“Turning up a Multi-chassis Net-
work Element with Raman Amplifi-
cation (MTC-9 based)“
Appendix A: Lists the optional configuration procedures that may be performed
during the turn-up.
“Optional Configuration“
Appendix B: Provides a graphical representation of the XCM, IMM, MCM, and OMM
rebranding procedure.
“XCM/IMM/MCM/OMM Rebrand-
ing Flow“

Page lviii About this Document
Chapter Description
Appendix C: Provides procedures on how to route and connect fibers to the XTC,
MTC-9, DTC/MTC, and OTC.
“Connecting and Routing Fiber
Optic and BNC Video Cables“
Appendix D: Provides procedures on how to identify and clean the removable and
non-removable fiber connectors, and client fiber connectors used on the
“Raman Fiber Connector Cleaning“
Raman Amplifier Modules (RAMs) and Optical Raman Modules (ORMs)
which are installed in the OTC, and Infinera Line System (ILS) Raman
Modules (IRMs) which are installed in the MTC-9.
Appendix E: Provides a list of acronyms and their definitions used in Infinera
Technical Publications.
“Acronyms“

Documents for Release 10.0 Page lix
Documents for Release 10.0

The following documents are available for Infinera Intelligent Transport Network™ systems:
Document Name Document ID Description
DTN and DTN-X Installation Guides Portfolio
Infinera DTN and DTN-X 1900-001267 Describes procedures for turning up, commissioning and testing
Turn-up and Test Guide the installed Infinera DTN-X, FlexILS, DTN, and Optical Ampli-
fier network elements. Includes the description of circuit activa-
tion and end-end system testing procedures.
Infinera DTN and DTN-X Site 1900-001268 Describes the procedures for initial installation of the Infinera
Preparation and Hardware DTN-X, FlexILS, DTN, and Optical Amplifier network elements
Installation Guide at any given site. Includes procedures for site preparation and
site testing, system cabling, safety procedures and hand-over to
provisioning activities.
DTN and DTN-X Procedure Guides Portfolio
Infinera DTN and DTN-X 1900-001269 Provides the routine task oriented procedures (TOPs) used in
Task Oriented Procedures support of the Infinera DTN-X, FlexILS, DTN, and Optical Ampli-
Guide fier network elements.
DTN and DTN-X Reference Guides Portfolio
Infinera DTN and DTN-X 1900-001270 Provides the hardware description of the Infinera DTN-X,
Hardware Description Guide FlexILS, DTN, and Optical Amplifier network elements which
includes the description of chassis, common modules and circuit
packs. It provides hardware block diagrams, functional descrip-
tions, mechanical and electrical specifications for each module.
Infinera DTN and DTN-X 1900-001271 Describes the user interface for the Infinera DTN-X, FlexILS,
SNMP Agent Reference and DTN Simple Network Management Protocol (SNMP) Agent.
Guide It provides detailed instructions to configure and operate the
Infinera SNMP Agent from the Infinera network element.
Infinera DTN and DTN-X 1900-001272 Provides an overview of the Infinera Intelligent Transport Net-
System Description Guide work and its principal elements, including the Infinera DTN-X,
FlexILS, DTN, and the Optical Amplifier. Includes a description
of the Infinera IQ Network Operating System and an overview of
the management interfaces for Infinera products.
DTN and DTN-X User Guides Portfolio
Infinera GNM Overview 1900-001273 Describes the Infinera Graphical Node Manager user interface.
Guide It also describes the new features, the hardware and software
requirements required to launch the GNM. It also provides pro-
cedures to install and upgrade the software and database on the
Infinera network elements.

Page lx About this Document
Document Name Document ID Description
Infinera GNM Fault 1900-001274 Describes the Fault Management inventories, Alarm Manager
Management and and Event Log. It also provides the procedures to perform diag-
Diagnostics Guide nostic tests on Infinera network elements. In addition, it
describes the alarms raised by the Infinera network elements
and the corrective procedures to perform to clear the alarms.
Infinera GNM Configuration 1900-001275 Describes the procedures to use the Infinera GNM to configure
Management Guide the Infinera network elements and the network topology. It also
provides a description on the Equipment Manager and Facility
Manager.
Infinera GNM Performance 1900-001276 Describes the procedures to use Infinera GNM to view perfor-
Management Guide mance monitoring (PM) data and modify PM thresholds for the
Infinera DTN-X, FlexILS, DTN, and Optical Amplifier network
elements. It also provides the PM parameters details reported
by the Infinera network elements.
Infinera GNM Security 1900-001277 Describes the procedures to perform security and access man-
Management Guide agement tasks such as creating, deleting and managing user
accounts on the Infinera network elements.
Infinera GNM Service 1900-001278 Describes the procedures to provision cross-connects, subnet-
Provisioning Guide work connections (SNCs) and protected services on Infinera
DTN-X, FlexILS, DTN, and Optical Amplifier network elements.
It includes a description of the various inventory managers dis-
played in the Infinera GNM.
Infinera DTN and DTN-X TL1 1900-001279 Describes the TL1 interface supported by the Infinera DTN-X,
User Guide FlexILS, DTN, and Optical Amplifier network elements. It
includes the description of the supported TL1 commands and
the procedures for the commonly performed OAM&P functions.

Release 10.0 New and Updated Features Page lxi
Release 10.0 New and Updated Features

Table i lists the new and updated features for IQ NOS software and the DTN-X, DTN, Optical Amplifier,
and FlexILS nodes for Release 10.0:
Note: Unless specifically noted otherwise, all references to “line module” will refer interchange-
ably to either the DLM, XLM, ADLM, AXLM, SLM, AXLM-80, ADLM-80 and/or SLM-80
(DTC/MTC only) and AOFM, AOFX, AOLM, AOLM2, AOLX, AOLX2, SOLM, SOLM2,
SOLX, and/or SOLX2 (XTC only). The term “LM-80” is used to specify the LM-80 sub-set
of line modules and refers interchangeably to the AXLM-80, ADLM-80 and/or SLM-80
(DTC/MTC only). Note that the term “line module” does not refer to TEMs, as they do not
have line-side capabilities and are used for tributary extension.
Table i New and Updated Features for DTN-X, DTN, Optical Amplifier, and FlexILS Nodes
Feature Description
Node Configurations
DTN-X with ROADM In Release 10.0, a DTN-X node (a node with an XTC as a Main Chassis) can be con-
figured with MTC-9 Expansion Chassis to support FlexILS ROADM functionality.
FlexILS ROADM Release 10.0 introduces the FlexILS products and functionality. The Infinera FlexILS
ROADM is a reconfigurable optical add/drop multiplexer node with an MTC-9 as a
Main Chassis. The FlexILS ROADM node provides colorless ROADM (optical
express) functionality, and can also be used to provide dynamic spectral shaping
capability, with each FRM dynamically equalizing the optical spectrum in one direc-
tion.
FlexILS Optical Line Ampli- The FlexILS Optical Line Amplifier is a node used for optical amplification of FlexILS
fier services with an MTC-9 as a Main Chassis.
NOTE: In previous releases, a node with an OTC as the Main Chassis (and an OMM
as the node controller module) was referred to in the documentation as an "Optical
Line Amplifier" node. Note that the management interfaces have always referred to
this node type as an "Optical Amplifier." In Release 10, the customer documentation
is updated to match the terminology of the management interfaces, wherein a node
with an OTC Main Chassis is called an "Optical Amplifier." Note that the term "Optical
Line Amplifier" is re-introduced as a node with an MTC-9 as the Main Chassis (with
an IMM as the node controller module) and configured with IAMs/IRMs.
Multi-chassis Configura- In Release 10.0, the multi-chassis scalability for a DTN-X node has been increased:
tions • The total number of chassis supported on a DTN-X has been increased from 54 to
60 to accommodate a maximum of 6 MTC-9s.

Page lxii About this Document
Feature Description
XTC Hardware and Hardware Modules

Advanced OTN FlexChan- Release 10.0 introduces the AOFM, a tunable super channel (SCh) based OTN line
nel Line Module (AOFM) module that utilizes Soft Decision-Forward Error Correction (SD-FEC). The AOFM is
optically connected to an MTC-9 (either directly to an FSM or indirectly to an FRM via
an FSP-C or FMP-C) to provide bandwidth for up to 9.5Tbps of traffic signals. The
following AOFMs are supported in Release 10.0:
• AOFM-500-T4-n-C5 (n = 1, 5, 9, 13, or 17)
• AOFM-500-T4-n-C6 (n = 1, 5, 9, 13, or 17)
• AOFM-500-T4-n-C8 (n = 1, 5, 9, 13, or 17)
• AOFM-500B-T4-n-C5 (n = 1, 5, 9, 13, or 17)
• AOFM-500B-T4-n-C6 (n = 1, 5, 9, 13, or 17)
• AOFM-500B-T4-n-C8 (n = 1, 5, 9, 13, or 17)
Advanced OTN FlexChan- Release 10.0 introduces the AOFX, a tunable super channel (SCh) based OTN line
nel Switching Line Module module that utilizes Soft Decision-Forward Error Correction (SD-FEC). The AOFX is
(AOFX) optically connected to an MTC-9 (either directly to an FSM or indirectly to an FRM via
an FSP-C or FMP-C) to provide bandwidth for up to 9.5Tbps of traffic signals. The
AOFX has a bidirectional backplane interface to the switch fabric to enable all
switched data to be directed to any of the line card slots within the XTC. The follow-
ing AOFXs are supported in Release 10.0:
• AOFX-500-T4-n-C5 (n = 1, 5, 9, 13, or 17)
• AOFX-500-T4-n-C6 (n = 1, 5, 9, 13, or 17)
• AOFX-500-T4-n-C8 (n = 1, 5, 9, 13, or 17)
• AOFX-500B-T4-n-C5 (n = 1, 5, 9, 13, or 17)
• AOFX-500B-T4-n-C6 (n = 1, 5, 9, 13, or 17)
• AOFX-500B-T4-n-C8 (n = 1, 5, 9, 13, or 17)
Instant Bandwidth Line Release 10.0 introduces the following Instant Bandwidth versions of the AOFX and
Modules the AOFM:
• AOFM-500B-T4-n-C5 (n = 1, 5, 9, 13, or 17)
• AOFM-500B-T4-n-C6 (n = 1, 5, 9, 13, or 17)
• AOFM-500B-T4-n-C8 (n = 1, 5, 9, 13, or 17)
• AOFX-500B-T4-n-C5 (n = 1, 5, 9, 13, or 17)
• AOFX-500B-T4-n-C6 (n = 1, 5, 9, 13, or 17)
• AOFX-500B-T4-n-C8 (n = 1, 5, 9, 13, or 17)
NOTE: The Instant Bandwidth modules have identical functions and features as their
non-Instant Bandwidth counterparts. The only difference between each Instant Band-
width module and its non-Instant Bandwidth counterpart is the Instant Bandwidth
licensing functionality itself.

Release 10.0 New and Updated Features Page lxiii
Feature Description
Tributary Interface Module Release 10.0 introduces the following TIMs for the XTC:
(TIM) • TIM-1-100GM
• TIM-1-100GX
NOTE: In Release 10.0, these TIMs function similarly to the existing TIM-1-100G. In
Release 10.0 the provisioned equipment type and installed equipment type for these
TIMs is “TIM-1-100G.”
DTN-X Interconnect Mod- Release 10.0 introduces full PON support for the XICM module for the XTC chassis.
ule (XICM) The XICM hardware and functionality was supported in previous releases, but the
user interfaces displayed the XICM as “TIM-5-10GM”. In Release 10.0, the user
interfaces display the full PON: “XICM-T-5-10GM”.The PONs are automatically
migrated upon software upgrade to Release 10.0.
DTN Interconnect Module Release 10.0 introduces full PON support for the DICM modules for the XTC chassis.
(DICM) The DICM hardware and functionality was supported in previous releases, but the
user interfaces displayed the DICMs as TAMs:
• DICM-T-2-10GM was displayed as “TAM-2-10GM”
• DICM-T-2-10GT was displayed as “TAM-2-10GT”
In Release 10.0, the user interfaces display the full DICM PONs. The PONs are auto-
matically migrated upon software upgrade to Release 10.0.
Tributary Optical Module Release 10.0 introduces support of the following TOM on the TIM-5-10GM,
(TOM) TIM-5-10GX, TIM-5B-10GM, and XICM-T-5-10GMof an XTC:
• TOM-10GE-LRL
Release 10.0 introduces support of the following TOM on the TIM-1-40G and
TIM-1-40GE of an XTC:
• TOM-40GMR-ER4
NOTE: In Release 10.0, the TOM-40GMR-ER4 is displayed in the user interfaces as
“40G TOM”.
Release 10.0 introduces support for the following TOM on the TAM-1-40GE and
TAM-1-40GR of a DTC/MTC:
• TOM-40GMR-ER4
Release 10.0 introduces full support for the TOM-10G-SFPP-SR0:
• Supported on the TIM-5-10GM, TIM-5-10GX, TIM-5B-10GM, and XICM-T-5-10GM
on an XTC
• Supported on the TAM-8-2.5GM on an MTC/DTC
NOTE: In previous releases, the TOM-10G-SFPP-SR0 was supported, but in the
user interfaces was displayed as “10G TOM”. In Release 10.0, the user interfaces
will display “TOM-10G-SFPP-SR0.”
MTC-9 Hardware and Hardware Modules
Modular Transport Chassis Release 10.0 introduces the MTC-9, a chassis that houses the common equipment
(MTC-9) required for operations and the circuit packs that support FlexILS functionality.

Page lxiv About this Document
Feature Description
Infinera Management Mod- Release 10.0 introduces the Infinera Management Module (IMM), a single-width
ule (IMM) module that provides shelf controller functionality for all modules resident within the
chassis, or node controller functionality when housed in the Main Chassis of a Flex-
ILS node.
Infinera Line System (ILS) Release 10.0 introduces Infinera Line System Amplifier Module (IAM), an EDFA-
Amplifier Module (IAM) based optical pump module that generates high power pump light onto the transmis-
sion fiber to provide EDFA amplification to the signal channels within the Infinera
Intelligent Transport Network. The IAM provides amplification for FlexILS configura-
tions. The following IAM is supported in Release 10.0:
• IAM-B-ECXH2
ILS Raman Amplifier Mod- Release 10.0 introduces Infinera Line System Raman Amplifier Module (IRM), a
ule (IRM) hybrid Raman and EDFA optical pump module that couples high power pump light
onto the transmission fiber to provide Raman assisted EDFA amplification to the sig-
nal channels within the Infinera Intelligent Transport Network. The IRM provides
amplification for FlexILS configurations. The following IRM is supported in Release
10.0:
• IRM-B-ECXH1
FlexROADM Module Release 10.0 introduces the FlexROADM Module (FRM), a multi-degree super chan-
(FRM) nel (SCh) based routing module that provides Reconfigurable Optical Add/Drop Mul-
tiplexer (ROADM) capability. The following FRM is supported in Release 10.0:
• FRM-9D-R-8-EC
FlexROADM Switching Release 10.0 introduces the FlexROADM Switching Module (FSM), a multi-degree
Module (FSM) super channel (SCh) based switching module that provides multiplexing, demultiplex-
ing, and switching of up to twelve optical channels for colorless, directionless, and
contentionless (CDC) add/drop connections. The following FSM is supported in
Release 10.0:
• FSM-CDC-8D-12-EC
FlexROADM Switching Release 10.0 introduces the FlexROADM Switching Expansion Module (FSE), a four
Expansion Module (FSE) degree switching expansion module that plugs into the expansion slot on the FSM to
provide four additional line ports. The following FSE is supported in Release 10.0:
• FSE-4D-EC
MTC-9 Blank Circuit Packs Whenever a circuit pack is removed in a MTC-9 chassis, the blank space must be
occupied by a blank circuit pack. The following MTC-9 blank circuit pack is supported
in Release 10.0:
• MTC-BLANK-1
Fiber Panel Chassis (FPC) Hardware and Hardware Modules
Fiber Panel Chassis (FPC) Release 10.0 introduces Fiber Panel Chassis (FPC), which houses Fiber Shuffle
Panel (FSP) and/or Fiber Multiplexing Panel (FMP) modules that provide fiber con-
nectivity to/from FRMs and/or FSMs residing on the MTC-9. The FPC is a rack
mountable passive chassis and does not require management or power.

Release 10.0 New and Updated Features Page lxv
Feature Description
Fiber Shuffle Panel (FSP) Release 10.0 introduces Fiber Shuffle Panels (FSPs), passive shelves that provide
fiber connectivity to/from FRMs and/or FSMs residing on the MTC-9. The following
FSPs are supported in Release 10.0:
• FSP-E-9D-18MPO
• FSP-C-1D-1MPO-4LC
• FSP-S-4D-8MPO
Fiber Multiplexing Panel Release 10.0 introduces the Fiber Multiplexing Panel (FMP), a pluggable module that
(FMP) is installed in an FPC and provides fiber connectivity to/from FRMs and/or FSMs for
colorless multiplexing of add/drop traffic. The following FMP is supported in Release
10.0:
• FMP-C-8-4-LC-MPO
Submarine Control Mod- The SCM-2, introduced in Release 9.0, supports a configuration wherein both Idler
ule (SCM) Channel CTPs are set to the same channel number and configured with a frequency
offset between the two lasers. Because this configuration is not supported on the
SCM-1, the user interfaces in Release 10.0 are updated to allow the user to config-
ure the channel number and the channel frequency offset only when an SCM-2 is
physically installed in the chassis. In addition, the some of the parameter defaults for
both SCM-1 and SCM-2 are updated in Release 10.0:
• Channel Number:
• For SCM-1, Idler #1—The default is 1
• For SCM-1, Idler #2—The default is 96
• For SCM-2, both idlers—The default is 1
• Channel Frequency Offset
• For SCM-1, both idlers—The default is 0GHz
• For SCM-2, Idler #1—The default is +6GHz
• For SCM-2, Idler #2—The default is -6GHz
• SBS Amplitude—The default is 1% for all idlers.
• SBS Frequency Width—The default is 1GHz for all idlers.
• SBS Status—The default is ON for all idlers.
In addition, two new alarms are added for SCMs:
• IDLER-SEPARATION-OOR—(SCM-2 only) The Idler Separation Out of Range
condition indicates when the difference between the two idler frequencies on an
SCM-2 is less than 10GHz and the channel numbers are the same.
• SBS-OFF—(both SCM-1 and SCM-2) The Stimulated Brillouin Scattering Off con-
dition indicates that SBS is turned off, or if the SBS frequency width is set to zero.
Service Provisioning and Service Recovery
Client Signal Fail (CSF) as Release 10.0 introduces support for configuration of client signal fail (CSF) as protec-
a Protection Trigger tion switch trigger for D-SNCP on the DTN-X.

Page lxvi About this Document
Feature Description
Configurable Fault Isola- Release 10.0 introduces support for configuration of the fault isolation layer used for
tion Layer for 1 Port D- 1 Port D-SNCP on the DTN-X.
SNCP
Fault Management
Maintenance and Trouble- In Release 10.0, the FRM, FSM, and FSE support unidirectional path loss check
shooting operations on SCGs to detect any faults or excessive loss in the dataplane connec-
tivity over MPO connectors used between SCG ports.
Automatic Saving of Release 10.0 supports a new enhancement to the warm reset behavior for all mod-
Debug Logs Before Warm ules containing a central processor complex (CPC), such as the BMM, OTM, OAM,
Reset FSM, ORM, line modules, etc. When the user warm resets a module with a CPC, the
module will first save the debug logs before beginning the warm reset process. Note
that in Release 10.0 there is a small delay between when the warm reset is
requested by the user and when the module begins the warm reset process while the
module saves the debug logs.
System Discovery and Inventory
Optical Data Plane Auto- Release 10.0 supports Auto-discovery of optical connections between certain Flex-
discovery ILS modules.
Third Party Power Supply Release 10.0 introduces support for a third party power supply mode for the XTC-10
chassis type.

Technical Assistance Page lxvii
Technical Assistance
Customer Support for Infinera products is available, 24 hours a day, 7 days a week (24x7). For information
or assistance with Infinera products, please contact the Infinera Technical Assistance Center (TAC) using
any of the methods listed below:
 Email: techsupport@infinera.com
 Telephone:
Direct within United States: +1-408-572-5288
Outside North America: +1-408-572-5288
Toll-free within United States: +1-877-INF-5288 (+1-877-463-5288)
Toll-free within Germany/France/Benelux/United Kingdom: 00-800-4634-6372
Toll-free within Japan: 010-800-4634-6372
 Fax: +1-408-572-5458
 Infinera corporate website: http://www.infinera.com
 Infinera Customer Web Portal: https://customersupport.infinera.com
Infinera Customer Web Portal

A wealth of technical support resources are available 24x7 through the Infinera Customer Web Portal at:
https://customersupport.infinera.com (login and password required).
To request access to the Infinera Customer Web Portal, send email to: techsupport@infinera.com.
Customer Web Portal Resource Log on to Customer Web Portal and then...
Access Infinera Customer Service Module (CSM): Click Link to CSM

• Create and submit incident (service request) cases
• Check status and update incident cases
• Run incident case reports
View Infinera technical support policies and procedures Click How To Guides
Download software updates Click Downloads
Download product documentation Click Documentation
View training courses and/or sign up for training Click Training
View important technical and product bulletins Click Technical Bulletins
View data sheets and/or brochures regarding service Click Service Portfolio Offerings
portfolio offerings
View Infinera contact information Click Contact Us

Page lxviii About this Document
Submitting Service Requests

To submit a service request, contact the Infinera TAC using any of the methods listed previously. Service
requests are monitored and responded to on a 24x7 basis by live TAC specialists.
Track and Update Service Requests

To check incident case status and make updates online through the Infinera Customer Web Portal,
perform the following:
Step 1 Log in at: https://customersupport.infinera.com.
Step 2 Click Link to CSM.
Step 3 Click on your incident title or ID to check your incident case status.
Step 4 To update your incident case, perform the following:
Step 4a Enter your service request within the Notes field.
Step 4b Click Submit to update the incident case.
You can also track and update Infinera CSM cases by contacting the Infinera TAC via phone or email.
Information to Provide
When submitting service request(s), have the following information available:
 Caller Name, Company, and/or Contact Information
 Priority (for example, High, Medium, Low, and/or Informational)
 Network Impact (for example, service-affecting, non-service affecting, and/or intermittent)
 Network Status (for example, deployment in progress, field trial, and/or production live)
 Software Version (if relevant)
Affected Hardware Chassis/Module/Cable Type
 Description of the problem and symptoms
 Network topology and configuration
 Supporting information (for example, data logs, troubleshooting steps taken, etc.)

Technical Assistance Page lxix
Incident Classification/Handling/Response
All service requests are immediately assigned to an Infinera Tier 3+ TAC specialist, who ensures proper
and timely handling of your request through closure. To facilitate flawless handling of customer-reported
incidents, the Infinera TAC utilizes a customer relationship management (CRM) system called the Infinera
Customer Service Module (CSM) to track and manage all reported incidents and service requests
including RMAs.
Every service request is tracked as a unique case within the Infinera CSM, and is classified in accordance
with the table below. The table below also describes the standard Service Level response and resolution
targets supported by the Infinera TAC.
Targeted Maximum
Priority Definition Handling and Escalation Time for Resolution
1—High Network service is “down”, Infinera TAC coordinates all 4 hours to find resolution, or
or extended (>30 minutes) necessary resources, 4 hours to attain workaround
loss of network manage- around-the-clock, to bring and downgrade to Major (if
ment. incident to closure. acceptable to customer).
Engagement of higher-level For software incidents with
specialists and management workaround, maintenance
with highest level of priority, release to be issued as soon
within 2 hours after incident as possible with high priority
report. engagement of Infinera
engineering resources.
2—Medium Network operation is Infinera TAC coordinates all 8 hours to attain workaround
degraded, or unacceptable necessary resources, and downgrade to Minor (if
levels of network perfor- around-the-clock, to bring acceptable to customer).
mance. Significant impact incident to closure. 8 hours for root cause identi-
on business operations. Engagement of higher-level fication.
specialists and management For software incidents,
within 4 hours after incident maintenance release to be
report. issued at time of next sched-
uled maintenance release.
3—Low Network operation is Infinera TAC coordinates all 72 hours for root cause iden-
impaired, but causes little/no necessary resources during tification.
impact on business opera- normal business hours. Fix issue in next major
tions. Engagement of higher-level release, if committed by
specialists and management Infinera development
within 2.5 days after incident resources.
report.
4—Informational An informational request Infinera will commit Varies, depending upon
that has little/no impact on resources and address dur- nature of request.
business operations. ing normal business hours.

Page lxx About this Document
Escalation
You may escalate your service request to higher levels of attention if you are not satisfied with its current
handling. All service requests are routed to management within 15 minutes of receiving your notification.
To escalate by phone or email:
Step 1 Contact the Infinera TAC.
Step 2 Provide your Infinera CSM case number.
To escalate through the Infinera Customer Web Portal:
Step 2 Click Link to CSM.
Step 3 Click on your incident title or ID.
Step 4 Enter your escalation request within the Notes field.
Step 5 Click Submit.
Return Material Authorization (RMA)

Infinera supports the following types of RMAs:
Advanced Replacement
 Repair and/or Replace
 Return for Credit
 Defective on Arrival
 Product Recall
 Takeback
To request a Return for Credit RMA, contact your Infinera Account Manager.
To request all other types of RMA, submit your RMA request to the Infinera TAC.
To download additional information on the Infinera RMA Handling Policy and Procedures, including return-
module packing instructions:
Step 2 Click How To Guides.
Step 3 Under RMA Procedures, click one of the following documents:
RMA Procedure - Customer Quick Reference.pdf
RMA Procedure.pdf

Documentation Feedback Page lxxi
Documentation Feedback
Infinera strives to constantly improve the quality of its products and documentation. Please submit
comments or suggestions regarding Infinera Technical Product Documentation using any of the following
methods:
 Submit a service request using the Infinera Customer Web Portal
 Send email to: techpubs@infinera.com
 Send mail to the following address:
Attention: Infinera Technical Documentation and Technical Training

Infinera Corporation
140 Caspian Court
Sunnyvale, CA 94089
When submitting comments, please include the following information:
 Document name and document ID written on the document cover page
 Document release number and version written on the document cover page
 Page number(s) in the document on which there are comments

Page lxxii About this Document

CHAPTER 1
Observing Safety Procedures
This chapter provides the safety procedures to follow when installing and servicing the Infinera DTN-X,
FlexILS, DTN, and Optical Amplifier network elements. Field installation and service personnel should not
perform any of the procedures in this guide without first reading and understanding all of the safety
precautions, practices, and warnings described in this chapter.
This chapter contains the following sections.
“Notational Conventions” on page 1-2
“Safety Standards” on page 1-4
“Safety Guidelines” on page 1-7
“Handling Circuit Packs” on page 1-17

Page 1-2 Notational Conventions
Notational Conventions
To prevent personal injury, equipment damage, or service interruptions, observe all of the precautionary
messages found in this guide, in addition to the safety practices established by your company.
The following precautionary symbols are used in this guide:
Electrical Hazard:
CAUTION
A precautionary message with this symbol indicates a risk of personal injury caused by the
exposure to dangerous voltages.
Electrostatic Discharge (ESD):
CAUTION
A precautionary message with this symbol indicates that an electrical or electronic device,
assembly, or system is susceptible to ESD exposure and requires special handling to pre-
vent damage.
Invisible Laser Radiation:
CAUTION
A precautionary message with this symbol indicates a risk of personal injury caused by
invisible laser radiation.
Handling Heavy Equipment:
CAUTION
A precautionary message with this symbol alerts you to the need for assistance when mov-
ing or lifting an object. The symbol may also appear to alert you to the fact that the item
being referenced is heavy and it must be handled as described in the procedure.
CAUTION
A precautionary message with this symbol alerts you to the fact that the item being
referenced is heavy and it must be handled as described in the procedure to pre-
vent personal injury or equipment damage.

Observing Safety Procedures Page 1-3
Generic Caution:
CAUTION
A precautionary message with this symbol alerts you to follow an important procedure to
prevent personal injury or equipment damage.

Page 1-4 Safety Standards
Safety Standards
The Switching Transport Chassis (XTC), Modular Transport Chassis (MTC-9), Digital Transport Chassis
(DTC), MTC, and Optical Transport Chassis (OTC) comply with many industry standard specifications as
described in Table 1-1 (XTC), Table 1-2 on page 1-5 (MTC-9), and Table 1-3 on page 1-6 (DTC/MTC/
OTC).
Table 1-1 XTC Hardware Compliancy
Category Approval Agency / Requirement
Safety Certifications • IEC/EN/UL 60950: Safety of Information Technology Equipment

• CAN/CSA C22.2 No. 60950: Safety of Information Technology Equipment
• AS/NZS 60950: Approval & Test specification - Safety of Information Technology
Equipment
• UL Class II: Fire Safety (air filters)
NEBS/ETSI Compliancy • NEBS Level 1/3
• GR-63-CORE: Network Equipment Building Systems - Physical Protection
• GR-1089-CORE: Electromagnetic Compatibility and Electrical Safety - Generic
requirement for Network Telecommunications Equipment
• ETS 300 386
• ETS 300 019-2-1, 2, 3, and 4 A1 (earthquake test methods)
EMC Emissions • CISPR 22/EN55022 Class A, FCC-A, VCCI-A
EMC Immunity • CISPR 24/EN55024
Laser Safety • IEC/EN 60825 Series: Safety of Laser Products
• IEC/EN 60825-1: 2007
• IEC/EN 60825-2: 2004+A1+A2
• FDA 21 CFR 1040: Performance Standard of Light Emitting Products
General Compliancy • ETSI ETS 300 119-2
• ETSI ETS 300 119-4
• GR-78-CORE
• GR-253-CORE
• GR-1209-CORE
• GR-1221-CORE
• ATIS 00600315 (previously ANSI T1.315)
• ATIS T1.304 (previously ANSI T1.304)
• ATT-TP-76200

Table 1-2 MTC-9 Hardware Compliancy

Equipment
• ETS 300 386
• ETS 300 753
• IEC/EN 60825-1: 2007
• IEC/EN 60825-2: 2004+A1+A2
• ETSI ETS 300 119-4
• GR-78-CORE
• GR-253-CORE
• GR-1209-CORE
• GR-1221-CORE
• ATT-TP-76200

Page 1-6 Safety Standards
Table 1-3 DTC/MTC/OTC Hardware Compliancy

Equipment
• ETS 300 386
• ETS 300 753
• IEC/EN 60825-1: 2007
• IEC/EN 60825-2: 2004+A1
• ETSI ETS 300 119-4
• GR-78-CORE
• GR-253-CORE
• GR-1209-CORE
• GR-1221-CORE
• ATT-TP-76200

Safety Guidelines
This section contains general safety guidelines and warnings to help ensure your safety and protect your
equipment from damage during turn-up and test procedures.
General Safety Guidelines

Adhere to the following general safety guidelines at all times during turn-up and test procedures:
 Only trained personnel should perform installation, service and maintenance of the DTN-X, FlexILS,
DTN, and Optical Amplifier network elements
 Exclude all unauthorized personnel from the immediate area of the turn-up and test
 Keep the chassis area clear of obstructions and dust-free before, during, and after turn-up and test
 Keep tools and equipment away from walk areas
 Do not wear loose clothing or any other items that might be caught in the equipment
 Secure long hair
 Never attempt to lift any object alone that might be too heavy for one person to lift safely
 Locate the emergency power-off switch for the room in which you are working
 Be aware of possible hazards in your work area such as: wet floors, ungrounded power extension
cords, or missing safety grounds
 Do not work alone if potentially hazardous conditions exist anywhere in the work area
 The maximum recommended ambient temperature for the network element is 55oC (131oF). Take
care to allow sufficient air circulation or space between units when the network element is installed
in a closed or multi-rack assembly (the operating ambient temperature of the rack environment
might be greater than room ambient temperature)
 Slots and openings in the chassis are provided for ventilation. To ensure reliable operation of the
network element and to protect it from overheating, do not cover the slots and openings
 The final configuration of the product must comply with the applicable safety standards and regula-
tory requirements of the country in which it is installed. If necessary, consult with the appropriate
regulatory agencies and inspection authorities to ensure compliance

Page 1-8 Safety Guidelines
Intra-Building Port Connectivity Warning

The intra-building ports of the equipment or subassembly are suitable for connection to intra-building or
unexposed wiring or cabling only. Intra-building ports include RS-232 and RJ-45 ports. In addition, the
following caveats should be noted:
 The intra-building port(s) of the equipment or subassembly must not be metallically connected to
interfaces that connect to the outside plant (OSP) or its wiring
 These interfaces are designed for use as intra-building interfaces only (Type 2 or Type 4 ports as
described in GR-1089-CORE, Issue 4) and require isolation from the exposed OSP cabling
 The addition of primary protectors is not sufficient protection in order to connect these interfaces
metallically to OSP wiring
Jewelry Removal Warning

Before working on equipment that is connected to power lines, remove jewelry including rings, necklaces,
and watches. Metal objects heat up when connected to power and ground, and can cause serious burns or
become welded to terminals.
Electrical Safety
Note: Unless specifically noted otherwise, all references to the XTC will refer to the XTC-10
and/or XTC-4 interchangeably.
The XTC-10 utilizes a power entry module (PEM) shelf that houses up to six PEMs (A1, A2, A3, B1, B2,
and B3); the XTC-4 houses up to four PEMs (PA1, PA2, PB1, and PB2). Each PEM contains two power
feeds that accept an input voltage ranging from 40V DC to 72V DC.
The MTC-9, DTC, MTC, and OTC each have two PEMs (PEM A and PEM B), which accept an input
voltage ranging from 40V DC to 72V DC.
The XTC, MTC-9, DTC, MTC, and OTC also have connectors on the shelf backplane to provide a DC
voltage supply to the circuit packs installed in the chassis.
The following precautions must be observed while handling this equipment:
CAUTION
Risk of electrical shock.
Personal injury can be caused by –48V DC. Take appropriate precautions.

 The connections and equipment that supply power to the XTC, MTC-9, DTC, MTC, and OTC must
be capable of operating safely within the maximum power requirement of the equipment. In the
event of a power overload, the supply circuits and supply wiring should not become hazardous. The
input rating for the XTC, MTC-9, DTC, MTC, and OTC PEMs is described below:
The input rating (60A) of the XTC is labeled on the PEM as shown in Figure 1-1 (PEM safety
cover is removed). Each PEM contains dual 60A circuit breakers on two power feeds
The MTC-9 PEM (Figure 1-2 on page 1-10) is connected to the power distribution unit (PDU).
The PDU must have a 15A or 20A circuit breaker
The input rating (70A or 35A) of the DTC/MTC is labeled on the PEM as shown in
Figure 1-3 on page 1-10 and Figure 1-4 on page 1-11 (PEM safety cover is removed)
The OTC PEM is connected to the PDU. The PDU must have a 10A circuit breaker
Figure 1-1 XTC Power Entry Module
Note:
The compression lugs used must
have 1/4 inch diameter stud hole size,
ON ON 5/8 inch hole spacing, and the lug
60A width must not exceed 0.60 inch.
Circuit Breaker
On-Off Switch
(Black Handle)
OFF OFF
Power LEDs
infn_860

Figure 1-2 MTC-9 Power Entry Module
Power LEDs
infn_1172
Figure 1-3 DTC/MTC Power Entry Module (PEM-70)
POWER POWER
INPUT FAULT
Power LEDs
Note:
The compression lugs used must have
RTN
1/4 inch diameter stud hole size, 5/8 inch
hole spacing, and the lug width must not
exceed 0.60 inch.
-48V
ON OFF
Power 70A Rating
On-Off Switch 70A Circuit Breaker
(Black Handle)
POWER A infn_062

Figure 1-4 DTC/MTC Power Entry Module (PEM-35)
POWER POWER
INPUT FAULT
Power LEDs
Note:
The compression lugs used must have
RTN
1/4 inch diameter stud hole size, 5/8 inch
hole spacing, and the lug width must not
exceed 0.60 inch.
-48V
ON OFF
Power 35A Rating
On-Off Switch 35A Circuit Breaker
(White Handle)
POWER A infn_778
 Ground the XTC-10/XTC-4 cabinet, XTC-10, XTC-10 PEM shelf, XTC-4, MTC-9, DTC, MTC, and
OTC in compliance with local and national electrical codes:
The XTC-10 cabinet (X-CABINET-X10) contains three internal grounding points: two at the front,
(lower left side on the cabinet) and one on the front door (lower right section); and four external
grounding points: two on the top panel, one at the front (upper left section), and one at the rear
(upper left section)
The XTC-10 and XTC-4 cabinet (X-CABINET-E1-X10 and X-CABINET-E1-X4) each contain four
internal grounding points: two at the front, upper left section (one on the front door and one on
the left side of the cabinet), one at the rear (upper right section), and one grounding bus bar at
the upper rear section
The XTC-10 contains five grounding points: one at the front (lower left section of the chassis on
the chassis kickplate), two at the left side of the chassis (upper and lower rear sections), and two
at the right side of the chassis (upper and lower rear sections)
The XTC-10 PEM shelf contains two electrical grounding points: one on each side at the rear
The XTC-4 contains four electrical grounding points: two at the front of the chassis (lower left
and right sections) and one on each side of the chassis (lower rear section)
The MTC-9 contains two electrical grounding points: one at the rear and one on the left side of
the chassis
The DTC, MTC, and OTC contain four electrical grounding points: two at the rear and one on
each side at the front for forward mount grounding
 Never connect or disconnect the power-input cables to the PEM when the other end is connected to
the power supply

 Prior to install, verify that the PEM(s) on the XTC, MTC-9, DTC, MTC, and/or OTC are not receiving
power
 Do not use both hands when working on or near a voltage source
 Use the buddy system when working around voltage sources
 Never remove a PEM while power is applied. Turn off the power at the battery distribution fuse bay
(BDFB) or PDU, and disconnect the power-input cables before removing the PEM
 Some of the connectors on the shelf backplane present an electrical hazard. Never reach into a
shelf with a conductive tool or your bare hand when power is applied to the equipment
 The DC power source to the PEM must comply with the Safety Extra-Low Voltage (SELV) require-
ments specified in UL 60950
 Install the equipment in compliance with appropriate local and national electrical codes
In the United States, use National Fire Protection Association (NFPA) 70 and the United States
National Electrical Code (NEC)
In Canada, use the Canadian Electrical Code, part I, CSA C22.1
In other countries, use International Electrotechnical Commission (IEC) 364, parts 1 through 7
 Infinera equipment is intended for installation in restricted access areas. A restricted access area is
one in which access can only be gained by service personnel through the use of a special tool, lock,
key, or other means of security, and access is controlled by the authority responsible for the location
Lifting Precautions
CAUTION
Heavy object.
The equipment is heavy. Unassisted or improper lifting techniques can cause
personal injury. Take appropriate safety precautions.
Before installing any Infinera equipment, ensure that your site is set up so that you won’t have to move
equipment later to provide direct access to power sources and other connections.
When lifting or handling materials manually, use only methods that ensure personal safety and protection
of the equipment. Never attempt to lift objects that are too bulky or heavy to handle safely. Whenever
possible, push loads instead of pulling them.
Whenever you lift or move any heavy object, take the following precautions:
 Enlist the assistance of a second person. Do not attempt to lift them by yourself
 Secure your footing while lifting. Balance the lifted weight equally between your feet
 Lift the object slowly; avoid making sudden movements or twisting your body as you lift
 Keep your back straight and lift with your legs. If you must bend down to lift the object, bend your
knees to reduce the strain on your lower back, and avoid bending solely at the waist

Always disconnect all external cables before lifting or moving Infinera equipment
ESD Safety
The XTC, DTC, MTC, and OTC have field replaceable modules that are susceptible to damage caused by
static electricity that builds up on work surfaces and personnel. The effect of Electrostatic Discharge (ESD)
damage may be immediate failure or it may manifest itself as a latent failure affecting the reliability of the
equipment.
CAUTION
Risk of damage to equipment.
The equipment is susceptible to Electrostatic Discharge (ESD). Use ESD grounding
straps when handling equipment and follow ESD procedures.
Take the following precautions to avoid ESD damage:

 Wear a grounded wrist strap or a heel strap and stand on a grounded static-dissipating floor mat
when handling chassis, circuit packs, and cables and fibers connected to circuit packs
 The wrist straps and heel straps must fit snugly, making firm contact with your skin. Ensure that the
wrist straps and heel straps are tested
 Connect the grounding cord of the wrist strap to a ground jack provided on the chassis
 Whenever possible, maintain relative humidity above 20%
Laser Safety
The XTC, MTC-9, DTC, MTC, and OTC have circuit packs with laser sources that emit light energy into
optical fibers. This energy is within the infrared (not visible) band of the electromagnetic spectrum. All
optical circuit packs (listed below) contain warning labels as shown in Figure 1-5 on page 1-15.
 XTC optical circuit packs:
Advanced OTN Line Module 500G (AOLM-500/AOLM-500B/AOLM2-500/AOLM2-500B)
Advanced OTN Switching Line Module 500G (AOLX-500/AOLX-500B/AOLX2-500/

AOLX2-500B)
Submarine OTN Line Module 500G (SOLM-500/SOLM2-500/SOLM2-500B)
Submarine OTN Switching Line Module 500G (SOLX-500/SOLX2-500/SOLX2-500B)
Advanced OTN FlexChannel Line Module 500G (AOFM-500)
Advanced OTN FlexChannel Switching Line Module 500G (AOFX-500)
OTN Tributary Module 500G (OTM-500/OTM2-500)
Class 1M Tributary Optical Module (TOM)

 MTC-9 optical circuit packs:

ILS Amplifier Module (IAM)
ILS Raman Amplifier Module (IRM)
FlexROADM Module (FRM)
FlexROADM Switching Module (FSM)
FlexROADM Switching Expansion Module (FSE)
 DTC/MTC optical circuit packs:
Band Multiplexing Module (BMM)

Channel Multiplexing Module (CMM)
Digital Line Module (DLM)
Switching Line Module (XLM)
Amplified Digital Line Module (ADLM)
Amplified Switching Line Module (AXLM)
Submarine Line Module (SLM)
Amplified Digital Line Module 80G (ADLM-80)
Amplified Switching Line Module 80G (AXLM-80)
Submarine Line Module 80G (SLM-80)
Class 1M Tributary Optical Module (TOM)
 OTC optical circuit packs:
Optical Amplification Module (OAM)
Raman Amplifier Module (RAM)
Optical Raman Module (ORM)
Submarine Control Module (SCM)

Figure 1-5 Warning Labels on Circuit Packs

Class 1M Warning on
AOLM-500, AOLM-500B, AOLX-500, AOLX-500B, Class 1M Warning on
SOLM-500, SOLX-500, AOLM2-500, AOLM2-500B, OTM-500 and OTM2-500
AOLX2-500, AOLX2-500B, SOLM2-500, SOLM2-500B, Circuit Packs Class 1M Warning on
SOLX2-500, SOLX2-500B, AOFM-500, and AOFX-500 TOM Circuit Packs
Circuit Packs INVISIBLE LASER
RADIATION
DO NOT VIEW CLASS 1M LASER
INVISIBLE LASER RADIATION 1550 nm
DIRECTLY WITH
DO NOT VIEW DIRECTLY WITH OPTICAL 15 mW
OPTICAL INSTRUMENTS INSTRUMENTS
CLASS 1M LASER PRODUCT CLASS 1M LASER
PRODUCT
1528 -1564nm – 35.5mW
Class 1M Warning on
IAM, IRM, and FRM Circuit Packs
Class 1M Warning on
INVISIBLE LASER
RADIATION FSM and FSE Circuit Packs
DO NOT VIEW
DIRECTLY WITH INVISIBLE LASER RAYONNEMENT
OPTICAL RADIATION LASER INVISIBLE
INSTRUMENTS DO NOT VIEW NE PAS REGARDER
DIRECTLY WITH DIRECTEMENT AVEC
RAYONNEMENT OPTICAL DES INSTRUMENTS
LASER INVISIBLE INSTRUMENTS OPTIQUES
NE PAS REGARDER CLASS 1M LASER PRODUIT LASER
DIRECTEMENT AVEC PRODUCT CLASS 1M
DES INSTRUMENTS 1525-1565 nm 1525-1565 nm
OPTIQUES 135mW 135 mW
LASER PRODUCT
PRODUIT LASER
CLASS 1M
1525-1565 nm
135 mW
Class 1M Warning on
Class 1 Warning on BMM, OAM, ORM, Class 1M Warning on
Class 1 Warning on
CMM Circuit Packs and SCM Circuit Packs RAM Circuit Packs
DLM, XLM, ADLM, AXLM, SLM
ADLM-80, AXLM-80, and SLM-80 INVISIBLE LASER INVISIBLE LASER
RADIATION RADIATION
Circuit Packs CLASS 1 LASER DO NOT VIEW
DIRECTLY WITH DO NOT VIEW
PRODUCT OPTICAL DIRECTLY WITH
LASER PRODUCT INSTRUMENTS OPTICAL
CLASS 1M LASER INSTRUMENTS
PRODUIT LASER PRODUCT (IEC) CLASS 1M LASER
CLASS I LASER PRODUCT
CLASS 1 PRODUCT (CDRH)
1426 - 1610nm - 1mW
1550nm-50mW
Note: Unless specifically noted otherwise, all references to the BMM will refer to either the BMM,
BMM2, BMM2P, BMM1H, BMM2H, and/or BMM2C interchangeably.
Note: Unless specifically noted otherwise, all references to the RAM will refer to either the
RAM-1, RAM-2-OR, or REM-2 interchangeably.

Note: Unless specifically noted otherwise, all references to the ORM will refer to either the
ORM-CXH1-MS and/or ORM-CXH1 interchangeably.
Note: Unless specifically noted otherwise, all references to the SCM will refer to either the
SCM-1 and/or SCM-2 interchangeably.
The warning labels on AOLM-500, AOLM-500B, AOLM2-500, AOLM2-500B, AOLX-500, AOLX-500B,

AOLX2-500, AOLX2-500B, SOLM-500, SOLX-500, SOLX2-500, SOLX2-500B, AOFM-500, AOFM-500B,
AOFX-500, AOFX-500B, OTM-500, OTM2-500, BMM, OAM, RAM, ORM, SCM, Class 1M TOM, IAM, IRM,
FSM, and/or FSE circuit packs convey the following information:
 Warn the user of the risk associated with invisible laser radiation and the potential hazard associated
with exposed optical fiber ends and unterminated connectors. A hazard can exist on either the fixed
or free end of a connector, depending on the direction of transmission
 List the nominal wavelength and line output for each particular circuit pack. The line output complies
with CLASS 1M or CLASS I standards per IEC 60825
The CMM, DLM, XLM, ADLM, AXLM, SLM, ADLM-80, AXLM-80, SLM-80, and/or Class 1 TOM circuit
packs comply with CLASS 1 or CLASS I standards per IEC 60825.
Note: Class 1 TOM circuit packs do not have a laser safety warning label.
Take the following precautions when handling or working with optical circuit packs:
 Never disconnect an optical fiber and look directly into the optical connector
 Wear laser safety goggles whenever you are in close proximity to lasers
 Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and/or
microscopes) within a distance of 100mm may pose an eye hazard
 Use of controls, adjustments, or performance of procedures other than those specified within this
guide may result in hazardous radiation exposure
 Do not adjust lasers, as it could result in hazardous radiation exposure
 Never look at an optical fiber using a direct magnification fiberscope without verifying that all light-
wave sources on the fiber are turned off
 Install protective covers or caps over connectors when they are not being used
Always assume that exposed optical connectors and cables are energized
Always make an optical power measurement of the fiber or connector before cleaning or before
visual inspection, to ensure that the fiber is not energized

Handling Circuit Packs

CAUTION
Optical connectors can be damaged if their protective covers or dust caps are not installed
when the connectors are not in use.
All circuit packs have electronic components that are susceptible to damage due to improper handling or
electrostatic discharge. Take the following precautions when handling circuit packs:
 Do not remove the circuit pack from the shipping package until you are ready to install it. Remove a
circuit pack from the antistatic protective casing only once it is in the installation vicinity
 Do not place a circuit pack down on a flat surface (on the backplane connectors) as the connectors
are susceptible to damage
 When circuit packs are not in use, store each one separately in an antistatic protective casing or
original shipping container, even if the circuit pack is defective and you are returning it
 Wear a grounded wrist strap or a heel strap before removing a circuit pack from the package or from
the shelf, and before installing it in the shelf
 Never touch the electronic components of a circuit pack. Handle the circuit pack by the faceplate
and the ejector or the handles on the faceplate
 Inspect the pin connectors on the circuit pack for any damage before inserting into the shelf
 Protect all optical connectors of the circuit packs with clean dust caps when fibers are not connected
Allow the circuit pack to reach room temperature before you insert into the shelf
 When transporting circuit packs, pack each circuit pack in its original shipping container and pad-
ding, or in a shielded bag. If the original packing material is lost, use another antistatic protective
container
 Handle circuit packs with care to prevent damage from accidental drop
 The circuit packs used in the DTN-X, FlexILS, DTN, and Optical Amplifier network elements are not
field serviceable circuit packs. Do not attempt to disassemble or repair any of the circuit packs. For
more information or assistance please contact an Infinera Technical Assistance Center (TAC)
resource using any of the methods listed in “Technical Assistance” on page lxvii

Page 1-18 Handling Circuit Packs

CHAPTER 2
Preparing for Turn-up and Test
This chapter lists the necessary tools and equipment used to turn up and test the Infinera DTN-X, FlexILS,
DTN, and Optical Amplifier network elements. This chapter is organized into the following sections:
“Tasks” on page 2-2
“Required Tools and Test Equipment” on page 2-5
“Prerequisites” on page 2-7
Before you begin to turn up and test the Infinera equipment, first complete the installation procedures, and
connect and route the fibers and cables as instructed in the Infinera DTN and DTN-X Site Preparation and
Hardware Installation Guide and the Site Survey.
Note: Unless specifically noted otherwise, all references to the DTC will refer to either the DTC-A,
DTC-B, or MTC interchangeably.

Page 2-2 Tasks
Tasks
Table 2-1 lists the tasks to be performed during this portion of the turn-up and test procedure. Use this
table to record the initial commissioning data, keep track of the tasks that have been completed, and to
record test results.
Table 2-1 Preparation Checklist and Test Results
Task/Test Page Done Results/Comments
“Required Tools and Test Equipment“ page

2-5
“GNM Terminal“ page
2-7
“Hardware Requirements“ page
2-7
“Software Requirements“ page
2-8
“Java Web Start Requirements“ page
2-9
“Browser Requirements“ page
2-11
“Commissioning Data“ page
2-12
“Main Chassis (Yes or No)—Parame- page
ter that qualifies the chassis as a Main 2-12
Chassis or Expansion Chassis“
“Network element name—Unique page
identifier to identify the network ele- 2-12
ment.“
“Router ID—Internal router ID (IP page
address) for internal communication 2-12
between the Optical Supervisory
Channel (OSC) channels. The router
ID must be unique across the net-
work“
“Data Communications Network page
(DCN) IP address—Externally acces- 2-12
sible IP address of this network ele-
ment“
“DCN netmask—Required for the page
DCN IP address“ 2-12

Preparing for Turn-up and Test Page 2-3
“Target management subnet—Subnet page

in which the customer management 2-12
stations are located“
“Target management subnet mask page
prefix (#bits)—Subnet mask for the 2-12
network in which the customer man-
agement stations are located. The
default length is 8“
“Target management subnet gate- page
way—IP address of the router in the 2-12
DCN IP subnet through which the
customer management stations can
be reached“
“OSC Out of Band Mode Required— page
Under normal operation, the node will 2-12
use the OSC wavelength in the optical
transport section (OTS) for manage-
ment. For specific applications, the
OSC can be routed via the AUX port
to an external DCN network for man-
agement“
“System time of day—System date page
and time“ 2-12
“Commit/Reconfigure/reBoot—type C page
to commit the information just 2-12
entered, R to reconfigure and repeat
the steps in case a mistake was
made, or B to reboot the XCM/MCM
and discard the changes“
“Database (Empty or restored)— page
Parameter that specifies if the data- 2-12
base (DB) must be restored on the
network element or the XCM/IMM/
MCM must come up with an empty
database“
“Infinera software release—The ver- page
sion of the software to be installed“ 2-12
“OSC IP address—The IP address of page
the OSC channel terminating on this 2-12
node“

Page 2-4 Tasks
“Provision the TX fiber type—Fiber page

type that is connected to the OUT 2-12
Line port on a BMM“
“Expected span loss information page
(optional task)—Expected power on 2-12
the receive fiber“
“Expected dispersion compensation page
(optional task)—Expected dispersion 2-12
compensation based on DCM model
number“

Required Tools and Test Equipment

The following tools and test equipment are required to turn up and test the DTN-X, FlexILS, DTN, and
Optical Amplifier network elements:
 Craft computer (this guide refers to this as the Graphical Node Manager (GNM) terminal)
 Straight-through Ethernet cable
 Crossover Ethernet cable
 Serial cable (9-pin female/male connectors)
 USB to DB9 serial adapter cable
 Latest version of communications software (HyperTerminal or TeraTerm)
 Fixed and variable attenuators
 Digital multimeter
 Optical power meter
Note: The optical power meter should be calibrated to minimize errors between measured and
actual power during deployment.
 SONET/SDH test set capable of testing OC-768, OC-192, OC-48, OC-12, OC-3, STM-256,
STM-64, STM-16, STM-4, and STM-1
 Infinera Raman, ORM, and/or IRM Point Loss Offset (PLO) adjustment utilities (contact Infinera TAC
to obtain the latest versions)
 Fiber patch cord removal tool (Panduit P/N PCRT1)
 Fiber cleaning kit consisting of:
Fiber cleaning wipes containing isopropyl alcohol; for example, Fiber-Clean

Cletop cleaning swabs for 1.25mm (White stick)
Cletop cleaning swabs for 2.5mm (White stick)
Cletop cleaning cartridge (Type A) with White tape for 1.25mm ferrules
Cletop cleaning cartridge (Type B) with Blue tape for 2.5mm ferrules
Cletop cleaning cartridge (Type MPO) with White tape for MPO-APO connectors
200x (or higher) video microscope kit; for example, JDSU FBP-SM05. Infinera recommends that
the kit be equipped with the following accessories/adapters:
Note: Some of the items listed may already be included with the video microscope kit while others
may need to be acquired individually. For additional information or assistance, contact the
Infinera deployment team.

Page 2-6 Required Tools and Test Equipment
Hand-held display
LC bulkhead adapter tip
SC bulkhead adapter tip
MPO-APC bulkhead adapter tip
MPO-APC probe tip adapter sleeve
1.25mm patchcord tip
2.5mm patchcord tip
Optional: Westover CleanBlast system or equivalent

Prerequisites
The items listed in the following sections are required before beginning the turn-up and test procedures.
GNM Terminal
The Infinera Graphical Node Manager (referred to as Infinera GNM) management application will be
required for the turn-up and test procedures. Infinera GNM is run on a craft computer (referred to as GNM
terminal). The GNM terminal must have Ethernet connectivity and must meet the requirements listed in the
sections below.
Hardware Requirements
The GNM terminal must meet one of the hardware requirements listed in Table 2-2, Table 2-3, Table 2-4
on page 2-8, or Table 2-5 on page 2-8.
Table 2-2 GNM Terminal Hardware Requirements for Oracle Solaris
Oracle Solaris
Requirements Minimum Recommended
Processor speed 1GHz 1GHz

Memory 2 GB 3 GBa
Hard disk free space 2 GB 2 GB
a. Swap space equal to or greater than the physical RAM size
Table 2-3 GNM Terminal Hardware Requirements for Microsoft Windows
Microsoft Windows
Processor speed 1.5 GHz 2 GHz

Memory 2 GB 3 GBa
a. The recommended virtual memory is 1.5 times to 3 times the memory
size

Page 2-8 Prerequisites
Table 2-4 GNM Terminal Hardware Requirements for Red Hat Linux
Red Hat Linux
Processor speed 1GHz 2GHz

Memory 2 GB 3 GBa
a. Swap space equal to or greater than the physical RAM size
Table 2-5 GNM Terminal Hardware Requirements for Apple Macintosh
Apple Macintosh
Processor speed 2.4GHz 2.4GHz

Memory 2 GB 3 GB
Software Requirements
The GNM terminal must meet any of the operating system requirements listed in Table 2-6.
Table 2-6 GNM Terminal Operating System Requirements
Requirements Versions
Oracle Solaris Oracle Solaris 11 (64 bit)

Microsoft Windows 7 Windows Service Pack 1
Microsoft Windows 8 Windows Service Pack 1
Red Hat Enterprise Linux Version 6
Apple Macintosh Version 10.8
For Oracle Solaris machines:

 Ensure that all operating system (OS) patches are installed as recommended by Oracle. For the
patch cluster, go to https://support.oracle.com
 Ensure that the following Solaris patches or the latest revision of the same are installed:
118833-36 or later
118777-13 or later
119963-14 or later

120753-06 or later
139574-03 or later
 Ensure that the patch cluster required for Java is installed as recommended by Oracle. For a list of
patches go to https://support.oracle.com
In addition, the Verisign License Signature must be accepted. Infinera GNM prompts you to accept the
license if it is not already accepted.
Java Web Start Requirements

This section lists the Java Runtime Environment (JRE) requirements to run Infinera GNM as follows:
 If Infinera GNM is launched from a Microsoft Windows or an Oracle Solaris machine, the minimum
version of the JRE required is 1.6.0_29
 If Infinera GNM is launched from a Red Hat Linux machine, the minimum version of the JRE
required is 1.6.0_45
 If Infinera GNM is launched from an Apple Macintosh machine, the version of the JRE required is
1.6.0_29
When you first launch Infinera GNM and if no JRE is installed on your machine and internet connectivity is
available, Infinera GNM will automatically download and install the JRE version (if available for automatic
download). For information on the list of JRE versions that are available for auto-download is available at:
http://www.oracle.com/technetwork/systems/patches/overview/index.html
If the JRE version is not available for auto-download, go to:
http://www.oracle.com/technetwork/java/javase/downloads/index.html to download the JRE version
manually and install the required version.
If Infinera GNM is launched from a Windows machine, and any other JRE versions are installed on your
machine, the GNM Client selects the JRE in the following order: 1.8.0_05, 1.7.0_51, 1.6.0_29.
If Infinera GNM is launched from a Solaris machine, and any other JRE versions are installed on your
machine, the GNM Client selects the JRE in the following order: 1.7.0_07, 1.6.0_35.
If Infinera GNM is launched from a Linux machine, and any other JRE versions are installed on your
machine, the GNM Client selects the JRE in the following order: 1.7.0_45, 1.6.0_45.
Note: Infinera GNM does not restrict the launch of the GNM client using JRE versions higher than
the listed above. It is recommended to contact Infinera TAC before using a JRE version not
listed above.

Installing JRE when internet connectivity is not available
To install JRE on a Microsoft Windows PC
Step 1 Navigate to the directory where jre-6u29-windows-i586-p.exe is located.

Step 2 Double-click on jre-6u29-windows-i586-p.exe to install the JRE.
To install JRE on a 64-bit Oracle Solaris platform
Note: Use the Common Desktop Environment (CDE) to install the JRE on an Oracle Solaris plat-
form.
Step 1 Copy the following files to the root directory. Enter:

jre-6u29-solaris-sparc.sh
jre-6u29-solaris-sparcv9.sh
Step 2 Change permissions to the following files. Enter:
chmod 777 jre-6u29-solaris-sparc.sh
chmod 777 jre-6u29-solaris-sparcv9.sh
Step 3 Execute the two files. Enter:
./jre-6u29-solaris-sparc.sh
./jre-6u29-solaris-sparcv9.sh
Step 4 Remove the old/existing softlink to java. Enter:
rm /usr/java
Step 5 Create the java softlink for the new JRE. Enter:
ln -s /jre1.6.0_29 /usr/java
Step 6 Remove the old/existing softlink to javaws. Enter:
rm /usr/bin/javaws
Step 7 Create the javaws softlink for the new JRE. Enter:
ln -s /jre1.6.0_29/bin/javaws /usr/bin/javaws
Step 8 Remove the old/existing softlink to mozilla plug-in. Enter:
rm /usr/sfw/lib/mozilla/plugins/libjavaplugin_oji.so
Step 9 Create the mozilla plug-in softlink for the new JRE. Enter:
ln -s /jre1.6.0_29/plugin/sparc/ns7/libjavaplugin_oji.so /usr/sfw/lib/
mozilla/plugins/libjavaplugin_oji.so

To install JRE on a Red Hat Linux platform
Step 1 Copy the file jre-6u45-linux-i586.bin file to the /usr/java directory:

Step 2 Change directory to /usr/java. Enter:
cd /usr/java
Step 3 Change permissions to the file. Enter:
chmod 777 jre-6u45-linux-i586.bin
Step 4 Execute the file. Enter:
./jre-6u45-linux-i586.bin
Step 5 Remove the old/existing softlink to java. Enter:
rm /usr/bin/java
Step 6 Remove the old/existing softlink to javaws. Enter:
rm /usr/bin/javaws
Step 7 Create the javaws softlink for the new JRE. Enter:
ln -s /usr/java/jre1.6.0_45/bin/java /usr/bin/java
ln -s /usr/java/jre1.6.0_45/bin/javaws /usr/bin/javaws
Browser Requirements
In order to run Infinera GNM, the GNM terminal must have one of the browsers listed in Table 2-7.
Table 2-7 GNM Terminal Browser Requirements
Sun Solaris Microsoft Windows Red Hat Linux Apple Macintosh
Mozilla Firefox 1.7 (and Internet Explorer 8, 9, and Mozilla Firefox 17.0.1 Safari 5.0.5
above) 10 (and above)
Mozilla Firefox 17.0.1 (and
above)

Commissioning Data
BMM2, BMM2P, BMM1H, BMM2H, and/or BMM2C interchangeably.
The site specific commissioning data, which you may obtain from the customer, is required in order to
turn-up and test the Infinera Intelligent Transport Network. Use Table 2-1 on page 2-2 to record this
information and keep it at hand during the turn-up and test procedures.
The following information is required for a node that will function as a Gateway Network Element (GNE):
Note: Configuring an Optical Amplifier as a GNE is not supported.
 Main Chassis (Yes or No)—Parameter that qualifies the chassis as a Main Chassis or Expansion
Chassis
 Network element name—Unique identifier to identify the network element.
 Router ID—Internal router ID (IP address) for internal communication between the Optical Supervi-
sory Channel (OSC) channels. The router ID must be unique across the network
 Data Communications Network (DCN) IP address—Externally accessible IP address of this network
element
 DCN netmask—Required for the DCN IP address
 Target management subnet—Subnet in which the customer management stations are located
 Target management subnet mask prefix (#bits)—Subnet mask for the network in which the customer
management stations are located. The default length is 8
 Shelf ID—Unique identifier to identify the chassis. Valid range is 1 - 63 (default is 1)
 Target management subnet gateway—IP address of the router in the DCN IP subnet through which
the customer management stations can be reached
 OSC Out of Band Mode Required—Under normal operation, the node will use the OSC wavelength
in the optical transport section (OTS) for management. For specific applications, the OSC can be
routed via the AUX port to an external DCN network for management
 System time of day—System date and time
 Commit/Reconfigure/reBoot—type C to commit the information just entered, R to reconfigure and

repeat the steps in case a mistake was made, or B to reboot the XCM/MCM and discard the
changes
 Database (Empty or restored)—Parameter that specifies if the database (DB) must be restored on
the network element or the XCM/IMM/MCM must come up with an empty database
 Infinera software release—The version of the software to be installed
 OSC IP address—The IP address of the OSC channel terminating on this node

 Provision the TX fiber type—Fiber type that is connected to the OUT Line port on a BMM
 Expected span loss information (optional task)—Expected power on the receive fiber
 Expected dispersion compensation (optional task)—Expected dispersion compensation based on

DCM model number
The following information is required for a node that will function as a Subtending Network Element (SNE):
 Main Chassis (Yes or No)—Parameter that qualifies the chassis as a Main Chassis or Expansion
Chassis
 Network element name—Unique identifier to identify the network element
 Router ID—Internal router ID (IP address) for internal communication between the OSC channels.
The router ID must be unique across the network
 System time of day—System date and time
 Database (Empty or restored)—Parameter that specifies if the database must be restored on the
network element or the XCM/IMM/MCM/OMM must come up with an empty database
 Infinera software release—The version of the software to be installed
 OSC IP address—The IP address of the OSC channel terminating on this node
 Expected span loss information (optional task)—Expected power on the receive fiber
 Expected dispersion compensation (optional task)—Expected dispersion compensation based on

DCM model number

IP Address Recommendations
The section below lists some of the recommendations while assigning IP address in the Infinera Intelligent
Transport Network:
 The following IP addresses are allocated for private internet use:
10.0.0.0 - 10.255.255.255(10/8 prefix)
172.16.0.0 - 172.31.255.255(172.16/12 prefix)
192.168.0.0 - 192.168.255.255(192.168/16 prefix)
It is recommended that you assign the Router ID, OSC IP Address, and Craft IP Address to use any
of the above IP address ranges.
Note: Do not use IP addresses in the 127.X.X.X network because the network elements use this
address range for internal IP addresses for modules populated in the chassis.
 If the DCN and/or AUX is also using a private address, Router ID, OSC IP Address and Craft IP
Address should use a different prefix from DCN and/or AUX
Use 30 bit prefix for each OSC link subnet
Use a common prefix for all OSC subnets
 Use the same prefix for all Router IDs within the Infinera Intelligent Transport Network. It is recom-
mended that the Router ID prefix be different from the OSC prefix
 Use the same Craft IP Address for all network elements in the Infinera Intelligent Transport Network
 The target management subnet should not match or overlap with OSC and router ID network
addresses

CHAPTER 3
Turning up a DTN-X as a GNE
This chapter provides the procedures to turn up and test a DTN-X as a Gateway Network Element (GNE).
This chapter is organized into the following sections:
“DTN-X Main Chassis Turn-up” on page 3-2
“Testing XTC Circuit Packs” on page 3-64
“Verifying Network Element Alarms” on page 3-68
“Datawire Service Turn-up” on page 3-76

Page 3-2 DTN-X Main Chassis Turn-up
DTN-X Main Chassis Turn-up

Note: Unless specifically noted otherwise, all references to the "line module" will refer to the
AOLM-500, AOLM-500B, AOLX-500, AOLX-500B, SOLM-500, SOLX-500, AOLM2-500,
AOLM2-500B, AOLX2-500, AOLX2-500B, SOLM2-500, SOLM2-500B, SOLX2-500,
SOLX2-500B, AOFM-500, AOFM-500B, AOFX-500, and/or AOFX-500B interchangeably.
The DTN-X consists of one or more Switching Transport Chassis (XTC), Digital Transport Chassis (DTC),
MTC, and/or Optical Transport Chassis (OTC). The XTC is available in the following options:
 XTC-10—is a single bay chassis option providing ten universal card slots to house line modules
and/or OTM-500/OTM2-500s. In addition, the XTC-10 is a nominal ETSI (600mm) width chassis
type with an available 23-inch mounting option. Figure 3-1 on page 3-3 shows the various hardware
components of the XTC-10
 XTC-4—is a half-bay chassis option providing four universal card slots to house line modules and/or
OTM-500/OTM2-500s. In addition, the XTC-4 is an ANSI 19-inch width chassis type with an avail-
able ETSI (600mm) and 23-inch mounting option. Figure 3-2 on page 3-4 shows the various hard-
ware components of the XTC-4
Note: The DTN-X (XTC-10 and XTC-4) is designed to operate in open frame racks or Infinera
supplied cabinets. Contact your Infinera account team or the Infinera deployment team if a
third-party cabinet is considered for installation as Infinera will need to review the cabinet
specifications.

Turning up a DTN-X as a GNE Page 3-3
Figure 3-1 XTC-10 Front View
PEMs PEM Shelf
IOTAP
Fan Tray 1
Fan Tray 2
Fiber Tray
TIMs/XICMs TSM-X10
OTM-500s/ Line Modules
OTM2-500s
Upper Universal
Card Slots TIM Blanks
TIMs/XICMs
Universal Blank XCM
Fiber Tray
Switch Fabric OXM-X10s

Card Slots
Fiber Tray
Air Filters
Air Inlet Plenum
Fiber Tray
XCM
Line Modules
TIM Blanks
TIMs/XICMs
Lower Universal
Card Slots
TIMs/XICMs Universal Blank
OTM-500s/OTM2-500s
TSM-X10
Fiber Tray
Fan Tray 3
Fan Tray 4
Chassis Kickplate infn_828

PEMs
XCMs
TAP I/O Panel
Fiber Trays
OTM-500s/OTM2-500s
Line Modules
TSM-X4
OXM-X4s
TIMs/XICMs
TIM Blanks
Fiber Tray
Fan Tray 1
Fan Tray 2
Air Filter
Air Inlet Plenum infn_900

Tasks
Table 3-1 lists the tasks that will be performed during this portion of the turn-up and test procedure. This
table should be used to keep track of the tasks that have been completed and to record test results.
Table 3-1 DTN-X Turn-up Checklist and Test Results
“Making a Serial Connection“ page

3-7
“Connecting the GNM Terminal to a page
Craft Ethernet Port“ 3-9
“Configuring the GNM Terminal“ page
3-10
“Verifying Power to the XTC“ page
3-12
“Powering up the XTC“ page
3-16
“Initial Commissioning for the XTC page
Main Chassis Gateway Network Ele- 3-18
ment (GNE)“
“Verifying XCM Craft Ethernet Port IP page
Connectivity“ 3-27
“Verifying DCN IP Connectivity“ page
3-28
“Launching Infinera GNM“ page
3-29
“Verifying Software Version“ page
3-32
“Setting Up User Accounts with Turn- page
up and Test Privileges“ 3-33
“XTC Expansion Chassis Turn-up“ page (if applicable)
5-2
“MTC-9 Expansion Chassis Turn-up“ page (if applicable)
9-2
“DTC/MTC Expansion Chassis Turn- page (if applicable)
up“ 13-2
“OTC Expansion Chassis Turn-up“ page (if applicable)
16-2
“Configuring Tunable Line Modules“ page (if applicable)
3-35

“Interconnecting the Line Module to page (if applicable)

BMM OCG Fibers“ 3-37
“Verifying Line Module Auto-discovery page (if applicable)
Completion“ 3-38
“Verifying Optical Carrier Group page (if applicable)
(OCG) Loss Threshold for Line Mod- 3-41
ules“
“Configuring Tunable Line Modules page (if applicable)
for Open Wave Line System Mode“ 3-46
“Interconnecting the Line Module-to- page (if applicable)
Line Module OCG Fibers for Open 3-50
Wave Line System Mode“
for IGCC“ 3-51
“Provisioning the Primary and Sec- page
ondary GNE IP Address“ 3-53
“Provisioning a Cross-connect“ page
3-55
“Verifying OPR and OPT on a Trib page
Port“ 3-61
“Installing the Standby XCM“ page (if applicable)
3-62
“Verifying Inventory“ page
3-63

Making a Serial Connection

Before performing the turn-up and test procedures on an XTC, a serial connection between the network
element and the craft computer (referred to as GNM terminal) must be established. Serial connectivity
requires an RS-232 serial cable with a DB-9 male connector at one end and a USB connector at the other
end.
To make a serial connection
Step 1 Insert the DB-9 male connector end of the serial cable into the port labeled Craft DCE on the
XCM.
Step 2 Insert the USB connector end of the serial cable into a USB port on the GNM terminal.
Step 3 Start the communication software application on the GNM terminal by selecting Start > Pro-
grams > Accessories > Communications then select your communications software applica-
tion (this example uses HyperTerminal). The Connection Description window is displayed.
Figure 3-3 Connection Description
Step 4 Enter a name for the new connection in the Name field (this example uses Test).
Step 5 Select any icon in the Icon field and click OK. The Connect To screen is displayed.
Figure 3-4 Connect To

Step 6 Select the appropriate COM port from the Connect Using drop-down menu (this example uses
COM1).
Step 7 Click OK to continue. The COM1 Properties window is displayed.
Figure 3-5 COM1 Properties
Step 8 In the COM1 Properties window enter the following serial set-up parameters:
Bits per second=9600
Data bits=8 bit
Parity=none
Stop bits=1 bit
Flow control=none
Step 9 Click OK. The window containing the HyperTerminal session will launch.
Note: This window should be kept open until the initial commissioning of the XTC is complete.
The HyperTerminal session (serial connection) is now created.

Connecting the GNM Terminal to a Craft Ethernet Port

The GNM terminal must be connected to the target network element and configured in order to access the
Infinera GNM interface. The XTC provides a craft Ethernet port on the XCM. The following procedure
describes how to connect an Ethernet cable to the XCM. Ethernet connectivity requires either a straight-
through or a crossover CAT5 Ethernet cable (Figure 3-6) with RJ-45 connectors at both ends. Older GNM
terminals may require a crossover CAT5 Ethernet cable.
Each network element must have an IP address to access Infinera GNM. The default IP address that is
used to access the Infinera GNM from the XCM is 192.168.0.1. The default subnet mask that is used to
access the Infinera GNM from the XCM is 255.255.255.0.
Figure 3-6 Ethernet Connection
Active XCM
(PWR, NC, and
ACT Lit Solid Green)
PWR
FLT ACT NC
CRAFT DCE
10/100/1000 BaseT
DATA
CRAFT
LINK
NCT1
C
XCM
NCT2
C
infn_930
To connect the Ethernet cable from the craft computer to the target network element
Step 1 Connect the Ethernet cable to the Ethernet port on the craft computer.
Step 2 Connect the Ethernet cable to the connector labeled Craft on the active XCM.
Note: If there is a redundant XCM, it should not be installed in the slot at this time.

Configuring the GNM Terminal
Note: The following procedures were verified using the Microsoft Windows Version 7 platform.
Perform the following procedure to establish a direct connection between the GNM terminal and the target
XTC.
If there are any values entered prior to configuration, record the values and enter the new values as
suggested.
To configure the GNM terminal
Step 1 If the craft computer is connected to the LAN using an Ethernet connection, disconnect the
Ethernet cable and reboot the craft computer before proceeding. From your Microsoft Windows
desktop, hoose Start > Control Panel > Network and Sharing Center > Change adapter set-
tings. Right-click Local Area Connection and select Properties. The Local Area Connection
Properties window is displayed.
Figure 3-7 Local Area Connection Properties

Step 2 Select Internet Protocol (TCP/IP Protocol), and click Properties. The Internet Protocol
(TCP/IP) Properties window is displayed.
Note: There may be several versions of TCP/IP listed (for example, TCP/IP, TCP/IPv4, and/or
TCP/IPv6). Contact the Network Administrator to determine which version to configure.
Figure 3-8 TCP/IP Properties
Step 3 Select Use the following IP address.

Step 4 In the IP Address field, enter an IP address (Infinera recommends using 192.168.0.5). The IP
address should be in the same subnet as the IP address configured for the target XCM or the
XTC. The last octet must vary between 2 and 255.
Note: The default IP address of the XCM is: 192.168.0.1.
Step 5 In the Subnet Mask field, enter 255.255.255.0.

Step 6 In the Default Gateway field, leave this field blank.
Step 7 Click OK to save the changes.
Step 8 Click OK.
Step 9 Click Close.

Verifying Power to the XTC
CAUTION
XTC-10 PEM Configuration

Power Entry Modules (PEMs) are installed in the XTC-10 PEM shelf, referred to as PEM shelf. The PEM
shelf is used exclusively with the XTC-10 and houses up to six PEMs (providing N+N redundancy)
depending on system load requirements and the customer’s configuration. The three PEMs occupying the
left half of the shelf comprise feed A, and the three PEMs occupying the right half of the shelf comprise
feed B. The PEM shelf slots are individually labeled, A1 (center slot) through A3 (left-most slot) and B1
(center slot) through B3 (right-most slot).
Note: The XTC-10 PEM shelf can be “colocated” with the XTC-10 (i.e. XTC-10 and XTC-10 PEM
shelf reside on the same cabinet/rack) or “non-colocated” (i.e. XTC-10 resides on a local
cabinet/rack and the PEM shelf resides on a remote cabinet/rack, located within a maxi-
mum distance of 10 feet).

The top position of the XTC-4 accommodates up to four PEMs providing N+N redundancy depending on
system load requirements and the customer’s configuration. The two PEMs occupying the top left half
comprise feed A and are labeled PA1 (center position) and PA2 (left-most position), and the two PEMs
occupying the top right half comprise feed B and are labeled PB1 (center position) and PB2 (right-most
position).
Perform the following procedure to verify the power to the XTC.
To verify power supply to the XTC
Step 1 At each PEM installed on the XTC-10 PEM shelf or XTC-4 (PEM A and PEM B feeds), verify that
both circuit breakers are set to the OFF position.
Step 2 Remove the PEM safety cover(s) as follows:
Step 2a Grasp the top and bottom of the cover.
Step 2b Unlatch one side of the cover by gently pushing the cover toward one side and simul-
taneously pull cover away from the PEM.

Step 3 At the BDFB power source for PEM A feed only, turn on the power.
WARNING
Power is now present on the terminals.
Step 4 At each PEM installed on the XTC-10 PEM shelf or XTC-4 (PEM A feed), using a multimeter set
to measure DC polarity, verify that the polarity is correct (must be negative). If the polarity is
incorrect, report readings to facilities personnel for further troubleshooting and correction.
Step 5 At the BDFB power source for PEM A feed, turn off the power.
Step 6 At the BDFB power source for PEM B feed only, turn on the power.
WARNING
Step 7 At each PEM installed on the XTC-10 PEM shelf or XTC-4 (PEM B feed), using a multimeter set
Step 8 At the BDFB power source for PEM B feed, turn off the power.
WARNING
Step 10 At each PEM installed on the XTC-10 PEM shelf or XTC-4 (PEM A feed only), turn both circuit
breakers to ON.
Step 11 Using a multimeter set to measure DC voltage, measure the voltage across the tips of the
terminal studs (not the lugs) at each PEM. See Figure 3-9 on page 3-15.
Step 11a If the readings are within the specified range (-40 to -72V DC), proceed to Step 11b.
If the measured voltage is not within the specified range, report readings to facilities
personnel for further troubleshooting and correction.
Step 11b Measure the voltage across the tips of the terminal studs (not the lugs) at each PEM
for PEM B feed (there should be no voltage present). If no voltage is measured, pro-
ceed to Step 12. If voltage is present, report readings to facilities personnel for fur-
ther troubleshooting and correction.
Step 12 At each PEM installed on the XTC-10 PEM shelf or XTC-4 (PEM A feed), turn both circuit break-
ers to OFF.

WARNING
Step 14 At each PEM installed on the XTC-10 PEM shelf or XTC-4 (PEM B feed only), turn both circuit
breakers to ON.
for PEM A feed (there should be no voltage present). If no voltage is measured, pro-
Step 16 At each PEM installed on the XTC-10 PEM shelf or XTC-4 (PEM A and PEM B feeds), turn both
circuit breakers to OFF.
Step 17 Reinstall the PEM safety cover(s) as follows:
Step 17a Align each side of the cover with the mounting tabs on the PEM terminal block.
Step 17b Press the cover against the PEM; cover should snap into place.
After you have verified that power is available to all installed PEMs and no faults exist, you are ready to
power up the XTC and perform the initial start-up procedure.

Figure 3-9 Measuring DC Voltage at the PEMs
Terminal studs
Measure voltage across

the tips of the terminal
studs (not the lugs).
ON ON
OFF OFF
infn_888

Powering up the XTC

The following section provides the procedure to power up the XTC.
Initial Start-up
After the installation procedure has been completed the XTC may be started up. Ensure that all modules
are installed (fully seated) in the universal and switch fabric card cages of the XTC-10 and/or XTC-4 except
for the standby XCM; the standby XCM (if equipped) is installed in a later task.
Refer to the Infinera DTN and DTN-X Site Preparation and Hardware Installation Guide for additional
information.
To startup the XTC
CAUTION
Step 2 At the BDFB power source that provides the PEM A feed, turn on the power.
Step 3 At the BDFB power source that provides the PEM B feed, turn on the power.
ers to ON.
Step 5 At each PEM installed on the XTC-10 PEM shelf or XTC-4 (PEM B feed), turn both circuit break-
ers to ON.
Step 6 Verify PEM LEDs on each PEM as follows:
The normal state is the Green INPUT LED ON, Green OUTPUT LED ON, and Red FAULT
LED OFF
Green Power INPUT LED on each PEM should be:
ON if an input voltage of the proper specifications is applied to the PEM
OFF if the input voltage to the PEM is not present or is present but not within the proper
specifications. Check for proper voltage being applied to the PEM
Green Power OUTPUT LED on each PEM should be:
ON if the output voltage from the PEM is within the proper specifications
OFF if the output voltage is not present (or the input voltage to the PEM is not present or
is present but not within the proper specifications)

Red Power FAULT LED on each PEM should be:

OFF if the input voltage to the PEM is within the proper specifications and no internal
fault(s) are present on the PEM
ON if the input voltage to the PEM is not within the proper specifications or no power is
present (if the other PEMs have power), or an internal fault(s) is present on the PEM.
Check for proper voltage being applied to the PEM
Step 7 Verify the Chassis POWER INPUT LED is ON.
Step 8 Initiate a lamp test by depressing the lamp test button located on the IOTAP (for XTC-10) or TAP
(for XTC-4). Ensure that the button is held down for the duration of the test.
Step 8a Verify that all LEDs on the IOTAP (for XTC-10) or TAP (for XTC-4) and all circuit
packs installed on the chassis are lit (power LEDs illuminate Green, fault LEDs illu-
minate Red, and all bi-color LEDs toggle between Green and Yellow).
Step 8b Release the lamp test button and verify that all LEDs return to the previous condition.
Step 8c If any issues are encountered during this test, contact an Infinera Technical Assis-
tance Center (TAC) resource.
After you have verified that power is present on all installed PEMs and no faults exist, you are ready to
initially configure the XTC.

Initial Commissioning for the XTC Main Chassis Gateway

Network Element (GNE)
Note: Ensure that only one XCM is installed (fully seated) in either upper universal XCM slot A-6B
or lower universal XCM slot B-6B on the XTC-10, or XCM slot A-5A or A-5B on the XTC-4;
if a redundant XCM is occupying the second slot, ensure that it is not fully seated).
After you have powered up the XTC for the first time, the boot up process is initiated. Within a minute or
two of power up, data starts scrolling in the HyperTerminal session. This session will be used to configure
the XTC. You must have the site specific commissioning data at hand (listed in “Commissioning Data” on
page 2-12 and previously recorded in Table 2-1 on page 2-2).
The procedures to commission an XTC vary depending on whether the XCM was commissioned
previously or not.
 If the XCM was not commissioned previously, see “To initially commission the Main Chassis of a
GNE if the XCM was not commissioned previously” on page 3-18
 If the XCM was commissioned previously, see “To initially commission the Main Chassis of a GNE if
the XCM was commissioned previously” on page 3-22.
See “XCM/IMM/MCM/OMM Rebranding Flow” on page B-1 for a graphical representation of the XCM
branding procedure.
To initially commission the Main Chassis of a GNE if the XCM was not commissioned previously
If the XCM was not commissioned previously, the following message is displayed in the HyperTerminal
session:
Main Chassis[yes|no] (yes) ?
Note: Information displayed within brackets [ ] indicates choices available, must be typed as dis-
played, and is case sensitive. Information displayed in parenthesis ( ) indicates default or
previously input entries, press Enter to accept the previous entry, or enter new data and
then press Enter.
Enter ~ to unconfigure optional information. Enter ? to see already configured information.
Enter the following parameters:

Step 1 Main Chassis - [yes|no](yes)?—Press Enter or type yes.
Step 2 NE Name—Unique identifier to identify the network element.

Note: NE Name is a character string with a maximum of 20 characters. Blank spaces are not
allowed. The allowable characters are alphanumeric, underscore, and hyphen. The NE
Name must begin with an alpha character.
Step 3 Router ID—Internal router ID (IP address) for communication between the XCMs. The router ID
must be unique across the network.
Note: The Router ID is also referred to in Infinera GNM as the GMPLS Node ID.
Note: When the Router ID is changed, a warning message is displayed.
Step 4 DCN IP—Externally accessible IP address of this network element.
Note: If your network configuration requires that the DCN ports be configured specifically for
100Mbps, full-duplex mode with auto-negotiation disabled, perform the following sub-step.
Otherwise, enter the DCN IP address only (with no additional input) and proceed to Step 5.
(Straight-through Ethernet cables are required for the DCN ports. Refer to the Infinera DTN
and DTN-X Site Preparation and Hardware Installation Guide for additional information.)
Step 4a To configure the DCN ports for 100Mbps, full-duplex mode with auto-negotiation
disabled, enter the DCN IP address using the following format:
xxx.xxx.xxx.xxx/FixedRate100M.
For example, 10.100.179.195/FixedRate100M
Note: If you enter this parameter incorrectly, the following error message is displayed:
Invalid parameter for DCN AutoNeg configuration. Please try again.
Step 5 DCN Netmask—Required for the DCN IP address.

Step 6 Target Management Subnet— Subnet in which the customer management stations are
located.
Step 7 Target Management Subnet Mask Prefix—Subnet mask for the network in which the customer
management stations are located. The default length is 8.
Note: Static route 10.0.0.0/255.0.0.0 will be added to the routing table.
Step 8 Target Management Subnet Gateway—IP address of the router in the DCN IP subnet through
which the customer management stations can be reached.

Step 9 Shelf ID—Unique identifier to identify the chassis. Valid range is 1 - 63 (default is 1).
Note: Changing the Shelf ID will bring up the system with an empty database (DB).
Step 10 OSC Out of Band Mode Required—Under normal operation, the node will use the Optical
Supervisory Channel (OSC) wavelength in the optical transport section (OTS) for management.
For specific applications, the OSC can be routed via the AUX port to an external DCN network for
management. Leave this field as False for normal OSC operation (in-band) or type True for Out
Of Band OSC management.
Step 11 At Do you want to change system time, verify the time. Type yes to make necessary adjust-
ments or type no to retain the system time.
Note: The system will default to the time on the GNM terminal.
Step 12 At Reinitialize SC [Delete database/nodeid/shelfid], type yes.

Step 13 At Commit/Reconfigure/reBoot, type C to commit the information just entered, R to reconfigure
and repeat the steps in case a mistake was made, or B to reboot the XCM and discard the
changes.
The XCM will reboot and the following message is displayed:
ccli: OsSystem::Reboot() Reboot...
Thu Mar 13 09:59:47 2014
The XCM boot process will stop at Do you want to go ahead with reconfiguration[yes|no].
Step 14 At Do you want to go ahead with reconfiguration[yes|no], type no. The output of the infor-
mation in the above steps is listed below:
Thu Mar 13 10:02:20 2014
ccli: Chassis is already Commissioned.
Thu Mar 13 10:02:20 2014
ccli: Branding() does not match NeId(MA4012210867) on Backplane.
CCLI configuration is mandatory. Review parameters
carefully to avoid collision with the configuration of other NE's
Already Configured Information
Main Chassis : yes
NE Name : Node1
Router ID : 11.100.179.195
Dcn IP : 10.100.179.195
Dcn Auto Negotiation Enable : True

Dcn Netmask : 255.255.255.224

Target Management Subnet : 10.0.0.0
Target Management Subnet Mask Prefix (#bits) : 8
Target Management Subnet Gateway : 10.100.179.193
Shelf ID : 1
OSC Out Of Band Mode Enabled : False
Do you want to go ahead with reconfiguration[yes|no] ? no
Note: Disconnecting the serial cable during the boot up process may cause the XCM to hang and
not boot up correctly. Ensure the boot up process is complete before disconnecting the
serial cable.
The XCM can take some time to complete the boot up process. When the PWR, NC, and ACT LEDs are
all lit solid Green the XCM has completed booting up. This indicates the XCM is operational (and safe to
remove the serial cable). The following message is displayed when the system is ready:
Cmog: Opening the management interface. System is ready.
Telnet Security not enabled. Not stopping telnet
This completes the initial commissioning of the XCM.

To initially commission the Main Chassis of a GNE if the XCM was commissioned previously
If the XCM was commissioned previously, the following message is displayed in the HyperTerminal
session:
Main Chassis : yes
NE Name : Node_2
Router ID : 11.10.2.23
Dcn IP : 10.10.2.21
Dcn Netmask : 255.255.252.0
Shelf ID : 1
Do you want to go ahead with reconfiguration[yes|no] ?
Step 1 At Do you want to go ahead with reconfiguration[yes|no] ? Type yes to proceed.
then press Enter.



Step 7 Target Management Subnet—Subnet in which the customer management stations are located.
For specific applications, the OSC can be routed via the AUX port to an external DCN network
for management. Leave this field as False for normal OSC operation (in-band) or type True for
Out Of Band OSC management.


changes. The output of the information in the above steps is listed below:
Do you want to go ahead with reconfiguration[yes|no] ? yes
Note : Enter "~" to unconfigure optional information
Note : Enter "?" to see already configured information
NE Name(Node_2) ? Node1
Router ID(11.10.2.23) ? 11.10.2.22
!!!!!!!!!!!!!!!!!!!!!!!!!! WARNING: Changing Router ID interrupts the
services provided by the dynamically signaled SNCs. Follow the recom-
mended procedures to minimize the service interruption.
!!!!!!!!!!!!!!!!!!!!!!!!!!
Do you want to continue(Y/N)[N] Y
Dcn IP(10.10.2.21) ? 10.10.2.20
Dcn Auto Negotiation Enable (True)
Dcn Netmask(255.255.252.0) ?
Target Management Subnet(10.0.0.0) ?
Target Management Subnet Mask Prefix (#bits)(8) ?
static route 10.0.0.0/255.0.0.0 will be added to the routing table
Target Management Subnet Gateway(10.10.1.1) ?
OSC Out Of Band Mode Required[True|False] (False) ?
Do you want to change system date and time(2014/03/13 09:30:00)(Y/
N)[N]?
Commit(C)/Reconfigure(R)/reBoot(B)? C
Step 15 At ccli: Branding(MA4105010230) does not match NeId(MA4104480501)!!!. Type [yes] to
continue...... the following message is displayed:
(1132135975) Thu Mar 13 10:12:55 2014
ccli: Branding(MA4105010230) does not match NeId(MA4104480501)!!!. Type
[yes] to continue......
Type yes to re-brand the XCM.

Step 16 Two different messages may be displayed:

If the XCM did not have a database stored on it, the following message is displayed:
Bring Up system with empty database or restore it?

Go to Step 17
If the XCM had a database stored on it, the following message is displayed:
Foreign Database detected - the database seems to belong to some

other network element.
Would you like the system to force a foreign database on this system?
This operation (database re-branding) can be service impacting.
Would you like to continue[yes|no]?
Go to Step 18
Step 17 At Bring Up System with empty database or restore it? Type empty. The chassis will boot up
with an empty database.
serial cable.
This completes the initial commissioning of the XCM. The XCM can take some time to complete the boot
up process. When the PWR, NC, and ACT LEDs are all lit solid Green the XCM has completed booting up.
This indicates the XCM is operational.
Step 18 There are two options:
Type yes to re-brand the XCM. The following message is displayed:
This operation (Database re-branding) can cause service impact not

just to this network element but may affect traffic on the network as
a whole. Are you sure you want to proceed with this operation[yes/
no]?
Step 18a Type yes to proceed. The following message is displayed:
Do you want to go ahead with reconfiguration.
Step 18b Type yes to proceed.
serial cable.

Type no if you do not want to re-brand the XCM. The following message is displayed:
ccli: Foreign database detected - the database seems to belong to
some other network element.
Would you like to the system to force a foreign database on this sys-
tem? This operation (database re-branding) can be service impacting.
Would you like to continue[yes|no] ?
Step 18c Type no to proceed. The following message is displayed:
Delete the database to proceed or Reboot[delete|reboot] ?
Step 18d Type delete to proceed. The following message is displayed:
Bring Up System with empty database or restore
it[empty|restore|reboot] ?
Step 18e Type empty to proceed. The following message is displayed:
ccli: System will come up with empty database.
serial cable.
This indicates the XCM is operational (and safe to remove the serial cable).

Verifying XCM Craft Ethernet Port IP Connectivity

To verify XCM craft Ethernet port IP connectivity, first ping the XCM IP address, and then test the network
element connection.
If the GNM terminal will be used to verify the XCM craft Ethernet port IP connectivity:
 Ensure that an Ethernet cable is connected from the GNM terminal to the correct XCM craft Ether-
net port on the XTC. If the XCM is located in upper universal XCM slot A-6B, use XCM craft Ethernet
port A. If the XCM is located in lower universal XCM slot B-6B, use XCM craft Ethernet port B
 Verify that the GNM terminal IP address is in the same IP domain as the XTC
Note: Follow the steps in “Configuring the GNM Terminal” on page 3-10 to change the GNM ter-
minal IP address.
To ping the XCM craft Ethernet port IP address
Step 1 Open a Microsoft Windows command prompt:

Step 1a Go to Start > Run and enter cmd and click OK.
Step 1b At the cmd prompt, enter the following command:
ping [XCM Craft Ethernet Port IP Address]

Step 2 Verify the ping response:
Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
To test the XCM craft Ethernet port IP connection of the target XTC
Step 1 Start any of the supported browsers.

Step 2 Enter the XCM craft Ethernet port IP address of the target XTC in the web address (URL) field. If
the connection is established, a login window is displayed. This verifies XCM craft Ethernet port
IP connectivity to the network element.

Verifying DCN IP Connectivity

To verify DCN IP connectivity, first ping the DCN IP address, and then test the network element
connection. If the GNM terminal will be used to verify the DCN IP connectivity:
Note: Set your terminal static IP address to interface with the DCN IP address.
 Ensure that an Ethernet cable is connected from the GNM terminal to the correct DCN port on the
XTC. If the XCM is located in upper universal XCM slot A-6B, use DCN port A. If the XCM is located
in lower universal XCM slot B-6B, use DCN port B
minal IP address.
To ping the DCN IP address

ping [DCN IP Address]


Note: Ping the gateway from the craft computer. If you do not receive a response, a network issue
exists (for instance, the router may be down). Contact the Network Administrator to identify
and correct the issue.
To test the DCN IP connection of the target XTC

Step 2 Enter the DCN IP address of the target XTC in the web address (URL) field. If the connection is
established, a login window is displayed. This verifies DCN IP connectivity to the network ele-
ment.

Launching Infinera GNM
Note: This procedure assumes that the GNM terminal meets the requirements as mentioned in
“Software Requirements” on page 2-8 and that JDK 1.6 or above is already installed on the
GNM terminal (see “Java Web Start Requirements” on page 2-9).
Note: Infinera GNM may be launched from the Ethernet craft port of an XCM using the craft
Ethernet port IP address.
Note: GNM Client launch aborts when an intermittent or sustained loss of network connectivity is
detected during the GNM Client initialization or JAR file download process. An error mes-
sage is displayed.
Perform the following procedure to launch Infinera GNM.
To launch Infinera GNM using Internet Explorer or Mozilla browser
Step 1 Start one of the recommended browsers.

Step 2 In the browser, enter the DCN IP address of the target XTC. Infinera GNM is launched in a new
window and the Login window is displayed.
Figure 3-10 Login Window
Step 3 Enter the default User Name (secadmin) and Password (Infinera1).
Step 4 Click Login. A Security Message is displayed.
Step 5 Click OK in the Security Message dialog box to continue. Infinera GNM prompts you to change
the password. This is mandatory.

Figure 3-11 Change Password
Step 6 Enter the current password and new password as prompted. The password must contain 6 to 10
alphanumeric characters and at least one alphabetic and one numeric or special character.
Step 7 Click Apply to close the window. A success message is displayed.
Step 8 Click OK to continue. The Infinera GNM user interface is displayed.
Note: The Infinera GNM window should be kept open until all remaining turn-up and test proce-
dures have been completed.
The Infinera GNM Main View is displayed showing all circuit packs installed and their current alarm
conditions (see Figure 3-12 on page 3-31).

Figure 3-12 Infinera GNM Main View of XTC

Verifying Software Version

It is important to know what version of software is on the Active XCM in the XTC. The software version
should be recorded in Table 3-1 on page 3-5. The software release version is of the format X.Y.Z where X
is the major version number, Y is the minor version number, and Z is the maintenance version number.
To verify the software version
Do one of the following:

 From the Equipment View, select the Active XCM. The Quick View Browser panel in the lower left
corner displays the XCM software version number as shown in Figure 3-13
Figure 3-13 Quick View Browser
Software
Version
 From the Main Menu select Help > About. The About Graphical Node Manager window displays
the Build/Software Version information as shown in Figure 3-14
When finished, click Close to exit the About Graphical Node Manager window
Figure 3-14 About Graphical Node Manager

Setting Up User Accounts with Turn-up and Test Privileges

Perform the following procedure to setup user accounts with turn-up and test privileges.
To setup user accounts with turn-up and test privileges
Step 1 Log into Infinera GNM with security administrator privileges.

Step 2 Select Security > NE Security Administration. The NE Security Administration window is
displayed.
Figure 3-15 NE Security Administration Window
Step 3 In the NE Security Administration window, select secadmin.

Step 4 In the Roles panel, click each of the following check boxes:
Network Engineer
Restricted Access
Provisioning
Test and Turn Up
Security Administrator
Note: Monitoring Access (grayed out) and Network Administrator should already be checked.
Step 5 Click Apply. A success message is displayed.

Step 6 Click OK.

Step 7 In the NE Security Administration window, select emsadmin.

Step 8 In the Lock Account field select No.
Step 9 In the Password panel under the Password Expiry Age (days) field enter 0.
Note: Setting the Password Expiry Age to zero (0) will ensure the password will never expire.

Step 11 Click OK.
Step 12 Click Close to exit the NE Security Administration window.
Step 13 Logout from Infinera GNM. Select File > Exit. A confirmation message is displayed.
Step 14 Click Yes to logout.
Step 15 Log into Infinera GNM using the new user just created in order for the new roles to take effect.
Note: This user account can be used to log back into the network element through the TL1 inter-
face.

Configuring Tunable Line Modules
Note: Unless specifically noted otherwise, all references to the “line module” will refer to the
AOLM2-500B, AOLX2-500, AOLX2-500B, SOLM2-500, SOLM2-500B, SOLX2-500, and/or
SOLX2-500B interchangeably.
Note: Ensure that the DTC/MTC and/or OTC Expansion Chassis has been initially commissioned
prior to performing this procedure. Refer to “DTC/MTC Expansion Chassis Turn-up” on
page 13-2 and/or “OTC Expansion Chassis Turn-up” on page 16-2.
Note: This procedure is applicable to line modules operating in either OCG (default mode) or
Open Wave line system mode.
Each XTC-10 may contain up to ten (10) tunable line modules and each XTC-4 may contain up to four (4)
tunable line modules. The line modules are optically connected to a DTC/MTC (BMM/BMM2/BMM2P/
BMM2H) and/or OTC (BMM2C).
Perform the following procedure to verify and/or to configure the operating mode and the installed OCG
number on each line module.
To verify and/or configure tunable line modules
Note: The AOLM-500B/AOLX-500Bs and/or AOLM2-500B/AOLX2-500B/SOLM2-500B/SOLX2-

500Bs initially provide 100Gbps or 50Gbps of Instant Bandwidth (depending on modulation
format). Contact your Infinera account team to purchase additional Instant Bandwidth soft-
ware licenses for additional line module bandwidth. Software licensing is managed via
Infinera Digital Network Administrator (DNA), and the activated bandwidth for the modules
can be viewed in Infinera Graphical Node Manager (GNM) or the TL1 interface. Refer to
the Infinera License Management Guide for details regarding Instant Bandwidth license
application and management. For example, obtaining a license, assigning or reassigning a
license, regenerating a license, moving a license within a chassis or to another chassis, or
moving a license back to the license store.
Step 1 From the Equipment View, right-click the tunable line module and select Admin State -> Lock.
A warning message is displayed.
Step 2 Click Lock OLM.
Step 3 From the Equipment View, right-click the tunable line module and select Properties. The OLM
Properties window is displayed. See Figure 3-16 on page 3-36.
Step 4 Click on the Tunable tab.

Step 5 Click the Operating Mode drop-down menu and select the appropriate operating mode.
Note: Must be set to Gen1 when optically connecting a line module to a BMM2C.
Step 6 Verify that the Installed OCG Number field lists the correct OCG number. If necessary, click the
Provisioned OCG Number drop-down menu and select the appropriate OCG number.
Step 7 Click Apply. A warning message is displayed.
Step 8 Click Continue.
Step 9 Click Close.
Step 10 From the Equipment View, right-click the tunable line module and select Admin State ->
Unlock.
Step 11 Repeat Step 1 through Step 10 for each installed tunable line module.
Note: If you are planning to configure the tunable line module for Open Wave line system mode
proceed to “Configuring Tunable Line Modules for Open Wave Line System Mode” on
page 3-46. Otherwise continue to “Interconnecting the Line Module to BMM OCG Fibers”
on page 3-37.
Figure 3-16 Configuring Tunable Line Modules
Tunable tab
Operating Mode
Installed OCG Number
Provisioned OCG
Number

Interconnecting the Line Module to BMM OCG Fibers
Note: This procedure is not applicable to line modules operating in Open Wave line system
mode.
BMM2H).
To interconnect OCG fiber cables between the line module and the DTC/MTC (BMM/BMM2/BMM2P/
BMM2H) perform one of the following procedures:
“To connect OCG cables between XTC line modules and DTC/MTC BMM/BMM2/BMM2P/
BMM2Hs” on page C-6
“To connect OCG cables between XTC SOLM-500/SOLX-500s and DTC BMM2/BMM2Ps” on
page C-13
“To connect OCG cables between XTC line modules and DTC BMM2/BMM2Ps” on page C-18

Verifying Line Module Auto-discovery Completion
Note: These procedures are not applicable to line modules operating in Open Wave line system
mode. Auto-discovery is not supported on line modules operating in Open Wave line sys-
tem mode.
BMM2H) and/or OTC (BMM2C).
Perform the following procedure to verify that Auto-discovery has completed on each installed line module.
To verify line module Auto-discovery completion
Step 1 From the Equipment View, right-click the line module and select Optical Carrier Group. The
OLM OCG Port Properties window is displayed. See Figure 3-17 on page 3-39.
Step 2 Click on the General tab.
Step 3 Verify that the Connected BMM Port field lists the correct BMM and the Tx Auto Discovery
State reports Completed.
Step 4 Click Apply.
Step 5 Click Close.
Step 6 Repeat Step 1 through Step 5 for each installed line module.

Figure 3-17 Verifying Line Module Auto-discovery Completion
General tab
Connected BMM port

Tx Auto Discovery
State
Note: If the Tx Auto Discovery State field reports In Progress, click Close. Wait several minutes
and repeat Step 1 through Step 3. In certain cases, it may be necessary to manually initi-
ate Auto-discovery, see “To manually initiate line module Auto-discovery” on page 3-39.
To manually initiate line module Auto-discovery
Step 2 Click on the State tab.
Step 3 In the State tab, click Administrative State -> Locked.
Step 6 Click Start Auto-Discovery. A warning message is displayed.
Step 7 Click Start Auto-Discovery.
Step 8 In the State tab, click Administrative State -> Unlocked.
Step 9 Click Close.

Figure 3-18 Manually Initiating Line Module Auto-discovery
State tab
Administrative
State
Start Auto-Discovery

Verifying Optical Carrier Group (OCG) Loss Threshold for

Line Modules
BMM2, BMM2P, BMM2H, and/or BMM2C interchangeably.
mode.
Perform the following procedure(s) to verify the OCG loss threshold between a line module in the XTC and
a BMM in the DTC/MTC. The procedures are listed as follows:
“To verify OCG loss threshold for a line module to BMM (set to Gen 1 mode) interconnection” on
page 3-42
“To verify OCG loss threshold for a line module to BMM2/BMM2P/BMM2H/BMM2C interconnection”
on page 3-44
Table 3-2 shows the supported OCG loss threshold between a line module and BMM.
Table 3-2 Supported OCG Loss Threshold between a Line Module and BMM
Line Module Type BMM Type OCG Loss Out of Range High (OORH)
Threshold
AOLM-500/AOLM-500B/ BMM 16.5dB (from OLM OCG to BMM OCG)

AOLX-500/AOLX-500B NOTE: When connecting to a Gen 1 BMM, the
addition of a 15dB optical attenuator pad is
required for normal operation.
BMM2/BMM2P/ 1.5dB (from OLM OCG to BMM OCG)
.BMM2H/BMM2C
SOLM-500/SOLX-500 BMM2/BMM2P/ 1.5dB (from OLM OCG to BMM OCG)
BMM2C
AOLM2-500/AOLM2-500B/ BMM2/BMM2P/ 1.5dB (from OLM OCG to BMM OCG)
AOLX2-500/AOLX2-500B/ BMM2C
SOLM2-500/SOLM2-500B/
SOLX2-500/SOLX2-500B

To verify OCG loss threshold for a line module to BMM (set to Gen 1 mode) interconnection
Note: This procedure is applicable to an interconnection between any one of the following line
module types only: AOLM-500, AOLM-500B, AOLX-500, or AOLX-500B, and a Gen 1
BMM type (set to Gen 1 mode).
Note: If the OCG loss threshold is exceeded, an OCG Loss Out of Range - High alarm will be
reported for the OLM OCG.
For a line module connected to a Gen 1 BMM (set to Gen 1 mode), the supported OCG loss threshold
between the line module and BMM is 16.5dB (15dB attenuator pad + 1.5dB).
Step 1 Right-click the BMM for which you would like to verify the OCG loss threshold and select Optical
Carrier Group. The BMM OCG Port Properties window is displayed.
Figure 3-19 BMM OCG Port Properties

Step 2 In the list frame, select the appropriate BMM OCG.

Step 3 Click the Real-Time PM tab and record the value listed for Total Optical Power Received
(OPR).
Step 4 Right-click the line module for which you would like to verify the OCG loss threshold and select
Optical Carrier Group. The OLM OCG Port Properties window is displayed.
Figure 3-20 OLM OCG Port Properties
Step 5 Click the Real-Time PM tab and record the value listed for Total Optical Power Transmitted
(OPT).
Step 6 Using the values obtained in Step 3 through Step 5, verify that the loss threshold between the
line module and BMM is within 16.5dB.
Loss threshold = 15.0dB + (OLM OCG OPT - BMM OCG OPR)
Step 7 Repeat Step 2 through Step 6 for each configured OCG in the system.

To verify OCG loss threshold for a line module to BMM2/BMM2P/BMM2H/BMM2C interconnection
module types: AOLM-500, AOLM-500B, AOLX-500, AOLX-500B, SOLM-500, SOLX-500,
AOLM2-500, AOLM2-500B, AOLX2-500, AOLX2-500B, SOLM2-500, SOLM2-500B,
SOLX2-500, or SOLX2-500B, and any one of the following BMM types: BMM2, BMM2P,
BMM2H, or BMM2C.
For a line module connected to a BMM2/BMM2P/BMM2H/BMM2C, the supported OCG loss threshold
between the line module and BMM is 1.5dB.


(OPR).
(OPT).
Loss threshold = OLM OCG OPT - BMM OCG OPR

Configuring Tunable Line Modules for Open Wave Line

System Mode
AOLM-500, AOLM-500B, AOLX-500, AOLX-500B, AOLM2-500, AOLM2-500B, AOLX2-
500, AOLX2-500B, SOLM2-500, SOLM2-500B, SOLX2-500, and/or SOLX2-500B inter-
changeably.
Note: This procedure is optional and only applicable if you are planning to configure for Open
Wave line system mode. Note that Auto-discovery is not supported on line modules operat-
ing in Open Wave line system mode.
tunable line modules. In Release 10.0, Open Wave line system mode is supported on certain line modules
(see first note above) allowing for a direct line module-to-line module interconnection without the
requirement of an intermediate BMM. Note that the local and remote end line modules can be different
types. For example, an AOLM-500-T4-C5 can be optically connected to an AOLX-500-T4-C6, or an
AOLM-500B-T4-C6 can be optically connected to AOLX-500-T4-C5, etc. However, each line module must
be tuned to the same OCG. For example, an AOLM-500-T4-C5 (tuned to OCG1) can be optically
connected to an AOLX-500-T4-C6 (tuned to OCG1).
Perform the following procedure to configure the line system operating mode on the line module for Open
Wave.
To configure tunable line modules for Open Wave line system mode

Step 1 From the Equipment View, right-click the tunable line module and select Admin State -> Lock. A
warning message is displayed.
Step 3 From the Equipment View, right-click the tunable line module and select Optical Carrier Group.
The OLM Port Properties window is displayed. See Figure 3-23 on page 3-47.

Figure 3-23 Configuring Line System Mode
General tab
Line System Mode

Provisioned Peer TP
Step 4 Click the General tab.

Step 5 Click the Line System Mode drop-down menu and select Open Wave.
Note: The line system mode cannot be set to Open Wave if an association exists between the line
module and a BMM or GAM OCG.
Step 6 In the Provisioned Peer TP field, click ... to select the neighbor node termination point. The Pro-
visioned Remote TP Selection dialog is displayed.See Figure 3-24 on page 3-47.
Figure 3-24 Provisioned Remote TP Selection Dialog - Part 1
List frame
Step 7 In the list frame, highlight the appropriate neighbor node and click Next.

List frame
Step 8 In the list frame, highlight the appropriate line module and click Ok.
Step 9 Verify that the Provisioned Peer TP field is now populated with the chassis and line module of
the neighbor node. See Figure 3-26 on page 3-48.
Figure 3-26 Provisioning Peer TP, Target Tx OCG Power, and Channel Count
Provisioned Peer TP
Target Tx OCG Power
Channel Count
Step 10 In the Target Tx OCG Power field, enter the appropriate value between -5.0 and +5.5,
adjustable in 0.1 increments (default is 5.0).
Step 11 In the Channel Count field, enter the appropriate value between 4 and 20 (default is 10).
Step 13 Click Ok.
Step 14 Click Close.

Unlock.
Step 16 Repeat Step 1 through Step 15 for the tunable line module at the other end of the link.

Interconnecting the Line Module-to-Line Module OCG Fibers

for Open Wave Line System Mode
changeably.
To interconnect OCG fiber cables between the line modules configured for Open Wave, refer to “To
connect OCG cables between XTC line modules configured for Open Wave line system mode” on page C-
26.

Configuring Tunable Line Modules for IGCC
Note: This procedure is optional and only applicable if you are planning to configure for IGCC.
tunable line modules. In Release 10.0, DTN-X nodes support the Infinera General Communication
Channel (IGCC), a custom control channel that supports GMPLS, protection signaling, and network
management traffic for nodes without access to the OSC such as in Open Wave line system mode or
SLTE applications. For each IGCC, an associated GMPLS control channel (GMPLSCC) is created (similar
to the GMPLSCC associated with the OSC channel). The GMPLSCC carries control traffic to bring up the
control link. Refer to the Infinera DTN and DTN-X System Description Guide for additional information.
Perform the following procedure to configure IGCC on line modules.
To configure tunable line modules for IGCC

Step 1 From the Equipment View, right-click the tunable line module and select Create IGCC. The Cre-
ate IGCC window is displayed. See Figure 3-27 on page 3-52.

Figure 3-27 Create IGCC Window
OLM AID GCC Type
IP Address
Net Mask
Step 2 In the OLM AID field, click ... The OLM Selection dialog is displayed which lists the filtered OLMs
on which IGCC can be created.
Figure 3-28 OLM Selection Dialog
List frame
Step 3 In the list frame, highlight the appropriate line module and click Ok. The AID for the selected line
module is entered into the OLM AID field.
Step 4 In the IP Address field, enter the IP address for the line module.
Note: This attribute is applicable only when the GCC Type is set to XGCC0-VCAT.
Step 5 In the Net Mask field, enter the Net Mask for the line module.
Step 6 Click GCC Type and select XGCC0-VCAT.

Step 7 Click Apply.
Step 8 Click Close.

Provisioning the Primary and Secondary GNE IP Address
Note: Provisioning a primary and secondary GNE IP address is required for a Subtending Net-
work Element (SNE) to enable FTP services. Infinera recommends that both the primary
and secondary GNE IP address be provisioned on each GNE to ensure FTP services con-
tinue to function in the event of an interruption of DCN service to the GNE. For each GNE,
the closest alternate GNE GMPLS Router ID should be used for the primary GNE and the
next closest alternate GNE GMPLS Router ID should be used for the secondary GNE.
Note: The Router ID, also referred to as the GMPLS Node ID for the GNE, must be known before
starting this procedure. To identify the GMPLS Node ID of a GNE, log in to the GNE and
right-click any BMM and select GMPLS Link. The GMPLS Node ID is located in the bottom
left corner of the GMPLS Link Properties window. Record the GMPLS Node ID for the Pri-
mary and Secondary GNE. This is the Primary/Secondary GNE IP Address utilized by
SNEs for routing IP traffic and requests.
Perform the following procedure to provision the primary and secondary GNE IP address in the XTC.
Step 1 Do one of the following:
From the Equipment Tree, right-click the network element icon and select Properties
From the Main Menu, select Configuration > Network Element
The Network Element Properties window is displayed. See Figure 3-29 on page 3-54.
Step 2 In the Summary panel, ensure that IP Gateway Proxy is checked (this is selected by default). If
the IP Gateway Proxy is not checked, click the box; a check mark is displayed.
Step 3 Select the GNE tab.
Step 4 Enter the IP address in the Primary GNE IP Address field.
Note: The IP address entered in this field is the Router ID (GMPLS Node ID) of the closest alter-
nate GNE for the Primary GNE, not the DCN IP address of the Primary GNE.
Step 5 Enter the Router ID in the Secondary GNE IP Address field.
Note: The IP address entered in this field is the Router ID (GMPLS Node ID) of the next closest
alternate GNE for the Secondary GNE, not the DCN IP address of the Secondary GNE.
Step 6 Click Apply.

Figure 3-29 GNE Network Element Properties
Summary panel
IP Gateway Proxy
GNE tab
Primary and
Secondary GNE
IP Addresses

Provisioning a Cross-connect
Perform the following procedure to create a cross-connect in the XTC.
To provision a cross-connect
Note: The following procedure provides an example of the creation of an Unprotected, 100GbE
LAN, Add/Drop cross-connect type. For detailed information regarding the creation of other
supported cross-connect types, refer to the Infinera GNM Service Provisioning Guide.

From the Infinera GNM Main Menu, select Provisioning -> Cross-connect Manager. The
Cross-connect Manager is displayed in the Workspace Area. Click New
From the Infinera GNM Main Menu, select Provisioning -> Create Cross-connect
From the Equipment Manager, right-click a row for the line module/LM-80, TEM, TAM, and/or
TOM and select Provisioning -> Cross-connect Manager. The Cross-connect Manager
is displayed in the Workspace Area. Click New
TOM and select Provisioning -> Create Cross-connect
From the Equipment View right-click a line module/LM-80, TEM, TAM, and/or TOM and
select Provisioning -> Cross-connect Manager. The Cross-connect Manager is dis-
played in the Workspace Area. Click New
select Provisioning -> Create Cross-connect
The Create Cross-connect Home screen is displayed. See Figure 3-30 on page 3-56.

Figure 3-30 Create Cross-connect (Home Screen)
Service type
Service rate
(payload type)
Connectivity type
Step 2 Click the Service Type drop-down menu to view the supported service types
(for example, select Unprotected).
Step 3 Click the Service Rate drop-down menu to view the supported payload types
(for example, select GbE -> 100GbE LAN).
Step 4 Click the Connectivity drop-down menu to view the supported connectivity types
(for example, select Add/Drop).
Note: For unidirectional service, Express, Hairpin, Add, and Drop traffic types are supported.
Note: For bidirectional service, Add/Drop, Express, and Hairpin traffic types are supported.
Note: Add traffic type and Drop traffic type are supported only for unidirectional cross-connects.
Note: Add/Drop traffic type is supported only for bidirectional cross-connects.

Note: Express traffic type is not supported for a Channelized cross-connect.
Step 5 Click Next. The Create Cross-connect window is displayed.
Note: The Create Cross-connect window may appear differently and contain different fields
depending on the service type, payload type, and/or connectivity type selected in the previ-
ous steps. See Figure 3-31 and Figure 3-32 on page 3-58.
Figure 3-31 Create Cross-connect Window
Circuit ID (CID)
Label
Source Endpoint
Intermediate LM
Destination
Endpoint

Figure 3-32 Create Cross-connect: Payload Type Screens

Step 6 Enter information in the following fields:

Circuit ID (CID)—a recommended but not mandatory field associated with the service. It is
an alpha-numeric string (identifier) used to identify the cross-connect. The string can have a
maximum of 48 characters with ‘-’, ‘_’, ‘:’, and ‘ ‘ as special characters. Although ‘ ‘ (spaces)
are supported, the string must not start or end with this. It is highly recommended that ‘~’, ‘!’,
‘%’, ‘*’, ‘(‘, ‘)’, ‘[‘, ‘]’, and ‘,’ (comma) special characters are not used in the CID field. This field
can be entered at the time of creation of the service and can be modified even after the cre-
ation of the service irrespective of the Administrative State of the service
Label—an optional field (a character string with a maximum of 128 characters) assigned at
the time of cross-connect creation to further identify the circuit
Source Endpoint—the source endpoint of the cross-connect. Click the [...] button to
view a list of the valid termination points displayed as AIDs. The Endpoint Source window is
displayed along with a list of multipoint cross-connects. Select the source endpoint and click
Ok
Figure 3-33 Endpoint Source
Intermediate LM—a field used to select the intermediate line module (LM) used by the
cross-connect. This is applicable to a multi-hop cross-connect traversing more than two LMs,
including the source and the destination. Click the Intermediate LM drop-down menu and
select an intermediate LM
Destn Endpoint—the destination endpoint of the cross-connect. Click the [...] button to
displayed along with a list of multipoint cross-connects. Select the destination endpoint and
click Ok
Step 7 Click Create. A cross-connect creation confirmation dialog is displayed.
Step 8 Click Ok. A cross-connect success confirmation dialog is displayed.
Step 9 Click Ok.
Step 10 Click Close to exit the Create Cross-connect window.
The new cross-connect that has just been created is visible in a tabular form (Cross-connect Table) in the
Cross-connect Manager (see Figure 3-34 on page 3-60).

Figure 3-34 Cross-connect Manager

Verifying OPR and OPT on a Trib Port

CAUTION
Ensure that appropriate attenuation is used when installing and/or performing loopback
tests involving optical Tributary Optical Modules (TOMs). Improper attenuation can over-
load and damage the transceiver (particularly IR and LR modules). Contact your Infinera
account team and/or an Infinera TAC resource to obtain information regarding Infinera
approved attenuator pads. Refer to the TOM section of the Infinera DTN and DTN-X Hard-
ware Description Guide for details regarding specific TOM optical specifications.
Perform the following procedure to verify the Optical Power Received (OPR) and Optical Power
Transmitted (OPT) values for all trib ports in the XTC.
To verify OPR and OPT on a Trib port
Step 1 Right-click on a TOM.

Step 2 Select Trib Port.
Step 3 In the Trib Port Properties, select Real-Time PM.
Step 4 View and record the OPR and OPT values.
Step 5 When completed, click Close.
Step 6 Repeat Step 1 through Step 5 for each TOM installed in the system.

Installing the Standby XCM

Perform the following procedure to install the standby XCM in the XTC.
To install the standby XCM
Step 1 Install the standby XCM.

The XCM takes some time to complete the boot up process. When it is complete, look at the
XCM and verify that the PWR LED is lit and Green and the ACT LED is lit and Yellow.
Step 2 Ensure the following:
In the Management Card Properties window, ensure the XCM Redundancy Status of the
XCMs are Active and Standby
The ACT LED on the standby XCM is Yellow.

Verifying Inventory
On an initial login, the Infinera GNM Main View is displayed. The Infinera GNM Main View provides access
to equipment, facilities, and tools used to control and monitor the XTC. The Infinera GNM Main View also
includes a graphical representation of the XTC being managed.
To verify equipment
 Select Configuration > Equipment Manager. Use the Equipment Manager to verify serial num-
bers, software versions, operation states, hardware version, and part number to those listed on the
Bill of Materials (BOM)
Note: The Equipment Inventory list can be exported to an application (such as Microsoft Excel) in
order to print and compare the equipment inventory to the original bill of material.
To verify termination points
 Select Configuration > Facility Manager. The Facility Manager displays a list of termination points
associated with the network element
Note: The Facility Inventory list can be exported to an application (such as Microsoft Excel) in
order to print a list of termination points associated with the network element.

Page 3-64 Testing XTC Circuit Packs
Testing XTC Circuit Packs

The following sections provide detailed instructions for testing and troubleshooting the circuit packs in the
XTC:
“Testing TOMs” on page 3-64
“Testing TIMs” on page 3-65
“Testing XICMs” on page 3-65
“Testing Line Module/OTM-500/OTM2-500s” on page 3-66

“Testing OXMs” on page 3-66
“Testing TSMs” on page 3-67
“Testing XCMs” on page 3-67
Testing TOMs
Note: The following procedure applies to all TOM types.
Perform the following procedure to test a TOM.
To test a TOM with an equipment failure alarm
Step 1 Examine the LEDs on each TOM on the XTC. The FLT is illuminated if an alarm exists. If a TOM
has an alarm, view the Alarm Manager to verify the type of alarm.
Step 2 Clear the alarm condition. Refer to the Infinera GNM Fault Management and Diagnostics Guide
for procedures to clear alarm conditions or utilize Online Help by clicking on the Troubleshoot
button in the Alarm Details window.
Step 3 The circuit pack is operational if no equipment alarms are present. To verify the operational
state, right-click the TOM from the Equipment View.
Step 4 Select Properties. The TOM Properties window is displayed.
Step 5 Click the State tab and verify that the Operational State is set to Enabled.

Testing TIMs
Note: The following procedure applies to all TIM types.
Perform the following procedure to test a TIM.
To test a TIM with an equipment failure alarm
Step 1 Examine the LEDs on each TIM on the XTC. The FLT LED is illuminated if an alarm exists. If a
TIM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the TIM from the Equipment View.
Step 4 Select Properties. The TIM Properties window is displayed.
Testing XICMs
Note: The following procedure applies to all XICM types.
Perform the following procedure to test a XICM.
To test an XICM with an equipment failure alarm
Step 1 Examine the LEDs on each XICM on the XTC. The FLT LED is illuminated if an alarm exists. If a
XICM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the XICM from the Equipment View.
Step 4 Select Properties. The XICM Properties window is displayed.

Testing Line Module/OTM-500/OTM2-500s
Perform the following procedure to test a line module/OTM-500/OTM2-500.
To test a line module/OTM-500/OTM2-500 with an equipment failure alarm
Step 1 Examine the LEDs on each line module/OTM-500/OTM2-500 on the XTC. The FLT LED is illumi-
nated if an alarm exists. If a line module/OTM-500/OTM2-500 has an alarm, view the Alarm
Manager to verify the type of alarm.
state, right-click the line module/OTM-500/OTM2-500 from the Equipment View.
Step 4 Select Properties. The OLM Properties window is displayed.
Testing OXMs
Perform the following procedure to test an OXM.
To test an OXM with an equipment failure alarm
Step 1 Examine the LEDs on each OXM on the XTC. The FLT LED is illuminated if an alarm exists. If an
OXM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the OXM from the Equipment View.
Step 4 Select Properties. The OXM Properties window is displayed.

Testing TSMs
Perform the following procedure to test a TSM.
To test a TSM with an equipment failure alarm
Step 1 Examine the LEDs on each TSM on the XTC. The FLT LED is illuminated if an alarm exists. If a
TSM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the TSM from the Equipment View.
Step 4 Select Properties. The TSM Properties window is displayed.
Testing XCMs
Note: An XCM equipment failure alarm is reported only for standby XCMs. If an equipment failure
alarm occurs on the active XCM, the XTC will not be accessible through any of the man-
agement interfaces.
Perform the following procedure to test an XCM.
To test an XCM with an equipment failure alarm
Step 1 Examine the LEDs on each XCM on the XTC. The FLT LED is illuminated if an alarm exists. If an
XCM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the XCM from the Equipment View.
Step 4 Select Properties. The XCM Properties window is displayed.

Page 3-68 Verifying Network Element Alarms
Verifying Network Element Alarms

Perform the following procedure using Infinera GNM Alarm Manager to verify if any alarms are present on
the XTC.
To view Network Element Alarms
Step 1 From the Main Menu select Fault Management > Alarm Manager. The Alarm Manager panel
is displayed listing any existing alarms on the network element.
Figure 3-35 Alarm Manager

Maximize or Minimize
the Alarm Manager Severity Filtering panel
Alarm Filtered Count panel
Alarm Filter panel
Hide the Filter panel Alarm Table
Step 2 In the Alarm Manager panel, double-click on the alarm for which you would like to view details.
The Alarm Details window is displayed listing the alarm details.

Figure 3-36 Alarm Properties
Because this is the first time you have powered up the network element and fibers may have not been
connected to the circuit packs, some alarms are expected. See Table 3-4 on page 3-70 for a list of
expected alarms for the XTC.
Alarm Severity
The alarm severity is a classification of alarms depending on the degree of perceived degradation or
disruption of service or equipment. The severity of alarms are indicated by the following color code:
Table 3-3 Alarm Severities
Alarm Severity Color Code Description
Critical (CR) Red Critical alarms indicate a severe, service-affecting condition for which imme-
diate corrective action is required to restore service.
Major (MJ) Orange Major alarms indicate a serious disruption of service, malfunctioning or failure
of important circuits. These alarms require immediate response to restore or
maintain system capability. Major alarms indicate a lesser immediate or
impending effect on service or system performance.
Minor (MN) Yellow Minor alarms are used for issues that do not have a serious effect on service
to customers.
Warning (WN) Blue Warning alarms that are used to provide information regarding special pre-
cautions.

Table 3-4 lists expected alarms that may occur upon turning up an XTC.
Table 3-4 Expected XTC Alarms
Alarm Type Cause
Optical Loss of Signal (OLOS) • No fibers are connected.

(line module to BMM connection) • Fibers are connected but they do not
have light because of Automatic Laser
Shutdown (ALS).
Optical Loss of Signal-Payload • Optical Carrier Group not present or sig-
(line module to BMM connection) nal not received in the Optical Carrier
Group.
Optical Loss of Signal • No fibers are connected.
(OLOS)(Tributary Optical Module • Fibers are connected but they do not
side) have light.
NC1 Loss of Enet Link from Con- • Expansion Chassis not present or con-
troller B (NC port not connected) nectivity with expansion chassis failed.
Note: For troubleshooting information on alarms, refer to the Infinera GNM Fault Management
and Diagnostics Guide or utilize Online Help by clicking on the Troubleshoot button in the
Alarm Details window.
Verifying Alarm Contacts

Environmental alarms are those triggered by an abnormal condition at the XTC site. The XTCs support
input and output alarm contacts to monitor and control customer’s equipment. Alarm input contacts allow
users to connect external equipment (reactors), such as fire, alarm detector, high temperature detector,
door open and so on to the XTC. When the connected equipment triggers an input contact point, it raises
an alarm with an alarm message and severity as configured by the user. Alarm output contacts allow users
to connect external equipment to the XTC.
The XTC can trigger the operation of the connected external equipment. The maximum threshold is
defined as -73.5 +/-0.5V negative going, -72.5 +/-0.5V positive going with at least 0.5V hysteresis.

Configuring Alarm Input/Output Contacts

The IOTAP contains a 68-pin SCSI connector that connects to a customer-supplied external alarm wire
wrap panel using a customer-supplied SCSI cable.
Table 3-5 lists the assignment of the alarm input/output SCSI connector pins for the XTC.
Table 3-5 XTC Alarm Input/Output Connector Pin Assignments
Pin Signal Description I/O
1 ALM_IN_GEN0_N50V Negative 50V reference for ALM_IN_GEN0 N/A

2 ALM_IN_GEN0 General Purpose Alarm Input 0 Input
7 ALM_BAY_CRIT_IN_N50V Negative 50V reference for ALM_BAY_CRIT_IN_L N/A
8 ALM_BAY_CRIT_IN_L Bay Critical Alarm Input Input
9 ALM_BAY_MIN_IN_N50V Negative 50V reference for ALM_BAY_MIN_IN_L N/A
10 ALM_BAY_MIN_IN_L Bay Minor Alarm Input Input
11 N/C N/A N/A
12 N/C N/A N/A
13 N/C N/A N/A
14 ALM_OUT_GEN2_NC General Purpose Alarm Output 2 - Normally Closed Output
15 ALM_OUT_GEN2_NO General Purpose Alarm Output 2 - Normally Open Output
16 ALM_OUT_GEN2_CT General Purpose Alarm Output 2 - Common Terminal Output
17 ALM_OUT_BAY_CRIT_NC Bay Critical Alarm Output - Normally Closed Output
18 ALM_OUT_BAY_CRIT_NO Bay Critical Alarm Output - Normally Open Output
19 ALM_OUT_BAY_CRIT_CT Bay Critical Alarm Output - Common Terminal Output
20 ALM_OUT_BAY_MIN_NC Bay Minor Alarm Output - Normally Closed Output
21 ALM_OUT_BAY_MIN_NO Bay Minor Alarm Output - Normally Open Output
22 ALM_OUT_BAY_MIN_CT Bay Minor Alarm Output - Common Terminal Output
23 ALM_OUT_VIS_MAJ_NC Visual Major Alarm Output - Normally Closed Output
24 ALM_OUT_VIS_MAJ_NO Visual Major Alarm Output - Normally Open Output
25 ALM_OUT_VIS_MAJ_CT Visual Major Alarm Output - Common Terminal Output
26 ALM_OUT_AUD_CRIT_NC Audible Critical Alarm Output - Normally Closed Output
27 ALM_OUT_AUD_CRIT_NO Audible Critical Alarm Output - Normally Open Output
28 ALM_OUT_AUD_CRIT_CT Audible Critical Alarm Output - Common Terminal Output
29 ALM_OUT_AUD_MIN_NC Audible Minor Alarm Output - Normally Closed Output
30 ALM_OUT_AUD_MIN_NO Audible Minor Alarm Output - Normally Open Output

31 ALM_OUT_AUD_MIN_CT Audible Minor Alarm Output - Common Terminal Output

39 ALM_IN_GEN5_50V Negative 50V reference for ALM_IN_GEN5 N/A
41 ALM_BAY_MAJ_IN_N50V Negative 50V reference for ALM_BAY_MAJ_IN_L N/A
42 ALM_BAY_MAJ_IN_L Bay Major Alarm Input Input
43 ALM_ACO_EXT_N50V Negative 50V reference for ALM_ACO_EXT_L N/A
44 ALM_ACO_EXT_L External Alarm Cutoff Alarm Input Input
45 N/C N/A N/A
46 N/C N/A N/A
47 N/C N/A N/A
51 ALM_OUT_BAY_MAJ_NC Bay Major Alarm Output - Normally Closed Output
52 ALM_OUT_BAY_MAJ_NO Bay Major Alarm Output - Normally Open Output
53 ALM_OUT_BAY_MAJ_CT Bay Major Alarm Output - Common Terminal Output
54 ALM_OUT_VIS_CRIT_NC Visual Critical Alarm Output - Normally Closed Output
55 ALM_OUT_VIS_CRIT_NO Visual Critical Alarm Output - Normally Open Output
56 ALM_OUT_VIS_CRIT_CT Visual Critical Alarm Output - Common Terminal Output
57 ALM_OUT_VIS_MIN_NC Visual Minor Alarm Output - Normally Closed Output
58 ALM_OUT_VIS_MIN_NO Visual Minor Alarm Output - Normally Open Output
59 ALM_OUT_VIS_MIN_CT Visual Minor Alarm Output - Common Terminal Output
60 ALM_OUT_AUD_MAJ_NC Audible Major Alarm Output - Normally Closed Output
61 ALM_OUT_AUD_MAJ_NO Audible Major Alarm Output - Normally Open Output
62 ALM_OUT_AUD_MAJ_CT Audible Major Alarm Output - Common Terminal Output
63 ALM_OUT_PWR_FLT_NC Power Fault Alarm Output - Normally Closed Output
64 ALM_OUT_PWR_FLT_NO Power Fault Alarm Output - Normally Open Output
65 ALM_OUT_PWR_FLT_CT Power Fault Alarm Output - Common Terminal Output


To configure Alarm Input Contacts
Figure 3-37 Configure Alarm Input Contacts
Step 1 From the Equipment View, right-click just below the title bar (next to the ACO-OFF button) and
select Alarm Input Contacts. The Alarm Input Contact Properties window is displayed.
Step 2 Select the input alarm contact that you want to configure in the Alarm Input Contact table. The
configurable parameters are displayed.
Step 3 Enter and edit the values.
Step 4 To save the changes, click Apply.
Step 5 When finished, click Close to exit the Alarm Input Contact Properties window.

To configure Alarm Output Contacts
Figure 3-38 Configure Alarm Output Contacts
select Alarm Output Contacts. The Alarm Output Contacts Properties window is displayed.
Step 2 Select the alarm contact you want to edit in the Output Alarm Contact table.
Step 5 When finished, click Close to exit the Alarm Output Contact Properties window.
Alarm Cutoff (ACO)

The XTC system provides a feature to acknowledge an alarm condition and turn off the audible indicator.
The ACO push button is used to mute the current audible alarms and is located on the chassis or can be
operated remotely through the Infinera GNM interface. When the ACO is enabled, all the outstanding audio
alarms are turned off and the ACO LED on the chassis is illuminated. The ACO LED indicates that one or
more audible alarms are present, but the audible indicators have been muted. The ACO LED is turned off
when the silenced audible alarms are cleared. The alarm acknowledgment by the user does not change
the ACO LED state.
Note: The ACO LED state is not shown in the Infinera GNM user interface.

To enable an ACO
Step 1 From the Equipment View, right-click just below the title bar (next to the ACO-OFF/ACO-ON but-
tons).
Step 2 From the short cut menu, select Switch On ACO State. A Warning Message is displayed
prompting the user to confirm the suppression of all current audible alarms.
Step 3 To confirm the selection click ACO ON.
Testing an ACO
Note: An external audible alarm system must be attached to one of the outputs for the ACO alarm
to be audible.
After enabling an ACO, it must be tested.
To test an ACO
Step 1 Create an alarm on the chassis (for example, remove the circuit pack). Verify that the:
ACO alarm is audible
Alarm is visible in the Alarm Manager of Infinera GNM
Step 2 Press the ACO push button on the chassis or remotely through the Infinera GNM interface. Ver-
ify that the ACO alarm is muted.
Step 3 Validate the ACO feature by verifying the following:
The audible alarm should cease
The alarm is displayed in the Alarm Manager of Infinera GNM
The ACO LED should be ON (steady Yellow)
Step 4 Clear the alarm by re-inserting the circuit pack. The ACO LED should be OFF. The ACO has
been successfully tested.

Page 3-76 Datawire Service Turn-up
Datawire Service Turn-up

Note: This procedure is optional, depending on whether or not this component is present in your
node configuration.
Perform the following procedure to configure datawire services on the XTC. The port used for the datawire
function is the AUX port.
To turn up Datawire Service
Note: The DCN and AUX ports on an Expansion Chassis are disabled.
Note: Infinera GNM may be launched from the Ethernet craft port of an XCM installed in an
Expansion Chassis.
Step 1 In the Tree View panel on the Infinera GNM Main View, right-click on the network element and
select Properties. The Network Element Properties window is displayed.

Figure 3-39 Network Element Properties

Step 2 In the Auxiliary Interface panel of the Access Interfaces tab, check Enable to specify the Auxil-
iary Port that will be used.
Step 3 Enter the IP address associated with the AUX network. The auxiliary interface is disabled when
the node is turned-up.
Step 4 Enter the Subnet Mask (this is the Netmask value of the Auxiliary IP address).
Step 5 Select the Traffic Rate Limit (in Mbps).
Step 6 Check Alter TOS Byte.
Step 7 When you are done, click Apply to save the changes.
Step 8 Click Close to exit the Network Element Properties window.
The Status Bar at the bottom left corner of the Infinera GNM Main View will display an “Operation
Successful” message if the operation is completed successfully. If it did not, you must repeat the
procedure.

CHAPTER 4
Turning up a DTN-X as an SNE
This chapter provides the procedures to turn up and test a DTN-X as a Subtending Network Element
(SNE). This chapter is organized into the following sections:


The DTN-X consists of one or more Switching Transport Chassis (XTC), Digital Transport Chassis (DTC),
MTC, and/or Optical Transport Chassis (OTC). The XTC is available in the following options:
specifications.

Turning up a DTN-X as an SNE Page 4-3
PEMs PEM Shelf
IOTAP
Fan Tray 1
Fan Tray 2
Fiber Tray
TIMs/XICMs TSM-X10
OTM2-500s
Upper Universal
TIMs/XICMs
Universal Blank XCM
Fiber Tray

Card Slots
Fiber Tray
Air Filters
Air Inlet Plenum
Fiber Tray
XCM
Line Modules
TIM Blanks
TIMs/XICMs
Lower Universal
Card Slots
OTM-500s/OTM2-500s
TSM-X10
Fiber Tray
Fan Tray 3
Fan Tray 4

PEMs
XCMs
TAP I/O Panel
Fiber Trays
OTM-500s/OTM2-500s
Line Modules
TSM-X4
OXM-X4s
TIMs/XICMs
TIM Blanks
Fiber Tray
Fan Tray 1
Fan Tray 2
Air Filter

Tasks

4-7
4-10
4-12
4-12
Main Chassis Subtending Network 4-18
Element (SNE)“
4-26
4-29
“XTC Expansion Chassis Turn-up“ page (if applicable)
5-2
9-2
“DTC/MTC Expansion Chassis Turn- page (if applicable)
up“ 13-2
“OTC Expansion Chassis Turn-up“ page (if applicable)
16-2
4-32


Completion“ 4-35
ules“
for IGCC“ 4-48
4-52
Port“ 4-58
4-59
4-60


end.
XCM.

COM1).


Active XCM
(PWR, NC, and
PWR
FLT ACT NC
CRAFT DCE
10/100/1000 BaseT
DATA
CRAFT
LINK
NCT1
C
XCM
NCT2
C
infn_930

XTC.
suggested.
desktop, hoose Start > Control Panel > Network and Sharing Center > Change adapter set-



Step 8 Click OK.
Step 9 Click Close.

CAUTION


position).

WARNING
WARNING
WARNING
breakers to ON.
ers to OFF.

WARNING
breakers to ON.

Terminal studs

ON ON
OFF OFF
infn_888

Powering up the XTC

Initial Start-up
information.
To startup the XTC
CAUTION
ers to ON.
ers to ON.
LED OFF



Initial Commissioning for the XTC Main Chassis Subtending

Network Element (SNE)
Note: DCN IP, DCN Netmask, Target Management Subnet, Target Management Subnet Mask
Prefix and Target Management Subnet Gateway are only configured for network ele-
ments that will function as a Gateway Network Element (GNE). For details on the function-
ality of the GNE refer to the Infinera DTN and DTN-X System Description Guide.
Note: Before commissioning an SNE, ensure the OSC IP address and GMPLS information has
been configured and the SNE is reachable by verifying from the network neighborhood of a
GNM terminal.
previously or not.
 If the XCM was not commissioned previously, see “To initially commission the Main Chassis of an
SNE if the XCM was not commissioned previously” on page 4-19
 If the XCM was commissioned previously, see “To initially commission the Main Chassis of an SNE
if the XCM was commissioned previously” on page 4-21.
branding procedure.

To initially commission the Main Chassis of an SNE if the XCM was not commissioned previously
session:
Main Chassis - [yes|no](yes)?
then press Enter.

Step 4 DCN IP—Press Enter.



changes.
The output of the information in the above steps is listed below:
NE Name? Node1
Router ID? 11.10.2.22
Shelf ID[1-63]? 1
Changing shelfID will bring up system with empty DB
N)[N]?
Main Chassis : yes
NE Name : Node1
Router ID : 11.10.2.22
Shelf ID : 1
Step 10 Type no to proceed. The following message is displayed:
chassis_check: 4 card(s) don't belong to this chassis (#1) detected:
chassis_check: (127_1_3_1) (127_1_3_2) (127_2_3_1) (127_2_3_2).
chassis_check: Rebooting all cards in the chassis...
Note: The chassis will reboot with an empty database. Disconnecting the serial cable during the
boot up process may cause the XCM to hang and not boot up correctly. Ensure the boot up
process is complete before disconnecting the serial cable.

To initially commission the Main Chassis of an SNE if the XCM was commissioned previously
session:
Main Chassis : yes
NE Name : Node_2
Router ID : 11.10.2.22
Dcn IP : 10.10.2.20
Shelf ID : 1
OSC Out Of Band Mode Required : False
then press Enter.

Step 5 DCN IP—If the DCN IP is blank, press Enter. If a previously commissioned DCN IP address is
present, press ~ (tilda) to unconfigure the DCN IP address.

Note: The DCN IP address must not be configured on an SNE.
Step 8 At Do you want to change system time, type yes to change the time or type no to retain the
system time.

Router ID(11.10.2.23) ? 11.10.2.22
!!!!!!!!!!!!!!!!!!!!!!!!!!
N)[N]?


(1132135975) Thu Mar 13 10:12:55 2014

Go to Step 13

Go to Step 14
serial cable.

no]?

serial cable.

serial cable.


element connection. If the GNM terminal will be used to verify the XCM craft Ethernet port IP connectivity:
minal IP address.





Note: Infinera GNM may be launched from the Ethernet craft port of an XCM using the craft Ether-
net port IP address.
sage is displayed.

Step 2 In the browser, enter the XCM Craft Ethernet Port IP address of the target XTC. Infinera GNM is
launched in a new window and the Login window is displayed.




Software
Version



displayed.


Step 6 Click OK.



Step 11 Click OK.
face.

Note: Ensure that the DTC/MTC and/or OTC Expansion Chassis has been initially commissioned
prior to performing this procedure. Refer to “DTC/MTC Expansion Chassis Turn-up” on
page 13-2 and/or “OTC Expansion Chassis Turn-up” on page 16-2.
tunable line modules. The line modules are optically connected between the XTC and a DTC/MTC (BMM/
BMM2/BMM2P/BMM2H) and/or OTC (BMM2C).


Step 9 Click Close.
Unlock.
on page 4-34.
Tunable tab
Operating Mode
Provisioned OCG
Number

mode.
BMM2H).
“To connect OCG cables between XTC line modules and DTC/MTC BMM/BMM2/BMM2P/BMM2Hs”
on page C-6
page C-13

tem mode.
Step 4 Click Apply.
Step 5 Click Close.

General tab
Connected BMM port

Tx Auto Discovery
State
and repeat Step 1 through Step 3. In certain cases, it may be necessary to manually
initiate Auto-discovery, see “To manually initiate line module Auto-discovery” on page 4-36.
Step 9 Click Close.

General tab
Connected BMM port

Tx Auto Discovery
State


Line Modules
mode.
page 4-39
on page 4-41
Threshold

.BMM2H/BMM2C
BMM2C



(OPR).
(OPT).

BMM2H, or BMM2C.


(OPR).
(OPT).


System Mode
changeably.
Wave.


General tab
Line System Mode

Provisioned Peer TP

visioned Remote TP Selection dialog is displayed. See Figure 4-24 on page 4-44.
List frame

List frame
Provisioned Peer TP
Target Tx OCG Power
Channel Count
Step 13 Click Ok.

Unlock.


changeably.
26.

management traffic for nodes without access to the OSC such as in Open Wave line system mode or SLTE
applications. For each IGCC, an associated GMPLS control channel (GMPLSCC) is created (similar to the
GMPLSCC associated with the OSC channel). The GMPLSCC carries control traffic to bring up the control
link. Refer to the Infinera DTN and DTN-X System Description Guide for additional information.


OLM AID GCC Type
IP Address
Net Mask
List frame

Step 7 Click Apply.
Step 8 Click Close.

Note: The IP address entered in this field is the Router ID (GMPLS Node ID) of the Primary GNE,
not the DCN IP address of the Primary GNE.
Note: The IP address entered in this field is the Router ID (GMPLS Node ID) of the Secondary
GNE, not the DCN IP address of the Secondary GNE.
Step 6 Click Apply.

Summary panel
IP Gateway Proxy
GNE tab
Primary and
Secondary GNE
IP Addresses

Note: The following procedure provides an example of the creation of an Unprotected, 100GbE
LAN, Add/Drop cross-connect type. For detailed information regarding the creation of other
supported cross-connect types, refer to the Infinera GNM Service Provisioning Guide.

TOM and select Provisioning -> Cross-connect Manager. The Cross-connect Manager is
displayed in the Workspace Area. Click New
select Provisioning -> Cross-connect Manager. The Cross-connect Manager is displayed
in the Workspace Area. Click New

Service type
Service rate
(payload type)
Connectivity type
(for example, select Add/Drop).

Circuit ID (CID)
Label
Source Endpoint
Intermediate LM
Destination
Endpoint



Source Endpoint—the source endpoint of the cross-connect. Click the [...] button to view
a list of the valid termination points displayed as AIDs. The Endpoint Source window is dis-
played along with a list of multipoint cross-connects. Select the source endpoint and click Ok
click Ok
Step 9 Click Ok.



CAUTION





Verifying Inventory
To verify equipment



XTC:
Testing TOMs

Testing TIMs
Testing XICMs

Step 1 Examine the LEDs on each line module/OTM-500/OTM2-500 on the XTC. The FLT LED is illu-
minated if an alarm exists. If a line module/OTM-500/OTM2-500 has an alarm, view the Alarm
Testing OXMs

Testing TSMs
Testing XCMs
agement interfaces.


the XTC.

Alarm Filter panel

Alarm Severity
to customers.
cautions.

Alarm Type Cause

Shutdown (ALS).
Group.
side) have light.




11 N/C N/A N/A
12 N/C N/A N/A
13 N/C N/A N/A


45 N/C N/A N/A
46 N/C N/A N/A
47 N/C N/A N/A



Alarm Cutoff (ACO)

operated remotely through the Infinera GNM interface. When the ACO is enabled, all the outstanding
audio alarms are turned off and the ACO LED on the chassis is illuminated. The ACO LED indicates that
one or more audible alarms are present, but the audible indicators have been muted. The ACO LED is
turned off when the silenced audible alarms are cleared. The alarm acknowledgment by the user does not
change the ACO LED state.

To enable an ACO
tons).
Testing an ACO
to be audible.
To test an ACO


node configuration.
Expansion Chassis.

procedure.

CHAPTER 5
Turning up an XTC as an Expansion

Chassis
This chapter provides the procedures to turn up and test an XTC as an Expansion Chassis and is
organized into the following sections:
“XTC Expansion Chassis Turn-up” on page 5-2
“Configuring DTN-Xs for Preamplifier Configuration” on page 5-61

Page 5-2 XTC Expansion Chassis Turn-up
XTC Expansion Chassis Turn-up

The XTC is available in the following options:

specifications.

Turning up an XTC as an Expansion Chassis Page 5-3
PEMs PEM Shelf
IOTAP
Fan Tray 1
Fan Tray 2
Fiber Tray
TIMs/XICMs TSM-X10
OTM2-500s
Upper Universal
TIMs/XICMs
Universal Blank XCM
Fiber Tray

Card Slots
Fiber Tray
Air Filters
Air Inlet Plenum
Fiber Tray
XCM
Line Modules
TIM Blanks
TIMs/XICMs
Lower Universal
Card Slots
OTM-500s/OTM2-500s
TSM-X10
Fiber Tray
Fan Tray 3
Fan Tray 4

PEMs
XCMs
TAP I/O Panel
Fiber Trays
OTM-500s/OTM2-500s
Line Modules
TSM-X4
OXM-X4s
TIMs/XICMs
TIM Blanks
Fiber Tray
Fan Tray 1
Fan Tray 2
Air Filter

Tasks
Table 5-1 XTC Expansion Chassis Turn-up Checklist and Test Results

5-6
5-10
Expansion Chassis“ 5-12
“Installing XTC Multi-chassis NC page
Ethernet Cables“ 5-14
5-30
“Creating an Expansion Chassis“ page
5-33
5-35
Completion“ 5-38
ules“
for IGCC“ 5-51
5-53
Port“ 5-59
5-60

CAUTION


position).

WARNING
WARNING
WARNING
breakers to ON.
ers to OFF.

WARNING
breakers to ON.

Terminal studs

ON ON
OFF OFF
infn_888

Powering up the XTC

Initial Start-up
information.
To startup the XTC
CAUTION
ers to ON.
ers to ON.
LED OFF



Initial Commissioning for the XTC Expansion Chassis
the XTC. Wait for the following message to be displayed:
then press Enter.
To initially commission the Expansion Chassis

Step 1 Main Chassis - [yes|no](yes)?—Type no.
Step 2 At Do you want to change system time, verify the time. Make any necessary adjustments and
select yes or select no to leave the system time. The system should be set to local time.

The output of the information in the above steps is listed below.
Main Chassis[yes|no] (yes) ? no
Do you want to change system date and time (2014/03/13 09:39:01) (Y/N)
[N]?
ReInitialize SC [Delete database/nodeid/shelfid] ?[yes|no] (no) ? yes
changes. The output of the information in this step is listed below.

serial cable.
This will allow system software to be pushed from the Main Chassis to the newly created Expansion
Chassis. Note that this process will take approximately 10 minutes to complete. During this process, the
fault LED on the Expansion Chassis will be flashing Red (indicating that the download is still in progress).
up process. When the PWR and ACT LEDs are all lit solid Green the XCM has completed booting up. This
indicates the XCM is operational (and safe to remove the serial cable).

Installing XTC Multi-chassis NC Ethernet Cables

In a multi-chassis configuration, chassis are interconnected at the nodal control (NC) ports of the
XCM/IMMs using straight-through unshielded twisted pair CAT6 Ethernet cables that conform to
100BaseTX (IEEE 802.3) specifications, with male RJ-45 connectors at both ends. The maximum length
allowed for each NC cable segment between chassis is 328 feet (100 meters). A third-party Ethernet
media converter can be used for connecting NC ports to support extended distances. Contact your Infinera
account team for assistance with third-party Ethernet media converters.
Note: When using a third-party Ethernet media converter, ensure that the set-up parameters on
the media converter are configured for the following:
Full-duplex mode
Auto-negotiation
100Mbps port speed
If an option for crossover or straight-through is provided, select straight-through
Ensure that straight-through (not crossover) CAT6 Ethernet cables are used for all NC
connections. Refer to the documentation supplied with the third-party Ethernet media con-
verter for additional information.
The Main Chassis cannot be pre-provisioned, and must be provisioned during network element turn-up.
Expansion Chassis may be pre-provisioned. The physical connection of NC cables may be made prior to
provisioning the chassis, or after pre-provisioning the chassis.
Release 10.0 certifies a DTN-X multi-chassis configuration consisting of up to 60 interconnected chassis
(up to 10 XTCs, up to 6 MTC-9s, up to 32 DTC/MTCs, and up to 12 OTCs). The Main Chassis must be an
XTC but the Expansion Chassis can be any combination of XTC/MTC-9/DTC/MTC/OTCs.
Note: When interconnecting multiple XTCs with MTC-9s, DTC/MTCs and/or OTCs, ensure that all
XTCs are interconnected together (first), followed by (in any particular order): MTC-9s,
DTC/MTCs, and/or OTCs. For example, if you are interconnecting a multi-chassis network
element consisting of 2 XTCs, 1 MTC-9, 2 DTCs, and 2 OTCs, the interconnect order can
be: XTC-XTC-MTC-9-DTC-DTC-OTC, or XTC-XTC-DTC-DTC-OTC-MTC-9, etc.
Refer to “Installing MTC-9 Multi-chassis NC Ethernet Cables” on page 9-9 for MTC-9 multi-chassis
configurations consisting of MTC-9/OTCs. This section is organized as follows:
“Dual-chassis Configuration NC Cabling” on page 5-15
“Multi-chassis Configuration NC Cabling” on page 5-22
Note: Although there are many ways to interconnect multiple chassis, the following recommended
configurations provide the greatest level of redundancy, capacity, and management/control
plane availability.

Dual-chassis Configuration NC Cabling
Note: Although there are many ways to interconnect multiple chassis, the following recom-
mended configurations provide the greatest level of redundancy, capacity, and manage-
ment/control plane availability.
This section contains the following procedures:

“To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) with full XCM redundancy” on page 5-
15
“To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) with full XCM redundancy” on
page 5-17
“To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) with XCM redundancy only on Main
Chassis” on page 5-18
“To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) with XCM redundancy only on
Main Chassis” on page 5-19
“To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) non-redundant XCMs” on page 5-20
“To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) non-redundant XCMs” on page 5-

21
To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) with full XCM redundancy
In the procedure below, the following convention is used to specify NC ports on a particular XTC/MTC-9
chassis:
[ChassisID]-NC-[PortNumber] [Active (ACT) or Standby (STBY) controller]
For example, NC port 1 on chassis 1 with the Active XCM is specified as 1-NC-1 ACT.
Step 1 Connect 1-NC-1 ACT to 2-NC-2 ACT.
Step 2 Connect 1-NC-2 ACT to 2-NC-1 STBY.
Step 3 Connect 1-NC-1 STBY to 2-NC-2 STBY.
Step 4 Connect 1-NC-2 STBY to 2-NC-1 ACT.
The final logical connectivity is shown in Figure 5-4 on page 5-16.

Figure 5-4 NC Connectivity for Dual-chassis (XTC-to-XTC.MTC-9) with Full XCM Redundancy
XTC
Chassis 1
XCM Active (ACT) XCM Standby (STBY)
NC 1 NC 1
NC 2 NC 2
XTC/MTC-9
Chassis 2
XCM/IMM ACT XCM/IMM STBY
NC 1 NC 1
NC 2 NC 2
Nodal Control (NC) Cable Connection infn_924

To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) with full XCM redundancy
In the procedure below, the following convention is used to specify NC ports on a particular XTC chassis
and NCT ports on a particular DTC/MTC/OTC chassis:
 On the XTC: [ChassisID]-NC-[PortNumber] [Active (ACT) or Standby (STBY) controller].
For example, NC port 1 on chassis 1 with the Active XCM is specified as 1-NC-1 ACT
 On the DTC/MTC/OTC: [ChassisID]-NCT-[PortNumber][A|B].
For example, NCT port 1A on chassis 2 is specified as 2-NCT-1A
Step 1 Connect 1-NC-1 ACT to 2-NCT-2A.
Step 2 Connect 1-NC-2 ACT to 2-NCT-1B.
Step 3 Connect 1-NC-1 STBY to 2-NCT-2B.
Step 4 Connect 1-NC-2 STBY to 2-NCT-1A.
The final logical connectivity is shown in Figure 5-5.
Figure 5-5 NC Connectivity for Dual-chassis (XTC-to-DTC/MTC/OTC) with Full XCM Redundancy
XTC
Chassis 1
NC 1 NC 1
NC 2 NC 2
DTC/MTC/OTC
I/O Panel or I/O Alarm Panel

NCT 2A NCT 1A NCT 2B NCT 1B
Chassis 2
MCM MCM
in 7A in 7B
or CPU or CPU
OMM OMM
in 1A in 1B
Switch/ Switch/
Router Router
Nodal Control (NC/NCT) Cable Connection

infn_1137

To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) with XCM redundancy only on Main
Chassis
chassis:
Main Chassis
Chassis 1 XTC
NC 1 NC 1
NC 2 NC 2
Chassis 2 XTC/MTC-9
XCM/IMM ACT
NC 1
NC 2

To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) with XCM redundancy only on Main
Chassis
 On the DTC/MTC/OTC: [ChassisID]-NCT-[PortNumber][A|B]
Main Chassis
XTC
Chassis 1
NC 1 NC 1
NC 2 NC 2
DTC/MTC/OTC
Chassis 2
MCM
in 7A
or CPU
OMM
in 1A
Switch/
Router

infn_1138

To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) non-redundant XCMs
chassis:
Figure 5-8 NC Connectivity for Dual-chassis (XTC-to-XTC/MTC-9) Non-redundant XCMs
XTC
Chassis 1
XCM Active (ACT)
NC 1
NC 2
XTC/MTC-9
Chassis 2
XCM/IMM ACT
NC 1
NC 2
Nodal Control (NC) Cable Connection

infn_926

To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) non-redundant XCMs
Figure 5-9 NC Connectivity for Dual-chassis (XTC-to-DTC/MTC/OTC) Non-redundant XCMs
XTC
Chassis 1
XCM Active (ACT)
NC 1
NC 2
DTC/MTC/OTC

Chassis 2
MCM
in 7B
or CPU
OMM
in 1B
Switch/
Router

infn_1139

Multi-chassis Configuration NC Cabling
plane availability.

“To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9) with full XCM redundancy” on page 5-
22
“To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9/DTC/MTC/OTC) with full XCM redun-
dancy” on page 5-24
“To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9) with XCM redundancy only on Main
“To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9/DTC/MTC/OTC) with XCM redun-
dancy only on Main Chassis” on page 5-28
Note: When interconnecting multiple XTCs with MTC-9s, DTC/MTCs and/or OTCs, ensure that all
XTCs are interconnected together (first), followed by (in any particular order): MTC-9s,
To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9) with full XCM redundancy
In the procedure below, the following convention is used to specify NC ports on a particular chassis:
For example, NC port 1 on chassis 1 with the Active XCM is specified as 1-NC-1 ACT. The last chassis in
the configuration is referred to as chassis n.
Step 2 Connect 2-NC-1 ACT to n-NC-2 ACT.
Step 3 Connect n-NC-1 ACT to 1-NC-2 STBY.
Step 5 Connect 2-NC-1 STBY to n-NC-2 STBY.
Step 6 Connect n-NC-1 STBY to 1-NC-2 ACT.
The final logical connectivity is shown in Figure 5-10 on page 5-23 where full XCM redundancy is available
on every chassis on the network element.

Figure 5-10 NC Connectivity for Multi-chassis (XTC-to-XTC/MTC-9) with Full XCM Redundancy
XTC
Chassis 1
NC 1 NC 1
NC 2 NC 2
XTC/MTC-9
Chassis 2
NC 1 NC 1
NC 2 NC 2
XTC/MTC-9
Chassis n
NC 1 NC 1
NC 2 NC 2
Note: The last chassis in the configuration is referred to as chassis n.

To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9/DTC/MTC/OTC) with full XCM

redundancy
chassis and NCT ports on a particular DTC/MTC/OTC chassis:
 On the XTC/MTC-9: [ChassisID]-NC-[PortNumber] [Active (ACT) or Standby (STBY) controller].
For example, NCT port 1A on chassis n is specified as n-NCT-1A. The last chassis in the configura-
tion is referred to as chassis n.
Step 2 Connect 1-NC-2 ACT to n-NCT-1B.
Step 4 Connect 1-NC-2 STBY to n-NCT-1A.
Step 5 Connect 2-NC-1 ACT to n-NCT-2A.
Step 6 Connect 2-NC-1 STBY to n-NCT-2B.


Redundancy
XTC
Chassis 1
NC 1 NC 1
NC 2 NC 2
XTC/MTC-9
XCM/IMM Active (ACT) XCM/IMM Standby (STBY)

Chassis 2
NC 1 NC 1
NC 2 NC 2
DTC/MTC/OTC
Chassis n
MCM MCM
in 7A in 7B
or CPU or CPU
OMM OMM
in 1A in 1B
Switch/ Switch/
Router Router
Nodal Control (NC/NCT) Cable Connection infn_1267

To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9) with XCM redundancy only on Main
Chassis
chassis:
on chassis 1 (Main Chassis) only.

Main Chassis
XTC
Chassis 1
NC 1 NC 1
NC 2 NC 2
XTC/MTC-9
Chassis 2
XCM/IMM ACT
NC 1
NC 2
XTC/MTC-9
Chassis n XCM/IMM ACT
NC 1
NC 2

To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9/DTC/MTC/OTC) with XCM redundancy

only on Main Chassis


Redundancy only on Main Chassis
XTC
Chassis 1
NC 1 NC 1
NC 2 NC 2
XTC/MTC-9
XCM/IMM Active (ACT)

Chassis 2
NC 1
NC 2
DTC/MTC/OTC
Chassis n
MCM
CPU
in 7A
or
Nodal Control (NC/NCT) OMM
Switch/
Cable Connection Router in 1A
infn_1268

Expansion Chassis.
sage is displayed.




Creating an Expansion Chassis

Perform the following procedure to create an Expansion Chassis.
To create an Expansion Chassis
Step 1 In the Infinera GNM interface, from the Equipment tree, click the Discovered Chassis icon. The
newly commissioned expansion chassis serial number is displayed. See Figure 5-17.
Figure 5-17 Create Chassis
Discovered
Chassis
Serial Number
Step 2 Right-click on the serial number and select Add. The Create Chassis window is displayed. See
Figure 5-18 on page 5-34.

Step 3 Click the Chassis Type drop-down menu and select a Chassis Type (DTC, DTC-A, DTC-B,
MTC-A, OTC, XTC-10, or XTC-4) to create.
Figure 5-18 Select Chassis Type
Step 4 In the Chassis ID field, enter a Chassis ID (1 - 63).

Step 5 Click Apply. A success confirmation dialog is displayed.
Step 6 Click Ok.
Step 7 Click Close.

BMM2/BMM2P/BMM2H) or OTC (BMM2C).


Step 9 Click Close.
Unlock.
on page 5-37.
Tunable tab
Operating Mode
Provisioned OCG
Number

mode.
BMM2H).
“To connect OCG cables between XTC line modules and DTC/MTC BMM/BMM2/BMM2P/
BMM2Hs” on page C-6
page C-13

tem mode.
Step 4 Click Apply.
Step 5 Click Close.

General tab
Connected BMM port

Tx Auto Discovery
State
and repeat Step 1 through Step 3. In certain cases, it may be necessary to manually
initiate Auto-discovery, see “To manually initiate line module Auto-discovery” on page 5-39.
Step 9 Click Close.

State tab
Administrative
State
Start Auto-Discovery


Line Modules
mode.
page 5-42
on page 5-44
Threshold

.BMM2H/BMM2C
BMM2C



(OPR).
(OPT).

BMM2H, or BMM2C.


(OPR).
(OPT).


System Mode
changeably.
Wave.


General tab
Line System Mode

Provisioned Peer TP

visioned Remote TP Selection dialog is displayed. See Figure 5-27 on page 5-47.
List frame

List frame
Provisioned Peer TP
Target Tx OCG Power
Channel Count
Step 13 Click Ok.

Unlock.


changeably.
26.

management traffic for nodes without access to the OSC such as in Open Wave line system mode or
SLTE applications. For each IGCC, an associated GMPLS control channel (GMPLSCC) is created (similar
to the GMPLSCC associated with the OSC channel). The GMPLSCC carries control traffic to bring up the
control link. Refer to the Infinera DTN and DTN-X System Description Guide for additional information.


OLM AID GCC Type
IP Address
Net Mask
List frame

Step 7 Click Apply.
Step 8 Click Close.

Note: The following procedure provides an example of the creation of an Unprotected, 100GbE,
Express cross-connect type. For detailed information regarding the creation of other sup-
ported cross-connect types, refer to the Infinera GNM Service Provisioning Guide.

TOM and select Provisioning -> Cross-connect Manager. The Cross-connect Manager
is displayed in the Workspace Area. Click New
select Provisioning -> Cross-connect Manager. The Cross-connect Manager is dis-
played in the Workspace Area. Click New

Service type
Service rate
(payload type)
Connectivity type
(for example, select Express).

Circuit ID (CID)
Label
Source Endpoint
Intermediate LM
Destination
Endpoint



Ok
click Ok
Step 9 Click Ok.



CAUTION





Configuring DTN-Xs for Preamplifier

Configuration
Infinera strongly recommends the use of bend insensitive fiber (BIF) for all fiber connections (whenever
possible). BIF cables provide greater resistance to bending losses due to excessive bends in the fiber
cables (compared to non-BIF cables), and are identified by a Blue cable jacket. Contact your Infinera
account team and/or an Infinera TAC resource for additional information. Always clean and label fiber
optics before use, and observe the safety precautions outlined in “Laser Safety” on page 1-13.
CAUTION
Risk of exposure to invisible radiation.
Do not view the fibers and optical connectors directly with optical instruments. Class 1
and Class 1M.
CAUTION
Raman modules generate large and potentially dangerous optical power levels. Ensure
that you are familiar with the safety procedures described in “Observing Safety Proce-
dures” on page 1-1.
CAUTION
Raman gain is dependent on fiber type and sensitive to fiber plant issues. Ensure that you
are familiar with the fiber cleaning procedures described in “Raman Fiber Connector Clean-
ing” on page D-1.
CAUTION
Using attenuator pads not approved by Infinera can result in physical damage to the Line
port of an OAM/ORM. Contact your Infinera account team and/or an Infinera TAC resource
to obtain information regarding Infinera approved attenuator pads.
A line system configuration with a preamplifier is supported at a DTN-X site to provide a longer reach
across a digital span by improving the optical add/drop multiplexer (OADM) performance of the Infinera
Intelligent Transport Network.

Page 5-62 Configuring DTN-Xs for Preamplifier Configuration
Table 5-3 lists the required modules for a DTN-X with a preamplifier configuration.
Table 5-3 DTN-X Preamplifier Configuration
Node Type Main Module Booster Module Preamplifier Module
DTN-X BMM2P-8-CH1-MS Not supported Any one of the following:

• OAM-CXH1-MS
• OAM-CXH2-MS
• OAM-CXH3-MS
• ORM-CXH1-MS
• ORM-CXH1
OAM-CXH1-MS + RAM-2-OR
Note: Preamplifier modules must be associated with the main module (from the management
interfaces) to provide preamplifier functions for the required digital span(s). Otherwise,
Infinera’s Automated Gain Control (AGC) will not function along the span(s).
Minimum Equipment Configuration

Before proceeding with the turn-up and test, ensure that all nodes involved in the configuration have been
initially commissioned as Main Chassis and Expansion Chassis where applicable:
 Main Chassis - XTC turned up as a Multi-chassis network element with one line module
(AOLM-500/AOLM-500B/AOLX-500/AOLX-500B) installed, and Auto-discovery completed
 Expansion Chassis - DTC turned up as a Multi-chassis network element with one
BMM2P-8-CH1-MS and one line module (ADLM/AXLM) installed, and Auto-discovery completed
 Expansion Chassis - OTC turned up as a Multi-chassis network element with one OAM-CXH1-MS
and one RAM-2-OR installed, and Auto-discovery completed
To turn up a DTN-X with an OAM-CXH1-MS preamplifier and RAM-2-OR configuration
Note: This procedure assumes that all nodes have been initially commissioned as outlined in
“Minimum Equipment Configuration” on page 5-62.
Note: For information on additional preamplifier configurations supported on the DTN-X, refer to
“Configuring DTNs for Preamplifier Configuration” on page 13-93.
Figure 5-37 on page 5-63 shows an example configuration of a DTN-X with an OAM-CXH1-MS
preamplifier and RAM-2-OR.

Figure 5-37 Example Configuration of a DTN-X with an OAM-CXH1-MS Preamplifier and RAM-2-OR
OTC
OMM OMM
Line Line
Out OSC In
In Out
OAM-CXH1-MS
To BMM/OAM Line
Out RAM-2-OR In Transmission
Fiber
In Out
Expansion Chassis
XTC Main Chassis Expansion Chassis
DTC
TIM
Line Module
BMM2P
TSM
TAM
In
MCM
Out
TIM
OTM-500/OTM2-500
TAM
IN OUT In Out
Line Connectors
Out In
TIM
Expansion Port Connectors

TAM
In Out
DCM Connectors
Out In
Out In
Out In
TAM
XCM
TIM
ADLM/AXLM
MCM
Out In
OCG Out In
Connectors Out In
TAM
Out In
TIM
Out In
infn_1068a
Step 1 Launch Infinera GNM and establish GNM connectivity with all nodes in the configuration. Refer
to “Launching Infinera GNM” on page 5-30.
Note: The Infinera GNM window should be kept open until this procedure is complete. In addition,
refer to Figure 5-37 while performing this procedure.

Step 2 Create the association between the BMM2P-8-CH1-MS and the OAM-CXH1-MS. At the DTC
Expansion Chassis:
Step 2a Lock the BMM2P in slot 1. From the Infinera GNM Equipment View, right-click the
BMM2P and select Admin State -> Lock.
Step 2b From the Equipment View, highlight the appropriate BMM2P to be configured, right-
click and select Span. The Span Properties window is displayed. See Figure 5-38.
Step 2c In the Association panel, click on Rx Associated OTS AID and select the appropri-
ate OAM OTS AID that is connected to the BMM2P Line In (Rx) connector.
Step 2d Click Apply.
Step 2e A warning message is displayed. Click Continue.
Step 2f Click Close.
Figure 5-38 Setting the DTN-X with OAM-CXH1-MS Preamplifier Association
Span/C-Band tab
Association panel
Rx Associated
OTS AID

Step 3 Verify the association between the BMM2P-8-CH1-MS and the OAM-CXH1-MS. At the DTC
Expansion Chassis:
Step 3a From the Equipment View, highlight the appropriate BMM2P to be configured, right-
Step 3b In the Association panel, verify that the OAM-CXH1-MS is listed in the Rx Associated
OTS Eqpt box.
Step 3c Click Close.
Figure 5-39 Verifying the DTN-X with OAM-CXH1-MS Preamplifier Association
Span/C-Band tab
Association panel
Rx Associated
OTS Eqpt

Step 4 Create the association between the RAM-2-OR connector ports (L1 Transmit and L2 Receive) to
associate them with the correct BMM/OAM OTS ports as listed in Table 17-2 on page 17-15. At
the OTC Expansion Chassis:
Step 4a Lock the RAM-2-OR in slot 2. From the Infinera GNM Equipment View, right-click the
RAM-2-OR and select Admin State -> Lock.
Step 4b From the Equipment View, highlight the appropriate RAM-2-OR to be configured,
right-click and select Span. The Span Properties window is displayed. See
Step 4c In the list frame, ensure that L1 OTS ID is highlighted. See Figure 5-40 on page 5-67.
Step 4d From the tabs listed in the middle of the window, select the Span/C-Band tab.
Step 4e In the BMM/OAM Association panel, click on Tx Associated OTS and select the
appropriate OAM OTS ID from the drop-down menu. For example, select the OAM
OTS AID that is connected to the RAM-2-OR L1 Tx (To BMM/OAM) connector.
Step 4f Click Apply.
Step 4g In the list frame, ensure that L2 OTS ID is highlighted. See Figure 5-41 on page 5-68.
Step 4h From the tabs listed in the middle of the window, select the Span/C-Band tab.
Step 4i In the Peer OTS Association panel, click on Rx Associated OTS and select the
appropriate BMM OTS ID from the drop-down menu. For example, select the BMM
OTS AID that is connected to the RAM-2-OR L2 RX (BMM/OAM In) connector.
Step 4j Click Apply.
Step 4k Click Close.

Figure 5-40 Setting the RAM-2-OR L1 Association
List frame (L1 selected)
Span/C-Band tab
BMM/OAM Association panel
Tx Associated OTS

Span/C-Band tab
Peer OTS Association panel
Rx Associated OTS
Step 5 At the DTC Expansion Chassis: provision the fiber type for the BMM2P-CH1-MS. Refer to
“Provisioning Fiber Information” on page 13-81.
Step 6 At the OTC Expansion Chassis: provision the fiber type for the OAM-CXH-MS. Refer to
“Entering DCM/PSE/DSE Information” on page 16-24.
Step 7 At the OTC Expansion Chassis: verify the RAM-2-OR L1 association on the OAM-CXH1-MS and
the L2 association on the BMM2P-CH1-MS.
Step 7a From the Equipment View, highlight the configured OAM-CXH1-MS, right-click and
select Span. The Span Properties window is displayed. See Figure 5-42 on page 5-
69.
Step 7b From the tabs listed in the middle of the window, select the Span/C-Band tab.
Step 7c In the Raman Association panel, verify that the Rx Associated OTS AID selected in
Step 4 is now grayed out. See Figure 5-42 on page 5-69.
Step 7d In the Raman Association panel, verify that the Tx Associated OTS AID selected in
Step 7e Click Close.

Figure 5-42 Verifying the RAM-2-OR L1 and L2 Association
Span/C-Band tab
Raman Association panel

Rx Associated OTS AID (grayed out)
Tx Associated OTS AID (grayed out)
Step 8 Check the fiber connectors for cleanliness, refer to “Raman Fiber Connector Cleaning” on
page D-1. Then install clean, labeled, fiber optic cables at the DTN-X between the Main and
Expansion Chassis as follows:
Step 8a Connect the DTC BMM2P Slot 1 Line Out port to the OTC RAM-2-OR Slot 2
BMM/OAM In port.
Step 8b Connect the OTC RAM-2-OR Slot 2 BMM/OAM Out port to the OTC OAM-CXH1-MS
Slot 1 Line In port.
Step 8c Connect the OTC OAM Slot 1 OSC Out port to the OSC In port.
Step 8d Connect OTC OAM-CXH1-MS Slot 1 Line Out port to the DTC BMM2P Slot 1 Line In
port.
Step 8e Connect the OTC RAM-2-OR Slot 2 Line Out port to the outgoing transmission fiber.
Step 8f Connect the incoming transmission fiber to the OTC RAM-2-OR Slot 2 Line In port.
Step 8g Connect the OCG fiber optic cables between the XTC line module and the DTC
BMM2P, proceed to “To connect OCG cables between XTC line modules and DTC/
MTC BMM/BMM2/BMM2P/BMM2Hs” on page C-6.
Step 9 At the DTC Expansion Chassis: unlock the BMM2P in slot 1. From the Infinera GNM Equipment
View, right-click the BMM2P and select Admin State -> Unlock.

Step 10 At the OTC Expansion Chassis: unlock the RAM-2-OR in slot 2.

Step 10a From the Equipment View, right-click the RAM-2-OR and select
Admin State -> Unlock.
Step 10b Wait 3 minutes before proceeding to allow the Raman pumps to turn on and stabilize.
Note: Raman modules will receive fiber type information automatically from the system software
when the C-Band traffic is turned on.
Step 11 At the OTC Expansion Chassis: initiate the Raman point loss offset (PLO) adjustment utility, see
“Setting the Point Loss Offset for Raman Modules” on page 17-62.
Note: Refer to Table 17-10 on page 17-21 for allowable maximum point loss range for
RAM-2-ORs based on fiber type.


XTC:
Testing TOMs

Testing TIMs
Testing XICMs

Step 1 Examine the LEDs on each line module/OTM-500/OTM2-500 on the XTC. The FLT LED is illu-
minated if an alarm exists. If a line module/OTM-500/OTM2-500 has an alarm, view the Alarm
Testing OXMs

Testing TSMs
Testing XCMs
agement interfaces.


the XTC.

Alarm Filter panel

Alarm Severity
to customers.
cautions.

Alarm Type Cause

Shutdown (ALS).
Group.
side) have light.




11 N/C N/A N/A
12 N/C N/A N/A
13 N/C N/A N/A


45 N/C N/A N/A
46 N/C N/A N/A
47 N/C N/A N/A



Alarm Cutoff (ACO)

operated remotely through the Infinera GNM interface. When the ACO is enabled, all the outstanding
audio alarms are turned off and the ACO LED on the chassis is illuminated. The ACO LED indicates that
one or more audible alarms are present, but the audible indicators have been muted. The ACO LED is
turned off when the silenced audible alarms are cleared. The alarm acknowledgment by the user does not
change the ACO LED state.

To enable an ACO
tons).
Testing an ACO
to be audible.
To test an ACO

CHAPTER 6
Turning up a DTN-X ROADM Multi-

chassis Network Element
This chapter provides the procedures to turn up and test a DTN-X colorless, directionless, and
contentionless (CDC) Reconfigurable Optical Add/Drop Multiplexer (ROADM) network element, or a
DTN-X colorless ROADM multi-chassis network element and is organized into the following sections:
“DTN-X ROADM Turn-up and Test Overview” on page 6-2

Page 6-2 DTN-X ROADM Turn-up and Test Overview
DTN-X ROADM Turn-up and Test Overview

Note: Unless specifically noted otherwise, all references to the “FlexChannel line module” will
refer to the AOFM-500, AOFM-500B, AOFX-500, and/or AOFX-500B interchangeably.
In Release 10.0, a DTN-X multi-chassis network element (a network element with an XTC as a Main
Chassis) can be configured with an MTC-9 Expansion Chassis to provide CDC or colorless ROADM
functionality. For additional information, refer to the Infinera DTN and DTN-X System Description Guide.
This section contains the following:
“DTN-X CDC ROADM Configuration” on page 6-2
“Minimum Equipment Configuration” on page 6-3
“DTN-X Colorless ROADM Configuration” on page 6-4
DTN-X CDC ROADM Configuration

Figure 6-1 on page 6-3 shows an example of a DTN-X CDC ROADM configuration.

Turning up a DTN-X ROADM Multi-chassis Network Element Page 6-3
Figure 6-1 Example Configuration of a DTN-X CDC ROADM
XTC
AOFX-500s
AOFM-500/
SCh
IN/OUT
Main Chassis
FSM 5 FRM 1
FPC (with FSP-S)
SYSTEM
IN
LINE ADD/DROP
OUT IN/OUT
PORTS
MTC-9
IAM
LINE
FSM IN/OUT
SYSTEM LINE
LINE FRM IN/OUT IN/OUT
IN IAM
SYSTEM infn_1285
OUT Expansion Chassis

 Main Chassis (XTC-10/XTC-4 base chassis) with one (or more) tunable FlexChannel line modules
(AOFM-500/AOFM-500B/AOFX-500/AOFX-500Bs) installed
Note: A base XTC-10 chassis contains at least one XCM, one TSM-X10, and nine OXM-X10s.
A base XTC-4 chassis contains at least one XCM, one TSM-X4, and five OXM-X4s.
 Expansion Chassis (MTC-9 base chassis) with one FlexROADM Switching Module (FSM), one
FlexROADM Module (FRM), and one Infinera Line System (ILS) Amplifier Module (IAM) or ILS
Raman Amplifier Module (IRM) installed
Note: A base MTC-9 chassis contains at least one Infinera Management Module (IMM).
A Fiber Panel Chassis (FPC) with one (or more) Fiber Shuffle Panel (FSP-S) modules

Page 6-4 DTN-X ROADM Turn-up and Test Overview
DTN-X Colorless ROADM Configuration

Figure 6-2 shows an example of a DTN-X Colorless ROADM configuration.
Figure 6-2 Example Configuration of a DTN-X Colorless ROADM
XTC
AOFX-500s
AOFM-500/
SCh
IN/OUT
Main Chassis
SYSTEM FPC (with FSP-C)

IN
LINE LINE AD
OUT IN/OUT IN/OUT
MTC-9
IAM
SYSTEM LINE
FRM IN/OUT IN/OUT
LINE
IN IAM
SYSTEM
OUT Expansion Chassis infn_1286

 Main Chassis (XTC-10/XTC-4 base chassis) with one (or more) tunable FlexChannel line modules
(AOFM-500/AOFM-500B/AOFX-500/AOFX-500Bs) installed
 Expansion Chassis (MTC-9 base chassis) with one FRM, and one IAM or IRM installed
Note: A base MTC-9 chassis contains at least one IMM.
An FPC with a minimum of one (or more) FSP-C modules


The XTC is available in the following options:

specifications.

PEMs PEM Shelf
IOTAP
Fan Tray 1
Fan Tray 2
Fiber Tray
TIMs/XICMs TSM-X10
OTM2-500s
Upper Universal
TIMs/XICMs
Universal Blank XCM
Fiber Tray

Card Slots
Fiber Tray
Air Filters
Air Inlet Plenum
Fiber Tray
XCM
Line Modules
TIM Blanks
TIMs/XICMs
Lower Universal
Card Slots
OTM-500s/OTM2-500s
TSM-X10
Fiber Tray
Fan Tray 3
Fan Tray 4

PEMs
XCMs
TAP I/O Panel
Fiber Trays
OTM-500s/OTM2-500s
Line Modules
TSM-X4
OXM-X4s
TIMs/XICMs
TIM Blanks
Fiber Tray
Fan Tray 1
Fan Tray 2
Air Filter

Tasks
Table 6-1 DTN-X Main Chassis Turn-up Checklist and Test Results
“DTN-X ROADM Turn-up and Test page

Overview“ 6-2
6-10
6-13
6-15
6-19
“Initial Commissioning for the XTC page (if applicable)
Main Chassis Gateway Network Ele- 6-21 NOTE: If you are initially commissioning the XTC
ment (GNE)“ for SNE, skip this task and proceed to the next.
“Initial Commissioning for the XTC page (if applicable)
Main Chassis Subtending Network 6-30 NOTE: If you have initially commissioned the
Element (SNE)“ XTC for GNE, skip this task and proceed to the
next.
“Verifying DCN IP Connectivity“ page (if applicable)
6-38 NOTE: If you have initially commissioned the
XTC for SNE, skip this task and proceed to the
next.
“Installing XTC Multi-chassis NC page
6-55
6-58


Port“ 6-63
6-64
6-65
“MTC-9 Expansion Chassis Turn-up“ page
9-2
“Configuring Tunable FlexChannel page
Line Modules“ 6-66
“Interconnecting the Tunable Flex- page
Channel Line Module to FRM/FSM 6-69
SCh Fibers“
“Creating a Fiber Panel“ page
6-70
“Interconnecting the FSP/FMP Fibers“ page
6-71
“Associating the FRM and FSM Ports page (if applicable)
on the Fiber Panel“ 6-72 NOTE: This task is only applicable if you are con-
figuring a DTN-X CDC ROADM.
“Associating the FRM Ports on the page (if applicable)
Fiber Panel“ 6-73 NOTE: This task is only applicable if you are con-
figuring a DTN-X colorless ROADM.
“Provisioning an Optical Cross-con- page
nect“ 6-74


end.
XCM.

COM1).


Active XCM
(PWR, NC, and
PWR
FLT ACT NC
CRAFT DCE
10/100/1000 BaseT
DATA
CRAFT
LINK
NCT1
C
XCM
NCT2
C
infn_930

XTC.
suggested.
desktop, choose Start > Control Panel > Network and Sharing Center > Change adapter
settings. Right-click Local Area Connection and select Properties. The Local Area Connec-
tion Properties window is displayed.

Step 2 Select Internet Protocol (TCP/IP Protocol), and click Properties. The Internet Protocol (TCP/
IP) Properties window is displayed.


Step 8 Click OK.
Step 9 Click Close.

CAUTION


position).

WARNING
WARNING
WARNING
breakers to ON.
ers to OFF.

WARNING
breakers to ON.

Terminal studs

ON ON
OFF OFF
infn_888

Powering up the XTC

Initial Start-up
are installed (fully seated) in the universal and switch fabric card cages of the XTC-10 and/or XTC-4
except for the standby XCM; the standby XCM (if equipped) is installed in a later task.
information.
To startup the XTC
CAUTION
ers to ON.
ers to ON.
LED OFF


packs installed on the chassis are lit (power LEDs illuminate Green, fault LEDs illumi-
nate Red, and all bi-color LEDs toggle between Green and Yellow).

Initial Commissioning for the XTC Main Chassis Gateway

previously or not.
 If the XCM was not commissioned previously, see “To initially commission the Main Chassis of a
GNE if the XCM was not commissioned previously” on page 6-21
 If the XCM was commissioned previously, see “To initially commission the Main Chassis of a GNE if
the XCM was commissioned previously” on page 6-25.
branding procedure.
To initially commission the Main Chassis of a GNE if the XCM was not commissioned previously
session:
then press Enter.



located.


Step 13 At Commit/Reconfigure/reBoot, type C to commit the information just entered, R to reconfig-
ure and repeat the steps in case a mistake was made, or B to reboot the XCM and discard the
changes.
Thu Mar 13 09:59:47 2014
The XCM boot process will stop at Do you want to go ahead with reconfiguration[yes|no].
Thu Mar 13 10:02:20 2014
Thu Mar 13 10:02:20 2014
Main Chassis : yes
NE Name : Node1
Router ID : 11.100.179.195
Dcn IP : 10.100.179.195

Dcn Netmask : 255.255.255.224

Shelf ID : 1
serial cable.
The XCM can take some time to complete the boot up process. When the PWR, NC, and ACT LEDs are all
lit solid Green the XCM has completed booting up. This indicates the XCM is operational (and safe to

To initially commission the Main Chassis of a GNE if the XCM was commissioned previously
session:
Main Chassis : yes
NE Name : Node_2
Router ID : 11.10.2.23
Dcn IP : 10.10.2.21
Dcn Netmask : 255.255.252.0
Shelf ID : 1
then press Enter.





ure and repeat the steps in case a mistake was made, or B to reboot the XCM and discard the
Router ID(11.10.2.23) ? 11.10.2.22
!!!!!!!!!!!!!!!!!!!!!!!!!!
Dcn IP(10.10.2.21) ? 10.10.2.20
Dcn Netmask(255.255.252.0) ?
N)[N]?
(1132135975) Thu Mar 13 10:12:55 2014



Go to Step 17

This operation (database re-branding) can be service impacting. Would
you like to continue[yes|no]?
Go to Step 18
serial cable.

no]?
serial cable.

serial cable.

Initial Commissioning for the XTC Main Chassis Subtending

Network Element (SNE)
GNM terminal.
previously or not.
 If the XCM was not commissioned previously, see “To initially commission the Main Chassis of an
SNE if the XCM was not commissioned previously” on page 6-31
 If the XCM was commissioned previously, see “To initially commission the Main Chassis of an SNE
if the XCM was commissioned previously” on page 6-33.
branding procedure.

To initially commission the Main Chassis of an SNE if the XCM was not commissioned previously
session:
then press Enter.




changes.
NE Name? Node1
Router ID? 11.10.2.22
Shelf ID[1-63]? 1
N)[N]?
Main Chassis : yes
NE Name : Node1
Router ID : 11.10.2.22
Shelf ID : 1
chassis_check: (127_1_3_1) (127_1_3_2) (127_2_3_1) (127_2_3_2).
boot up process may cause the XCM to hang and not boot up correctly. Ensure the boot up

To initially commission the Main Chassis of an SNE if the XCM was commissioned previously
session:
Main Chassis : yes
NE Name : Node_2
Router ID : 11.10.2.22
Dcn IP : 10.10.2.20
Shelf ID : 1
then press Enter.


system time.

Router ID(11.10.2.23) ? 11.10.2.22
!!!!!!!!!!!!!!!!!!!!!!!!!!
N)[N]?


(1132135975) Thu Mar 13 10:12:55 2014

Go to Step 13

Go to Step 14
serial cable.

no]?

serial cable.

serial cable.


element connection.
If the GNM terminal will be used to verify the XCM craft Ethernet port IP connectivity:
minal IP address.






XTC. If the XCM is located in upper universal XCM slot A-6B, use DCN port A. If the XCM is located
in lower universal XCM slot B-6B, use DCN port B
minal IP address.



To test the DCN IP connection of the target XTC

Step 2 Enter the DCN IP address of the target XTC in the web address (URL) field. If the connection is
established, a login window is displayed. This verifies DCN IP connectivity to the network ele-
ment.

Installing XTC Multi-chassis NC Ethernet Cables

In a multi-chassis configuration, chassis are interconnected at the nodal control (NC) ports of the
XCM/IMMs using straight-through unshielded twisted pair CAT6 Ethernet cables that conform to
allowed for each NC cable segment between chassis is 328 feet (100 meters). A third-party Ethernet
media converter can be used for connecting NC ports to support extended distances. Contact your Infinera
account team for assistance with third-party Ethernet media converters.
Release 10.0 certifies a DTN-X multi-chassis configuration consisting of up to 60 interconnected chassis
(up to 10 XTCs, up to 6 MTC-9s, up to 32 DTC/MTCs, and up to 12 OTCs). The Main Chassis must be an
XTC but the Expansion Chassis can be any combination of XTC/MTC-9/DTC/MTC/OTCs.
Note: When interconnecting multiple XTCs with MTC-9s, DTC/MTCs and/or OTCs, ensure that
all XTCs are interconnected together (first), followed by (in any particular order): MTC-9s,
Refer to “Installing MTC-9 Multi-chassis NC Ethernet Cables” on page 9-9 for MTC-9 multi-chassis
configurations consisting of MTC-9/OTCs. This section is organized as follows:
“Dual-chassis Configuration NC Cabling” on page 6-40
“Multi-chassis Configuration NC Cabling” on page 6-47

Dual-chassis Configuration NC Cabling
plane availability.

“To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) with full XCM redundancy” on page 6-
40
“To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) with full XCM redundancy” on
page 6-42
“To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) with XCM redundancy only on Main
“To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) with XCM redundancy only on
“To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) non-redundant XCMs” on page 6-45
“To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) non-redundant XCMs” on page 6-

46
To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) with full XCM redundancy
chassis:
Step 2 Connect 1-NC-2 ACT to 2-NC-1 STBY.

Figure 6-12 NC Connectivity for Dual-chassis (XTC-to-XTC.MTC-9) with Full XCM Redundancy
XTC
Chassis 1
NC 1 NC 1
NC 2 NC 2
XTC/MTC-9
Chassis 2
NC 1 NC 1
NC 2 NC 2

To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) with full XCM redundancy
 On the DTC/MTC/OTC: [ChassisID]-NCT-[PortNumber][A|B].
Step 3 Connect 1-NC-1 STBY to 2-NCT-2B.
Figure 6-13 NC Connectivity for Dual-chassis (XTC-to-DTC/MTC/OTC) with Full XCM Redundancy
XTC
Chassis 1
NC 1 NC 1
NC 2 NC 2
DTC/MTC/OTC

Chassis 2
MCM MCM
in 7A in 7B
or CPU or CPU
OMM OMM
in 1A in 1B
Switch/ Switch/
Router Router

infn_1137

To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) with XCM redundancy only on Main
Chassis
chassis:
Main Chassis
Chassis 1 XTC
NC 1 NC 1
NC 2 NC 2
Chassis 2 XTC/MTC-9
XCM/IMM ACT
NC 1
NC 2

To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) with XCM redundancy only on Main
Chassis
Figure 6-15 NC Connectivity for Dual-chassis (XTC-to-DTC/MTC/OTC) with XCM Redundancy only
on Main Chassis
XTC
Chassis 1
NC 1 NC 1
NC 2 NC 2
DTC/MTC/OTC
Chassis 2
MCM
in 7A
or CPU
OMM
in 1A
Switch/
Router

infn_1138

To connect NC cables for dual-chassis (XTC-to-XTC/MTC-9) non-redundant XCMs
chassis:
Figure 6-16 NC Connectivity for Dual-chassis (XTC-to-XTC/MTC-9) Non-redundant XCMs
XTC
Chassis 1
XCM Active (ACT)
NC 1
NC 2
XTC/MTC-9
Chassis 2
XCM/IMM ACT
NC 1
NC 2
Nodal Control (NC) Cable Connection

infn_926

To connect NC cables for dual-chassis (XTC-to-DTC/MTC/OTC) non-redundant XCMs
Figure 6-17 NC Connectivity for Dual-chassis (XTC-to-DTC/MTC/OTC) Non-redundant XCMs
XTC
Chassis 1
XCM Active (ACT)
NC 1
NC 2
DTC/MTC/OTC

Chassis 2
MCM
in 7B
or CPU
OMM
in 1B
Switch/
Router

infn_1139


“To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9) with full XCM redundancy” on
page 6-47
“To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9/DTC/MTC/OTC) with full XCM redun-
dancy” on page 6-49
“To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9) with XCM redundancy only on Main
“To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9/DTC/MTC/OTC) with XCM redun-
dancy only on Main Chassis” on page 6-53
Note: When interconnecting multiple XTCs with MTC-9s, DTC/MTCs and/or OTCs, ensure that
all XTCs are interconnected together (first), followed by (in any particular order): MTC-9s,
To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9) with full XCM redundancy
In the procedure below, the following convention is used to specify NC ports on a particular chassis:

Figure 6-18 NC Connectivity for Multi-chassis (XTC-to-XTC/MTC-9) with Full XCM Redundancy
XTC
Chassis 1
NC 1 NC 1
NC 2 NC 2
XTC/MTC-9
Chassis 2
NC 1 NC 1
NC 2 NC 2
XTC/MTC-9
Chassis n
NC 1 NC 1
NC 2 NC 2

To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9/DTC/MTC/OTC) with full XCM

redundancy
Step 4 Connect 1-NC-2 STBY to n-NCT-1A.


Redundancy
XTC
Chassis 1
NC 1 NC 1
NC 2 NC 2
XTC/MTC-9
XCM/IMM Active (ACT) XCM/IMM Standby (STBY)

Chassis 2
NC 1 NC 1
NC 2 NC 2
DTC/MTC/OTC
Chassis n
MCM MCM
in 7A in 7B
or CPU or CPU
OMM OMM
in 1A in 1B
Switch/ Switch/
Router Router
Nodal Control (NC/NCT) Cable Connection infn_1267

To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9) with XCM redundancy only on Main
Chassis
chassis:

Main Chassis
XTC
Chassis 1
NC 1 NC 1
NC 2 NC 2
XTC/MTC-9
Chassis 2
XCM/IMM ACT
NC 1
NC 2
XTC/MTC-9
Chassis n XCM/IMM ACT
NC 1
NC 2

To connect NC cables for multi-chassis (XTC-to-XTC/MTC-9/DTC/MTC/OTC) with XCM redundancy

only on Main Chassis


Redundancy only on Main Chassis
XTC
Chassis 1
NC 1 NC 1
NC 2 NC 2
XTC/MTC-9
XCM/IMM Active (ACT)

Chassis 2
NC 1
NC 2
DTC/MTC/OTC
Chassis n
MCM
CPU
in 7A
or
Nodal Control (NC/NCT) OMM
Switch/
Cable Connection Router in 1A
infn_1268

Expansion Chassis.
sage is displayed.






Software
Version



displayed.


Step 6 Click OK.



Step 11 Click OK.
face.

right-click any IAM/IrM and select GMPLS Link. The GMPLS Node ID is located in the bot-
tom left corner of the GMPLS Link Properties window. Record the GMPLS Node ID for
the Primary and Secondary GNE. This is the Primary/Secondary GNE IP Address utilized
by SNEs for routing IP traffic and requests.
Step 6 Click Apply.

Summary panel
IP Gateway Proxy
GNE tab
Primary and
Secondary GNE
IP Addresses


CAUTION





Verifying Inventory
To verify equipment

Configuring Tunable FlexChannel Line Modules
Note: Ensure that the MTC-9 Expansion Chassis has been initially commissioned prior to per-
forming this procedure. Refer to “MTC-9 Expansion Chassis Turn-up” on page 9-2.
Note: This procedure is applicable to tunable FlexChannel line modules operating in either SCG
(default mode) or Open Wave line system mode.
Each XTC-10 may contain up to ten (10) tunable FlexChannel line modules and each XTC-4 may contain
up to four (4) tunable FlexChannel line modules. The tunable FlexChannel line modules are optically
connected to an MTC-9 (either directly to an FSM or indirectly to an FRM via an FSP-C or FMP-C).
Perform the following procedure to verify and/or to configure the operating mode and the installed SCh
number on each tunable FlexChannel line module.
To verify and/or configure tunable FlexChannel line modules
Note: The AOFM-500B/AOFX-500Bs initially provide 100Gbps or 50Gbps of Instant Bandwidth

(depending on modulation format). Contact your Infinera account team to purchase addi-
tional Instant Bandwidth software licenses for additional line module bandwidth. Software
licensing is managed via Infinera Digital Network Administrator (DNA), and the activated
bandwidth for the modules can be viewed in Infinera Graphical Node Manager (GNM) or
the TL1 interface. Refer to the Infinera License Management Guide for details regarding
Instant Bandwidth license application and management. For example, obtaining a license,
assigning or reassigning a license, regenerating a license, moving a license within a chas-
sis or to another chassis, or moving a license back to the license store.
Step 1 From the Equipment View, right-click the tunable FlexChannel line module and select Admin
State -> Lock. A warning message is displayed.
Step 2 Click Lock OFX.
Step 3 From the Equipment View, right-click the tunable FlexChannel line module and select Super
Channel. The SCHCTP Properties window is displayed. See Figure 6-29 on page 6-68.
Step 5 Click the Provisioned SCH Number drop-down menu and select the appropriate SCh.
Step 6 If you need to configure the modulation format, click Provisioned Modulation drop-down menu
and select the appropriate modulation format.


Step 9 Click Close.
Step 10 If you need to configure the encoding format and/or the line system mode, perform the following.
Otherwise proceed to Step 11.
Step 10a From the Equipment View, right-click the tunable FlexChannel line module and
select Super Channel Group.... The OFX SCG Port Properties window is displayed.
See Figure 6-30 on page 6-68.
Step 10b Click on the General tab.
Step 10c In the Other panel, click the Provisioned Encoding Format drop-down menu and
select the appropriate encoding format.
Step 10d If you need to configure the line system mode, click the Line System Mode
drop-down menu and select the appropriate line system mode.
Step 10e Click Apply. A warning message is displayed.
Step 10f Click Proceed.
Step 10g Verify that the Installed Encoding Mode field lists the selected encoding mode.
Step 10h Verify that the Line System Mode drop-down menu lists the selected line system
mode.
Step 10i Click Close.
Step 11 From the Equipment View, right-click the tunable FlexChannel line module and select Admin
State -> Unlock.
Step 12 Repeat Step 1 through Step 11 for each installed tunable FlexChannel line module.

Figure 6-29 Configuring Tunable FlexChannel Line Modules
General tab
Provisioned SCH
Number
Installed SCH
Provisioned
Number
Encoding
Format Installed
Modulation
Installed Encoding
Mode
Figure 6-30 Configuring Encoding Mode and/or Line System Mode on Tunable FlexChannel Line
Modules
General tab
Other panel
Provisioned
Encoding Mode
Installed
Encoding Mode
Line System
Mode

Interconnecting the Tunable FlexChannel Line Module to

FRM/FSM SCh Fibers
Note: This procedure is applicable to tunable FlexChannel line modules operating in either SCG
(default mode) or Open Wave line system mode.
Each XTC-10 may contain up to ten (10) tunable FlexChannel line modules and each XTC-4 may contain
up to four (4) tunable FlexChannel line modules. The tunable FlexChannel line modules are optically
connected to an MTC-9 (either directly to an FSM or indirectly to an FRM via an FSP-C or FMP-C).
To interconnect SCh fiber cables between the tunable FlexChannel line module and the MTC-9 (FSM) or
FPC (FSP-C/FMP-S), perform one of the following procedures:
“To connect SCh cables between XTC FlexChannel line modules and MTC-9 FSMs” on page C-30
“To connect SCh cables between XTC FlexChannel line modules and FPC FSP/FMPs” on page C-
32

Creating a Fiber Panel

Perform the following procedure to create a Fiber Panel. The Fiber Panel consists of Fiber Shuffle Panel
(FSP) and/or Fiber Multiplexing Panel (FMP) modules which provide fiber connectivity to/from FlexROADM
Modules (FRMs) and/or FlexROADM Switching Modules (FSMs) residing on an MTC-9.
Step 1 From the Equipment Tree, right-click the network element icon and select Create FP. The Create
FP window is displayed.
Step 2 Click the FP Type drop-down menu and select FSP-S-4D-8MPO (for a DTN-X CDC ROADM
configuration) or FSP-C-1D-1MPO-4LC (for a DTN-X colorless ROADM configuration). See
Figure 6-31 or Figure 6-32.
Step 3 Enter a value in the AID field.
The AID field is an alpha-numeric string (identifier) used to identify the Fiber Panel. The string
can have a maximum of 40 characters.
Step 4 Enter a value in the Label field.
The label is an optional field (a character string with a maximum of 128 characters) assigned to
further identify the Fiber Panel.
Step 5 Enter a value in the Serial Number field.
The serial number field (a character string with a maximum of 60 characters) represents the
manufacturing serial number of the installed equipment.
Step 6 Click Apply.
Step 7 Repeat Step 1 through Step 6 for additional Fiber Panels.
Figure 6-31 Creating a Fiber Panel (FSP-S) for a DTN-X CDC ROADM Configuration
FP Type
Figure 6-32 Creating a Fiber Panel (FSP-C) for a DTN-X Colorless ROADM Configuration
FP Type

Interconnecting the FSP/FMP Fibers

The Fiber Panel consists of Fiber Shuffle Panel (FSP) and/or Fiber Multiplexing Panel (FMP) modules that
provide fiber connectivity to/from AOFM-500/AOFM-500B/AOFX-500/AOFX-500Bs residing on an XTC,
and to/from FlexROADM Modules (FRMs) and/or FlexROADM Switching Modules (FSMs) residing on an
MTC-9.
To interconnect the FSP/FMP fibers, refer to “Connect and Route FSP/FMP Fiber Optic Cables” on
page C-44.

Associating the FRM and FSM Ports on the Fiber Panel
Note: This procedure is only applicable if you are configuring a DTN-X CDC ROADM. For a
DTN-X colorless ROADM configuration, refer to “Associating the FRM Ports on the Fiber
Panel” on page 6-73.
Perform the following procedure to associate the FRM add/drop (system) and FSM (line) ports on the Fiber
Panel.
To associate the FRM add/drop (system) and FSM (line) ports on the Fiber Panel
Step 1 From the Equipment Tree, right-click the Fiber Panel and select Properties. The FP Properties
window is displayed. See Figure 6-33.
Step 2 In the MPO Connections panel, select the desired MPO connection.
Step 3 Click Apply.
Figure 6-33 Associating the FRM and FSM Ports on the Fiber Panel
MPO Connections tab

Associating the FRM Ports on the Fiber Panel
Note: This procedure is only applicable if you are configuring a DTN-X colorless ROADM. For a
DTN-X CDC ROADM configuration, refer to “Associating the FRM and FSM Ports on the
Fiber Panel” on page 6-72.
Perform the following procedure to associate the FRM add/drop ports on the Fiber Panel.
To associate the FRM add/drop ports on the Fiber Panel
Step 3 Click Apply.
Figure 6-34 Associating the FRM Ports on the Fiber Panel
MPO Connections tab

Provisioning an Optical Cross-connect

 For a DTN-X CDC ROADM configuration only, perform the following procedure: “To provision an
optical cross-connect from an FSM tributary port to an FRM line port” on page 6-74
 For a DTN-X colorless ROADM configuration only, perform the following procedure: “To provision an
optical cross-connect from an FRM system port to an FRM line port” on page 6-79
To provision an optical cross-connect from an FSM tributary port to an FRM line port
Note: This procedure is only applicable if you are configuring a DTN-X CDC ROADM.
Perform the following procedure to create an add/drop optical cross-connect from an FSM tributary port to
an FRM line port.
Step 1 From the Equipment View, right-click the FSM and select Provisioning -> Create Optical
Cross-connect. The Create Optical Cross-Connect Home screen is displayed.
Figure 6-35 Create Optical Cross-connect (Home Screen)
Connectivity

Step 2 Click the Connectivity drop-down menu and select Add/Drop.

Step 3 Click Next.
Figure 6-36 Create Optical Cross-connect (Entering Circuit ID, Label, Source and Destination
Endpoints)
Circuit ID (CID)
Label
Source Endpoint
Destination
Endpoint
Step 4 Enter a value in the Circuit ID (CID) field.

The circuit ID is a recommended but not mandatory field associated with the service. It is an
alpha-numeric string (identifier) used to identify the cross-connect. The string can have a maxi-
mum of 48 characters with ‘-’, ‘_’, ‘:’, and ‘ ‘ as special characters. Although ‘ ‘ (spaces) are sup-
ported, the string must not start or end with this. It is highly recommended that ‘~’, ‘!’, ‘%’, ‘*’, ‘(‘,
‘)’, ‘[‘, ‘]’, and ‘,’ (comma) special characters are not used in the CID field. This field can be
entered at the time of creation of the service and can be modified even after the creation of the
service irrespective of the Administrative State of the service.
The label is an optional field (a character string with a maximum of 128 characters) assigned at
the time of cross-connect creation to further identify the circuit.
Step 6 In the Source Endpoint field, click the [...] button. The Endpoint Source window is dis-
played.

Step 7 Select the desired source endpoint.

Step 8 Click Ok.
Step 9 In the Destination Endpoint field, click the [...] button. The Endpoint Destination window is
displayed.
Figure 6-38 Endpoint Destination
Step 10 Select the desired destination endpoint.

Step 11 Click Ok.

Figure 6-39 Create Optical Cross-connect (Create)
Step 12 Click Create.
Note: If you did not enter a value for the Circuit ID field, a confirmation message is displayed.
Click Continue without CID to proceed. The Circuit ID is not mandatory (but is recom-
mended).
An optical cross-connect successful dialog is displayed.
Figure 6-40 Create Optical Cross-connect (Successful Dialog)
Step 13 Click Ok.

Step 14 To view optical cross-connects. From the Main Menu, click Provisioning -> Cross-Connect
Manager. Click the Optical tab. See Figure 6-41.
Figure 6-41 Cross-connect Manager (Optical)

To provision an optical cross-connect from an FRM system port to an FRM line port
Note: This procedure is only applicable if you are configuring a DTN-X colorless ROADM.
Perform the following procedure to create an add/drop optical cross-connect from an FRM system port to
an FRM line port.
Step 1 From the Equipment View, right-click the FRM and select Provisioning -> Create Optical
Connectivity
Step 2 Click the Connectivity drop-down menu and select Add/Drop.

Step 3 Click Next.

Endpoints)
Circuit ID (CID)
Label
Source Endpoint
Destination
Endpoint

Step 6 In the Source Endpoint field, click the [...] button. The Endpoint Source window is
displayed.


Step 8 Click Ok.
displayed.

Step 11 Click Ok.

mended).
Step 13 Click Ok.



XTC:

Testing TOMs

Testing TIMs
Testing XICMs

Step 1 Examine the LEDs on each line module/OTM-500/OTM2-500 on the XTC. The FLT LED is illumi-
nated if an alarm exists. If a line module/OTM-500/OTM2-500 has an alarm, view the Alarm
Testing OXMs

Testing TSMs
Testing XCMs
agement interfaces.


the XTC.

Alarm Filter panel

Alarm Severity
to customers.
cautions.

Alarm Type Cause

• Fibers are connected but they do not
Shutdown (ALS).
side) have light.




11 N/C N/A N/A
12 N/C N/A N/A
13 N/C N/A N/A


45 N/C N/A N/A
46 N/C N/A N/A
47 N/C N/A N/A



Alarm Cutoff (ACO)

the ACO LED state.

To enable an ACO
tons).
Testing an ACO
to be audible.
To test an ACO


node configuration.
Expansion Chassis.


procedure.

CHAPTER 7
Turning up a FlexILS as a GNE
This chapter provides the procedures to turn up and test a FlexILS as a Gateway Network Element (GNE).
“FlexILS Main Chassis Turn-up” on page 7-2
“Testing MTC-9 Circuit Packs” on page 7-40
Note: In previous software releases, a node with an OTC as the Main Chassis (i.e. OMM as the
node controller module) was referred to in the documentation as an "Optical Line Amplifier"
node. Note that the management interfaces have always referred to this node type as an
"Optical Amplifier". Starting in Release 10.0, the customer documentation is updated to
match the terminology of the management interfaces, wherein a node with an OTC Main
Chassis is called an "Optical Amplifier" and a node with an MTC-9 Main Chassis (i.e. IMM
as the node controller module) configured with IAMs/IRMs is now called an "Optical Line
Amplifier". Note that an MTC-9 Main Chassis configured with FRMs is called a
FlexROADM node, to support optical multiplexing.

Page 7-2 FlexILS Main Chassis Turn-up
FlexILS Main Chassis Turn-up

The FlexILS network element, referred to as the FlexILS, is an optimized network element that combines
digital Reconfigurable Optical Add/Drop Multiplexer (ROADM) services with flexible grid and colorless,
directionless, and contentionless (CDC) capabilities to extend the optical reach between DTN-Xs deployed
in an Intelligent Transport Network. Depending on the hardware configuration, a FlexILS network element
can be deployed as a FlexROADM node or an Optical Line Amplifier node.
The FlexILS is comprised of one or more Modular Transport Chassis (MTC-9) and zero or more Fiber
Panel Chassis (FPC) which house Fiber Shuffle Panel (FSP) and/or Fiber Multiplexing Panel (FMP)
modules that provide fiber connectivity to/from FlexROADM Modules (FRMs) and/or FlexROADM
Switching Modules (FSMs) residing on the MTC-9.
Figure 7-1 shows the various hardware components of the MTC-9.
Figure 7-1 MTC-9 Front View

Fan Tray
Fiber Management Air
PEMs Tray Filter
Cable
Management
PEM
A/B
IOP IOP
PWR
FLT
Slot 9 Reserved
for IMM 9
8
Redundant IMM
Universal Blank 7
AIRFLOW DIRECTION
6
DIRECTEMENT AVEC
NE PAS REGARDER
DES INSTRUMENTS
LASER PRODUCT
INVISIBLE LASER
LASER INVISIBLE
PRODUIT LASER
DIRECTLY WITH
RAYONNEMENT
INSTRUMENTS
DO NOT VIEW
1525-1565 nm
RADIATION
OPTIQUES
CLASS 1M
OPTICAL
135 mW
5
IAMs/IRMs/
IAM-B-ECXH2
FRMs/FSMs
4
2
DIRECTEMENT AVEC
NE PAS REGARDER
DES INSTRUMENTS
LASER PRODUCT
INVISIBLE LASER
LASER INVISIBLE
PRODUIT LASER
DIRECTLY WITH
RAYONNEMENT
INSTRUMENTS
DO NOT VIEW
1525-1565 nm
RADIATION
OPTIQUES
CLASS 1M
OPTICAL
135 mW
FRM-9D-R-8-EC
Air Inlet Plenum

infn_1164

Turning up a FlexILS as a GNE Page 7-3
Tasks
Table 7-1 FlexILS Turn-up Checklist and Test Results

7-5
7-8
“Verifying Power to the MTC-9“ page
7-10
“Powering up the MTC-9“ page
7-12
“Initial Commissioning for the MTC-9 page
Main Chassis Gateway Network Ele- 7-13
ment (GNE)“
“Verifying IMM Craft Ethernet Port IP page
7-23
7-24
7-26
9-2
“Interconnecting Line Side Fibers page
between Two Nodes“ 7-29
“Configuring the Optical Supervisory page
Channel“ 7-30
“Verifying the Optical Supervisory page
Channel“ 7-32
“Provisioning Fiber Information“ page
7-33

“Verifying Span Loss“ page

7-35
“Installing the Standby IMM“ page (if applicable)
7-38
7-39


Before performing the turn-up and test procedures on an MTC-9, a serial connection between the network
end.
IMM.

COM1).
Note: This window should be kept open until the initial commissioning of the MTC-9 is complete.


Infinera GNM interface. The MTC-9 provides a craft Ethernet port on the IMM. The following procedure
describes how to connect an Ethernet cable to the IMM. Ethernet connectivity requires either a straight-
used to access the Infinera GNM from the IMM is 192.168.0.1. The default subnet mask that is used to
access the Infinera GNM from the IMM is 255.255.255.0.

Active IMM
(PWR, NC, and
PWR
FLT
PWR
DCE 10/100/1000 BaseT

ACT
FLT
NC
DATA
LINK
LINK
CRAFT
Craft Ethernet
Port
infn_1213
Step 2 Connect the Ethernet cable to the connector labeled Craft on the active IMM.
Note: If there is a redundant IMM, it should not be installed in the slot at this time.

MTC-9.
suggested.
desktop, choose Start > Control Panel > Network and Sharing Center > Change adapter set-


address should be in the same subnet as the IP address configured for the target IMM or the
MTC-9. The last octet must vary between 2 and 255.
Note: The default IP address of the IMM is: 192.168.0.1.

Step 8 Click OK.
Step 9 Click Close.

Verifying Power to the MTC-9
CAUTION
Perform the following procedure to verify the power to the MTC-9.
To verify power supply to the MTC-9
Step 1 At the power distribution unit (PDU) power source that feeds MTC-9 POWER A and B (PEM A
and PEM B), verify that the power is turned off and perform the following.
Step 1a At each PEM (PEM A and B), using a #1 Phillips screwdriver, remove the two pan
head screws securing the PEM safety cover to the PEM and remove the cover.
Step 2 At the PDU power source that feeds MTC-9 POWER A (PEM A), turn on the power.
WARNING
Step 3 Using a multimeter set to measure DC voltage, measure the voltage across the heads of the
terminal screws at PEM A. See Figure 7-8 on page 7-11.
Step 3a If the reading is within the specified range (-40 to -72V DC) with correct polarity, pro-
ceed to Step 3b. If the polarity is incorrect or the measured voltage is not within the
specified range, report readings to facilities personnel for further troubleshooting and
correction.
Step 3b Measure the voltage across the tips of the terminal studs (not the lugs) at PEM B
(there should be no voltage present). If no voltage is measured, proceed to Step 4. If
voltage is present, report readings to facilities personnel for further troubleshooting
and correction.
Step 4 At the PDU power source that feeds MTC-9 POWER A (PEM A), turn off the power.
Step 5 At the PDU power source that feeds MTC-9 POWER B (PEM B), turn on the power.
WARNING
terminal screws at PEM B. See Figure 7-8 on page 7-11.

correction.
Step 6b Measure the voltage across the tips of the terminal studs (not the lugs) at PEM A
and correction.
Step 7 At the PDU power source that feeds MTC-9 POWER B (PEM B), turn off the power.
Step 8 At the MTC-9, perform the following steps.
Step 8a At each PEM (PEM A and B), install the two pan head screws and secure the PEM
safety cover to the PEM using a #1 Phillips screwdriver.
Step 8b Install one IMM into slot 9 or slot 8 (verify that only one IMM is fully seated; if a
redundant IMM is occupying the second slot, ensure that it is not fully seated).
Step 8c Verify that any modules occupying slots 7 through 1 are not fully seated.
After you have verified that power is available to both PEMs and no faults exist, you are ready to power up
the MTC-9 and perform the initial start-up procedure.
Figure 7-8 Measuring DC Voltage at MTC-9 PEMs
Note:
If using compression lugs,
the lugs must fit a #6-32 block
screw and the lug width must
not exceed 0.31 inch. Terminal
screws
Measure voltage
across the heads
of the terminal
screws.
infn_1212

Powering up the MTC-9
CAUTION
Perform the following procedure to power up the MTC-9.
Initial Start-up
After the installation procedure has been completed (refer to the Infinera DTN and DTN-X Site Preparation
and Hardware Installation Guide), the MTC-9 may be started up.
To startup the MTC-9
and PEM B), turn on the power.
Step 2 Verify PEM LEDs on both PEMs as follows:
The normal state is the Green POWER INPUT LED ON and the Red POWER FAULT LED
OFF
Green Power Input LEDs on each PEM should be:
ON if an input voltage of the proper polarity is applied to this PEM
OFF if the input voltage is not present or wrong polarity to this PEM. Check for proper
voltage and polarity being applied to this PEM
Red Power Fault LEDs on each PEM should be:
OFF if the input voltage to this PEM is within specifications (or no power is present on
either PEM)
ON if the input voltage to this PEM is not within specifications or no power is present (if
the other PEM has power). Check for proper voltage and polarity being applied
After you have verified that power is present on both PEMs and no faults exist, initially configure the
MTC-9.

Initial Commissioning for the MTC-9 Main Chassis Gateway

Note: Ensure that only one IMM is installed (fully seated) in either reserved slot 9 or universal slot
8 on the MTC-9; if a redundant IMM is occupying the second slot, ensure that it is not fully
seated).
After you have powered up the MTC-9 for the first time, the boot up process is initiated. Within a minute or
the MTC-9. You must have the site specific commissioning data at hand (listed in “Commissioning Data”
on page 2-12 and previously recorded in Table 2-1 on page 2-2).
The procedures to commission an MTC-9 vary depending on whether the IMM was commissioned
previously or not.
 If the IMM was not commissioned previously, see “To initially commission the Main Chassis of a
GNE if the IMM was not commissioned previously” on page 7-13
 If the IMM was commissioned previously, see “To initially commission the Main Chassis of a GNE if
the IMM was commissioned previously” on page 7-17.
See “XCM/IMM/MCM/OMM Rebranding Flow” on page B-1 for a graphical representation of the IMM
branding procedure.
To initially commission the Main Chassis of a GNE if the IMM was not commissioned previously
If the IMM was not commissioned previously, the following message is displayed in the HyperTerminal
session:
then press Enter.


Step 3 Router ID—Internal router ID (IP address) for communication between the IMMs. The router ID

located.


ure and repeat the steps in case a mistake was made, or B to reboot the IMM and discard the
changes.
The IMM will reboot and the following message is displayed:
Thu Mar 13 09:59:47 2014
The IMM boot process will stop at Do you want to go ahead with reconfiguration[yes|no].
Thu Mar 13 10:02:20 2014
Thu Mar 13 10:02:20 2014
Main Chassis : yes
NE Name : Node1
Router ID : 11.100.179.195
Dcn IP : 10.100.179.195

Dcn Netmask : 255.255.255.224

Shelf ID : 1
Note: Disconnecting the serial cable during the boot up process may cause the IMM to hang and
serial cable.
The IMM can take some time to complete the boot up process. When the PWR, NC, and ACT LEDs are all
lit solid Green the IMM has completed booting up. This indicates the IMM is operational (and safe to
This completes the initial commissioning of the IMM.

To initially commission the Main Chassis of a GNE if the IMM was commissioned previously
If the IMM was commissioned previously, the following message is displayed in the HyperTerminal
session:
Main Chassis : yes
NE Name : Node_2
Router ID : 11.10.2.23
Dcn IP : 10.10.2.21
Dcn Netmask : 255.255.252.0
Shelf ID : 1
then press Enter.





Router ID(11.10.2.23) ? 11.10.2.22
!!!!!!!!!!!!!!!!!!!!!!!!!!
Dcn IP(10.10.2.21) ? 10.10.2.20
Dcn Netmask(255.255.252.0) ?
N)[N]?
(1132135975) Thu Mar 13 10:12:55 2014
Type yes to re-brand the IMM.


If the IMM did not have a database stored on it, the following message is displayed:

Go to Step 17
If the IMM had a database stored on it, the following message is displayed:

Go to Step 18
serial cable.
This completes the initial commissioning of the IMM. The IMM can take some time to complete the boot up
process. When the PWR, NC, and ACT LEDs are all lit solid Green the IMM has completed booting up.
This indicates the IMM is operational.
Type yes to re-brand the IMM. The following message is displayed:

no]?
serial cable.

Type no if you do not want to re-brand the IMM. The following message is displayed:
serial cable.
This indicates the IMM is operational (and safe to remove the serial cable).

Verifying IMM Craft Ethernet Port IP Connectivity

To verify IMM craft Ethernet port IP connectivity, first ping the IMM IP address, and then test the network
element connection.
If the GNM terminal will be used to verify the IMM craft Ethernet port IP connectivity:
 Ensure that an Ethernet cable is connected from the GNM terminal to the correct IMM craft Ethernet
port on the MTC-9. If the IMM is located in reserved slot 9, use IMM craft Ethernet port A. If the IMM
is located in universal slot 8, use IMM craft Ethernet port B
 Verify that the GNM terminal IP address is in the same IP domain as the MTC-9
Note: Follow the steps in “Configuring the GNM Terminal” on page 7-8 to change the GNM termi-
nal IP address.
To ping the IMM craft Ethernet port IP address

ping [IMM Craft Ethernet Port IP Address]


To test the IMM craft Ethernet port IP connection of the target MTC-9

Step 2 Enter the IMM craft Ethernet port IP address of the target MTC-9 in the web address (URL) field.
If the connection is established, a login window is displayed. This verifies IMM craft Ethernet port


nal IP address.



To test the DCN IP connection of the target MTC-9

Step 2 Enter the DCN IP address of the target MTC-9 in the web address (URL) field. If the connection
is established, a login window is displayed. This verifies DCN IP connectivity to the network ele-
ment.

Note: Infinera GNM may be launched from the Ethernet craft port of an IMM using the craft Ether-
sage is displayed.

Step 2 In the browser, enter the DCN IP address of the target MTC-9. Infinera GNM is launched in a
new window and the Login window is displayed.

conditions (see Figure 7-11).
Figure 7-11 Infinera GNM Main View of MTC-9


It is important to know what version of software is on the Active IMM in the MTC-9. The software version

 From the Equipment View, select the Active IMM. The Quick View Browser panel in the lower left
corner displays the IMM software version number as shown in Figure 7-12
Software
Version



displayed.


Step 6 Click OK.



Step 11 Click OK.
face.

Interconnecting Line Side Fibers between Two Nodes

Each MTC-9 may contain two ILS Amplifier Modules (IAMs) or two ILS Raman Modules (IRMs). It is
recommended that a node numbering scheme be established for the network. For example, eastbound
traffic numbering is from IAM/IRM slot 1 (Node A) to IAM/IRM slot 3 (Node B) and westbound traffic is from
IAM/IRM slot 3 (Node B) to IAM/IRM slot 1 (Node A).
To connect Nodes A and B
Step 1 Connect line fibers from the OUT (Transmit) Line Port on IAM/IRM slot 1 (Node A) to the IN
(Receive) Line Port on IAM/IRM slot 3 (Node B) for eastbound traffic.
Step 2 Connect line fibers from the OUT (Transmit) Line Port on IAM/IRM slot 3 (Node B) to the IN
(Receive) Line Port on IAM/IRM slot 1 (Node A) for westbound traffic.
Now Nodes A and B are connected and you have created an optical link.

Configuring the Optical Supervisory Channel
Note: To enable the OSC connectivity, this configuration must be performed on each IAM/IRM at
each end of the link.
Once the chassis has been initially commissioned and the fibers have been connected, perform the
following procedure to create an optical link and configure the Optical Supervisory Channel (OSC) on the
MTC-9.
To configure the OSC
Step 1 From the Equipment View, highlight the appropriate IAM/IRM to which the optical link is con-
nected.
Step 2 Right-click and select OSC. The OSC Properties window is displayed.
Figure 7-15 OSC Properties

Step 3 In the OSC IP Address panel, click Edit. The GMPLS Link Properties window is displayed.
Step 4 In the OSC/GMPLS Control panel, click the drop-down menu and select Enable OSC.
Note: The OSC IP address and the DCN IP address for each MTC-9 must be on different IP net-
works.
When MTC-9s are physically connected, the OSC IP address configured on the IAM/IRMs must
be in the same subnet in order for the OSC to function properly. For example, IAM/IRM slot 1
(Node A) will have an address such as: 192.168.30.1 and Subnet Mask such as: 255.255.255.0;
and IAM/IRM slot 1 (Node B) will have an address like 192.168.30.2 with Subnet Mask like
255.255.255.0. This is the OSC IP address between the two adjacent network elements.
Step 5 In the OSC IP Address panel, enter the IP Address and Subnet Mask.
Step 6 In the Routing Info panel, uncheck the Disable GMPLS (& Mgmt Plane) box.
Step 8 When you are done, click Close to exit the GMPLS Link Properties window.
Step 9 Click Close to exit the OSC Properties window.
Step 10 Repeat Step 1 through Step 9 for the remaining IAM/IRM.
Once you have created an OSC, you must verify the connection as described in the following procedure.

Verifying the Optical Supervisory Channel
Note: Before proceeding with this procedure, ensure that the OSC has been provisioned on each
IAM/IRM at each end of the link.
Perform the following procedure to verify the OSC connectivity between neighboring nodes in the network.
To verify OSC connectivity
Step 1 From the Infinera GNM Main Menu, select Tools > Connectivity Verification Tools. The Con-
nectivity Verification Tools window is displayed.
Step 2 In the IP Address/Node Name panel, enter the IP Address of the network element with which
you want to check connectivity.
Step 3 In the Commands panel, select Ping.
Figure 7-16 Connectivity Verification Tools
Step 4 Click Execute to verify the connectivity.

If a success message is displayed in the Response panel, it verifies the connection through the OSC
between neighboring nodes on the network.

Provisioning Fiber Information

Perform the following procedure to provision the fiber information for each IAM/IRM in the MTC-9.
To provision fiber information
Step 1 From the Equipment View, highlight the appropriate IAM/IRM to be configured, right-click and
select Admin State -> Maintenance.
Step 2 Click Apply.
Step 3 Right-click the IAM/IRM and select Span. The Span Properties window is displayed. From the
tabs listed in the middle of the window, select the Span/C-Band tab.
Step 4 In the Fiber panel (Figure 7-17 on page 7-34), perform the following:
Step 4a Enter the Span Length value (if this value is not known, leave the field blank).
Step 4b Enter the Line Out Pad (attenuator) value (line out = IAM/IRM Tx port).
Step 4c Enter the Line In Pad (attenuator) value (line in = IAM/OIRM Rx port).
Step 4d Click the Tx Fiber Type drop-down menu and select the appropriate transmit fiber
type.
Step 4e Enter the Rx Eqpt List information (optional).
Step 4f Enter the Tx Eqpt List information (optional).

Figure 7-17 Span Properties
Span/C-Band
tab
Fiber panel
Step 5 Click Apply to save the changes.

Step 6 When completed, click Close to exit the Span Properties window.
Step 7 From the Equipment View, highlight the appropriate IAM/IRM, right-click and select

Verifying Span Loss

Perform the following procedure to verify the span loss on each IAM/IRM in the MTC-9.
To verify span loss
Step 1 From the Equipment View, highlight the appropriate IAM/IRM.

Step 2 Right-click on the IAM/IRM and select Span. The Span Properties window is displayed.
Step 3 In the Span Properties window, select Span/C-Band.
Step 4 In the Detected Span Loss field, verify that the span loss is within specifications for the installed
IAM/IRM.
Step 5 When finished, click Close

right-click any IAM/IRM and select GMPLS Link. The GMPLS Node ID is located in the bot-
tom left corner of the GMPLS Link Properties window. Record the GMPLS Node ID for the
Primary and Secondary GNE. This is the Primary/Secondary GNE IP Address utilized by
Perform the following procedure to provision the primary and secondary GNE IP address in the MTC-9.
Step 6 Click Apply.

Summary panel
IP Gateway Proxy
GNE tab
Primary and
Secondary GNE
IP Addresses

Installing the Standby IMM

Perform the following procedure to install the standby IMM in the MTC-9.
To install the standby IMM
Step 1 Install the standby IMM.

The IMM takes some time to complete the boot up process. When it is complete, look at the IMM
and verify that the PWR LED is lit and Green and the ACT LED is lit and Yellow.
In the Management Card Properties window, ensure the IMM Redundancy Status of the
IMMs are Active and Standby
The ACT LED on the standby IMM is Yellow.

Verifying Inventory
to equipment, facilities, and tools used to control and monitor the MTC-9. The Infinera GNM Main View
also includes a graphical representation of the MTC-9 being managed.
To verify equipment

Page 7-40 Testing MTC-9 Circuit Packs
Testing MTC-9 Circuit Packs

MTC-9:
“Testing IAMs” on page 7-40
“Testing IRMs” on page 7-41
“Testing FRMs” on page 7-41
“Testing FSMs” on page 7-42

“Testing IMMs” on page 7-42
Testing IAMs
Note: The following procedure applies to all IAM types.
Perform the following procedure to test an IAM.
To test an IAM with an equipment failure alarm
Step 1 Examine the LEDs on each IAM on the MTC-9. The FLT LED is illuminated if an alarm exists. If
an IAM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the IAM from the Equipment View.
Step 4 Select Properties. The IAM Properties window is displayed.

Testing IRMs
Note: The following procedure applies to all IRM types.
Perform the following procedure to test an IRM.
To test an IRM with an equipment failure alarm
Step 1 Examine the LEDs on each IRM on the MTC-9. The FLT LED is illuminated if an alarm exists. If
an IRM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the IRM from the Equipment View.
Step 4 Select Properties. The IRM Properties window is displayed.
Testing FRMs
Note: The following procedure applies to all FRM types.
Perform the following procedure to test an FRM.
To test an FRM with an equipment failure alarm
Step 1 Examine the LEDs on each FRM on the MTC-9. The FLT LED is illuminated if an alarm exists. If
an FRM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the FRM from the Equipment View.
Step 4 Select Properties. The FRM Properties window is displayed.

Testing FSMs
Note: The following procedure applies to all FSM types.
Perform the following procedure to test an FSM.
To test an FSM with an equipment failure alarm
Step 1 Examine the LEDs on each FSM on the MTC-9. The FLT LED is illuminated if an alarm exists. If
an FSM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the FSM from the Equipment View.
Step 4 Select Properties. The FSM Properties window is displayed.
Testing IMMs
Note: An IMM equipment failure alarm is reported only for standby IMMs. If an equipment failure
alarm occurs on the active IMM, the MTC-9 will not be accessible through any of the man-
agement interfaces.
Perform the following procedure to test an IMM.
To test an IMM with an equipment failure alarm
Step 1 Examine the LEDs on each IMM on the MTC-9. The FLT LED is illuminated if an alarm exists. If
an IMM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the IMM from the Equipment View.
Step 4 Select Properties. The IMM Properties window is displayed.


the MTC-9.

Alarm Filter panel

expected alarms for the MTC-9.
Alarm Severity
to customers.
cautions.

Table 7-3 lists expected alarms that may occur upon turning up an MTC-9.
Table 7-3 Expected MTC-9 Alarms
Alarm Type Cause

Shutdown (ALS).

Environmental alarms are those triggered by an abnormal condition at the MTC-9 site. The MTC-9s
support input and output alarm contacts to monitor and control customer’s equipment. Alarm input
contacts allow users to connect external equipment (reactors), such as fire, alarm detector, high
temperature detector, door open and so on to the MTC-9. When the connected equipment triggers an input
contact point, it raises an alarm with an alarm message and severity as configured by the user. Alarm
output contacts allow users to connect external equipment to the MTC-9.
The MTC-9 can trigger the operation of the connected external equipment. The maximum threshold is


Table 7-4 specifies the assignment of alarm input contact pins for the MTC-9. One alarm contact is
predefined. There are six user-defined alarm contacts useful for generation of customized alarms which
can be triggered remotely through network management.
Table 7-4 MTC-9 Alarm Input Contact Pin Assignments
Pin Description Function
1 Reserved for Alarm Cutoff (ACO)a Predefined

2 General Purpose Alarm Input 1 User defined
a. ACO can be enabled using the input contact pins in addition to the ACO push button and the Infinera GNM
user interface.
Table 7-5 lists the assignment of alarm output contact pins for the MTC-9. Seven alarm contacts are
pre-defined in the system and the remaining four contacts can be customized by the users to monitor the
environmental alarms.
Table 7-5 MTC-9 Alarm Output Contact Pin Assignments
Relay
Number Description Function
1 Critical Audible Alarm Predefined

2 Major Audible Alarm Predefined
3 Minor Audible Alarm Predefined
4 Critical Visual Alarm Predefined
5 Major Visual Alarm Predefined
6 Minor Visual Alarm Predefined
7 Chassis Power Predefined
8 General Purpose 1 User defined


Alarm Cutoff (ACO)

The MTC-9 system provides a feature to acknowledge an alarm condition and turn off the audible indicator.
the ACO LED state.

To enable an ACO
tons).
Testing an ACO
to be audible.
To test an ACO


node configuration.
Perform the following procedure to configure datawire services on the MTC-9. The port used for the
datawire function is the AUX port.
Note: Infinera GNM may be launched from the Ethernet craft port of an IMM installed in an Expan-
sion Chassis.


procedure.

CHAPTER 8
Turning up a FlexILS as an SNE
This chapter provides the procedures to turn up and test a FlexILS as a Subtending Network Element
(SNE). This chapter is organized into the following sections:



Fan Tray
PEMs Tray Filter
Cable
Management
PEM
A/B
IOP IOP
PWR
FLT
Slot 9 Reserved
for IMM 9
8
Redundant IMM
Universal Blank 7
AIRFLOW DIRECTION
6
DIRECTEMENT AVEC
NE PAS REGARDER
DES INSTRUMENTS
LASER PRODUCT
INVISIBLE LASER
LASER INVISIBLE
PRODUIT LASER
DIRECTLY WITH
RAYONNEMENT
INSTRUMENTS
DO NOT VIEW
1525-1565 nm
RADIATION
OPTIQUES
CLASS 1M
OPTICAL
135 mW
5
IAMs/IRMs/
IAM-B-ECXH2
FRMs/FSMs
4
2
DIRECTEMENT AVEC
NE PAS REGARDER
DES INSTRUMENTS
LASER PRODUCT
INVISIBLE LASER
LASER INVISIBLE
PRODUIT LASER
DIRECTLY WITH
RAYONNEMENT
INSTRUMENTS
DO NOT VIEW
1525-1565 nm
RADIATION
OPTIQUES
CLASS 1M
OPTICAL
135 mW
FRM-9D-R-8-EC
Air Inlet Plenum

infn_1164

Turning up a FlexILS as an SNE Page 8-3
Tasks

8-5
8-8
8-10
8-10
Main Chassis Subtending Network 8-13
Element (SNE)“
8-21
8-23
9-2
Channel“ 8-27
Channel“ 8-29
8-30
8-32


8-35
8-36


end.
IMM.

COM1).



Active IMM
(PWR, NC, and
PWR
FLT
PWR
DCE 10/100/1000 BaseT

ACT
FLT
NC
DATA
LINK
LINK
CRAFT
Craft Ethernet
Port
infn_1213

MTC-9.
suggested.



Step 8 Click OK.
Step 9 Click Close.

CAUTION
WARNING
correction.
and correction.
WARNING

correction.
and correction.
Note:
screws
Measure voltage
across the heads
of the terminal
screws.
infn_1212

CAUTION
Initial Start-up
OFF
either PEM)
MTC-9.

Initial Commissioning for the MTC-9 Main Chassis

Subtending Network Element (SNE)
seated).
Note: DCN IP, DCN Netmask, Target Management Subnet, Target Management Subnet
Mask Prefix and Target Management Subnet Gateway are only configured for network
elements that will function as a Gateway Network Element (GNE). For details on the func-
tionality of the GNE refer to the Infinera DTN and DTN-X System Description Guide.
GNM terminal.
previously or not.
 If the IMM was not commissioned previously, see “To initially commission the Main Chassis of an
SNE if the IMM was not commissioned previously” on page 8-14
 If the IMM was commissioned previously, see “To initially commission the Main Chassis of an SNE if
branding procedure.

To initially commission the Main Chassis of an SNE if the IMM was not commissioned previously
session:
then press Enter.




changes.
NE Name? Node1
Router ID? 11.10.2.22
Shelf ID[1-63]? 1
N)[N]?
Main Chassis : yes
NE Name : Node1
Router ID : 11.10.2.22
Shelf ID : 1
chassis_check: (127_1_3_1) (127_1_3_2) (127_2_3_1) (127_2_3_2).
boot up process may cause the IMM to hang and not boot up correctly. Ensure the boot up

To initially commission the Main Chassis of an SNE if the IMM was commissioned previously
session:
Main Chassis : yes
NE Name : Node_2
Router ID : 11.10.2.22
Dcn IP : 10.10.2.20
Shelf ID : 1
then press Enter.


system time.

Router ID(11.10.2.23) ? 11.10.2.22
!!!!!!!!!!!!!!!!!!!!!!!!!!
N)[N]?


(1132135975) Thu Mar 13 10:12:55 2014

Go to Step 13

Go to Step 14
serial cable.

no]?

serial cable.

serial cable.


element connection. If the GNM terminal will be used to verify the IMM craft Ethernet port IP connectivity:
nal IP address.





sage is displayed.

Step 2 In the browser, enter the IMM Craft Ethernet Port IP address of the target MTC-9. Infinera GNM
is launched in a new window and the Login window is displayed.



Software
Version



displayed.


Step 6 Click OK.



Step 11 Click OK.
face.



MTC-9.
nected.

works.




Step 2 Click Apply.
type.

Span/C-Band
tab
Fiber panel


Verifying Span Loss

To verify span loss

IAM/IRM.

Step 6 Click Apply.

Summary panel
IP Gateway Proxy
GNE tab
Primary and
Secondary GNE
IP Addresses




Verifying Inventory
To verify equipment



MTC-9:
Testing IAMs

Testing IRMs
Testing FRMs

Testing FSMs
Testing IMMs
agement interfaces.


the MTC-9.

Alarm Filter panel

Alarm Severity
to customers.
cautions.

Alarm Type Cause

Shutdown (ALS).
Group.
side) have light.
NCT1 Loss of Enet Link from • Expansion Chassis not present or con-
Controller B (NCT port not connectivity with expansion chassis failed.
nected)

support input and output alarm contacts to monitor and control customer’s equipment. Alarm input contacts
allow users to connect external equipment (reactors), such as fire, alarm detector, high temperature
detector, door open and so on to the MTC-9. When the connected equipment triggers an input contact
point, it raises an alarm with an alarm message and severity as configured by the user. Alarm output
contacts allow users to connect external equipment to the MTC-9.



user interface.
Relay



Alarm Cutoff (ACO)

The MTC-9 system provides a feature to acknowledge an alarm condition and turn off the audible
indicator. The ACO push button is used to mute the current audible alarms and is located on the chassis or
can be operated remotely through the Infinera GNM interface. When the ACO is enabled, all the
outstanding audio alarms are turned off and the ACO LED on the chassis is illuminated. The ACO LED
indicates that one or more audible alarms are present, but the audible indicators have been muted. The
ACO LED is turned off when the silenced audible alarms are cleared. The alarm acknowledgment by the
user does not change the ACO LED state.

To enable an ACO
tons).
Testing an ACO
to be audible.
To test an ACO


node configuration.
Note: Infinera GNM may be launched from the Ethernet craft port of an IMM installed in an
Expansion Chassis.

procedure.

CHAPTER 9
Turning up an MTC-9 as an
Expansion Chassis
This chapter provides the procedures to turn up and test an MTC-9 as an Expansion Chassis and is
“MTC-9 Expansion Chassis Turn-up” on page 9-2

Page 9-2 MTC-9 Expansion Chassis Turn-up
MTC-9 Expansion Chassis Turn-up

This section provides the turn-up and test procedures for an MTC-9 Expansion Chassis.

Fan Tray
PEMs Tray Filter
Cable
Management
PEM
A/B
IOP IOP
PWR
FLT
Slot 9 Reserved
for IMM 9
8
Redundant IMM
Universal Blank 7
AIRFLOW DIRECTION
6
DIRECTEMENT AVEC
NE PAS REGARDER
DES INSTRUMENTS
LASER PRODUCT
INVISIBLE LASER
LASER INVISIBLE
PRODUIT LASER
DIRECTLY WITH
RAYONNEMENT
INSTRUMENTS
DO NOT VIEW
1525-1565 nm
RADIATION
OPTIQUES
CLASS 1M
OPTICAL
135 mW
5
IAMs/IRMs/
IAM-B-ECXH2
FRMs/FSMs
4
2
DIRECTEMENT AVEC
NE PAS REGARDER
DES INSTRUMENTS
LASER PRODUCT
INVISIBLE LASER
LASER INVISIBLE
PRODUIT LASER
DIRECTLY WITH
RAYONNEMENT
INSTRUMENTS
DO NOT VIEW
1525-1565 nm
RADIATION
OPTIQUES
CLASS 1M
OPTICAL
135 mW
FRM-9D-R-8-EC
Air Inlet Plenum

infn_1164

Turning up an MTC-9 as an Expansion Chassis Page 9-3
Tasks
Table 9-1 MTC-9 Expansion Chassis Turn-up Checklist and Test Results

9-4
9-6
“Installing MTC-9 Multi-chassis NC page
9-22
9-24
“Interconnecting Line Side Fibers page (if applicable)
“Configuring the Optical Supervisory page (if applicable)
Channel“ 9-27
“Verifying the Optical Supervisory page (if applicable)
Channel“ 9-29
“Provisioning Fiber Information“ page (if applicable)
9-30
“Verifying Span Loss“ page (if applicable)
9-32
9-35
9-36

CAUTION
WARNING
correction.
and correction.
WARNING

correction.
and correction.
Note:
screws
Measure voltage
across the heads
of the terminal
screws.
infn_1212

CAUTION
Initial Start-up
OFF
either PEM)
MTC-9.

Initial Commissioning for the MTC-9 Expansion Chassis
seated).
the MTC-9. Wait for the following message to be displayed:
then press Enter.


[N]?

serial cable.
process. When the PWR and ACT LEDs are all lit solid Green the IMM has completed booting up. This
indicates the IMM is operational (and safe to remove the serial cable).

Installing MTC-9 Multi-chassis NC Ethernet Cables

In a multi-chassis configuration, chassis are interconnected at the nodal control (NC) ports of the IMMs
using straight-through unshielded twisted pair CAT6 Ethernet cables that conform to 100BaseTX (IEEE
802.3) specifications, with male RJ-45 connectors at both ends. The maximum length allowed for each NC
cable segment between chassis is 328 feet (100 meters). A third-party Ethernet media converter can be
used for connecting NC ports to support extended distances. Contact your Infinera account team for
assistance with third-party Ethernet media converters.
Release 10.0 certifies the following FlexILS multi-chassis configurations:
A FlexILS ROADM can support up to 16 interconnected chassis (up to 12 MTC-9s and up to 4
OTCs. The Main Chassis must be an MTC-9; the Expansion Chassis can be any combination of
MTC-9/OTCs
A FlexILS Optical Line Amplifier can support one MTC-9 only (Main Chassis). Multi-chassis support
is not available on a FlexILS Optical Line Amplifier
Refer to “Installing XTC Multi-chassis NC Ethernet Cables” on page 5-14 for DTN-X multi-chassis
configurations consisting of XTC/MTC-9/DTC/MTC/OTCs. This section is organized as follows:
 Cabling a multi-chassis configuration for fully redundant IMMs, see one of the following:
“To connect NC cables for multi-chassis (MTC-9-to-MTC-9) with full IMM redundancy” on
page 9-10
“To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) with full IMM redundancy” on
page 9-12
 Cabling a multi-chassis configuration for IMM redundancy only on the Main Chassis, see one of the
following:
“To connect NC cables for multi-chassis (MTC-9-to-MTC-9) with IMM redundancy only on Main

“To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) with IMM redundancy only on
 Cabling a multi-chassis configuration for non-redundant IMMs, see one of the following:
“To connect NC cables for multi-chassis (MTC-9-to-MTC-9) non-redundant IMMs” on page 9-18
 “To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) non-redundant IMMs” on

page 9-20
plane availability.
To connect NC cables for multi-chassis (MTC-9-to-MTC-9) with full IMM redundancy
In the procedure below, the following convention is used to specify NC ports on a particular MTC-9 chassis:
For example, NC port 1 ACT on chassis 1 is specified as 1-NC-1 ACT. The last chassis in the configuration
is referred to as chassis n.
The final logical connectivity is shown in Figure 9-3 on page 9-11 where full IMM redundancy is available

Figure 9-3 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9) with Full IMM Redundancy
MTC-9
Chassis 1
IMM Active (ACT) IMM Standby (STBY)
NC 1 NC 1
NC 2 NC 2
MTC-9
Chassis 2
IMM ACT IMM STBY
NC 1 NC 1
NC 2 NC 2
MTC-9
Chassis n
IMM ACT IMM STBY
NC 1 NC 1
NC 2 NC 2

To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) with full IMM redundancy
In the procedure below, the following convention is used to specify NC ports on a particular MTC-9 chassis
and NCT ports on a particular OTC chassis:
 On the MTC-9: [ChassisID]-NC-[PortNumber] [Active (ACT) or Standby (STBY) controller].
For example, NC port 1 on chassis 1 with the Active IMM is specified as 1-NC-1 ACT
 On the OTC: [ChassisID]-NCT-[PortNumber][A|B].
Step 3 Connect n-NCT-1A to 1-NC-2 STBY.
Step 6 Connect n-NCT-1B to 1-NC-2 ACT.

Figure 9-4 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9/OTC) with Full IMM Redundancy
MTC-9
Chassis 1
NC 1 NC 1
NC 2 NC 2
MTC-9
Chassis 2
IMM ACT IMM STBY
NC 1 NC 1
NC 2 NC 2
OTC
Chassis n I/O Alarm Panel
OMM OMM
in 1A CPU in 1B CPU
Nodal Control (NC/NCT) Switch/ Switch/

Cable Connection Router Router
infn_1266

To connect NC cables for multi-chassis (MTC-9-to-MTC-9) with IMM redundancy only on Main
Chassis
For example, NC port 1 on chassis 1 is specified as 1-NC-1. The last chassis in the configuration is
referred to as chassis n.

Figure 9-5 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9) with IMM Redundancy only on Main
Chassis
MTC-9
Chassis 1
NC 1 NC 1
NC 2 NC 2
MTC-9
Chassis 2
IMM ACT
NC 1
NC 2
MTC-9
Chassis n IMM ACT
NC 1
NC 2

To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) with IMM redundancy only on Main
Chassis
Step 2 Connect 2-NC-2 ACT to n-NTC-1B.
Step 3 Connect n-NTC-2B to 1-NC-1 ACT.

Main Chassis
MTC-9
Chassis 1
NC 1 NC 1
NC 2 NC 2
MTC-9
Chassis 2
IMM ACT
NC 1
NC 2
OTC
OMM
in 1B CPU
Nodal Control (NC/NCT)

Cable Connection Switch/
Router
infn_1265

To connect NC cables for multi-chassis (MTC-9-to-MTC-9) non-redundant IMMs
Step 3 Connect n-NC-2 ACT to 1-NC-1 ACT.
The final logical connectivity is shown in Figure 9-7 on page 9-19 where redundancy is not available on
any chassis on the network element.

Figure 9-7 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9) Non-redundant IMMs
MTC-9
Chassis 1
IMM Active (ACT)
NC 1
NC 2
MTC-9
Chassis 2
IMM ACT
NC 1
NC 2
MTC-9
Chassis n IMM ACT
NC 1
NC 2

To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) non-redundant IMMs

Figure 9-8 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9/OTC) Non-redundant IMMs
MTC-9
Chassis 1
IMM Active (ACT)
NC 1
NC 2
MTC-9
Chassis 2
IMM ACT
NC 1
NC 2
OTC
OMM
in 1B CPU

Router
infn_1264

Note: Infinera GNM may be launched from the Ethernet craft port of an IMM installed in an Expan-
sion Chassis.
sage is displayed.




Discovered
Chassis
Serial Number


Step 6 Click Ok.
Step 7 Click Close.



MTC-9.
nected.

works.




Step 2 Click Apply.
type.

Span/C-Band
tab
Fiber panel


Verifying Span Loss

To verify span loss

IAM/IRM.

Step 6 Click Apply.

Summary panel
IP Gateway Proxy
GNE tab
Primary and
Secondary GNE
IP Addresses




Verifying Inventory
To verify equipment



MTC-9:
Testing IAMs

Testing IRMs
Testing FRMs

Testing FSMs
Testing IMMs
agement interfaces.


the MTC-9.

Alarm Filter panel

Alarm Severity
to customers.
cautions.

Alarm Type Cause

Shutdown (ALS).




user interface.
Relay



Alarm Cutoff (ACO)


To enable an ACO
tons).
Testing an ACO
to be audible.
To test an ACO

CHAPTER 10
Turning up a FlexILS ROADM Multi-

chassis Network Element
This chapter provides the procedures to turn up and test a FlexILS Reconfigurable Optical Add/Drop
Multiplexer (ROADM) multi-chassis network element and is organized into the following sections:
“FlexILS ROADM Turn-up and Test Overview” on page 10-2

Page 10-2 FlexILS ROADM Turn-up and Test Overview
FlexILS ROADM Turn-up and Test Overview

In Release 10.0, a FlexILS multi-chassis network element (a network element with an MTC-9 as a Main
Chassis) can be configured with an MTC-9 Expansion Chassis to support colorless ROADM (optical
express) functionality. For additional information, refer to the Infinera DTN and DTN-X System Description
Guide.
This section contains the following:
“FlexILS Colorless ROADM Configuration” on page 10-2
FlexILS Colorless ROADM Configuration

Figure 10-1 shows an example of a FlexILS colorless ROADM configuration.
Figure 10-1 Example Configuration of a FlexILS Colorless ROADM

Main Chassis
MTC-9
SYSTEM LINE
FRM IN/OUT IN/OUT
IAM
FRM 1A
FSP-E
SYSTEM
IN
FRM 2A
LINE
OUT
MTC-9
IAM
SYSTEM LINE
FRM IN/OUT IN/OUT
LINE
IN IAM
SYSTEM infn_1287
OUT Expansion Chassis

Turning up a FlexILS ROADM Multi-chassis Network Element Page 10-3

 Main Chassis (MTC-9 base chassis) with one FlexROADM Module (FRM), and one Infinera Line
System (ILS) Amplifier Module (IAM) or ILS Raman Amplifier Module (IRM) installed
Note: A base MTC-9 chassis contains at least one Infinera Management Module (IMM).
 Expansion Chassis (MTC-9 base chassis) with one FRM, and one IAM or IRM installed
A Fiber Panel Chassis (FPC) with one FSP-E module



Fan Tray
PEMs Tray Filter
Cable
Management
PEM
A/B
IOP IOP
PWR
FLT
Slot 9 Reserved
for IMM 9
8
Redundant IMM
Universal Blank 7
AIRFLOW DIRECTION
6
DIRECTEMENT AVEC
NE PAS REGARDER
DES INSTRUMENTS
LASER PRODUCT
INVISIBLE LASER
LASER INVISIBLE
PRODUIT LASER
DIRECTLY WITH
RAYONNEMENT
INSTRUMENTS
DO NOT VIEW
1525-1565 nm
RADIATION
OPTIQUES
CLASS 1M
OPTICAL
135 mW
5
IAMs/IRMs/
IAM-B-ECXH2
FRMs/FSMs
4
2
DIRECTEMENT AVEC
NE PAS REGARDER
DES INSTRUMENTS
LASER PRODUCT
INVISIBLE LASER
LASER INVISIBLE
PRODUIT LASER
DIRECTLY WITH
RAYONNEMENT
INSTRUMENTS
DO NOT VIEW
1525-1565 nm
RADIATION
OPTIQUES
CLASS 1M
OPTICAL
135 mW
FRM-9D-R-8-EC
Air Inlet Plenum

infn_1164

Tasks
“FlexILS ROADM Turn-up and Test page

Overview“ 10-2
10-7
10-10
10-12
10-14
“Initial Commissioning for the MTC-9 page (if applicable)
Main Chassis Gateway Network Ele- 10-15 NOTE: If you are initially commissioning the
ment (GNE)“ MTC-9 for SNE, skip this task and proceed to the
next.
“Initial Commissioning for the MTC-9 page (if applicable)
Main Chassis Subtending Network 10-24 NOTE: If you have initially commissioned the
Element (SNE)“ MTC-9 for GNE, skip this task and proceed to the
next.
“Verifying DCN IP Connectivity“ page (if applicable)
10-32 NOTE: If you have initially commissioned the
MTC-9 for SNE, skip this task and proceed to the
next.
“Installing MTC-9 Multi-chassis NC page
10-46
10-48


“Installing the Standby IMM“ page
10-53
10-54
9-2
“Creating a Fiber Panel“ page
10-55
“Interconnecting the FSP-E Fibers“ page
10-56
“Associating the FRM Ports on the page
Fiber Panel“ 10-57
“Provisioning an Optical Cross-con- page
nect“ 10-58


end.
IMM.

COM1).



Active IMM
(PWR, NC, and
PWR
FLT
PWR
DCE 10/100/1000 BaseT

ACT
FLT
NC
DATA
LINK
LINK
CRAFT
Craft Ethernet
Port
infn_1213

MTC-9.
suggested.



Step 8 Click OK.
Step 9 Click Close.

CAUTION
WARNING
correction.
and correction.
WARNING

correction.
and correction.
Note:
screws
Measure voltage
across the heads
of the terminal
screws.
infn_1212

CAUTION
Initial Start-up
OFF
either PEM)
MTC-9.

Initial Commissioning for the MTC-9 Main Chassis Gateway

seated).
previously or not.
 If the IMM was not commissioned previously, see “To initially commission the Main Chassis of a
GNE if the IMM was not commissioned previously” on page 10-15
 If the IMM was commissioned previously, see “To initially commission the Main Chassis of a GNE if
branding procedure.
To initially commission the Main Chassis of a GNE if the IMM was not commissioned previously
session:
then press Enter.



located.


changes.
Thu Mar 13 09:59:47 2014
The IMM boot process will stop at Do you want to go ahead with reconfiguration[yes|no].
Thu Mar 13 10:02:20 2014
Thu Mar 13 10:02:20 2014
Main Chassis : yes
NE Name : Node1
Router ID : 11.100.179.195
Dcn IP : 10.100.179.195

Dcn Netmask : 255.255.255.224

Shelf ID : 1
serial cable.

To initially commission the Main Chassis of a GNE if the IMM was commissioned previously
session:
Main Chassis : yes
NE Name : Node_2
Router ID : 11.10.2.23
Dcn IP : 10.10.2.21
Dcn Netmask : 255.255.252.0
Shelf ID : 1
then press Enter.





Router ID(11.10.2.23) ? 11.10.2.22
!!!!!!!!!!!!!!!!!!!!!!!!!!
Dcn IP(10.10.2.21) ? 10.10.2.20
Dcn Netmask(255.255.252.0) ?
N)[N]?
(1132135975) Thu Mar 13 10:12:55 2014



Go to Step 17

Go to Step 18
serial cable.

no]?
serial cable.

serial cable.

Initial Commissioning for the MTC-9 Main Chassis

seated).
GNM terminal.
previously or not.
 If the IMM was not commissioned previously, see “To initially commission the Main Chassis of an
SNE if the IMM was not commissioned previously” on page 10-25
 If the IMM was commissioned previously, see “To initially commission the Main Chassis of an SNE if
branding procedure.

To initially commission the Main Chassis of an SNE if the IMM was not commissioned previously
session:
then press Enter.




and repeat the steps in case a mistake was made, or B to reboot the IMM and discard the
changes.
NE Name? Node1
Router ID? 11.10.2.22
Shelf ID[1-63]? 1
N)[N]?
Main Chassis : yes
NE Name : Node1
Router ID : 11.10.2.22
Shelf ID : 1
chassis_check: (127_1_3_1) (127_1_3_2) (127_2_3_1) (127_2_3_2).
boot up process may cause the IMM to hang and not boot up correctly. Ensure the boot up

To initially commission the Main Chassis of an SNE if the IMM was commissioned previously
session:
Main Chassis : yes
NE Name : Node_2
Router ID : 11.10.2.22
Dcn IP : 10.10.2.20
Shelf ID : 1
then press Enter.


system time.

and repeat the steps in case a mistake was made, or B to reboot the IMM and discard the
Router ID(11.10.2.23) ? 11.10.2.22
!!!!!!!!!!!!!!!!!!!!!!!!!!
N)[N]?


(1132135975) Thu Mar 13 10:12:55 2014

Go to Step 13

Go to Step 14
serial cable.

no]?

serial cable.

serial cable.


element connection.
If the GNM terminal will be used to verify the IMM craft Ethernet port IP connectivity:
minal IP address.






minal IP address.



To test the DCN IP connection of the target MTC-9

Step 2 Enter the DCN IP address of the target MTC-9 in the web address (URL) field. If the connection
is established, a login window is displayed. This verifies DCN IP connectivity to the network ele-
ment.

Installing MTC-9 Multi-chassis NC Ethernet Cables

In a multi-chassis configuration, chassis are interconnected at the nodal control (NC) ports of the IMMs
using straight-through unshielded twisted pair CAT6 Ethernet cables that conform to 100BaseTX (IEEE
802.3) specifications, with male RJ-45 connectors at both ends. The maximum length allowed for each NC
cable segment between chassis is 328 feet (100 meters). A third-party Ethernet media converter can be
used for connecting NC ports to support extended distances. Contact your Infinera account team for
assistance with third-party Ethernet media converters.
Release 10.0 certifies the following FlexILS multi-chassis configurations:
A FlexILS ROADM can support up to 16 interconnected chassis (up to 12 MTC-9s and up to 4
OTCs. The Main Chassis must be an MTC-9; the Expansion Chassis can be any combination of
MTC-9/OTCs
A FlexILS Optical Line Amplifier can support one MTC-9 only (Main Chassis). Multi-chassis support
is not available on a FlexILS Optical Line Amplifier
Refer to “Installing XTC Multi-chassis NC Ethernet Cables” on page 5-14 for DTN-X multi-chassis
configurations consisting of XTC/MTC-9/DTC/MTC/OTCs. This section is organized as follows:
 Cabling a multi-chassis configuration for fully redundant IMMs, see one of the following:
“To connect NC cables for multi-chassis (MTC-9-to-MTC-9) with full IMM redundancy” on
page 10-34
“To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) with full IMM redundancy” on
page 10-36
 Cabling a multi-chassis configuration for IMM redundancy only on the Main Chassis, see one of the
following:
“To connect NC cables for multi-chassis (MTC-9-to-MTC-9) with IMM redundancy only on Main

“To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) with IMM redundancy only on
 Cabling a multi-chassis configuration for non-redundant IMMs, see one of the following:
“To connect NC cables for multi-chassis (MTC-9-to-MTC-9) non-redundant IMMs” on page 10-
42
 “To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) non-redundant IMMs” on
page 10-44
plane availability.
To connect NC cables for multi-chassis (MTC-9-to-MTC-9) with full IMM redundancy
For example, NC port 1 ACT on chassis 1 is specified as 1-NC-1 ACT. The last chassis in the configuration
is referred to as chassis n.
The final logical connectivity is shown in Figure 10-10 on page 10-35 where full IMM redundancy is
available on every chassis on the network element.

Figure 10-10 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9) with Full IMM Redundancy
MTC-9
Chassis 1
NC 1 NC 1
NC 2 NC 2
MTC-9
Chassis 2
IMM ACT IMM STBY
NC 1 NC 1
NC 2 NC 2
MTC-9
Chassis n
IMM ACT IMM STBY
NC 1 NC 1
NC 2 NC 2

To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) with full IMM redundancy
Step 3 Connect n-NCT-1A to 1-NC-2 STBY.
Step 6 Connect n-NCT-1B to 1-NC-2 ACT.
available on every chassis on the network element.

Figure 10-11 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9/OTC) with Full IMM Redundancy
MTC-9
Chassis 1
NC 1 NC 1
NC 2 NC 2
MTC-9
Chassis 2
IMM ACT IMM STBY
NC 1 NC 1
NC 2 NC 2
OTC
OMM OMM
in 1A CPU in 1B CPU
Nodal Control (NC/NCT) Switch/ Switch/

Cable Connection Router Router
infn_1266

To connect NC cables for multi-chassis (MTC-9-to-MTC-9) with IMM redundancy only on Main
Chassis
available on chassis 1 (Main Chassis) only.

Main Chassis
MTC-9
Chassis 1
NC 1 NC 1
NC 2 NC 2
MTC-9
Chassis 2
IMM ACT
NC 1
NC 2
MTC-9
Chassis n IMM ACT
NC 1
NC 2

To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) with IMM redundancy only on Main
Chassis
Step 2 Connect 2-NC-2 ACT to n-NTC-1B.
available on chassis 1 (Main Chassis) only.

Figure 10-13 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9/OTC) with IMM Redundancy only
on Main Chassis
MTC-9
Chassis 1
NC 1 NC 1
NC 2 NC 2
MTC-9
Chassis 2
IMM ACT
NC 1
NC 2
OTC
OMM
in 1B CPU

Router
infn_1265

To connect NC cables for multi-chassis (MTC-9-to-MTC-9) non-redundant IMMs
Step 3 Connect n-NC-2 ACT to 1-NC-1 ACT.

Figure 10-14 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9) Non-redundant IMMs
MTC-9
Chassis 1
IMM Active (ACT)
NC 1
NC 2
MTC-9
Chassis 2
IMM ACT
NC 1
NC 2
MTC-9
Chassis n IMM ACT
NC 1
NC 2

To connect NC cables for multi-chassis (MTC-9-to-MTC-9/OTC) non-redundant IMMs

Figure 10-15 NC Connectivity for Multi-chassis (MTC-9-to-MTC-9/OTC) Non-redundant IMMs
MTC-9
Chassis 1
IMM Active (ACT)
NC 1
NC 2
MTC-9
Chassis 2
IMM ACT
NC 1
NC 2
OTC
OMM
in 1B CPU

Router
infn_1264

sage is displayed.




should be recorded in Table 10-1 on page 10-5. The software release version is of the format X.Y.Z
where X is the major version number, Y is the minor version number, and Z is the maintenance version
number.

Software
Version



displayed.


Step 6 Click OK.



Step 11 Click OK.
face.

Step 6 Click Apply.

Summary panel
IP Gateway Proxy
GNE tab
Primary and
Secondary GNE
IP Addresses




Verifying Inventory
To verify equipment


Creating a Fiber Panel

Perform the following procedure to create a Fiber Panel. The Fiber Panel consists of Fiber Shuffle Panel
(FSP) and/or Fiber Multiplexing Panel (FMP) modules which provide fiber connectivity to/from
FlexROADM Modules (FRMs) and/or FlexROADM Switching Modules (FSMs) residing on an MTC-9.
Step 1 From the Equipment Tree, right-click the network element icon and select Create FP. The Cre-
ate FP window is displayed.
Step 2 Click the FP Type drop-down menu and select FSP-E-9D-18MPO. See Figure 10-23.
Step 3 Enter a value in the AID field.
The AID field is an alpha-numeric string (identifier) used to identify the Fiber Panel. The string
can have a maximum of 40 characters.
The label is an optional field (a character string with a maximum of 128 characters) assigned to
further identify the Fiber Panel.
Step 5 Enter a value in the Serial Number field.
The serial number field (a character string with a maximum of 60 characters) represents the
manufacturing serial number of the installed equipment.
Step 6 Click Apply.
Step 7 Repeat Step 1 through Step 6 for additional Fiber Panels.
Figure 10-23 Creating a Fiber Panel (FSP-E) for a FlexILS ROADM Configuration
FP Type

Interconnecting the FSP-E Fibers

The Fiber Panel consists of Fiber Shuffle Panel (FSP) and/or Fiber Multiplexing Panel (FMP) modules that
provide fiber connectivity to/from FlexROADM Modules (FRMs) and/or FlexROADM Switching Modules
(FSMs) residing on an MTC-9.
To interconnect the FSP/FMP fibers, refer to “Connect and Route FSP/FMP Fiber Optic Cables” on
page C-44.

Associating the FRM Ports on the Fiber Panel

Perform the following procedure to associate the FRM express ports on the Fiber Panel.
To associate the FRM express ports on the Fiber Panel
Step 3 Click Apply.
Figure 10-24 Associating the FRM Express Ports on the Fiber Panel
MPO Connections tab

Provisioning an Optical Cross-connect
To provision an optical cross-connect from an FRM line port to an FRM line port
Perform the following procedure to create an express optical cross-connect from an FRM line port to an
FRM line port.
Step 1 From the Equipment View, right-click the FRM and select Provisioning -> Create Optical
Connectivity
Step 2 Click the Connectivity drop-down menu and select Express.

Step 3 Click Next.

Endpoints)
Circuit ID (CID)
Label
Source Endpoint
Destination
Endpoint

Step 6 In the Source Endpoint field, click the [...] button. The Endpoint Source window is
displayed.


Step 8 Click Ok.
displayed.

Step 11 Click Ok.

mended).
Step 13 Click Ok.



MTC-9:
Testing IAMs

Testing IRMs
Testing FRMs

Testing FSMs
Testing IMMs
agement interfaces.


the MTC-9.

Alarm Filter panel

Alarm Severity
to customers.
cautions.

Alarm Type Cause

Shutdown (ALS).




user interface.
Relay



Alarm Cutoff (ACO)


To enable an ACO
tons).
Testing an ACO
to be audible.
To test an ACO


node configuration.
Note: Infinera GNM may be launched from the Ethernet craft port of an IMM installed in an
Expansion Chassis.

procedure.

CHAPTER 11
Turning up a DTN as a GNE
This chapter provides the procedures to turn up and test a DTN as a Gateway Network Element (GNE).
“DTN Main Chassis Turn-up” on page 11-2
“Testing DTC/MTC Circuit Packs” on page 11-102

Page 11-2 DTN Main Chassis Turn-up
DTN Main Chassis Turn-up

Note: Unless specifically noted otherwise, all references to the “line module” will refer to either the
DLM, XLM, ADLM, AXLM, and/or SLM interchangeably. All references to the “LM-80” will
refer to the ADLM-80, AXLM-80, and/or SLM-80 interchangeably.
The DTN consists of at least one Digital Transport Chassis (DTC) or MTC, and zero or more Dispersion
Management Chassis (DMC).
Figure 11-1 on page 11-3 shows the various hardware components of the DTC.
Figure 11-2 on page 11-4 shows the various hardware components of the MTC.
The DTC-A is generally no longer available but is still supported; all DTNs currently shipping contain either
the DTC-B or MTC chassis types. The DTC-B is fully backward compatible with the DTC-A and uses all of
the existing hardware currently deployed in the DTC-A.
For detailed information on the functionality and capabilities of the DTC-A, DTC-B, and MTC, refer to the
Infinera DTN and DTN-X System Description Guide.

Turning up a DTN as a GNE Page 11-3
Figure 11-1 DTC Front View
Note: The DTC-A and the DTC-B chassis look very similar. The two chassis can be differentiated
by looking on the fiber tray: the DTC-B has a label to identify the chassis as a DTC-B,
whereas there is no label on the DTC-A. In addition, there is a product label on the right
side of the chassis that includes the Product Ordering Name (PON) of the chassis.

Figure 11-2 MTC Front View

Tasks
Table 11-1 DTN Turn-up Checklist and Test Results

11-8
11-11
“Verifying Power to the DTC/MTC“ page
11-14
“Powering up the DTC/MTC“ page
11-17
“Initial Commissioning for the DTC/ page
MTC Main Chassis Gateway Network 11-18
Element (GNE)“
“Verifying MCM Craft Ethernet Port IP page
11-28
11-29
11-33
“Configuring the Chassis for Mesh page (if applicable)
Switching Mode“ 11-36
“Entering Expansion BMM Informa- page (if applicable)
tion on a Base BMM2“ 11-39
Channel“ 11-44
Channel“ 11-46

“Interconnecting Line Module to BMM page

OCG Fibers“ 11-47
“Interconnecting Expansion Fibers page (if applicable)
between Base and Expansion BMMs“ 11-48
“Verifying Line Module Auto-discovery page
Completion“ 11-49
11-50
“Verifying Optical Carrier Group page
ules“
“Interconnecting LM-80 to CMM and page (if applicable)
CMM to BMM OCH/OCG Fibers“ 11-72
“Configuring LM-80 OCH Ports“ page (if applicable)
11-73
“Configuring CMM OCG and OCH page (if applicable)
Ports“ 11-75
(OCG) Loss Threshold for CMMs“ 11-78
“Verifying Optical Channel (OCH) page (if applicable)
Loss Threshold for CMMs“ 11-81
“Configuring BMM Channels“ page
11-84
“Entering DCM/DSE Information“ page (if applicable)
11-86
11-87
“Entering Span Loss between Adja- page
cent Nodes“ 11-89
11-92
Port“ 11-99

“Installing the Standby MCM“ page (if applicable)

11-
100
11-
101


Before performing the turn-up and test procedures on a DTC/MTC, a serial connection between the
network element and the craft computer (referred to as GNM terminal) must be established. Serial
connectivity requires an RS-232 serial cable with a DB-9 male connector at one end and a USB connector
at the other end.
MCM.

COM1).
Note: This window should be kept open until the initial commissioning of the DTC/MTC is com-
plete.


Infinera GNM interface. The DTC/MTC provides a craft Ethernet port on the MCM. The following procedure
describes how to connect an Ethernet cable to the MCM. Ethernet connectivity requires either a straight-
used to access the Infinera GNM from the MCM is 192.168.0.1. The default subnet mask that is used to
access the Infinera GNM from the MCM is 255.255.255.0.

Step 2 Connect the Ethernet cable to the connector labeled Craft on the active MCM.
Note: If there is a redundant MCM, it should not be installed in the slot at this time.
DTC/MTC.
suggested.



address should be in the same subnet as the IP address configured for the target MCM or the
DTC/MTC. The last octet must vary between 2 and 255.
Note: The default IP address of the MCM is: 192.168.0.1.

Step 8 Click OK.
Step 9 Click Close.

Verifying Power to the DTC/MTC
CAUTION
CAUTION
Ensure that only the PEMs and fan trays are fully seated in the DTC/MTC. Additionally,
ensure that all modules occupying slots 3, 4, 5, 6, 7A, and 7B are not seated prior to per-
forming this procedure.
Perform the following procedure to verify the power to the DTC/MTC.
To verify power supply to the DTC/MTC
Step 1 At the battery distribution fuse bay (BDFB) power source that feeds the DTC/MTC POWER A
and B circuit breakers (PEM A and PEM B), verify that the power is turned off.
Step 2 At the DTC/MTC, verify that the POWER A and POWER B circuit breakers (PEM A and B) are
set to the OFF position and perform the following.
Step 3 At the BDFB power source for PEM A, turn on the power.
WARNING
Step 4 At the DTC/MTC POWER A circuit breaker (PEM A), using a multimeter set to measure DC
polarity, verify that the polarity is correct (must be negative). If the polarity is incorrect, report
readings to facilities personnel for further troubleshooting and correction.
Step 5 At the BDFB power source for PEM A, turn off the power.
Step 6 At the BDFB power source for PEM B, turn on the power.
WARNING
Step 7 At the DTC/MTC POWER B circuit breaker (PEM B), using a multimeter set to measure DC

Step 8 At the BDFB power source for PEM B, turn off the power.
WARNING
Step 10 At the DTC/MTC, turn the POWER A circuit breaker (PEM A) to ON.
terminal studs (not the lugs) at PEM A. See Figure 11-9 on page 11-16.
Step 11a If the reading is within the specified range (-40 to -72V DC), proceed to Step 11b. If
the measured voltage is not within the specified range, report readings to facilities
(there should be no voltage present). If no voltage is measured, proceed to Step 12.
If voltage is present, report readings to facilities personnel for further troubleshooting
and correction.
Step 12 At the DTC/MTC, turn the POWER A circuit breaker (PEM A) to OFF.
WARNING
Step 14 At the DTC/MTC, turn the POWER B circuit breaker (PEM B) to ON.
terminal studs (not the lugs) at PEM B. See Figure 11-9 on page 11-16.
and correction.
Step 16 At the DTC/MTC, turn the POWER B circuit breaker (PEM B) to OFF and perform the following.
Step 16b Install one MCM into slot 7A or slot 7B (verify that only one MCM is fully seated; if a
redundant MCM is occupying the second slot, ensure that it is not fully seated).
Step 16c Verify that any modules occupying slots 3, 4, 5, and/or 6 are not fully seated.

the DTC/MTC and perform the initial start-up procedure.
Figure 11-9 Measuring DC Voltage at DTC/MTC PEMs
POWER POWER
INPUT FAULT
Terminal studs
RTN

-48V the tips of the terminal
ON OFF
70A
POWER A infn_062a
Note: Figure 11-9 applies to all DTC/MTC PEM types.

Powering up the DTC/MTC
CAUTION
The following section provides the procedure to power up the DTC/MTC.
Initial Start-up
and Hardware Installation Guide), the DTC/MTC may be started up.
To startup the DTC/MTC
set to the OFF position.
Step 2 At the BDFB power source that feeds the DTC/MTC PEM A, turn on the power.
Step 3 At the BDFB power source that feeds the DTC/MTC PEM B, turn on the power.
OFF
either PEM)
After you have verified that power is present on both PEMs and no faults exist, you are ready to initially
configure the DTC/MTC.

Initial Commissioning for the DTC/MTC Main Chassis

Gateway Network Element (GNE)
Note: Ensure that only one MCM is installed (fully seated) in either slots 7A or 7B and any mod-
ules occupying slots 3, 4, 5, and/or 6 are not fully seated.
After you have powered up the DTC/MTC for the first time, the boot up process is initiated. Within a minute
or two of power up, data starts scrolling in the HyperTerminal session. This session will be used to
configure the DTC/MTC. You must have the site specific commissioning data at hand (listed in
“Commissioning Data” on page 2-12 and previously recorded in Table 2-1 on page 2-2).
The procedures to commission a DTC/MTC vary depending on whether the MCM was commissioned
previously or not.
 If the MCM was not commissioned previously, see “To initially commission the Main Chassis of a
GNE if the MCM was not commissioned previously” on page 11-18
 If the MCM was commissioned previously, see “To initially commission the Main Chassis of a GNE if
the MCM was commissioned previously” on page 11-22.
See “XCM/IMM/MCM/OMM Rebranding Flow” on page B-1 for a graphical representation of the MCM
branding procedure.
To initially commission the Main Chassis of a GNE if the MCM was not commissioned previously
If the MCM was not commissioned previously, the following message is displayed in the HyperTerminal
session:
then press Enter.


Step 3 Router ID—Internal router ID (IP address) for communication between the MCMs and OMMs.
The router ID must be unique across the network.
(Cross-over Ethernet cables are required for the DCN ports. Refer to the Infinera DTN and
DTN-X Site Preparation and Hardware Installation Guide for additional information.)

located.


and repeat the steps in case a mistake was made, or B to reboot the MCM and discard the
NE Name? Node1
Router ID? 11.10.2.22
Dcn IP? 10.10.2.20
Dcn Auto Negotiation Enable? True
Dcn Netmask? 255.255.252.0
Target Management Subnet? 10.0.0.0
Target Management Subnet Mask Prefix (#bits)? 8
Note:Static route 10.0.0.0/255.0.0.0 will be added to the routing table
Target Management Subnet Gateway? 10.10.1.1
Shelf ID[1-63]? 1
N)[N]?
The MCM will reboot and the following message is displayed:
Main Chassis : yes
NE Name : Node1
Router ID : 11.10.2.22

Dcn IP : 10.10.2.20
Dcn Netmask : 255.255.252.0
Shelf ID : 1
chassis_check: (127_1_3_1) (127_1_3_2) (127_2_3_1) (127_2_3_2).
boot up process may cause the MCM to hang and not boot up correctly. Ensure the boot
up process is complete before disconnecting the serial cable.
The MCM can take some time to complete the boot up process. When the PWR, NC, and ACT LEDs are
all lit solid Green the MCM has completed booting up. This indicates the MCM is operational (and safe to
This completes the initial commissioning of the MCM.

To initially commission the Main Chassis of a GNE if the MCM was commissioned previously
If the MCM was commissioned previously, the following message is displayed in the HyperTerminal
session:
Main Chassis : yes
NE Name : Node_2
Router ID : 11.10.2.23
Dcn IP : 10.10.2.21
Dcn Netmask : 255.255.252.0
Shelf ID : 1
then press Enter.


(Cross-over Ethernet cables are required for the DCN ports. Refer to the Infinera DTN and
DTN-X Site Preparation and Hardware Installation Guide for additional information.)



Router ID(11.10.2.23) ? 11.10.2.22
!!!!!!!!!!!!!!!!!!!!!!!!!!
Dcn IP(10.10.2.21) ? 10.10.2.20
Dcn Netmask(255.255.252.0) ?
N)[N]?
(1132135975) Thu Mar 13 10:12:55 2014
Type yes to re-brand the MCM/OMM.


If the MCM did not have a database stored on it, the following message is displayed:

Go to Step 17
If the MCM had a database stored on it, the following message is displayed:

Go to Step 18
Note: Disconnecting the serial cable during the boot up process may cause the MCM to hang and
serial cable.
This completes the initial commissioning of the MCM. The MCM can take some time to complete the boot
up process. When the PWR, NC, and ACT LEDs are all lit solid Green the MCM has completed booting
up. This indicates the MCM is operational.
Type yes to re-brand the MCM. The following message is displayed:

no]?
serial cable.

Type no if you do not want to re-brand the MCM. The following message is displayed:
serial cable.
up process. When the PWR, NC, and ACT LEDs are all lit solid Green the MCM has completed booting up.
This indicates the MCM is operational (and safe to remove the serial cable).

Verifying MCM Craft Ethernet Port IP Connectivity

To verify MCM craft Ethernet port IP connectivity, first ping the MCM IP address, and then test the network
element connection.
If the GNM terminal will be used to verify the MCM craft Ethernet port IP connectivity:
 Ensure that an Ethernet cable is connected from the GNM terminal to the correct MCM craft Ether-
net port on the DTC/MTC. If the MCM is located in Slot 7A, use MCM craft Ethernet port A. If the
MCM is located in Slot 7B, use MCM craft Ethernet port B
 Verify that the GNM terminal IP address is in the same IP domain as the DTC/MTC
minal IP address.
To ping the MCM craft Ethernet port IP address

ping [MCM Craft Ethernet Port IP Address]


To test the MCM craft Ethernet port IP connection of the target DTC/MTC

Step 2 Enter the MCM craft Ethernet port IP address of the target DTC/MTC in the web address (URL)
field. If the connection is established, a login window is displayed. This verifies MCM craft Ether-
net port IP connectivity to the network element.


To verify DCN IP connectivity, first ping the DCN IP address, and then test the network element connection.
If the GNM terminal will be used to verify the DCN IP connectivity:
DTC/MTC. If the MCM is located in Slot 7A, use DCN port A. If the MCM is located in Slot 7B, use
DCN port B
minal IP address.



To test the DCN IP connection of the target DTC/MTC

Step 2 Enter the DCN IP address of the target DTC/MTC in the web address (URL) field. If the connec-
tion is established, a login window is displayed. This verifies DCN IP connectivity to the network
element.

Note: Infinera GNM may be launched from the Ethernet craft port of an MCM using the craft
sage is displayed.

Step 2 In the browser, enter the DCN IP address of the target DTC/MTC. Infinera GNM is launched in a

conditions (see Figure 11-12 on page 11-31 for DTC and Figure 11-13 on page 11-32 for MTC).

Figure 11-12 Infinera GNM Main View of DTC

Figure 11-13 Infinera GNM Main View of MTC


It is important to know what version of software is on the Active MCM in the DTC/MTC. The software
version should be recorded in Table 11-1 on page 11-5. The software release version is of the format
X.Y.Z where X is the major version number, Y is the minor version number, and Z is the maintenance
version number.

 From the Equipment View, select the Active MCM. The Quick View Browser panel in the lower left
corner displays the MCM software version number as shown in Figure 11-14
Software
Version



displayed.


Step 6 Click OK.



Step 11 Click OK.
face.

Configuring the Chassis for Mesh Switching Mode
Note: This procedure is only required if you need to configure the chassis for Mesh switching
mode.
Note: Unless specifically noted otherwise, all references to the DTC will refer to either the DTC-B
or MTC interchangeably.
Note: DLM/ADLM/ADLM-80s and the DTC-A do not support Mesh switching mode.
BMM2, BMM2P, BMM1H, and/or BMM2H interchangeably.
Perform the following procedure to convert a DTC/MTC from Ring switching mode to Mesh switching
mode.
To configure the chassis for Mesh switching mode
Step 1 At the DTC/MTC, perform the following.

Step 1a Install one MCM into slot 7A or slot 7B (verify that only one MCM is fully seated; if a
Step 1b Install at least one BMM in either slots 1 and/or 2.
Step 2 From the Equipment Tree, right-click on the chassis and select Properties. The Chassis Proper-
ties window is displayed. See Figure 11-17 on page 11-37.
Step 3 In the Chassis Properties window under the Summary panel, for Switching Mode select the
Mesh radio button. See Figure 11-18 on page 11-38.
Step 4 Click Apply.
Step 5 Click Close.
Step 6 Install appropriate modules into slots 3, 4, 5, and/or 6.

Figure 11-17 Equipment Tree
Chassis Slots 3 through 6 (empty)

Figure 11-18 Chassis Properties Window
Switching
Mode

Entering Expansion BMM Information on a Base BMM2
Note: This procedure is only required on the base BMM2/BMM2P/BMM2H at each end of the link.
Note: This procedure assumes that the appropriate BMM2/BMM2P/BMM2H is installed in slot 1
and/or 2.
Perform the following procedure to establish the association between a base and expansion BMM2/
BMM2P/BMM2H for a 160-channel configuration in the DTC or an 80-channel configuration in the MTC.
To enter the expansion BMM information on a base BMM2/BMM2P/BMM2H
Step 1 From the Equipment View, highlight the appropriate base BMM2/BMM2P/BMM2H, right-click
and select Admin State -> Maintenance.
Step 2 Click Apply.
and select Properties. The BMM Properties window is displayed. See Figure 11-19 on
page 11-40.
Step 4 In the Summary panel, click the Expansion BMM drop-down menu and select the appropriate
expansion BMM2/BMM2P/BMM2H to establish the association between a base and expansion
BMM2/BMM2P/BMM2H.
Step 5 When completed, click Apply to save changes.
Step 6 Click Close to exit the BMM Properties window.
and select Admin State -> Unlock.
Step 8 From the Equipment View, highlight the appropriate expansion BMM2/BMM2P/BMM2H, right-
click and select Properties. The BMM Properties window is displayed.
Step 9 Verify that the association between a base and expansion BMM2/BMM2P/BMM2H has been
created. From the Summary panel, verify the setting of the Expansion BMM attribute:
Set to read only (grayed out). See Figure 11-20 on page 11-41
Lists the appropriate expansion BMM2/BMM2P/BMM2H (selected in Step 4)
Step 10 Repeat Step 1 through Step 9 for additional base BMM2/BMM2P/BMM2Hs.

Figure 11-19 BMM Properties: Expansion BMM (viewed from base BMM2/BMM2P/BMM2H)
Expansion BMM

Figure 11-20 BMM Properties: Expansion BMM (viewed from expansion BMM2/BMM2P/BMM2H)
Expansion BMM
(grayed out)

Each DTC/MTC may contain up to two (2) Band Multiplexing Modules (BMMs). Ensure that the appropriate
BMMs are installed in slots 1 and/or 2 of the DTC/MTC prior to performing this procedure. It is
recommended that a node numbering scheme be established for the network. For example, westbound
traffic BMM numbering is from BMM slot 1 (Node A) to BMM slot 2 (Node B) and eastbound traffic is from
BMM slot 2 (Node B) to BMM slot 1 (Node A).
Step 1 Connect line fibers from the OUT (transmit) line port on BMM slot 1 (Node A) to the IN (receive)
line port on BMM slot 2 (Node B) for westbound traffic. Ensure there is appropriate attenuation
(depending on span loss) at the input port of the BMM. Specific attenuation is required for BMM
deployments utilizing TW-C fiber type, refer to Table 11-2 on page 11-43.
Step 2 Connect line fibers from the OUT (transmit) line port on BMM slot 2 (Node B) to the IN (receive)
line port on BMM slot 1 (Node A) for eastbound traffic. Ensure there is appropriate attenuation

Table 11-2 BMM Optical Attenuator Pad Requirement for TW-C Fiber Type
BMM Launch Power (dBm/ch)
Gen 1 Gen 2 Gen 2

(80 Channels) (160 Channels)
0 1.5 -1.5
Channel Count TW-C Target Launch Required Optical

Power (dBm/ch) Attenuator Pad (dB)
10 to 40 -3.0 3 5 2
41 to 80 -3.0 3 5 2
81 to 160 -6.0 N/A N/A 5
Note: Attenuation is required for all links (BMM/BMM2/BMM2P-to-Raman, BMM/BMM2/BMM2P-

to-ORM, BMM-to-BMM, BMM2-to-BMM2, and/or BMM2P-to-BMM2P) when TW-C fiber is
deployed. Ensure that the appropriate optical attenuator pad is installed at the BMM/
BMM2/BMM2P Line Out port.

Note: To enable the OSC connectivity, this configuration must be performed on each BMM at each
end of the link.
Note: For BMM2s, ensure that the operating mode is set to Native-Automated (default).
following procedure to create an optical link and configure the Optical Supervisory Channel (OSC) on each
DTC/MTC.
Step 1 From the Equipment View, highlight the appropriate BMM to which the optical link is connected.
Step 2 Right-click the BMM and select OSC. The OSC Properties window is displayed.

Figure 11-22 GMPLS Link Properties
Note: The OSC IP address and the DCN IP address for each DTC/MTC must be on different IP
networks.
When two DTC/MTCs are physically connected, the OSC IP address configured on the BMMs
must be in the same subnet in order for the OSC to function properly. For example, BMM slot 1
and BMM slot 2 (Node B) will have an address like 192.168.30.2 with Subnet Mask like
Step 10 Repeat Step 1 through Step 9 for the remaining BMMs.

BMM at each end of the link.


Interconnecting Line Module to BMM OCG Fibers
DLM, XLM, ADLM, AXLM, and/or SLM interchangeably.
Each DTC/MTC may contain up to four (4) line modules and up to two (2) Band Multiplexing Modules
(BMMs).
Perform one of the following OCG fiber installation procedures depending on your configuration:
“To connect OCG cables between DLM/XLMs and BMM/BMM1Hs” on page C-55
“To connect OCG cables between DLM/XLMs and BMM2/BMM2Hs (with GAM-1s)” on page C-58
“To connect OCG cables between ADLM/AXLMs and BMM/BMM1H/BMM2/BMM2Hs (without

GAMs)” on page C-62
“To connect OCG cables between ADLM/AXLMs and BMM2/BMM2Hs (with GAM-1s)” on page C-
67
“To connect OCG cables between SLMs and BMM2s” on page C-73
“To connect OCG cables between ADLM/AXLMs and BMM2Ps (with GAM-2s)” on page C-77

Interconnecting Expansion Fibers between Base and

Expansion BMMs
Note: This procedure is only required if your system includes an expansion BMM2/BMM2P and/or
BMM2H.
Each DTC/MTC may contain up to two (2) Band Multiplexing Modules (BMMs).
Perform one of the following expansion fiber installation procedures depending on your configuration:
“To connect expansion fiber cables between a base and expansion BMM2 (160-channel systems)”
on page C-88
“To connect expansion fiber cables between a base and expansion BMM2P (160-channel systems)”
on page C-88
“To connect expansion fiber cables between a base and expansion BMM2H (80-channel systems)”
on page C-89

Each DTC/MTC may contain up to four (4) line modules. Perform the following procedure to verify that
Auto-discovery has completed on each installed line module.
DLM OCG Port Properties window is displayed.
General tab
Connected BMM port

Tx Auto Discovery
State
and repeat Step 1 through Step 3.
Step 4 Click Close.



Each DTC/MTC may contain up to four (4) tunable line modules (ADLM, AXLM, and/or SLM). Perform the
following procedure to verify and/or to configure the operating mode and the installed OCG number for
each tunable line module.
Note: In the event of a power cycle or reboot of the DTC/MTC and/or tunable line module, the
installed OCG number on the associated tunable line module is retained.
Step 2 Click Lock DLM/XLM.
Step 3 From the Equipment View, right-click the tunable line module and select Properties. The
ADLM/AXLM/SLM Properties window is displayed. See Figure 11-25 on page 11-51.
Step 9 Click Close.
Unlock.

Tunable tab
Operating Mode
Provisioned OCG
Number


Line Modules
DLM, XLM, ADLM, AXLM, and/ or SLM interchangeably.
Note: Unless specifically noted otherwise, all references to the GAM will refer to either the
GAM-1 and/or GAM-2 interchangeably.
Perform the following procedure(s) to verify the OCG loss threshold between a line module, GAM (if
required), and BMM in the DTC/MTC. The procedures are listed as follows:
“To verify OCG loss threshold for a Gen 1 system (DLM/XLM to BMM/BMM1H)” on page 11-54
“To verify OCG loss threshold for a Gen 1 system (DLM/XLM to BMM2/BMM2H via GAM-1)” on
page 11-56
“To verify OCG loss threshold for a Gen 1 system (ADLM/AXLM [Gen 1 mode] to BMM/BMM1H)” on
page 11-60
“To verify OCG loss threshold for a Gen 2 system (ADLM/AXLM [Gen 2 mode] to BMM2/BMM2H)”
on page 11-62
“To verify OCG loss threshold for a Gen 2 system (ADLM/AXLM [Gen 1 mode] to BMM2/BMM2H via
GAM-1)” on page 11-64
“To verify OCG loss threshold for a Gen 2 system (ADLM/AXLM [Gen 2 mode] to BMM2P via GAM-
2)” on page 11-68

Table 11-3 shows the supported OCG loss threshold between a line module, GAM (if required), and BMM.
Table 11-3 Supported OCG Loss Threshold between a Line Module, GAM, and BMM
Line Module Type GAM Required BMM Type OCG Loss Out of Range High
(Yes/No) (OORH) Threshold
DLM/XLM No BMM/BMM1H 3dB (from DLM/XLM OCG to

BMM OCG)
DLM/XLM Yes (GAM-1) BMM2/BMM2H 1.5dB (from DLM/XLM OCG to
GAM Trib OCG)
1.5dB (from GAM Line OCG to
BMM OCG)
ADLM/AXLM (set No BMM/BMM1H 3dB (from DLM/XLM OCG to
to Gen 1 mode) BMM OCG)
ADLM/AXLM (set No BMM2/BMM2H 1.5dB (from DLM/XLM OCG to
ADLM/AXLM (set Yes (GAM-1) BMM2/BMM2H 1.5dB (from DLM/XLM OCG to
to Gen 1 mode) GAM Trib OCG)
BMM OCG)
ADLM/AXLM (set Yes (GAM-2) BMM2P 1.5dB (from DLM/XLM OCG to
BMM OCG)

To verify OCG loss threshold for a Gen 1 system (DLM/XLM to BMM/BMM1H)
reported for the DLM OCG (DLM/XLM).
For a Gen 1 system, the supported OCG loss threshold between the DLM/XLM and BMM/BMM1H is 3dB.
Step 1 Right-click the BMM/BMM1H for which you would like to verify the OCG loss threshold and
select Optical Carrier Group. The BMM OCG Port Properties window is displayed.

(OPR).
Step 4 Right-click the DLM/XLM for which you would like to verify the OCG loss threshold and select
Optical Carrier Group. The DLM OCG Port Properties window is displayed.

Figure 11-27 DLM OCG Port Properties
(OPT).
DLM/XLM and BMM/BMM1H is within 3dB.
Loss threshold = DLM OCG OPT - BMM OCG OPR

To verify OCG loss threshold for a Gen 1 system (DLM/XLM to BMM2/BMM2H via GAM-1)
reported for the DLM OCG (DLM/XLM) and an OCG Loss Out of Range - High will be
reported for the GAM OCG.
For a system configured with a Gen 1 DLM/XLM connected to a Gen 2 BMM2/BMM2H via a GAM-1:
 DLM/XLM to GAM-1—supported loss threshold is 1.5dB
 GAM-1 to BMM2/BMM2H—supported loss threshold is 1.5dB
Step 1 Right-click the BMM2/BMM2H for which you would like to verify the OCG loss threshold and

(OPR).

Step 4 Right-click the GAM-1 for which you would like to verify the OCG loss threshold and select Opti-
cal Carrier Group. The GAM OCG Port Properties window is displayed.
Figure 11-29 GAM OCG Port Properties: BMM-to-GAM (OPT)
Step 5 In the list frame, select L1 (Line side).

(OPT).
Step 7 In the list frame, select T1 (Trib side).
(OPR).

Figure 11-30 GAM OCG Port Properties: GAM-to-DLM/XLM (OPR)
(OPT).

DLM/XLM and GAM-1 (Line side) is within 1.5dB, and between the GAM-1 (Trib side) and
BMM2/BMM2H is within 1.5dB.
Loss threshold = DLM OCG OPT - GAM OCG OPR (Trib side)
Loss threshold = GAM OCG OPT (Line side) - BMM OCG OPR

To verify OCG loss threshold for a Gen 1 system (ADLM/AXLM [Gen 1 mode] to BMM/BMM1H)
reported for the DLM OCG (ADLM/AXLM).
For a system configured with a Gen 2 ADLM/AXLM (set to Gen 1 mode) connected to a Gen 1 BMM/
BMM1H, the supported OCG loss threshold is 3dB.

(OPR).
Step 4 Right-click the ADLM/AXLM for which you would like to verify the OCG loss threshold and select

(OPT).
ADLM/AXLM and BMM/BMM1H is within 3dB.

To verify OCG loss threshold for a Gen 2 system (ADLM/AXLM [Gen 2 mode] to BMM2/BMM2H)
For a system configured with a Gen 2 ADLM/AXLM (set to Gen 2 mode) connected to a Gen 2 BMM2/
BMM2H, the supported OCG loss threshold is 1.5dB.

(OPR).

(OPT).
ADLM/AXLM and BMM2/BMM2H is within 1.5dB.

To verify OCG loss threshold for a Gen 2 system (ADLM/AXLM [Gen 1 mode] to BMM2/BMM2H via
GAM-1)
reported for the DLM OCG (ADLM/AXLM) and an OCG Loss Out of Range - High will be
BMM2H via a GAM-1:
 BMM2/BMM2H to GAM-1—supported loss threshold is 1.5dB
 GAM-1 to ADLM/AXLM—supported loss threshold is 1.5dB

(OPR).

(OPT).
(OPR).

Figure 11-38 GAM OCG Port Properties: GAM-to-ADLM/AXLM (OPR)
(OPT).

ADLM/AXLM and GAM-1 (Line side) is within 1.5dB, and between the GAM-1 (Trib side) and

To verify OCG loss threshold for a Gen 2 system (ADLM/AXLM [Gen 2 mode] to BMM2P via GAM-2)
For a system configured with a Gen 2 ADLM/AXLM (set to Gen 2 mode) connected to a Gen 2 BMM2P via
a GAM-2:
 BMM2P to GAM-2—supported loss threshold is 1.5dB
Step 1 Right-click the BMM2P for which you would like to verify the OCG loss threshold and select Opti-
cal Carrier Group. The BMM OCG Port Properties window is displayed.

(OPR).


(OPT).
(OPR).

(OPT).

BMM2P is within 1.5dB.

Interconnecting LM-80 to CMM and CMM to BMM OCH/OCG

Fibers
Note: Unless specifically noted otherwise, all references to the "LM-80" will refer to either the
ADLM-80, AXLM-80, and/or SLM-80 interchangeably.
Note: This procedure is only required if your system includes LM-80s and CMMs.
Each DTC/MTC may contain up to four (4) Channel Multiplexing Modules (CMMs) and/or LM-80s, and up
to two (2) Band Multiplexing Modules (BMMs).
Perform the following OCH/OCG fiber installation procedure:
 “To connect OCH and OCG cables between ADLM-80/AXLM-80/SLM-80s, CMMs, and BMMs” on
page C-80

Configuring LM-80 OCH Ports
Note: This procedure assumes that the BMMs, CMMs, and LM-80s are physically installed, the
necessary fiber optic cables have been connected, and Auto-discovery has completed for
all installed modules as part of the configuration.
Each DTC/MTC may contain up to four (4) LM-80s and/or Channel Multiplexing Modules (CMMs), and up
to two (2) Band Multiplexing Modules (BMMs). Perform the following procedure to verify and/or configure
the LM-80 OCH port(s).
To verify and/or configure LM-80 OCH ports
Step 1 From the Equipment View, locate the appropriate LM-80, right-click the OCH port and select
Admin State -> Lock.
Figure 11-44 Locking LM-80 OCH Port
Step 3 Click Lock LMOCHPTP.

Properties. The LM-80 OCH Port Properties window is displayed.

Figure 11-45 LM-80 OCH Port Properties

Step 6 Click the Modulation drop-down menu and select the appropriate modulation format
(QPSK = 40G Infinera wavelengths and BPSK = 20G Infinera wavelengths).
Note: For 40GbE and 100GbE signals (which are transported via separate channels), all of the
channels carrying the signal must be 10G channels, or channels that use the same modu-
lation format, either Binary Phase Shift Keying (BPSK) modulation or Quadrature Phase
Shift Keying (QPSK). If 40GbE or 100GbE signals are transported over channels with a mix
of 10G, BPSK, and QPSK, a Loss of Alignment (LOA) alarm is raised and service is
affected.
Step 7 Click the Tunable OCH Number drop-down menu and select the appropriate OCH number.
Step 8 Click the Tunable OCG Number drop-down menu and select the appropriate OCG number.
Step 9 Click the Apply OCH Number check-box (ensure that the box is checked).
Step 10 Click Apply.
Step 13 Repeat Step 1 through Step 12 for the remaining OCH port (if necessary).

Configuring CMM OCG and OCH Ports
the operating mode and to create an OCG association between the CMM and BMM, and an OCH
association between the LM-80 and CMM.
To verify and/or configure CMM OCG and OCH ports
Step 1 From the Equipment View, locate the appropriate CMM, right-click the OCG port and select
Figure 11-46 Locking CMM OCG Port
Step 3 Click Lock CMMOCGPTP.

Properties. The CMM OCG Port Properties window is displayed.

Figure 11-47 CMM OCG Port Properties

Select Gen1 when interconnecting the CMM to a Gen 1 BMM (BMM-4/BMM-8/BMM1H)
Select Gen2 when interconnecting the CMM to a Gen 2 BMM (BMM2/BMM2P/BMM2H)
Step 7 Click the Provisioned OCG Number drop-down menu and select the appropriate OCG number.
Step 8 Click Apply.
Step 9 Click Close.
Step 11 Repeat Step 1 through Step 10 for the remaining OCG port (if necessary).
Step 12 From the Equipment View, locate the appropriate CMM, right-click the OCH port and select
Figure 11-48 Locking CMM OCH Port
Step 14 Click Lock CMMOCHPTP.

Properties. The CMM OCH Port Properties window is displayed.
Figure 11-49 CMM OCH Port Properties

Step 17 Click the Provisioned OCH PTP drop-down menu and select the appropriate LM-80 OCH PTP
association.
Step 21 Repeat Step 12 through Step 20 for any remaining OCH ports (if necessary).


CMMs
Note: Unless specifically noted otherwise, all references to the CMM will refer to either the
CMM1D-20-CR and/or CMM1D-20-CB interchangeably.
Note: This procedure is only required if your system includes CMMs and BMMs.
Perform the following procedure to verify the OCG loss threshold between a CMM and BMM in the
DTC/MTC. Table 11-4 shows the supported OCG loss threshold between a CMM and BMM.
Table 11-4 Supported OCG Loss Threshold between a CMM and BMM
CMM Type BMM Type Optical Loss - Out of Range High Threshold
CMM1D-20-CR BMM 18.0dB (from CMM OCG to BMM OCG)

CMM1D-20-CB BMM1H (15.0dB attenuator pad + 3.0dB = 18.0dB)
NOTE: For Gen 1 BMMs, a 15.0dB attenuator pad
must be plugged into the BMM OCG IN port to
meet the power requirements for Auto-discovery.
BMM2 1.5dB (from CMM OCG to BMM OCG)
BMM2H
BMM2P

To verify OCG loss threshold between a CMM and BMM
Note: If the OCG loss threshold is exceeded, an Optical Loss - Out of Range High alarm will be
generated on the CMM OCG.
Step 1 Right-click the CMM for which you would like to verify the OCG loss threshold and select Optical
Carrier Group. The CMM OCG Port Properties window is displayed.
Step 2 In the list frame, select the appropriate CMM OCG.

(OPT).

(OPR).
CMM and BMM is within 18.0db or 1.5dB depending on the BMM type deployed:
18.0dB between CMM and Gen 1 BMM (BMM/BMM1H)
1.5dB between CMM and Gen 2 BMM (BMM2/BMM2H/BMM2P)
Loss threshold = CMM OCG OPT - BMM OCG OPR
Note: For Gen 1 BMMs, a 15.0dB attenuator pad must be plugged into the BMM OCG IN port to

Verifying Optical Channel (OCH) Loss Threshold for CMMs
Note: Unless specifically noted otherwise, all references to the “LM-80” will refer to the ADLM-80,
AXLM-80, and/or SLM-80 interchangeably.
Perform the following procedure to verify the OCH loss threshold between an LM-80 and CMM in the
DTC/MTC. Table 11-5 shows the supported OCH loss threshold between an LM-80 and CMM.
Table 11-5 Supported OCH Loss Threshold between an LM-80 and CMM
LM-80 Type CMM Type Optical Loss - Out of Range High Threshold
ADLM-80 CMM1D-20-CR 1.5dB (from LM-80 OCH to CMM OCH)

AXLM-80 CMM1D-20-CB
SLM-80

To verify OCH loss threshold between an LM-80 and CMM
Note: If the OCH loss threshold is exceeded, an Optical Loss - Out of Range High alarm will be
generated on the LM OCH.
Step 1 Right-click the LM-80 for which you would like to verify the OCH loss threshold and select Opti-
cal Channel Ports. The LM-80 OCH Port Properties window is displayed.
Step 2 In the list frame, select the appropriate LM OCH.

Step 3 Click the Real-Time PM tab and record the value listed for Och Optical Power Transmitted
(OPT).
Step 4 Right-click the CMM for which you would like to verify the OCH loss threshold and select Optical
Channel Ports. The CMM OCH Port Properties window is displayed.

Step 5 Click the Real-Time PM tab and record the value listed for Och Optical Power Received
(OPR).
LM-80 and CMM is within 1.5dB.
Loss threshold = LM OCH OPT - CMM OCH OPR
Step 7 Repeat Step 2 through Step 6 for each configured OCH in the system.

Configuring BMM Channels
Note: This procedure must be performed on each BMM at each end of the link. For BMM2/
BMM2P/BMM2H configurations, this procedure only needs to be performed on the base
BMM2/BMM2P/BMM2H at each end of the link. This procedure is not required on the
expansion BMM2/BMM2P/BMM2H. This procedure is also not required for BMM2/BMM2P/
BMM2Hs that will be configured to carry the maximum number of channels that the BMM2/
BMM2P/BMM2Hs are capable of carrying.
The number of configurable channels on a BMM ranges between 10 and 160 depending on the BMM type:
 40-channel full-height BMM and BMM1H—10, 20, or 40
 80-channel full-height BMM, BMM2-8-CXH2-MS, and BMM2H-4-R3-MS—10, 20, 40, 60, or 80
 BMM2-8-CH3-MS and BMM2P-8-CH1-MS—10, 20, 40, 60, 80, or 160
Perform the following procedure to enter the number of channels on a BMM in the DTC/MTC.
To configure the channels on a BMM
Step 1 From the Equipment View, highlight the appropriate BMM, right-click and select Admin State ->
Maintenance.
Step 2 Click Apply.
Step 3 From the Equipment View, highlight the appropriate BMM, right-click and select Properties. The
BMM Properties window is displayed. See Figure 11-54 on page 11-85.
Step 4 In the Summary panel click the Channels No. drop-down menu and select the number of chan-
nels.
Step 5 Click Apply to save changes.
Unlock.
Step 8 Repeat Step 1 through Step 7 for additional BMMs.

Figure 11-54 BMM Properties: Number of Channels
Number of Channels

Entering DCM/DSE Information
Note: Provisioning a DSE at mid-stage of a BMM/BMM2H/BMM2P is not supported. DSEs can

only be provisioned at mid-stage of a BMM2/OAM/ORM.
If a DTC/MTC includes a Dispersion Management Chassis (DMC), there may be multiple Dispersion
Compensation Module (DCM) ports. A DCM is optically connected to a BMM/BMM2/OAM/ORM mid-stage
access port (DCM) through a pair of front panel, duplex optical cables. DCMs can also be connected inline
(OTS), depending on customer configuration and fiber type deployed.
Release 10.0 supports the connection of a Dynamic Spectrum Equalizer (DSE) to a DCM port (DSEs are
physically installed in an OTC).
Perform the following procedure to enter the DCM/DSE information for a BMM/BMM2 in the DTC/MTC.
To enter DCM/DSE information
Step 1 From the Equipment View, highlight the appropriate BMM/BMM2, right-click and select Proper-
ties. The BMM Properties window is displayed.
Step 2 Click the Mid Stage Port tab.
For DCMs—from the Dispersion Compensation panel, click the DCM radio button and
select the appropriate DCM type from the DCM Type drop-down menu.
For DSEs—from the Dynamic Spectrum Equalizer panel, click the DSE radio button and
select the DSE from the DSE Module drop-down menu.
Figure 11-55 BMM Properties: Mid Stage Port

Step 5 Repeat Step 1 through Step 4 for remaining BMM/BMM2s that have a DCM/DSE.

Perform the following procedure to provision the fiber information for each BMM in the DTC/MTC.
Step 1 From the Equipment View, highlight the appropriate BMM to be configured, right-click and select
Admin State -> Maintenance.
Step 2 Click Apply.
Step 3 Right-click the BMM and select Span. The Span Properties window is displayed. From the tabs
listed in the middle of the window, select the Span/C-Band tab.
Step 4b Enter the Line Out Pad (attenuator) value (line out = BMM Tx port).
Step 4c Enter the Line In Pad (attenuator) value (line in = BMM Rx port).
type.
Step 4e Click the Inline DCM Type drop-down menu and select the appropriate DCM, DSE,
or PSE type.
Step 4f Enter the Rx Eqpt List information (optional). For example, BPF (or any extra DCMs
that might be deployed).
Step 4g Enter the Tx Eqpt List information (optional). For example, BPF (or any extra DCMs

Span/C-Band
tab
Fiber panel
Step 6 Click Close to exit the Span Properties window.
Unlock.
Step 8 Repeat Step 1 through Step 7 for all remaining BMMs.

Entering Span Loss between Adjacent Nodes
Perform the following procedure to enter the expected span loss for each BMM in the DTC/MTC.
To enter Span Loss
Step 1 Right-click the BMM and select Span. The Span Properties window displays. From the panels
listed in the middle of the window, select the Span/C-Band panel.
Step 2 Under Span Loss Threshold, enter the Expected Span Loss information in the Expected (ESL)
field.

Perform the following procedure to provision the primary and secondary GNE IP address in the DTC/MTC.
Step 6 Click Apply.

Summary panel
IP Gateway Proxy
GNE tab
Primary and
Secondary GNE
IP Addresses

Perform the following procedure to create a cross-connect in the DTC/MTC.
Note: The following procedure provides an example of the creation of an Unprotected, OC-192/
10GbE WAN, Express cross-connect type. For detailed information regarding the creation
of other supported cross-connect types, refer to the Infinera GNM Service Provisioning
Guide.

From the Equipment View right-click a line module/LM-80, TEM, TAM, and/or TOM and select
Provisioning -> Cross-connect Manager. The Cross-connect Manager is displayed in the
Workspace Area. Click New
From the Equipment View right-click a line module/LM-80, TEM, TAM, and/or TOM and select
Provisioning -> Create Cross-connect

Service type
Service rate
(payload type)
Connectivity type
Note: 2-port DSNCPs are not supported on the video TOMs (TOM-1.485HD-RX,
TOM-1.4835HD-RX, TOM-1.485HD-TX, and/or TOM-1.4835HD-TX).
(for example, select OC-192/10GbE WAN).
Note: When the Create Cross-connect wizard is launched from a line module, the default service
rate is 10G and the default Connectivity is Express. Only in cases where the Create Cross-
connect wizard is launched from a TAM or a TOM the default Connectivity is Add/Drop.
Note: OC-768, STM-256, 40G, 4XOC192, and 4XSTM64 are applicable only to 40G TAM.

Note: When provisioning 40G trib-to-trib connections through an intermediate node (with back-to-
back 10G TOMs installed), ensure that you provision four individual 10G Clear Channel
cross-connects as there is no option to create a single 4x10G Clear Channel cross-con-
nect. Also note that for this type of configuration, the 4XOC192 payload type is not valid.
Note: When provisioning a 1GbE circuit or cross-connect, ensure that the following parameters on
the customer equipment (router or switch connected to the TAM-8-1G or
TAM-8-2.5GM) are set as follows:
Auto-negotiation set to "on"
or
Auto-negotiation set to "off", static configuration of the customer equipment Ethernet
port capabilities set to "full-duplex," and the data rate set to "1GbE."
Note: The default payload type is 1GbE for 8x1GbE TAMs, OC-48 for 2.5G TAMs, OC-192/10GbE
for 10G TAMs, and OC-768 for 40G TAMs.
Note: Video TOMs are uni-directional TOMs that either receive a signal or transmit a signal, and
therefore must be configured correctly for either add cross-connects (for TOM-1.485HD-RX
and TOM-1.4835HD-RX), or for drop cross-connects (TOM-1.485HD-TX and TOM-
1.4835HD-TX). The DTC/MTC does not block incorrect cross-connect provisioning, such
as incorrectly provisioning an add cross-connect on a transmit TOM, but traffic will not
come up on incorrect cross-connect provisioning on electrical TOMs. When bidirectional
(add/drop) cross-connects are provisioned on the uni-directional video TOMs, traffic will
come up, but this is not a recommended configuration.

Circuit ID (CID)
Label
Source Endpoint
Intermediate LM
Destination
Endpoint



Source Endpoint—the source endpoint of the cross-connect. Click the [...] button to view
a list of the valid termination points displayed as AIDs. The Endpoint Source window is dis-
played along with a list of multipoint cross-connects. Select the source endpoint and click Ok
click Ok
Step 9 Click Ok.



CAUTION
Transmitted (OPT) values for all trib ports in the DTC/MTC.


Installing the Standby MCM
Note: Unless specifically noted otherwise, all references to the MCM will refer to either the
MCM-B and/or MCM-C interchangeably.
Note: The MCM-C does not support the following DTC fan tray PON type: D-FANTRAY-A.
Perform the following procedure to install the standby MCM in the DTC/MTC.
To install the standby MCM
Step 1 Install the standby MCM.

The MCM takes some time to complete the boot up process. When it is complete, look at the
MCM and verify that the PWR LED is lit and Green and the ACT LED is lit and Yellow.
In the Management Card Properties window, ensure the MCM Redundancy Status of the
MCMs are Active and Standby
The ACT LED on the standby MCM is Yellow.

Verifying Inventory
to equipment, facilities, and tools used to control and monitor the DTC/MTC. The Infinera GNM Main View
also includes a graphical representation of the DTC/MTC being managed.
To verify equipment

Page 11-102 Testing DTC/MTC Circuit Packs
Testing DTC/MTC Circuit Packs

DTC/MTC:
“Testing TAMs” on page 11-103
“Testing DICMs” on page 11-103
“Testing GAMs” on page 11-104

“Testing BMMs” on page 11-104
“Testing CMMs” on page 11-105
“Testing Line Module/LM-80/TEMs” on page 11-105
“Testing MCMs” on page 11-106
Testing TOMs
Step 1 Examine the LEDs on each TOM on the DTC/MTC. The FLT is illuminated if an alarm exists. If a
TOM has an alarm, view the Alarm Manager to verify the type of alarm.
Step 3 The circuit pack is operational if no equipment alarms are present. To verify the operational state,
right-click the TOM from the Equipment View.

Testing TAMs
Note: The following procedure applies to all TAM types.
Perform the following procedure to test a TAM.
To test a TAM with an equipment failure alarm
Step 1 Examine the LEDs on each TAM on the DTC/MTC. The FLT LED is illuminated if an alarm
exists. If a TAM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the TAM from the Equipment View.
Step 4 Select Properties. The TAM Properties window is displayed.
Testing DICMs
Note: The following procedure applies to all DICM types.
Perform the following procedure to test a DICM.
To test a DICM with an equipment failure alarm
DICM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the DICM from the Equipment View.
Step 4 Select Properties. The DICM Properties window is displayed.

Testing GAMs
Note: The following procedure applies to all GAM types.
Perform the following procedure to test a GAM.
To test a GAM with an equipment failure alarm
Step 1 Examine the LEDs on each GAM on the DTC/MTC. The FLT LED is illuminated if an alarm
exists. If a GAM has an alarm, view the Alarm Manager to verify the type of alarm.
right-click the GAM from the Equipment View.
Step 4 Select Properties. The GAM Properties window is displayed.
Testing BMMs
Note: The following procedure applies to all BMM types.
Perform the following procedure to test a BMM.
To test a BMM with an equipment failure alarm
Step 1 Examine the LEDs on each BMM on the DTC/MTC. The FLT LED is illuminated if an alarm
exists. If a BMM has an alarm, view the Alarm Manager to verify the type of alarm.
right-click the BMM from the Equipment View.
Step 4 Select Properties. The BMM Properties window is displayed.

Testing CMMs
Note: The following procedure applies to all CMM types.
Perform the following procedure to test a CMM.
To test a CMM with an equipment failure alarm
Step 1 Examine the LEDs on each CMM on the DTC/MTC. The FLT LED is illuminated if an alarm
exists. If a CMM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the CMM from the Equipment View.
Step 4 Select Properties. The CMM Properties window is displayed.
Testing Line Module/LM-80/TEMs
Note: A line module/LM-80 differs from a TAM Extender Module (TEM) due to the fact that the
TEM does not have a line side facility so it is not capable of creating an OCG. All TEM cir-
cuits and cross-connects are routed through the backplane to a line module/LM-80.
Perform the following procedure to test a line module/LM-80/TEM.
To test a line module/LM-80/TEM with an equipment failure alarm
Step 1 Examine the LEDs on each line module/LM-80/TEM on the DTC/MTC. The FLT LED is illumi-
nated if an alarm exists. If a line module/LM-80/TEM has an alarm, view the Alarm Manager to
verify the type of alarm.

right-click the line module/LM-80/TEM from the Equipment View.
Step 4 Select Properties. The DLM/XLM/TEM/ADLM/AXLM/SLM Properties window is displayed.
Testing MCMs
Note: An MCM equipment failure alarm is reported only for standby MCMs. If an equipment failure
alarm occurs on the active MCM, the DTC/MTC will not be accessible through any of the
management interfaces.
Note: The following procedure applies to all MCM types.
Perform the following procedure to test an MCM.
To test an MCM with an equipment failure alarm
Step 1 Examine the LEDs on each MCM on the DTC/MTC. The FLT LED is illuminated if an alarm
exists. If an MCM has an alarm, view the Alarm Manager to verify the type of alarm.
right-click the MCM from the Equipment View.
Step 4 Select Properties. The MCM Properties window is displayed.


the DTC/MTC.

Alarm Filter panel

expected alarms for the DTC/MTC.
Alarm Severity
to customers.
cautions.

Table 11-7 lists expected alarms that may occur upon turning up a DTC/MTC.
Table 11-7 Expected DTC/MTC Alarms
Alarm Type Cause
Optical Loss of Signal 1. No fibers are connected.

(OLOS) (BMM to BMM 2. Fibers are connected but they do not
connection) have light because of Automatic Laser
Shutdown (ALS).
Optical Loss of Signal- Optical Carrier Group not present or sig-
Payload (line module- nal not received in the Optical Carrier
BMM connection) Group.
(OLOS)(Tributary Optical 2. Fibers are connected but they do not
Module side) have light.
NCT1 Loss of Enet Link Expansion Chassis not present or con-
from Controller B (NCT nectivity with expansion chassis failed.
port not connected)

Environmental alarms are those triggered by an abnormal condition at the DTC/MTC site. The DTC/MTCs
temperature detector, door open and so on to the DTC/MTC. When the connected equipment triggers an
input contact point, it raises an alarm with an alarm message and severity as configured by the user. Alarm
output contacts allow users to connect external equipment to the DTC/MTC.
The DTC/MTC can trigger the operation of the connected external equipment. The maximum threshold is
Configuring Alarm Input Contacts

The DTC/MTCs support sixteen user-configurable alarm input contacts. Users can configure these input
contacts and when activated, generate a customized alarm.

See Table 11-8 for the DTC alarm input contact pin assignments and Table 11-9 on page 11-111 for the
MTC alarm input contact pin assignments.
Table 11-8 DTC Alarm Input Contact Pin Assignments
Row Column
1 A Alarm Input Contact 1 User defined
1 B Alarm Input Contact 1 User defined
1 C Alarm Input Contact 5 User defined
1 D Alarm Input Contact 5 User defined
1 E Alarm Input Contact 9 User defined
1 F Alarm Input Contact 9 User defined
1 G Alarm Input Contact 13 User defined
1 H Alarm Input Contact 13 User defined
1 I Reserved for Critical Bay alarm Predefined
1 J Reserved for Critical Bay alarm Predefined
2 I Reserved for Major Bay alarm Predefined
2 J Reserved for Major Bay alarm Predefined
3 I Reserved for Minor Bay alarm Predefined
3 J Reserved for Minor Bay alarm Predefined


4 I Reserved for Alarm Cut-Off (ACO)a Predefined
4 J Reserved for Alarm Cut-Off (ACO)a Predefined
a. In addition to the ACO push button and the Infinera GNM interface, you can enable ACO using the input contact pins.
Table 11-9 MTC Alarm Input Contact Pin Assignments
Row Column
2 G Reserved for Critical Bay alarm Predefined
2 H Reserved for Critical Bay alarm Predefined


3 G Reserved for Major Bay alarm Predefined
3 H Reserved for Major Bay alarm Predefined
4 G Reserved for Minor Bay alarm Predefined
4 H Reserved for Minor Bay alarm Predefined
5 G Reserved for Alarm Cut-Off (ACO) a Predefined
5 H Reserved for Alarm Cut-Off (ACO)a Predefined

Configuring Alarm Output Contacts

The DTC/MTCs support ten user-configurable alarm output contacts. Each output has NO (normally
open), NC (normally closed) and CM (common) contacts. Under normal conditions, the NO output is open
and the NC output is closed. When the output contact is enabled, the NO output is closed and the NC
output is opened. Users can enable or disable (normal condition) the output contacts either manually or
automatically on occurrence of user-defined alarm condition.

See Table 11-10 for the DTC alarm output contact pin assignments and Table 11-11 on page 11-118 for the
MTC alarm output contact pin assignments.
Table 11-10 DTC Alarm Output Contact Pin Assignments
Row Column
1 K Alarm Output Contact 1, User defined
RETURN
1 L Alarm Output Contact 1, User defined
NORMALLY OPEN
1 M Alarm Output Contact 1, User defined
NORMALLY CLOSED
1 N Alarm Output Contact 5, User defined
RETURN
1 O Alarm Output Contact 5, User defined
NORMALLY OPEN
1 P Alarm Output Contact 5, User defined
NORMALLY CLOSED
1 Q Alarm Output Contact 9, User defined
RETURN
1 R Alarm Output Contact 9, User defined
NORMALLY OPEN
1 S Alarm Output Contact 9, User defined
NORMALLY CLOSED
1 T Minor Audio Alarm, Predefined
RETURN
1 U Minor Audio Alarm, Predefined
NORMALLY OPEN
1 V Minor Audio Alarm, Predefined
NORMALLY CLOSED
1 W Power Fault Alarm, Predefined
RETURN
1 X Power Fault Alarm, Predefined
NORMALLY OPENa
1 Y Power Fault Alarm, Predefined
NORMALLY CLOSEDa
RETURN


NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
2 T Critical Visual Alarm, Predefined
RETURN
2 U Critical Visual Alarm, Predefined
NORMALLY OPEN
2 V Critical Visual Alarm, Predefined
NORMALLY CLOSED
2 W Critical Bay Alarm, Predefined
RETURN
2 X Critical Bay Alarm, Predefined
NORMALLY OPEN
2 Y Critical Bay Alarm, Predefined
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED


RETURN
NORMALLY OPEN
NORMALLY CLOSED
3 Q Critical Audio Alarm, Predefined
RETURN
3 R Critical Audio Alarm, Predefined
NORMALLY OPEN
3 S Critical Audio Alarm, Predefined
NORMALLY CLOSED
3 T Major Visual Alarm, Predefined
RETURN
3 U Major Visual Alarm, Predefined
NORMALLY OPEN
3 V Major Visual Alarm, Predefined
NORMALLY CLOSED
3 W Major Bay Alarm, Predefined
RETURN
3 X Major Bay Alarm, Predefined
NORMALLY OPEN
3 Y Major Bay Alarm, Predefined
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN


NORMALLY CLOSED
4 Q Major Audio Alarm, Predefined
RETURN
4 R Major Audio Alarm, Predefined
NORMALLY OPEN
4 S Major Audio Alarm, Predefined
NORMALLY CLOSED
4 T Minor Visual Alarm, Predefined
RETURN
4 U Minor Visual Alarm, Predefined
NORMALLY OPEN
4 V Minor Visual Alarm, Predefined
NORMALLY CLOSED
4 W Minor Bay Alarm, Predefined
RETURN
4 X Minor Bay Alarm, Predefined
NORMALLY OPEN
4 Y Minor Bay Alarm, Predefined
NORMALLY CLOSED
a. When there is no power fault condition, the Normally Open contact is closed and the Normally Closed contact is open.
When both PEM A and PEM B have power fault condition, the Normally Open contact is open and Normally Closed con-
tact is closed. The power fault is defined as when the power input into PEM A or PEM B is out of working range.

Table 11-11 MTC Alarm Output Contact Pin Assignments
Row Column
1 I Alarm Output Contact 1, User defined
RETURN
1 J Alarm Output Contact 1, User defined
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
1 O Critical Audio Alarm, Predefined
RETURN
1 P Critical Audio Alarm, Predefined
NORMALLY OPEN
NORMALLY CLOSED
1 R Minor Visual Alarm, Predefined
RETURN
1 S Minor Visual Alarm, Predefined
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN


NORMALLY OPEN
NORMALLY CLOSED
2 O Major Audio Alarm, Predefined
RETURN
2 P Major Audio Alarm, Predefined
NORMALLY OPEN
NORMALLY CLOSED
2 R Power Fault Alarm, Predefined
RETURN
2 S Power Fault Alarm, Predefined
NORMALLY OPENa
2 T Power Fault Alarm, Predefined
NORMALLY CLOSEDa
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
3 O Minor Audio Alarm, Predefined
RETURN
3 P Minor Audio Alarm, Predefined
NORMALLY OPEN
3 Q Minor Audio Alarm, Predefined
NORMALLY CLOSED

3 R Critical Bay Alarm, Predefined

RETURN
3 S Critical Bay Alarm, Predefined
NORMALLY OPEN
3 T Critical Bay Alarm, Predefined
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
4 O Critical Visual Alarm, Predefined
RETURN
4 P Critical Visual Alarm, Predefined
NORMALLY OPEN
4 Q Critical Visual Alarm, Predefined
NORMALLY CLOSED
4 R Major Bay Alarm, Predefined
RETURN
4 S Major Bay Alarm, Predefined
NORMALLY OPEN
4 T Major Bay Alarm, Predefined
NORMALLY CLOSED
RETURN
NORMALLY OPEN


NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
5 O Major Visual Alarm, Predefined
RETURN
5 P Major Visual Alarm, Predefined
NORMALLY OPEN
5 Q Major Visual Alarm, Predefined
NORMALLY CLOSED
5 R Minor Bay Alarm, Predefined
RETURN
5 S Minor Bay Alarm, Predefined
NORMALLY OPEN
5 T Minor Bay Alarm, Predefined
NORMALLY CLOSED

Alarm Cutoff (ACO)

The DTC/MTC system provides a feature to acknowledge an alarm condition and turn off the audible

To enable an ACO
tons).
Testing an ACO
to be audible.
To test an ACO


node configuration.
Perform the following procedure to configure datawire services on the DTC/MTC. The port used for the
Note: Infinera GNM may be launched from the Ethernet craft port of an MCM installed in an
Expansion Chassis.


procedure.

CHAPTER 12
Turning up a DTN as an SNE
This chapter provides the procedures to turn up and test a DTN as a Subtending Network Element (SNE).
“DTN Main Chassis Turn-up” on page 12-2

DTN Main Chassis Turn-up

The DTN consists of at least one Digital Transport Chassis (DTC) or MTC, and zero or more Dispersion
Management Chassis (DMC).
The DTC-A is generally no longer available but is still supported; all DTNs currently shipping contain either
the DTC-B or MTC chassis types. The DTC-B is fully backward compatible with the DTC-A and uses all of
the existing hardware currently deployed in the DTC-A.

Turning up a DTN as an SNE Page 12-3


Tasks

12-7
12-10
12-13
12-16
MTC Main Chassis Subtending Net- 12-17
work Element (SNE)“
“Verifying MCM Craft Ethernet Port IP page
12-25
12-29
Channel“ 12-40
Channel“ 12-42
OCG Fibers“ 12-43


Completion“ 12-45
12-46
(OCG) Loss Threshold“ 12-48
12-69
Ports“ 12-71
12-80
12-82
12-83
cent Nodes“ 12-85
12-88
Port“ 12-95
12-96
12-97


Before performing the turn-up and test procedures on a DTC/MTC, a serial connection between the
network element and the craft computer (referred to as GNM terminal) must be established. Serial
connectivity requires an RS-232 serial cable with a DB-9 male connector at one end and a USB connector
at the other end.
MCM.

COM1).
Note: This window should be kept open until the initial commissioning of the DTC/MTC is com-
plete.


Infinera GNM interface. The DTC/MTC provides a craft Ethernet port on the MCM. The following
procedure describes how to connect an Ethernet cable to the MCM. Ethernet connectivity requires either a
straight-through or a crossover CAT5 Ethernet cable (Figure 12-6) with RJ-45 connectors at both ends.
Older GNM terminals may require a crossover CAT5 Ethernet cable.
used to access the Infinera GNM from the MCM is 192.168.0.1. The default subnet mask that is used to
access the Infinera GNM from the MCM is 255.255.255.0.

Step 2 Connect the Ethernet cable to the connector labeled Craft on the active MCM.
Note: If there is a redundant MCM, it should not be installed in the slot at this time.
DTC/MTC.
suggested.



address should be in the same subnet as the IP address configured for the target MCM or the
DTC/MTC. The last octet must vary between 2 and 255.
Note: The default IP address of the MCM is: 192.168.0.1.

Step 8 Click OK.
Step 9 Click Close.

CAUTION
CAUTION
WARNING
WARNING

WARNING
and correction.
WARNING
and correction.

POWER POWER
INPUT FAULT
Terminal studs
RTN

ON OFF
70A
POWER A infn_062a

CAUTION
The following section provides the procedure to power up the DTC/MTC.
Initial Start-up
OFF
either PEM)
After you have verified that power is present on both PEMs and no faults exist, you are ready to initially
configure the DTC/MTC.

Initial Commissioning for the DTC/MTC Main Chassis

Note: Ensure that only one MCM is installed in either slots 7A or 7B and any modules occupying
slots 3, 4, 5, and/or 6 are not seated.
GNM terminal.
configure the DTC/MTC. You must have the site specific commissioning data at hand (listed in
“Commissioning Data” on page 2-12 and previously recorded in Table 2-1 on page 2-2).
The procedures to commission a DTC/MTC vary depending on whether the MCM was commissioned
previously or not.
 If the MCM was not commissioned previously, see “To initially commission the Main Chassis of an
SNE if the MCM was not commissioned previously” on page 12-18
 If the MCM was commissioned previously, see “To initially commission the Main Chassis of an SNE
if the MCM was commissioned previously” on page 12-20.
See “XCM/IMM/MCM/OMM Rebranding Flow” on page B-1 for a graphical representation of the MCM
branding procedure.

To initially commission the Main Chassis of an SNE if the MCM was not commissioned previously
If the MCM was not commissioned previously, the following message is displayed in the HyperTerminal
session:
then press Enter.




ure and repeat the steps in case a mistake was made, or B to reboot the MCM and discard the
changes.
NE Name? Node1
Router ID? 11.10.2.22
Shelf ID[1-63]? 1
N)[N]?
The MCM will reboot and the following message is displayed:
Main Chassis : yes
NE Name : Node1
Router ID : 11.10.2.22
Shelf ID : 1
chassis_check: (127_1_3_1) (127_1_3_2) (127_2_3_1) (127_2_3_2).
boot up process may cause the MCM to hang and not boot up correctly. Ensure the boot

The MCM can take some time to complete the boot up process. When the PWR, NC, and ACT LEDs are
all lit solid Green the MCM has completed booting up. This indicates the MCM is operational (and safe to
This completes the initial commissioning of the MCM.
To initially commission the Main Chassis of an SNE if the MCM was commissioned previously
If the MCM was commissioned previously, the following message is displayed in the HyperTerminal
session:
Main Chassis : yes
NE Name : Node_2
Router ID : 11.10.2.23
Dcn IP : 10.10.2.20
Shelf ID : 1
then press Enter.


system time.

Router ID(11.10.2.23) ? 11.10.2.22
!!!!!!!!!!!!!!!!!!!!!!!!!!
N)[N]?


(1132135975) Thu Mar 13 10:12:55 2014
Type yes to re-brand the MCM.
If the MCM did not have a database stored on it, the following message is displayed:

Go to Step 13
If the MCM had a database stored on it, the following message is displayed:

Go to Step 14
serial cable.
up process. When the PWR, NC, and ACT LEDs are all lit solid Green the MCM has completed booting up.
This indicates the MCM is operational.
Type yes to re-brand the MCM. The following message is displayed:

no]?

serial cable.
Type no if you do not want to re-brand the MCM. The following message is displayed:

serial cable.
up. This indicates the MCM is operational (and safe to remove the serial cable).

Verifying MCM Craft Ethernet Port IP Connectivity

To verify MCM craft Ethernet port IP connectivity, first ping the MCM IP address, and then test the network
element connection. If the GNM terminal will be used to verify the MCM craft Ethernet port IP connectivity:
 Ensure that an Ethernet cable is connected from the GNM terminal to the correct MCM craft Ether-
net port on the DTC/MTC. If the MCM is located in Slot 7A, use MCM craft Ethernet port A. If the
MCM is located in Slot 7B, use MCM craft Ethernet port B
minal IP address.
To ping the MCM craft Ethernet port IP address

ping [MCM Craft Ethernet Port IP Address]


To test the MCM craft Ethernet port IP connection of the target DTC/MTC

Step 2 Enter the MCM craft Ethernet port IP address of the target DTC/MTC in the web address (URL)
field. If the connection is established, a login window is displayed. This verifies MCM craft Ether-
net port IP connectivity to the network element.

Note: Infinera GNM may be launched from the Ethernet craft port of an MCM using the craft
sage is displayed.

Step 2 In the browser, enter the MCM Craft Ethernet Port IP address of the target DTC/MTC. Infinera
GNM is launched in a new window and the Login window is displayed.





It is important to know what version of software is on the Active MCM in the DTC/MTC. The software
version should be recorded in Table 12-1 on page 12-5. The software release version is of the format
X.Y.Z where X is the major version number, Y is the minor version number, and Z is the maintenance
version number.

 From the Equipment View, select the Active MCM. The Quick View Browser panel in the lower left
corner displays the MCM software version number as shown in Figure 12-14
Software
Version



displayed.


Step 6 Click OK.



Step 11 Click OK.
face.

mode.
mode.

Step 4 Click Apply.
Step 5 Click Close.


Switching
Mode

and/or 2.
Step 2 Click Apply.
page 12-36.
BMM2/BMM2P/BMM2H.
and select

Expansion BMM

Expansion BMM
(grayed out)

Each DTC/MTC may contain up to two (2) Band Multiplexing Modules (BMMs). Ensure that the appropriate
BMMs are installed in slots 1 and/or 2 of the DTC/MTC prior to performing this procedure. It is
Step 2 Connect line fibers from the OUT (transmit) line port on BMM slot 2 (Node B) to the IN (receive)
line port on BMM slot 1 (Node A) for eastbound traffic. Ensure there is appropriate attenuation

Gen 1 Gen 2 Gen 2

0 1.5 -1.5

10 to 40 -3.0 3 5 2
41 to 80 -3.0 3 5 2
81 to 160 -6.0 N/A N/A 5


Note: To enable the OSC connectivity, this configuration must be performed on each BMM at
DTC/MTC.

networks.



(BMMs).

67


Expansion BMMs
BMM2H.
on page C-88
on page C-88
on page C-89

Figure 12-24 Line Module Auto-discovery Completion
General tab
Connected BMM port

Tx Auto Discovery
State
Step 4 Click Close.



Step 9 Click Close.
Unlock.

Tunable tab
Operating Mode
Provisioned OCG
Number

Verifying Optical Carrier Group (OCG) Loss Threshold
page 12-52
page 12-56
on page 12-58
2)” on page 12-64


BMM OCG)
GAM Trib OCG)
BMM OCG)
BMM OCG)
BMM OCG)


(OPR).

(OPT).


(OPR).


(OPT).
(OPR).

(OPT).



(OPR).

(OPT).


(OPR).

(OPT).

GAM-1)
BMM2H via a GAM-1:

(OPR).

(OPT).
(OPR).

(OPT).


a GAM-2:

(OPR).


(OPT).
(OPR).

(OPT).



Fibers
page C-80




affected.




Step 8 Click Apply.
Step 9 Click Close.


association.


CMMs

BMM2H
BMM2P


(OPT).

(OPR).


AXLM-80 CMM1D-20-CB
SLM-80


(OPT).

(OPR).

Maintenance.
Step 2 Click Apply.
nels.
Unlock.

Number of Channels




Step 2 Click Apply.
type.
or PSE type.

Span/C-Band
tab
Fiber panel
Unlock.

To enter Span Loss
field.

Perform the following procedure to provision the primary and secondary GNE IP address in the DTC/MTC.
Step 6 Click Apply.

Summary panel
IP Gateway Proxy
GNE tab
Primary and
Secondary GNE
IP Addresses

Guide.


Service type
Service rate
(payload type)
Connectivity type
(for example, select OC-192/10GbE WAN).

or
Note: The default payload type is 1GbE for 8x1GbE TAMs, OC-48 for 2.5G TAMs, OC-192/
10GbE for 10G TAMs, and OC-768 for 40G TAMs.

Circuit ID (CID)
Label
Source Endpoint
Intermediate LM
Destination
Endpoint



Ok
click Ok
Step 9 Click Ok.



CAUTION
account team and/or an Infinera Technical Assistance Center (TAC) resource to obtain
information regarding Infinera approved attenuator pads. Refer to the TOM section of the
Infinera DTN and DTN-X Hardware Description Guide for details regarding specific TOM
optical specifications.




Verifying Inventory
to equipment, facilities, and tools used to control and monitor the DTC/MTC. The Infinera GNM Main View
also includes a graphical representation of the DTC/MTC being managed.
To verify equipment


DTC/MTC:

Testing TOMs

Testing TAMs
Testing DICMs

Testing GAMs
state, right-click the GAM from the Equipment View.
Testing BMMs
state, right-click the BMM from the Equipment View.

Testing CMMs

state, right-click the line module/LM-80/TEM from the Equipment View.
Testing MCMs
state, right-click the MCM from the Equipment View.


the DTC/MTC.

Alarm Filter panel
Hide the Filter panel Alarm table

Alarm Severity
to customers.
cautions.

Alarm Type Cause

Shutdown (ALS).
port not connected)



Row Column


Row Column





See Table 12-10 for the DTC alarm output contact pin assignments and Table 12-11 on page 12-114 for
the MTC alarm output contact pin assignments.
Row Column
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPENa
NORMALLY CLOSEDa
RETURN


NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED


RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN


NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED

Row Column
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN


NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPENa
NORMALLY CLOSEDa
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED


RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN


NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED

Alarm Cutoff (ACO)


To enable an ACO
tons).
Testing an ACO
to be audible.
To test an ACO

node configuration.
Perform the following procedure to configure datawire services on the DTC/MTC. The port used for the
Expansion Chassis.

procedure.


CHAPTER 13
Turning up a DTC/MTC as an
Expansion Chassis
This chapter provides the procedures to turn up and test a DTC/MTC as an Expansion Chassis and is
“DTC/MTC Expansion Chassis Turn-up” on page 13-2
“Configuring DTNs for Preamplifier Configuration” on page 13-93

Page 13-2 DTC/MTC Expansion Chassis Turn-up
DTC/MTC Expansion Chassis Turn-up

Note: In multi-chassis nodes, each DTC/MTC can be configured independently for Ring or Mesh
switching mode. The chassis in a multi-chassis node do not all have to be configured to the
same backplane switching mode.
The DTC-A is generally no longer available but is still supported; all DTC/MTCs currently shipping contain
either the DTC-B or MTC chassis types. The DTC-B is fully backward compatible with the DTC-A and uses
all of the existing hardware currently deployed in the DTC-A.

Turning up a DTC/MTC as an Expansion Chassis Page 13-3


Tasks
Table 13-1 DTC/MTC Expansion Chassis Turn-up Checklist and Test Results
“Installing DTC/MTC Multi-chassis page

NCT Ethernet Cables“ 13-7
13-16
13-19
13-20
13-24
MTC Expansion Chassis“ 13-26
Channel“ 13-37
Channel“ 13-40
OCG Fibers“ 13-41
Completion“ 13-43
13-44
(OCG) Loss Threshold“ 13-46

Table 13-1 DTC/MTC Expansion Chassis Turn-up Checklist and Test Results

13-67
Ports“ 13-69
13-78
13-80
13-81
cent Nodes“ 13-83
13-84
Port“ 13-91
13-92

Installing DTC/MTC Multi-chassis NCT Ethernet Cables

In a multi-chassis configuration, chassis are interconnected at the nodal control and timing (NCT) ports of
the I/O panels using straight-through unshielded twisted pair CAT5 Ethernet cables that conform to
allowed for each NCT cable segment between chassis is 328 feet (100 meters). A third-party Ethernet
media converter can be used for connecting NCT ports to support extended distances. Contact your
Infinera account team for assistance with third-party Ethernet media converters.
Ensure that straight-through (not crossover) CAT5 Ethernet cables are used for all NCT
Expansion Chassis may be pre-provisioned. The physical connection of NCT cables may be made prior to
Release 10.0 certifies the following multi-chassis configurations:
A DTN can support up to 44 interconnected chassis (up to 32 DTC/MTCs and up to 12 OTCs) if the
Main Chassis includes an MCM-C as the node controller (although a maximum of 44 chassis are
supported in a DTN, the DTN supports a chassis ID range of 1-63). The Main Chassis must be a
DTC or an MTC. The DTN can be configured with up to 8 BMMs, up to 96 line module/TEMs (with
optional control module redundancy on any chassis). Each OTC Expansion Chassis can house up
to 2 Raman modules or 2 DSEs (with optional control module redundancy on any chassis). Addition-
ally, the OTC Expansion Chassis can house OAM/ORMs when these modules are connected to
BMM2Ps
A DTN can support up to 17 interconnected chassis (DTC/MTC/OTCs) if the Main Chassis includes
an MCM-B as the node controller. The Main Chassis must be a DTC or an MTC; the 16 Expansion
Chassis can be any combination of DTC/MTC/OTCs. The DTN can be configured with up to 8
BMMs, up to 32 line module/TEMs (with optional control module redundancy on any chassis). Each
OTC Expansion Chassis can house up to 2 Raman modules or 2 DSEs (with optional control mod-
ule redundancy on any chassis). Additionally, the OTC Expansion Chassis can house OAM/ORMs
when these modules are connected to BMM2Ps

Refer to “Installing OTC Multi-chassis NCT Ethernet Cables” on page 16-4 for OTC multi-chassis
configurations consisting of OTCs. This section is organized as follows:
 Cabling dual-chassis for fully redundant MCMs (see “To connect NCT cables for dual-chassis with
full MCM redundancy” on page 13-8)
 Cabling dual-chassis for MCM redundancy only on the Main Chassis (see “To connect NCT cables
for dual-chassis with MCM redundancy only on Main Chassis” on page 13-10)
 Cabling dual-chassis for non-redundant MCMs (see “To connect NCT cables for dual-chassis non-
redundant MCMs” on page 13-11)
 Cabling multi-chass for fully redundant MCMs (see “To connect NCT cables for multi-chassis with
full MCM redundancy” on page 13-12)
 Cabling multi-chassis for MCM redundancy only on the Main Chassis (see “To connect NCT cables
for multi-chassis with MCM redundancy only on Main Chassis” on page 13-14)
plane availability.
Dual-chassis Configuration NCT Cabling
To connect NCT cables for dual-chassis with full MCM redundancy
In the procedure below, the following convention is used to specify NCT ports on a particular chassis:
[ChassisID]-NCT-[PortNumber][A|B]
For example, NCT port 1A on chassis 1 is specified as 1-NCT-1A.
Step 1 Connect 1-NCT-1A to 2-NCT-1B.
Step 2 Connect 1-NCT-1B to 2-NCT-2B.
Step 3 Connect 1-NCT-2A to 2-NCT-2A.
Step 4 Connect 1-NCT-2B to 2-NCT-1A.

Figure 13-3 NCT Connectivity for Dual-chassis with Full MCM Redundancy
DTC/MTC
I/O Panel
Chassis 1
MCM MCM
in 7A CPU in 7B CPU
Switch/ Switch/
Router Router
DTC/MTC
I/O Panel
Chassis 2
MCM MCM
in 7A CPU in 7B CPU
Switch/ Switch/
NCT Cable Router Router
Connection infn_113

To connect NCT cables for dual-chassis with MCM redundancy only on Main Chassis
Figure 13-4 NCT Connectivity for Dual-chassis with MCM Redundancy only on Main Chassis
DTC/MTC
I/O Panel
Chassis 1
MCM MCM
in 7A CPU in 7B CPU
Switch/ Switch/
Router Router
DTC/MTC
I/O Panel
Chassis 2
MCM
in 7A CPU
Switch/
NCT Cable Router
Connection
infn_115

To connect NCT cables for dual-chassis non-redundant MCMs
Figure 13-5 NCT Connectivity for Dual-chassis Non-redundant MCMs
DTC/MTC
I/O Panel
Chassis 1
MCM
in 7A CPU
Switch/
Router
DTC/MTC
I/O Panel
Chassis 2
MCM
in 7B CPU
NCT Cable
Switch/ Connection
Router
infn_114

Multi-chassis Configuration NCT Cabling

Release 10.0 certifies the following multi-chassis configurations:
A DTN can support up to 44 interconnected chassis (up to 32 DTC/MTCs and up to 12 OTCs) if the
Main Chassis includes an MCM-C as the node controller (although a maximum of 44 chassis are
supported in a DTN, the DTN supports a chassis ID range of 1-63). The Main Chassis must be a
DTC or an MTC
A DTN can support up to 17 interconnected chassis (DTC/MTC/OTCs) if the Main Chassis includes
an MCM-B as the node controller. The Main Chassis must be a DTC or an MTC; the 16 Expansion
Chassis can be any combination of DTC/MTC/OTCs
“To connect NCT cables for multi-chassis with full MCM redundancy” on page 13-12
“To connect NCT cables for multi-chassis with MCM redundancy only on Main Chassis” on page 13-
14
To connect NCT cables for multi-chassis with full MCM redundancy
For example, NCT port 1A on chassis 1 is specified as 1-NCT-1A. The last chassis in the configuration is
Step 3 Connect 1-NCT-2A to n-NCT-1B.
Step 4 Connect 1-NCT-2B to n-NCT-1A.
Step 5 Connect 2-NCT-1A to n-NCT-2A.
Step 6 Connect 2-NCT-1B to n-NCT-2B.

Figure 13-6 NCT Connectivity for Multi-chassis with Full MCM Redundancy

Chassis 1
MCM MCM
in 7A in 7B
or CPU or CPU
OMM OMM
in 1A in 1B
Switch/ Switch/
Router Router
DTC/MTC

Chassis 2
MCM MCM
in 7A in 7B
or CPU or CPU
OMM OMM
in 1A in 1B
Switch/ Switch/
Router Router
DTC/MTC/OTC

Chassis n
MCM MCM
in 7A in 7B
or CPU or CPU
OMM OMM
in 1A in 1B
Switch/ Switch/
DTC/MTC/OTC
Connection
infn_1165

To connect NCT cables for multi-chassis with MCM redundancy only on Main Chassis
Step 3 Connect n-NCT-2A to 1-NCT-1A.

Figure 13-7 NCT Connectivity for Multi-chassis with MCM Redundancy only on Main Chassis
DTC/MTC
I/O Panel
Chassis 1
MCM MCM
CPU CPU
in 7A in 7B
Switch/ Switch/
Router Router
DTC/MTC/OTC
I/O Alarm Panel
Chassis 2
MCM
CPU
in 7A
or
Switch/ OMM
Router in 1A
DTC/MTC/OTC
I/O Alarm Panel
Chassis n
MCM
CPU
in 7A
or
Switch/ OMM
NCT Cable in 1A
Router
Connection infn_133c
Note: Figure 13-7 shows an example of an NCT configuration where full MCM/OMM redundancy
is available on chassis 1 (Main Chassis) only. The last chassis in the configuration is

CAUTION
CAUTION
WARNING
WARNING

WARNING
and correction.
WARNING
and correction.

POWER POWER
INPUT FAULT
Terminal studs
RTN

ON OFF
70A
POWER A infn_062a

CAUTION
The following sections provide the procedures to power up the DTC/MTC.
Initial Start-up
OFF
either PEM)
After you have verified that power is present on both PEMs and no faults exist, you are ready to launch
Infinera GNM to create the expansion chassis followed by initial commissioning of the chassis.

Expansion Chassis.
sage is displayed.

Step 2 In the browser, enter the DCN IP address of the target DTC/MTC. Infinera GNM is launched in a





Note: Figure 13-13 shows a DTC Main Chassis. However, this procedure also applies if the Main
Chassis is an MTC or an XTC.
Discovered
Serial Number


Step 6 Click Ok.
Step 7 Click Close.

Initial Commissioning for the DTC/MTC Expansion Chassis
Note: Ensure that only one MCM is installed in either slots 7A or 7B and any modules occupying
slots 3, 4, 5, and/or 6 are not seated.
configure the DTC/MTC. Wait for the following message to be displayed:
then press Enter.


[N]?

Note: Disconnecting the serial cable during the boot up process may cause the MCM/OMM to
hang and not boot up correctly. Ensure the boot up process is complete before disconnect-
ing the serial cable.
Step 5 Login to Infinera GNM of the Main Chassis (Shelf 1). from the Equipment Tree, right-click on the
Expansion Chassis and select Properties. The Chassis Properties window is displayed.
Figure 13-15 Expansion Chassis Properties
Step 6 From the Properties window, in the Provisioned SN field, select the chassis serial number from
the drop-down menu.
Note: To verify the serial number for each Expansion Chassis, ensure the Provisioned SN
matches the serial number on the tag located on the right side of the chassis.
Step 7 Click Apply.

Step 8 When finished, click Close.
Step 9 From the Equipment Tree, right-click the Expansion Chassis and select Admin State.

Step 10 Change the Admin State of the Expansion Chassis you just created to Unlocked.
Once the software download is complete, you will see a new chassis name in the Infinera GNM Equipment
Tree but you may still see Red. Log out of the current GNM session and start a new session; this will allow
the equipment to be re-discovered and change the display (in the Equipment Tree) to Green.
up process. When the PWR and ACT LEDs are all lit solid Green the MCM has completed booting up. This
indicates the MCM is operational (and safe to remove the serial cable).

mode.
mode.

Step 4 Click Apply.
Step 5 Click Close.


Switching
Mode

and/or 2.
Step 2 Click Apply.
page 13-33.
BMM2/BMM2P/BMM2H.
and select Admin State -> Unlock.

Expansion BMM

Expansion BMM
(grayed out)

Each DTC/MTC may contain up to two (2) Band Multiplexing Modules (BMMs). Ensure that the
appropriate BMMs are installed in slots 1 and/or 2 of the DTC/MTC prior to performing this procedure. It is
Step 2 Connect line fibers from the OUT (transmit) line port on BMM slot 2 to the IN (receive) line port
on BMM slot 1 for eastbound traffic. Ensure there is appropriate attenuation (depending on span
loss) at the input port of the BMM. Specific attenuation is required for BMM deployments utilizing
TW-C fiber type, refer to Table 13-2 on page 13-36.

Gen 1 Gen 2 Gen 2

0 1.5 -1.5

10 to 40 -3.0 3 5 2
41 to 80 -3.0 3 5 2
81 to 160 -6.0 N/A N/A 5


Note: To enable the OSC connectivity, this configuration must be performed on each BMM at
DTC/MTC.
Expansion Chassis.

networks.




(BMMs).

67


Expansion BMMs
BMM2H.
on page C-88
on page C-88
on page C-89

Figure 13-23 Line Module Auto-discovery Completion
General tab
Connected BMM port

Tx Auto Discovery
State
Step 4 Click Close.



Step 9 Click Close.
Unlock.

Tunable tab
Operating Mode
Provisioned OCG
Number

Verifying Optical Carrier Group (OCG) Loss Threshold
page 13-50
page 13-54
on page 13-56
2)” on page 13-62


BMM OCG)
GAM Trib OCG)
BMM OCG)
BMM OCG)
BMM OCG)


(OPR).

(OPT).


(OPR).


(OPT).
(OPR).

(OPT).



(OPR).

(OPT).


(OPR).

(OPT).

GAM-1)
BMM2H via a GAM-1:

(OPR).

(OPT).
(OPR).

(OPT).


a GAM-2:

(OPR).


(OPT).
(OPR).

(OPT).



Fibers
page C-80




affected.




Step 8 Click Apply.
Step 9 Click Close.


association.


CMMs

BMM2H
BMM2P


(OPT).

(OPR).


AXLM-80 CMM1D-20-CB
SLM-80


(OPT).

(OPR).

Maintenance.
Step 2 Click Apply.
nels.
Unlock.

Number of Channels




Step 2 Click Apply.
type.
or PSE type.

Span/C-Band
tab
Fiber panel
Unlock.

To enter Span Loss
Expansion Chassis.
field.

Guide.


Service type
Service rate
(payload type)
Connectivity type
(for example, select OC-192/10GbE WAN):

or
Note: The default payload type is 1GbE for 8x1GbE TAMs, OC-48 for 2.5G TAMs, OC-192/
10GbE for 10G TAMs, and OC-768 for 40G TAMs.

Circuit ID (CID)
Label
Source Endpoint
Intermediate LM
Destination
Endpoint



Ok
click Ok
Step 9 Click Ok.



CAUTION




Configuring DTNs for Preamplifier

Configuration
account team and/or an Infinera TAC resource for additional information. Always clean and label fiber
optics before use, and observe the safety precautions outlined in “Laser Safety” on page 1-13.
CAUTION
and Class 1M.
CAUTION
CAUTION
ing” on page D-1.
CAUTION
A line system configuration with a preamplifier is supported at a DTN site to provide a longer reach across
a digital span by improving the optical add/drop multiplexer (OADM) performance of the Infinera Intelligent
Transport Network.
 “To turn up a DTN with an OAM preamplifier configuration” on page 13-94
 “To turn up a DTN with an ORM preamplifier configuration” on page 13-99
 “To turn up a DTN with an OAM-CXH1-MS preamplifier and RAM-2-OR configuration” on page 13-
103
Table 13-6 on page 13-94 lists the required modules for a DTN with a preamplifier configuration.

Page 13-94 Configuring DTNs for Preamplifier Configuration
Table 13-6 DTN Preamplifier Configuration
Node Type Main Module Booster Module Preamplifier Module
DTN BMM2P-8-CH1-MS Not supported Any one of the following:

• OAM-CXH1-MS
• OAM-CXH2-MS
• OAM-CXH3-MS
• ORM-CXH1-MS
• ORM-CXH1
OAM-CXH1-MS + RAM-2-OR
Note: Preamplifier modules must be associated with the main module (from the management
interfaces) to provide preamplifier functions for the required digital span(s). Otherwise,

initially commissioned as Main Chassis and Expansion Chassis where applicable:
 Main Chassis - DTC turned up as a Multi-chassis network element with one BMM2P-8-CH1-MS, one
line module (ADLM/AXLM), and one GAM-2 installed, and Auto-discovery completed
 Expansion Chassis - OTC turned up as a Multi-chassis network element with any of the following
modules installed: OAM-CXH1-MS, OAM-CXH2-MS, OAM-CXH3-MS, ORM-CXH1-MS, and/or
ORM-CXH1, and Auto-discovery
completed. (For a BMM2P with OAM + RAM configuration, ensure that one OAM-CXH1-MS and one
RAM-2-OR module is installed)
To turn up a DTN with an OAM preamplifier configuration
Figure 13-61 on page 13-95 shows an example configuration of a DTN with an OAM preamplifier.

Figure 13-61 Example Configuration of a DTN with an OAM Preamplifier

DTC
1 2 3 4 5 6
GAM-2 Control
BMM2P
7A GAM-2
In P1 In
MCM
Out
TAM
P1 Out
Line Out OCGn
In P2 In
Line In
TAM
P2 Out
7B OCGn
Out
OCGn
Out In
TAM
ADLM/AXLM
MCM
From To
TAM
BMM2P BMM2P
OCGn OCGn
Out In
Note:
Main Chassis
The OTS patch cable loss supported
between the OAM-CXH1-MS preamplifier
and the BMM2P is 1.5dB.
When an expansion BMM2P is configured,
Expansion Chassis
the OTS patch cable loss supported
OTC
between the base BMM2P and the
1A 1B
OMM OMM expansion BMM2P is 1.5dB.
OAM-CXH1-MS
OSC
Line 2 In Out Line
Out In Transmission
Fiber
3
BLANK
infn_141
infn_553
Note: The Infinera GNM window should be kept open until this procedure is complete.

Step 2 Create the association between the BMM2P-8-CH1-MS and the OAM-CXH1-MS. At the Main
Chassis:
Step 2g Unlock the BMM2P in slot 1. From the Infinera GNM Equipment View, right-click the
BMM2P and select Admin State -> Unlock.
Figure 13-62 Setting the DTN with OAM Preamplifier Association
Span/C-Band tab
Association panel
Rx Associated
OTS AID

Step 3 Verify the association between the BMM2P-8-CH1-MS and the OAM-CXH1-MS. At the Main
Chassis:
OTS Eqpt box.
Figure 13-63 Verifying the DTN with OAM Preamplifier Association
Span/C-Band tab
Association panel
Rx Associated
OTS Eqpt

Step 4 Install clean, labeled, fiber optic cables at the DTN between the Main and Expansion Chassis.
Refer to Figure 13-61 on page 13-95 while performing this step.
Step 4a Connect the GAM-2 P1 Out port to the ADLM/AXLM OCGn In port.
Step 4b Connect the ADLM/AXLM OCGn Out port to the GAM-2 P1 In port.
Step 4c Connect the GAM-2 P2 Out to the BMM2P Slot 1 OCGn In port.
Step 4d Connect the BMM2P Slot 1 OCGn Out port to the GAM-2 P2 In port.
Step 4e Connect the incoming transmission fiber to the OAM Slot 2 Line In port.
Step 4f Connect the OAM Slot 2 Line Out port to the BMM2P Slot 1 Line In port.
Step 4g Connect the BMM2P Slot 1 Line Out port to the outgoing transmission fiber.
Step 4h Connect the OAM Slot 2 OSC Out port to the OSC In port.

To turn up a DTN with an ORM preamplifier configuration
Figure 13-64 shows an example configuration of a DTN with an ORM preamplifier.
Figure 13-64 Example Configuration of a DTN with an ORM Preamplifier

DTC
1 2 3 4 5 6
GAM-2
BMM2P
7A GAM-2
In P1 In
Out MCM
TAM
P1 Out
Line Out OCGn
In P2 In
Line In
TAM
P2 Out
7B OCGn
Out
OCGn
Out In
TAM
ADLM/AXLM
MCM
Control
From To
TAM
BMM2P BMM2P
OCGn OCGn
Out In
Main Chassis Note:

The OTS patch cable loss supported
between the ORM-CXH1-MS/ORM-CXH1
preamplifier and the BMM2P is 1.5dB.
When an expansion BMM2P is configured,
Expansion Chassis the OTS patch cable loss supported
OTC between the base BMM2P and the
1A 1B expansion BMM2P is 1.5dB.
OMM OMM
Line ORM-CXH1-MS/ Line
Out OSC In
ORM-CXH1 In Out Transmission
2 Fiber
3
BLANK
infn_555

Step 2 Create the association between the BMM2P-8-CH1-MS and the ORM-CXH1-MS/ORM-CXH1.
At the Main Chassis:
click and select Span. The Span Properties window is displayed. See Figure 13-65
on page 13-101.
ate ORM OTS AID that is connected to the BMM2P Line In (Rx) connector.
Step 2g Unlock the BMM2P in slot 1. From the Infinera GNM Equipment View, right-click the
BMM2P and select Admin State -> Unlock.

Figure 13-65 Setting the DTN with ORM Preamplifier Association
Span/C-Band tab
Association panel
Rx Associated
OTS AID
Chassis:
on page 13-102.
Step 3b In the Association panel, verify that the ORM-CXH1-MS/ORM-CXH1 is listed in the
Rx Associated OTS Eqpt box.

Figure 13-66 Verifying the DTN with ORM Preamplifier Association
Span/C-Band tab
Association panel
Rx Associated
OTS Eqpt
Step 4 Install clean, labeled, fiber optic cables at the DTN between the Main and Expansion Chassis.
Step 4a Connect the GAM-2 P1 Out port to the ADLM/AXLM OCGn In port.
Step 4b Connect the ADLM/AXLM OCGn Out port to the GAM-2 P1 In port.
Step 4c Connect the GAM-2 P2 Out to the BMM2P Slot 1 OCGn Line In port.
Step 4d Connect the BMM2P Slot 1 OCGn Line Out port to the GAM-2 P2 In port.
Step 4e Connect the incoming transmission fiber to the ORM Slot 2 Line In port.
Step 4f Connect the ORM Slot 2 Line Out port to the BMM2P Slot 1 Line In port.
Step 4g Connect the BMM2P Slot 1 Line Out port to the outgoing transmission fiber.
Step 4h Connect the ORM Slot 2 OSC Out port to the OSC In port.

To turn up a DTN with an OAM-CXH1-MS preamplifier and RAM-2-OR configuration
Figure 13-67 shows an example configuration of a DTN with an OAM-CXH1-MS preamplifier and
RAM-2-OR.
Figure 13-67 Example Configuration of a DTN with an OAM-CXH1-MS Preamplifier and RAM-2-OR
OTC Expansion
Chassis
OMM OMM
Line Line
Out OSC In
In Out
OAM-CXH1-MS
To BMM/OAM Line
Out RAM-2-OR In Transmission
Fiber
In Out
DTC Main
Chassis
BMM2P
TAM
In
MCM
Out
TAM
In Out
Line Connectors
Out In
Expansion Port Connectors
TAM
In Out
DCM Connectors
Out In
Out In
Out In
TAM
ADLM/AXLM
MCM
Out In
OCG Out In
Connectors Out In
TAM
Out In
Out In
infn_1068b

Note: The Infinera GNM window should be kept open until this procedure is complete. In addition,
refer to Figure 13-67 on page 13-103 while performing this procedure.
Step 2 Create the association between the BMM2P-8-CH1-MS and the OAM-CXH1-MS. At the Main
Chassis:
on page 13-105.

Figure 13-68 Setting the DTN with OAM-CXH1-MS Preamplifier Association
Span/C-Band tab
Association panel
Rx Associated
OTS AID

Chassis:
OTS Eqpt box.
Figure 13-69 Verifying the DTN with OAM-CXH1-MS Preamplifier Association
Span/C-Band tab
Association panel
Rx Associated
OTS Eqpt

Step 4 Create the association between the RAM-2-OR connector ports (L1 Transmit and L2 Receive) to
associate them with the correct BMM/OAM OTS ports as listed in Table 17-2 on page 17-15. At
the OTC Expansion Chassis:
Step 4a Lock the RAM-2-OR in slot 2. From the Infinera GNM Equipment View, right-click the
RAM-2-OR and select Admin State -> Lock.
Step 4b From the Equipment View, highlight the appropriate RAM-2-OR to be configured,
Step 4c In the list frame, ensure that L1 OTS ID is highlighted. See Figure 13-70 on page 13-
108.
Step 4d From the tabs listed in the middle of the window, select the Span/C-Band tab.
Step 4e In the BMM/OAM Association panel, click on Tx Associated OTS and select the
appropriate OAM OTS ID from the drop-down menu. For example, select the OAM
Step 4f Click Apply.
Step 4g In the list frame, ensure that L2 OTS ID is highlighted. See Figure 13-71 on page 13-
109.
Step 4h From the tabs listed in the middle of the window, select the Span/C-Band tab.
Step 4i In the Peer OTS Association panel, click on Rx Associated OTS and select the
Step 4j Click Apply.
Step 4k Click Close.

Span/C-Band tab
Tx Associated OTS

Span/C-Band tab
Rx Associated OTS
Step 5 At the Main Chassis: provision the fiber type for the BMM2P-CH1-MS. Refer to “Provisioning
Fiber Information” on page 13-81.
Step 6 At the OTC Expansion Chassis: provision the fiber type for the OAM-CXH-MS. Refer to “Enter-
ing DCM/PSE/DSE Information” on page 16-24.
Step 7 At the OTC Expansion Chassis: verify the RAM-2-OR L1 association on the OAM-CXH1-MS and
the L2 association on the BMM2P-CH1-MS.
Step 7a From the Equipment View, highlight the configured OAM-CXH1-MS, right-click and
select Span. The Span Properties window is displayed. See Figure 13-72 on
page 13-110.

Span/C-Band tab


Step 8 Check the fiber connectors for cleanliness, refer to “Raman Fiber Connector Cleaning” on
page D-1. Then install clean, labeled, fiber optic cables at the DTN between the Main and
Expansion Chassis as follows:
Step 8a Connect the DTC BMM2P Slot 1 Line Out port to the OTC RAM-2-OR Slot 2
BMM/OAM In port.
Step 8b Connect the OTC RAM-2-OR Slot 2 BMM/OAM Out port to the OTC OAM-CXH1-MS
Step 8c Connect the OTC OAM Slot 1 OSC Out port to the OSC In port.
Step 8d Connect OTC OAM-CXH1-MS Slot 1 Line Out port to the DTC BMM2P Slot 1 Line In
port.
Step 8e Connect the OTC RAM-2-OR Slot 2 Line Out port to the outgoing transmission fiber.
Step 8f Connect the incoming transmission fiber to the OTC RAM-2-OR Slot 2 Line In port.
Step 9 At the DTC Expansion Chassis: unlock the BMM2P in slot 1. From the Infinera GNM Equipment
View, right-click the BMM2P and select Admin State -> Unlock.
Step 10 At the OTC Expansion Chassis: unlock the RAM-2-OR in slot 2.
Step 10a From the Equipment View, right-click the RAM-2-OR and select
Step 10b Wait 3 minutes before proceeding to allow the Raman pumps to turn on and stabi-
lize.
Step 11 At the OTC Expansion Chassis: initiate the Raman point loss offset (PLO) adjustment utility, see
“Setting the Point Loss Offset for Raman Modules” on page 17-62.
Note: Refer to Table 17-10 on page 17-21 for allowable maximum point loss range for
RAM-2-ORs based on fiber type.


DTC/MTC:

Testing TOMs

Testing TAMs
Testing DICMs

Testing GAMs
state, right-click the GAM from the Equipment View.
Testing BMMs
state, right-click the BMM from the Equipment View.

Testing CMMs

state, right-click the line module/LM-80/TEM from the Equipment View.
Testing MCMs
state, right-click the MCM from the Equipment View.


the DTC/MTC.

Alarm Filter panel

Alarm Severity
to customers.
cautions.

Alarm Type Cause

Shutdown (ALS).
port not connected)



Row Column


Row Column





See Table 13-11 for the DTC alarm output contact pin assignments and Table 13-12 on page 13-128 for
the MTC alarm output contact pin assignments.
Row Column
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPENa
NORMALLY CLOSEDa
RETURN


NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED


RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN


NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED

Row Column
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN


NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPENa
NORMALLY CLOSEDa
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED


RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN


NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED
RETURN
NORMALLY OPEN
NORMALLY CLOSED

Alarm Cutoff (ACO)


To enable an ACO
tons).
Testing an ACO
to be audible.
To test an ACO


CHAPTER 14
Turning up a Network Element for

Optical Express
This chapter provides the procedures to turn up and test a network element for Optical Express. This
chapter is organized into the following sections:
“Optical Express Overview” on page 14-3
“Optical Express Turn-up and Test” on page 14-9
“Optical Express Loops” on page 14-20
“Power Control Loop Mode for Optical Express OCGs” on page 14-22

Page 14-2
Tasks
Table 14-1 lists the tasks you will perform during this portion of the turn-up and test procedure. Use this
table to keep a track of the tasks you have completed and to record test results.
Table 14-1 Optical Express Turn-up Checklist and Test Results
“Optical Express Overview“ page

14-3
“General Guidelines“ page
14-4
“Optical Express Turn-up and Test“ page
14-9
“Optical Express Loops“ page (if applicable)
14-20
“Power Control Loop Mode for Optical page (if applicable)
Express OCGs“ 14-22

Turning up a Network Element for Optical Express Page 14-3
Optical Express Overview

Note: Unless specifically noted otherwise, all references to "line module" will refer interchange-
ably to either the DLM, XLM, ADLM, AXLM, and/or SLM (DTC/MTC only) and AOLM-500,
AOLM-500B, AOLX-500, AOLX-500B, SOLM-500, SOLX-500, AOLM2-500, AOLM2-
500B, AOLX2-500, AOLX2-500B, SOLM2-500, SOLM2-500B, SOLX2-500, and/or
SOLX2-500B (XTC only). All references to the "LM-80" will refer interchangeably to the
AXLM-80, ADLM-80 and/or SLM-80 (DTC/MTC only).
In addition to the digital add/drop capabilities that are supported via the combination of the line modules/
LM-80s and the BMMs of a node, a DTN and DTN-X can also support direct BMM-to-BMM Optical
Express, wherein a fiber jumper cable is connected from the Optical Carrier Group (OCG) output port
(transmit) on one BMM to the corresponding OCG input port (receive) of another BMM (the BMMs do not
have to reside in the same chassis). Refer to “General Guidelines” on page 14-4 for detailed information
regarding the supported BMM, OAM, ORM, and line module/LM-80 types as well as specific configuration
requirements and restrictions.
Figure 14-1 Optical Express in an Intelligent Transport Network
OCG 2
Node B
Node C
Node A
Node D
OCG 3 No Optical Express: OCG 3
OCG 5 OCGs Add/Drop Only OCG 5
Node E
infn_1152
OCG 2
Figure 14-1 shows an example of Optical Express in an Intelligent Transport Network. Note that Node D is
configured for only add/drop of its OCGs: no Optical Express is configured on Node D. For standard
Optical Express configuration in a ring network, there must be at least one node that add/drops all of its
OCGs. For information on support of Optical Express loops in a ring network, see “Optical Express Loops”
on page 14-20.

Page 14-4 Optical Express Overview
The DTN and DTN-X support up to sixteen (16) Optical Express connections. Optical Express is supported
on links that are configured with ORMs, RAMs, and/or DSEs. In addition, Optical Express is supported
(with manual OCG provisioning) on BMM2s (set to SLTE Mode 1). Refer to the Infinera SLTE Turn-up and
Test Guide for additional information.
Note: Optical Express is not supported for OCG/OCH interconnections of ADLM-80/AXLM-80/

SLM-80s and/or CMMs.
Note: For Optical Express connections between Gen 1 BMMs, the BMM OCG can be locked
without affecting traffic. However, for Optical Express connections between Gen 2 BMM2s,
between BMM2Ps, and between BMM2Cs, if the BMM2/BMM2P/BMM2C OCG is locked,
Auto-discovery is re-triggered, thus impacting traffic. Make sure that BMM2/BMM2P/
BMM2C OCGs are unlocked for Auto-discovery to succeed, thereby restoring traffic.
General Guidelines
Observe the following guidelines prior to configuring for Optical Express:
 Support is provided for the following BMM types only:
BMM-4-CX1-A
BMM-4-CX2-MS-A
BMM-4-CX3-MS-A
BMM1H-4-CX2
BMM2-8-CXH2-MS
BMM2-8-CH3-MS
BMM2-8-CEH3
BMM2P-8-CH1-MS
BMM2P-8-CEH1
BMM2H-4-R3-MS
BMM2H-4-B3
BMM2C-16-CH
 Optical Express is not supported between a BMM and a BMM2/BMM2P/BMM2C. The modules in an
Optical Express connection both must be BMMs, BMM2s, BMM2Ps, or BMM2Cs
 Optical Express is supported between a 40-channel full-height and a 40-channel half-height BMM
 Optical Express is supported between a full-height and a half-height BMM2 (the number of OCGs
between the BMM2s must match)

 Optical Express is supported on all OCG ports of 40-channel BMMs (OCGs 1, 3, 5, and 7)
 Optical Express is supported on all OCG ports of BMM2/BMM2Ps:
OCGs 1 - 8 for BMM2-8-CXH2-MS
OCGs 1 - 8 for BMM2-8-CH3-MS (base BMM2)
OCGs 9 - 16 for BMM2-8-CEH3 (expansion BMM2)
OCGs 1 - 8 for BMM2P-8-CH1-MS (base BMM2P)
OCGs 9 - 16 for BMM2P-8-CEH1 (expansion BMM2P)
OCGs 1 - 4 for BMM2H-4-R3-MS (base BMM2H)
OCGs 5 - 8 for BMM2H-4-B3 (expansion BMM2H)
Note: For BMM2/BMM2P to BMM2/BMM2P Optical Express connections, the OCG Loss Out of
Range High (OORH) Threshold between Optical Express OCGs is 3.0dB.
 Optical Express is supported on all OCG ports (OCGs 1 - 16) of BMM2Cs with the following cave-
ats:
Pre-provisioning of OCGs or physical OCG fiber connections for Auto-discovery is required only
for OCGs 1 - 8
Optical Express is not supported on OCGs 1 - 8 when any of the corresponding peer ports
(OCGs 9 - 16) are provisioned for add/drop and vice versa due to implementation of OCG port
pairing on the BMM2C (refer to Table 14-2 on page 14-6). Each pair of OCG ports can either be
dropped in a BMM2C or expressed by the BMM2C. For example, if one of the paired ports is
expressed (i.e. OCG 1), the peer port (OCG 9) is automatically expressed (note that the physical
fiber connections are required only for OCG 1; fiber connections are not required for OCG 9). If
one of the paired ports is dropped (i.e. OCG 2), the peer port (OCG 10) can only be dropped in
the same BMM2C and cannot be expressed

Table 14-2 BMM2C OCG Port Pairing
OCG Port Number

(Tx and Rx Pair) OCG Pairing
1 1, 9
2 2, 10
3 3, 11
4 4, 12
5 5, 16
6 6, 13
7 7, 14
8 8, 15
9 1, 9
10 2, 10
11 3, 11
12 4, 12
13 6, 13
14 7, 14
15 8, 15
16 5, 16
 BMM2s, BMM2Ps, or BMM2Cs can be used at an intermediate node to optically express traffic that
originates/terminates on BMM2s, BMM2Ps, or BMM2Cs. However, note that for 16 channel BMMs a
connection (either add/drop or Optical Express) must be made on a base OCG (OCG 1-8) before a
connection can be made on one of the expansion OCGs (OCGs 9-16)
 Gen 1 BMMs can optically express:
100Gbps OCGs from DLM/XLM/ADLM/AXLMs
200Gbps OCGs from ADLM-80/AXLM-80s (BPSK modulation)
400Gbps OCGs from ADLM-80/AXLM-80s (QPSK modulation)
500Gbps OCGs from AOLM-500/AOLM-500B/AOLX-500/AOLX-500B/SOLM-500/SOLX-500/

AOLM2-500/AOLM2-500B/AOLX2-500/AOLX2-500B/SOLM2-500/SOLM2-500B/SOLX2-500/
SOLX2-500Bs (QPSK modulation)
 BMM2/BMM2Ps can optically express:
100Gbps OCGs from DLM/XLM/ADLM/AXLMs
200Gbps OCGs from ADLM-80/AXLM-80/SLM-80s (BPSK modulation)
400Gbps OCGs from ADLM-80/AXLM-80/SLM-80s (QPSK modulation)


SOLX2-500Bs (BPSK modulation)
SOLX2-500Bs (QPSK modulation)
 BMM2Cs can optically express:
500Gbps OCGs from AOLM-500/AOLX-500/SOLM-500/SOLX-500/AOLM2-500/AOLM2-500B/

AOLX2-500/AOLX2-500B/SOLM2-500/SOLM2-500B/SOLX2-500/SOLX2-500Bs
 Optical Express connections require correct OCG levels between BMM/BMM2/BMM2P/BMM2Cs.
BMM2/BMM2P/BMM2Cs contain a variable optical attenuator (VOA) but 40-channel BMMs do not
and therefore require a 20dB or 22dB pad for correct optical span engineering:
20dB optical attenuator, Infinera PON PAD-20-PT
22dB optical attenuator, Infinera PON PAD-22-PT
 The express OCG power needs to be within a 3dB capture window (1dB above and 2dB below the
target power):
Typical 40-channel BMM receive (Rx) OCG power: -14.0 to -13.0dBm
Typical 80-channel BMM2/BMM2P/BMM2C receive (Rx) OCG power: -1.5 to 9.0dBm
 Support is provided for the following OAM/ORM types only (for Optical Express connections involv-
ing the deployment of Optical Amplifiers):
OAM-CX1-A
OAM-CXH1-A
OAM-CXH1-MS
OAM-CX2-MS-B
OAM-CXH2-MS-A
OAM-CX3-MS-A
OAM-CXH3-MS-A
ORM-CXH1-MS
ORM-CXH1
 Optical Express termination (via O-E-O conversion) is supported by the following line module/LM-80
types only (but there is no requirement that all optically expressed OCGs within a ring must be termi-
nated at a single node):
AOLM-500/AOLM-500B/AOLX-500/AOLX-500B/SOLM-500/SOLX-500/AOLM2-500/
AOLM2-500B/AOLX2-500/AOLX2-500B/SOLM2-500/SOLM2-500B/SOLX2-500/SOLX2-500B
DLM-n-C2 (where n=1-8)
DLM-n-C3 (where n=1-8)

XLM-n-C3 (where n=1-8)

ADLM-T1-n-C4 (where n=1,3,5,7)
ADLM-T1-n-C5 (where n=1,3,5,7
AXLM-T1-n-C4 (where n=1,3,5,7
AXLM-T1-n-C5 (where n=1,3,5,7)
SLM-T4-n-C4 (where n=1,3,5,7)
SLM-T4-n-C5 (where n=1,3,5,7)
ADLM-80-T1-C5
AXLM-80-T1-C5
SLM-80-T1-C5
 Optical Express requires the correct placement of DCM units (as determined by the span design)

Optical Express Turn-up and Test

Note: Refer to “General Guidelines” on page 14-4 prior to performing these procedures.
The following procedures assume that an Optical Express configuration will be made between three (3)
nodes as shown in Figure 14-2. These nodes are referred to as Nodes A, B, and C (Node B is the Optical
Express node). It is recommended that a node numbering scheme be established for the network. For
example, eastbound traffic numbering is from BMM slot 1 (Node A) to BMM slot 2 (Node C), Optical
Express connection is from BMM slot 1 (Node B) to BMM slot 2 (Node B), and westbound traffic is from
BMM slot 2 (Node C) to BMM slot 1 (Node A).
“To create a Gen 1 BMM-to-BMM Optical Express connection” on page 14-10
“To create a Gen 2 BMM-to-BMM Optical Express connection” on page 14-13
“To connect fiber optic cables for a Gen 1/Gen 2 Optical Express connection” on page 14-15
“To remove a Gen 1 BMM-to-BMM Optical Express connection” on page 14-16
“To remove a Gen 2 BMM-to-BMM Optical Express connection” on page 14-18
Figure 14-2 Optical Express Configuration

BMM to line module fiber connections (Nodes A and C)
BMM to BMM OCG fiber connections (Node B)
BMM line side fiber connections (Nodes A, B, and C)
Node A Node B Node C

BMM
BMM
BMM
BMM
TAM
TAM
empty
MCM
MCM
MCM
TAM
TAM
empty
empty
empty
empty
empty
empty
empty
empty
empty
empty
TAM
TAM
Line Module
Line Module
TAM
TAM
MCM
MCM
MCM
empty
TAM
TAM
1 2 3 4 5 6 7 1 2 3 4 5 6 7 1 2 3 4 5 6 7
Terminal Node Optical Express Node Terminal Node

infn_309b

Page 14-10 Optical Express Turn-up and Test
To create a Gen 1 BMM-to-BMM Optical Express connection
Note: Refer to “General Guidelines” on page 14-4 prior to performing this procedure.
Step 1 At the Optical Express node, do one of the following:

From the Equipment View, right-click one of the BMM icons and select Optical Carrier
Group
From the Equipment Tree, right-click a chassis name and select Optical Carrier Group
The BMM OCG Port Properties window is displayed.

Step 2 In the BMM OCG Port Properties window, select the appropriate OCG port.
Step 3 Click the State tab. See Figure 14-3.
Figure 14-3 Lock BMM OCG Port
OCG
port
State tab
Admin State
Step 4 Click Admin State -> Lock.

Step 5 Click Apply.

Step 6 Repeat Step 1 through Step 5 for the other BMM in the Optical Express configuration.
Step 8 In the OCG Connectivity panel, click the Provisioned OCGPTP drop-down menu, and select
the OCG port on the other BMM in the Optical Express configuration. See Figure 14-4.
Figure 14-4 Create Optical Express Connection
OCG
port
General
tab
OCG Connectivity
panel
Provisioned
OCGPTP
Step 9 Click Apply.

Step 10 In the OCG Configuration panel, verify that Express is listed. See Figure 14-5 on page 14-12.

Figure 14-5 Verify Optical Express Connection
OCG
Configuration
panel
Optical
Express
Step 11 Click Close to exit the BMM OCG Port Properties window.
Step 13 Proceed to “To connect fiber optic cables for a Gen 1/Gen 2 Optical Express connection” on
page 14-15.

To create a Gen 2 BMM-to-BMM Optical Express connection

Group

Step 2 In the BMM OCG Port Properties window, select the appropriate OCG port.
Step 4 In the OCG Configuration panel, verify that Express is listed. See Figure 14-6.
Figure 14-6 Verify Optical Express Connection
OCG
port
General
tab
OCG Optical
Configuration Express
panel

Step 6 Proceed to “To connect fiber optic cables for a Gen 1/Gen 2 Optical Express connection” on
page 14-15.

To connect fiber optic cables for a Gen 1/Gen 2 Optical Express connection
See Figure 14-2 on page 14-9 when performing this procedure.

Step 1 Connect a fiber from line module/LM-80 slot 3 OCG n OUT (Node A) to BMM slot 1 OCG n IN
(Node A) where n = 1 - 16.
Step 2 Connect a fiber from BMM slot 1 OCG n OUT (Node A) to line module/LM-80 slot 3 OCG n IN
(Node A) where n = 1 - 16.
Step 3 Connect a line fiber from BMM slot 1 LINE OUT (Node A) to BMM slot 1 LINE IN (Node B) for
eastbound traffic.
Step 4 Connect a line fiber from BMM slot 1 LINE OUT (Node B) to BMM slot 1 LINE IN (Node A) for
eastbound traffic.
Step 5 Connect a fiber jumper from BMM slot 1 OCG n OUT (Node B) to BMM slot 2 OCG n IN (Node
B) where n = 1 - 16.
Note: For 40-channel BMMs only: ensure there is a 20dB or 22dB optical attenuator at the input
port of the BMM in slot 2 depending on the loss required for your configuration.
Step 6 Connect a fiber jumper from BMM slot 2 OCG n OUT (Node B) to BMM slot 1 OCG n IN (Node
B) where n = 1 - 16.
Note: For 40-channel BMMs only: ensure there is a 20dB or 22dB optical attenuator at the input
port of the BMM in slot 1 depending on the loss required for your configuration.
Step 7 Connect a line fiber from BMM slot 2 LINE OUT (Node B) to BMM slot 2 LINE IN (Node C) for
westbound traffic.
Step 8 Connect a line fiber from BMM slot 2 LINE OUT (Node C) to BMM slot 2 LINE IN (Node B) for
westbound traffic.
Step 9 Connect a fiber from BMM slot 2 OCG n OUT (Node C) to line module/LM-80 slot 3 OCG n IN
(Node C) where n = 1 - 16.
Step 10 Connect a fiber from line module/LM-80 slot 3 OCG n OUT (Node C) to BMM slot 2 OCG n IN
(Node C) where n = 1 - 16.

To remove a Gen 1 BMM-to-BMM Optical Express connection

Group

Step 2 In the BMM OCG Port Properties window, select the appropriate OCG port. Ensure that both
OCGs for the BMMs configured for Optical Express are in a Locked state.
Figure 14-7 Error Message
Step 3 Click the State tab.

Step 5 Click Apply.
Step 8 From the Provisioned OCGPTP drop-down menu, select <Delete Assoc.>. See Figure 14-8 on
page 14-17.
Step 9 Click Apply.
Step 12 Ensure that the fiber optic cables for the Optical Express configuration have been removed.

Figure 14-8 Delete Optical Express Connection
OCG
port
General
tab
OCG Connectivity
panel
Delete
Association

To remove a Gen 2 BMM-to-BMM Optical Express connection

Group
The Optical Carrier Group Properties window is displayed.

Step 2 In the Optical Carrier Group Properties window, select the appropriate OCG port. Ensure that
both OCGs for the BMMs configured for Optical Express are in a Locked state.
Figure 14-9 Error Message
Step 3 Click the State tab.

Step 5 Click Apply.
Step 8 From the Provisioned OCGPTP drop-down menu, select <Delete Assoc.>. See Figure 14-10
on page 14-19.
Step 9 Click Apply.
Step 12 Ensure that the fiber optic cables for the Optical Express configuration have been removed.

Figure 14-10 Delete Optical Express Connection
OCG
port
General
tab
OCG Connectivity
panel
Delete
Association

Page 14-20 Optical Express Loops
Optical Express Loops

The default support for Optical Express in a network with a ring configuration is to require at least one node
in the ring to add/drop all of its OCGs, as in Figure 14-1 on page 14-3. However, Infinera nodes can be
configured to support an Optical Express loop, in which each node in the ring is configured with Optical
Express. Figure 14-11 shows an example ring network that is configured with an Optical Express loop. In
Figure 14-11, each of these nodes is configured for Optical Express of at least one OCG.
Figure 14-11 Example Configuration of an Optical Express Loop in the Network

OCG 2
Node B OCG 5
Node C
Node A Node D
OCG 3 OCG 3
OCG 5 OCG 2
infn_1151
Node E
To configure an Optical Express loop in the network, each BMM in the loop (and each BMM carrying
Optical Express traffic originating from the ring) must be enabled for the Optical Express route (OER) loop
feature. Unless this feature is enabled on each BMM, an Optical Express loop is not supported, meaning
that at least one node in the ring is required to add/drop all of its OCGs.
The following BMMs support Optical Express loops:
 BMM2P-8-CH1-MS
 BMM2-8-CXH2-MS
 BMM2-8-CH3-MS
 BMM2H-4-R3-MS
 BMM2C-16-CH
To enable Optical Express route loop
Step 1 From the Equipment View, right-click the BMM and select Admin State -> Lock. A warning mes-
sage is displayed.

Step 2 Click Lock BMM.

Step 3 From the Equipment View, right-click the BMM and select Properties. The BMM Properties win-
dow is displayed. See Figure 14-12.
Step 4 In the Summary panel, click OER Loop and select Enabled. A confirmation dialog is displayed.
Step 6 Click Apply.
Step 7 Click Close.
Step 8 From the Equipment View, right-click the BMM and select Admin State -> Unlock.
Step 9 Repeat Step 1 through Step 8 for the remaining BMMs in the OER loop configuration.
Figure 14-12 Enable Optical Express Route (OER) Loop
OER Loop

Page 14-22 Power Control Loop Mode for Optical Express OCGs
Power Control Loop Mode for Optical

Express OCGs
By default, the Power Control Loop mode for Optical Express OCGs is set to automatic. In rare cases
where the OCGs are carrying LM-80 channels, there may be a delay in Auto-discovery completion for
Optical Express connections between BMM2s where the effective channel count is less than five (refer to
the Infinera DTN and DTN-X System Description Guide and/or Infinera DTN and DTN-X Hardware
Description Guide for an explanation of effective channels).
In such cases, Auto-discovery may not complete, in which case the Power Control Loop Mode should be
changed to “open.” (This is called FORCEDOPENLOOP in the ED-OCG command of TL1.)
For OCGs in Open Loop mode, the BMM will not report OLOS nor OPR-OOR alarms, nor can the BMM
detect OLOS in the case where the fiber between the CMM and the BMM is unplugged.
Note: This feature is not supported for OCGs that are provisioned for manual (for example, when
Optical Express is configured for BMM2s set to SLTE Mode 1). Refer to the Infinera SLTE
Turn-up and Test Guide for additional information.
CAUTION
Before disconnecting an OCG fiber, it is important to lock the BMM OCGs at the Optical
Express site. (And then unlock the BMM OCG once the fiber is reconnected.)
Before disconnecting an OCG fiber between a CMM and a BMM, it is important that the
associated CMM OCG is set to the Locked admin state before unplugging an OCG fiber.
(And then unlock the CMM OCG once the fiber is reconnected.)

CHAPTER 15
Turning up an Optical Amplifier as an

SNE
This chapter provides the procedures to turn up and test an Optical Amplifier as a Subtending Network
Element (SNE). This chapter is organized into the following sections:
“Optical Amplifier Main Chassis Turn-up” on page 15-2
“Testing OTC Circuit Packs” on page 15-39
Note: Configuring an Optical Amplifier as a Gateway Network Element (GNE) is not supported.

Page 15-2 Optical Amplifier Main Chassis Turn-up
Optical Amplifier Main Chassis Turn-up

This section provides the turn-up and test procedures for an Optical Amplifier. The Optical Amplifier
consists of at least one Optical Transport Chassis (OTC) and zero or more Dispersion Management
Chassis (DMC).
Figure 15-1 shows the various hardware components of the OTC.
Figure 15-1 Front View OTC

Turning up an Optical Amplifier as an SNE Page 15-3
Tasks
Table 15-1 Optical Amplifier Turn-up Checklist and Test Results

15-5
15-7
“Verifying Power to the OTC“ page
15-10
“Powering up the OTC“ page
15-12
“Initial Commissioning for the OTC as page
a Subtending Network Element 15-13
(SNE)“
“Verifying OMM Craft Ethernet Port IP page
15-21
15-24
Channel“ 15-28
Channel“ 15-30
“Entering DCM/PSE/DSE Information“ page (if applicable)
15-31
15-32
15-34

Table 15-1 Optical Amplifier Turn-up Checklist and Test Results

“Installing the Standby OMM“ page (if applicable)
15-37
15-38


Before performing the turn-up and test procedures on an OTC, a serial connection between the network
end.
OMM.
Step 4 Enter a name for the new connection in the Name field (this example uses “Test”).

“COM1”).
Step 8 Enter the following serial setup parameters:

Step 9 Click OK.
Note: This window should be kept open until the initial commissioning of the OTC is complete.
The HyperTerminal (serial connection) is now created.


Infinera GNM interface. The OTC provides a craft Ethernet port on the OMM. The following procedure
describes how to connect an Ethernet cable to the OMM. Ethernet connectivity requires either a straight-
through or a crossover CAT5 Ethernet cable with RJ-45 connectors at both ends. Older GNM terminals
may require a crossover CAT5 Ethernet cable.
used to access the Infinera GNM from the OMM is 192.168.0.1.
Step 1 Connect the Ethernet cable to the Ethernet port on your craft computer.
Step 2 Connect the Ethernet cable to the connector labeled Craft on the active OMM.
OTC.
suggested.



address should be in the same subnet as the IP address configured for the target OMM or the
OTC. The last octet must vary between 2 and 255.
Note: The default IP address of the MCM/OMM is: 192.168.0.1.

Step 8 Click OK.
Step 9 Click Close.

Verifying Power to the OTC
CAUTION
CAUTION
Ensure that only the PEMs and fan trays are fully seated in the OTC. Additionally, ensure
that all modules occupying slots 1A, 1B, 2, and 3 are not seated prior to performing this
procedure.
Perform the following procedure to verify the power to the OTC.
To verify power supply to the OTC
Step 1 At the power distribution unit (PDU) power source that feeds OTC POWER A and B (PEM A and
PEM B), verify that the power is turned off and perform the following.
Step 2 At the PDU power source that feeds OTC POWER A (PEM A), turn on the power.
WARNING
correction.
and correction.
Step 4 At the PDU power source that feeds OTC POWER A (PEM A), turn off the power.

Step 5 At the PDU power source that feeds OTC POWER B (PEM B), turn on the power.
WARNING
terminal screws at PEM B. See Figure 15-7.
correction.
and correction.
Step 7 At the PDU power source that feeds OTC POWER B (PEM B), turn off the power.
Step 8 At the OTC, perform the following steps.
Step 8b Install one OMM into slot 1A or slot 1B (verify that only one OMM is fully seated; if a
redundant OMM is occupying the second slot, ensure that it is not fully seated).
Step 8c Verify that any modules occupying slots 2 and/or 3 are not fully seated.
the OTC and perform the initial start-up procedure.
Figure 15-7 Measuring DC Voltage at OTC PEMs
P
O
W ALARM INPUTS
-48V -48V E
R Terminal screws
RTN RTN
A Measure voltage
across the heads of
the terminal screws.
infn_084a

Powering up the OTC
CAUTION
Perform the following procedure to power up the OTC.
Initial Start-up
and Hardware Installation Guide), the OTC may be started up.
To startup the OTC
PEM B), turn on the power.
OFF
either PEM)
After you have verified that power is present on both PEMs and no faults exist, initially configure the OTC.

Initial Commissioning for the OTC as a Subtending Network

Element (SNE)
Note: Ensure that only one OMM is installed in either slots 1A or 1B.
Note: Configuring an OTC as a Gateway Network Element (GNE) is not supported.
GNM terminal.
After you have powered up the OTC for the first time, the boot up process is initiated. Within a minute or
the OTC. You must have the site specific commissioning data at hand (listed in “Commissioning Data” on
The procedures to commission an OTC vary depending on whether the OMM was commissioned
previously or not.
 “To initially commission the chassis as an SNE if the OMM was not commissioned previously” on
page 15-14
 “To initially commission the chassis as an SNE if the OMM was commissioned previously” on
page 15-16
See “XCM/IMM/MCM/OMM Rebranding Flow” on page B-1 for a graphical representation of the OMM
branding procedure.

To initially commission the chassis as an SNE if the OMM was not commissioned previously
If the OMM was not commissioned previously, the following message is displayed in the HyperTerminal
session:
Main Chassis - (yes|no)?
then press Enter.

Step 1 Main Chassis - [yes|no](yes)?—Type yes



NE Name? AMP1
Router ID? 11.10.2.22
Shelf ID[1-63]? 1
N)[N]?
The OMM will reboot and the following message is displayed:
Main Chassis : yes
NE Name : AMP1
Router ID : 11.10.2.22
Shelf ID : 1
chassis_check: (127_1_3_1) (127_1_3_2) (127_2_3_1) (127_2_3_2).
boot up process may cause the OMM to hang and not boot up correctly. Ensure the boot

The OMM can take some time to complete the boot up process. When the PWR, NC, and ACT LEDs are
all lit solid Green the OMM has completed booting up. This indicates the OMM is operational (and safe to
This completes the initial commissioning of the OMM.
To initially commission the chassis as an SNE if the OMM was commissioned previously
If the OMM was commissioned previously, the following message is displayed in the HyperTerminal
session:
Main Chassis : yes
NE Name : AMP2
Router ID : 11.10.2.23
Shelf ID : 1
then press Enter.
Step 2 Main Chassis - [yes|no](yes)?—Type yes


system time.

NE Name(Node_2) ? AMP3
Router ID(11.10.2.23) ? 11.10.2.22
!!!!!!!!!!!!!!!!!!!!!!!!!!
N)[N]?


(1132135975) Thu Mar 13 10:12:55 2014
Type yes to re-brand the OMM.
If the OMM did not have a database stored on it, the following message is displayed:

Go to Step 13
If the OMM had a database stored on it, the following message is displayed:

Go to Step 14
This completes the initial commissioning of the OMM. The OMM can take some time to complete the boot
up process. When the PWR, NC, and ACT LEDs are all lit solid Green the OMM has completed booting up.
This indicates the OMM is operational.
Type yes to re-brand the OMM. The following message is displayed:

no]?

up process. When the PWR, NC, and ACT LEDs are all lit solid Green the OMM has completed booting
up. This indicates the OMM is operational.
Type no if you do not want to re-brand the OMM. The following message is displayed:

up process. When the PWR, NC, and ACT LEDs are all lit solid Green the OMM has completed booting
up. This indicates the OMM is operational (and safe to remove the serial cable).

Verifying OMM Craft Ethernet Port IP Connectivity

To verify OMM craft Ethernet port IP connectivity, first ping the OMM craft Ethernet port IP address, and
then test the network element connection. If the GNM terminal will be used to verify the OMM craft
Ethernet port IP connectivity:
 Ensure that an Ethernet cable is connected from the GNM terminal to the correct OMM craft Ether-
net port on the OTC. If the OMM is located in Slot 1A, use OMM craft Ethernet port A. If the OMM is
located in Slot 1B, use OMM craft Ethernet port B
 Verify that the GNM terminal IP address is in the same IP domain as the OTC
minal IP address.
To ping the OMM craft Ethernet port IP address

ping [OMM Craft Ethernet Port IP Address]


To test the OMM craft Ethernet port IP connection of the target OTC

Step 2 Enter the OMM craft Ethernet port IP address of the target OTC in the web address (URL) field.
If the connection is established, a login window is displayed. This verifies OMM craft Ethernet
port IP connectivity to the network element.

Note: Infinera GNM may be launched from the Ethernet craft port of an OMM using craft Ethernet
port IP address.
sage is displayed.

Step 2 In the browser, enter the OMM Craft Ethernet Port IP address of the target OTC. Infinera GNM is
launched in a new window and the Login window is displayed.
your password. This is mandatory.

The Infinera GNM Main View of the OTC is displayed showing all circuit packs installed and their current
alarm conditions. See Figure 15-10 on page 15-23.

Figure 15-10 Infinera GNM Main View of OTC


It is important to know what version of software is on the Active OMM in the OTC. The software version
should be recorded in Table 15-1 on page 15-3. The software release version is of the format X.Y.Z
where X is the major version number, Y is the minor version number, and Z is the maintenance version
number.

 From the Equipment View, select the Active OMM. The Quick View Browser panel in the lower left
corner displays the OMM software version number as shown in Figure 15-11
Software
Version



displayed.


Step 6 Click OK.



Step 11 Click OK.
face.


Each OTC may contain two Optical Amplification Modules (OAMs) or two Optical Raman Modules
(ORMs). It is recommended that a node numbering scheme be established for the network. For example,
eastbound traffic numbering is from OAM/ORM slot 2 (Node A) to OAM/ORM slot 3 (Node B) and
westbound traffic is from OAM/ORM slot 3 (Node B) to OAM/ORM slot 2 (Node A).
Step 1 Connect line fibers from the OUT (Transmit) Line Port on OAM/ORM slot 2 (Node A) to the IN
(Receive) Line Port on OAM/ORM slot 3 (Node B) for eastbound traffic.
Step 2 Connect line fibers from the OUT (Transmit) Line Port on OAM/ORM slot 3 (Node B) to the IN
(Receive) Line Port on OAM/ORM slot 2 (Node A) for westbound traffic.

Note: To enable the OSC connectivity, this configuration must be performed on each OAM/ORM
at each end of the link.
OTC.
Step 1 From the Equipment View, highlight the appropriate OAM/ORM to which the optical link is con-
nected.

Note: The OSC IP address and the DCN IP address for each OTC must be on different IP net-
works.
When OTCs are physically connected, the OSC IP address configured on the OAM/ORMs must
be in the same subnet in order for the OSC to function properly. For example, OAM/ORM slot 1
and OAM/ORM slot 1 (Node B) will have an address like 192.168.30.2 with Subnet Mask like
Step 10 Repeat Step 1 through Step 9 for the remaining OAM/ORM.

OAM/ORM at each end of the link.


Entering DCM/PSE/DSE Information

If an OTC includes a Dispersion Management Chassis (DMC), there may be multiple Dispersion
Compensation Module (DCM) and/or Passive Spectrum Equalizer (PSE) ports. Release 10.0 also
supports the connection of a Dynamic Spectrum Equalizer (DSE) to a DCM port (DSEs are physically
installed in an OTC).
Perform the following procedure to enter the DCM/PSE/DSE information for an Optical Amplification
Module (OAM)/Optical Raman Module (ORM) in the OTC.
To enter DCM/PSE/DSE information
Step 1 From the Equipment View, highlight the appropriate OAM/ORM, right-click and select Proper-
ties. The OAM/ORM Properties window is displayed.
For PSEs—from the Dispersion Compensation panel, click the DCM radio button and
select the PSE from the DCM Type drop-down menu.
Figure 15-16 OAM/ORM Properties: Mid Stage Port

Step 4 Click Close to exit the OAM/ORM Properties window.
Step 5 Repeat Step 1 through Step 4 for remaining OAM/ORMs that have a DCM/PSE/DSE.


Perform the following procedure to provision the fiber information for each OAM/ORM in the OTC.
Step 1 From the Equipment View, highlight the appropriate OAM/ORM to be configured, right-click and
Step 2 Click Apply.
Step 3 Right-click the OAM/ORM and select Span. The Span Properties window is displayed. From
the tabs listed in the middle of the window, select the Span/C-Band tab.
Step 4b Enter the Line Out Pad (attenuator) value (line out = OAM/ORM Tx port).
Step 4c Enter the Line In Pad (attenuator) value (line in = OAM/ORM Rx port).
type.
or PSE type.

Span/C-Band
tab
Fiber panel

Step 7 From the Equipment View, highlight the appropriate OAM/ORM, right-click and select

Verifying Span Loss

Perform the following procedure to verify the span loss on each OAM/ORM in the OTC.
To verify span loss
Step 1 From the Equipment View, highlight the appropriate OAM/ORM.

Step 2 Right-click on the OAM/ORM and select Span. The Span Properties window is displayed.
OAM/ORM.

right-click any OAM/ORM and select GMPLS Link. The GMPLS Node ID is located in the
bottom left corner of the GMPLS Link Properties window. Record the GMPLS Node ID for
Perform the following procedure to provision the primary and secondary GNE IP address in the OTC.
From the Main Menu, select Configuration>Network Element
Step 5 Enter the IP address in the Secondary GNE IP Address field.
Step 6 Click Apply.

Summary panel
IP Gateway Proxy
GNE tab
Primary and
Secondary GNE
IP Addresses

Installing the Standby OMM

Perform the following procedure to install the standby OMM in the OTC.
To install the standby OMM
Step 1 Install the standby OMM.

The OMM takes some time to complete the boot up process. When it is complete, look at the
OMM and verify that the PWR LED is lit and Green and the ACT LED is lit and Yellow.
In the Management Card Properties window, ensure the OMM Redundancy Status of the
OMMs are Active and Standby
The ACT LED on the standby OMM is Yellow.

Verifying Inventory
The Infinera GNM Main View provides access to equipment, facilities, and tools used to control and
monitor the OTC. The Infinera GNM also includes a graphical representation of the OTC being managed.
To verify equipment
 Select Configuration > Equipment Manager to see a tabulated list of the installed equipment. Ver-
ify serial numbers, software versions, operation states, hardware version, and part number to those
listed on your bill of material

Testing OTC Circuit Packs

OTC:
“Testing OMMs” on page 15-39
“Testing OAMs” on page 15-40
“Testing ORMs” on page 15-40
Testing OMMs
Perform the following procedure to test an OMM.
To test an OMM with an equipment failure alarm
Step 1 Examine the LEDs on each OMM on the OTC. The FLT LED is illuminated if an alarm exists. If
an OMM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the OMM from the Equipment View.
Step 4 Select Properties. The OMM Properties window is displayed.

Page 15-40 Testing OTC Circuit Packs
Testing OAMs
Note: The following procedure applies to all OAM types.
Perform the following procedure to test an OAM.
To test an OAM with an equipment failure alarm
Step 1 Examine the LEDs on each OAM on the OTC. The FLT LED is illuminated if an alarm exists. If an
OAM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the OAM from the Equipment View.
Step 4 Select Properties. The OAM Properties window is displayed.
Testing ORMs
Note: The following procedure applies to all ORM types.
Perform the following procedure to test an ORM.
To test an ORM with an equipment failure alarm
Step 1 Examine the LEDs on each ORM on the OTC. The FLT LED is illuminated if an alarm exists. If an
ORM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the ORM from the Equipment View.
Step 4 Select Properties. The ORM Properties window is displayed.


the OTC.

Alarm Filter panel

Table 15-2 lists alarms that may occur upon turning up an OTC. These alarms do not require any
corrective action.
Table 15-2 Expected OTC Alarms
Alarm Type Cause

(OLOS) 2. Fibers are connected but they do not
have light.


Environmental alarms are those triggered by an abnormal condition at the OTC site. The OTCs support
to connect external equipment (reactors), such as fire, alarm detector, high temperature detector, door
open and so on to the OTC. When the connected equipment triggers an input contact point, it raises an
alarm with an alarm message and severity as configured by the user. Alarm output contacts allow users to
connect external equipment to the OTC.
The OTC can trigger the operation of the connected external equipment. The maximum threshold is

The OTC supports sixteen user-configurable alarm input contacts. Users can configure these input
Table 15-3 specifies the OTC alarm input contact pin-outs. One alarm contact is pre-defined in the system
and the remaining nineteen contacts can be customized by the users.
Note: Input contacts 17, 18, and 19 are not supported on the OTC.
Table 15-3 OTC Alarm Input Contact Pin Assignments
Row Column
1 I Alarm Input Contact 17 Not supported
1 J Alarm Input Contact 17 Not supported


4 I Reserved for Alarm cut-off a Predefined
4 J Reserved for Alarm cut-offa Predefined
a. ACO can be enabled using the input contact pins in addition to the ACO push button and the Infinera GNM user interface.

select Alarm Input Contacts. The Alarm Input Contacts Properties window is displayed.
Step 2 Select the input alarm contact that you want to configure in the input alarm contact table. The
Step 5 When you are done, click Close to exit the Alarm Input Contact Properties window.


The OTC supports ten user-configurable alarm output contacts. Each output has NO (normally open), NC
(normally closed) and CM (common) contacts. Under normal condition, the NO output is open and the NC
output is closed. When the output contact is enabled, the NO output is closed and the NC output is opened.
Users can enable or disable (normal condition) the output contacts either manually or automatically on
occurrence of user-defined alarm condition.
Table 15-4 specifies the OTC alarm output contact pinouts. Ten alarm contacts are pre-defined in the
system and the remaining ten contacts can be customized by the users.
Table 15-4 OTC Alarm Output Contact Pin Assignments
Row Column
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
1 W Power Fault Bay Alarm, Predefined
COMMON

1 X Power Fault Bay Alarm, Predefined

NORMALLY OPENa
1 Y Power Fault Bay Alarm, Predefined
NORMALLY CLOSEDa
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED


COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN


NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED

Figure 15-22 Configure Alarm Output Contact
Step 2 Select the alarm contact you want to edit in the Alarm Output Contact table.
Step 5 When you are done, click Close to exit the Alarm Output Contact Properties window.
Alarm Cutoff (ACO)

The OTC provides a feature to acknowledge an alarm condition and turn off the audible indicator. The ACO
push button is used to mute the current audible alarms and is located on the chassis or can be operated
remotely through the Infinera GNM interface. When the ACO is enabled, all the outstanding audio alarms
are turned off and the ACO LED on the chassis is illuminated. The ACO LED indicates that one or more
audible alarms are present, but the audible indicators have been suppressed. The ACO LED is turned off
when the silenced audible is cleared. The alarm acknowledgment by the user does not change the ACO
LED state.
To enable an ACO
Step 1 From the Equipment View, right-click just below the title bar (next to the Fan images).

Testing an ACO
to be audible.
After you have enabled an ACO, you must test it.
To test an ACO
Step 1 Create an alarm on the chassis (for example, loss of signal on an OAM).
Step 2 Press the ACO push button on the chassis or remotely through the Infinera GNM interface.
Step 3 Validate the procedure by verifying the following:
The FAULT LED should be ON (steady Red or Yellow)
Step 4 Clear the alarm. The Fault and ACO alarms should be OFF. The ACO has been successfully
tested.

node configuration.
Perform the following procedure to configure datawire services on the OTC. The port used for the datawire
Note: Infinera GNM may be launched from the Ethernet craft port of an OMM installed in an
Expansion Chassis.

procedure.


CHAPTER 16
Turning up an OTC as an Expansion

Chassis
This chapter provides the procedures to turn up and test an Optical Transport Chassis (OTC) as an
Expansion Chassis. This chapter is organized into the following sections:
“OTC Expansion Chassis Turn-up” on page 16-2
“Configuring Optical Amplifiers for Booster Configuration” on page 16-26
“Configuring an OTC with BMM2C and Preamplifier Configuration” on page 16-31
“Testing OTC Circuit Packs” on page 16-37

Page 16-2 OTC Expansion Chassis Turn-up
OTC Expansion Chassis Turn-up

This section provides the turn-up and test procedures for an OTC Expansion Chassis.
Note: The BMM2C is supported on the OTC (in slot 3 only) to provide optical line system support
for the DTN-X (XTC-10/XTC-4) and requires association with an OAM/ORM preamplifier.
The preamplifier must be equipped in slot 2 of the same OTC.

Turning up an OTC as an Expansion Chassis Page 16-3
Tasks
Table 16-1 OTC Expansion Chassis Turn-up Checklist and Test Results
“Installing OTC Multi-chassis NCT page

“Verifying Power to the OTC“ page
16-11
“Powering up the OTC“ page
16-13
“Initial Commissioning for the OTC page
16-17
16-20
“Entering DCM/PSE/DSE Information“ page (if applicable)
16-24
“Installing the Standby OMM“ page (if applicable)
16-25

Installing OTC Multi-chassis NCT Ethernet Cables

In a multi-chassis configuration, chassis are interconnected at the nodal control and timing (NCT) ports of
the I/O panels using straight-through unshielded twisted pair CAT5 Ethernet cables that conform to
allowed for each NCT cable segment between chassis is 328 feet (100 meters). A third-party Ethernet
media converter can be used for connecting NCT ports to support extended distances. Contact your
Infinera account team for assistance with third-party Ethernet media converters.
Ensure that straight-through (not crossover) CAT5 Ethernet cables are used for all NCT
Expansion Chassis may be pre-provisioned. The physical connection of NCT cables may be made prior to
Optical Amplifiers can be configured as a multi-chassis node (separate from a DTN). Multi-chassis Optical
Amplifiers can be configured with up to 4 OTCs (with optional control module redundancy on each chassis)
with 2 OAM/ORMs on the Main Chassis and up to 2 Raman modules or 2 DSEs on each Expansion
Chassis. Additionally, an OTC Expansion Chassis can house OAM/ORMs when these modules are
connected to BMM2Ps (installed in a DTC Main or DTC Expansion Chassis). Optical Amplifiers do not
support DTCs/MTCs as Expansion Chassis.
Refer to “Installing DTC/MTC Multi-chassis NCT Ethernet Cables” on page 13-7 for DTN multi-chassis
configurations consisting of DTC/MTCs and OTCs. This section is organized as follows:
 Cabling a multi-chassis configuration for fully redundant OMMs (see “To connect NCT cables for
multi-chassis with full OMM redundancy” on page 16-5)
 Cabling a multi-chassis configuration for OMM redundancy only on the Main Chassis (see “To con-
nect NCT cables for multi-chassis with OMM redundancy only on Main Chassis” on page 16-7)
 Cabling a multi-chassis configuration for non-redundant OMMs (see “To connect NCT cables for
multi-chassis non-redundant OMMs” on page 16-9)
plane availability.

Multi-chassis Configuration NCT Cabling
To connect NCT cables for multi-chassis with full OMM redundancy
Step 6 Connect 2-NCT-1B to n-NCT-1B.

Figure 16-2 NCT Connectivity for Multi-chassis with Full OMM Redundancy
OTC
I/O Alarm Panel
Chassis 1
OMM OMM
in 1A CPU in 1B CPU
Switch/ Switch/
Router Router
OTC
I/O Alarm Panel
Chassis 2
OMM OMM
in 1A CPU in 1B CPU
Switch/ Switch/
Router Router
OTC
I/O Alarm Panel
Chassis n
OMM OMM
in 1A CPU in 1B CPU
Switch/ Switch/

To connect NCT cables for multi-chassis with OMM redundancy only on Main Chassis
Step 3 Connect 2-NCT-2A to n-NCT-1A. The final logical connectivity is shown in Figure 16-3 on
page 16-8.

Figure 16-3 NCT Connectivity for Multi-chassis with OMM Redundancy only on Main Chassis
OTC
I/O Alarm Panel
Chassis 1
OMM OMM
in 1A CPU in 1B CPU
Switch/ Switch/
Router Router
OTC
I/O Alarm Panel
Chassis 2
OMM
in 1A CPU
Switch/
Router
OTC
I/O Alarm Panel
Chassis n
OMM
in 1A CPU
Switch/
NCT Cable Router

To connect NCT cables for multi-chassis non-redundant OMMs
Step 3 Connect 2-NCT-2B to n-NCT-1B. The final logical connectivity is shown in Figure 16-4 on
page 16-10.

Figure 16-4 NCT Connectivity for Multi-chassis Non-redundant OMMs
OTC
I/O Alarm Panel
Chassis 1
OMM
in 1A CPU
Switch/
Router
OTC
I/O Alarm Panel
Chassis 2
OMM
in 1B CPU
Switch/
Router
OTC
I/O Alarm Panel
Chassis n
OMM
in 1B CPU
NCT Cable Switch/

Connection Router
infn_127c

Verifying Power to the OTC
CAUTION
CAUTION
Ensure that only the PEMs and fan trays are fully seated in the OTC. Additionally, ensure
that all modules occupying slots 1A, 1B, 2, and 3 are not seated prior to performing this
procedure.
Perform the following procedure to verify the power to the OTC.
To verify power supply to the OTC
PEM B), verify that the power is turned off and perform the following.
Step 2 At the PDU power source that feeds OTC POWER A (PEM A), turn on the power.
WARNING
correction.
and correction.
Step 4 At the PDU power source that feeds OTC POWER A (PEM A), turn off the power.

Step 5 At the PDU power source that feeds OTC POWER B (PEM B), turn on the power.
WARNING
terminal screws at PEM B. See Figure 16-5.
correction.
and correction.
Step 7 At the PDU power source that feeds OTC POWER B (PEM B), turn off the power.
Step 8 At the OTC, perform the following steps.
Step 8b Install one OMM into slot 1A or slot 1B (verify that only one OMM is fully seated; if a
redundant OMM is occupying the second slot, ensure that it is not fully seated).
Step 8c Verify that any modules occupying slots 2 and/or 3 are not fully seated.
the OTC and perform the initial start-up procedure.
Figure 16-5 Measuring DC Voltage at OTC PEMs
P
O
W ALARM INPUTS
-48V -48V E
R Terminal screws
RTN RTN
A Measure voltage
across the heads of
the terminal screws.
infn_084a

Powering up the OTC
CAUTION
Perform the following procedure to power up the OTC.
Initial Start-up
and Hardware Installation Guide), the OTC may be started up.
To startup the OTC
PEM B), turn on the power.
OFF
either PEM)
After you have verified that power is present on both PEMs and no faults exist, you are ready to launch
Infinera GNM to create the expansion chassis followed by initial commissioning of the chassis.

Initial Commissioning for the OTC Expansion Chassis
Note: Ensure that only one OMM is installed in either slots 1A or 1B.
After you have powered up the OTC for the first time, the boot up process is initiated. Within a minute or
the OTC. Wait for the following message to be displayed:
then press Enter.


[N]?
and repeat the steps in case a mistake was made, or B to reboot the OMM and discard the

Step 5 Login to Infinera GNM of the Main Chassis (Shelf 1). From the Equipment Tree, right-click on the
Expansion Chassis and select Properties. The Chassis Properties window is displayed.
Figure 16-6 Chassis Properties
Step 6 From the Properties window, in the Provisioned SN field, select the chassis serial number from
the drop-down menu.
Note: To verify the serial number for each Expansion Chassis, ensure the Provisioned SN
matches the serial number on the tag located on the right side of the chassis.
Step 7 Click Apply.

Step 8 When finished, click Close.
Step 9 From the Equipment Tree, right-click the Expansion Chassis and select Admin State.

Step 10 Change the Admin State of the Expansion Chassis you just created to Unlocked.
Once the software download is complete, you will see a new chassis name in the Infinera GNM Equipment
Tree but you may still see Red. Log out of the current GNM session and start a new session; this will allow
the equipment to be re-discovered and change the display (in the Equipment Tree) to Green.
up process. When the PWR and ACT LEDs are all lit solid Green the OMM has completed booting up. This
indicates the OMM is operational (and safe to remove the serial cable).

Note: Infinera GNM may be launched from the Ethernet craft port of an OMM using craft Ethernet
port IP address.
sage is displayed.

Step 2 In the browser, enter the DCN IP address of the target OTC. Infinera GNM is launched in a new

your password. This is mandatory.
The Infinera GNM Main View of the OTC is displayed showing all circuit packs installed and their current
alarm conditions. See Figure 16-9 on page 16-19.

Figure 16-9 Infinera GNM Main View of OTC


Note: Figure 16-10 shows an OTC Main Chassis. However, this procedure also applies if the Main
Chassis is a DTC/MTC or an XTC.
Discovered
Serial Number


Step 6 Click Ok.
Step 7 Click Close.



displayed.


Step 6 Click OK.


Step 9 In the Password panel under the Password Expiry Age (days) field, enter 0.

Step 11 Click OK.
face.

Entering DCM/PSE/DSE Information

If an OTC includes a Dispersion Management Chassis (DMC), there may be multiple Dispersion
Compensation Module (DCM) and/or Passive Spectrum Equalizer (PSE) ports. Release 10.0 also
supports the connection of a Dynamic Spectrum Equalizer (DSE) to a DCM port (DSEs are physically
installed in an OTC).
Perform the following procedure to enter the DCM/PSE/DSE information for an Optical Amplification
Module (OAM)/Optical Raman Module (ORM) in the OTC.
To enter DCM/PSE/DSE information
Step 1 From the Equipment View, highlight the appropriate OAM/ORM, right-click and select Proper-
ties. The OAM/ORM Properties window is displayed.
For PSEs—from the Dispersion Compensation panel, click the DCM radio button and
select the PSE from the DCM Type drop-down menu.
Figure 16-13 OAM/ORM Properties: Mid Stage Port

Step 4 Click Close to exit the OAM/ORM Properties window.
Step 5 Repeat Step 1 through Step 4 for remaining OAM/ORMs that have a DCM/PSE/DSE.

Installing the Standby OMM

Perform the following procedure to install the standby OMM in the OTC.
To install the standby OMM
Step 1 Install the standby OMM.

The OMM takes some time to complete the boot up process. When it is complete, look at the
OMM and verify that the PWR LED is lit and Green and the ACT LED is lit and Yellow.
In the Management Card Properties window, ensure the OMM Redundancy Status of the
OMMs are Active and Standby
The ACT LED on the standby OMM is Yellow.

Page 16-26 Configuring Optical Amplifiers for Booster Configuration
Configuring Optical Amplifiers for Booster

Configuration
CAUTION
and Class 1M.
CAUTION
port of an OAM/ORM. Contact your Infinera account team and/or an Infinera Technical
Assistance Center (TAC) resource to obtain information regarding Infinera approved atten-
uator pads.
A line system configuration with a booster is supported at an Optical Amplifier site to provide a longer
reach across a digital span by improving the optical add/drop multiplexer (OADM) performance of the
Infinera Intelligent Transport Network.
Table 16-2 lists the required modules for an Optical Amplifier with booster configuration.
Table 16-2 Optical Amplifier Booster Configuration
Preamplifier
Node Type Main Module Booster Module Module
Optical Amplifier ORM-CXH1 OAM-CXH1-MS Not supported
Note: A booster amplifier module must be associated with the main module (from the manage-
ment interfaces) to provide the booster function for the required digital span(s). Otherwise,

initially commissioned as Main Chassis and Expansion Chassis where applicable.
 Main Chassis - OTC turned up as a Multi-chassis network element with an ORM-CXH1 installed and
Auto-discovery completed
 Expansion Chassis - OTC turned up as a Multi-chassis network element with an OAM-CXH1-MS
installed and Auto-discovery completed

To turn up an Optical Amplifier with an OAM booster configuration
Figure 16-14 shows an example configuration of an Optical Amplifier with an OAM booster.
Figure 16-14 Example Configuration of an Optical Amplifier with an OAM Booster
OTC
Control
1A 1B
OMM OMM
Line ORM-CXH1 OSC Line

Transmission In In Out Out
Fiber 2
Line OAM-CXH1-MS/ Line

ORM-CXH1-MS/ In Out Transmission
Note: Out In
ORM-CXH1 OSC Fiber
A 10dB optical attenuator is 3
required at the OSC In
(crossover fiber) of the Main Main Chassis
Chassis ORM-CXH1 in slot 2
(to reduce the high power
OSC entering into the Expansion Chassis
booster amplifier).
OTC
1A OMM 1B OMM
Line Line
In OAM-CXH1-MS OSC Out
In Out
2 Note:
The OTS patch cable loss
supported between the Main
BLANK Chassis ORM-CXH1 in slot 2
and the Expansion Chassis
3
OAM-CXH1-MS booster
amplifier in slot 2 is 1.5dB.
infn_556

Step 2 Create the association between the ORM-CXH1 and the OAM-CXH1-MS. At the Main Chassis:
Step 2a Lock the ORM in slot 2. From the Infinera GNM Equipment View, right-click the ORM
and select Admin State -> Lock.
Step 2b From the Equipment View, highlight the appropriate ORM to be configured, right-click
and select Span. The Span Properties window is displayed. See Figure 16-15.
Step 2c In the Association panel, click on Tx Associated OTS AID and select the appropri-
ate OAM OTS AID that is connected to the ORM Line Out (Tx) connector.
Step 2g Unlock the ORM in slot 2. From the Infinera GNM Equipment View, right-click the
ORM and select Admin State -> Unlock.
Figure 16-15 Setting the Optical Amplifier with an OAM Booster Association
Span/C-Band tab
Association panel
Tx Associated
OTS AID

Step 3 Verify the association between the ORM-CXH1 and the OAM-CXH1-MS. At the Main Chassis:
Step 3a From the Equipment View, highlight the appropriate ORM to be configured, right-
Step 3b In the Association panel, verify that the OAM-CXH1-MS is listed in the Tx Associated
OTS Eqpt box.
Figure 16-16 Verifying the Optical Amplifier with an OAM Booster Association
Span/C-Band tab
Association panel
Tx Associated
OTS Eqpt

Step 4 Install clean, labeled, fiber optic cables at the Optical Amplifier between the Main and Expansion
Chassis. Refer to Figure 16-14 on page 16-27 while performing this step.
Step 4a Connect the incoming transmission fiber (West direction) to the Main Chassis ORM
Step 4b Connect the Main Chassis ORM Slot 2 Line Out port to the Expansion Chassis OAM
Step 4c Connect the Expansion Chassis OAM Slot 2 Line Out port to the outgoing transmis-
sion fiber (East direction).
Step 4d Connect the incoming transmission fiber (East direction) to the Main Chassis OAM/
ORM Slot 3 Line In port.
Step 4e Connect the Main Chassis OAM/ORM Slot 3 Line Out port to the outgoing transmis-
sion fiber (West direction).
Step 4f Insert a 10dB optical attenuator at the Main Chassis ORM Slot 2 OSC In port.
Step 4g Connect the Main Chassis ORM Slot 2 OSC Out port to the Main Chassis OAM/ORM
Slot 3 OSC In port.
Step 4h Connect the Main Chassis OAM/ORM Slot 3 OSC Out port to the Main Chassis ORM
Slot 2 OSC In port.
Step 4i Connect the Expansion Chassis OAM Slot 2 OSC Out port to the OSC In port.

Configuring an OTC with BMM2C and

Preamplifier Configuration
CAUTION
and Class 1M.
CAUTION
The BMM2C-16-CH, referred to as BMM2C, is a Gen 2 BMM type used exclusively on the OTC to provide
optical line system support for the DTN-X (XTC-10/XTC-4). The BMM2C requires association with an
OAM/ORM preamplifier. The preamplifier is equipped in slot 2 while the BMM2C can only be equipped in
slot 3 (both in the same OTC). This slot restriction is mechanical due to the physical placement of the fiber
guide on the BMM2C front panel.
Table 16-3 lists the required modules for a BMM2C with a preamplifier configuration.
Table 16-3 OTC with BMM2C and Preamplifier Configuration
Chassis Type Main Module Booster Module Preamplifier Module
OTC BMM2C-16-CH Not supported Any one of the following:

• OAM-CXH1-MS
• OAM-CXH1-MS-B
• OAM-CXH2-MS
• OAM-CXH3-MS
• ORM-CXH1-MS
• ORM-CXH1

initially commissioned as Main Chassis and Expansion Chassis where applicable.
 Main Chassis - DTN-X (XTC-10/XTC-4) turned up as a Multi-chassis network element and
Auto-discovery completed

Page 16-32 Configuring an OTC with BMM2C and Preamplifier Configuration
 Expansion Chassis - OTC turned up as a Multi-chassis network element with an OAM/ORM
preamplifier (in slot 2) and BMM2C (in slot 3) installed and Auto-discovery completed
To turn up an OTC with a BMM2C and OAM/ORM preamplifier configuration
Figure 16-17 shows an example configuration of a BMM2C with an OAM/ORM preamplifier. Note that this
illustration depicts an XTC-10 but applies to the XTC-4 as well.
Figure 16-17 Example Configuration of an OTC with BMM2C and Preamplifier

A-6A/
A-1/B-1 A-2/B-2 A-3/B-3 A-4/B-4 A-5/B-5 B-6B
XTC-10
Line Module
Line Module
TSM
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
IN OUT IN OUT
XCM
A-6B Control
/
B-6A
Main Chassis
Expansion Chassis
OTC
1A 1B
OMM OMM
Line Line
Out OAM/ORM OSC In
In Out Transmission
2 Fiber
Line In
3 OSC Line Note: The OCG port connections
BMM2C In Out
are not shown for clarity.
infn_1047

Step 2 Create the association between the BMM2C and the OAM/ORM.
Step 2a Lock the BMM2C in slot 3. From the Infinera GNM Equipment View, right-click the
BMM2C and select Admin State -> Lock.
Step 2b From the Equipment View, highlight the appropriate BMM2C to be configured, right-
on page 16-34.
Step 2c In the Rx Association panel, click on Rx Associated OTS AID and select the appro-
priate OAM/ORM OTS AID that is connected to the BMM2C Line In (Rx) connector.
Step 2g Unlock the BMM2C in slot 3. From the Infinera GNM Equipment View, right-click the
BMM2C and select Admin State -> Unlock.

Figure 16-18 Setting the BMM2C with an OAM/ORM Preamplifier Association
Span/C-Band tab
Rx Association panel
Rx Associated
OTS AID
Step 3 Verify the association between the BMM2C and the OAM/ORM.
Step 3a From the Equipment View, highlight the appropriate OAM/ORM to be configured,
Step 3b In the Tx Association panel, verify that the BMM2C is listed in the Tx Associated OTS
Eqpt box.

Figure 16-19 Verifying the BMM2C with an OAM/ORM Preamplifier Association
Span/C-Band tab
Tx Association panel
Tx Associated
OTS Eqpt
Step 4 Configure the Optical Supervisory Channel (OSC) on the OAM/ORM associated with the
BMM2C, refer to “Configuring the Optical Supervisory Channel” on page 15-28.
Step 5 Verify the OSC on the OAM/ORM associated with the BMM2C, refer to “Verifying the Optical
Supervisory Channel” on page 15-30.
Step 6 Install clean, labeled, fiber optic cables at the OTC between the Main and Expansion Chassis.
Step 6a Connect the incoming transmission fiber to the OAM/ORM Slot 2 Line In port.
Step 6b Connect the OAM/ORM Slot 2 Line Out port to the BMM2C Slot 3 Line In port.
Step 6c Connect the BMM2C Slot 3 Line Out port to the outgoing transmission fiber.
Step 6d Connect the OAM/ORM Slot 2 OSC Out port to the BMM2C Slot 3 OSC In port.
Step 7 Install clean, labeled, fiber optic cables between the DTN-X line module and the BMM2C, refer
to “To connect OCG cables between XTC line modules and OTC BMM2Cs” on page C-93.

Step 8 Configure the operating mode and the installed OCG number on the DTN-X line module con-
nected to the BMM2C, refer to “Configuring Tunable Line Modules” on page 3-35. The operating
mode on the DTN-X line module must be set to Gen1.
Step 9 Verify that Auto-discovery has completed between the DTN-X line module and the BMM2C, refer
to “Verifying Line Module Auto-discovery Completion” on page 3-38.

Testing OTC Circuit Packs

OTC:
“Testing OMMs” on page 16-37
“Testing OAMs” on page 16-38
“Testing BMM2Cs” on page 16-38
“Testing ORMs” on page 16-39
“Testing SCMs” on page 16-39
“Testing DSEs” on page 16-40
Testing OMMs
Perform the following procedure to test an OMM.
To test an OMM with an equipment failure alarm
Step 1 Examine the LEDs on each OMM on the OTC. The FLT LED is illuminated if an alarm exists. If
an OMM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the OMM from the Equipment View.
Step 4 Select Properties. The OMM Properties window is displayed.

Testing OAMs
Note: The following procedure applies to all OAM types.
Perform the following procedure to test an OAM.
To test an OAM with an equipment failure alarm
Step 1 Examine the LEDs on each OAM on the OTC. The FLT LED is illuminated if an alarm exists. If an
OAM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the OAM from the Equipment View.
Step 4 Select Properties. The OAM Properties window is displayed.
Testing BMM2Cs
Note: The following procedure applies to all BMM2C types.
Perform the following procedure to test a BMM2C.
To test a BMM2C with an equipment failure alarm
Step 1 Examine the LEDs on each BMM2C on the OTC. The FLT LED is illuminated if an alarm exists. If
a BMM2C has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the BMM2C from the Equipment View.

Testing ORMs
Note: The following procedure applies to all ORM types.
Perform the following procedure to test an ORM.
To test an ORM with an equipment failure alarm
Step 1 Examine the LEDs on each ORM on the OTC. The FLT LED is illuminated if an alarm exists. If
an ORM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the ORM from the Equipment View.
Step 4 Select Properties. The ORM Properties window is displayed.
Testing SCMs
Note: The following procedure applies to all SCM types.
Perform the following procedure to test an SCM.
To test an SCM with an equipment failure alarm
Step 1 Examine the LEDs on each SCM on the OTC. The FLT LED is illuminated if an alarm exists. If
an SCM has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the SCM from the Equipment View.
Step 4 Select Properties. The SCM Properties window is displayed.

Testing DSEs
Note: The following procedure applies to all DSE types.
Perform the following procedure to test a DSE.
To test a DSE with an equipment failure alarm
Step 1 Examine the LEDs on each DSE on the OTC. The FLT LED is illuminated if an alarm exists. If a
DSE has an alarm, view the Alarm Manager to verify the type of alarm.
state, right-click the DSE from the Equipment View.
Step 4 Select Properties. The DSE Properties window is displayed.


the OTC.

Alarm Filter panel

Table 16-4 lists alarms that may occur upon turning up an OTC. These alarms do not require any
corrective action.
Table 16-4 Expected OTC Alarms
Alarm Type Cause

(OLOS) 2. Fibers are connected but they do not
have light.


Environmental alarms are those triggered by an abnormal condition at the OTC site. The OTCs support
to connect external equipment (reactors), such as fire, alarm detector, high temperature detector, door
open and so on to the OTC. When the connected equipment triggers an input contact point, it raises an
alarm with an alarm message and severity as configured by the user. Alarm output contacts allow users to
connect external equipment to the OTC.
The OTC can trigger the operation of the connected external equipment. The maximum threshold is

The OTC supports sixteen user-configurable alarm input contacts. Users can configure these input
Table 16-5 specifies the OTC alarm input contact pin-outs. One alarm contact is pre-defined in the system
and the remaining nineteen contacts can be customized by the users.
Note: Input contacts 17, 18, and 19 are not supported on the OTC.
Row Column


4 I Reserved for Alarm cut-off a Predefined
4 J Reserved for Alarm cut-offa Predefined
a. ACO can be enabled using the input contact pins in addition to the ACO push button and the Infinera GNM user interface.

select Alarm Input Contacts. The Alarm Input Contacts Properties window is displayed.
Step 2 Select the input alarm contact that you want to configure in the input alarm contact table. The
Step 5 When you are done, click Close to exit the Alarm Input Contact Properties window.


The OTC supports ten user-configurable alarm output contacts. Each output has NO (normally open), NC
(normally closed) and CM (common) contacts. Under normal condition, the NO output is open and the NC
output is closed. When the output contact is enabled, the NO output is closed and the NC output is opened.
Users can enable or disable (normal condition) the output contacts either manually or automatically on
occurrence of user-defined alarm condition.
Table 16-6 specifies the OTC alarm output contact pinouts. Ten alarm contacts are pre-defined in the
system and the remaining ten contacts can be customized by the users.
Row Column
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
1 W Power Fault Bay Alarm, Predefined
COMMON

1 X Power Fault Bay Alarm, Predefined

NORMALLY OPENa
1 Y Power Fault Bay Alarm, Predefined
NORMALLY CLOSEDa
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED


COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN


NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED
COMMON
NORMALLY OPEN
NORMALLY CLOSED

Figure 16-23 Configure Alarm Output Contact
Step 2 Select the alarm contact you want to edit in the Alarm Output Contact table.
Step 5 When you are done, click Close to exit the Alarm Output Contact Properties window.
Alarm Cutoff (ACO)

The OTC provides a feature to acknowledge an alarm condition and turn off the audible indicator. The ACO
push button is used to mute the current audible alarms and is located on the chassis or can be operated
remotely through the Infinera GNM interface. When the ACO is enabled, all the outstanding audio alarms
are turned off and the ACO LED on the chassis is illuminated. The ACO LED indicates that one or more
audible alarms are present, but the audible indicators have been suppressed. The ACO LED is turned off
when the silenced audible is cleared. The alarm acknowledgment by the user does not change the ACO
LED state.
To enable an ACO
Step 1 From the Equipment View, right-click just below the title bar (next to the Fan images).

Testing an ACO
to be audible.
After you have enabled an ACO, you must test it.
To test an ACO
Step 1 Create an alarm on the chassis (for example, loss of signal on an OAM).
Step 2 Press the ACO push button on the chassis or remotely through the Infinera GNM interface.
Step 3 Validate the procedure by verifying the following:
The FAULT LED should be ON (steady Red or Yellow)
Step 4 Clear the alarm. The Fault and ACO alarms should be OFF. The ACO has been successfully
tested.


CHAPTER 17
Turning up a Multi-chassis Network

Element with Raman Amplification
(OTC based)
This chapter provides the procedures to turn up and test an OTC based multi-chassis network element
configured with Raman modules. (For an MTC-9 based multi-chassis network element, refer to “Turning up
a Multi-chassis Network Element with Raman Amplification (MTC-9 based)” on page 18-1.)
“Raman Turn-up and Test Overview” on page 17-4
“RAM-1 Turn-up and Test” on page 17-22
“RAM-2-OR Turn-up and Test” on page 17-32
“REM-2 Turn-up and Test” on page 17-41
“ORM Turn-up and Test” on page 17-57
“Setting the Point Loss Offset for Raman Modules” on page 17-62
“Setting the Point Loss Offset for ORM Modules” on page 17-77
“Setting the Target Gain Offset” on page 17-87

Page 17-2
Note: Figure 17-1 shows one example of an OTC configured with Raman modules. The OTC
Expansion Chassis may also house other modules (for other types of configurations) such
as OAMs, ORMs, SCMs and/or DSEs. Refer to “General Guidelines” on page 17-6 for
restrictions regarding Raman module configurations.

Turning up a Multi-chassis Network Element with Raman Amplification (OTC based) Page 17-3
Tasks
table to keep track of the tasks you have completed and to record test results.
Table 17-1 Raman Turn-up Checklist and Test Results
“Raman Turn-up and Test Overview“ page

17-4
17-6
“Tools, Test Equipment, and Fiber page
Cleaning Supplies“ 17-8
“Fiber Plant Preparation“ page
17-8
“Minimum Equipment Configuration“ page
17-9
“Initial Commissioning of Network Ele- page
ments“ 17-9
“Connecting DCM/DSEs“ page
17-9
“RAM-1 Turn-up and Test“ page
17-22
“RAM-2-OR Turn-up and Test“ page
17-32
“REM-2 Turn-up and Test“ page
17-41
“ORM Turn-up and Test“ page
17-57
“Setting the Point Loss Offset for page
Raman Modules“ 17-62
“Setting the Point Loss Offset for page
ORM Modules“ 17-77
“Setting the Target Gain Offset“ page
17-87

Page 17-4 Raman Turn-up and Test Overview
Raman Turn-up and Test Overview

CAUTION
and Class 1M.
CAUTION
Do not manually disable Automatic Laser Shutdown (ALS) unless specifically instructed to
do so. Disabling ALS may endanger personnel and/or equipment.
CAUTION
CAUTION
ing” on page D-1.
Figure 17-2 on page 17-5, Figure 17-3 on page 17-5, and Figure 17-4 on page 17-6 illustrate at a high
level the turn up order that must be followed during Raman turn-up and test.
These figures also show the Optical Transport Section (OTS) signal flow and the direction of Raman
amplification within the DTN/DTN-X network.

Figure 17-2 Raman Turn-up Order using RAM-1 Modules

Node A Amp 1 through n Node Z
1 2
OAM
RAM-1
RAM-1
RAM-1
RAM-1
BMM
BMM
OAM
4 3
Turn up the Raman modules in order beginning with the Raman module 1 that amplifies the span originating
from the BMM in the source node (Node A ).
Proceed across the network in the same direction to the farthest end node 2 (all Amps and Node Z ).
Then turn up the return direction beginning with the Raman module 3 that amplifies the span originating from
the BMM (Node Z ) working all the way back through the amplifier sites to Node A. 4
OTS Signal Flow Direction
Amplifier Pump Direction infn_148
Figure 17-3 Raman Turn-up Order using RAM-2-OR Modules

Node A Amp 1 through n Node Z
1 2
OAM
RAM-2-OR
RAM-2-OR
RAM-2-OR
RAM-2-OR
BMM
BMM
OAM
4 3
Turn up the Raman modules in order beginning with the Raman module 1 that amplifies the span originating
from the BMM in the source node (Node A ).
Proceed across the network in the same direction to the farthest end node 2 (all Amps and Node Z ).
Then turn up the return direction beginning with the Raman module 3 that amplifies the span originating from
the BMM (Node Z ) working all the way back through the amplifier sites to Node A. 4

Figure 17-4 Raman Turn-up Order using RAM-2-OR and REM-2 Modules
Node A Node B
1 2
REM-2
RAM-2-OR
RAM-2-OR
BMM
BMM
REM-2
4 3
Turn up the Raman modules in order beginning with the Raman module 1 that amplifies the span
originating from the BMM in the source node (Node A ).
Proceed across the network in the same direction to the farthest end node 2 (Node B ).
Then turn up the return direction beginning with the Raman module 3 that amplifies the span
originating from the BMM (Node B ) working all the way back to the source node (Node A ) 4

General Guidelines
Note: Unless specifically noted otherwise, all references to the RAM will refer to either the RAM-1,
RAM-2-OR, or REM-2 interchangeably.
The following hardware equipment is required to provide Raman amplification in both directions:
 Two OTCs
 Two OMMs
 Two RAMs or two ORMs

Configuration Guidelines
 Optical Transport Chassis (OTCs) configured as a Main Chassis can house OMMs, OAMs, and/or
Optical Raman Modules (ORMs) only. Supported configurations are described as follows:
Two OAMs can be provisioned in the same OTC
Two ORMs can be provisioned in the same OTC
One OAM and one ORM can be provisioned in the same OTC
 OTCs configured as an Expansion Chassis can house OMMs, RAMs, and/or Dynamic Spectrum
Equalizers (DSEs) only. Supported configurations are described as follows:
Two RAM-1s can be provisioned in the same OTC
One RAM-1 and one RAM-2-OR can be provisioned in the same OTC
Two RAM-2-ORs can be provisioned in the same OTC
One RAM-2-OR and one REM-2 can be provisioned in the same OTC
Two DSEs can be provisioned in the same OTC
One DSE and one RAM-1 or RAM-2-OR module can be provisioned in the same OTC
RAM-1 and REM-2 modules cannot be provisioned in the same OTC. An Equipment Mismatch
alarm will be reported by the management interfaces for the second (RAM-1 or REM-2) module
that is installed
Two REM-2 modules cannot be provisioned in the same OTC. An Equipment Mismatch alarm
will be reported by the management interfaces for the second REM-2 module that is installed
DSE and REM-2 modules cannot be provisioned in the same OTC. An Equipment Mismatch
alarm will be reported by the management interfaces for the second module that is installed
The following Dispersion Compensation Modules (DCMs) may be required to support specific Raman
applications:
 DCM2H-3000N—for festoon applications (extra long, single span). This DCM is channelized at 100
GHz channel spacing and therefore only supports up to 40 channels located in OCGs 1, 3, 5, and/or
7
 DCM2H-4000N—for festoon applications (extra long, single span). This DCM is channelized at 100
GHz channel spacing and therefore only supports up to 40 channels located in OCGs 1, 3, 5, and/or
7
 DCM1F-1700N-LL—for ultra long-haul applications
 DCM1F-1900N-LL—for ultra long-haul applications
Note: The DCM1F-1700N-LL/DCM1F-1900N-LL DCMs provide the same dispersion characteris-

tics as the DCM1F-1700N-A/ DCM1F-1900N-A DCMs but support a maximum loss of
<8.5dB through the DCM.

Tools, Test Equipment, and Fiber Cleaning Supplies

Ensure that you have the necessary tools, test equipment, and fiber cleaning supplies as outlined in
“Required Tools and Test Equipment” on page 2-5.
Fiber Plant Preparation

Ensure that the fiber plant does not have excessive point losses particularly in the first few kilometers of
fiber connected to the RAM-1/RAM-2-OR Line In port and the REM-2 Line Out port.
Proper operation is not specified for higher point losses. High point losses, especially in the form of dirty
fiber connectors, may lead to permanent damage of the fiber connectors, fibers, and/or the Raman
modules. Point losses often manifest themselves through dirty fiber connectors, poor patch panel
connections, and high splice losses.
Infinera recommends that the number of fiber connections between the Raman modules and the
transmission fiber be kept to a minimum. When possible, a direct fiber connection from the Raman
modules to the outside plant fiber is preferred. Care should also be taken to minimize bend losses and
stress in the fiber plant between the Raman modules and the outside fiber plant (the Infinera specification
for minimum fiber bend radius is 25mm).
Note: Infinera strongly recommends the use of bend insensitive fiber (BIF) for all fiber connections
(whenever possible). BIF cables provide greater resistance to bending losses due to
excessive bends in the fiber cables (compared to non-BIF cables), and are identified by a
Blue cable jacket. Contact your Infinera account team and/or an Infinera TAC resource for
additional information.
Note: Operating the system with point losses above 0.5dB is not recommended and the link per-
formance is not guaranteed. Refer to “Raman Maximum Point Loss” on page 17-21 which
provides information regarding the maximum point loss accommodated for the different
Raman modules based on fiber type.
Ensure that all connectors between the Raman modules and the actual line fibers are cleaned, inspected,
and properly connected throughout all involved patch panels. Refer to “Raman Fiber Connector Cleaning”
on page D-1.


Before proceeding with the turn-up and test of Raman modules, ensure that all nodes involved in the
configuration have been initially commissioned as Main Chassis and Expansion Chassis where applicable.
Initial Commissioning of Network Elements

 Node A - DTC/MTC turned up as a Multi-chassis network element. Refer to “Turning up a DTC/MTC
as an Expansion Chassis” on page 13-1
Main Chassis (DTC/MTC) with one BMM installed, one line module (DLM/XLM/ADLM/AXLM)
installed, and Auto-discovery completed
Expansion Chassis (OTC)
 Node B - OTC turned up as a Multi-chassis network element. Refer to “Turning up an OTC as an
Expansion Chassis” on page 16-1
Main Chassis (OTC) with two OAMs installed (or two ORMs depending on configuration)
Expansion Chassis (OTC)
 Node C - DTC/MTC turned up as a DTN. Refer to “Turning up a DTN as a GNE” on page 11-1
Main Chassis (DTC/MTC) with one BMM installed, one line module (DLM/XLM/ADLM/AXLM)
installed, and Auto-discovery completed
Connecting DCM/DSEs
Refer to the Infinera DTN and DTN-X Hardware Description Guide for detailed information regarding the
supported DCM/DSE types.
Refer to the Infinera DTN and DTN-X Site Preparation and Hardware Installation Guide for installing and
fibering DCM/DSEs which are required for specific Raman applications.

External Indicators and Connectors

The RAM/ORM faceplates provide the circuit pack status/port LED indicators, and line/port connectors as
follows:
 RAM-1 as shown in Figure 17-5
 RAM-2-OR as shown in Figure 17-6 on page 17-11
 REM-2 as shown in Figure 17-7 on page 17-12
 ORM-CXH1-MS as shown in Figure 17-8 on page 17-13

 ORM-CXH1 as shown in Figure 17-9 on page 17-14
Figure 17-5 RAM-1 Faceplate

Circuit Pack
Status LEDs
BMM/OAM Port LEDs Line Port LEDs
Ejector FLT, ACT, PWR Ejector
LOS ACT LOS ACT
INVISIBLE LASER
RADIATION
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
1426 - 1610nm - 1mW
REMOVABLE CONNECTOR
INTERNAL CLEANING REQUIRED
Warning Label
BMM/OAM INVISIBLE LASER
Line RADIATION Fiber Guide
Connectors High Power Connector Connectors DO NOT VIEW
(Removable for Cleaning)
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
1426 - 1610nm - 1mW infn_036

Figure 17-6 RAM-2-OR Faceplate

Circuit Pack
Status LEDs
BMM/OAM Port LEDs Line Port LEDs
Ejector FLT, ACT, PWR Ejector
LOS ACT LOS ACT
INVISIBLE LASER
RADIATION
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
1426 - 1610nm - 1mW
REMOVABLE CONNECTOR
Warning Label
BMM/OAM INVISIBLE LASER
Connectors Line RADIATION Fiber Guide
High Power Connector Connectors DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
1426 - 1610nm - 1mW infn_037

Figure 17-7 REM-2 Faceplate

Line Line Port Circuit Pack
Port LED LED Status LEDs
Ejector Ejector
LOS ACT FLT, ACT, PWR
INVISIBLE LASER
RADIATION
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
1426 - 1610nm - 1mW
REMOVABLE CONNECTOR
Warning Label
INVISIBLE LASER
RAM-2-OR Line RADIATION Fiber Guide
Connector Connector DO NOT VIEW
High Power Connector DIRECTLY WITH
(Removable for Cleaning) OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
1426 - 1610nm - 1mW infn_038

Figure 17-8 ORM-CXH1-MS Faceplate
OSA Monitor DCM Connectors

Connectors
for Line Input OSC Port Line Circuit Pack
and Output Connectors Connectors Status LEDs
FLT, ACT, PWR

OSA MONITOR
ORM-CXH1-MS
S/N
CLEI
INVISIBLE LASER
RADIATION
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT (IEC)
CLASS I LASER
PRODUCT (CDRH)
1550nm-50mW
REMOVABLE CONNECTOR
Warning Label
LOS ACT
Ejector LOS INVISIBLE LASER Fiber Ejector
OSC Port LED Port LEDs RADIATION Guide
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT (IEC)
CLASS I LASER
PRODUCT (CDRH)
1550nm-50mW infn_204

Figure 17-9 ORM-CXH1 Faceplate
OSC Port Line Circuit Pack

Ejector Connectors Connectors Status LEDs
FLT, ACT, PWR

L-BAND
L-BAND PUMP ORM-CXH1 S/N
CLEI
INVISIBLE LASER
RADIATION
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
REMOVABLE CONNECTOR 1425-1620nm
10mW
OSA MONITOR
Warning Label
LOS ACT
OSA Monitor LOS INVISIBLE LASER Fiber Ejector
Connectors OSC Port LED Port LEDs RADIATION Guide
DO NOT VIEW
for Line Input DIRECTLY WITH
and Output OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
1425-1620nm
10mW infn_470

Raman Connector to Software Association

During Raman module turn up, it will be necessary to manually associate the following in the system
software using Infinera GNM:
 RAM-1/RAM-2-OR OTS connector ports with the correct BMM/OAM OTS ports
 REM-2 OTS connector port with the correct RAM-2-OR OTS port
Table 17-2 and Table 17-3 show the association between the RAM-1/RAM-2-OR/REM-2 connector ports
and the system software.
Table 17-2 RAM-1/RAM-2-OR Connector to Software

Association
Connector
(Module Faceplate Label) Software Object Model
BMM/OAM IN L2 Rx
BMM/OAM OUT L1 Tx
LINE IN L1 Rx
LINE OUT L2 Tx
Note: Manual association is required only for the BMM/OAM IN and BMM/OAM OUT connectors.
Table 17-3 REM-2 Connector to Software Association
Connector
(Module Faceplate Label) Software Object Model
RAM-2-OR IN L1 Rx
LINE OUT L1 Tx
Note: Manual association is required only for the RAM-2-OR IN connector.

Raman Gain for RAM-1/RAM-2-OR/REM-2

Table 17-4 lists the amount of gain provided by the different Raman modules based on fiber type.
Table 17-4 RAM Maximum Gain
Tx and Rx
RAM Type Fiber Type Default Gain (dB) Losses (dB) Net Gain (dB)
RAM-1 SMF-28, LEAF, ELEAF, 10.0 1.7 to 3.4 6.6 to 8.3

TW-C, TW-RS, TW-Plus,
LS, DSF
PSCF 9.0 1.7 to 3.4 5.6 to 7.3
RAM-2-OR SMF-28, LEAF, ELEAF, 18.0 1.9 to 3.8 14.2 to 16.1
TW-C, TW-RS, TW-Plus,
LS, DSF, PSCF
REM-2 SMF-28, PSCF 13.0 0.2 to 0.8 12.2 to 12.8
(20 channels)
REM-2 SMF-28, PSCF 11.0 0.2 to 0.8 10.2 to 10.8
(40 channels)
REM-2 SMF-28, PSCF 8.5 0.2 to 0.8 7.7 to 8.3
(80 channels)
REM-2 SMF-28, PSCF 8.5 0.2 to 0.8 7.7 to 8.3
(160 channels)
Raman/EDFA Gain and Span Loss Support for ORM

Table 17-5 lists the amount of Raman and EDFA gain provided by the ORM and the supported span loss
range based on fiber type.
Table 17-5 ORM Maximum Gain and Span Loss Support
ORM Type Fiber Type Raman Gain EDFA Gain Total ORM Span Loss
(dB) (dB) Gain Range Range
(dB) (dB)
ORM-CXH1-MS SMF-28, PSCF 5.0 to 11.0 11.0 to 14.0 16.0 to 25.0 16.0 to 25.0
LEAF 5.0 to 14.0 11.0 to 14.0 16.0 to 28.0 16.0 to 28.0
TW-C, TW-RS, 7.0 to 16.0 11.0 to 14.0 18.0 to 30.0 18.0 to 30.0
LS, DSF
ORM-CXH1 SMF-28, PSCF 5.0 to 11.0 11.0 to 16.0 16.0 to 27.0 16.0 to 27.0
LEAF 5.0 to 14.0 11.0 to 16.0 16.0 to 30.0 16.0 to 30.0
TW-C, TW-RS, 7.0 to 16.0 11.0 to 16.0 18.0 to 32.0 18.0 to 32.0
LS, DSF

ORM Maximum Raman Gain vs. Point Loss Offset

ORM Raman gain range is dependent on the point loss offset (PLO) value. The PLO is applied to an ORM
to accommodate for point losses sustained within the fiber plant (for example connector losses and/or
patch cable losses). ORM maximum Raman gain is supported only if the PLO is less than 0.5dB as
recommended by Infinera. Operating the system with point losses above 0.5dB is not recommended and
the link performance is not guaranteed.
Long-term damage can arise from dirty or improper fiber connections. Proceed with above 0.5dB point
losses only if one is certain that the fiber connectors are clean, the connections are of good quality, and the
patch cords and fiber span do not have abnormal high loss or reflection.
Figure 17-10 illustrates the relationship between ORM-CXH1-MS maximum Raman gain and point loss
offset based on deployed fiber type.
Figure 17-11 on page 17-18 illustrates the relationship between ORM-CXH1 maximum Raman gain and
point loss offset based on deployed fiber type.
Figure 17-10 ORM-CXH1-MS Maximum Raman Gain vs. Point Loss Offset
18
16
SMF
14
LEAF
12
TWC
10
TWRS
Gain (dB)
8 PSC
6 DS
4 LS
2
-1 0 1 2 3 4
Point Loss Offset (dB) infn_462

Figure 17-11 ORM-CXH1 Maximum Raman Gain vs. Point Loss Offset
18
16
SMF
14 LEAF
12 TWC
TWRS
10
Max Raman PSC
Gain (dB)
8
DS
6 LS
2
-1 -0.5 0 0.5 1 1.5 2 2.5 3 3.5
Point Loss Offset (dB) infn_600

Raman Target Gain Offset

The target gain offset is user-configurable and applied to a Raman module to adjust the effective Raman
gain from the default gain set point. Under most conditions, the target gain offset does not require
adjustment and should be left at the default value (0.0dB). However, for certain configurations the target
gain offset may require an adjustment to help close a particular span. Note that parameters such as
Raman ASE power level and span loss take into consideration the target gain offset when calculating
these types of parameters.
The allowable range for the target gain offset value is +/-2.0dB from the default gain set point based on
fiber type and Raman module deployed. In some cases the maximum target gain offset is limited by
available Raman pump power.
Table 17-6 lists the target gain offset range for RAM-1s based on fiber type.
Table 17-6 RAM-1 Target Gain Offset
Target Gain Offset Range (dB)a
Fiber Type Default Gain (dB) Minimum Maximum
SMF-28 10.0 -2.0 1.3

LEAF 10.0 -2.0 2.0
TW-RS 10.0 -2.0 2.0
DSF 10.0 -2.0 2.0
LS 10.0 -2.0 2.0
PSC 9.0 -2.0 1.8
a. The target gain offset values listed assume signal power is 0dBm/ch.
Note: The target gain offset value is set to 0.0dB by default. Do not configure the target gain offset
unless consulted to do so by an Infinera Technical Assistance Center (TAC) resource.

Table 17-7 lists the target gain offset range for RAM-2-ORs based on fiber type.
Table 17-7 RAM-2-OR Target Gain Offset
Fiber Type Default Gain (dB) Minimum Maximum
SMF-28 18.0 -2.0 2.0

LEAF 18.0 -2.0 2.0
TW-RS 18.0 -2.0 2.0
DSF 18.0 -2.0 2.0
LS 18.0 -2.0 2.0
PSC 18.0 -2.0 2.0
unless consulted to do so by an Infinera TAC resource.
Table 17-8 lists the target gain offset range for REM-2s based on fiber type and number of channels.
Table 17-8 REM-2 Target Gain Offset

Channel
Fiber Type Loading Default Gain (dB) Minimum Maximum
SMF-28 20 13.0 -2.0 1.0

40 11.0 -2.0 0.5
80 8.5 -2.0 1.0
160 8.5 -2.0 1.0
PSC 20 13.0 -2.0 1.0
40 11.0 -2.0 0.0
80 8.5 -2.0 0.6
160 8.5 -2.0 0.6
unless consulted to do so by an Infinera TAC resource.

Raman Maximum Point Loss

Table 17-9 lists the maximum point loss accommodated for RAM-1s based on fiber type.
Table 17-9 RAM-1 Maximum Point Loss
Maximum Point
Fiber Type Default Gain (dB) Loss (dB)
SMF-28 10.0 0.5

LEAF 1.1
TW-RS 1.7
DSF 2.6
LS 2.5
PSC 9.0 0.6
Table 17-10 lists the maximum point loss accommodated for RAM-2-ORs based on fiber type.
Table 17-10 RAM-2-OR Maximum Point Loss
Maximum Point
Fiber Type Default Gain (dB) Loss (dB)
SMF-28 18.0 0.9

LEAF 1.9
TW-RS 2.2
DSF 3.3
LS 3.0
PSC 0.8
Table 17-11 lists the maximum point loss accommodated for REM-2s based on fiber type.
Table 17-11 REM-2 Maximum Point Loss
REM-2 (Signal Power 0dBm/ch)
Maximum
Maximum Maximum Point Loss
Point Loss Point Loss 80/160
Default Gain 20 Channels Default Gain 40 Channels Default Gain Channels
Fiber Type (dB) (dB) (dB) (dB) (dB) (dB)
SMF-28 13.0 1.3 11.0 1.6 8.5 2.8

PSC 1.2 1.5 2.7

Page 17-22 RAM-1 Turn-up and Test
RAM-1 Turn-up and Test

This procedure is used to turn up and test a multi-chassis network element configured with RAM-1
modules, see Figure 17-12. It provides information to turn up a single link with only one Raman amplified
span.
When turning up a link with multiple Raman spans, repeat this procedure for each Raman span. Turn up
Raman amplification completely for one direction at a time. In each direction start turning up Raman
amplification in the span closest to the transmitting node and work your way down the link to the receiving
node.
Figure 17-12 Raman Deployment using RAM-1 Modules

DTC/ DTC/
MTC 1 MTC 1
OTC
BMM
Line In Line In
Line In 2 Line Out
OAM
Line 3 OAM
Out
BMM
Line Line In Line

Out Main Chassis Out
Main Chassis Main Chassis
OTC BMM/ OTC BMM/

OAM OAM
Line In L1 Tx Out Line In L1 Tx Out
2 RAM-1 2 RAM-1
Line L2 Rx BMM/OAM Line L2 Rx BMM/OAM
Out BLANK In Out 3 BLANK In
3
Expansion Chassis Expansion Chassis Manually

Associated
Automatically
Associated
infn_129aa
Note: In order for Infinera's Automated Gain Control (AGC), Automatic Laser Shutdown (ALS),
and point loss offset (PLO) calculation to perform as designed, ensure that the correct fiber
connections and manual associations (as shown in Figure 17-12) are made while perform-
ing this procedure. Prior to link turn-up and test, ensure that the fiber connectors used in
the configuration are checked for cleanliness prior to use, and the correct fiber provision-
ing steps have been performed as specified in this procedure.

To turn up a RAM-1 configuration
Note: Ensure that all assumptions and prerequisites are fully understood and met as outlined in
“General Guidelines” on page 17-6. This procedure assumes that all nodes have been ini-
tially commissioned as outlined in “Minimum Equipment Configuration” on page 17-9.
Step 1 Launch Infinera GNM and establish GNM connectivity with Node A, B, and C. Refer to “Launch-
ing Infinera GNM” on page 11-29.
Step 2 At Node A: lock the BMM in slot 1 using Infinera GNM.

Step 2a From the Infinera GNM Equipment View, right-click the BMM/OAM and select Admin
State -> Lock.
Step 3 At Node B: repeat Step 2 and lock the OAMs in slots 2 and 3.
Step 4 At Node C: repeat Step 2 and lock the BMM in slot 1.
Step 5 At Node A: pre-provision a RAM-1 in slot 2 and lock it using Infinera GNM.
Step 5a From the Equipment View, right-click on slot 2 and select Pre-provision -> Raman -
> RAM-1.
Step 5b From the Equipment View, right-click the RAM-1 and select Admin State -> Lock.
Step 6 At Node B: repeat Step 5 to pre-provision a RAM-1 in slot 2 and lock it.
Step 7 At Node A: set the associated OTSPTP values manually on the RAM-1 connector ports (L1
Transmit and L2 Receive) to associate them with the correct BMM OTS port as listed in
Table 17-2 on page 17-15 and Table 17-3 on page 17-15 using Infinera GNM. Figure 17-12 on
page 17-22 provides details regarding which ports require manual association.
Step 7a From the Equipment View, highlight the appropriate RAM-1 to be configured, right-
on page 17-24.
Step 7b In the list frame, ensure that L1 OTS ID is highlighted. See Figure 17-13 on page 17-
24.
Step 7c From the tabs listed in the middle of the window, select the Span/C-Band tab.
Step 7d In the BMM/OAM Association panel, click on Tx Associated OTS and select the
OTS AID that is connected to the RAM-1 L1 Tx (To BMM/OAM) connector.
Step 7e Click Apply.
Step 7f In the list frame, ensure that L2 OTS ID is highlighted. See Figure 17-14 on page 17-
25.
Step 7g From the tabs listed in the middle of the window, select the Span/C-Band tab.

Step 7h In the Peer OTS Association panel, click on Rx Associated OTS and select the
OTS AID that is connected to the RAM-1 L2 RX (BMM/OAM In) connector.
Step 7i Click Apply.
Step 7j Click Close.
Figure 17-13 Setting the RAM-1 L1 Association
Span/C-Band tab
Tx Associated OTS

Figure 17-14 Setting the RAM-1 L2 Association
Span/C-Band tab
Rx Associated OTS
Step 8 At Node B: repeat Step 7 to set the associated OTSPTP values manually on the RAM-1 connec-
tor ports (L1 Transmit and L2 Receive) to associate them with the correct OAM OTS port.
Step 9 At Node A: provision the fiber type for the BMM. Refer to “Provisioning Fiber Information” on
page 11-87.
Step 10 At Node B: provision the fiber type for the OAMs. Refer to “Entering DCM/PSE/DSE Information”
on page 16-24.
Step 11 At Node A: verify the RAM-1 L1 and L2 association on the BMM using Infinera GNM.
Step 11a From the Equipment View, highlight the appropriate configured BMM, right-click and
select Span. The Span Properties window is displayed. See Figure 17-15 on
page 17-26.

Figure 17-15 Verifying the RAM-1 L1 and L2 Association
Span/C-Band tab

Step 12 At Node B: repeat Step 11 to verify the RAM-1 L1 and L2 association on the configured OAMs.
Step 13 At Node B and C: label the fibers which will be used for the BMM/OAM side connectors and line
side connectors. Check the fiber connectors for cleanliness, refer to “Raman Fiber Connector
Cleaning” on page D-1 and connect line side fibers between Node B OTC and Node C DTC/
MTC.
Step 13a From OAM slot 2 LINE OUT (Tx) to BMM slot 1 LINE IN (Rx).
Step 13b From BMM slot 1 LINE OUT (Tx) to OAM slot 3 LINE IN (Rx).
Step 14 At Node A: insert a RAM-1 partially into the OTC.
Step 14a Remove the RAM-1 from the ESD protected bag.
Step 14b Reposition the ejectors on the RAM-1 to the full open position (perpendicular).
Step 14c Holding the RAM-1 in one hand and while guiding it with your other hand, align it to
the rail guides in slots 2 and/or 3 on the OTC with the product label at the bottom
side. In this orientation, the front panel of the RAM-1 is right reading.
Step 14d Slide the RAM-1 in partially; ensure that the RAM-1 is not fully seated against the
backplane (the RAM-1 must remain powered off).

Step 15 At Node A: label the fibers and check the fiber connectors for cleanliness, refer to “Raman Fiber
Connector Cleaning” on page D-1. Connect fibers between DTC/MTC and OTC.
Step 15a From RAM-1 slot 2 BMM/OAM OUT (L1 Tx) to BMM slot 1 OTS IN (Rx).
Step 15b From BMM slot 1 OTS OUT (Tx) to RAM-1 slot 2 BMM/OAM IN (L2 Rx).
Connector Cleaning” on page D-1. Connect LINE side fibers for RAM-1. For example, RAM-1
LINE IN (L1 Rx) and RAM-1 LINE OUT (L2 Tx).
Note: A minimum of 50kms of fiber is required for connecting the Raman line side.
Step 17 At Node A: complete the RAM-1 installation.

Step 17a Gently push the RAM-1 toward the backplane until it stops.
Step 17b Close the left side and right side ejectors simultaneously.
Step 17c Lock the ejectors by turning the ejector screw 1/4 turn using a #1 Phillips screw-
driver.
Step 17d Verify that the RAM-1 powers up; wait 5 minutes before proceeding.
Step 18 At Node B: repeat Step 14 to insert a RAM-1 partially into the OTC.
Step 19 At Node B: label the fibers which will be used for the BMM/OAM side connectors and line side
connectors.
Step 20 At Node B: check the fiber connectors for cleanliness, refer to “Raman Fiber Connector Clean-
ing” on page D-1. Connect fibers between OTCs.
Step 20a From RAM-1 slot 2 BMM/OAM OUT (L1 Tx) to OAM slot 2 OTS IN (Rx).
Step 20b From OAM slot 3 OTS OUT (Tx) to RAM-1 slot 2 BMM/OAM IN (L2 Rx).
ing” on page D-1. Connect LINE side fibers for RAM-1. For example, RAM-1 LINE IN (L1 Rx)
and RAM-1 LINE OUT (L2 Tx).
Step 22 At Node B: repeat Step 17 to complete the RAM-1 installation.

Step 23 At Node A: verify that the OSCT power is received on the RAM-1 from the BMM to which it is
connected using Infinera GNM.
click and select Transparent OSC. The OSCTCTP Properties window is displayed.
See
Figure 17-16.
Step 23b In the list frame, ensure that O2 OSCT ID is highlighted.
Step 23c From the tabs listed in the middle of the window, select the Real-Time PM tab.
Step 23d Verify the optical power values.
Figure 17-16 Verifying the OSCT Power for RAM-1
List frame (O2 selected)
Real-Time PM tab
Optical power values
Step 24 At Node B: repeat Step 23 to verify that the OSCT power is received on the RAM-1 from the
OAM to which it is connected.
Step 25 At Node A: verify the ALS Pilot Signal State indicates normal using Infinera GNM.
on page 17-29.
Step 25b In the list frame, ensure that L1 OTS ID is highlighted.

Step 25d In the ALS Pilot Signal panel, verify that the ALS Pilot Signal State is set to Normal.
Figure 17-17 Verifying the ALS Pilot Signal
Span/C-Band tab
ALS Pilot Signal State
Step 26 At Node B: repeat Step 25 to verify the ALS Pilot Signal State (should be Normal).
Step 27 At Node A and B: unlock the RAM-1 using Infinera GNM.
Step 27a From the Equipment View, right-click the RAM-1 and select Admin State -> Unlock.
lize.
Step 28 At Node A: unlock the BMM in slot 1 using Infinera GNM.
Step 28a From the Equipment View, right-click the BMM/OAM and select Admin State ->
Unlock.
Step 29 At Node B and C: repeat Step 28 for all BMM/OAMs.

Step 30 At Node A and B: check that the correct fiber type is transferred to all the Raman modules.

Step 31 At Node A: initiate the Raman point loss offset (PLO) adjustment utility, see “Setting the Point
Loss Offset for Raman Modules” on page 17-62.
Note: Refer to Table 17-9 on page 17-21 for allowable maximum point loss range for RAM-1s
based on fiber type.
Optional: A Target Gain Offset can be applied to a RAM-1 to adjust the effective Raman gain
from its default gain set point. Under most conditions, this setting should remain at default
(0.0dB). To set the Target Gain Offset for the RAM-1 using Infinera GNM, see “Setting the Tar-
get Gain Offset” on page 17-87.
Step 32 At Node B: repeat Step 31.

Page 17-32 RAM-2-OR Turn-up and Test
RAM-2-OR Turn-up and Test

This procedure is used to turn up and test a multi-chassis network element configured with RAM-2-OR
modules, see Figure 17-18. It provides information to turn up one link with only one Raman amplified span.
When turning up a link with multiple Raman spans, repeat this procedure for each Raman span. Turn up
Raman amplification completely for one direction at a time. In each direction start turning up Raman
amplification closest to the transmitting node and work your way down the link.
Figure 17-18 Raman Deployment using RAM-2-OR Modules

DTC/
DTC/
MTC 1
OTC MTC 1
BMM
Line In Line In Line Out Line In
2 OAM
Line 3 OAM
BMM
Out Line Line In Line

Out Main Chassis Out
Main Chassis
Main Chassis
OTC BMM/ OTC BMM/

OAM OAM
2 RAM-2-OR 2 RAM-2-OR
Line L2 Rx BMM/OAM Line L2 Rx BMM/OAM
Out 3 In Out 3 In
BLANK BLANK
Expansion Chassis Expansion Chassis Manually

Associated
Automatically
Associated
infn_130aa

To turn up a RAM-2-OR configuration

State -> Lock.
Step 3 At Node B: repeat Step 2 and lock the OAMs in slots 2 and 3.
Step 5 At Node A: pre-provision a RAM-2-OR in slot 2 and lock it using Infinera GNM.
> RAM-2-OR.
Step 5b From the Equipment View, right-click the RAM-2-OR and select Admin State ->
Lock.
Step 6 At Node B: repeat Step 5 to pre-provision a RAM-2-OR in slot 2 and lock it.
Step 7 At Node A: set the associated OTSPTP values manually on the RAM-2-OR connector ports (L1
Step 7a From the Equipment View, highlight the appropriate RAM-2-OR to be configured,
34.
Step 7e Click Apply.
Step 7f In the list frame, ensure that L2 OTS ID is highlighted. See Figure 17-20 on page 17-
35.
Step 7g From the tabs listed in the middle of the window, select the Span/C-Band tab.

Step 7h In the Peer OTS Association panel, click on Rx Associated OTS and select the
Step 7i Click Apply.
Step 7j Click Close.
Span/C-Band tab
Tx Associated OTS

Span/C-Band tab
Rx Associated OTS
Step 8 At Node B: repeat Step 7 to set the associated OTSPTP values manually on the RAM-2-OR
connector ports (L1 Transmit and L2 Receive) to associate them with the correct OAM OTS port.
page 11-87.
Step 10 At Node B: provision the fiber type for the OAMs. Refer to “Entering DCM/PSE/DSE Information”
on page 16-24.
Step 11 At Node A: verify the RAM-2-OR L1 and L2 association on the BMM using Infinera GNM.
Step 11a From the Equipment View, highlight the configured BMM, right-click and select
Span. The Span Properties window is displayed. See Figure 17-21 on page 17-36.

Span/C-Band tab

Step 12 At Node B: repeat Step 11 to verify the RAM-2-OR L1 and L2 association on the OAMs.
Step 13 At Node B and C: label the fibers which will be used for the BMM/OAM side connectors and line
side connectors. Check the fiber connectors for cleanliness, refer to “Raman Fiber Connector
Cleaning” on page D-1 and connect line side fibers between Node B OTC and Node C DTC/
MTC.
Step 13a From OAM slot 2 LINE OUT (Tx) to BMM slot 1 LINE IN (Rx).
Step 13b From BMM slot 1 LINE OUT (Tx) to OAM slot 3 LINE IN (Rx).
Step 14 At Node A: insert a RAM-2-OR partially into the OTC.
Step 14a Remove the RAM-2-OR from the ESD protected bag.
Step 14b Reposition the ejectors on the RAM-2-OR to the full open position (perpendicular).
Step 14c Holding the RAM-2-OR in one hand and while guiding it with your other hand, align it
to the rail guides in slots 2 and/or 3 on the OTC with the product label at the bottom
side. In this orientation, the front panel of the RAM-2-OR is right reading.
Step 14d Slide the RAM-2-OR in partially; ensure that the RAM-2-OR is not fully seated
against the backplane (the RAM-2-OR must remain powered off).

Connector Cleaning” on page D-1. Connect fibers between DTC/MTC and OTC.
Step 15a From RAM-2-OR slot 2 BMM/OAM OUT (L1 Tx) to BMM slot 1 OTS IN (Rx).
Step 15b From BMM slot 1 OTS OUT (Tx) to RAM-2-OR slot 2 BMM/OAM IN (L2 Rx).
Connector Cleaning” on page D-1. Connect LINE side fibers for RAM-2-OR. For example, RAM-
2-OR LINE IN (L1 Rx) and RAM-2-OR LINE OUT (L2 Tx).
Step 17 At Node A: complete the RAM-2-OR installation.

Step 17a Gently push the RAM-2-OR toward the backplane until it stops.
Step 17c Lock the ejectors by turning the ejector screw 1/4 turn using a #1 Phillips screw-
driver.
Step 17d Verify that the RAM-2-OR powers up; wait 5 minutes before proceeding.
Step 18 At Node B: repeat Step 14 to insert a RAM-2-OR partially into the OTC.
Step 19 At Node B: label the fibers which will be used for the BMM/OAM side connectors and line side
connectors.
ing” on page D-1. Connect fibers between OTCs.
Step 20a From RAM-2-OR slot 2 BMM/OAM OUT (L1 Tx) to OAM slot 2 OTS IN (Rx).
Step 20b From OAM slot 3 OTS OUT (Tx) to RAM-2-OR slot 2 BMM/OAM IN (L2 Rx).
ing” on page D-1. Connect LINE side fibers for RAM-2-OR. For example, RAM-2-OR LINE IN
(L1 Rx) and RAM-2-OR LINE OUT (L2 Tx).
Step 22 At Node B: repeat Step 17 to complete the RAM-2-OR installation.

Step 23 At Node A: verify that the OSCT power is received on the RAM-2-OR from the BMM to which it is
right-click and select Transparent OSC. The OSCTCTP Properties window is dis-
played. See Figure 17-22.
Figure 17-22 Verifying the OSCT Power for RAM-2-OR
Real-Time PM tab
Step 24 At Node B: repeat Step 23 to verify that the OSCT power is received on the RAM-2-OR from the
OAM to which it is connected.

Span/C-Band tab
Step 27 At Node A and B: unlock the RAM-2-OR using Infinera GNM.
Step 27a From the Equipment View, right-click the RAM-2-OR and select Admin State ->
Unlock.
lize.
Step 28 At Node A: Unlock the BMM in slot 1 using Infinera GNM.
Unlock.
Step 29 At Node B and C: repeat Step 28 for all BMM/OAMs.

Step 30 At Node A and B: check that the correct fiber type is transferred to all the Raman modules.
Note: Refer to Table 17-9 on page 17-21 for allowable maximum point loss range for RAM-2-ORs
based on fiber type.
Optional: A Target Gain Offset can be applied to a RAM-2-OR to adjust the effective Raman
gain from its default gain set point. Under most conditions, this setting should remain at default
(0.0dB). To set the Target Gain Offset for the RAM-2-OR using Infinera GNM, see “Setting the
Target Gain Offset” on page 17-87.

REM-2 Turn-up and Test

This procedure is used to turn up and test a multi-chassis network element configured with REM-2
modules, see Figure 17-24. Note that this is an example and that the REM-2 with RAM-2-OR configuration
is also supported from OAM sites.
Figure 17-24 Raman Deployment using REM-2 Modules

Node A Node B
DTC/ DTC/
MTC 1 MTC 1
Line In Line In
Line Line
Out Out
BMM
Main Chassis BMM Main Chassis
OTC OTC
BMM/OAM BMM/OAM
2 2
Line Out RAM-2-OR Line Out RAM-2-OR
L2 Rx BMM/OAM In L2 Rx BMM/OAM In
3 REM-2 3 REM-2
RAM-2-OR In L1 Rx Line Out RAM-2-OR In L1 Rx Line Out
Expansion Chassis Expansion Chassis
Manually Automatically
Associated Associated infn_131aa

Page 17-42 REM-2 Turn-up and Test
To turn up a REM-2 configuration
Step 1 Launch Infinera GNM and establish GNM connectivity with Node A and B. Refer to “Launching
Infinera GNM” on page 11-29.

State -> Lock.
Step 3 At Node A: pre-provision a RAM-2-OR in slot 2, pre-provision a REM-2 in slot 3, and lock both
modules using Infinera GNM.
> RAM-2-OR.
Step 3b From the Equipment View, right-click the REM-2 and select Admin State -> Lock.
Step 3c From the Equipment View, right-click on slot 3 and select Pre-provision -> Raman -
> REM-2.
Step 3d From the Equipment View, right-click the RAM-2-OR and select Admin State ->
Lock.
Step 4 At Node B: repeat Step 2 and lock the BMM in slot 1.
Step 5 At Node B: repeat Step 3 to pre-provision a RAM-2-OR in slot 2, a REM-2 in slot 3, and lock both
modules.
Step 6 At Node A: set the associated OTSPTP values manually on the RAM-2-OR connector ports (L1
43.
OTS AID that is connected to the RAM-2-OR module L1 Tx (To BMM/OAM) connec-
tor.

Step 6e In the list frame, ensure that L2 OTS ID is highlighted. See Figure 17-26 on page 17-
44.
Step 6f From the tabs listed in the middle of the window, select the Span/C-Band tab.
Step 6g In the Peer OTS Association panel, click on Rx Associated OTS and select the
Step 6h Click Apply.
Step 6i Click Close.
Span/C-Band tab
Tx Associated OTS

Span/C-Band tab
Rx Associated OTS
Step 7 At Node B: repeat Step 6 to set the associated OTSPTP values manually on the RAM-2-OR con-
nector ports (L1 Transmit and L2 Receive) to associate them with the correct BMM OTS port.
page 11-87.
Step 9 At Node B: provision the fiber type for the BMM. Refer to “Provisioning Fiber Information” on
page 11-87.

Step 10 At Node A: verify the RAM-2-OR L1 and L2 association on the BMM using Infinera GNM.
Step 10a From the Equipment View, highlight the configured BMM, right-click and select
Span. The Span Properties window is displayed. See Figure 17-27.
Step 6 is now grayed out. See Figure 17-27.
Step 6 is now grayed out. See Figure 17-27.
Span/C-Band tab

Step 11 At Node B: repeat Step 10 to verify the RAM-2-OR L1 and L2 association on the OAMs.
Step 12 At Node A and B: provision the ultimate system maximum channel count using Infinera GNM.
Note: This is the ultimate channel capacity of the system and determines the REM-2 default gain
set point. Once the turn-up is complete, this channel count cannot be exceeded at any
time.

Step 12a From the Equipment View, right-click the BMM/OAM and select Properties. The
BMM Properties window is displayed.
Step 12b In the Summary panel, click Channels No. and select the appropriate number of
channels (ensure that this is the same value used for the REM-2s) in Step 12f. See
Figure 17-28.
Step 12c Click Apply.
Step 12d Click Close.
Figure 17-28 Selecting the Number of Channels for BMM
Channels No.
BMM State tab
Note: The Channels No. value can only be edited when the BMM is in a Maintenance or Locked
state.
Step 12e From the Equipment View, right-click the REM-2 and select Properties. The RAM
Step 12f In the Summary panel, click Max Number of Channels and select the appropriate
number of channels (ensure that this is the same value used for the BMMs in
Step 12b). See Figure 17-29 on page 17-47.
Step 12g Click Apply.
Step 12h Click Close.

Figure 17-29 Selecting the Number of Channels for RAM
Max Number of
Channels
RAM State tab
Note: The Max Number of Channels value can only be edited when the RAM is in a Mainte-
nance or Locked state.
Step 13 At Node A: set the associated OTSPTP values manually on the REM-2 connector ports (L1
Receive) to associate them with the correct RAM-2-OR OTS port as listed in Table 17-2 on
page 17-15 and Table 17-3 on page 17-15 using Infinera GNM. Figure 17-24 on page 17-41 pro-
vides details regarding which ports require manual association.
Step 13a From the Equipment View, highlight the appropriate REM-2 to be configured, right-
on page 17-48.
Step 13c In the BMM/OAM Association panel, click on Rx Associated OTS and select the
appropriate RAM-2 OTS ID from the drop-down menu. For example, select the RAM-
2-OR OTS AID that is connected to the REM-2 L1 RX (RAM-2-OR In) connector.

Figure 17-30 Setting the REM-2 L1 Association
Span/C-Band tab
Rx Associated OTS
Step 14 At Node B: repeat Step 13 to set the associated OTSPTP values manually on the REM-2 con-
nector ports (L1 Receive) to associate them with the correct RAM-2-OR OTS port.
Step 15 At Node A: verify the REM-2 L2 association on the RAM-2-OR using Infinera GNM.
Step 15a From the Equipment View, highlight the configured RAM-2-OR, right-click and select
Span. The Span Properties window is displayed. See Figure 17-31 on page 17-49.
49.
Step 15d In the Peer OTS Association panel, verify that the Tx Associated OTS selected in
Step 13 is now grayed out.

Figure 17-31 Verifying the REM-2 L2 Association
Span/C-Band tab
Tx Associated OTS (grayed out)
Step 16 At Node B: repeat Step 15 to verify the REM-2 L2 association on the RAM-2-OR.
Step 17 At Node A: insert a RAM-2-OR partially into the OTC.
Step 18 At Node A: repeat Step 17 and insert a REM-2 partially into the OTC in slot 3.
Step 19 At Node A: label the fibers which will be used for the BMM/RAM side connectors and line side
connectors.

Step 20 At Node A: check the fiber connectors for cleanliness, refer to “Raman Fiber Connector Clean-
ing” on page D-1. Connect fibers between DTC/MTC and OTC.
Step 21 At Node A: check the fiber connectors for cleanliness, refer to “Raman Fiber Connector Clean-
ing” on page D-1. Connect fibers between RAM-2-OR and REM-2.
Step 21a From RAM-2-OR slot 2 LINE OUT to REM-2 slot 3 RAM-2-OR IN.
Step 22 At Node B: insert a RAM-2-OR partially into the OTC.
Step 23 At Node B: repeat Step 17 and insert a REM-2 partially into the OTC in slot 3.
Step 24 At Node B: label the fibers which will be used for the BMM/RAM side connectors and line side
connectors.
ing” on page D-1. Connect fibers between DTC/MTC and OTC.
Step 26 At Node B: connect fibers between RAM-2-OR and REM-2.
Step 26a From RAM-2-OR slot 2 LINE OUT to REM-2 slot 3 RAM-2-OR IN.
Step 27 At Node A and B: check the fiber connectors for cleanliness, refer to “Raman Fiber Connector
Cleaning” on page D-1. Connect fibers between both OTCs.
Step 27a From Node A OTC REM-2 LINE OUT to Node B OTC RAM-2-OR slot 2 LINE IN.
Step 27b From Node B OTC REM-2 LINE OUT to Node A OTC RAM-2-OR slot 2 LINE IN.
Step 28 At Node A: complete the RAM-2-OR installation.
Step 28a Gently push the RAM-2-OR toward the backplane until it stops.
Step 28c Lock the ejectors by turning the ejector screw 1/4 turn using a #1 Phillips screwdriver.
Step 28d Verify that the RAM-2-OR powers up; wait 5 minutes before proceeding.
Step 29 At Node A: repeat Step 28 to complete the REM-2 installation.

Step 30 At Node B: repeat Step 28 to complete the RAM-2-OR installation.

Step 31 At Node B: repeat Step 28 to complete the REM-2 installation.
Step 32 At Node A: verify that the OSCT power is received on the RAM-2-OR from the BMM to which it is
right-click and select Transparent OSC. The OSCTCTP Properties window is dis-
played. See Figure 17-32.
Figure 17-32 Verifying the OSCT Power for RAM-2-OR
Real-Time PM tab
Step 33 At Node B: repeat Step 32 to verify that the OSCT power is received on the RAM-2-OR from the
BMM to which it is connected.

Figure 17-33.
Span/C-Band tab
Step 36 At Node A: unlock the BMM using Infinera GNM.
Step 36a From the Equipment View, right-click the BMM and select Admin State -> Unlock.
Step 37 At Node B: repeat Step 36 and unlock the BMM.
Step 38 At Node A and B: repeat Step 36 and unlock all RAM-2-OR/REM-2s. Wait 3 minutes before pro-
ceeding to allow the system to stabilize. The fiber type information will now be transferred.

Step 39 At Node A and B: verify the fiber type information on the RAM-2-OR and REM-2s using Infinera
GNM.
Step 39a From the Equipment View, highlight the appropriate REM-2 to be configured, right-
click and select Span. The Span Properties window is displayed. See Figure 17-34,
Figure 17-35 on page 17-54, and Figure 17-36 on page 17-55 depending on module
type.
Step 39b In the list frame, ensure that L1/L2 OTS ID is highlighted (for REM-2s, proceed to
Step 39c).
Step 39d In the Fiber panel, verify the correct fiber type information for each RAM-2-OR and
REM-2.
Figure 17-34 Verifying the Fiber Type for RAM-2-OR L1
List frame
(L1 selected)
Span/C-Band tab
Rx Fiber Type Tx Fiber Type

Figure 17-35 Verifying the Fiber Type for RAM-2-OR L2
List frame
(L2 selected)
Span/C-Band tab

Figure 17-36 Verifying the Fiber Type for REM-2 L1
Span/C-Band tab

Note: Refer to Table 17-9 on page 17-21 for allowable maximum point loss range for Raman
modules based on fiber type.
Optional: A Target Gain Offset can be applied to a Raman module to adjust the effective Raman
gain from its default gain set point. Under most conditions, this setting should remain at default
(0.0dB). To set the Target Gain Offset for the Raman module using Infinera GNM, see “Setting
the Target Gain Offset” on page 17-87.
Step 42 Proceed with turn up of the downstream (far end of the span) RAM-2-OR (in this example, Node
B). Refer to “To turn up a RAM-2-OR configuration” on page 17-33.
Step 43 Repeat Step 36 through Step 42 to turn up the opposite direction.

ORM Turn-up and Test

This procedure is used to turn up and test a multi-chassis network element configured with ORM modules,
see Figure 17-37.
Figure 17-37 Raman Deployment using ORM Modules
DTC/ OTC DTC/

MTC 1 1A OMM 1B OMM MTC 1
Line In ORM
Line Out
2 Line Out Line In
Line Out
Line In ORM
3 Line In Line Out
BMM
BMM
Main Chassis
Main Chassis Main Chassis

infn_278a
connections (as shown in Figure 17-37) are made while performing this procedure. Prior to
link turn-up and test, ensure that the fiber connectors used in the configuration are
checked for cleanliness prior to use, and the correct fiber provisioning steps have been
performed as specified in this procedure.

Page 17-58 ORM Turn-up and Test
To turn up an ORM configuration
Step 2 At Node A: provision the fiber type for the BMM in slot 1. Refer to “Provisioning Fiber Informa-
tion” on page 11-87.
Step 3 At Node C: provision the fiber type for the BMM in slot 1. Refer to “Provisioning Fiber Informa-
State -> Lock.
Step 6 At Node B: label the fibers which will be used for the BMM/ORM side connectors and line side
connectors. Check the fiber connectors for cleanliness, refer to “Raman Fiber Connector Clean-
ing” on page D-1.
Note: A minimum of 50kms of fiber is required for connecting the ORM line side. Refer to
Table 17-5 on page 17-16 for supported span loss range.
Step 7 At Node B: pre-provision an ORM in slot 2 and lock it using Infinera GNM.
Step 7a From the Equipment View, right-click on slot 2 and select Pre-provision -> ORM.
Step 7b From the Equipment View, right-click the ORM and select Admin State -> Lock.
Step 7c Repeat Step 7a and Step 7b for the ORM in slot 3.
Step 8 At Node B: set the OSC IP address for the ORM in slot 2.
Step 8a From the Equipment View, right-click the ORM and select GMPLS Link...
The GMPLS Link Properties window is displayed. See Figure 17-38 on page 17-59.
Step 8b In the OSC/GMPLS Control panel enter the IP Address and Subnet Mask.
Step 8e Repeat Step 8a through Step 8d for the ORM in slot 3.

Step 9 At Node B: provision the fiber type for the ORM in slot 2. Refer to “Provisioning Fiber Informa-
Step 10 At Node B: provision the fiber type for the ORM in slot 3. Refer to “Provisioning Fiber Informa-
Step 11 At Node B: insert an ORM partially into the OTC.
Step 11a Remove the ORM from the ESD protected bag.
Step 11b Reposition the ejectors on the ORM to the full open position (perpendicular).
Step 11c Holding the ORM in one hand and while guiding it with your other hand, align it to the
rail guides in slot 2 on the OTC with the product label at the bottom side. In this orien-
tation, the front panel of the ORM is right reading.
Step 11d Slide the ORM in partially; ensure that the ORM is not fully seated against the back-
plane (the ORM must remain powered off).
Step 11e Repeat Step 11a and Step 11d for the ORM in slot 3.
Step 12 At Node B: connect line side fibers between Node A DTC/MTC and Node B OTC.
Step 12a From BMM slot 1 LINE OUT (Tx) to ORM slot 2 LINE IN (Rx).
Step 12b From ORM slot 3 LINE OUT (Tx) to BMM slot 1 LINE IN (Rx).
Step 13 At Node B: connect line side fibers between Node B OTC and Node C DTC/MTC.
Step 13a From ORM slot 2 LINE OUT (Tx) to BMM slot 1 LINE IN (Rx).
Step 13b From BMM slot 1 LINE OUT (Tx) to ORM slot 3 LINE IN (Rx).

Page 17-60 ORM Turn-up and Test
Step 14 At Node B: connect OSC cross over fibers between ORM slot 2 and ORM slot 3.
Step 14a Connect the Main Chassis ORM Slot 2 OSC Out port to the Main Chassis ORM Slot
3 OSC In port.
Step 14b Connect the Main Chassis ORM Slot 3 OSC Out port to the Main Chassis ORM Slot
2 OSC In port.
Note: If DCM/DSEs are not being deployed, ensure that loopback fibers are connected at each
ORM-CXH1-MS DCM connector (connect DCM OUT to DCM IN).
Step 15 At Node B: complete the ORM installation.

Step 15a Gently push the ORM toward the backplane until it stops.
Step 15c Lock the ejectors by turning the ejector screw 1/4 turn using a #1 Phillips screwdriver.
Step 15d Verify that the ORM powers up; wait 5 minutes before proceeding.
Step 15e Repeat Step 15a and Step 15d for the ORM in slot 3.
Step 16 At Node A: unlock the BMM in slot 1 using Infinera GNM.
Unlock.
Step 17 At Node C: repeat Step 16 to unlock the BMM in slot 1.
Step 18 At Node B: unlock the ORM in slot 2 using Infinera GNM.
Step 18a From the Equipment View, right-click the ORM and select Admin State -> Unlock.
Step 18b Wait 3 minutes before proceeding to allow the Raman pumps to turn on and stabilize.
Step 18c Repeat Step 18a and Step 18b for the ORM in slot 3.
Step 19 At Node A: verify neighbor connectivity with Node B.
Step 19a From the Equipment View, highlight the BMM in slot 1, right-click and select Span.
The Span Properties window is displayed. See Figure 17-39 on page 17-61.
Step 19b From the tabs listed in the middle of the window, select the Neighbor Connectivity
tab.
Step 19c Verify that the Node ID listed corresponds to Node B and the OTS ID of the Node B
ORM is displayed correctly (1-A-2-L1).

Step 20 At Node B: verify neighbor connectivity with Node A.

Step 20a From the Equipment View, highlight the ORM in slot 2, right-click and select Span.
The Span Properties window is displayed. See Figure 17-39 on page 17-61.
tab.
Step 20c Verify that the Node ID listed corresponds to Node A and the OTS ID of the Node A
BMM is displayed correctly (1-A-1-L1).
Step 21 At Node C: repeat Step 19 to verify neighbor connectivity with Node B (for the BMM in slot 1).
Step 22 At Node B: repeat Step 20 to verify neighbor connectivity with Node C (for the ORM in slot 3).
Figure 17-39 Verifying Neighbor Connectivity
Neighbor
Connectivity tab
Discovered
Node ID
Step 23 Proceed to “Setting the Point Loss Offset for ORM Modules” on page 17-77.

Page 17-62 Setting the Point Loss Offset for Raman Modules
Setting the Point Loss Offset for Raman

Modules
WARNING
The point loss offset must be recalculated (on all affected Raman modules) whenever the
span loss changes +/-2dB after initial turn-up and service is impacted. Infinera recom-
mends that the point loss offset be recalculated during a maintenance window for the fol-
lowing conditions:
1. Whenever the link is restored after a fiber cut or a RAM line side fiber reconnection
within 50kms from where the RAM pump enters the transmission fiber.
2. Whenever the span loss changes +/-2dB and service is not impacted.
3. Whenever a RAM is removed and replaced with a different RAM.
WARNING
Operating RAMs without proper point loss offset settings may severely degrade the link
performance.
Note: Unless specifically noted otherwise, all references to the term “Raman module” and/or RAM
will refer to either the RAM-1, RAM-2-OR, or REM-2 interchangeably.
Note: The RamanPLO.jar file, referred to as Raman point loss offset (PLO) adjustment utility, is
distributed with Infinera DNA but requires Infinera GNM to execute (point loss offset adjust-
ments are not supported using Infinera DNA). If you do not have access to Infinera DNA
and/or the RamanPLO.jar file, contact an Infinera TAC resource for further assistance.
The purpose of this procedure is to provide instructions for setting the point loss offset on Raman modules
to reach the target gain. The Raman PLO adjustment utility is initiated through Infinera GNM and
supported for all Raman modules.
This section is organized as follows:
“Overview” on page 17-64
“Crash Recovery” on page 17-65
“Error and Warning Messages” on page 17-75

Prerequisites
Note: This procedure can only be performed by users that have the appropriate privileges. The
Raman PLO adjustment utility requires security administrator (SA) access enabled in order
to perform a network administrator (NA), network engineer (NE), and test and turn up (TA)
privilege check. Refer to “Setting Up User Accounts with Turn-up and Test Privileges” on
page 11-34 for more details.
1. Completion of the appropriate Raman turn-up procedure. Refer to “To turn up a RAM-1 configura-
tion” on page 17-23, “To turn up a RAM-2-OR configuration” on page 17-33, and/or “To turn up a
REM-2 configuration” on page 17-42 for more details.
2. Access to Infinera DNA (the RamanPLO.jar file, referred to as Raman PLO adjustment utility, is
distributed with Infinera DNA).
3. At least one line module with eight (8) active channels (or greater) must be present in the system to
provide C-Band signals to measure Raman gain. However, the link should have the maximum
number of OCGs provisioned (for the deployment) as possible.
4. The OSC channel must be active and Infinera’s Automated Gain Control (AGC) must be enabled.
5. The launch fiber type must be provisioned correctly on all fiber spans. The Raman PLO adjustment
utility will attempt to confirm proper fiber connection and quit if the connection is not properly con-
figured or if the information provided does not match the link information.
6. Alarm reporting should be enabled and the Admin State for all modules set to the Unlocked state
(In-Service, Normal).
7. Configuration changes should not be attempted during point loss offset calculation/adjustment exe-
cution including the following:
Link configuration (for example, the provisioned transmit fiber type or the number of channels).
Link power levels. The Raman PLO adjustment utility will attempt to check for power changes
but there is no guarantee that transients will be captured by the utility.
Number of channels in the link must be set to eight (8) or greater.
8. All result and log files should be saved for failure analysis.
Ensure that the RamanResultSummary.csv and RamanResultDetail.csv result files, and the
RamanTurnUpTool.html log information is collected from the network elements installed in the
span whenever a failure occurs during Raman PLO adjustment utility execution.
Note: All result and log files are contained in a separate directory named logs. The logs directory
contains individual directories (each with a unique name including date and timestamp)
and resides in the same directory as the RamanPLO.jar file.

Overview
1. The Raman PLO adjustment utility is initiated through Infinera GNM.
2. The Raman PLO adjustment utility must not be executed simultaneously on a particular digital
span.
3. Execution of the Raman PLO adjustment utility is unidirectional (for example, the direction being
turned up: West to East or East to West).
4. The Raman PLO adjustment utility displays an error message if the required point loss offset is out-
side the range of -0.5 to +0.5dB. The error message will suggest that the user clean the fiber con-
nections involved in the link or verify the fiber type. Also note that the particular fiber type has a
maximum supported point loss offset range depending on the Raman module type deployed, refer
to “Raman Maximum Point Loss” on page 17-21.
5. The Raman PLO adjustment utility will calculate and set the point loss offset depending on Raman
module type, refer to “Raman Maximum Point Loss” on page 17-21. If the span requires the point
loss offset to be outside the allowed range, the utility will prompt for user confirmation to cap it to the
maximum allowed PLO value.
6. If an error occurs during execution of the Raman PLO adjustment utility, the utility will restore the
link settings back to the original/initial settings. This includes the following:
Enable AGC in the link.
Reset the Raman module point loss offset to the original values.
Set the Admin State for all BMMs, OAMs, RAMs, and/or ORMs involved in the turn up to the
previous state.
7. For each RAM, the average time for Raman PLO adjustment utility execution is approximately 10
minutes (for the initial iteration) and 5 minutes for each additional iteration. The utility no longer lim-
its the maximum change of the point loss offset per iteration provided it is within the allowed range
for the deployed fiber type.
8. After the Raman PLO adjustment utility completes, any outstanding alarms (mainly Equipment) or
conditions in the span will be highlighted for debugging.
9. Result and log files are created to ensure that any failures can be debugged and any extraneous
circumstances can be identified. The Raman PLO adjustment utility will either continue or terminate
properly after error condition notification.

Crash Recovery
The Raman PLO adjustment utility provides for crash recovery in the event of a crash. A crashrecovery.log
file is created to provide the utility with a mechanism to restore the link settings back to the original/initial
settings should any of the following events occur:
 Crash during utility execution
 User abort/abrupt termination of the utility
 Incompletion execution of the utility
CAUTION
Do not attempt to delete or remove the crashrecovery.log file during utility execution or after
an abrupt termination of the utility.
Note: The crashrecovery.log file resides in the same directory as the RamanPLO.jar file.

To set the point loss offset for Raman modules
When performing this procedure, refer to Figure 17-40. The Raman PLO adjustment utility should be
executed on nodes installed in the West direction toward the East. Once completed, the utility should be
repeated for nodes in the East direction toward the West. Alternatively, the Raman PLO adjustment utility
can be executed on nodes installed in the East direction toward the West and then be repeated with nodes
installed in the West direction toward the East.
Figure 17-40 Example Raman Turn-up Reference Diagram
West to East Direction
Node A Node B Node C Node D

BMM
BMM
Line Line
Out In
OMM OMM OMM OMM
Line Line
OAM ORM
In Line Line Line Line Out
In Out In Out
Line ORM Line Line OAM Line

Out In Out In
OMM OMM OMM OMM OMM OMM OMM OMM

OUT IN OUT IN
RAM-1 RAM-1 OUT IN
RAM-2-OR RAM-2-OR OUT
OUT
BMM/OAM Line Line BMM/OAM BMM/OAM Line Line BMM/OAM
IN IN OUT IN OUT IN OUT IN
East to West Direction Amplifier Pump Direction

infn_456a
Note: If RAMs and ORMs are deployed in the same digital span, complete the turn up of the
Raman modules first (including the Raman PLO adjustment). A confirmation dialog is
displayed during execution of the Raman PLO adjustment utility. For example:
NodeC: ORM Found as Main Card of the Node.

ORM must be calibrated using ORM Turn-up Script
Please confirm to continue execution!!!

Step 1 Launch Infinera GNM and establish GNM connectivity with Node A and D. Refer to “Launching
Infinera GNM” on page 15-21.
Step 2 At Node A: initiate the Raman PLO adjustment utility for the West to East direction. Refer to
Step 2a From the Infinera GNM Equipment View, right-click the RAM-1 in slot 1 and select
Step 2b Right-click the RAM-1 and select Adjust Point Loss -> Link. The Raman Turn-up
window is displayed.
Figure 17-41 Raman Point Loss Offset (PLO) Adjustment - Initiated through Infinera GNM
The Span menu option provides PLO adjustment for a single Raman module in the direction
being turned up (unidirectional) and must be repeated on the peer Raman module. The Link
menu option provides PLO adjustment for Raman modules in each span in the direction being
turned up (for example, the Raman modules installed in Node A and C in the West to East direc-
tion, or the Raman modules installed in Node D and B in the East to West direction. Refer to
Figure 17-40 on page 17-66).

Figure 17-42 Raman Turn-up Window
Note: The GNE IP Address field is user editable (from the Raman Turn-up window). (This field
does not change the DCN IP address.) This feature provides additional flexibility during
execution of the Raman PLO adjustment utility in the event that DCN connectivity is not
available. For example, the user can set the GNE IP address to the value currently
assigned to the Craft IP port. However, ensure that the GNE IP address is reset back to the
previously assigned value upon successful completion of the utility. For SNE nodes the
default value will display a GNE IP Address of 0.0.0.0. This IP address will need to be
changed to the DCN IP address of either the primary or secondary GNE that the SNE uses
for file transfers.
Step 3 In the Raman Turn-up window, click Browse. The Open... window is displayed.
Figure 17-43 RamanPLO.jar File Location
Step 4 In the Open... window, navigate to the directory where RamanPLO.jar is located.
Note: The RamanPLO.jar file is distributed with Infinera DNA. Refer to the Infinera DNA Adminis-
trator Guide for additional information. If you do not have access to Infinera DNA and/or the
RamanPLO.jar file, contact an Infinera TAC resource for further assistance before proceed-
ing.
Step 5 Select RamanPLO.jar and click Open.

Step 6 In the Raman Turn-up window, click Run. A warning message dialog box is displayed indicating
that the Raman PLO adjustment utility is about to execute. Click Continue.
Figure 17-44 Warning Message
The Raman Turn-up Tool introduction screen is displayed.
Note: The term “Raman Turn-up Tool” refers to the Raman PLO adjustment utility.
Figure 17-45 Raman Turn-up Tool Introduction Screen
Step 7 Click Ok. The Configuration Details window is displayed.

Figure 17-46 Configuration Details
Step 8 In the Configuration Details window, click Apply to all NE. The Config User window is dis-
played.
Figure 17-47 Config User
Step 9 In the Config User window, perform the following:

Step 9a Click the User Name check box and enter the user name information.
Step 9b Click the Password check box and enter the password information.
Step 9c In the Re-Confirm field, re-enter the password information.
Figure 17-48 Config User - Example

Step 9d Click Apply. The Configuration Details - Complete window is displayed with the
TL1 User, TL1 Password, and TL1 Confirm Password fields filled in for all nodes in
the link.
Figure 17-49 Configuration Details - Complete
Step 10 In the Configuration Details - Complete window, click Execute.

Step 11 A confirmation message dialog box is displayed indicating that the Raman PLO calibration is
about to execute. Click Ok.
Figure 17-50 Confirmation Message
The Configuration Details - Execution window is displayed showing details of the Raman PLO
adjustment utility execution.
Note: The Raman PLO adjustment utility initially sets the PLO to zero (0) on each Raman module
prior to calculating new values.

Figure 17-51 Configuration Details - Execution
Optional: to abort the Raman PLO adjustment utility during execution, click Abort. A confirma-
tion message dialog box is displayed. Click Yes.
Figure 17-52 Configuration Details - User Abort
Note: Refer to “Additional Abort Scenarios” on page 17-74 for information regarding additional
abort scenarios.

Step 12 If any errors are encountered during execution of the Raman PLO adjustment utility, verify net-
work connectivity or resolve the issue prior to executing the utility again. Refer to “Error and
Warning Messages” on page 17-75 for typical errors and/or warning messages. If no errors are
encountered during execution of the utility, the point loss offset will be set for Raman modules in
each span in the direction being turned up (for example, the Raman modules installed in Node A
and C in the West to East direction, or the Raman modules installed in Node D and B in the East
to West direction. Refer to Figure 17-40 on page 17-66).
Optional: when an error occurs, the Raman PLO adjustment utility performs a cleanup opera-
tion (graceful shutdown) and closes the session. The user can either close the window or rerun
the utility (without closing the window) by selecting View -> Configure User. See Figure 17-53.
Figure 17-53 Configuration Details - Configure User Feature
WARNING
Do not reset XCMs, MCMs, OMMs, OAMs, RAMs, and/or ORMs while the Raman PLO
adjustment utility is executing. Ensure that the link is stable and that no configuration
changes (such as XCM/MCM/OMM/OAM/RAM/ORM warm reboots, cold reboots, lock/
unlock of line cards, and/or OCG add/drops) are made during point loss offset calculation/
adjustment.
Step 13 In the Configuration Details window, click Close.

Step 14 Click Yes.

Step 15 At Node D: repeat Step 2 through Step 14 for all RAMs in the East to West direction. Refer to
WARNING
The point loss offset must be recalculated (on all affected Raman modules) whenever the
lowing conditions:
1. Whenever the link is restored after a fiber cut or a RAM line side fiber reconnection
within 50kms from where the RAM pump enters the transmission fiber.
3. Whenever a RAM is removed and replaced with a different RAM.
Step 16 To initiate ORM PLO adjustment for any installed ORMs, proceed to “Setting the Point Loss Off-
set for ORM Modules” on page 17-77.
Note: ORM PLO adjustment utilizes a different utility, ORMTurnup.exe, which is also initiated
through Infinera GNM (and distributed with Infinera DNA).
Additional Abort Scenarios

When the Raman PLO adjustment utility is closed abruptly or aborted, it is recommended that a cleanup
operation (graceful shutdown) be performed when prompted (by clicking Yes) as shown in the following
examples:
Figure 17-54 Confirmation Message - Abrupt Close
Figure 17-55 Confirmation Message - Abrupt Close, Start Next Execution

Error and Warning Messages

Typical errors and/or warning messages displayed during execution of the Raman PLO adjustment utility
are listed in Table 17-12.
Note: The Raman PLO adjustment utility will only display the following errors and/or warning
messages if an error is encountered during execution; the utility does not check for any
other conditions. Ensure that the link is stable and that no configuration changes (such as
XCM/MCM/OMM/OAM/RAM/ORM warm reboots, cold reboots, lock/unlock of line cards,
and/or OCG add/drops) are made during point loss offset calculation/adjustment.
Table 17-12 Error and Warning Messages
Error/Warning Raman PLO Adjustment

Message Probable Cause Utility Action
Incomplete control link This error message is displayed if the control link infor- Restore the link settings
information mation is incomplete. back to the original/initial
GNE IP incomplete This error message is displayed if the GNE IP informa- settings and exit the utility.
tion field is empty.
TL1 login details incom- This error message is displayed if the utility detects the
plete login information fields are empty.
Invalid card AID This error message is displayed if an invalid card AID is
detected by the utility.
Raman association is This error message is displayed if the Raman associa-
not present tion with a BMM/OAM/ORM has not been set.
Incomplete last utility This error message is displayed if the utility detects that Prompt for user confirma-
execution the last utility execution was unsuccessful. tion to restore the link set-
tings back to the original/
initial settings and continue.
Cannot read input XML This error message is displayed if the utility is unable to Restore the link settings
file read the XML file correctly or the XML file is not in the back to the original/initial
correct format. settings and exit the utility.
Rx fiber type is This error message is displayed if the utility detects that
unknown the receive (Rx) fiber type is unknown. This can occur if
Infinera’s AGC/ADAPT did not run successfully prior to
utility execution.
Card in OLOS This error message is displayed if the utility detects that Attempt to unlock any
a card is in an OLOS state. locked cards and recover
from OLOS.

Error/Warning Raman PLO Adjustment

Equipment fault present This error message is displayed if the utility detects that Restore the link settings
a card is in a faulted state. back to the original/initial
OSC fault present This error message is displayed if the utility detects that settings and exit the utility.
a card in the span is exhibiting OSC failure.
Unable to login to the This error message is displayed if the utility is unable to
NE create a session with the NE.
Unable to reconnect to This error message is displayed if the utility is unable to
the NE re-connect to the NE after disconnect.
TL1 object initialization This error message is displayed if the utility is unable to
failed initialize the TL1 object.
Card unreachable This error message is displayed if any of the cards are
unreachable during utility execution.
Card not present This error message is displayed if the utility detects that
the required cards (BMM, OAM, ORM, and/or Raman)
are not present.
Point loss offset is OOR This error message is displayed if the utility detects that Prompt for user confirma-
the calculated PLO is outside the range of -0.5 to 0.5dB. tion and cap it to the maxi-
This error message is also displayed if the utility detects mum value.
that the calculated PLO is outside the range for the
deployed fiber type (refer to “Raman Maximum Point
Loss” on page 17-21).
Point loss offset is out- This error message is displayed if the utility detects that Prompt for user confirma-
side standard range the calculated PLO is outside the range of -0.5 to 0.5dB. tion and continue.
Unable to come out of This error message is displayed if the Raman card does Restore the link settings
OLOS not come out of OLOS after unlock operation. back to the original/initial
Unable to lock card This error message is displayed if the utility is unable to settings and exit the utility.
lock the card during execution.
Unable to unlock card This error message is displayed if the utility is unable to
unlock the card during execution.
Unable to retrieve PM This error message is displayed if the utility is unable to
for the card retrieve PM data for the card.
Unable to retrieve card This error message is displayed if the utility is unable to
details retrieve card details (i.e. Rx fiber type, Admin state, etc.)
for the card.
Power instability This error message is displayed if the utility detects that Restore the link settings
power has become unstable during utility execution. back to the original/initial
settings, prompt user to
rerun utility, and exit.

Setting the Point Loss Offset for ORM

Modules
WARNING
The point loss offset must be recalculated (on all affected ORM modules) whenever the
lowing conditions:
1. Whenever the link is restored after a fiber cut or an ORM line side fiber reconnection
within 50kms from where the ORM pump enters the transmission fiber.
3. Whenever an ORM is removed and replaced with a different ORM.
WARNING
Operating RAMs and/or ORMs without proper point loss offset settings may severely
degrade the link performance.
Note: The ORMTurnup file, referred to as ORM point loss offset (PLO) adjustment utility, is dis-
tributed with Infinera DNA but requires Infinera GNM to execute (point loss offset adjust-
ments are not supported using Infinera DNA). There are three (3) versions of the file
available:
1. ORMTurnup.exe—for Microsoft Windows based systems.
2. ORMTurnup_Linux_32—for Red Hat Linux 32 bit based systems.
3. ORMTurnup_Linux_64—for Red Hat Linux 64 bit based systems.
If you do not have access to Infinera DNA and/or the ORMTurnup file, contact an Infinera
TAC resource for further assistance.
The purpose of this procedure is to provide instructions for setting the point loss offset on ORMs to reach
the target gain. The ORM PLO adjustment utility is initiated through Infinera GNM and supported for ORMs
in the following configurations:
 Inline amplifier (ORM-CXH1-MS/ORM-CXH1)
 Preamplifier (ORM-CXH1-MS/ORM-CXH1)
 Booster amplifier (ORM-CXH1 with an OAM-CXH1-MS as booster amplifier)


Page 17-78 Setting the Point Loss Offset for ORM Modules
Prerequisites
Note: This procedure can only be performed by users that have the appropriate privileges. Refer
to “Setting Up User Accounts with Turn-up and Test Privileges” on page 11-34 for more
details.
1. Completion of the ORM turn-up procedure. Refer to “To turn up an ORM configuration” on page 17-
58 for more details.
2. If RAMs and ORMs are deployed in the same digital span, complete the turn up of the Raman
FRUs first (including the Raman point loss offset calculation) before performing this procedure on
the ORMs. Refer to “Raman Turn-up and Test Overview” on page 17-4.
3. Access to Infinera DNA (the ORMTurnup file, referred to as ORM PLO adjustment utility, is
distributed with Infinera DNA).
4. At least one line module (DLM/XLM/ADLM/AXLM) with eight (8) active channels (or greater) must
be present in the system to provide C-Band signals to measure Raman gain.
6. The launch fiber type must be provisioned correctly on all fiber spans. The ORM PLO adjustment
utility will attempt to confirm proper fiber connection and quit if the connection is not properly config-
ured or if the information provided does not match the link information.
Link power levels. The ORM PLO adjustment utility will attempt to check for power changes but
there is no guarantee that transients will be captured by the utility.
9. All log files should be saved for failure analysis. Ensure that the ORM debugXfr log information is
collected from the network elements installed in the span as well as the Log.txt file whenever a fail-
ure occurs during ORM PLO adjustment utility execution.
10. In rare cases, it may be necessary to reduce the maximum configured channel count to a lower
value. However, the value has to be greater than or equal to the actual channel count. The channel
count configuration can be reset to the original value after the ORM PLO adjustment utility has
completed. This assures that there is no ORM saturation issue. After the point loss offset is set, any
channel count configuration will be supported by the ORM. Refer to “Overview” on page 17-79 for
more details.

Overview
1. The ORM PLO adjustment utility is initiated through Infinera GNM.
2. The ORM PLO adjustment utility must not be executed simultaneously on a particular digital span.
3. The ORM PLO adjustment utility displays an error message if the required point loss offset is out-
side the range of -0.5 to +0.5dB. The error message will suggest that the user clean the fiber con-
nections involved in the link.
4. The ORM PLO adjustment utility will calculate and set the point loss offset within the range of -0.5
to +3dB. If the span requires the point loss offset to be outside the allowed range, an error mes-
sage will be displayed.
5. If an error occurs during execution of the ORM PLO adjustment utility, the utility will restore the link
settings back to the original/initial settings. This includes the following:
Reset the Launch Power Offset of the modules in previous nodes.
Reset the ORM point loss offset to the original values.
Set the Admin State for all BMMs, OAMs, and/or ORMs involved in the turn up to the Unlocked
state.
6. When the ORM is locked, its input power should be within the photodetector (PD) dynamic range
specifications (≥ -19dBm for ORM-CXH1-MS and ≥ -28dBm for ORM-CXH1).
If the power is below the dynamic range, the launch power of previous nodes will be increased to
bring the ORM input power within the dynamic range.
If the ORM PLO adjustment utility is still unable to bring the ORM input power above the required
power levels, a prompt is displayed with an option to terminate the utility or continue.
To continue with the ORM PLO adjustment utility, reduce the maximum configured channel
count to a lower value (which must be greater than or equal to the actual channel count), wait for
one AGC cycle (approximately 7 minutes), and then continue with the utility.
The network element may report an Inter-module Mis-connection alarm if the maximum channel
count configurations of end-BMMs do not match (the alarm can be ignored during utility execu-
tion). For example, if the actual number of channels being carried is only 20 and the channel
count value is 80, set the channel count in the head-end BMMs in the link to 40, wait approxi-
mately 7 minutes, and then continue with the utility.
After successful completion of the utility, set the channel count value back to 80.
7. For each ORM, the average time for ORM PLO adjustment utility execution is approximately 10
minutes (for the initial iteration) and 5 minutes for each additional iteration. The utility no longer lim-
its the maximum change of the point loss offset per iteration. All utility actions are logged in the
Log.txt file.
8. After the ORM PLO adjustment utility completes, any outstanding alarms (mainly Equipment) or
conditions in the span will be highlighted for debugging.

9. Log files are created to ensure that any failures can be debugged and any extraneous circum-
stances can be identified. The ORM PLO adjustment utility will either continue or terminate properly
after error condition notification.
To set the point loss offset for ORM modules
When performing this procedure, refer to Figure 17-56. The OAM/ORMs installed in the top slot are
referred to as card AID 1-A-2 and the OAM/ORMs installed in the bottom slot are referred to as card AID 1-
A-3.
The ORM PLO adjustment utility should be executed on nodes installed in the West direction toward the
East. Once completed, the utility should be repeated for nodes in the East direction toward the West.
Alternatively, the ORM PLO adjustment utility can be executed on nodes installed in the East direction
toward the West and then be repeated with nodes installed in the West direction toward the East.
Figure 17-56 Example ORM Turn-up Reference Diagram
Node A Node B Node C Node D Node E
OMM OMM OMM OMM OMM OMM

Line
OAM ORM ORM In
Line Line Line Line Line Line Line
Out In Out In Out In Out
Line Line ORM Line Line ORM Line Line OAM Line
Out In Out In Out In Line
In
Out
East to West Direction

infn_456
Note: If RAMs and ORMs are deployed in the same digital span, complete the turn up of the
Raman FRUs first (including the Raman point loss offset calculation) before performing this
procedure on the ORMs. Refer to “Raman Turn-up and Test Overview” on page 17-4.
Note: The ORM turn-up procedure must be completed prior to performing this procedure. Refer to
“To turn up an ORM configuration” on page 17-58.
Step 1 Launch Infinera GNM and establish GNM connectivity with Node B, C, and D. Refer to “Launch-

Step 2 At Node C: initiate the point loss offset process for the West to East direction starting with the
ORM in slot 2. See Figure 17-56 on page 17-80.
Step 3 From Infinera GNM, right-click the ORM in slot 2 and select Admin State -> Maintenance.
Step 4 From Infinera GNM, right-click the ORM in slot 2 and select Adjust Point Loss -> Digital Span.
Note: The Digital Span menu option provides point loss offset adjustment for all ORMs installed
in the same direction of the digital span in a sequential order. The turn up action is taken in
only one direction of the span (the direction that is facing the ORM) and must be repeated
for the opposite direction of the span. The FRU menu option provides point loss offset
adjustment for a single ORM.
Note: If the ORMTurnup.exe file is not present in the default location, a Browse button is shown
(adjacent to the Fill All button) indicating that the ORMTurnup.exe file could not be located
(the Browse button is shown only if the file cannot be located). Click the Browse button
and provide the path to where the file is located.
The ORM Turnup window is displayed.
Figure 17-57 ORM Turnup Window
Note the following regarding the ORM Turnup window:

The Calibrate check box provides the user with the option to individually select a node (or
set of nodes) on which the ORM PLO adjustment utility will be executed. A check mark
means that the utility will be executed for the particular node. No check mark means that the
utility will not be executed for the particular node
The GNE IP Address field is user editable (from the ORM Turnup window). (This field does
not change the DCN IP address.) This feature provides additional flexibility during execution
of the ORM point loss offset utility in the event that DCN connectivity is not available. For
example, the user can set the GNE IP address to the value currently assigned to the Craft IP
port. However, ensure that the GNE IP address is reset back to the previously assigned
value upon successful completion of the utility. For SNE nodes the default value will display a
GNE IP Address of 0.0.0.0. This IP address will need to be changed to the DCN IP address
of either the primary or secondary GNE that the SNE uses for file transfers

Step 5 In the ORM Turnup window, select the first row, and click Fill All. The Fill All option allows for
editing of the username and passwords all at the same time. This information can also be
entered directly within the table (see Figure 17-57 on page 17-81). The Login Details window is
displayed.
Figure 17-58 Login Details Window
Step 6 In the Login Details window, enter the information for: TL1 User Name, TL1 Password, Confirm
Password, ACLI Password, and Confirm Password.
Step 7 Click Apply.
Step 8 A warning message dialog box is displayed indicating that the login and password details will be
applied to all nodes in the span. Click Continue.
Step 9 Click Apply.

Step 10 A warning message dialog box is displayed indicating that the ORM PLO adjustment utility is
about to execute. Click Continue.
The point loss offset calculation/adjustment session is launched in a separate console window.
See Figure 17-61 on page 17-83.

WARNING
Do not reset XCMs, MCMs, OMMs, OAMs, and/or ORMs while the ORM PLO adjustment
utility is executing. Ensure that the link is stable and that no configuration changes (such as
XCM/MCM/OMM/ORM warm reboots, cold reboots, lock/unlock of line cards, and/or OCG
add/drops) are made during point loss offset calculation/adjustment.
WARNING
Point loss offset calculation/adjustment will continue until completion even if the Infinera
GNM session is closed. The ORM PLO adjustment utility must not be executed simultane-
ously on a particular digital span.
Figure 17-61 ORM PLO Adjustment Utility Console Window
Step 11 If any errors are encountered during execution of the ORM PLO adjustment utility, verify network
connectivity or resolve the issue prior to executing the utility again. Refer to “Error and Warning
Messages” on page 17-84 for typical errors and/or warning messages.

WARNING
1. In most error scenarios, the ORM PLO adjustment utility makes an attempt to restore all
the link parameters to the original settings before quitting. However, in rare cases the resto-
ration process may not complete. User interaction is required to enable AGC at the head-
end BMM node, restore the launch power offsets to the original values (which are displayed
in the ORM PLO adjustment utility console window and copied into the Log.txt file), unlock
any of the locked cards or place cards into a Maintenance state, and reset the point loss
offset to original values.
2. Do not execute the utility on ORMs installed downstream if the utility is not successful for
the preceding ORM. If the problem persists, collect debugXfr logs from the network ele-
ments installed in the span and the Log.txt files, and contact an Infinera TAC resource for
assistance.
If no errors are encountered during execution of the ORM PLO adjustment utility, the point loss
offset will be set for each ORM in the direction being turned up (for example West to East, or
East to West). The ORM that was previously locked at Step 3 will be unlocked.
Step 13 Repeat Step 2 through Step 12 for all ORMs in the East to West direction starting with the ORM
in slot 3. See Figure 17-56 on page 17-80.
WARNING
The point loss offset must be recalculated (on all affected ORM modules) whenever the
lowing conditions:
1. Whenever the link is restored after a fiber cut or an ORM line side fiber reconnection
within 50kms from where the ORM pump enters the transmission fiber.
3. Whenever an ORM is removed and replaced with a different ORM.

Typical errors and/or warning messages are listed below:
Note: The ORM PLO adjustment utility will only display the following errors and/or warning mes-
sages if an error is encountered during execution; the utility does not check for any other
conditions. Ensure that the link is stable and that no configuration changes (such as OMM/
ORM warm reboots, cold reboots, lock/unlock of line cards, and/or OCG add/drops) are
made during point loss offset calculation/adjustment.

1. Not able to login into card. Quitting...

2. Channel count is less than 8. Quitting…
3. Rx Fiber type on ORM is Unknown. Either AGC is not running or Tx Fiber type on Previous Node is
not set. Quitting...
4. Mismatch in Rx Fiber type of ORM and Previous node Tx Fiber Type. Something incorrect with the
Automated Gain Control Loop. Quitting...
5. Warning: Point Loss Offset required is less than -0.5dB. Suggested value is clamped to -0.5dB
6. Warning: Setting Point Loss Offset value to X dB above 0.5dB might cause Long-term damage to
connectors, Proceed only if you are certain that fiber connectors are clean and all fibers are good
quality, Proceed if you are sure (y/n)?
WARNING
Possible Range for Point Loss Offset Value in ORM (dB): -0.5 to +3.0
Operating the system with point losses above 0.5dB is not recommended and the link per-
formance is not guaranteed. Long-term damage can arise from dirty or improper fiber con-
nections. Proceed with above 0.5dB point loss only if one is certain that the fiber
connectors are clean, the connections are of good quality, and the patch cords and fiber
span do not have abnormal high loss or reflection.
7. Warning: Operating the system with point loss above 3dB is not allowed. Suggested value is
clamped to 3dB
8. Span loss is greater than supported value by ORM card
9. Span loss is less than supported value by ORM card
Note: Refer to Table 17-5 on page 17-16 for ORM maximum gain and span loss values.
10. Equipment degradation Alarm is present on Node

11. Equipment failure Alarm is present on Node
12. Equipment partial failure Alarm is present on Node
13. Connectivity between ORM card in ORM node and Previous card in Previous node is incorrect.
Quitting...
14. Not able to Lock card properly. Quitting...
15. Not able to Unlock card properly. Quitting...
16. ORM Pumps are not in stable state... Quitting...
17. Input Power to Previous node is not stable. Quitting...
18. Point Loss Set to Extreme, Cannot improve link further. Quitting...
19. Unable to change the PL Offset. Quitting...

20. Unable to change the LP Offset. Quitting...

21. System already reached Maximum Supported Launch Power Offset Limit
22. ORM Input Power is very less. Do you want to continue (y/n)?
23. Not able to Retrieve Point Loss Offset value from ORM Card at ORM Node
24. TL1 Object Initialization Failure
25. Error while reading excel sheet
26. Node Names are not in proper order

Setting the Target Gain Offset

Note: Contact an Infinera TAC resource to obtain the specific target gain offset value to be
entered prior to performing this procedure.
Perform the following procedure to manually adjust the target gain offset for a Raman module.
Step 1 Launch Infinera GNM and establish GNM connectivity with the node. Refer to “Launching Infin-
era GNM” on page 16-17.
Step 2 From the Equipment View, highlight the configured RAM, right-click and select Properties. The
RAM Properties window is displayed.
Step 3 In the RAM State tab, select Admin State -> Maintenance.
Step 4 Click Apply.
Step 5 In the Summary panel, enter the Target Gain Offset. The allowable range for the target gain off-
set value is +/-2.0dB from the default gain set point based on fiber type and Raman module
deployed. See “Raman Target Gain Offset” on page 17-19 for additional information.
Step 6 Click Apply.
Step 7 Click Close.
Figure 17-62 Setting the RAM Target Gain Offset
Target Gain Offset value

Page 17-88 Setting the Target Gain Offset

CHAPTER 18
Turning up a Multi-chassis Network

Element with Raman Amplification
(MTC-9 based)
This chapter provides the procedures to turn up and test an MTC-9 based multi-chassis network element
configured with Infinera Line System (ILS) Raman Amplifier (IRM) modules. (For an OTC based multi-
chassis network element, refer to “Turning up a Multi-chassis Network Element with Raman Amplification
(OTC based)” on page 17-1).
“IRM Turn-up and Test Overview” on page 18-4
“IRM Turn-up and Test” on page 18-9
“Setting the Point Loss Offset for IRM Modules” on page 18-16

Page 18-2
Figure 18-1 Front View MTC-9

PEMs
PEM
A/B
PWR
IOP
FLT
AIRFLOW DIRECTION
6
5
IAMs/IRMs/
DIRECTEMENT AVEC
NE PAS REGARDER
DES INSTRUMENTS
LASER PRODUCT
INVISIBLE LASER
LASER INVISIBLE
PRODUIT LASER
DIRECTLY WITH
RAYONNEMENT
INSTRUMENTS
DO NOT VIEW
1525-1565 nm
RADIATION
OPTIQUES
CLASS 1M
OPTICAL
135 mW
FRMs/FSMs
4
FRM-9D-R-8-EC
3
DIRECTEMENT AVEC
NE PAS REGARDER
DES INSTRUMENTS
LASER PRODUCT
INVISIBLE LASER
LASER INVISIBLE
PRODUIT LASER
DIRECTLY WITH
RAYONNEMENT
INSTRUMENTS
DO NOT VIEW
1525-1565 nm
RADIATION
OPTIQUES
CLASS 1M
OPTICAL
135 mW
2
IRM-B-ECXH1
infn_1296
Note: Figure 18-1 shows one example of an MTC-9 configured with an IRM and an FRM. The
MTC-9 may also house other modules (for other types of configurations) such as IAMs
and/or FSM/FSEs. Refer to “General Guidelines” on page 18-4 for restrictions regarding
MTC-9 configurations.

Turning up a Multi-chassis Network Element with Raman Amplification (MTC-9 based) Page 18-3
Tasks
table to keep track of the tasks you have completed and to record test results.
Table 18-1 Raman Turn-up Checklist and Test Results
“IRM Turn-up and Test Overview“ page

18-4
18-4
“Tools, Test Equipment, and Fiber page
Cleaning Supplies“ 18-5
“Fiber Plant Preparation“ page
18-5
“Minimum Equipment Configuration“ page
18-6
“Initial Commissioning of Network Ele- page
ments“ 18-6
“IRM Turn-up and Test“ page
18-9
“Setting the Point Loss Offset for IRM page
Modules“ 18-16

Page 18-4 IRM Turn-up and Test Overview
IRM Turn-up and Test Overview

CAUTION
and Class 1M.
CAUTION
Do not manually disable Automatic Laser Shutdown (ALS) unless specifically instructed to
do so. Disabling ALS may endanger personnel and/or equipment.
CAUTION
IRM modules generate large and potentially dangerous optical power levels. Ensure that
you are familiar with the safety procedures described in “Observing Safety Procedures” on
page 1-1.
CAUTION
ing” on page D-1.
General Guidelines
The following hardware equipment is required to provide Raman amplification in both directions:
 Two MTC-9s
 Two IMMs
 Two IRMs
Configuration Guidelines
An MTC-9 configured as part of a FlexILS ROADM node can house IMMs, FRMs, FSM/FSEs, IAMs,
and/or IRMs
An MTC-9 configured as part of a FlexILS Optical Line Amplifier node can house IMMs, IAMs, and/or
IRMs only (FRMs and FSM/FSEs are not supported on FlexILS Optical Line Amplifier nodes)

Tools, Test Equipment, and Fiber Cleaning Supplies

Ensure that you have the necessary tools, test equipment, and fiber cleaning supplies as outlined in
“Required Tools and Test Equipment” on page 2-5.
Fiber Plant Preparation

Ensure that the fiber plant does not have excessive point losses particularly in the first few kilometers of
fiber connected to the IRM Line In/Out ports.
Proper operation is not specified for higher point losses. High point losses, especially in the form of dirty
fiber connectors, may lead to permanent damage of the fiber connectors, fibers, and/or the IRMs. Point
losses often manifest themselves through dirty fiber connectors, poor patch panel connections, and high
splice losses.
Infinera recommends that the number of fiber connections between the IRMs and the transmission fiber be
kept to a minimum. When possible, a direct fiber connection from the IRMs to the outside plant fiber is
preferred. Care should also be taken to minimize bend losses and stress in the fiber plant between the
IRMs and the outside fiber plant (the Infinera specification for minimum fiber bend radius is 25mm).
Note: Infinera strongly recommends the use of bend insensitive fiber (BIF) for all fiber connec-
tions (whenever possible). BIF cables provide greater resistance to bending losses due to
Note: Operating the system with point losses above 0.5dB is not recommended and the link per-
formance is not guaranteed.
Ensure that all connectors between the IRMs and the actual line fibers are cleaned, inspected, and
properly connected throughout all involved patch panels. Refer to “Raman Fiber Connector Cleaning” on
page D-1.


Before proceeding with the turn-up and test of IRMs, ensure that all nodes involved in the configuration
have been initially commissioned as Main Chassis and Expansion Chassis where applicable. When
performing this procedure, refer to Figure 18-3 on page 18-9.
Initial Commissioning of Network Elements

 Node A - XTC turned up as a DTN-X ROADM Multi-chassis network element. Refer to “Turning up a
DTN-X ROADM Multi-chassis Network Element” on page 6-1
Main Chassis (XTC-10/XTC-4 base chassis) with one (or more) tunable FlexChannel line mod-
ules (AOFM-500/AOFM-500B/AOFX-500/AOFX-500Bs) installed
Expansion Chassis (MTC-9 base chassis) with one FRM and one IRM installed
Note: A base MTC-9 chassis contains at least one IMM.
An FPC with a minimum of one (or more) FSP-C modules
 Node B - MTC-9 turned up as a FlexILS Optical Line Amplifier network element. Refer to “Turning up
a FlexILS as a GNE” on page 7-1
Main Chassis (MTC-9 base chassis) with two IRMs available for installation (but not physically
installed in the chassis); this will be performed during the IRM turn-up and test procedure
 Node C - XTC turned up as a DTN-X ROADM Multi-chassis network element. Refer to “Turning up a
DTN-X ROADM Multi-chassis Network Element” on page 6-1
Main Chassis (XTC-10/XTC-4 base chassis) with one (or more) tunable FlexChannel line mod-
ules (AOFM-500/AOFM-500B/AOFX-500/AOFX-500Bs) installed
Expansion Chassis (MTC-9 base chassis) with one FRM and one IRM installed
An FPC with a minimum of one (or more) FSP-C modules

External Indicators and Connectors

The IRM faceplate provides the circuit pack status/port LED indicators, and line/port connectors as shown
in Figure 18-2.
Figure 18-2 IRM-B-ECXH1 Faceplate
INVISIBLE LASER
RADIATION
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
RAYONNEMENT
Laser Safety Warning Label LASER INVISIBLE
(located on shutter dust cap) NE PAS REGARDER
DIRECTEMENT AVEC
DES INSTRUMENTS
System Port Line Port Line Port OPTIQUES
LEDs LED (LOS) LED (ACT) LASER PRODUCT
(ACT, LOS) PRODUIT LASER
CLASS 1M
OSA Line Input/ System Input/ 1525-1565 nm
Output Output Line Output 135 mW
Connectors Connectors Connector Warning Label
SYSTEM
LINE
OTDR
OSA
DIRECTEMENT AVEC
NE PAS REGARDER
DES INSTRUMENTS
LASER PRODUCT
INVISIBLE LASER
LASER INVISIBLE
PRODUIT LASER
ACT
LOS
DIRECTLY WITH
RAYONNEMENT
INSTRUMENTS
DO NOT VIEW
1525-1565 nm
LOS
ACT
RADIATION
OPTIQUES
CLASS 1M
OPTICAL
135 mW
OTDR Input/
LINE
OSA
Output
Connectors
OSA
SYS
(not supported)
PWR
ACT
FLT
CLEI S/N IRM-B-ECXH1
PWR, ACT, FLT

OSA System Line Input Connector
Ejector (with integrated
Circuit Pack Output Connector Captive
Status LEDs shutter dust cap) Ejector
Screw infn_1157

Raman/EDFA Gain and Span Loss Support for IRM

Table 18-2 lists the amount of Raman and EDFA gain provided by the IRM and the supported span loss
range based on fiber type.
Table 18-2 IRM Maximum Gain and Span Loss Specifications
IRM Type Fiber Type Maximum Maximum Span Loss

Raman Gain EDFA Gain Range
(dB) (dB) (dB)
IRM-B-ECXH1 SMF, Pre-1993 5.0 to 14.0 11.5 to 21.0 16.5 to 35.0

SMF, AllWave,
Pure Silica Core
Original LEAF, 5.0 to 17.0 11.5 to 21.0 16.5 to 35.0
E-LEAF, TeraLight
MetroCor, TW-C, 7.0 to 17.0 11.5 to 21.0 16.5 to 35.0
TW-RS, TW Plus,
LS, DSF

IRM Turn-up and Test

When performing this procedure, refer to Figure 18-3. The IRMs installed in Node A and Node C
(Expansion Chassis, MTC-9 slot 1) are referred to as AID 2-A-1, and the IRMs installed in Node B (Main
Chassis, MTC-9 slots 1 and 4) are referred to as card AID 1-A-1 and AID 1-A-4 respectively.
Figure 18-3 Raman Deployment using IRM Modules

XTC XTC
AOFX-500s
AOFX-500s
AOFM-500/
AOFM-500/
SCh SCh
IN/OUT IN/OUT
SYSTEM LINE LINE

IN/OUT IN OUT
Main Chassis IRM Main Chassis
FPC FPC
LINE AD LINE AD
IN/OUT IN/OUT IN/OUT IN/OUT
Expansion Chassis Main Chassis Expansion Chassis

MTC-9 MTC-9
SYSTEM LINE SYSTEM LINE

FRM IN/OUT IN/OUT IRM FRM IN/OUT IN/OUT
MTC-9 IRM IRM IRM

infn_1284
connections (as shown in Figure 18-3) are made while performing this procedure. Prior to
link turn-up and test, ensure that the fiber connectors used in the configuration are
checked for cleanliness prior to use, and the correct fiber provisioning steps have been
performed as specified in this procedure.

Page 18-10 IRM Turn-up and Test
To turn up an IRM configuration
Step 2 At Node A: provision the fiber type for the IRM in slot 1. Refer to “Provisioning Fiber Information”
on page 9-30.
Step 3 At Node C: provision the fiber type for the IRM in slot 1. Refer to “Provisioning Fiber Information”
on page 9-30.
Step 4 At Node A: lock the IRM in slot 1 using Infinera GNM.
Step 4a From the Infinera GNM Equipment view, right-click the IRM and select
Step 5 At Node C: repeat Step 4 and lock the IRM in slot 1.
Step 6 At Node B: label the fibers which will be used for the IRM system and line side connectors.
Check the fiber connectors for cleanliness, refer to “Raman Fiber Connector Cleaning” on
page D-1.
Note: A minimum of 50kms of fiber is required for connecting the IRM line side. Refer to
Table 18-2 on page 18-8 for supported span loss range.
Step 7 At Node B: pre-provision an IRM in slot 1 and lock it using Infinera GNM.
Step 7a From the Equipment View, right-click on slot 1 and select Pre-provision -> IRM.
Step 7b From the Equipment View, right-click the IRM and select Admin State -> Lock.
Step 7c Repeat Step 7a and Step 7b for the IRM in slot 4.
Step 8 At Node B: set the OSC IP address for the IRM in slot 1.
Step 8a From the Equipment View, right-click the IRM and select GMPLS Link...
The GMPLS Link Properties window is displayed. See Figure 18-4 on page 18-11.
Step 8b In the OSC/GMPLS Control panel enter the IP Address and Subnet Mask.
Step 8e Repeat Step 8a through Step 8d for the IRM in slot 4.
Step 9 At Node A: repeat Step 8 to set the OSC IP address for the IRM in slot 1.

Step 10 At Node C: repeat Step 8 to set the OSC IP address for the IRM in slot 1.
Figure 18-4 Setting the OSC IP Address
Step 11 At Node B: provision the fiber type for the IRM in slot 1. Refer to “Provisioning Fiber Information”
on page 7-33.
Step 12 At Node B: provision the fiber type for the IRM in slot 4. Refer to “Provisioning Fiber Information”
on page 7-33.
Step 13 At Node B: insert an IRM partially into the MTC-9.
Step 13a Remove the IRM from the ESD protected bag.
Step 13b Using your thumb and forefinger, squeeze the ejector handles on the IRM to unlatch
and open the ejector handles. Position the ejectors to the full open position (approxi-
mately 45 degrees).
Step 13c Align the IRM to the rail guides in slot 1 on the MTC-9 (the IRM is a triple-width
module requiring three adjacent slots).
Step 13d Slide the IRM in partially; ensure that the IRM is not fully seated against the back-
plane (the IRM must remain powered off).
Step 13e Repeat Step 13a and Step 13d for the IRM in slot 4.
Step 14 At Node A: set the FRM-to-IRM association.
Step 14a From the Equipment view, right-click the Line port of the FRM in slot 4 and select
Properties. The Band Port Properties window is displayed. See Figure 18-5 on
page 18-12.
Step 14b Click the General tab.
Step 14c Click the Provisioned Neighbor TP drop-down menu and select the appropriate
association.

Step 15 At Node C: repeat Step 14 to set the FRM-to-IRM association.
Figure 18-5 Setting the FRM-to-IRM Association
Step 16 At Node B: set the IRM-to-IRM association.

Step 16a From the Equipment view, right-click the System port of the IRM in slot 4 and select
Properties. The Band Port Properties window is displayed. See Figure 18-6 on
page 18-13.
Step 16b Click the General tab.
Step 16c Click the Provisioned Neighbor TP drop-down menu and select the appropriate
association.

Figure 18-6 Setting the IRM-to-IRM Association
Step 17 At Node A: connect system side to line side fibers between IRM slot 1 and FRM slot 4.
Step 17a Connect the IRM slot 1 SYSTEM OUT (Tx) to the FRM slot 4 LINE IN (Rx).
Step 17b Connect the FRM slot 4 LINE OUT (Tx) to the IRM slot 1 SYSTEM IN (Rx).
Step 18 At Node A: connect line side fibers between Node A MTC-9 and Node B MTC-9.
Step 18a From IRM slot 1 LINE OUT (Tx) to IRM slot 4 LINE IN (Rx).
Step 18b From IRM slot 4 LINE OUT (Tx) to IRM slot 1 LINE IN (Rx).
Step 19 At Node B: connect system side fibers between IRM slot 1 and IRM slot 4.
Step 19a Connect the IRM slot 1 SYSTEM OUT (Tx) to the IRM slot 4 SYSTEM IN (Rx).
Step 19b Connect the IRM slot 4 SYSTEM OUT (Tx) to the IRM slot 1 SYSTEM IN (Rx).
Step 20 At Node B: connect line side fibers between Node B MTC-9 and Node C MTC-9.
Step 20a From IRM slot 1 LINE OUT (Tx) to IRM slot 1 LINE IN (Rx).
Step 20b From IRM slot 1 LINE OUT (Tx) to IRM slot 1 LINE IN (Rx).
Step 21 At Node C: connect system side to line side fibers between IRM slot 1 and FRM slot 4.
Step 21a Connect the IRM slot 1 SYSTEM OUT (Tx) to the FRM slot 4 LINE IN (Rx).
Step 21b Connect the FRM slot 4 LINE OUT (Tx) to the IRM slot 1 SYSTEM IN (Rx).
Step 22 At Node B: complete the IRM installation.
Step 22a Gently push the IRM slot 1 toward the backplane until it stops. Do not use force.
Step 22b Close the left and right ejectors simultaneously.
Step 22c Tighten the captive screw using a #2 Phillips screwdriver.
Step 22d Remove the cleaning caution label using the thumb and forefinger to pull the adhe-
sive-backed portion of the label away from the high power connector.

Step 22e Repeat Step 22a and Step 22d for the IRM in slot 4.
Step 23 At Node A: unlock the IRM in slot 1 using Infinera GNM.
Step 23a From the Equipment View, right-click the IRM and select Admin State -> Unlock.
Step 23b Wait 3 minutes before proceeding to the allow the Raman pumps to turn on and sta-
bilize.
Step 24 At Node C: repeat Step 23 to unlock the IRM in slot 1.
Step 25 At Node B: repeat Step 23 to unlock the IRM in slot 1 and slot 4.
CAUTION
Do not physically remove the line side fibers from any of the IRMs involved in the
configuration while the Raman pumps are turned on.
Step 26 At Node A: verify neighbor connectivity with Node B (IRM in slot 4).
Step 26a From the Equipment View, right-click the IRM in slot 1 and select Span. The Span
Properties window is displayed. See Figure 18-7.
tab.
Step 26c Verify that the Node ID listed corresponds to Node B and the OTS ID of the Node B
IRM is displayed correctly (i.e. 2-A-4-L1).
Step 27 At Node B: repeat Step 26 to verify neighbor connectivity with Node A (IRM in slot 1).
Step 28 At Node B: repeat Step 26 to verify neighbor connectivity with Node C (IRM in slot 1).
Step 29 At Node C: repeat Step 26 to verify neighbor connectivity with Node B (IRM in slot 1).
Step 30 Proceed to “Setting the Point Loss Offset for IRM Modules” on page 18-16.

Figure 18-7 Verifying Neighbor Connectivity
Neighbor
Connectivity tab
Discovered
Node ID

Page 18-16 Setting the Point Loss Offset for IRM Modules
Setting the Point Loss Offset for IRM

Modules
WARNING
The point loss offset must be recalculated (on all affected IRM modules) whenever the
lowing conditions:
1. Whenever the link is restored after a fiber cut or an IRM line side fiber reconnection
within 50kms from where the IRM pump enters the transmission fiber.
3. Whenever an IRM is removed and replaced with a different IRM.
WARNING
Operating IRMs without proper point loss offset settings may severely degrade the link per-
formance.
Note: The IRMPLO.jar file, referred to as IRM point loss offset (PLO) adjustment utility, is distrib-
uted with Infinera DNA but requires Infinera GNM to execute (point loss offset adjustments
are not supported using Infinera DNA). If you do not have access to Infinera DNA and/or
the IRMPLO.jar file, contact an Infinera TAC resource for further assistance.
The purpose of this procedure is to provide instructions for setting the point loss offset on IRMs to reach
the target gain. The IRM PLO adjustment utility is initiated through Infinera GNM and supported for IRMs in
the following configurations:
 Inline amplifier (IRM-B-ECXH1)
 Preamplifier (IRM-B-ECXH1)


Prerequisites
Note: This procedure can only be performed by users that have the appropriate privileges. Refer
to “Setting Up User Accounts with Turn-up and Test Privileges” on page 6-59 for more
details.
1. Completion of the IRM turn-up procedure. Refer to “To turn up an IRM configuration” on page 18-
10 for more details.
2. Access to Infinera DNA (the IRM PLO adjustment utility is distributed with Infinera DNA).
3. At least one FlexChannel line module (AOFM-500/AOFM-500B/AOFX-500/AOFX-500B) with eight
(8) active channels (or greater) must be present in the system to provide C-Band signals to mea-
sure Raman gain.
5. The launch fiber type must be provisioned correctly on all fiber spans. The IRM PLO adjustment
utility will attempt to confirm proper fiber connection and quit if the connection is not properly con-
figured or if the information provided does not match the link information.
Link power levels. The IRM PLO adjustment utility will attempt to check for power changes but
there is no guarantee that transients will be captured by the utility.
8. All log files should be saved for failure analysis. Ensure that the IRM debugXfr log information is
collected from the network elements installed in the span as well as the Log.txt file whenever a fail-
ure occurs during IRM PLO adjustment utility execution.
9. In rare cases, it may be necessary to reduce the maximum configured channel count to a lower
value. However, the value has to be greater than or equal to the actual channel count. The channel
count configuration can be reset to the original value after the IRM PLO adjustment utility has com-
pleted. This assures that there is no IRM saturation issue. After the point loss offset is set, any
channel count configuration will be supported by the IRM. Refer to “Overview” on page 18-18 for
more details.

Overview
1. The IRM PLO adjustment utility is initiated through Infinera GNM.
2. The IRM PLO adjustment utility must not be executed simultaneously on a particular optical span.
3. The IRM PLO adjustment utility displays an error message if the required point loss offset is outside
the range of -0.5 to +0.5dB. The error message will suggest that the user clean the fiber connec-
tions involved in the link.
4. The IRM PLO adjustment utility will calculate and set the point loss offset within the range of -0.5 to
+3dB. If the span requires the point loss offset to be outside the allowed range, an error message
will be displayed.
5. If an error occurs during execution of the IRM PLO adjustment utility, the utility will restore the link
settings back to the original/initial settings. This includes the following:
Reset the Launch Power Offset of the modules in previous nodes.
Reset the IRM point loss offset to the original values.
Set the Admin State for all IAMs and/or IRMs involved in the turn up to the Unlocked state.
6. When the IRM is locked, its input power should be within the photodetector (PD) dynamic range
specifications (≥ -19dBm for IRM-B-ECXH1).
If the power is below the dynamic range, the launch power of previous nodes will be increased to
bring the IRM input power within the dynamic range.
If the IRM PLO adjustment utility is still unable to bring the IRM input power above the required
power levels, a prompt is displayed with an option to terminate the utility or continue.
To continue with the IRM PLO adjustment utility, reduce the maximum configured channel count
to a lower value (which must be greater than or equal to the actual channel count), wait for one
AGC cycle (approximately 7 minutes), and then continue with the utility.
7. For each IRM, the average time for IRM PLO adjustment utility execution is approximately 10 min-
utes (for the initial iteration) and 5 minutes for each additional iteration. The utility no longer limits
the maximum change of the point loss offset per iteration. All utility actions are logged in the Log.txt
file.
8. After the IRM PLO adjustment utility completes, any outstanding alarms (mainly Equipment) or con-
ditions in the span will be highlighted for debugging.
9. Log files are created to ensure that any failures can be debugged and any extraneous circum-
stances can be identified. The IRM PLO adjustment utility will either continue or terminate properly
after error condition notification.

To set the point loss offset for IRM modules
When performing this procedure, refer to Figure 18-8. The IRMs installed in Node A and Node C
(Expansion Chassis, MTC-9 slot 1) are referred to as AID 2-A-1, and the IRMs installed in Node B (Main
Chassis, MTC-9 slots 1 and 4) are referred to as card AID 1-A-1 and AID 1-A-4 respectively.
The IRM PLO adjustment utility should be executed on nodes installed in the West direction toward the
East. Once completed, the utility should be repeated for nodes in the East direction toward the West.
Alternatively, the IRM PLO adjustment utility can be executed on nodes installed in the East direction
toward the West and then be repeated with nodes installed in the West direction toward the East.
Figure 18-8 Example IRM Turn-up Reference Diagram

XTC XTC
AOFX-500s
AOFX-500s
AOFM-500/
AOFM-500/
SCh SCh
IN/OUT IN/OUT
SYSTEM LINE LINE

IN/OUT IN OUT
Main Chassis IRM Main Chassis
FPC FPC
LINE AD LINE AD
IN/OUT IN/OUT IN/OUT IN/OUT
Expansion Chassis Main Chassis Expansion Chassis

MTC-9 MTC-9
SYSTEM LINE SYSTEM LINE

FRM IN/OUT IN/OUT IRM FRM IN/OUT IN/OUT
MTC-9 IRM IRM IRM
infn_1295
East to West Direction
Note: The IRM turn-up procedure must be completed prior to performing this procedure. Refer to
“To turn up an IRM configuration” on page 18-10.

Step 2 At Node A: initiate the point loss offset process for the West to East direction starting with the
IRM in slot 1. See Figure 18-8 on page 18-19.
Step 2a From Infinera GNM, right-click the IRM in slot 1 and select Admin State -> Mainte-
nance.
Step 2b From Infinera GNM, right-click the IRM in slot 1 and select Adjust Point Loss ->
Span. The IRM Turnup window is displayed.
Figure 18-9 IRM Point Loss Offset (PLO) Adjustment - Initiated through Infinera GNM
The Span menu option provides point loss offset adjustment for all IRMs installed in the same
direction of the optical span in a sequential order. The turn up action is taken in only one direction
of the span (the direction that is facing the IRM) and must be repeated for the opposite direction
of the span. The Link menu option provides point loss offset adjustment for a single IRM.

Figure 18-10 IRM Turn-up Window
Note: The GNE IP Address field is user editable (from the IRM Turn-up window). (This field does
not change the DCN IP address.) This feature provides additional flexibility during execu-
tion of the IRM PLO adjustment utility in the event that DCN connectivity is not available.
For example, the user can set the GNE IP address to the value currently assigned to the
Craft IP port. However, ensure that the GNE IP address is reset back to the previously
assigned value upon successful completion of the utility. For SNE nodes the default value
will display a GNE IP Address of 0.0.0.0. This IP address will need to be changed to the
DCN IP address of either the primary or secondary GNE that the SNE uses for file trans-
fers.
Note: If the IRMPLO.jar file is not present in the default location, a Browse button is shown (adja-
cent to the Run button) indicating that the IRMPLO.jar file could not be located (the
Browse button is shown only if the file cannot be located). Click the Browse button and
provide the path to where the file is located.
Step 3 In the IRM Turn-up window, click Browse. The Open... window is displayed.
Figure 18-11 IRMPLO.jar File Location
Step 4 In the Open... window, navigate to the directory where IRMPLO.jar is located.

Note: The IRMPLO.jar file is distributed with Infinera DNA. Refer to the Infinera DNA Administra-
tor Guide for additional information. If you do not have access to Infinera DNA and/or the
IRMPLO.jar file, contact an Infinera TAC resource for further assistance before proceeding.
Step 5 Select IRMPLO.jar and click Open.

Step 6 In the IRM Turn-up window, click Run. A warning message dialog box is displayed indicating that
the IRM PLO adjustment utility is about to execute. Click Continue.
The IRM Turn-up Tool introduction screen is displayed.
Note: The term “IRM Turn-up Tool” refers to the IRM PLO adjustment utility.
Figure 18-13 IRM Turn-up Tool Introduction Screen
Step 7 Click Ok. The Configuration Details window is displayed.

Figure 18-14 Configuration Details
Step 8 In the Configuration Details window, click Apply to all NE. The Config User window is dis-
played.
Figure 18-15 Config User
Step 9 In the Config User window, perform the following:

Step 9a Click the TL1 User Name check box and enter the TL1 user name information.
Step 9b Click the TL1 Password check box and enter the TL1 password information.
Step 9c In the TL1 Re-Confirm field, re-enter the TL1 password information.
Step 9d Click the ACLI Password check box and enter the ACLI password.
Step 9e In the ACLI Re-Confirm field, re-enter the ACLI password information.

Figure 18-16 Config User - Example
Step 9f Click Apply. The Configuration Details - Complete window is displayed with the
TL1 User, TL1 Password, TL1 Confirm Password, ACLI Password, and ACLI Confirm
Password fields filled in for all nodes in the link.
Figure 18-17 Configuration Details - Complete
Step 10 In the Configuration Details - Complete window, click Execute.

Step 11 A confirmation message dialog box is displayed indicating that the IRM PLO calibration is about
to execute. Click Ok.

Figure 18-18 Confirmation Message
The Configuration Details - Execution window is displayed showing details of the IRM PLO
adjustment utility execution.
Note: The IRM PLO adjustment utility initially sets the PLO to zero (0) on each IRM prior to calcu-
lating new values.
Figure 18-19 Configuration Details - Execution
Optional: to abort the IRM PLO adjustment utility during execution, click Abort. A confirmation
message dialog box is displayed. Click Yes.

Figure 18-20 Configuration Details - User Abort
Note: Refer to “Additional Abort Scenarios” on page 18-28 for information regarding additional
abort scenarios.
Step 12 If any errors are encountered during execution of the IRM PLO adjustment utility, verify network
connectivity or resolve the issue prior to executing the utility again. Refer to “Error and Warning
Messages” on page 18-29 for typical errors and/or warning messages. If no errors are encoun-
tered during execution of the utility, the point loss offset will be set for IRMs in each span in the
direction being turned up (for example, the IRMs installed in Node B and C in the West to East
direction, or the IRMs installed in Node B and A in the East to West direction. Refer to Figure 18-
8 on page 18-19).
Optional: when an error occurs, the IRM PLO adjustment utility performs a cleanup operation
(graceful shutdown) and closes the session. The user can either close the window or rerun the
utility (without closing the window) by selecting View -> Configure User. See Figure 18-21 on
page 18-27.

Figure 18-21 Configuration Details - Configure User Feature
WARNING
Do not reset XCMs, IMMs, IAMs, IRMs, and/or FRMs while the IRM PLO adjustment utility
is executing. Ensure that the link is stable and that no configuration changes (such as
XCM/IMM/IAM/IRM/FRM warm reboots, cold reboots, lock/unlock of line cards, and/or SCh
add/drops) are made during point loss offset calculation/adjustment.
Step 13 In the Configuration Details window, click Close.

Step 14 Click Yes.
Step 15 At Node C: repeat Step 2 through Step 14 for all IRMs in the East to West direction. Refer to
WARNING
The point loss offset must be recalculated (on all affected IRMs) whenever the span loss
changes +/-2dB after initial turn-up and service is impacted. Infinera recommends that the
point loss offset be recalculated during a maintenance window for the following conditions:
1. Whenever the link is restored after a fiber cut or an IRM line side fiber reconnection
within 50kms from where the IRM pump enters the transmission fiber.
3. Whenever an IRM is removed and replaced with a different IRM.

Additional Abort Scenarios

When the IRM PLO adjustment utility is closed abruptly or aborted, it is recommended that a cleanup
operation (graceful shutdown) be performed when prompted (by clicking Yes) as shown in the following
examples:
Figure 18-22 Confirmation Message - Abrupt Close
Figure 18-23 Confirmation Message - Abrupt Close, Start Next Execution


Typical errors and/or warning messages displayed during execution of the IRM PLO adjustment utility are
listed in Table 18-3.
Note: The IRM PLO adjustment utility will only display the following errors and/or warning mes-
sages if an error is encountered during execution; the utility does not check for any other
conditions. Ensure that the link is stable and that no configuration changes (such as XCM/
IMM/IAM/IRM/FRM warm reboots, cold reboots, lock/unlock of line cards, and/or SCh add/
drops) are made during point loss offset calculation/adjustment.
Error/Warning IRM PLO Adjustment

Incomplete control link This error message is displayed if the control link infor- Restore the link settings
information mation is incomplete. back to the original/initial
GNE IP incomplete This error message is displayed if the GNE IP informa- settings and exit the utility.
tion field is empty.
TL1/ACLI login details This error message is displayed if the utility detects the
incomplete login information fields are empty.
Invalid card AID This error message is displayed if an invalid card AID is
detected by the utility.
Peer card association is This error message is displayed if the Raman associa-
not present tion with an IAM/IRM/FRM has not been set.
IRM cards are not book- This error message is displayed for the transmit (Tx) and
ended receive (Rx) nodes if the IRM cards are not bookended.
Incomplete last utility This error message is displayed if the utility detects that Prompt for user confirma-
execution the last utility execution was unsuccessful. tion to restore the link set-
tings back to the original/
initial settings and continue.
Cannot read input XML This error message is displayed if the utility is unable to Restore the link settings
file read the XML file correctly or the XML file is not in the back to the original/initial
correct format. settings and exit the utility.
Rx fiber type is This error message is displayed if the utility detects that
unknown the receive (Rx) fiber type is unknown. This can occur if
Infinera’s AGC/ADAPT did not run successfully prior to
utility execution.
Card in OLOS This error message is displayed if the utility detects that Attempt to unlock any
a card is in an OLOS state. locked cards and recover
from OLOS.

Error/Warning IRM PLO Adjustment

Equipment fault present This error message is displayed if the utility detects that Restore the link settings
a card is in a faulted state. back to the original/initial
OSC fault present This error message is displayed if the utility detects that settings and exit the utility.
a card in the span is exhibiting OSC failure.
Unable to login to the This error message is displayed if the utility is unable to
NE create a session with the NE.
Unable to reconnect to This error message is displayed if the utility is unable to
the NE re-connect to the NE after disconnect.
TL1/ACLI object initial- This error message is displayed if the utility is unable to
ization failed initialize the TL1 object.
Card unreachable This error message is displayed if any of the cards are
unreachable during utility execution.
Card not present This error message is displayed if the utility detects that
the required cards (IAM, IRM, and/or FRM) are not pres-
ent.
Point loss offset is OOR This error message is displayed if the utility detects that Prompt for user confirma-
the calculated PLO is outside the range of -0.5 to 3.0dB. tion and cap it to the maxi-
This error message is also displayed if the utility detects mum value.
that the calculated PLO is outside the range for the
deployed fiber type.
Unable to come out of This error message is displayed if the Raman card does Restore the link settings
OLOS not come out of OLOS after unlock operation. back to the original/initial
Unable to lock card This error message is displayed if the utility is unable to settings and exit the utility.
lock the card during execution.
Unable to unlock card This error message is displayed if the utility is unable to
unlock the card during execution.
Unable to retrieve PM This error message is displayed if the utility is unable to
for the card retrieve PM data for the card.
Unable to retrieve card This error message is displayed if the utility is unable to
details retrieve card details (i.e. Rx fiber type, Admin state, etc.)
for the card.
Power instability This error message is displayed if the utility detects that Restore the link settings
power has become unstable during utility execution. back to the original/initial
settings, prompt user to
rerun utility, and exit.

Appendix A
Optional Configuration
The following sections describe the optional configuration procedures you may perform during the turn-up.
“Configuring the Alarm Severity Assignment Profile” on page A-2
“Configuring the Network Element Date and Time” on page A-4
“Configuring the Security Parameters” on page A-6
“Configuring the PM Thresholds” on page A-13
“Configuring the Enhanced Security Settings” on page A-16
“Configuring the Launch Power Offset for BMM/OAM/ORM” on page A-17

Page A-2 Configuring the Alarm Severity Assignment Profile
Configuring the Alarm Severity Assignment

Profile
All alarms generated are assigned factory-set default severity and service affecting values. The factory-
default values can be edited using the Alarm Severity Assignment Profile (ASAP) feature.
The ASAP feature can be used to customize the following attributes:
 Severity
Affects Chassis LED
The Alarm Severity Assignment Profile (see Figure A-1) is edited from the Alarm Severity
Assignment Profile Settings window.
Figure A-1 Alarm Severity Assignment Profile

Profile table
Profile Attributes
To edit the Alarm Severity Assignment Profile
Step 1 In the Infinera GNM Main View, select Fault Management > Alarm Severity Profile Settings.
The Alarm Severity Assignment Profile Settings window is displayed.
Step 2 Select alarm object. The attributes are displayed in the Profile Attributes panel.
Step 3 Select the new severity from the Severity list.

Optional Configuration Page A-3
Step 4 Check Affects Chassis LED if the LED should be lit when the alarm is raised. Otherwise, leave
the check-box blank.
Step 6 When you are done, click Close to exit the Alarm Severity Assignment Profile Settings win-
dow.

Page A-4 Configuring the Network Element Date and Time
Configuring the Network Element Date and

Time
You can configure the network element for the following:
 Derive the current date and time from a reference source using network time protocol (NTP)
 Ensure proper ordering of alarms and events at both the network element and network-level
 Configure the network elements to synchronize the date and time to a reference source
Alternatively, you can manually configure the current date and time. The network element maintains the
local time using a local clock with the stability of 23ppm or about a minute per month (if left free running
without syncing to an external NTP server). For purposes of the NTP protocol, the MCM/OMM local clock
is designated as a Stratum 5 clock.
The network element can operate both as a NTP client (deriving the current time from an external source)
and as a NTP server, providing NTP services to other network elements within the same routing domain.
Note: You must take care when setting up NTP references within the network to make sure that
the timing references are consistent. In a typical configuration, a GNE network element is
configured to derive current time from an external NTP reference; all other network ele-
ments within this routing domain are set to use the GNE network element as a NTP refer-
ence.
To set the date and time using the external NTP server
Step 1 In the Infinera GNM Main View, select Configuration > Network Element. The Network Ele-
ment Properties window is opened.
Step 2 In the Network Element Properties window, click DateTime tab.
Step 3 In the NTP Server, select Enable.
Step 4 Specify the IP addresses of the NTP server; for a GNE specify the IP address of an external NTP
server located outside your network. For an SNE, specify the Router ID of a specific GNE within
the same routing domain providing NTP service.
Note: Setting the NTP Server address on a GNE to its own Router ID or DCN IP address could
cause the MCM to lock. Ensure the correct external NTP Server IP Address is entered
before clicking Apply.

Step 6 When you are done, click Close to exit the Network Element Properties window.

To configure the date and time manually
Step 1 In the Infinera GNM Main View, select Configuration > Network Element. The Network Ele-
ment Properties window is opened.
Step 2 In the Network Element Properties window, click Date Time tab.
Step 3 In the NTP Server, deselect Enable.
Step 4 In the DateTime, click [...]. The Calendar is displayed.
Step 5 Set the Date and Time. Click Apply.
Step 6 When you are done, click Close to exit the Network Element Properties window.

Page A-6 Configuring the Security Parameters
Configuring the Security Parameters

The following sections provide valuable information for managing the security parameters on the DTN
during the turn-up and test procedure. Refer to the Infinera DTN and DTN-X GNM Security Management
Guide for further information.
Changing Password at Initial Login

A change password request is prompted when any one of the following occurs:
 You are logging in for the first time
 The Security Administrator has changed your account password
To change the password at initial login
Step 1 In the browser, type the IP address of the DTN that you want to access.
Step 2 In the Login dialog box, enter the following:
User Name
Password
The Security Message dialog box is displayed.

Step 3 Click OK to continue. The Change Password window is displayed.
Figure A-2 Password Configurator
Step 4 Enter the current and new passwords.

Step 5 Click Apply to save the changes. A confirmation message is displayed.
Step 6 Click OK to continue.

Changing Your Account Password

The password for an user account can be changed at any time.
To change your own password
Step 1 Log into Infinera GNM with your user ID and password.
Step 2 Select Security > Change Password. The Change Password window is displayed.
Step 3 Specify:
Current Password
Enter New Password—User password which meets these requirements:
The password must contain 6 to 10 alphanumeric characters and at least one alphabetic
and one numeric or special character
The password may contain these special characters: ! @ # $ % ^ ( ) _ + | ~ { } [ ] ? -
The password must not contain the associated user ID or blank spaces
The password is case-sensitive
Confirm New Password
Figure A-3 Change Password Configurator
Step 4 To save the changes, click Apply. A success message is displayed.

Step 5 Click OK.
The password for your account has now been changed. The new password will take effect the next time
you log into Infinera GNM.

Changing the Account Password to the Network Element Default

Password
Security administrator can reset the user password to the network element default password at any time.
The new password takes effect at next user log in.
To change the user password to the default password

displayed.
Step 3 In the Tree View of the NE Security Administration window, select the user whose password
you want to reset.
Step 4 Right-click and choose Reset Password to System Default. A success message is displayed.
Figure A-4 Reset Password to Default
Step 5 Click OK.

The password for the user account is set to the network element’s default password. The new password is
valid only from consecutive login session.

Changing the Password Expiry Period
To change the expiry period of the password

Step 2 From the Infinera GNM Main Menu, select Security > NE Security Administration. The NE
Security Administration window is displayed.
Step 3 In the tree structure, select the user account name for which the password expiry time must be
changed. The details of the user account are displayed.
Step 4 Select the Password tab to view the password details.
Figure A-5 NE Security Administration - Password Expiry
Step 5 Check Need to Change Password if the password must be changed.

Step 6 Edit the value of the password expiry age in the Password Expiry Age (days) field. The pass-
word expiry age can vary from 0 to 999 days.
Step 7 Click Apply to save the changes. A success message is displayed.
Step 8 Click OK.

Changing the Maximum Number of Invalid Login Attempts

The network element maintains a count of the maximum number of invalid attempts. If the number of
attempts made by the user exceeds the Max Invalid Login Attempts count, the user account is
temporarily locked for Max Invalid Login Lockout Period.
To change the count of maximum number of login attempts

Step 2 From the Infinera GNM Main View, select Security > NE-Wide Security Settings. The NE-Wide
Security Settings window is displayed.
Figure A-6 Network Element Wide Security Settings
Step 3 In the Intrusion Detection Settings panel, enter the number of attempts in the Max Invalid
Login Attempts field. The default value is 3.
Step 4 Enter the time period for which the user account is locked if the number of invalid attempts
exceeds the Max Invalid Login Lockout Period (secs). The default time period is 60 seconds.
Click Close to close the NE-Wide Security Settings window.

Changing the Password History Count

Users are encouraged to change passwords regularly in order to maintain the security of the system. The
DTN maintains a record of the previous passwords. The count of the number of passwords recorded is
configurable by the user and ranges from 1–5.
To change the password history count

Step 2 From the Infinera GNM Main View, select Security > NE-Wide Security Settings. The NE-
Wide Security Settings window is displayed.
Step 3 In the Password Settings panel, enter the count of passwords to be recorded in the Password
Reuse History Count. The maximum number of times the password can be reused is 5.
Step 4 To save the changes, click Apply. A success message is displayed.
Step 5 Click OK.
Step 6 When you have completed your updates, click Close to exit.
Changing the Network Element’s Default Password
To reset network element password to the default password

Step 2 From the Infinera GNM Main View, select Security >NE-Wide Security Settings. The NE-Wide
Step 3 In the Password Settings panel, click Set. The Change Default Password dialog box is dis-
played.
Figure A-7 Change Default Password
Step 4 Enter the new password.

Step 5 Click Apply to save the changes. The default password for the managed DTN is set to this
value.

Changing the Login Banner

A successful login results in the Informational Message displaying the Infinera Notice, Unsuccessful Login
Attempts and the Last Login Time. The Infinera Notice displayed is configurable and can be edited.
Figure A-8 Informational Message
To edit the login banner text

Step 2 From the Infinera GNM Main View, select Security > NE-Wide Security Settings. The NE-Wide
Step 3 In the Login Banner Settings panel, enter the text that you would like to display in the Informa-
tion Message window.
Step 5 When you have completed your updates, click Close to exit.
The new text is displayed in the Information Message window the next time you login.

Configuring the PM Thresholds

AOLM-500B, AOLX-500, AOLX-500B, SOLM-500, SOLX-500, AOLM2-500, AOLM2-
500B, AOLX2-500, AOLX2-500B, SOLM2-500, SOLM2-500B, SOLX2-500, and/or
SOLX2-500B (XTC only). All references to the "LM-80" will refer interchangeably to the
AXLM-80, ADLM-80 and/or SLM-80 (DTC/MTC only).
Thresholds are used to set error levels for each PM. PM threshold ranges can be set depending on what
values are to be monitored. During the accumulation cycle, if the current value of a performance
monitoring parameter reaches or exceeds its corresponding value, a threshold crossing alert (TCA) is
generated in the Event Log. These messages provide early detection of performance degradation. When a
threshold is crossed, the node continues to count the errors during a given accumulation period.
The threshold should be changed if the default value does not satisfy the error monitoring needs. You may
change the following:
 Near End—This button displays all PMs occurring for the selected card on the incoming signal
 Far End—This button displays all PMs recorded for the selected card on the outgoing signal as it
was received at the far-end
To change the threshold values for a line module
Step 1 From the Equipment View, right-click the line module for which you want to change thresholds.
Step 2 Select Optical Channels. The Optical Channel Properties window is displayed.

Page A-14 Configuring the PM Thresholds
Figure A-9 Optical Channel Properties
Step 3 In the PM Collection panel, check the Enable check-box.

Step 4 In the PM Configuration panel, enter the following values for 15 Minute or 24 Hr time intervals:
CV
ES
SES
Step 5 Select the relevant check-boxes in the 15Min Reporting and 24Hr Reporting columns if TCAs
are to be reported.
Step 7 When you are done, click Close to exit the Optical Channel Properties window.
The Status Bar at the bottom left corner of the Infinera GNM Main View displays the message Channel
Configuration Successful if the operation completed successfully. If it did not, you must repeat the
procedure.

To change the threshold values for a TOM
Step 1 From the Equipment View, right-click the TOM for which you want to change thresholds and
select Trib DTF Path. The DTF Path Properties window is displayed.
Step 2 Go to the PM Configuration tab.
Figure A-10 DTF Path: PM Configuration
Step 3 In the Rx DTF Path Threshold panel, enter the following values for 15 Minute or 24 Hr time
intervals:
CV
ES
SES
UAS
Step 4 Select the relevant check-boxes in the 15MinReporting and 24Hr Reporting columns if TCAs
are to be reported.
Step 6 When you are done, click Close to exit the DTF Path Properties window.
The Status Bar at the bottom left corner of the Infinera GNM Main View displays the message DTF Path
Updation Successful if the operation completed successfully. If it did not, you must repeat the procedure.

Page A-16 Configuring the Enhanced Security Settings
Configuring the Enhanced Security Settings

To enable SSHv2-based security for the network element

Step 2 From the Infinera GNM Main View, select Security >NE-Wide Security Settings. The NE-Wide
Figure A-11 NE-Wide Security Settings Window
Step 3 In the Enhanced Security Settings panel, check the appropriate box to enable SSHv2-based
security for the network element for each of the interface ports (that is, to protect communications
via TL1, Telnet, File Transfer or XML Agent). By default, enhanced security is not enabled.
Note: The SSH enhanced security feature may be enabled at any time. However, if the enhanced
security flag is updated during run-time, existing sessions continue to function in its earlier
mode. Any new established sessions will operate according to the new security setting. You
must perform a warm or cold reboot of the active MCM in order to effect the security
changes to existing sessions.

Configuring the Launch Power Offset for

BMM/OAM/ORM
Note: Do not configure the launch power offset unless consulted to do so by an Infinera Technical
Assistance Center (TAC) resource. The launch power offset should not require adjustment
after the initial turn-up and test of the Infinera network has been completed.
Note: This procedure assumes that the BMM/OAM/ORM has been previously turned up as part of
a newly deployed Infinera network and the deployment personnel performing this proce-
dure are familiar with Infinera GNM.
The BMM, OAM, and/or ORMs have a launch power offset feature that is user-configurable to offset the
standard transmit power of the EDFA laser.
To configure the launch power offset for a BMM, OAM, and/or ORM
Note: This procedure applies to all BMM/OAM/ORM types.
Step 1 From the Equipment View, highlight the appropriate base BMM/OAM/ORM, right-click and select
Step 2 From the Equipment View, highlight the appropriate BMM/OAM/ORM, right-click and select
Properties. The BMM/OAM/ORM Properties window is displayed. See Figure A-12 on page A-
18.
Step 3 In the Summary panel, enter the Launch Power Offset value. The supported range values are:
BMMs: -2.0 to +2.0dB/Ch (adjustable in 0.1dB increments)
BMM2P-8-CH1-MS/OAM/ORMs: -10.0 to +10.0dB/Ch (adjustable in 0.1dB increments)
Step 4 Click Apply.
Note: In a live network, when changing the launch power offset value, Infinera recommends that
you not implement a step size greater than 0.5dB/Ch per iteration. However, in an initial
turn-up any step size (within the supported range for the particular BMM/OAM/ORM) is
acceptable. If a value greater than 0.5dB/Ch is required, wait several minutes before mak-
ing any further changes.

Page A-18 Configuring the Launch Power Offset for BMM/OAM/ORM
Figure A-12 BMM Properties: Configuring the Launch Power Offset
Summary
panel
Launch Power
Offset Value
Step 5 A warning message dialog box is displayed indicating that changing the launch power offset
value may be service affecting. Click Continue.
Figure A-13 Warning Message
Step 6 Click Close.

Step 7 From the Equipment View, highlight the appropriate BMM/OAM/ORM, right-click and select

Appendix B
XCM/IMM/MCM/OMM Rebranding
Flow
This chapter displays the XCM/IMM/MCM/OMM Rebranding flow graphically. The flow chart (see
Figure B-1 on page B-2) represents the flow to rebrand an XCM/IMM/MCM/OMM.
The procedure to rebrand an XCM/IMM/MCM/OMM is similar for a single-chassis and multi-chassis
network element.

Page B-2 XCM/IMM/MCM/OMM Rebranding Flow Diagram
XCM/IMM/MCM/OMM Rebranding Flow

Diagram
Figure B-1 XCM/IMM/MCM/OMM Rebranding Flow
Insert first XCM/IMM/MCM/OMM
Chassis is already Yes XCM/IMM/MCM/OMM No

commissioned previously
configured?
Press Enter to
reconfigure or wait
for normal startup... Commission
Chassis
Reconfigure the
XCM/IMM/MCM/OMM
Commit
Commit
Branding does not
match NEID!!! Press
enter to continue
Press
enter
Did
XCM/IMM/MCM/OMM No
have a database
present?
Bring up
Restore database empty empty
Yes database or
restore?
Local Remote
Local/remote?
Foreign Database Select the tarball

detected - the from the list
Delete Reboot database seems to
belong to some other
network element
Delete/reboot? Provide the FTP
server information
Delete
Delete Rebrand
database or
rebrand?
System comes up infn_1199

Appendix C
Connecting and Routing Fiber Optic

and BNC Video Cables
This chapter provides procedures to connect and route fiber optic and BNC video cables in an
XTC/DTC/MTC/OTC:
“Connect and Route XTC Fiber Optic Cables” on page C-3
“Connect and Route MTC-9 Fiber Optic Cables” on page C-42
“Connect and Route FSP/FMP Fiber Optic Cables” on page C-44
“Connect and Route DTC/MTC Fiber Optic and BNC Video Cables” on page C-51
“Connect and Route OTC Fiber Optic Cables” on page C-91
AOLM-500B, AOLX-500, AOLX-500B, SOLM-500, SOLX-500, AOLM2-500, AOLM2-500B,
AOLX2-500, AOLX2-500B, SOLM2-500, SOLM2-500B, SOLX2-500, SOLX2-500B,
AOFM-500, AOFM-500B, AOFX-500, and/or AOFX-500B interchangeably. (XTC only). All

Page C-2
references to the "LM-80" will refer interchangeably to the AXLM-80, ADLM-80 and/or
SLM-80 (DTC/MTC only).
Note: Unless specifically noted otherwise, on a DTC/MTC/OTC, all references to the BMM will
refer to either the BMM, BMM2, BMM2P, BMM1H, BMM2H, and/or BMM2C interchange-
ably.
Note: Unless specifically noted otherwise, on a DTC/MTC, all references to the GAM will refer to
either the GAM-1 and/or GAM-2 interchangeably.

Connecting and Routing Fiber Optic and BNC Video Cables Page C-3
Connect and Route XTC Fiber Optic Cables

account team and/or an Infinera TAC resource for additional information. Always clean and label fiber optic
cables before use, and observe the safety precautions outlined in “Laser Safety” on page 1-13.
CAUTION
and Class 1M.
To connect and route fiber optic cables, perform the following sequence (depending on system
configuration):
1. “To connect the TOM port fiber optic cables” on page C-4.
2. “To connect OCG cables between XTC line modules and DTC/MTC BMM/BMM2/BMM2P/
BMM2Hs” on page C-6.
3. “To connect OCG cables between XTC SOLM-500/SOLX-500s and DTC BMM2/BMM2Ps” on
page C-13.
4. “To connect OCG cables between XTC line modules and DTC BMM2/BMM2Ps” on page C-18.
5. “To connect OCG cables between XTC line modules configured for Open Wave line system mode”
on page C-26.
6. “To connect SCh cables between XTC FlexChannel line modules and MTC-9 FSMs” on page C-
30.
7. “To connect SCh cables between XTC FlexChannel line modules and FPC FSP/FMPs” on page C-
32.
8. “To route the OCG/SCh and tributary port fiber optic cables” on page C-34.

Page C-4 Connect and Route XTC Fiber Optic Cables
To connect the TOM port fiber optic cables
CAUTION
Step 1 Remove the XTC front door(s) (if applicable). Refer to the Infinera DTN and DTN-X Site Prepara-
tion and Hardware Installation Guide.
Step 2 Insert a pair of clean, labeled fiber optic cables into the upper (IN) and lower (OUT) connectors in
each installed TOM as shown in Figure C-1 on page C-5:
Step 2a Connect incoming tributary fibers to the IN ports.
Step 2b Connect outgoing tributary fibers to the OUT ports.
Step 3 Repeat Step 2 for each installed TOM.
Step 4 Reinstall the XTC front door(s) (if applicable). Refer to the Infinera DTN and DTN-X Site Prepa-
ration and Hardware Installation Guide.

Figure C-1 Connecting the Fiber Optic Cables to the Optical TOM
OTM-500/
OTM2-500
TIM-5-10G
Module
infn_922
Note: Figure C-1 applies to all TOM types supported on the XTC. The optical fiber connections as
illustrated are shown for clarity. Infinera recommends that you utilize appropriate fiber man-
agement. Infinera strongly recommends the use of bend insensitive fiber (BIF) for all fiber
connections (whenever possible). BIF cables provide greater resistance to bending losses
due to excessive bends in the fiber cables (compared to non-BIF cables), and are identified
by a Blue cable jacket. Contact your Infinera account team and/or an Infinera TAC
resource for additional information.

To connect OCG cables between XTC line modules and DTC/MTC BMM/BMM2/BMM2P/BMM2Hs
Note: This procedure applies to the following XTC line module types only: AOLM-500,
AOLM-500B, AOLX-500, and/or AOLX-500Bs.
For SOLM-500 and/or SOLX-500s, refer to “To connect OCG cables between XTC SOLM-
500/SOLX-500s and DTC BMM2/BMM2Ps” on page C-13.
For AOLM2-500, AOLM2-500B, AOLX2-500, AOLX2-500B, SOLM2-500, SOLM2-500B,

SOLX2-500, and/or SOLX2-500Bs, refer to “To connect OCG cables between XTC line
modules and DTC BMM2/BMM2Ps” on page C-18.
The XTC line modules are tunable modules that can be configured for one of four OCGs in a 160-channel
system, or one of two OCGs in an 80-channel system. For example, the AOLX-500-T4-1-C5 can be tuned
to carry signals on OCG 1, 2, 9, or 10.
XTC line modules are optically connected to a DTC/MTC BMM/BMM2/BMM2P/BMM2H, and can be
installed in upper universal card slots A-1 through A-5 and/or lower universal card slots B-1 through B-5 of
the XTC-10, and/or universal slots A-1 through A-4 of the XTC-4.
Ensure that the OCG port on the XTC line module is connected to the corresponding OCG port on the
DTC/MTC BMM/BMM2/BMM2P/BMM2H as listed in Table C-1 on page C-7.
 Each BMM-4 (BMM-4-CX2-MS-A/BMM-4-CX3-MS-A) supports four OCGs (OCG 1, OCG 3, OCG 5,
and OCG 7)
 Each BMM-8 (BMM-8-CXH2-MS/BMM-8-CXH3-MS) supports eight OCGs (OCG 1, OCG 2, OCG 3,
OCG 4, OCG 5, OCG 6, OCG 7, and OCG 8)
 Each BMM2-8 (BMM2-8-CXH2-MS/BMM2-8-CH3-MS) supports eight OCGs (OCG 1, OCG 2,
OCG 3, OCG 4, OCG 5, OCG 6, OCG 7, and OCG 8)
 Each BMM2-8-CEH3 (expansion BMM2) supports eight OCGs (OCG 9, OCG 10, OCG 11, OCG 12,
OCG 13, OCG 14, OCG 15, and OCG 16) only when used with a BMM2-8-CH3-MS (base BMM2)
 Each BMM2P-8-CH1-MS (base BMM2P) supports eight OCGs (OCG 1, OCG 2, OCG 3, OCG 4,
OCG 5, OCG 6, OCG 7, and OCG 8)
 Each BMM2P-8-CEH1 (expansion BMM2P) supports eight OCGs (OCG 9, OCG 10, OCG 11,
OCG 12, OCG 13, OCG 14, OCG 15, and OCG 16) only when used with a BMM2P-8-CH1-MS
(base BMM2P)
 Each BMM2H-4-R3-MS (base BMM2H) supports four OCGs (OCG 1, OCG 2, OCG 3, and OCG 4)
 Each BMM2H-4-B3 (expansion BMM2H) supports four OCGs (OCG 5, OCG 6, OCG 7, and OCG 8)
only when used with a BMM2H-4-R3-MS (base BMM2H)
Note: When connecting a DTN-X line module to a Gen 1 BMM, ensure that a 15.0dB
attenuator pad is plugged into the BMM OCG IN port to meet the power requirements for
Auto-discovery.

Note: For 160-channel systems using full-height BMM2/BMM2Ps, a configuration with up to 4

OCGs provisioned on the expansion BMM2/BMM2P requires a minimum of 1 OCG to be
provisioned on the base BMM2/BMM2P. A configuration with 5 to 8 OCGs provisioned on
the expansion BMM2/BMM2P requires a minimum of 2 OCGs to be provisioned on the
base BMM2/BMM2P.
Note: For 80-channel systems using half-height BMM2Hs, a configuration with up to 4 OCGs pro-
visioned on the expansion BMM2H requires a minimum of 1 OCG to be provisioned on the
base BMM2H.
Table C-1 XTC Line Module to DTC/MTC BMM/BMM2/BMM2P/BMM2H OCG Port Association
DTC/MTC BMM/BMM2/BMM2P/BMM2H
XTC Line Module OCG Ports OCG Ports
AOLM-500-T4-1-C5/C6 OCG 1 BMM-4-CX2-MS-A OCG 1

AOLX-500-T4-1-C5/C6 OCG 1 BMM-4-CX3-MS-A OCG 1
AOLM-500B-T4-1-C5/C6 OCG 1 BMM-8-CXH2-MS OCG 1
AOLX-500B-T4-1-C5/C6 OCG 1 BMM-8-CXH3-MS OCG 1
BMM2-8-CXH2-MS OCG 1
BMM2-8-CH3-MS OCG 1
BMM2P-8-CH1-MS OCG 1
BMM2H-4-R3-MS OCG 1
AOLM-500-T4-1-C5/C6 (tuned as OCG 2) BMM-8-CXH2-MS OCG 2
AOLX-500-T4-1-C5/C6 (tuned as OCG 2) BMM-8-CXH3-MS OCG 2
AOLM-500B-T4-1-C5/C6 (tuned as OCG 2) BMM2-8-CXH2-MS OCG 2
AOLX-500B-T4-1-C5/C6 (tuned as OCG 2) BMM2-8-CH3-MS OCG 2
BMM2H-4-R3-MS OCG 2
BMM2-8-CH3-MS OCG 3
BMM2H-4-R3-MS OCG 3


BMM2H-4-R3-MS OCG 4
BMM2-8-CH3-MS OCG 5
BMM2H-4-B3 OCG 5
BMM2H-4-B3 OCG 6
BMM2-8-CH3-MS OCG 7
BMM2H-4-B3 OCG 7
BMM2H-4-B3 OCG 8

AOLM-500-T4-1-C5/C6 (tuned as OCG 9) BMM2-8-CEH3 OCG 9

AOLX-500-T4-1-C5/C6 (tuned as OCG 9) BMM2P-8-CEH1 OCG 9
AOLM-500B-T4-1-C5/C6 (tuned as OCG 9)
AOLX-500B-T4-1-C5/C6 (tuned as OCG 9)
AOLM-500-T4-3-C5/C6 tuned as OCG 12) BMM2-8-CEH3 OCG 12
AOLX-500-T4-3-C5/C6 tuned as OCG 12) BMM2P-8-CEH1 OCG 12
AOLM-500B-T4-3-C5/C6 tuned as OCG 12)
AOLX-500B-T4-3-C5/C6 tuned as OCG 12)
AOLM-500-T4-5-C5/C6 tuned as OCG 14) BMM2-8-CEH3 OCG 14
AOLX-500-T4-5-C5/C6 tuned as OCG 14) BMM2P-8-CEH1 OCG 14

Step 1 Ensure the fiber optic cables are clean and labeled.
Step 2 Remove the XTC and/or DTC/MTC front covers and/or doors (if applicable). Refer to the Infinera
DTN and DTN-X Site Preparation and Hardware Installation Guide.
Step 3 Connect the OCG port on the XTC line module to the corresponding OCG port on the DTC/MTC
BMM/BMM2/BMM2P/BMM2H with the fiber optic cables, using the port association specified in
Table C-1 on page C-7. For a given OCG, be sure to connect the XTC line module OCG OUT
port to the DTC/MTC BMM OCG IN port, and the XTC line module OCG IN port to the DTC/MTC
BMM OCG OUT port.
Note: When connecting a DTN-X line module to a Gen 1 BMM, ensure that a 15.0dB
attenuator pad is plugged into the BMM OCG IN port to meet the power requirements for
Auto-discovery.
Step 4 Repeat Step 3 for remaining XTC line module to DTC/MTC BMM/BMM2/BMM2P/BMM2H con-
nections.
Step 5 Reinstall the XTC and/or DTC/MTC front covers and/or doors (if applicable). Refer to the Infinera
Figure C-2 on page C-11 (for XTC-10) and Figure C-3 on page C-12 (for XTC-4) show how OCG optical
fiber pairs are connected between XTC line modules and DTC/MTC BMM/BMM2/BMM2P/BMM2Hs.

BMM2Hs
DTC/MTC XTC-10
A-6A/
A-1/B-1 A-2/B-2 A-3/B-3 A-4/B-4 A-5/B-5 B-6B
1
BMM/BMM2/BMM2P/BMM2H
TIM-1-100G
TIM-1-100G
TIM-1-100G
TSM
Line Module
Line Module
TIM-1-100G
TIM-1-100G
TIM-1-100G
LINE IN OUT IN OUT
IN OUT
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
TIM-5-10G
TIM-5-10G
Line
West / East
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
OUT IN
OCG 1
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
TIM-5-10G
TIM-5-10G
OCG 2
Optical Fiber
OCG 3
Connections
XCM
Between OCG 4
Circuit Packs
OCG 5
Connected
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
TIM-5-10G
to OCG 1 TIM-5-10G
OCG 6
Connected
OCG 7
to OCG 3
OCG 8
A-6B/
B-6A
infn_923b
Note: The optical fiber connections as illustrated are shown for clarity. Infinera recommends that
you utilize appropriate fiber management. Infinera strongly recommends the use of bend
insensitive fiber (BIF) for all fiber connections (whenever possible). BIF cables provide
greater resistance to bending losses due to excessive bends in the fiber cables (compared
to non-BIF cables), and are identified by a Blue cable jacket. Contact your Infinera account
team and/or an Infinera TAC resource for additional information.

BMM2Hs
TAP I/O Panel
XTC-4
DTC/MTC
XCM
XCM
1
BMM/BMM2/BMM2P/BMM2H
A-5A A-5B
TIM-1-100G
TIM-1-100G
Line Module
Line Module
TIM-1-100G
TIM-1-100G
OXM
TSM
S-1 A-6
LINE IN OUT IN OUT
IN OUT
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
Line
West / East
OTM-500/OTM2-500
OTM-500/OTM2-500
OUT IN
OXM
OXM
TIM-1-40G
TIM-1-40G
OCG 1
TIM-5-10G
TIM-5-10G
OCG 2
Optical Fiber S-2 S-3
Connections OCG 3
Between OCG 4
Circuit Packs
OCG 5 Connected
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
to OCG 1
OCG 6
Connected
OXM
OXM
OCG 7 to OCG 3
OCG 8
A-1 A-2 S-4 S-5 A-3 A-4

infn_974b

To connect OCG cables between XTC SOLM-500/SOLX-500s and DTC BMM2/BMM2Ps
Note: This procedure applies to the following XTC line module types only: SOLM-500 and/or
SOLX-500s.
For AOLM-500, AOLM-500B, AOLX-500, and/or AOLX-500Bs, refer to “To connect OCG
cables between XTC line modules and DTC/MTC BMM/BMM2/BMM2P/BMM2Hs” on
page C-6.
For AOLM2-500, AOLM2-500B, AOLX2-500, AOLX2-500B, SOLM2-500, SOLM2-500B,

SOLX2-500, and/or SOLX2-500Bs, refer to “To connect OCG cables between XTC line
modules and DTC BMM2/BMM2Ps” on page C-18.
The XTC SOLM-500/SOLX-500s are tunable modules that can be configured for one of four OCGs in a
160-channel system, or one of two OCGs in an 80-channel system. For example, the SOLX-500-T4-1-C11
can be tuned to carry signals on OCG 1, 2, 9, or 10.
XTC SOLM-500/SOLX-500s are optically connected to a DTC BMM2/BMM2P, and can be installed in
upper universal card slots A-1 through A-5 and/or lower universal card slots B-1 through B-5 of the
XTC-10, and/or universal slots A-1 through A-4 of the XTC-4.
Ensure that the OCG port on the XTC SOLM-500/SOLX-500 is connected to the corresponding OCG port
on the DTC BMM2/BMM2P as listed in Table C-2 on page C-14.
(base BMM2P)

base BMM2/BMM2P.

Table C-2 XTC SOLM-500/SOLX-500 to DTC BMM2/BMM2P OCG Port Association
XTC SOLM-500/SOLX-500 OCG Ports DTC BMM2/BMM2P OCG Ports
SOLM-500-T4-1-C11 OCG 1 BMM2-8-CXH2-MS OCG 1

SOLX-500-T4-1-C11 OCG 1 BMM2-8-CH3-MS OCG 1
SOLM-500-T4-1-C11 (tuned as OCG 2) BMM2-8-CXH2-MS OCG 2
SOLX-500-T4-1-C11 (tuned as OCG 2) BMM2-8-CH3-MS OCG 2
SOLM-500-T4-1-C11 (tuned as OCG 9) BMM2-8-CEH3 OCG 9
SOLX-500-T4-1-C11 (tuned as OCG 9) BMM2P-8-CEH1 OCG 9
SOLM-500-T4-3-C11 tuned as OCG 12) BMM2-8-CEH3 OCG 12
SOLX-500-T4-3-C11 tuned as OCG 12) BMM2P-8-CEH1 OCG 12

Table C-2 XTC SOLM-500/SOLX-500 to DTC BMM2/BMM2P OCG Port Association
XTC SOLM-500/SOLX-500 OCG Ports DTC BMM2/BMM2P OCG Ports
SOLM-500-T4-5-C11 tuned as OCG 14) BMM2-8-CEH3 OCG 14

SOLX-500-T4-5-C11 tuned as OCG 14) BMM2P-8-CEH1 OCG 14
Step 2 Remove the XTC and/or DTC front covers and/or doors (if applicable). Refer to the Infinera DTN
and DTN-X Site Preparation and Hardware Installation Guide.
Step 3 Connect the OCG port on the XTC SOLM-500/SOLX-500 to the corresponding OCG port on the
DTC BMM2/BMM2P with the fiber optic cables, using the port association specified in Table C-2
on page C-14. For a given OCG, be sure to connect the XTC SOLM-500/SOLX-500 OCG OUT
port to the DTC BMM OCG IN port, and the XTC SOLM-500/SOLX-500 OCG IN port to the DTC
BMM OCG OUT port.
Step 4 Repeat Step 3 for remaining XTC SOLM-500/SOLX-500 to DTC BMM2/BMM2P connections.
Step 5 Reinstall the XTC and/or DTC front covers and/or doors (if applicable). Refer to the Infinera DTN
fiber pairs are connected between XTC SOLM-500/SOLX-500s and DTC BMM2/BMM2Ps.

Figure C-4 Fiber Connections between XTC-10 SOLM-500/SOLX-500s and DTC BMM2/BMM2Ps
DTC XTC-10
A-6A/
A-1/B-1 A-2/B-2 A-3/B-3 A-4/B-4 A-5/B-5 B-6B
1
BMM2/BMM2P
TIM-1-100G
TIM-1-100G
TIM-1-100G
TSM
SOLM-500/SOLX-500
SOLM-500/SOLX-500
TIM-1-100G
TIM-1-100G
TIM-1-100G
LINE IN OUT IN OUT
IN OUT
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
TIM-5-10G
TIM-5-10G
Line
West / East
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
OUT IN
OCG 1 TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
TIM-5-10G
TIM-5-10G
OCG 2
Optical Fiber
OCG 3
Connections
XCM
Between OCG 4
Circuit Packs
OCG 5
Connected
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
TIM-5-10G
TIM-5-10G
OCG 6 to OCG 1
Connected
OCG 7
to OCG 3
OCG 8
A-6B/
B-6A
infn_923c

Figure C-5 Fiber Connections between XTC-4 SOLM-500/SOLX-500s and DTC BMM2/BMM2Ps
TAP I/O Panel
XTC-4
DTC
XCM
XCM
1
A-5A A-5B
BMM2/BMM2P
TIM-1-100G
TIM-1-100G
SOLM-500/SOLX-500
SOLM-500/SOLX-500
TIM-1-100G
TIM-1-100G
OXM
TSM
S-1 A-6
LINE IN OUT IN OUT
IN OUT
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
Line
West / East OTM-500/OTM2-500
OTM-500/OTM2-500
OUT IN
OXM
OXM
TIM-1-40G
TIM-1-40G
OCG 1
TIM-5-10G
TIM-5-10G
OCG 2
Connections OCG 3
Between OCG 4
Circuit Packs
OCG 5 Connected
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
to OCG 1
OCG 6
Connected
OXM
OXM
OCG 7 to OCG 3
OCG 8
A-1 A-2 S-4 S-5 A-3 A-4

infn_974c

To connect OCG cables between XTC line modules and DTC BMM2/BMM2Ps
Note: This procedure applies to the following XTC line module types only: AOLM2-500,
SOLX2-500Bs.
For AOLM-500, AOLM-500B, AOLX-500, and/or AOLX-500Bs, refer to “To connect OCG
cables between XTC line modules and DTC/MTC BMM/BMM2/BMM2P/BMM2Hs” on
page C-6.
For SOLM-500 and/or SOLX-500s, refer to “To connect OCG cables between XTC SOLM-
500/SOLX-500s and DTC BMM2/BMM2Ps” on page C-13.
system, or one of two OCGs in an 80-channel system. For example, the AOLX2-500-T4-1-C5 can be tuned
XTC line modules are optically connected to a DTC BMM2/BMM2P, and can be installed in upper universal
card slots A-1 through A-5 and/or lower universal card slots B-1 through B-5 of the XTC-10, and/or
universal slots A-1 through A-4 of the XTC-4.
Ensure that the OCG port on the XTC line module is connected to the corresponding OCG port on the DTC
BMM2/BMM2P as listed in Table C-3 on page C-19.
(base BMM2P)

base BMM2/BMM2P.

Table C-3 XTC Line Module to DTC BMM2/BMM2P OCG Port Association
XTC Line Module OCG Ports DTC BMM2/BMM2P OCG Ports
AOLM2-500-T4-1-C5/C6/C8 OCG 1 BMM2-8-CXH2-MS OCG 1

AOLX2-500-T4-1-C5/C6/C8 OCG 1 BMM2-8-CH3-MS OCG 1
AOLM2-500B-T4-1-C5/C6/C8OCG 1 BMM2P-8-CH1-MS OCG 1
AOLX2-500B-T4-1-C5/C6/C8 OCG 1
SOLM2-500-T4-1-C12/C13 OCG 1
SOLX2-500-T4-1-C12/C13 OCG 1
SOLM2-500B-T4-1-C12/C13 OCG 1
SOLX2-500B-T4-1-C12/C13 OCG 1
AOLM2-500-T4-1-C5/C6/C8 (tuned as OCG 2) BMM2-8-CXH2-MS OCG 2
AOLX2-500-T4-1-C5/C6/C8 (tuned as OCG 2) BMM2-8-CH3-MS OCG 2
AOLM2-500B-T4-1-C5/C6/C8 (tuned as OCG 2) BMM2P-8-CH1-MS OCG 2
AOLX2-500B-T4-1-C5/C6/C8 (tuned as OCG 2)
SOLM2-500-T4-1-C12/C13 (tuned as OCG 2)
SOLX2-500-T4-1-C12/C13 (tuned as OCG 2)
SOLM2-500B-T4-1-C12/C13 (tuned as OCG 2)
SOLX2-500B-T4-1-C12/C13 (tuned as OCG 2)
AOLM2-500B-T4-3-C5/C6/C8 OCG 3 BMM2P-8-CH1-MS OCG 3
SOLM2-500-T4-3-C12/C13 OCG 3
SOLX2-500-T4-3-C12/C13 OCG 3
SOLM2-500B-T4-3-C12/C13 OCG 3
SOLX2-500B-T4-3-C12/C13 OCG 3


SOLM2-500-T4-5-C12/C13 OCG 5
SOLX2-500-T4-5-C12/C13 OCG 5
SOLM2-500B-T4-5-C12/C13 OCG 5
SOLX2-500B-T4-5-C12/C13 OCG 5
SOLM2-500-T4-7-C12/C13 OCG 7
SOLX2-500-T4-7-C12/C13 OCG 7
SOLM2-500B-T4-7-C12/C13 OCG 7
SOLX2-500B-T4-7-C12/C13 OCG 7

AOLM2-500-T4-1-C5/C6/C8 (tuned as OCG 9) BMM2-8-CEH3 OCG 9

AOLX2-500-T4-1-C5/C6/C8 (tuned as OCG 9) BMM2P-8-CEH1 OCG 9
AOLM2-500B-T4-1-C5/C6/C8 (tuned as OCG 9)
SOLM2-500-T4-1-C12/C13 OCG 9
SOLX2-500-T4-1-C12/C13 OCG 9
SOLM2-500B-T4-1-C12/C13 OCG 9
SOLX2-500B-T4-1-C12/C13 OCG 9
AOLM2-500-T4-3-C5/C6/C8 tuned as OCG 12) BMM2-8-CEH3 OCG 12
AOLX2-500-T4-3-C5/C6/C8 tuned as OCG 12) BMM2P-8-CEH1 OCG 12
AOLM2-500B-T4-3-C5/C6/C8 tuned as OCG 12)
AOLX2-500B-T4-3-C5/C6/C8 tuned as OCG 12)


AOLM2-500-T4-5-C5/C6/C8 tuned as OCG 14) BMM2-8-CEH3 OCG 14
AOLX2-500-T4-5-C5/C6/C8 tuned as OCG 14) BMM2P-8-CEH1 OCG 14

Step 2 Remove the XTC and/or DTC front covers and/or doors (if applicable). Refer to the Infinera DTN
Step 3 Connect the OCG port on the XTC line module to the corresponding OCG port on the DTC
BMM2/BMM2P with the fiber optic cables, using the port association specified in Table C-3 on
page C-19. For a given OCG, be sure to connect the XTC line module OCG OUT port to the
DTC BMM OCG IN port, and the XTC line module OCG IN port to the DTC BMM OCG OUT port.
Step 4 Repeat Step 3 for remaining XTC line module to DTC BMM2/BMM2P connections.
Step 5 Reinstall the XTC and/or DTC front covers and/or doors (if applicable). Refer to the Infinera DTN
fiber pairs are connected between XTC line modules and DTC BMM2/BMM2Ps.

Figure C-6 Fiber Connections between XTC-10 Line Modules and DTC BMM2/BMM2Ps
DTC XTC-10
A-6A/
A-1/B-1 A-2/B-2 A-3/B-3 A-4/B-4 A-5/B-5 B-6B
1
TIM-1-100G
TIM-1-100G
TIM-1-100G
TSM
BMM2/BMM2P
Line Module
Line Module
TIM-1-100G
TIM-1-100G
TIM-1-100G
LINE IN OUT IN OUT
IN OUT
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
TIM-5-10G
TIM-5-10G
Line
West / East
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
OUT IN
OCG 1 TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
TIM-5-10G
TIM-5-10G
OCG 2
Optical Fiber
OCG 3
Connections
XCM
Between OCG 4
Circuit Packs
OCG 5
Connected
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
TIM-5-10G
TIM-5-10G
OCG 6 to OCG 1
Connected
OCG 7
to OCG 3
OCG 8
A-6B/
B-6A
infn_923

Figure C-7 Fiber Connections between XTC-4 Line Modules and DTC BMM2/BMM2Ps
TAP I/O Panel
XTC-4
DTC
XCM
XCM
1
A-5A A-5B
TIM-1-100G
TIM-1-100G
BMM2/BMM2P
Line Module
Line Module
TIM-1-100G
TIM-1-100G
OXM
TSM
S-1 A-6
LINE IN OUT IN OUT
IN OUT
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
Line
West / East OTM-500/OTM2-500
OTM-500/OTM2-500
OUT IN
OXM
OXM
TIM-1-40G
TIM-1-40G
OCG 1
TIM-5-10G
TIM-5-10G
OCG 2
Connections OCG 3
Between OCG 4
Circuit Packs
OCG 5 Connected
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
to OCG 1
OCG 6
Connected
OXM
OXM
OCG 7 to OCG 3
OCG 8
A-1 A-2 S-4 S-5 A-3 A-4

infn_974

To connect OCG cables between XTC line modules configured for Open Wave line system mode
changeably.
tunable line modules. Open Wave line system mode is supported on certain line modules (see note above)
allowing for a direct line module-to-line module interconnection without the requirement of an intermediate
BMM. Note that the local and remote end line modules can be different types. For example, an AOLM-500-
T4-C5 can be optically connected to an AOLX-500-T4-C6, or an AOLM-500B-T4-C6 can be optically
connected to AOLX-500-T4-C5, etc. However, each line module must be tuned to the same OCG. For
example, an AOLM-500-T4-C5 (tuned to OCG1) can be optically connected to an AOLX-500-T4-C6 (tuned
to OCG1).
Step 2 Remove the XTC front doors (if applicable). Refer to the Infinera DTN and DTN-X Site Prepara-
Step 3 Connect the OCG port on the local end XTC line module to the corresponding OCG port on the
remote end XTC line module with the fiber optic cables. For a given OCG, be sure to connect the
local end XTC line module OCG OUT port to the remote end XTC line module OCG IN port, and
the remote end XTC line module OCG OUT port to the local end XTC line module OCG IN port.
Step 4 Repeat Step 3 for remaining XTC line module-to-line module to connections.
Step 5 Reinstall the XTC front doors (if applicable). Refer to the Infinera DTN and DTN-X Site Prepara-
Figure C-8 on page C-27, Figure C-9 on page C-28, and/or Figure C-10 on page C-29 provide examples of
how OCG optical fiber pairs are connected between XTC line modules over a third-party line system, a
back-to-back inter-chassis configuration, and/or a back-to-back intra-chassis configuration, respectively.

Mode over a Third-party Line System
Node A Node B
Line Module
Line Module
Line Module
Line Module
IN OUT IN OUT IN OUT IN OUT
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
Third-party
Line System
Connected Connected
to OCG 1 to OCG 1
XTC (local) XTC (remote)

infn_630
Infinera Scope of Control Infinera Scope of Control

Mode over a Back-to-Back (Inter-Chassis) Line Module Configuration
Node A Node B
Line Module
Line Module
Line Module
Line Module
IN OUT IN OUT IN OUT IN OUT
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
Connected Connected
to OCG 1 to OCG 1
XTC (local) XTC (remote)

infn_631

Mode over a Back-to-Back (Intra-Chassis) Line Module Configuration
Node A
Line Module
Line Module
IN OUT IN OUT
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
Connected
to OCG 1
Connected
to OCG 1
IN OUT IN OUT
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
Line Module
Line Module
XTC infn_632

To connect SCh cables between XTC FlexChannel line modules and MTC-9 FSMs
Note: This procedure applies to the following FlexChannel line module types only: AOFM-500,
AOFM-500B, AOFX-500, and/or AOFX-500B and assumes that the MTC-9 has been previ-
ously installed with the required modules.
The XTC FlexChannel line modules are tunable super channel (SCh) based OTN modules that can be
configured for one of four SChs. For example, the AOFM-500-T4-1-C5 is set to SCh 1 by default but can
be tuned via the management interfaces to carry signals on SCh 1, 2, 3, or 4.
XTC FlexChannel line modules are optically connected to an MTC-9 (either directly to an FSM or indirectly
to an FRM via an FSP-C or FMP-C) to provide bandwidth for up to 9.5Tbps of traffic signals. and can be
installed in upper universal card slots A-1 through A-5 and/or lower universal card slots B-1 through B-5 of
the XTC-10, and/or universal card slots A-1 through A-4 of the XTC-4.
Step 2 Remove the XTC and/or MTC-9 front doors (if applicable). Refer to the Infinera DTN and DTN-X
Site Preparation and Hardware Installation Guide.
Step 3 Connect the SCh port on the XTC FlexChannel line module to an available port on the MTC-9
FSM with the fiber optic cables. For a given SCh, be sure to connect the XTC FlexChannel line
module SCh OUT port to an available MTC-9 FSM Add/Drop IN port n (n=1-12), and the XTC
FlexChannel line module SCh IN port to the corresponding MTC-9 FSM Add/Drop OUT port n
(n=1-12).
Step 4 Repeat Step 3 for remaining XTC FlexChannel line module to MTC-9 FSM connections.
Step 5 Reinstall the XTC and/or MTC-9 front doors (if applicable). Refer to the Infinera DTN and DTN-X
Site Preparation and Hardware Installation Guide.
Figure C-11 on page C-31 (applies to both the XTC-10 and XTC-4) shows how SCh optical fiber pairs are
connected between XTC FlexChannel line modules and MTC-9 FSMs.

Figure C-11 Fiber Connections between XTC FlexChannel Line Modules and MTC-9 FSMs
AOFM-500/
AOFM-500/
AOFX-500
AOFX-500
SCh SCh Add/Drop

IN OUT IN OUT Port Connectors 7
3 6 9 12
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
2 5 8 11 5
1 4 7 10
4
FSM-CDC-8-12-EC
3
IAM-B-ECXH2
XTC MTC-9 infn_1282

To connect SCh cables between XTC FlexChannel line modules and FPC FSP/FMPs
Note: This procedure applies to the following FlexChannel line module types only: AOFM-500,
AOFM-500B, AOFX-500, and/or AOFX-500B and assumes that the FPC has been previ-
ously installed with the required modules.
The XTC FlexChannel line modules are tunable super channel (SCh) based OTN modules that can be
configured for one of four SChs. For example, the AOFM-500-T4-1-C5 is set to SCh 1 by default but can
be tuned via the management interfaces to carry signals on SCh 1, 2, 3, or 4.
XTC FlexChannel line modules are optically connected to an FPC (FSP/FMP) and can be installed in
upper universal card slots A-1 through A-5 and/or lower universal card slots B-1 through B-5 of the
XTC-10, and/or universal card slots A-1 through A-4 of the XTC-4.
Step 3 Connect the SCh port on the XTC FlexChannel line module to an available port on the FPC
FSP/FMP with the fiber optic cables. For a given SCh, be sure to connect the XTC FlexChannel
line module SCh OUT port to an available FSP Add/Drop (AD) IN port n (n=1-4) or FMP Add/
Drop (AD) IN port n (n=1A-4A or 1B-4B), and the XTC FlexChannel line module SCh IN port to
the corresponding FSP Add/Drop (AD) OUT port n (n=1-4) or FMP Add/Drop (AD) OUT port n
(n=1A-4A or 1B-4B).
Step 4 Repeat Step 3 for remaining XTC FlexChannel line module to FPC FSP/FMP connections.
Figure C-12 on page C-33 (applies to both the XTC-10 and XTC-4) shows how SCh optical fiber pairs are
connected between XTC FlexChannel line modules and FPC FSP/FMPs.

Figure C-12 Fiber Connections between XTC FlexChannel Line Modules and FPC FSP/FMPs
Add/Drop (AD) Add/Drop (AD)
AOFM-500/
AOFM-500/
Port Connectors Port Connectors

AOFX-500
AOFX-500
FMP-C-8-4-LC-MPO
FSP-C FMP-C
FSP-C-1D-1MPO-4LC
4 3 2 1 4B 4A 3B 3A 2B 2A 1B 1A
SCh SCh
IN OUT IN OUT FPC
OTM-500/OTM2-500
OTM-500/OTM2-500
XTC
infn_1283

To route the OCG/SCh and tributary port fiber optic cables
Note: Unless specifically noted otherwise, all references to the "FlexChannel line module" will
The line module OCG, FlexChannel SCh, and tributary fiber optic cables are routed through the fiber
guides to the fiber trays as follows:
 OCG fiber optic cables connected to the line modules are routed directly up or down to a fiber tray,
through fiber guides located on the line modules
 SCh fiber optic cables connected to the FlexChannel line modules are routed directly up or down to
a fiber tray, through fiber guides located on the FlexChannel line modules
 Tributary port fiber optic cables connected to TOM ports on the TIMs are routed up or down to a fiber
tray, through center and vertical fiber guides located on the OTM-500/OTM2-500s
Refer to Figure C-17 on page C-40 (for XTC-10) and Figure C-18 on page C-41 (for XTC-4) when
performing this procedure.
Step 1 Ensure that the line module, FlexChannel SCh, and/or OTM-500/OTM2-500 fiber guides have
been previously installed on all line modules/OTM-500/OTM2-500s, refer to the Infinera DTN
and DTN-X Site Preparation and Hardware Installation Guide for more information.
Step 2 Route the line module OCG fiber optic cables connected to the OCG ports through the fiber
guides located on the line module, directly up or down to a fiber tray.
Step 3 Route the FlexChannel line module SCh fiber optic cables through the fiber guides located on
the FlexChannel line module, directly up or down to a fiber tray.
Step 4 Route the OTM-500/OTM2-500 tributary fiber optic cables connected to the TOM ports on the
TIMs in sub-slots 1 through 10 as follows:

Note: The center fiber guides are used to route fibers from the TIM sub-slots located on the far
side of the OTM-500/OTM2-500 relative to the ejectors as shown in Figure C-13 on
page C-36, Figure C-14 on page C-37, Figure C-15 on page C-38, and Figure C-16 on
page C-39.
Step 4a The fibers from the TIMs in sub-slots 1 and 2 are routed directly up to the fiber tray at
the top of the card cage.
Step 4b The fibers from the TIM in sub-slot 3 are routed up through fiber guide A2 and then
up to the upper fiber tray.
Step 4c The fibers from the TIM in sub-slot 4 are routed through fiber guide A1, up through
fiber guide A2, and then up to the upper fiber tray.
Step 4d The fibers from the TIM in sub-slot 5 are routed through fiber guide A1, up through
fiber guide A2, and then up to the upper fiber tray.
Step 4e The fibers from the TIM in sub-slot 6 are routed through fiber guide B1, down through
fiber guide B2, and then down to the lower fiber tray.
Step 4f The fibers from the TIM in sub-slot 7 are routed through fiber guide B1, down through
fiber guide B2, and then down to the lower fiber tray.
Step 4g The fibers from the TIM in sub-slot 8 are routed through fiber guide B2 and then
down to the lower fiber tray.
Step 4h The fibers from the TIMs in sub-slots 9 and 10 are routed directly down to the fiber
tray at the bottom of the card cage.
Step 5 Route the fibers in the fiber trays to the left or right (depending on line module, FlexChannel line
module, and/or OTM-500/OTM2-500 card slot location) into the vertical routing channels on
either side of the XTC, up and out through the top of the cabinet/rack:
For XTC-10: fibers originating in universal card slots A-1/B-1 through A-3/B-3 are routed to
the left and up, and fibers in slots A-4/B-4 and A-5/B-5 are routed to the right and up. (Fibers
from slot A-3/B-3 can be routed to the left or right depending on the customer configuration)
For XTC-4: fibers originating in universal card slots A-1 and A-2 are routed to the left and up,
and fibers in slots A-3 and A-4 are routed to the right and up
Step 6 Repeat Step 2 through Step 5 for each installed line module, FlexChannel line module, and/or
OTM-500/OTM2-500.

Figure C-13 Example of OTM-500/OTM2-500 Fiber Optic Cable Routing through Fiber Guides
Ejector
Fiber Optic
Cable
Fiber Routed
through Center
Fiber Guides A and B Center Fiber
Guide
Center Fiber
Guide A
OTM-500/
OTM2-500
Center Fiber
Guide B
Note:
Center Fiber Guides are used to
route fibers from the TIM sub-slots
TIMs located on the far side of the
OTM-500/OTM2-500 relative to
the ejectors.
Ejector
OTM-500/OTM2-500
infn_1037

Figure C-14 Example of OTM-500/OTM2-500 Fiber Optic Cable Routing from TIM Sub-slot #4
Ejector
OTM-500/OTM2-500
Note:
located on the far side of the
OTM-500/OTM2-500 relative to
the ejectors.
TIM
Example of Fiber
Routed from
TIM Sub-slot #4
Center Fiber
Guide A
infn_1039

OTM-500/OTM2-500
Ejector
TIMs
Center Fiber
Guide A Example of Fiber
Routed from
TIM Sub-slot #6
Note:
Center Fiber
Guide B OTM-500/OTM2-500 relative to
the ejectors.
infn_1038

Center Fiber
Guide B Example of Fiber
Routed from
TIM Sub-slot #8
TIMs
OTM-500/OTM2-500
Note:
Ejector Center Fiber Guides are used to
OTM-500/OTM2-500 relative
to the ejectors.
infn_1040

Figure C-17 Example of XTC-10 Fiber Optic Cable Routing
Upper Card Slots

Fiber Detail
Guides
A2
A1 Center
Fiber Guide A
Fiber Center
Guides Fiber Guide B
B1
Fiber
Guides
A2
B2
A1
Center
Fiber Guide A
Center
Fiber Guide B B1
Radius Horn
B2
Lower Card Slots
Fibers from Fibers from Detail
infn_824
Card Slots A-1, A-2, Card Slots A-4,A-5
B-1, B-2 B-4, B-5
Routed to Left Routed to Right
Note: Fibers from card slot A-3/B-3 can be routed to the left or right depending on the customer
configuration. Infinera strongly recommends the use of bend insensitive fiber (BIF) for all
fiber connections (whenever possible). BIF cables provide greater resistance to bending
losses due to excessive bends in the fiber cables (compared to non-BIF cables), and are

identified by a Blue cable jacket. Contact your Infinera account team and/or an Infinera
TAC resource for additional information.
Note: The XTC-10 and/or XTC-4 are shipped without slack managers pre-installed. For rack
installations that require slack management, remove the slack on the fiber optic cables by
wrapping the extra fiber around the slack managers. Refer to the Infinera DTN and DTN-X
Site Preparation and Hardware Installation Guide for more information.
Figure C-18 Example of XTC-4 Fiber Optic Cable Routing

Card Slots A-3 & A-4
Detail:
Radius Horn
Fiber
Guides
A2
Center A1
Fiber Guide A
Center
Fiber Fiber Guide B
Guide B1
B2
Fibers from Fibers from

Card Slots A-1 & A-2 Card Slots A-3 & A-4
Routed to Left Routed to Right
infn_823

Page C-42 Connect and Route MTC-9 Fiber Optic Cables
Connect and Route MTC-9 Fiber Optic

Cables
CAUTION
and Class 1M.
CAUTION
port of an IAM/IRM. Contact your Infinera account team and/or an Infinera TAC resource to
obtain information regarding Infinera approved attenuator pads.
Note: All MPO connectors are angled physical contact (APC) type.
To connect and route fiber optic cables, perform the following:
To connect and route the fiber optic cables

Step 1 Insert a pair of clean, labeled fiber optic cables into the connectors in each IAM/IRM/FRM/FSM
(see Figure C-19 on page C-43 for the physical insertion of the cables).
Note: For IAM/IRMs only: to provide line amplification for signals going from West to East, the
Line IN port on a given IAM/IRM is connected to the incoming fiber from one direction (for
example, West) while the Line OUT port on the same IAM/IRM is connected to the outgoing
fiber in the opposite direction (for example, East). As a result, the receiver on the
IAM/IRM receives from one direction and the transmitter on the same IAM/IRM transmits
toward the opposite direction.
Step 2 Route the cables toward the right side through the fiber management tray (located on the chas-
sis). See Figure C-19 on page C-43.
Step 3 Secure the cable pairs using cable ties (where appropriate).

Figure C-19 Physically Connecting the Fiber Optic Cables
Fiber Management
Fiber
Optic
Cables
IAMs/
IRMs
FRMs/FSMs AIRFLOW DIRECTION
Bend Insensitive
Fiber Optic Cables
MPO Fiber Optic Cables
Fiber Guides
infn_1226

Page C-44 Connect and Route FSP/FMP Fiber Optic Cables
Connect and Route FSP/FMP Fiber Optic

Cables
MPO fiber cables are required for most FSP/FMP fiber connections. But in cases where MPO fiber cables
are not required, Infinera strongly recommends the use of bend insensitive fiber (BIF). BIF cables provide
greater resistance to bending losses due to excessive bends in the fiber cables (compared to non-BIF
cables), and are identified by a Blue cable jacket. Contact your Infinera account team and/or an Infinera
TAC resource for additional information. Always clean and label fiber optics before use, and observe the
safety precautions outlined in “Laser Safety” on page 1-13.
CAUTION
port of an IAM/IRM. Contact your Infinera account team and/or an Infinera TAC resource to
obtain information regarding Infinera approved attenuator pads.
To connect the fiber optic cables
Step 1 Insert clean fiber optic cables into the port connectors of the FSP/FMP as shown in Figure C-20
on page C-45. Refer to your site survey for configuration details.
Step 2 Connect the fiber cables between the FSP/FMPs, FRMs, and/or AOFM-500/AOFM-500B/
AOFX-500/AOFX-500Bs as listed in Table C-4 on page C-46.
Step 3 Secure all fiber cables as necessary using velcro straps (or equivalent).
Step 4 Repeat Step 1 through Step 3 to fiber an additional FSP/FMP.

Figure C-20 Connecting the Fiber Optic Cables to the FSP/FMP
FMP-C
A
FS
D
4B
A
M 6
D
4A
A
D
3B
A
D
3A
A
D
2B
5
A
D
2A
A
D
1B
A
D
4
1A
FSP-S-
FR
3
M 2
FS
7
M 6
FR
3
M 2
1
MPO Fiber
Optic Cables
infn_1237

Table C-4 FSP/FMP Connectors
Number of
Module Type Connectors Connector Typea Purpose
FSP-E-9D-18MPO, 18 MPO, Front access Connects to/from FRM-9Ds for express con-
Type 1 nectivity. For an example, see Figure C-21
FSP-E-9D-18MPO-B1, on page C-47
Type 1
FSP-C-1D-1MPO-4LC, 1 MPO, Front access Connects to/from an FRM-9D. For an exam-
Type 2 ple, see Figure C-22 on page C-48
4 LC, Front access Connects to/from AOFM-500/AOFM-500B/
AOFX-500/AOFX-500Bs for colorless add/
drop connectivity. For an example, see
Figure C-22 on page C-48
FSP-S-4D-8MPO, 8 MPO, Front access Connects to/from FRM-9D and/or FSM-8Ds
Type 3 for CDC add/drop connectivity. For an exam-
FSP-S-4D-8MPO-B1 ple, see Figure C-23 on page C-49
Type 3
FMP-C-8-4-LC-MPO 1 MPO, Front access Connects to/from an FRM-9D. For an exam-
ple, see Figure C-24 on page C-50
8 LC, Front access Connects to/from AOFM-500/AOFM-500B/
AOFX-500/AOFX-500Bs for colorless add/
drop connectivity. For an example, see
Figure C-24 on page C-50
a. All MPO connectors are angled physical contact (APC) type.

Figure C-21 FSP-E Express Connectivity with FRM-9Ds

FSP-E-9D-18MPO
FSP-E
Faceplate
FSP-E
FRM-9D FRM-9D FRM-9D FRM-9D FRM-9D FRM-9D FRM-9D FRM-9D FRM-9D

#9 #8 #7 #6 #5 #4 #3 #2 #1
18 MPO fiber cables in Star Configuration (2 MPO connectors
from each FRM-9D) for express connectivity
MPO Connector infn_1269

Figure C-22 FSP-C Connectivity with FRM-9Ds (for Colorless Add/Drop Configuration)
MPO connector to LC connectors to
FRM-9D AOFM-500/AOFX-500s
FSP-C-1D-1MPO-4LC
FSP-C
Faceplate
MPO Connector
LC Connector
FSP-C
AOFM-500/ AOFM-500/ AOFM-500/ AOFM-500/

FRM-9D
AOFX-500 AOFX-500 AOFX-500 AOFX-500
Up to 4 AOFM-500/AOFX-500s can be connected to infn_1270

a single FSP-C for colorless add/drop connectivity

Figure C-23 FSP-S Connectivity between FRM-9Ds and FSM-8Ds (for CDC Add/Drop Configuration)
MPO connectors to FRM-9D/FSM-8D
FSP-S-4D-8MPO
FSP-S
Faceplate
FRM-9D FRM-9D FRM-9D FRM-9D

#4 #3 #2 #1
4 3 2 1
MPO Connectors
Up to 4 FRM-9Ds and up to FSP-S

4 FSM-8Ds can be connected Internal Bidirectional
to a single FSP-S for CDC Fiber Pairs
5 6 7 8
add/drop connectivity
FSM-8D FSM-8D FSM-8D FSM-8D

#1 #2 #3 #4 infn_1271

Figure C-24 FMP-C Connectivity with FRM-9Ds (for Colorless Add/Drop Configuration)
MPO connector to LC connectors to
FRM-9D AOFM-500/AOFX-500s
FMP-C-8-4-LC-MPO
AD4B AD4A AD3B AD3A AD2B AD2A AD1B AD1A
MPO Connector
LC Connector
FMP-C
AOFM-500/ AOFM-500/ AOFM-500/ AOFM-500/ AOFM-500/ AOFM-500/ AOFM-500/ AOFM-500/

FRM-9D
AOFX-500 AOFX-500 AOFX-500 AOFX-500 AOFX-500 AOFX-500 AOFX-500 AOFX-500
Up to 8 AOFM-500/AOFX-500s can be connected to infn_1272

a single FMP-C for colorless add/drop connectivity

Connect and Route DTC/MTC Fiber Optic

and BNC Video Cables
CAUTION
and Class 1M.
To connect and route fiber optic and BNC video cables, perform the following sequence (depending on
system configuration):
1. “To connect the line module/TEM tributary port fiber optic cables” on page C-52.
2. “To connect the line module/TEM tributary port BNC video cables” on page C-54.
3. “To connect OCG cables between DLM/XLMs and BMM/BMM1Hs” on page C-55.
4. “To connect OCG cables between DLM/XLMs and BMM2/BMM2Hs (with GAM-1s)” on page C-58.
5. “To connect OCG cables between ADLM/AXLMs and BMM/BMM1H/BMM2/BMM2Hs (without
GAMs)” on page C-62.
6. “To connect OCG cables between ADLM/AXLMs and BMM2/BMM2Hs (with GAM-1s)” on page C-
67.
7. “To connect OCG cables between SLMs and BMM2s” on page C-73.
8. “To connect OCG cables between ADLM/AXLMs and BMM2Ps (with GAM-2s)” on page C-77.
9. “To connect OCH and OCG cables between ADLM-80/AXLM-80/SLM-80s, CMMs, and BMMs” on
page C-80.
10. “To route the OCG and tributary port fiber optic cables” on page C-85.
To connect expansion fiber cables between a base and expansion BMM2/BMM2P, perform the following:
1. “To connect expansion fiber cables between a base and expansion BMM2 (160-channel systems)”
on page C-88.
2. “To connect expansion fiber cables between a base and expansion BMM2P (160-channel sys-
tems)” on page C-88.
To connect expansion fiber cables between a base and expansion BMM2H, perform the following:
1. “To connect expansion fiber cables between a base and expansion BMM2H (80-channel systems)”
on page C-89.

Page C-52 Connect and Route DTC/MTC Fiber Optic and BNC Video Cables
To connect the BMM line side fiber optic cables, perform the following:
1. “To connect line side fiber cables to the DTN” on page C-89.
2. “To connect line side fiber cables between two DTNs” on page C-90.
3. “To connect line side fiber cables from the DTN to an Optical Amplifier” on page C-90.
To connect the line module/TEM tributary port fiber optic cables
CAUTION
Step 5 Remove the DTC/MTC front cover and/or door, refer to the Infinera DTN and DTN-X Site Prepa-
Step 6 Insert a pair of clean, labeled fiber optic cables into the upper (IN) and lower (OUT) connectors in
each optical TOM on the line module/TEM as shown in Figure C-25 on page C-53:
Step 6a Connect incoming tributary fibers to the IN ports.
Step 6b Connect outgoing tributary fibers to the OUT ports.
Step 7 Repeat Step 6 for each installed line module/TEM.
Step 8 Reinstall the DTC/MTC front cover and/or door.

Figure C-25 Connecting the Fiber Optic Cables to the Optical TOM
infn_074
Note: Figure C-25 applies to all TOM types supported on the DTC/MTC. The optical fiber connec-
tions as illustrated are shown for clarity. Infinera recommends that you utilize appropriate
fiber management. Infinera strongly recommends the use of bend insensitive fiber (BIF) for
all fiber connections (whenever possible). BIF cables provide greater resistance to bending
losses due to excessive bends in the fiber cables (compared to non-BIF cables), and are
identified by a Blue cable jacket. Contact your Infinera account team and/or an Infinera
TAC resource for additional information.

To connect the line module/TEM tributary port BNC video cables
Note: This procedure assumes the use of industry standard 75 ohm BNC cables and connectors.
Step 2 Attach the angle adapter (supplied with the video TOM) to a clean, labeled 75 ohm BNC video
cable as shown in Figure C-26.
Step 3 Connect the video cable with adapter onto each video TOM on the line module/TEM as shown in
Figure C-26.
Step 4 Repeat Step 2 and Step 3 for each installed line module/TEM.
Figure C-26 Connecting the BNC Video Cables to the Video TOM
Angle Adapter to Video Cable with Adapter

Video Cable to Video TOM
infn_582
Note: When using video TOMs in the TAM-8-2.5GM, the TOM slot(s) next to the video TOM must
be left open to avoid mechanical interference. Mechanical interference can cause difficul-
ties in inserting and removing the adjacent TOMs, which could damage the TAM/TOMs.

To connect OCG cables between DLM/XLMs and BMM/BMM1Hs
 Each BMM-4 supports four OCGs (OCG 1, OCG 3, OCG 5, and OCG 7)
 Each BMM-8 supports eight OCGs (OCG 1, OCG 2, OCG 3, OCG 4, OCG 5, OCG 6, OCG 7, and
OCG 8)
 Each BMM1H supports four OCGs (OCG 1, OCG 3, OCG 5, and OCG 7)
Note: The DLM/XLM must be connected directly to a BMM/BMM1H (and not through any fiber
patch panel).
There are four DLM/XLM slots on a chassis. Ensure that the OCG port on the DLM/XLM is connected to
the corresponding OCG port on the BMM/BMM1H as listed in Table C-5.
Table C-5 DLM/XLM to BMM/BMM1H OCG Port Association
DLM/XLM OCG Ports BMM/BMM1H OCG Ports
DLM-1-C2 OCG 1 BMM-4 OCG 1

XLM-1-C3 OCG 1 BMM1H OCG 1
DLM-2-C3 OCG 2
XLM-2-C3 OCG 2
DLM-4-C3 OCG 4
XLM-4-C3 OCG 4
DLM-6-C3 OCG 6
XLM-6-C3 OCG 6
DLM-8-C3 OCG 8
XLM-8-C3 OCG 8

Step 3 Connect the OCG port on a DLM/XLM to the corresponding OCG port on the BMM/BMM1H with
the fiber optic cables, using the port association specified in Table C-5 on page C-55. For a given
OCG, be sure to connect the DLM/XLM OCG OUT port to the BMM/BMM1H OCG IN port, and
the DLM/XLM OCG IN port to the BMM/BMM1H OCG OUT port.
Note: If installing a multi-chassis system, the OCG fiber cables may interconnect BMM/BMM1Hs
and DLM/XLMs residing on different chassis.
Step 4 Repeat Step 3 for remaining DLM/XLM to BMM/BMM1H connections.

Figure C-27 on page C-57 shows how an OCG optical fiber pair is connected between a DLM/XLM and a
BMM/BMM1H.

Figure C-27 Fiber Connections between DLM/XLMs and BMM/BMM1Hs
1 2 3 4 5 6
7A
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
1 1 1 1
OUT OUT OUT OUT
MCM
IN IN IN IN
2 2 2 2
OCG 7 OUT OCG 5 OUT OCG 3 OUT OCG 1 OUT
IN IN IN IN
BMM-4-CX1-A
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
OUT IN OUT IN OUT IN OUT IN
1 1 1 1
OUT OUT OUT OUT
DLM-7-C2-A
DLM-5-C2-A
DLM-3-C2-A
DLM-1-C2-A
IN IN IN IN
2 2 2 2
OUT OUT OUT OUT
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
1 1 1 1
LINE OUT OUT OUT OUT
IN OUT
Line IN IN IN IN 7B
2 2 2 2
OUT OUT OUT OUT
West / East
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
MCM
OUT IN IN IN IN IN
1 1 1 1
OCG 1 OUT OUT OUT OUT
Optical Fiber IN IN IN IN
OCG 3 2 2 2 2
Connections OUT OUT OUT OUT
Between
Circuit Packs OCG 5
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
1 1 1 1
OUT OUT OUT OUT
OCG 7
IN IN IN IN
2 2 2 2
OUT OUT OUT OUT
infn_117
Note: The DLM/XLM must be connected directly to a BMM/BMM1H (and not through any fiber
patch panel).
The optical fiber connections as illustrated above are shown for clarity. Infinera recom-
mends that you utilize appropriate fiber management. Infinera strongly recommends the
use of bend insensitive fiber (BIF) for all fiber connections (whenever possible). BIF cables
provide greater resistance to bending losses due to excessive bends in the fiber cables
(compared to non-BIF cables), and are identified by a Blue cable jacket. Contact your Infin-
era account team and/or an Infinera TAC resource for additional information.

To connect OCG cables between DLM/XLMs and BMM2/BMM2Hs (with GAM-1s)
When a DLM/XLM is connected to a BMM2/BMM2H, it must be connected via a Gain Adapter Module
(GAM-1) due to the increased launch power required on the BMM2/BMM2H.
Figure C-28 (top part of the figure) shows how the GAM-1 is interconnected between a DLM/XLM and a
BMM2/BMM2H on the same chassis.
Note: The GAM-1 does not have to reside in the same chassis as the DLM/XLM that it is amplify-
ing, see Figure C-28 (bottom part of the figure).
Note: The DLM/XLM must be connected directly to a GAM-1, and the GAM-1 must be connected
directly to a BMM2/BMM2H (and not through any fiber patch panel).
Figure C-28 Interconnecting the GAM-1 with DLM/XLMs and BMM2/BMM2Hs
BMM2/BMM2H DLM/XLM
GAM-1
Line System
In Out
Out In
BMM OCG
GAM OCG
DLM OCG
BMM2/BMM2H DLM/XLM/TEM/ DLM/XLM

ADLM/AXLM/SLM
GAM-1
Line System
In Out
Out In
BMM OCG DLM OCG
GAM OCG
infn_118b


There are four DLM/XLM slots on a chassis. Ensure that the OCG port on the DLM/XLM is connected to a
GAM-1 before being connected to the corresponding OCG port on the BMM2-8/BMM2H-4 as listed in
Table C-6.
Note: For 80-channel systems using half-height BMM2Hs, the BMM2H-4-R3-MS (base BMM2H)
supports OCG 1 - 4 and the BMM2H-4-B3 (expansion BMM2H) supports OCG 5 - 8.
base BMM2H.
Table C-6 DLM/XLM to BMM2/BMM2H via GAM-1 OCG Port Association
DLM/XLM OCG Ports GAM-1 System/Line Port Interconnects BMM2/BMM2H OCG Ports
DLM-1-C2 OCG 1 DLM/XLM OCG OUT -> GAM-1 SYSTEM IN BMM2-8-CXH2-MS OCG 1
DLM-1-C3 OCG 1 GAM-1 SYSTEM OUT -> DLM/XLM OCG IN BMM2-8-CH3-MS OCG 1
XLM-1-C3 OCG 1 GAM-1 LINE OUT -> BMM2/BMM2H OCG IN BMM2H-4-R3-MS OCG 1
BMM2/BMM2H OCG OUT -> GAM-1 LINE IN

Table C-6 DLM/XLM to BMM2/BMM2H via GAM-1 OCG Port Association
DLM/XLM OCG Ports GAM-1 System/Line Port Interconnects BMM2/BMM2H OCG Ports
XLM-5-C3 OCG 5 GAM-1 LINE OUT -> BMM2/BMM2H OCG IN BMM2H-4-B3 OCG 5
Step 3 Connect the DLM/XLM OCG OUT port to the GAM-1 SYSTEM IN port with fiber optic cables,
using the port association specified in Table C-6 on page C-59.
Step 4 Connect the GAM-1 SYSTEM OUT port to the DLM/XLM OCG IN port with fiber optic cables,
Step 5 Connect the GAM-1 LINE OUT port to the BMM2/BMM2H OCG IN with the fiber optic cables,
Step 6 Connect the BMM2/BMM2H OCG OUT to the GAM-1 LINE IN port with fiber optic cables, using
the port association specified in Table C-6 on page C-59.
Note: If installing a multi-chassis system, the OCG fiber cables may interconnect
BMM2/BMM2Hs, DLM/XLM, and GAM-1s residing on different chassis.
Step 7 Repeat Step 3 through Step 6 for remaining DLM/XLM -> GAM-1 -> BMM2/BMM2H connec-
tions.

Figure C-29 shows how an OCG optical fiber pair is connected between a DLM/XLM, GAM-1, and a
BMM2/BMM2H.
Figure C-29 Fiber Connections between DLM/XLMs and BMM2/BMM2Hs via GAM-1s
1 2 3 4 5 6
7A
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
GAM-1
1 1 1 1
OUT OUT OUT OUT
BMM2-8-CH3-MS
MCM
IN IN IN IN
2 2 2 2
IN IN IN IN
TAM-2-10G
TAM-2-10G
TAM-2-10G
GAM-1
1 1 1 1
OUT OUT OUT OUT
DLM-7-C2
DLM-5-C2
DLM-3-C2
DLM-1-C2
IN IN IN IN
2 2 2 2
OUT OUT OUT OUT
LINE
IN OUT
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
GAM-1
1 1 1 1
Line OUT OUT OUT OUT
IN IN IN IN 7B
West / East 2 2 2 2
OUT OUT OUT OUT
OUT IN
OCG 1
TAM-2-10G
TAM-2-10G
TAM-2-10G
MCM
IN IN IN IN
GAM-1
1 1 1 1
OCG 3
IN IN IN IN
Optical Fiber 2 2 2 2
Connections
Between OCG 5
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
Circuit Packs 1 1 1 1
OCG 7
IN IN IN IN
2 2 2 2
infn_255
Note: The DLM/XLM must be connected directly to a GAM-1, and the GAM-1 must be connected
directly to a BMM2/BMM2H (and not through any fiber patch panel).

To connect OCG cables between ADLM/AXLMs and BMM/BMM1H/BMM2/BMM2Hs (without GAMs)
The ADLM/AXLMs are tunable line modules that can be configured for one of four OCGs in a 160-channel
system, or one of two OCGs in an 80-channel system. For example, the ADLM-T4-1-C4 can be tuned to
carry signals on OCG 1, 2, 9, or 10.
Release 10.0 supports the following configurations:
ADLM/AXLMs can be connected directly to BMM2/BMM2Hs. When connected to a BMM2/BMM2H
directly, the ADLM/AXLM must be set to Gen 2 mode
ADLM/AXLMs can be connected directly to BMM/BMM1Hs. When connected to a BMM/BMM1H,
the ADLM/AXLM must be set to Gen 1 mode
Note: ADLM/AXLMs set to Gen 1 mode can be connected to BMM2/BMM2Hs but require a
GAM-1, see “To connect OCG cables between ADLM/AXLMs and BMM2/BMM2Hs (with
GAM-1s)” on page C-67.
Note: ADLM/AXLMs can be connected to BMM2Ps but require a GAM-2, see “To connect OCG
cables between ADLM/AXLMs and BMM2Ps (with GAM-2s)” on page C-77.
There are four ADLM/AXLM slots on a chassis. Ensure that the OCG port on the ADLM/AXLM is
connected to the corresponding OCG port on the BMM/BMM1H/BMM2/BMM2H as listed in Table C-7 on
page C-63.
OCG 8)
 Each BMM1H-4-CX2 supports four OCGs (OCG 1, OCG 3, OCG 5, and OCG 7)
 Each BMM2-8 (BMM2-8-CXH2-MS/BMM2-8-CH3-MS) supports eight OCGs (OCG 1, OCG 2, OCG
3, OCG 4, OCG 5, OCG 6, OCG 7, and OCG 8)
Note: For 160-channel systems using full-height BMM2s, the BMM2-8-CH3-MS (base BMM2)
supports OCG 1 - 8 and the BMM2-8-CEH3 (expansion BMM2) supports OCG 9 - 16.

Note: For 160-channel systems using full-height BMM2s, a configuration with up to 4 OCGs pro-
visioned on the expansion BMM2 requires a minimum of 1 OCG to be provisioned on the
base BMM2. A configuration with 5 to 8 OCGs provisioned on the expansion BMM2
requires a minimum of 2 OCGs to be provisioned on the base BMM2.
base BMM2H.
Table C-7 ADLM/AXLM to BMM/BMM1H/BMM2/BMM2H OCG Port Association
ADLM/AXLM OCG Ports BMM/BMM1H/BMM2/BMM2H OCG Ports
ADLM-T4-1-C4 OCG 1 BMM-4 OCG 1

AXLM-T4-1-C4 OCG 1 BMM1H-4-CX2 OCG 1
AXLM-T4-1-C5 OCG 1 BMM2-8-CXH2-MS OCG 1
BMM2-8-CH3-MS OCG 1
BMM2H-4-R3-MS OCG 1
ADLM-T4-1-C4 (tuned as OCG 2) BMM-8 OCG 2
ADLM-T4-1-C5 (tuned as OCG 2) BMM2-8-CXH2-MS OCG 2
AXLM-T4-1-C4 (tuned as OCG 2) BMM2-8-CH3-MS OCG 2
AXLM-T4-1-C5 (tuned as OCG 2) BMM2H-4-R3-MS OCG 2
BMM2-8-CH3-MS OCG 3
BMM2H-4-R3-MS OCG 3
AXLM-T4-3-C5 (tuned as OCG 4) BMM2H-4-R3-MS OCG 4


BMM2-8-CH3-MS OCG 5
BMM2H-4-B3 OCG 5
AXLM-T4-5-C5 (tuned as OCG 6) BMM2H-4-B3 OCG 6
BMM2-8-CH3-MS OCG 7
BMM2H-4-B3 OCG 7
AXLM-T4-7-C5 (tuned as OCG 8) BMM2H-4-B3 OCG 8
ADLM-T4-1-C4 (tuned as OCG 9) BMM2-8-CEH3 OCG 9
ADLM-T4-1-C5 (tuned as OCG 9)
AXLM-T4-1-C4 (tuned as OCG 9)

ADLM-T4-3-C4 tuned as OCG 12) BMM2-8-CEH3 OCG 12

ADLM-T4-3-C5 tuned as OCG 12)
ADLM-T4-5-C4 tuned as OCG 14) BMM2-8-CEH3 OCG 14
ADLM-T4-5-C5 tuned as OCG 14)
Step 3 Connect the OCG port on the ADLM/AXLM to the corresponding OCG port on the
BMM/BMM1H/BMM2/BMM2H with the fiber optic cables, using the port association specified in
Table C-7 on page C-63. For a given OCG, be sure to connect the ADLM/AXLM OCG OUT port
to the BMM/BMM1H/BMM2/BMM2H OCG IN port, and the ADLM/AXLM OCG IN port to the
BMM/BMM1H/BMM2/BMM2H OCG OUT port.
Note: If installing a multi-chassis system, the OCG fiber cables may interconnect BMM/BMM1H/
BMM2/BMM2Hs and ADLM/AXLMs residing on different chassis.
Step 4 Repeat Step 3 for remaining ADLM/AXLM to BMM/BMM1H/BMM2/BMM2H connections.

Figure C-30 shows how an OCG optical fiber pair is connected between an ADLM/AXLM and a BMM/
BMM1H/BMM2/BMM2H.

Figure C-30 Fiber Connections between ADLM/AXLMs and BMM/BMM1H/BMM2/BMM2Hs
1 2 3 4 5 6
7A
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
1 1 1 1
OUT OUT OUT OUT
BMM2-8-CH3-MS
MCM
IN IN IN IN
2 2 2 2
IN IN IN IN
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
1 1 1 1
OUT OUT OUT OUT
ADLM-T4-7-C4
ADLM-T4-5-C4
ADLM-T4-3-C4
ADLM-T4-1-C4
IN IN IN IN
2 2 2 2
OUT OUT OUT OUT
LINE
IN OUT
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
1 1 1 1
IN IN IN IN 7B
West / East 2 2 2 2
OUT OUT OUT OUT
OUT IN
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
MCM
OCG 1 IN IN IN IN
1 1 1 1
OUT OUT OUT OUT
OCG 2
Optical Fiber
Connections OCG 3 IN IN IN IN
2 2 2 2
OUT OUT OUT OUT
Between OCG 4
Circuit Packs
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
OCG 5 IN IN IN IN
1 1 1 1
OUT OUT OUT OUT
OCG 6
OCG 7 IN IN IN IN
2 2 2 2
OUT OUT OUT OUT
OCG 8
infn_256
Note: The ADLM/AXLM must be connected directly to a BMM/BMM1H/BMM2/BMM2H (and not

through any fiber patch panel).

To connect OCG cables between ADLM/AXLMs and BMM2/BMM2Hs (with GAM-1s)
ADLM/AXLMs can be connected to BMM2/BMM2Hs but require an intermediate GAM-1. When connected
to a GAM-1, the ADLM/AXLM must be set to Gen 1 mode.
Note: For connecting ADLM/AXLMs directly to BMM/BMM1H/BMM2/BMM2Hs without intermedi-

ate GAM-1s, see “To connect OCG cables between ADLM/AXLMs and BMM/BMM1H/
BMM2/BMM2Hs (without GAMs)” on page C-62.
Note: ADLM/AXLMs can be connected to BMM2Ps but require a GAM-2, see “To connect OCG
cables between ADLM/AXLMs and BMM2Ps (with GAM-2s)” on page C-77.
Figure C-31 on page C-68 (top part of the figure) shows how the GAM-1 is interconnected between an
ADLM/AXLM and a BMM2/BMM2H on the same chassis.
Note: The GAM-1 does not have to reside in the same chassis as the ADLM/AXLM that it is
amplifying, see Figure C-31 on page C-68 (bottom part of the figure).
Note: The ADLM/AXLM must be connected directly to a GAM-1, and the GAM-1 must be con-
nected directly to a BMM2/BMM2H (and not through any fiber patch panel).

Figure C-31 Interconnecting the GAM-1 with ADLM/AXLMs and BMM2/BMM2Hs
BMM2/BMM2H ADLM/AXLM
GAM-1
Line System
In Out
Out In
BMM OCG
GAM OCG
DLM OCG
BMM2/BMM2H DLM/XLM/TEM/ ADLM/AXLM

ADLM/AXLM/SLM
GAM-1
Line System
In Out
Out In
BMM OCG DLM OCG
GAM OCG
infn_118c
connected to the corresponding OCG port on the BMM2/BMM2H as listed in Table C-8 on page C-69.

base BMM2H.
Table C-8 ADLM/AXLM to BMM2/BMM2H via GAM-1 OCG Port Association
ADLM/AXLM OCG Ports GAM-1 System/Line Port Interconnects BMM2/BMM2H OCG Ports
ADLM-T4-1-C4 OCG 1 ADLM/AXLM OCG OUT -> GAM-1 SYSTEM IN BMM2-8-CXH2-MS OCG 1
ADLM-T4-1-C5 OCG 1 GAM-1 SYSTEM OUT -> ADLM/AXLM OCG IN BMM2-8-CH3-MS OCG 1
AXLM-T4-1-C4 OCG 1 GAM-1 LINE OUT -> BMM2 OCG IN BMM2H-4-R3-MS OCG 1
AXLM-T4-1-C5 OCG 1 BMM2/BMM2H OCG OUT -> GAM-1 LINE IN
ADLM-T4-1-C4 (tuned as OCG 2) ADLM/AXLM OCG OUT -> GAM-1 SYSTEM IN BMM2-8-CXH2-MS OCG 2
ADLM-T4-1-C5 (tuned as OCG 2) GAM-1 SYSTEM OUT -> ADLM/AXLM OCG IN BMM2-8-CH3-MS OCG 2
AXLM-T4-1-C4 (tuned as OCG 2) GAM-1 LINE OUT -> BMM2/BMM2H OCG IN BMM2H-4-R3-MS OCG 2
AXLM-T4-1-C5 (tuned as OCG 2) BMM2/BMM2H OCG OUT -> GAM-1 LINE IN
AXLM-T4-3-C4 OCG 3 GAM-1 LINE OUT -> BMM2/BMM2H OCG IN BMM2H-4-R3-MS OCG 3
AXLM-T4-3-C4 (tuned as OCG 4) GAM-1 LINE OUT -> BMM2/BMM2H OCG IN BMM2H-4-R3-MS OCG 4
AXLM-T4-5-C4 OCG 5 GAM-1 LINE OUT -> BMM2/BMM2H OCG IN BMM2H-4-B3 OCG 5

AXLM-T4-5-C4 (tuned as OCG 6) GAM-1 LINE OUT -> BMM2/BMM2H OCG IN BMM2H-4-B3 OCG 6
AXLM-T4-7-C4 OCG 7 GAM-1 LINE OUT -> BMM2/BMM2H OCG IN BMM2H-4-B3 OCG 7
AXLM-T4-7-C4 (tuned as OCG 8) GAM-1 LINE OUT -> BMM2/BMM2H OCG IN BMM2H-4-B3 OCG 8
ADLM-T4-1-C4 (tuned as OCG 9) ADLM/AXLM OCG OUT -> GAM-1 SYSTEM IN BMM2-8-CEH3 OCG 9
ADLM-T4-1-C5 (tuned as OCG 9) GAM-1 SYSTEM OUT -> ADLM/AXLM OCG IN
AXLM-T4-1-C4 (tuned as OCG 9) GAM-1 LINE OUT -> BMM2/BMM2H OCG IN
ADLM-T4-3-C4 tuned as OCG 12) ADLM/AXLM OCG OUT -> GAM-1 SYSTEM IN BMM2-8-CEH3 OCG 12
ADLM-T4-3-C5 tuned as OCG 12) GAM-1 SYSTEM OUT -> ADLM/AXLM OCG IN

ADLM-T4-5-C4 tuned as OCG 14) ADLM/AXLM OCG OUT -> GAM-1 SYSTEM IN BMM2-8-CEH3 OCG 14
ADLM-T4-5-C5 tuned as OCG 14) GAM-1 SYSTEM OUT -> ADLM/AXLM OCG IN
Step 3 Connect the ADLM/AXLM OCG OUT port to the GAM-1 SYSTEM IN port with fiber optic cables,
Step 4 Connect the GAM-1 SYSTEM OUT port to the ADLM/AXLM OCG IN port with fiber optic cables,
Step 5 Connect the GAM-1 LINE OUT port to the BMM2/BMM2H OCG IN with the fiber optic cables,
Step 6 Connect the BMM2/BMM2H OCG OUT to the GAM-1 LINE IN port with fiber optic cables, using
the port association specified in Table C-8 on page C-69.
Note: If installing a multi-chassis system, the OCG fiber cables may interconnect
BMM2/BMM2Hs, ADLM/AXLMs, and GAM-1s residing on different chassis.
Step 7 Repeat Step 3 through Step 6 for remaining ADLM/AXLM -> GAM-1 -> BMM2/BMM2H connec-
tions.
Figure C-32 on page C-72 shows how an OCG optical fiber pair is connected between an ADLM/AXLM,
GAM-1, and a BMM2/BMM2H.

Figure C-32 Fiber Connections between ADLM/AXLMs and BMM2/BMM2Hs via GAM-1s
1 2 3 4 5 6
7A
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
GAM-1
1 1 1 1
OUT OUT OUT OUT
BMM2-8-CH3-MS
MCM
IN IN IN IN
2 2 2 2
IN IN IN IN
TAM-2-10G
TAM-2-10G
TAM-2-10G
GAM-1
1 1 1 1
OUT OUT OUT OUT
ADLM-T4-7-C4
ADLM-T4-5-C4
ADLM-T4-3-C4
ADLM-T4-1-C4
IN IN IN IN
2 2 2 2
OUT OUT OUT OUT
LINE
IN OUT
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
GAM-1
1 1 1 1
IN IN IN IN 7B
West / East 2 2 2 2
OUT OUT OUT OUT
OUT IN
OCG 1
TAM-2-10G
TAM-2-10G
TAM-2-10G
MCM
IN IN IN IN
GAM-1
1 1 1 1
OCG 3
IN IN IN IN
Connections
Between OCG 5
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
OCG 7
IN IN IN IN
2 2 2 2
infn_255b
Note: The ADLM/AXLM must be connected directly to a GAM-1, and the GAM-1 must be con-
nected directly to a BMM2/BMM2H (and not through any fiber patch panel).

To connect OCG cables between SLMs and BMM2s
The SLMs are tunable line modules that can be configured for one of four OCGs in a 160-channel system,
or one of two OCGs in an 80-channel system. For example, the SLM-T4-1-C4 can be tuned to carry
signals on OCG 1, 2, 9, or 10.
Note: SLMs are used exclusively for DTN links operating in submarine line terminating equipment
(SLTE) mode. SLMs interoperate with full-height BMM2s (BMM2-8-CXH2-MS, BMM2-8-
CH3-MS, and/or BMM2-8-CEH3) set to SLTE Mode 1. The SLM is not interoperable with
BMMs, BMM2Ps, BMM1Hs, and/or BMM2Hs. Refer to the Infinera SLTE Turn-up and Test
Guide for additional information.

There are four SLM slots on a chassis. Ensure that the OCG port on the SLM is connected to the
corresponding OCG port on the BMM2-8 as listed in Table C-9 on page C-74.

Table C-9 SLM to BMM2 OCG Port Association
SLM OCG Ports BMM2 OCG Ports
SLM-T4-1-C4 OCG 1 BMM2-8-CXH2-MS OCG 1

SLM-T4-1-C5 OCG 1 BMM2-8-CH3-MS OCG 1
SLM-T4-1-C4 (tuned as OCG 2) BMM2-8-CXH2-MS OCG 2
SLM-T4-1-C5 (tuned as OCG 2) BMM2-8-CH3-MS OCG 2
SLM-T4-1-C4 (tuned as OCG 9) BMM2-8-CEH3 OCG 9
SLM-T4-1-C5 (tuned as OCG 9)

Step 3 Connect the OCG port on the SLM to the corresponding OCG port on the BMM2 with the fiber
optic cables, using the port association specified in Table C-9 on page C-74. For a given OCG,
be sure to connect the SLM OCG OUT port to the BMM2 OCG IN port, and the SLM OCG IN
port to the BMM2 OCG OUT port.
Note: If installing a multi-chassis system, the OCG fiber cables may interconnect BMM2s and
SLMs residing on different chassis.
Step 4 Repeat Step 3 for remaining SLM to BMM2 connections.

Figure C-33 on page C-76 shows how an OCG optical fiber pair is connected between an SLM and a
BMM2.

Figure C-33 Fiber Connections between SLMs and BMM2s
1 2 3 4 5 6
7A
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
1 1 1 1
OUT OUT OUT OUT
BMM2-8-CH3-MS
MCM
IN IN IN IN
2 2 2 2
IN IN IN IN
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
1 1 1 1
OUT OUT OUT OUT
SLM-T4-7-C4
SLM-T4-5-C4
SLM-T4-3-C4
SLM-T4-1-C4
IN IN IN IN
2 2 2 2
OUT OUT OUT OUT
LINE
IN OUT
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
1 1 1 1
IN IN IN IN 7B
West / East 2 2 2 2
OUT OUT OUT OUT
OUT IN
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
MCM
OCG 1 IN IN IN IN
1 1 1 1
OUT OUT OUT OUT
OCG 2
Optical Fiber
Connections OCG 3 IN IN IN IN
2 2 2 2
OUT OUT OUT OUT
Between OCG 4
Circuit Packs
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
OCG 5 IN IN IN IN
1 1 1 1
OUT OUT OUT OUT
OCG 6
OCG 7 IN IN IN IN
2 2 2 2
OUT OUT OUT OUT
OCG 8
infn_256b
Note: The SLM must be connected directly to a BMM2 (and not through any fiber patch panel).

To connect OCG cables between ADLM/AXLMs and BMM2Ps (with GAM-2s)
ADLM/AXLMs can be connected to BMM2Ps but require an intermediate GAM-2. When connected to a
GAM-2, the ADLM/AXLM must be set to Gen 2 mode.
Note: The GAM-2 does not have to reside in the same chassis as the ADLM/AXLM that it is
amplifying.
connected to the corresponding OCG port on the BMM2P.
(base BMM2P)
Note: For 160-channel systems using full-height BMM2Ps, the BMM2P-8-CH1-MS (base
BMM2P) supports OCG 1 - 8 and the BMM2P-8-CEH1 (expansion BMM2P) supports
OCG 9 - 16.
Note: For 160-channel systems using BMM2Ps, a configuration with up to 4 OCGs provisioned
on the expansion BMM2P requires a minimum of 1 OCG to be provisioned on the base
BMM2P. A configuration with 5 to 8 OCGs provisioned on the expansion BMM2P requires
a minimum of 2 OCGs to be provisioned on the base BMM2P.

Figure C-34 Interconnecting the GAM-2 with BMM2Ps and ADLM/AXLMs
BMM2P DLM/XLM/TEM/ ADLM/AXLM

ADLM/AXLM/SLM
GAM-2
P2 P1
In Out
Amp Amp
BMM OCG DLM OCG
Out In
GAM OCG
infn_547b
Step 1 Ensure the fiber optic cables are clean and labeled. Refer to Figure C-34 when performing this
procedure.
Step 3 Connect the ADLM/AXLM OCG OUT port to the GAM-2 P1 AMP IN port.
Step 4 Connect the GAM-2 P2 AMP OUT port to the BMM2P OCG IN port.
Step 5 Connect the BMM2P OCG OUT port to the GAM-2 P2 IN port.
Step 6 Connect the GAM-2 P1 OUT port to the ADLM/AXLM OCG IN port.
Note: If installing a multi-chassis system, the OCG fiber cables may interconnect BMM2Ps,
GAM-2s, and ADLM/AXLMs residing on different chassis.
Step 7 Repeat Step 3 through Step 6 for remaining ADLM/AXLM OCGn -> BMM2P OCGn connections.
Figure C-35 on page C-79 shows how an OCG optical fiber pair is connected between an ADLM/AXLM,
GAM-2, and a BMM2P.

Figure C-35 Fiber Connections between ADLM/AXLMs and BMM2Ps via GAM-2s
1 2 3 4 5 6
7A
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
GAM-1
1 1 1 1
OUT OUT OUT OUT
BMM2P-8-CH1-MS
MCM
IN IN IN IN
2 2 2 2
IN IN IN IN
TAM-2-10G
TAM-2-10G
TAM-2-10G
GAM-1
1 1 1 1
OUT OUT OUT OUT
ADLM-T4-7-C4
ADLM-T4-5-C4
ADLM-T4-3-C4
ADLM-T4-1-C4
IN IN IN IN
2 2 2 2
OUT OUT OUT OUT
LINE
IN OUT
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
GAM-1
1 1 1 1
IN IN IN IN 7B
West / East 2 2 2 2
OUT OUT OUT OUT
OUT IN
OCG 1
TAM-2-10G
TAM-2-10G
TAM-2-10G
MCM
IN IN IN IN
1 1 1 1
GAM-2
OCG 3
IN IN IN IN
Connections
Between OCG 5
TAM-2-10G
TAM-2-10G
TAM-2-10G
TAM-2-10G
IN IN IN IN
OCG 7
IN IN IN IN
2 2 2 2
infn_255c
Note: The optical fiber connections as illustrated above are shown for clarity. Infinera recom-

To connect OCH and OCG cables between ADLM-80/AXLM-80/SLM-80s, CMMs, and BMMs
The ADLM-80/AXLM-80/SLM-80s are C-Band tunable line modules that contain two ports (for transmitting
and receiving two single 40Gbps or 20Gbps DWDM wavelengths) and support Optical Carrier Groups
(OCGs) 1 - 16 in a 160-channel system. The CMMs multiplex/demultiplex up to twenty Infinera wavelength
optical channels (OCHs) onto two OCGs.
The ADLM-80/AXLM-80/SLM-80 is optically connected to a CMM (on the OCH side) and the CMM is
optically connected to a BMM (on the OCG side).
There are four ADLM-80/AXLM-80/SLM-80/CMM slots on a chassis. Ensure that the OCG port on the
CMM is connected to the corresponding OCG port on the BMM as listed in Table C-10 on page C-81.
 Each CMM1D-20-CR supports eight OCGs (OCG 1, OCG 2, OCG 3, OCG 4, OCG 9, OCG 10,
OCG 11, and OCG 12)
 Each CMM1D-20-CB supports eight OCGs (OCG 5, OCG 6, OCG 7, OCG 8, OCG 13, OCG 14,
OCG 15, and OCG 16)
OCG 8)
 Each BMM1H supports four OCGs (OCG 1, OCG 3, OCG 5, and OCG 7)

(base BMM2P)

Table C-10 CMM to BMM OCG Port Association
CMM OCG Ports BMM OCG Ports
CMM1D-20-CR Line 1 OCGs 1 - 4, 9 - 12 BMM-4 OCG 1

BMM1H OCG 1
BMM2-8-CH3-MS OCG 1
BMM2H-4-R3-MS OCG 1
CMM1D-20-CR Line 2 OCGs 1 - 4, 9 - 12 BMM2-8-CXH2-MS OCG 2
BMM2-8-CH3-MS OCG 2
BMM2H-4-R3-MS OCG 2
BMM1H OCG 3
BMM2-8-CH3-MS OCG 3
BMM2H-4-R3-MS OCG 3
CMM1D-20-CR Line 2 OCGs 1 - 4, 9 - 12 BMM2-8-CXH2-MS OCG 4
BMM2-8-CH3-MS OCG 4
BMM2H-4-R3-MS OCG 4
CMM1D-20-CB Line 1 OCGs 5 - 8, 13 - 16 BMM-4 OCG 5
BMM1H OCG 5
BMM2-8-CH3-MS OCG 5
BMM2H-4-B3-MS OCG 5

Table C-10 CMM to BMM OCG Port Association
CMM OCG Ports BMM OCG Ports

CMM1D-20-CB Line 2 OCGs 5 - 8, 13 - 16 BMM2-8-CXH2-MS OCG 6
BMM2-8-CH3-MS OCG 6
BMM2H-4-B3-MS OCG 6
BMM1H OCG 7
BMM2-8-CH3-MS OCG 7
BMM2H-4-B3-MS OCG 7
CMM1D-20-CB Line 2 OCGs 5 - 8, 13 - 16 BMM2-8-CXH2-MS OCG 8
BMM2-8-CH3-MS OCG 8
BMM2H-4-B3-MS OCG 8
CMM1D-20-CR Line 1 OCGs 1 - 4, 9 - 12 BMM2-8-CEH3 OCG 9
CMM1D-20-CR Line 2 OCGs 1 - 4, 9 - 12 BMM2P-8-CEH1 OCG 9
CMM1D-20-CB Line 1 OCGs 5 - 8, 13 - 16 BMM2-8-CEH3 OCG 13
CMM1D-20-CB Line 2 OCGs 5 - 8, 13 - 16 BMM2P-8-CEH1 OCG 13

Step 3 Connect the OCH n (n = 1 or 2) port on the ADLM-80/AXLM-80/SLM-80 to any available OCH
port on the CMM (Line 1, CH 1 - CH 10 or Line 2, CH 1 - CH 10) with the fiber optic cables.
Step 4 Connect the OCG port on the CMM (Line 1 or Line 2) to the corresponding OCG port on the
BMM with the fiber optic cables, using the port association specified in Table C-10 on page C-
81. For a given OCG, be sure to connect the CMM OCG OUT port to the BMM OCG IN port, and
the CMM OCG IN port to the BMM OCG OUT port.
Note: If Gen 1 BMMs are used, ensure that a 15.0dB attenuator pad is plugged into the BMM
OCG IN port to meet the power requirements for Auto-discovery.
Note: If installing a multi-chassis system, the OCH and OCG fiber cables may interconnect
ADLM-80/AXLM-80/SLM-80s, CMMs, and BMMs residing on different chassis.
Step 5 Repeat Step 3 and Step 4 for remaining ADLM-80/AXLM-80/SLM-80 to CMM, and CMM to
BMM connections.
Figure C-36 on page C-84 shows how OCH and OCG optical fiber pairs are connected between an ADLM-
80/AXLM-80/SLM-80, a CMM, and a BMM.

Figure C-36 Fiber Connections between ADLM-80/AXLM-80/SLM-80s, CMMs, and BMMs
1 2 3 4 5 6
7A
TAM-2-10G
IN
1
OUT
BMM2-8-CH3-MS
MCM
IN
CMM1D-20-CR
2
OUT
TAM-2-10G
IN
1
OUT
IN
2 LINE 1 LINE 2
OUT OUT IN OUT IN
AXLM-80-T1-C5
LINE
OCG 1-4, 9-12 OCG 1-4, 9-12
IN OUT
TAM-2-10G
IN OUT IN OUT IN
1 CH 1
Line OUT
CH 2
IN CH 3 7B
West / East 2
OUT
OUT IN CH 4
CH 5
TAM-2-10G
MCM
OCG 1 IN
1
CH 6
OUT
OCG 2 OCH1
CH 7
Optical Fiber IN
Connections OCG 3 IN
CH 8
OUT 2
OUT
Between OCG 4 CH 9
OCH2
Circuit Packs IN CH 10
TAM-2-10G
OCG 5 IN
OUT 1
OUT
OCG 6
OCG 7 IN
2
OUT
OCG 8
infn_765
Note: The optical fiber connections as illustrated above are shown for clarity. Infinera recom-

To route the OCG and tributary port fiber optic cables
The line module OCG and tributary fiber optic cables are routed through the fiber guides to the fiber trays.
Step 1 Route the line module OCG port and tributary fiber optic cables connected to the TOM ports on
the TAM in sub-slot 1 through 5 through the fiber guides as shown in Figure C-37 on page C-86:
Step 1a The fibers from the TAM in sub-slot 1 are routed through the fiber guide cable hold-
ers closest to the faceplate, in stair stepped routing.
Step 1b The fibers from the TAM in sub-slot 2 are routed through the fiber guide cable hold-
ers in the 2nd column closest to the faceplate, in stair stepped routing.
Step 1c The fibers from the TAM in sub-slot 3 are routed through the fiber guide cable hold-
ers in the 3rd column closest to the faceplate, in stair stepped routing.
Step 1d The fibers from the TAM in sub-slot 4 are routed through the fiber guide cable hold-
ers in the 4th column closest to the faceplate, in stair stepped routing.
Step 1e The fibers from the TAM in sub-slot 5 are routed directly through the fiber guide tray.
Step 2 Repeat Step 1 for each installed line module.
Step 3 Route all the fiber optic cables from the line module in slot 3 and slot 4 to the left half of the fiber
guide tray (see Figure C-38 on page C-87).
Step 4 Route all the fiber optic cables from the line module in slot 5 and slot 6 to the right half of the
fiber guide tray (see Figure C-38 on page C-87).
Note: The DTC is shipped with slack managers pre-installed for the 23-inch rack in 5-inch and 6-
inch forward mount configurations (see Figure C-38 on page C-87). The MTC is shipped
without slack managers pre-installed (refer to the Infinera DTN and DTN-X Site Prepara-
tion and Hardware Installation Guide). For the remaining DTC/MTC configurations, an
external slack management tray must be used.
Step 5 Remove the slack on the fiber optic cables by wrapping the extra fiber around the slack manag-
ers, if present on the chassis, or by using an external slack manager tray (see Figure C-38 on
page C-87).

Figure C-37 Route the Line Module Fiber Optic Cables through the Fiber Guides
TOM Slot 1
TAM Slot 1
TOM Slot 2
From OCG IN and

OCG OUT Ports
TOM Slot 1
TAM Slot 2
TOM Slot 2
Fiber Guide
TOM Slot 1
TAM Slot 3
TOM Slot 2
Stair Stepping
Fiber Cable through
the Fiber Guide infn_075

Figure C-38 Routing the Fiber Optic Cables through the Bottom Fiber Guide Tray
Fiber Optic
Cable
TOM
TAM
Fiber Guide
Slack
Manager
Fiber Guide
Tray
infn_076

To connect expansion fiber cables between a base and expansion BMM2 (160-channel systems)
For 160-channel systems using full-height BMM2s, the BMM2-8-CH3-MS (base BMM2) supports
OCG 1 - 8 and the BMM2-8-CEH3 (expansion BMM2) supports OCG 9 - 16.
Perform the following to connect expansion fiber cables between a base and an expansion BMM2.
Step 2 At the base BMM2 (BMM2-8-CH3-MS), connect an expansion fiber to the IN (receive) port of the
Expansion BMM2 connector.
Step 3 At the expansion BMM2 (BMM2-8-CEH3), connect the opposite end of the expansion fiber to the
OUT (transmit) port of the Base BMM2 connector.
Step 4 At the base BMM2 (BMM2-8-CH3-MS), connect an expansion fiber to the OUT (transmit) port of
the Expansion BMM2 connector.
Step 5 At the expansion BMM2 (BMM2-8-CEH3), connect the opposite end of the expansion fiber to the
IN (receive) port of the Base BMM2 connector.
Step 6 If no other cabling is required, reinstall the DTC/MTC front cover and/or door, refer to the Infinera
To connect expansion fiber cables between a base and expansion BMM2P (160-channel systems)
For 160-channel systems using full-height BMM2Ps, the BMM2P-8-CH1-MS (base BMM2P) supports
OCG 1 - 8, and the BMM2P-8-CEH1 (expansion BMM2P) supports OCG 9 - 16.
Perform the following to connect expansion fiber cables between a base and an expansion BMM2P.
Step 2 At the base BMM2P (BMM2P-CH1-MS), connect an expansion fiber to the IN (receive) port of
the Expansion BMM2P connector.
Step 3 At the expansion BMM2P (BMM2P-CEH1), connect the opposite end of the expansion fiber to
the OUT (transmit) port of the Base BMM2P connector.
Step 4 At the base BMM2P (BMM2P-CH1-MS), connect an expansion fiber to the OUT (transmit) port of
the Expansion BMM2P connector.
Step 5 At the expansion BMM2P (BMM2P-CEH1), connect the opposite end of the expansion fiber to
the IN (receive) port of the Base BMM2P connector.

To connect expansion fiber cables between a base and expansion BMM2H (80-channel systems)
For 80-channel systems using half-height BMM2Hs, the BMM2H-4-R3-MS (base BMM2H) supports
OCG 1 - 4 and the BMM2H-4-B3 (expansion BMM2H) supports OCG 5 - 8.
Perform the following to connect expansion fiber cables between a base and an expansion BMM2H.
Step 2 At the base BMM2H (BMM2H-4-R3-MS), connect an expansion fiber to the IN (receive) port of
the Expansion BMM2H connector.
Step 3 At the expansion BMM2H (BMM2H-4-B3), connect the opposite end of the expansion fiber to the
OUT (transmit) port of the Base BMM2H connector.
Step 4 At the base BMM2H (BMM2H-4-R3-MS), connect an expansion fiber to the OUT (transmit) port
of the Expansion BMM2H connector.
Step 5 At the expansion BMM2H (BMM2H-4-B3), connect the opposite end of the expansion fiber to the
IN (receive) port of the Base BMM2H connector.
To connect line side fiber cables to the DTN
Each DTC may contain up to two (2) BMMs, each supporting two line ports (IN/receive and OUT/transmit)
for line side fiber cables.
Step 2 Connect the incoming line side fiber to the IN (receive) line port on the BMM.
Step 3 Connect the outgoing line side fiber to the OUT (transmit) line port on the BMM.
Step 4 Repeat Step 2 and Step 3 for each BMM.
Step 5 If no other cabling is required, reinstall the DTC/MTC front cover and/or door (refer to the Infin-
era DTN and DTN-X Site Preparation and Hardware Installation Guide).

To connect line side fiber cables between two DTNs
Each DTN can contain up to two (2) BMMs. It is recommended that a node numbering scheme be
established for the network. For example, eastbound traffic numbering is from the BMM slot 1 (Node A) to
the BMM slot 2 (Node B) and westbound traffic is from the BMM slot 2 (Node B) to the BMM slot 1 (Node
A).
Step 2 Connect line fibers from the OUT (transmit) line port on the BMM slot 1 (Node A) to the IN
(receive) line port on the BMM slot 2 (Node B) for eastbound traffic.
Step 3 Connect line fibers from the OUT (transmit) line port on the BMM slot 2 (Node B) to the IN
(receive) line port on the BMM slot 1 (Node A) for westbound traffic.
To connect line side fiber cables from the DTN to an Optical Amplifier
Each DTC may contain up to two (2) BMMs and each Optical Amplifier may contain up to two (2) OAMs. It
is recommended that a node numbering scheme be established for the network. For example, eastbound
traffic numbering is from the BMM slot 1 (Node A) to the OAM slot 2 (Node B) and westbound traffic is from
the OAM slot 2 (Node B) to the BMM slot 1 (Node A).
Step 2 Connect line fibers from the OUT (transmit) line port on the BMM slot 1 (Node A) to the IN
(receive) line port on the OAM slot 2 (Node B) for eastbound traffic.
Step 3 Connect line fibers from the OUT (transmit) line port on the OAM slot 2 (Node B) to the IN
(receive) line port on the BMM slot 1 (Node A) for westbound traffic.
DTN Site Preparation and Hardware Installation Guide.

Connect and Route OTC Fiber Optic Cables

CAUTION
and Class 1M.
CAUTION
To connect and route fiber optic cables, perform the following sequence (depending on system
configuration):
1. “To connect and route the OAM/ORM fiber optic cables” on page C-91.
2. “To connect the OSC jumper” on page C-92.
To connect and route the OAM/ORM fiber optic cables
To provide line amplification for signals going from West to East, the Line IN port on a given OAM/ORM is
connected to the incoming fiber from one direction (for example, West) while the Line OUT port on the
same OAM/ORM is connected to the outgoing fiber in the opposite direction (for example, East). As a
result, the receiver on the OAM/ORM receives from one direction and the transmitter on the same OAM/
ORM transmits toward the opposite direction.
Step 1 Insert a pair of clean, labeled fiber optic cables into the connectors in each OAM/ORM for the
physical insertion of the cables as shown in Figure C-39 on page C-92.
Step 2 Route the cables toward the right side through the fiber guide (located on the chassis).
Step 3 Secure the cable pairs using tie-downs or wrap extra fiber around a slack manager. The OTC
supports optional slack management ears, Infinera P/N O-FIBMGMT-B1.

Page C-92 Connect and Route OTC Fiber Optic Cables
Figure C-39 Physically Connecting the Fiber Optic Cables

DCM Connectors
on OAM/ORM Fiber Guide
CA
UT
IO
N
OAMs
ORMs
Fiber Guide
Fiber Optic Cable infn_251
To connect the OSC jumper
The OSC jumper transmits OSC signals between OAM/ORMs in a bidirectional Optical Amplifier. With this
configuration, an OAM/ORM failure would impact the OSC in one direction only, and the node would still be
accessible. To connect the OSC jumper, take the following steps:
Step 1 Using the OSC optical patch cord (SC to SC fiber cable, shipped with the OAM/ORM), connect
the OSC OUT port on the first OAM/ORM to the OSC IN port on the second OAM/ORM.
Step 2 Using another OSC optical patch cord, connect the OSC IN port on the first OAM/ORM to the
OSC OUT port on the second OAM/ORM.

To connect OCG cables between XTC line modules and OTC BMM2Cs
system, or one of two OCGs in an 80-channel system. For example, the AOLX-500-T4-1-C5 can be tuned
XTC line modules are optically connected to an OTC BMM2C, and can be installed in upper universal card
slots A-1 through A-5 and/or lower universal card slots B-1 through B-5 of the XTC-10, and/or universal
slots A-1 through A-4 of the XTC-4.
Ensure that the OCG port on the XTC line module is connected to the corresponding OCG port on the
OTC BMM2C as listed in Table C-11 on page C-94.
Each BMM2C-16-CH supports sixteen OCGs (OCG 1, OCG 2, OCG 3, OCG 4, OCG 5, OCG 6, OCG 7,
OCG 8, OCG 9, OCG 10, OCG 11, OCG 12, OCG 13, OCG 14, OCG 15, and OCG 16
Note: The BMM2C can only be connected to DTN-X line modules (DTN line modules must not be
connected to a BMM2C). For OTS interoperability, the BMM2C must be connected to a
BMM2, BMM2C, or BMM2P. A BMM-to-BMM2C connection is not supported. Also note
that the DTN-X line modules must be set to Gen 1 mode.
Note: For 160-channel systems using BMM2Cs, a configuration with up to 4 OCGs provisioned
requires a minimum of 1 OCG to be provisioned.

Table C-11 XTC Line Module to OTC BMM2C OCG Port Association
XTC Line Module OCG Ports OTC BMM2C OCG Ports
AOLM-500-T4-1-C5/C6 OCG 1 BMM2C-16-CH OCG 1

AOLX-500-T4-1-C5/C6 OCG 1
AOLM-500B-T4-1-C5/C6 OCG 1
AOLX-500B-T4-1-C5/C6 OCG 1
SOLM-500-T4-1-C11 OCG 1
SOLX-500-T4-1-C11 OCG 1
AOLM2-500-T4-1-C5/C6/C8 OCG 1
AOLX2-500-T4-1-C5/C6/C8 OCG 1
AOLM2-500B-T4-1-C5/C6/C8OCG 1
SOLM2-500-T4-1-C12/C13 OCG 1
SOLX2-500-T4-1-C12/C13 OCG 1
SOLM2-500B-T4-1-C12/C13 OCG 1
SOLX2-500B-T4-1-C12/C13 OCG 1
AOLM-500-T4-1-C5/C6 (tuned as OCG 2) BMM2C-16-CH OCG 2
AOLX-500-T4-1-C5/C6 (tuned as OCG 2)
SOLM-500-T4-1-C11 (tuned as OCG 2)
SOLX-500-T4-1-C11 (tuned as OCG 2)
AOLM2-500-T4-1-C5/C6/C8 (tuned as OCG 2)
AOLX2-500-T4-1-C5/C6/C8 (tuned as OCG 2)


SOLM-500-T4-3-C11 OCG 3
SOLX-500-T4-3-C11 OCG 3
AOLM2-500-T4-3-C5/C6/C8 OCG 3
AOLX2-500-T4-3-C5/C6/C8 OCG 3
AOLM2-500B-T4-3-C5/C6/C8 OCG 3
SOLM2-500-T4-3-C12/C13 OCG 3
SOLX2-500-T4-3-C12/C13 OCG 3
SOLM2-500B-T4-3-C12/C13 OCG 3
SOLX2-500B-T4-3-C12/C13 OCG 3


SOLM-500-T4-5-C11 OCG 5
SOLX-500-T4-5-C11 OCG 5
AOLM2-500-T4-5-C5/C6/C8 OCG 5
AOLX2-500-T4-5-C5/C6/C8 OCG 5
SOLM2-500-T4-5-C12/C13 OCG 5
SOLX2-500-T4-5-C12/C13 OCG 5
SOLM2-500B-T4-5-C12/C13 OCG 5
SOLX2-500B-T4-5-C12/C13 OCG 5


SOLM-500-T4-7-C11 OCG 7
SOLX-500-T4-7-C11 OCG 7
AOLM2-500-T4-7-C5/C6/C8 OCG 7
AOLX2-500-T4-7-C5/C6/C8 OCG 7
SOLM2-500-T4-7-C12/C13 OCG 7
SOLX2-500-T4-7-C12/C13 OCG 7
SOLM2-500B-T4-7-C12/C13 OCG 7
SOLX2-500B-T4-7-C12/C13 OCG 7


SOLM2-500-T4-1-C12/C13 OCG 9
SOLX2-500-T4-1-C12/C13 OCG 9
SOLM2-500B-T4-1-C12/C13 OCG 9
SOLX2-500B-T4-1-C12/C13 OCG 9


AOLM-500-T4-3-C5/C6 tuned as OCG 12) BMM2C-16-CH OCG 12
AOLX-500-T4-3-C5/C6 tuned as OCG 12)
SOLM-500-T4-3-C11 tuned as OCG 12)
SOLX-500-T4-3-C11 tuned as OCG 12)
AOLM2-500-T4-3-C5/C6/C8 tuned as OCG 12)
AOLX2-500-T4-3-C5/C6/C8 tuned as OCG 12)


AOLM-500-T4-5-C5/C6 tuned as OCG 14) BMM2C-16-CH OCG 14
AOLX-500-T4-5-C5/C6 tuned as OCG 14)
SOLM-500-T4-5-C11 tuned as OCG 14)
SOLX-500-T4-5-C11 tuned as OCG 14)
AOLM2-500-T4-5-C5/C6/C8 tuned as OCG 14)
AOLX2-500-T4-5-C5/C6/C8 tuned as OCG 14)



Step 3 Connect the OCG port on the XTC line module to the corresponding OCG port on the OTC
BMM2C with the fiber optic cables, using the port association specified in Table C-11 on page C-
94. For a given OCG, be sure to connect the XTC line module OCG OUT port to the OTC
BMM2C OCG IN port, and the XTC line module OCG IN port to the OTC BMM2C OCG OUT
port.
Note: The BMM2C can only be connected to DTN-X line modules (DTN line modules must not be
connected to a BMM2C). For OTS interoperability, the BMM2C must be connected to a
BMM2, BMM2C, or BMM2P. A BMM-to-BMM2C connection is not supported. Also note that
the DTN-X line modules must be set to Gen 1 mode.
Step 4 Repeat Step 3 for remaining XTC line module to OTC BMM2C connections.
Figure C-40 on page C-103 (for XTC-10 and XTC-4) shows how OCG optical fiber pairs are connected
between XTC line modules and OTC BMM2Cs.

Figure C-40 Fiber Connections between XTC-10/XTC-4 Line Modules and OTC BMM2Cs
A-6A/
A-1/B-1 A-2/B-2 A-3/B-3 A-4/B-4 A-5/B-5 B-6B
XTC-10
TIM-1-100G
TIM-1-100G
TIM-1-100G
TSM
Line Module
Line Module
TIM-1-100G
TIM-1-100G
TIM-1-100G
IN OUT IN OUT
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
TIM-5-10G
TIM-5-10G
OTM-500/OTM2-500
OTM-500/OTM2-500
OTM-500/OTM2-500
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
TIM-5-10G
TIM-5-10G
XCM
Connected
TIM-1-40G
TIM-1-40G
TIM-5-10G
TIM-5-10G
TIM-5-10G
TIM-5-10G
to OCG 1
Connected
to OCG 3
Optical Fiber A-6B/

Connections B-6A
Between
Circuit Packs
LINE
IN OUT
OTC
with 3
BMM2C
(in slot 3) 1 BMM2C-16-CH
infn_1048
OCG


Appendix D
Raman Fiber Connector Cleaning
This chapter provides procedures to identify and clean the removable and non-removable fiber
connectors, and client fiber connectors used on the Raman Amplifier Modules (RAMs; RAM-1, RAM-2-OR,
and REM-2) and Optical Raman Modules (ORMs) which are installed in the Optical Transport Chassis
(OTC), and Infinera Line System (ILS) Raman Modules (IRMs) which are installed in the Modular
Transport Chassis (MTC-9). This chapter includes the following sections:
“Optical Connector Inspection Standards” on page D-2
“Removing the RAM/ORM/IRM and Identifying Fiber Connectors” on page D-3
“Cleaning the Removable Connector” on page D-9
“Cleaning the Non-removable Connector” on page D-12
“Cleaning the Client Fiber Connector” on page D-13
“Installing the RAM/ORM/IRM” on page D-14
Note: Unless specifically noted otherwise, all references to the RAM will refer to either the
RAM-1, RAM-2-OR, or REM-2 interchangeably.
Note: The procedures documented in this chapter assume that the user is familiar with fiber
cleaning and inspection standards as well as items used in the cleaning of fiber optic
cables and connectors including Cletop cleaning cartridges and video fiberscopes.

Page D-2 Raman Fiber Connector Cleaning
Optical Connector Inspection Standards

 Chip—divots, voids in the ferrule or the fiber
 Loose contaminant—any contaminant such as dirt, dust, film, or flakes that can be removed by the
cleaning process
 Fixed contaminant—any contaminant that cannot be removed by the cleaning process
 Pit—a divot in the surface
 Speck—a small particle

 Scratch (fine and deep)—a defect on a polished optical surface deep enough for the base material
to be visible
Figure D-1 Optical Connector End-face Quality Criteria

Zone A
Zone B
Zone C
Zone D
infn_140
Table D-1 Allowable Defects per Zone
Zone Zone Size Allowable Defects
A 0 to 25μm None
B 25 to 125μm No more than two scratches < 2μm
No more than two pits or chips < 5μm
No more than two contaminates < 5μm
C 125 to 250μm Any number of scratches < 2μm
Any number of pits or chips < 10μm
Any number of contaminates < 10μm
D > 250μm Any number of scratches < 4μm
Any number of pits or chips < 20μm
Any number of contaminates < 20μm

Raman Fiber Connector Cleaning Page D-3
Removing the RAM/ORM/IRM and

Identifying Fiber Connectors
CAUTION
and Class 1M.
CAUTION
Note: This procedure assumes that the RAM/ORM/IRM has been placed Out-of-service with the
Admin State set to Lock.
Ensure that you have the necessary tools and fiber cleaning supplies as outlined in “Required Tools and
Test Equipment” on page 2-5.
To remove the RAM/ORM/IRM and identify the fiber connectors
Step 1 For RAM/ORMs only.

Step 1a Loosen the ejectors on the RAM/ORM by turning the ejector screw one quarter turn
using a #1 Phillips screwdriver.
Step 1b Open the left and right side ejectors simultaneously to the full-open position (perpen-
dicular to the faceplate) and disengage the RAM/ORM from the backplane so that it
powers off.
Step 2 For IRMs only:
Step 2a Loosen the captive screw using a #2 Phillips screwdriver.
Step 2b Using your thumb and forefinger, squeeze the ejector handles on the IRM to unlatch
and open the ejector handles and disengage the IRM from the backplane so that it
powers off.
Step 3 Label and remove the fibers attached to the RAM/ORM/IRM.
Step 4 Holding the ejectors, slide the RAM/ORM/IRM all the way out of the OTC/MTC-9 and place
RAM/ORM/IRM on a work bench (or suitable working area).

Step 5 There are two types of connectors used on the RAM/ORM/IRM: removable and non-removable.
Identify the fiber connectors depending on the module type:
For RAM-1/RAM-2-OR connectors, see Figure D-2
For REM-2 connectors, see Figure D-3 on page D-5
For ORM-CXH1-MS connectors, see Figure D-4 on page D-6
For ORM-CXH1 connectors, see Figure D-5 on page D-7
For IRM-B-ECXH1 connectors, see Figure D-6 on page D-8
Step 6 Proceed to “To clean the removable connector” on page D-9.
Figure D-2 RAM-1/RAM-2-OR Connectors

Ejector High Power Connector Ejector
INVISIBLE LASER
RADIATION
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
1426 - 1610nm - 1mW
REMOVABLE CONNECTOR
Warning Label
INVISIBLE LASER
Non-removable Connectors RADIATION Fiber Guide
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
1426 - 1610nm - 1mW infn_041

Figure D-3 REM-2 Connectors
Ejector High Power Connector Ejector

INVISIBLE LASER
RADIATION
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
1426 - 1610nm - 1mW
REMOVABLE CONNECTOR
Warning Label
INVISIBLE LASER
Non-removable RADIATION Fiber Guide
Connector DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
1426 - 1610nm - 1mW infn_035

Figure D-4 ORM-CXH1-MS Connectors

INVISIBLE LASER
RADIATION
DO NOT VIEW
DIRECTLY WITH
OPTICAL
Non-removable Connectors INSTRUMENTS
CLASS 1M LASER
PRODUCT (IEC)
CLASS I LASER
Non-removable Removable PRODUCT (CDRH)
Connectors Connector 1550nm-50mW
Warning Label
OSA MONITOR
ORM-CXH1-MS
S/N
CLEI
INVISIBLE LASER
RADIATION
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT (IEC)
CLASS I LASER
PRODUCT (CDRH)
1550nm-50mW
REMOVABLE CONNECTOR
Ejector Fiber Guide Ejector infn_248

Figure D-5 ORM-CXH1 Connectors

Non-removable Connectors
Removable
Ejector Connector
L-BAND
L-BAND PUMP ORM-CXH1 S/N
CLEI
INVISIBLE LASER
RADIATION
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
REMOVABLE CONNECTOR 1425-1620nm
10mW
OSA MONITOR
Warning Label
Non-removable INVISIBLE LASER Fiber Ejector
Connectors RADIATION Guide
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
1425-1620nm
10mW infn_477

Figure D-6 IRM-B-ECXH1 Connectors
INVISIBLE LASER
RADIATION
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
RAYONNEMENT
LASER INVISIBLE
NE PAS REGARDER
DIRECTEMENT AVEC
DES INSTRUMENTS
OPTIQUES
LASER PRODUCT
PRODUIT LASER
Removable
CLASS 1M
Connector 1525-1565 nm
135 mW
Warning Label
SYSTEM
LINE
OTDR
OSA
DIRECTEMENT AVEC
NE PAS REGARDER
DES INSTRUMENTS
LASER PRODUCT
INVISIBLE LASER
LASER INVISIBLE
PRODUIT LASER
ACT
LOS
DIRECTLY WITH
RAYONNEMENT
INSTRUMENTS
DO NOT VIEW
1525-1565 nm
LOS
ACT
RADIATION
OPTIQUES
CLASS 1M
OPTICAL
135 mW
LINE
OSA
OSA
SYS
PWR
ACT
FLT
CLEI S/N IRM-B-ECXH1
Ejector Non-removable Connectors Captive

Ejector
Screw infn_1220

Cleaning the Removable Connector

CAUTION
and Class 1M.
CAUTION
CAUTION
High Power Connector—The connector (both internal and external) and the corresponding
fiber optic cable must be cleaned to prevent permanent damage due to contamination.
To clean the removable connector
Step 1 Install the SC bulkhead adapter tip onto the fiberscope. Open the shutter on the bulkhead
adapter and insert the fiberscope tip. On the hand-held display, examine the cleanliness of the
removable connector end face compared to the criteria listed in “Optical Connector Inspection
Standards” on page D-2. If it passes the inspection criteria, proceed to “To clean the non-remov-
able connector” on page D-12. Otherwise, continue with Step 2.
Step 2 Loosen the two ¼-turn fasteners securing the connector bracket to the RAM/ORM/IRM and pull
it out from the module just far enough to disengage the SC pigtail from the shuttered bulkhead
adapter. See Figure D-7 on page D-10.
Note: Use caution when pulling the SC pigtail and ensure that the pigtail does not extend beyond
1 inch past the boot.

Figure D-7 RAM/ORM/IRM Removable Connector
INVISIBLE LASER
RADIATION
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
1426 - 1610nm - 1mW
REMOVABLE CONNECTOR
High Power Connector

(Removable for Cleaning) infn_042
Step 3 Clean the pigtail connector using a Cletop cleaning cartridge with Blue tape as follows:
Step 3a Press the end of the connector to the Blue tape at the top of one slot and gently wipe
by pulling to the bottom of the slot.
Step 3b Rotate connector 90 degrees and clean again using the other slot.
Step 3c Do not scrub or clean the connector on the same surface of the tape more than once.
This can potentially contaminate or damage the connector.
Step 3d Remove a White Cletop swab from its packaging without touching the swab part.
Clean the shuttered bulkhead adapter by inserting the swab into the barrel and gently
rotating the swab. Use a new swab each time an adapter is cleaned.
Step 4 Engage the SC pigtail into the open end of the shuttered bulkhead adapter.
Step 5 Inspect with video fiberscope as described in Step 1. If it passes the inspection criteria, proceed
to Step 10. Otherwise, continue with Step 6.
Step 6 Disengage the pigtail connector from the shuttered bulkhead adapter.
Step 7 Clean the pigtail connector using a fiber cleaning wipe containing isopropyl alcohol. Rub the con-
nector against the wipe using a figure S motion (approximately 8 to 10 times). Then clean the
pigtail connector using the Cletop as described in Step 3.
Note: Do not use Kimwipes or other general purpose wipes. Use only wipes designed specifically
for fiber optic cleaning.
Step 8 Engage the SC pigtail into the open end of the shuttered bulkhead adapter.
Step 9 Inspect with video fiberscope as described in Step 1. If it passes the inspection criteria, continue
with Step 10. Otherwise, repeat Step 7 through Step 9. If the pigtail connector is still not clean,
replace the module.

Step 10 Carefully slide the SC pigtail back into the module, pushing the fiber in parallel to the angle of the
adapter. Continue until the connector bracket is in position against the module front panel. Do
not force the pigtail in. If resistance is met, the fiber is not being pushed at the correct angle;
remove the pigtail and reinstall. Proper installation will ensure that the pigtail does not form a
tight bend or kink.
Step 11 Tighten the two ¼-turn fasteners. Verify that both fasteners are engaged and the connector
bracket is properly secured against the module.
Step 12 Proceed to “To clean the non-removable connector” on page D-12.

Cleaning the Non-removable Connector

CAUTION
and Class 1M.
CAUTION
To clean the non-removable connector
Step 1 Install the SC bulkhead adapter tip onto the fiberscope. Remove dust cap from non-removable
adapter and insert the fiberscope tip. On the hand-held display, examine the cleanliness of the
non-removable connector end face compared to the criteria listed in “Optical Connector Inspec-
tion Standards” on page D-2. If it passes the inspection criteria, proceed to “To clean the client
fiber connector(s)” on page D-13; otherwise, continue with Step 2.
Step 2 If available, clean the non-removable connector(s) using a Westover CleanBlast system or
equivalent. Otherwise, remove a White Cletop swab from its packaging without touching the
swab part.
Step 2a Insert the swab into the barrel of the adapter until it touches the endface of the con-
nector.
Step 2b Gently rotate the swab and remove it.
Step 2c Use a new swab for each connector.
Step 3 Inspect with video fiberscope as described in Step 1. If it passes the inspection criteria, proceed
to “To clean the client fiber connector(s)” on page D-13; otherwise, repeat Step 2 and re-inspect.
If the connector is still not clean, replace the module.
Step 4 Proceed to “To clean the client fiber connector(s)” on page D-13.

Cleaning the Client Fiber Connector

CAUTION
and Class 1M.
CAUTION
To clean the client fiber connector(s)
Step 1 Install the 2.5mm patchcord tip onto the fiberscope and insert the client fiber connector. On the
hand-held display, examine the cleanliness of the client fiber connector end face compared to
the criteria listed in “Optical Connector Inspection Standards” on page D-2. If it passes the
inspection criteria, mate the client fiber to the module and proceed to “To install the RAM/ORM/
IRM” on page D-14; otherwise, continue with Step 2.
Step 2 Clean the client fiber connector with a Cletop cleaning cartridge with Blue tape as follows:
Step 2a Press the end of the connector to the Blue tape at the top of one slot and gently wipe
by pulling to the bottom of the slot.
Step 2b Rotate connector 90 degrees and clean again using the other slot.
Step 2c Do not scrub or clean the connector on the same surface of the tape more than
once. This can potentially contaminate or damage the connector.
Step 2d Remove a White Cletop swab from its packaging without touching the swab part.
Clean the shuttered bulkhead adapter by inserting the swab into the barrel and gen-
tly rotating the swab. Use a new swab each time an adapter is cleaned.
Step 3 Inspect with video fiberscope as described in Step 1. If it passes the inspection criteria, mate the
client fiber to the module and proceed to Step 6; otherwise continue with Step 4.
Step 4 Clean the client fiber connector using a fiber cleaning wipe containing isopropyl alcohol. Rub the
connector against the wipe using a figure S motion (approximately 8 to 10 times). Then clean the
client fiber connector using the Cletop as described in Step 2.
Step 5 Inspect with video fiberscope as described in Step 1. If it passes the inspection criteria, mate the
client fiber to the module and proceed to Step 6; otherwise, repeat Step 4. If the client fiber con-
nector is still not clean, replace it.
Step 6 Proceed to “To install the RAM/ORM/IRM” on page D-14.

Installing the RAM/ORM/IRM

CAUTION
and Class 1M.
CAUTION
CAUTION
The equipment is susceptible to damage if modules are improperly installed. Always
inspect the backplane for bent pins prior to inserting a module in a card slot. Inspect the
connector blocks on the rear of the module to ensure proper alignment prior to installing
into any slot. Ensure that the modules are aligned properly with the card cage rail guides
prior to insertion; insert modules slowly and do not use force.
Note: This procedure assumes that the RAM/ORM/IRM has been placed Out-of-service with the
Admin State set to Lock.
To install the RAM/ORM/IRM
Step 1 For RAM/ORMs only: insert the RAM/ORM partially into the OTC.
Step 1a Reposition the ejectors on the RAM/ORM to the full open position (perpendicular).
Step 1b Holding the RAM/ORM in one hand and while guiding it with your other hand, align it
side. In this orientation, the front panel of the RAM/ORM is right reading.
Step 1c Slide the RAM/ORM in partially; ensure that the RAM/ORM is not fully seated against
the backplane (the RAM/ORM must remain powered off).
Step 2 For IRMs only: insert the IRM partially into the MTC-9.
Step 2a Using your thumb and forefinger, squeeze the ejector handles on the IRM to unlatch
and open the ejector handles. Position the ejectors to the full open position (approxi-
mately 45 degrees).

Step 2b Align the IRM to the rail guides in slots 1 through 8 on the MTC-9 (the IRM is a triple-
width module requiring three adjacent slots).
Step 2c Slide the IRM in partially; ensure that the IRM is not fully seated against the back-
plane (the IRM must remain powered off).
Step 3 Reconnect the fibers.
Step 4 Gently push the RAM/ORM/IRM toward the backplane until it stops; RAM/ORM/IRM will now
power on.
Step 5 Close the left side and right side ejectors simultaneously.
Step 6 For RAM/ORMs only: lock the ejectors by turning the ejector screw 1/4 turn using a #1 Phillips
screwdriver.
Step 7 For IRMs only: tighten the captive screw using a #2 Phillips screwdriver.


Appendix E
Acronyms
List of Acronyms
Acronym Definition
A
AAM ATN Amplifier Module
AC air conditioner; alternating current
ACLI administrative command line interface
ACO alarm cutoff
ACT active
AD add/drop
ADLM Amplified Digital Line Module
ADM add/drop multiplexer
AGC Automated Gain Control
AID access identifier
AINS automatic in-service
AIS alarm indication signal
ALS Automatic Laser Shutdown
AMM ATN Management Module
AMP amplifier
ANSI American National Standards Institute
AOFM Advanced OTN FlexChannel Line Module

Page E-2 Acronyms
Acronym Definition
AOFX Advanced OTN FlexChannel Switching Line Module

AOLM Advanced OTN Line Module
AOLX Advanced OTN Switching Line Module
APC angled physical contact
APD avalanche photo diode
API application programming interface
APS automatic protection switching
ARC Alarm Reporting Control
ARP address resolution protocol
ASAP Alarm Severity Assignment Profile Settings (for ATN; other Infinera network ele-
ments use ASPS)
ASCII American Standard Code for Information Interchange
ASE amplified spontaneous emission
ASIC application-specific integrated circuit
ASPS Alarm Severity Profile Settings
ATC-A ATN Transport Chassis - Active
ATC-P ATN Transport Chassis - Passive
ATIS Alliance for Telecommunications Industry Solutions
ATM asynchronous transfer mode
AU administrative unit
AUX auxiliary port
AVC attribute value change
AWG array waveguide grating; American wire gauge
AXLM Amplified Switching Line Module
B
BDFB battery distribution fuse bay
BDI backward defect indication
BEI backward error indication
BER bit error rate; bit error ratio
BERT bit error rate testing
BIF bend insensitive fiber
BIP-8 bit interleaved parity
BITS building-integrated timing supply
BLSR bi-directional line switched ring
BMM Band Multiplexing Module

Acronyms Page E-3
Acronym Definition
BNC bayonet Neill-Concelman; British Naval Connector

BOL beginning of life
BOM bill of material
BOOTP bootstrap protocol
BPF Band Pass Filter
BPOST Boot Power On Self Test
bps bits per second
BPV bipolar violations
C
C Celsius
CBN Common Bonding Network
CBS committed burst size
CCITT Consultative Committee on International Telegraph and Telephone
(now known as the ITU-T)
CCLI commissioning command line interface
CDC colorless, directionless, and contentionless
CDE chromatic dispersion equalizer
CDR clock and data recovery
CDRH Center for Devices and Radiological Health
cDTF Clear Channel Digital Transport Frame
CET Channel Engineering Tool
CFP 100G* form factor pluggable *(C = 100 in Roman numerals; Centum)
CFR code for federal regulations
CH/Ch/ch channel
CID circuit identifier
CIR committed information rate
CIT craft interface terminal
CLEI common language equipment identifier
CLI command line interface
CLM C-band and L-band Coupler
CMM Channel Multiplexing Module
CNM Customer Network Manager
CO central office
CODEC coder and decoder
COM communication

Page E-4 Acronyms
Acronym Definition
CORBA Common Object Request Broker Architecture

CoS class of service
CPC common processor complex
CPE customer premises equipment
CPLD complex programmable logic device
CPU central processing unit
CRC cyclic redundancy check
CRM customer relationship management
CS contiguous spectrum
CSM Customer Service Module
CSPF constraint-based shortest path first algorithm
CSV comma separated value
CTAG correlation tag, customer tag
CTP connection termination point, channel trail termination point, client termination point
CTS clear to send
CV coding violation
CV-L coding violation-line
CV-P coding violation-path
CV-S coding violation-section
CWDM coarse wavelength division multiplexing
D
DA digital amplifier
DB database
dB decibel
DC direct current; dual carrier
DCC data communications channel
DCE data communications equipment
DCF dispersion compensation fiber
DCM Dispersion Compensation Module
DCN data communication network
DDR double data rate
DEMUX de-multiplexing
DFB distributed feedback
DFE decision feedback equalizer
DGE dynamic gain equalization; dynamic gain equalizer

Acronyms Page E-5
Acronym Definition
DHCP dynamic host configuration protocol

DHDW dual height dual width
DICM DTN Interconnect Module
DLM Digital Line Module
DLV Digital Link Viewer
DMC Dispersion Management Chassis
DNA Digital Network Administrator
DPSK differential phase shift keying
DQPSK differential quadrature phase shift keying
DR digital repeater
DSE Dynamic Spectrum Equalizer
DSF dispersion shifted fiber
DSNCP Digital Subnetwork Connection Protection
DSP digital signal processor
DT digital terminal
DTC Digital Transport Chassis
DTC-B Digital Transport Chassis-B
DTE data terminal equipment
DTF Digital Transport Frame
DTL digital transport line; designated transit list
DTP digital transport path
DTS digital transport section
DV digital video
DVB digital video broadcasting
DWDM dense wavelength division multiplexing
E
EBS excess burst size
ECC error-correcting code; error correction code
EDFA erbium doped fiber amplifier
EEPROM electrically-erasable programmable read-only memory
EFEC enhanced forward error correction
EIR excess information rate
EMC electromagnetic compatibility
EMI electromagnetic interference
EML element management layer

Page E-6 Acronyms
Acronym Definition
EMS element management system

EOA end of availability
EOL end of life
EOS end of support
EPL Ethernet private line
ES-L line-errored seconds
ES-P path-errored seconds
ES-S section-errored seconds
ESCON Enterprise Systems Connection
ESD electrostatic discharge; electrostatic-sensitive device
ESL effective span loss
ESP Encapsulating Security Payload
ETS IEEE European Test Symposium
ETSI European Telecommunications Standards Institute
EVC Ethernet virtual connection
F
F Fahrenheit
FA frame alignment; failure analysis
FAS frame alignment signal
FBG fiber Bragg grating
FC Fibre Channel; fiber channel; failure count
FCAPS fault management, configuration management, accounting, performance monitor-
ing, and security administration
FCC Federal Communications Commission (USA)
FDA Food and Drug Administration
FDI forward defect indication
FDR field data recorder
FEC forward error correction
FICON Fibre Connection
FIFO first-in-first-out
FIS Fault Integration Server
FIT failures in time
FLT fault
FMP Fiber Multiplexing Panel
FOADM fixed optical add drop multiplexer

Acronyms Page E-7
Acronym Definition
FPC Fiber Panel Chassis

FPGA field programmable gate array
FRM FlexROADM Module
FRU field replaceable unit
FSE FlexROADM Switching Expansion Module
FSM FlexROADM Switching Module
FSP Fiber Shuffle Panel
FTP file transfer protocol; floating termination point
FW firmware
G
GAM Gain Adapter Module
GbE gigabit Ethernet
Gbps gigabits per second
GCC general communication channel
GFEC general forward error correction
GFP generic framing protocol
GHz gigahertz
GMPLS generalized multi protocol label switching
GNE gateway network element
GNM Graphical Node Manager
GRE generic routing encapsulation
GTP group termination point
GUI graphical user interface
H/I
HD high definition
HD-FEC Hard Decision Forward Error Correction
HDLC high-level data link control
HTML hypertext markup language
HTTP hypertext transfer protocol
HW hardware
I/O input/output
I2C inter-integrated circuit
IAM ILS Amplifier Module
IAP input, output, and alarm panel

Page E-8 Acronyms
Acronym Definition
ICG invalid code group

ID identification
IDF invalid data flag
IEC International Electrical Commission
IFF Intermittent Fault Flag
IGCC Infinera General Communication Channel
ILS Infinera Line System
IMM Infinera Management Module
IMS Infinera Management Suite
IOP input/output panel
IP Internet protocol
IQ see IQ NOS
IQ NOS Infinera IQ Network Operating System
IQA NOS ATN Infinera IQA Network Operating System ATN
IR intermediate reach
IRM ILS Raman Amplifier Module
IS in-service
ITE information technology equipment
ITU-T International Telecommunications Union - Telecommunications
J/K/L
JDK Java Development Kit
JRE Java Runtime Environment
JS jabber seconds
LAN local area network
LBC laser bias current
LC fiber optic cable connector type
LCK locked
LED light-emitting diode
LME Line Monitoring Equipment
LMM Line Multiplexing Module
LOC loss of communication
LOF loss of frame
LOL loss of light
LOP loss of pointer
LOS loss of signal; loss of sync

Acronyms Page E-9
Acronym Definition
LOSYNC loss of sync

LP launch power
LR long reach
LSA link state advertisement
LSB least significant bit
LTE line-terminating equipment
M
MA monitoring access
MAC media access control
MAP management application proxy
MB megabyte
Mbps megabits per second
MCM Management Control Module
MEMS micro electro mechanical systems
MFAS multi frame alignment signal
MIB management information base
MMF multimode fiber
MPO multiple-fibre push-on/pull-off
MS multiplex section
MSA multi source agreement
MSB most significant bit
MSO multi-service operator
MSOH multiplex section overhead
MTBF mean time between failure
MTC-9 Modular Transport Chassis, 9 slot
MTU maximum transmission unit
MUX multiplex; multiplexer; multiplexing
N
NA network administrator
NAND flash type
NC normally closed; node controller; nodal control
NCT nodal control and timing
NDSF non zero dispersion shifted fiber
NE network engineer

Page E-10 Acronyms
Acronym Definition
NEBS network equipment building standards

NEC National Electrical Code
NECG net electrical coding gain
NEL network element layer
NEPA National Environmental Policy Act
NFPA National Fire Protection Association
nm nanometer
NML network management layer
NMS network management system
NNI network-to-network interface
NO normally open
NOC network operations center
NPS Network Planning System
NRZ non-return to zero
NSA non-service affecting
NTP network time protocol
NVRAM nonvolatile random access memory
O
O-SNC optical subnetwork connection
O-TE link optical traffic engineering link
OA Optical Amplifier
OAM Optical Amplification Module
OAM&P operation, administration, maintenance and provisioning
OC-3 optical carrier signal at 155.52Mbps
OC-12 optical carrier signal at 622.08Mbps
OC-48 optical carrier signal at 2.48832Gbps
OC-n optical carrier signal of level n (for example, OC-3, OC-48, etc.)
OCG optical carrier group
Och optical channel
OCI open connection indication
ODF optical distribution frame
ODU optical data unit
ODU0 optical data unit at the rate of 1.24Gbps.

Acronyms Page E-11
Acronym Definition

ODU1e optical data unit at the rate of 10.36Gbps.
ODU2e optical data unit at the rate of 10.4Gbps.
ODU3e1 optical data unit at the rate of 41.77Gbps.
ODU3e2 optical data unit at the rate of 41.79Gbps.
ODUk optical data unit of level k (for example, ODU1, ODU3e2, etc.)
ODUki The enhanced Infinera optical data unit of level k (for example, ODU3i, ODU4i, etc.
OE Optical Engine
OEL optically engineered lightpath
OEO optical-electrical-optical
OER optically engineered route; Optical Express Route
OFC open fiber control
OFM Optical Filter Module
OH overhead
OIF Optical Internetworking Forum
OLOS optical loss of signal
OMA optical modulation amplitude
OMM Optical Management Module
OMS optical multiplex section
OOK on-off keying
OOS out-of-service
OOS-MT out-of-service maintenance
OPM optical power monitor
OPN Optical Private Network
OPR optical power received
OPSW Optical Protection Switch
OPT optical power transmitted
OPU optical payload unit
ORL optical return loss
ORM Optical Raman Module
OS operating system
OSA optical spectrum analyzer
OSC Optical Supervisory Channel

Page E-12 Acronyms
Acronym Definition
OSMINE Operations Systems Modifications for the Integration of Network Elements

OSNR optical signal-to-noise ratio
OSPF open shortest path first
OSS operations support system
OTC Optical Transport Chassis
OTDR optical time domain reflectometer
OTM OTN Tributary Module
OTN Optical Transport Network
OTS optical transport section
OTU optical transport unit
OTU1 optical transport unit at the rate of 2.67Gbps.
OTU1e optical transport unit at the rate of 11.05Gbps.
OTU2 optical transport unit at the rate of 10.71Gbps.
OTU2e optical transport unit at the rate of 11.1Gbps.
OTU3 optical transport unit at the rate of 43.02Gbps
OTU3e1 optical transport unit at the rate of 44.57Gbps
OTU3e2 optical transport unit at the rate of 44.58Gbps
OTU4 optical transport unit at the rate of 111.81Gbps
OTUk optical transport unit of level k (for example, OTU1, OTU3e2, etc.)
OTUki The enhanced Infinera optical transport unit of level k (for example, OTU3i+,
OTU4i, etc.)
OW orderwire
OWM Orderwire Module
OXM OTN Switch Module
P/Q
PC personal computer
PCM Power Conversion Module
PCPM per channel power monitoring
PCS physical coding sublayer
PD photo diode
PDU protocol data unit; power distribution unit
PEM Power Entry Module
PG protection group
PHY physical
PIC Photonic Integrated Circuit

Acronyms Page E-13
Acronym Definition
PID protocol identifier

PIN positive-intrinsic negative
PJO positive justification opportunity
PL point loss
PLC Planar Lightwave Circuit
PLD programmable logic device
PLL phase locked loop
PLO point loss offset
PM performance monitoring; phase modulation; polarization multiplexed; preventive
maintenance
PM-BPSK polarization multiplexed-bi phase shift keying
PM-DQPSK polarization multiplexed-differential quadrature phase shift keying
PM-QPSK polarization multiplexed-quadrature phase shift keying
PMD polarization mode dispersion
PNTP provisioned neighbor termination point
POH path overhead
PON product ordering name
POP point-of-presence
POST Power On Self Test
PPM part per million
PPP point-to-point protocol
PR provisioning
PRBS pseudo random binary sequence
PROV provisioning
PRTP provisioned remote termination point
ps pico second (unit of measure for dispersion)
PSBT phase shaped binary transmission
PSC protection switch completion; protection switch count
PSD protection switch duration; power spectral density
PSE Passive Spectrum Equalizer
PSTN public switched telephone network
PTP physical termination point; point-to-point
PU protection unit
PWR power
QOS quality of service

Page E-14 Acronyms
Acronym Definition
R
RADIUS Remote Authentication Dial-In User Service
RAM Raman Amplifier Module; random access memory
RBM Red/Blue Band Mux/Demux
RDI remote defect indication
REI-L remote error indication-line
REI-P remote error indication-path
REM Raman Extender Module
RFI remote failure indication
RLL Receive Light Level
RMA return material authorization
ROADM reconfigurable optical add/drop multiplexer
ROM read-only memory
RS regenerator section; Reed-Solomon
RSOH regenerator section overhead
RSTP rapid spanning tree protocol
RTC real time clock
RTN return lead
RTS ready to send
RU rack unit
Rx receiver; receive
Rx Q receiver quality
RZ return to zero
RZ-DQPSK return to zero-differential quadrature phase shift keying
S
SA service affecting; security administrator; security association
SAPI source access point identifier
SC shelf controller; single carrier; square shaped fiber optic cable connector; super
channel
SCh super channel
SCG super channel group
SCM Submarine Control Module
SD signal degrade; standard definition
SD-FEC Soft Decision Forward Error Correction

Acronyms Page E-15
Acronym Definition
SDH synchronous digital hierarchy

SDI serial digital interface
SDRAM synchronized dynamic random access memory
SEF severely errored frame
SEFS severely errored frame second
SELV safety extra low voltage
SERDES serializer and deserializer
SES severely errored seconds
SF signal fail
SFP small form factor pluggable
SFTP secure file transfer protocol
SID source identifier; system identifier
SIM Service Interface Module
SL span loss
SLL Send Light Level
SLM Submarine Line Module
SLTE submarine line terminal equipment
SMF single-mode fiber
SML service management layer
SMPTE Society of Motion Picture and Television Engineers
SNC subnetwork connection
SNCP subnetwork connection protection
SNE subtending network element
SNMP simple network management protocol
SNR signal-to-noise ratio
SOH section overhead
SOL start of life
SOLM Submarine OTN Line Module
SOLX Submarine OTN Switching Line Module
SONET synchronous optical network
SPE synchronous payload envelope
SQ signal quality
SR short reach
SS split spectrum
SSHv2 Secure Shell version 2
SSL secure sockets layer

Page E-16 Acronyms
Acronym Definition
STAG service tag

STE section terminating equipment
STM synchronous transport module; synchronous transport mode
STM-1 synchronous transport module level 1 (SDH signal at 155.52Mbps)
STM-4 synchronous transport module level 4 (SDH signal at 622.08Mbps)
STM-16 synchronous transport module level 16 (SDH signal at 2.48832Gbps)
STM-n synchronous transport module of level n (for example, STM-64, STM-16)
STP spanning tree protocol
STS synchronous transport signal
STS-n synchronous transport signal of level n (for example, STS-12, STS-48)
SW software
T/U/V
TAC technical assistance center
TAM Tributary Adapter Module
TAP Timing and Alarm Panel
TCA threshold crossing alert
TCC threshold crossing condition
TCM tandem connection monitoring
TCP transmission control protocol
TE traffic engineering
TEC thermo-electric cooler
TEM TAM Extender Module
TERM terminal
TFTP trivial file transfer protocol
TID target identifier
TIM Tributary Interface Module; trace identifier mismatch
TL1 Transaction Language 1
TLA terminal line amplifier
TLS tunable laser source
TMF TeleManagement Forum
TMN telecommunications management network
TOM Tributary Optical Module
TP termination point

Acronyms Page E-17
Acronym Definition
TR transceiver
TSM Timing Synchronization Module
TSV tab separated value
TT test and turn-up
TTI trail trace identifier
TWC true-wave-classic
Tx transmitter; transmit
UA unavailable seconds
UART universal asynchronous receiver transmitter
UAS unavailable seconds
UAS-L unavailable seconds, near-end line
UAS-P unavailable seconds, near-end path
UDP user datagram protocol
ULH ultra long haul
UNI user-network interface
UPC ultra physical contact
UPSR unidirectional path switched ring
URL universal resource locator
USB Universal Serial Bus
UTC Coordinated Universal Time
V volt
VCAT virtual concatenation
VCCI Voluntary Control Council for Interference by Information Technology Equipment
VCG virtual concatenation group
VGA variable gain amplifier
VLAN virtual local area network
VOA variable optical attenuator
VPN virtual private network
VSR very short reach
W/X/Y/Z
WAN wide area network
WDM wavelength division multiplexing
WPCS Wet Plant Control and Surveillance System
WPLM Wet Plant Link Manager
WSS wavelength selective switch

Page E-18 Acronyms
Acronym Definition
WTR wait to restore, wait to revert

XC cross-connect
XCM DTN-X Control Module
XFP 10Gbps small form factor pluggable
XICM DTN-X Interconnect Module
XLM Switching Line Module
XML extensible markup language
XTC Switching Transport Chassis
MISC
1R re-amplification
2R re-amplification, re-shape
3R re-amplification, re-shape, re-time
4R re-amplification, re-shape, re-time, re-code
μEDFA micro-erbium doped fiber amplifier

Infinera

Uploaded by

Copyright:

Available Formats

Infinera

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

Infinera

Uploaded by

Copyright:

Available Formats

Infinera DTN and DTN-X

Turn-up and Test Guide

Infinera DTN-X, DTN, and ATN Regulatory Compliance

About this Document

Chapter 1 - Observing Safety Procedures

Chapter 2 - Preparing for Turn-up and Test

Infinera Proprietary and Confidential

Required Tools and Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Chapter 3 - Turning up a DTN-X as a GNE

Infinera Proprietary and Confidential

Testing Line Module/OTM-500/OTM2-500s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66

Chapter 4 - Turning up a DTN-X as an SNE

Infinera Proprietary and Confidential

Testing Line Module/OTM-500/OTM2-500s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63

Chapter 5 - Turning up an XTC as an Expansion Chassis

Infinera Proprietary and Confidential

Testing OXMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73

Chapter 6 - Turning up a DTN-X ROADM Multi-chassis Network Element

Infinera Proprietary and Confidential

Chapter 7 - Turning up a FlexILS as a GNE

Infinera Proprietary and Confidential

Testing IAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40

Chapter 8 - Turning up a FlexILS as an SNE

Infinera Proprietary and Confidential

Verifying Alarm Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42

Chapter 9 - Turning up an MTC-9 as an Expansion Chassis

Chapter 10 - Turning up a FlexILS ROADM Multi-chassis Network Element

Infinera Proprietary and Confidential

Chapter 11 - Turning up a DTN as a GNE

Infinera Proprietary and Confidential

Powering up the DTC/MTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17

Infinera Proprietary and Confidential

Configuring Alarm Input Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-109

Chapter 12 - Turning up a DTN as an SNE

Infinera Proprietary and Confidential

Testing DTC/MTC Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-98

Chapter 13 - Turning up a DTC/MTC as an Expansion Chassis

Infinera Proprietary and Confidential

Verifying Optical Channel (OCH) Loss Threshold for CMMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-75

Chapter 14 - Turning up a Network Element for Optical Express

Chapter 15 - Turning up an Optical Amplifier as an SNE

Infinera Proprietary and Confidential

Initial Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12

Chapter 16 - Turning up an OTC as an Expansion Chassis

Infinera Proprietary and Confidential

Configuring an OTC with BMM2C and Preamplifier Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-31

Infinera Proprietary and Confidential

Setting the Point Loss Offset for ORM Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-77

Appendix A - Optional Configuration

Appendix B - XCM/IMM/MCM/OMM Rebranding Flow

Infinera Proprietary and Confidential

Appendix D - Raman Fiber Connector Cleaning

Infinera Proprietary and Confidential

Infinera Proprietary and Confidential

Figure 1-1 XTC Power Entry Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9

Infinera Proprietary and Confidential

Figure 3-22 OLM OCG Port Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45

Infinera Proprietary and Confidential

Figure 4-27 Create IGCC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49