hiT 7300

5.60 70

OLR Commissioning

HDM-73R56070-11-0C
Revision C
January 2022

Please refer to the Infinera Customer Web Portal for the most recent version of this document.

Infinera continually strives to reduce the adverse environmental effects of its products and services. We invite you to join us in working towards a
cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products.

Infinera Corporation. Visit us at www.infinera.com.

OLR Commissioning

Copyright
© Copyright 2022 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, consequen-
tial 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®, FastSMP™, FlexCoherent®, iWDM®, What the Network Will Be®, and logos that contain Infinera are trademarks or registered trade-
marks of Infinera Corporation or its subsidiaries, in the United States and other countries.
All other trademarks in this manual are the property of their respective owners.

Infinera Regulatory Compliance for Class A Digital Devices

Federal Communications Commission (FCC) Statement
Note: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These
limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual,
may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference
in which case the user will be required to correct the interference at his own expense.

Industry Canada Statement

This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.

Japan Voluntary Control Council for Interference (VCCI) Statement

Translation:
This is a Class A equipment. Operation of this equipment in a residential environment could cause radio interference. In such a case, the user may
be required to take corrective actions. VCCI-A

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.

U.S. Food and Drug Administration (FDA) Regulations for Laser Products
This product complies with the United States Code of Federal Regulations, CFR Title 21, Ch. 1, Sections 1040.10, and 1040.11, except for devi-
ations pursuant to the “Laser Notice No. 50" guidance document, issued on June 24, 2007.

Product Safety
Important Notice on Product Safety
This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install,
operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety
information is provided in the “Safety Instructions”, part of this document or documentation set.
The same text in German:

Wichtiger Hinweis zur Produktsicherheit

Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen. Installation, Betrieb,
Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sich-
erheitsanforderungen erfolgen. Die Sicherheitsanforderungen finden Sie unter “Sicherheitshinweise” dieses Dokuments oder dieses Dokumenta-
tionssatzes.

HDM-73R56070-11-0C Page 2 © Infinera 2022

OLR Commissioning

Table of Contents
This document has 76 pages.

Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Commissioning rules and preconditions . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1 General rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Hardware and software prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Commissioning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1 Pre-commissioning tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2 NE configuration part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3 Network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.4 NE configuration part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.5 Final commissioning tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.6 Post-commissioning tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4 Pre-commissioning tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.1 Defining the OLR commissioning strategy . . . . . . . . . . . . . . . . . . . . . . . 18
4.2 Checking the prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.3 Checking if the NE is set to factory default . . . . . . . . . . . . . . . . . . . . . . . 19

5 OLR commissioning procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5.1 Connecting to the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.1.1 Installing the root certificate from the NE . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1.1.1 Downloading the NE’s root certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1.1.2 Importing the NE’s root certificate to the Trusted Root Certification Authorities
storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.1.1.3 Importing the NE’s root certificate to the Trusted Publishers storage. . . 23
5.1.1.4 Importing the NE’s root certificate to the Java Trusted Publishers storage23
5.1.2 Connecting on-site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.1.3 Connecting remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2 Configuring the NE with the Customer Code . . . . . . . . . . . . . . . . . . . . . 27
5.3 Configuring the NE name and location . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.4 Configuring NE parameters with a Network Configuration File. . . . . . . . 28
5.4.1 Downloading and swapping an NCF. . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.5 Configuring shelf parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.5.1 Configuring shelf location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.5.2 Configuring shelf display mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.5.3 Clearing the fan filter alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.5.4 Disabling ILAN connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.6 Configuring NE EOW telephone number . . . . . . . . . . . . . . . . . . . . . . . . 32
5.7 Configuring RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.7.1 Configuring RADIUS DHCP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.7.2 Configuring RADIUS proxy list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

HDM-73R56070-11-0C Page 3 © Infinera 2022

OLR Commissioning

5.7.3 Configuring RADIUS server settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.8 Configuring the Network Time Protocol and NE time . . . . . . . . . . . . . . . 37
5.8.1 Configuring an external NTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.8.2 Configuring NE time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.8.3 Configuring NTP keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.9 Configuring NE parameters manually . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.9.1 Checking NE type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.9.2 Setting the core provisioning via NMS mode . . . . . . . . . . . . . . . . . . . . . 40
5.9.3 Adding a DCM tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.9.4 Adding cards to shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.9.5 Setting THz decimal digits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.10 Configuring external interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.10.1 Configuring Ring Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.10.2 Configuring user channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.10.2.1 Configuring the User 1/User 2 interface . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.10.2.2 Configuring user channels via OSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.11 Configuring a CFSU-x card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.12 Configuring fan filter maintenance settings. . . . . . . . . . . . . . . . . . . . . . . 46
5.12.1 Configuring fan filter maintenance settings for single shelf NEs. . . . . . . 46
5.12.2 Configuring fan filter maintenance settings for multiple shelves NEs . . . 47
5.13 Configuring MCP4-x cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.14 Activating and deactivating the Mark card by slow flashing of LEDs function
49
5.15 Setting card user label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.16 Verifying NE DCN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.17 Changing the administrator’s password . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.18 Setting NE state to commissioned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

6 Post-commissioning tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.1 Uploading the MIB contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.2 Opening the Troubleshooting Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . 53

7 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

8 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

HDM-73R56070-11-0C Page 4 © Infinera 2022

OLR Commissioning Preface

1 Preface
This commissioning manual provides instructions for commissioning an Optical Line
Repeater (OLR), a network element (NE) of the Coriant hiT 7300 system (hereinafter
referred to as hiT 7300).

t Coriant and all its products, including hiT 7300 are now part of Infinera Corporation.
However, throughout this document several Coriant references are still included.

1.1 Intended audience

This document is intended for personnel who are tasked to commission a hiT 7300 OLR.
Personnel performing this task must be familiar with Coriant or equivalent optical transmis-
sion and telecommunication hardware. Personnel must also comply with all relevant safety
practices whenever working with hiT 7300 equipment.

1.2 Structure of this document

To fully commission a hiT 7300 system (that is, NE bring-up process), it is necessary to
complete the phases listed in Table 1.
It is mandatory that these phases are completed in the displayed order. If a phase is
skipped, or not performed, the NE bring-up process cannot be completed.

Commissioning phase Documents Performed

Installation Installation Manual (IMN) On-site
Interconnect, Configuration and
Mechanical Assembly (ICMA)
OLR commissioning OLR Commissioning manual (this On-site/remotely
document)
Optical Link Commissioning Optical Link Commissioning (OLC) On-site/remotely
manual

Table 1 Bring-up sequence

Commissioning an OLR is the process of taking an installed OLR and bringing it into an
operational state. The OLR commissioning phase is performed after the OLR is installed
and powered up.
The OLR Commissioning manual contains the following sections:

Section Title Subject

Section 1 Preface Provides an introduction and overview of this
document.
Section 2 Commissioning Provides a list of rules and preconditions for the hiT
rules and precondi- 7300 OLR commissioning.
tions
Section 3 Commissioning Provides an overview of the hiT 7300 OLR com-
overview missioning.

Table 2 Overview of document structure

HDM-73R56070-11-0C Page 5 © Infinera 2022

OLR Commissioning Preface

Section Title Subject

Section 4 Pre-commissioning Provides the necessary tasks to perform before the
tasks commissioning.
Section 5 OLR commissioning Provides the necessary procedures to complete
procedures the OLR commissioning.
Section 6 Post-commission- Provides the necessary tasks to perform after the
ing tasks commissioning.
Section 7 Resetting the NE to Provides the necessary procedures to reset the NE
default values to its default values.
Section 8 Glossary Provides a list of terms and corresponding defini-
tions used in this document.
Section 9 Abbreviations Provides a list of the abbreviations used in this doc-
ument.

Table 2 Overview of document structure (Cont.)

t Some features described in this document might not be available. In order to identify the
features released for the current product version, please refer to the Release Notes docu-
ment.

1.3 Symbols and conventions

The following symbols and mark-up conventions are used in this document:

Representation Meaning

f DANGER! A safety message indicates a dangerous situation where

personal injury is possible.
f WARNING! The keywords denote hazard levels with the following meaning:
f CAUTION! DANGER! - Indicates a hazardous situation which, if not
avoided, will result in death or serious (irreversible) personal
injury.
WARNING! - Indicates a hazardous situation which, if not
avoided, could result in death or serious (irreversible) personal
injury.
CAUTION! - Indicates a hazardous situation which, if not
avoided, may result in minor or moderate (reversible) personal
injury.

w NOTICE: A property damage message indicates a hazard that may result

in equipment damage, data loss, traffic interruption, and so on.

g A note provides important information related to the topic, for

example, not obvious exceptions to a rule or side effects.

t A tip provides additional information related to the topic which is

not essential in the context, but given for convenience.

Table 3 List of symbols and conventions

HDM-73R56070-11-0C Page 6 © Infinera 2022

OLR Commissioning Preface

Representation Meaning
Bold • All names of graphical user interface (GUI) objects, such as
windows, field names, buttons, and so on.
Example: Select the Full Screen check box and press OK.
• Terms and abbreviations which are linked to an entry in the
glossary and list of abbreviations respectively.
• Important key words.
Italic • Files, folders, and file system paths.
Example: /usr/etc/sbin/ftpd.exe
• Emphasized words.
typewriter • Input to be typed in a command line or a GUI field.
Examples:
ping -t 192.168.0.1
Enter World in the Domain field.
• Output from a command, error messages, content of a status
line, and so on.
• File content, such as program sources, scripts, logs, and set-
tings.
<angle brackets> Placeholders, for example as part of a file name or field value.
Examples:
<picture name>.png or <ip address>:<port number>
[square brackets] A key to be pressed on a PC keyboard, for example [F11].
Keys to be pressed simultaneously are concatenated with a “+”
sign, for example [CTRL]+[ALT]+[DEL].
Keys to be pressed one after another are concatenated with
spaces, for example [ESC] [SPACE] [M].
> The greater than symbol “>” is used to concatenate a series of
GUI items in order to depict a GUI path. This is an abridged pre-
sentation of a procedure to be carried out in order to perform an
action or display a window or dialog box.
Examples:
A simple menu path: File > Save as ...
A more complex GUI path:
> Main window > File menu > Change Password command >
Change Password dialog box
x For convenience, card names are sometimes listed with a lower
(in card names) case x variable, in order to concisely represent multiple cards.
Example:
I01T40G-x (is to be interpreted as I01T40G-1 and I01T40G-2)

Table 3 List of symbols and conventions (Cont.)

HDM-73R56070-11-0C Page 7 © Infinera 2022

OLR Commissioning Preface

Representation Meaning
(parentheses) For convenience, card variants are sometimes listed with a
section of their name between parentheses, in order to concisely
represent both card variants.
Example:
CCEP-3(/S) (is to be interpreted as CCEP-3 and CCEP-3/S)

Table 3 List of symbols and conventions (Cont.)

Screenshots of the graphical user interface are examples only to illustrate principles. This
especially applies to a software version number visible in a screenshot.

1.4 History of changes

Revision Revision date Remarks

A March 2020 Initial version
B September 2020 Maintenance version
C January 2022 Maintenance version

Table 4 History of changes

HDM-73R56070-11-0C Page 8 © Infinera 2022

OLR Commissioning Commissioning rules and preconditions

2 Commissioning rules and preconditions

This section contains general rules, notes and preconditions to be followed while commis-
sioning the OLR. Commissioning the OLR is the process of bringing the OLR system into
operational state after being installed and powered up.
All NEs in a link must be commissioned before beginning the optical link commissioning.
For optical link commissioning, refer to the Optical Link Commissioning (OLC) manual.

2.1 General rules

• Each OLR must be commissioned according with section 3 Commissioning overview
on page 11.
• The order in which the OLRs of a DCN are commissioned is irrelevant.
• In case of SFL600-3, OLR is supported as default NE type for first provisioning only.
The NE type must be manually changed to SON or ONN since functional OLR NE type
is not supported.
• The hiT 7300 system is available in different delivery formats which differ in:
• the preinstalled HW and SW;
• the commissioning strategy; and
• the necessary steps for commissioning.
Table 5 displays the available strategies and delivery formats to commission the hiT
7300 OLR system.

Strategy Delivery format

Factory pre-commissioned Rack and shelf pre-configuration: the entire
assembly work is assured by Coriant in
advance. In this case, all cards are plugged in
the shelves according to the customer List Of
Material (LOM), and installed in the correct
racks.
Commissioning on-site Shelf pre-configuration: all shelves are
equipped with cards according to the customer
LOM. In this case, the required software is
installed to the NE and the shelf ID (identifier) is
configured.
Bulk: the bulk delivery format does not provide
any pre-configured parameters for the NEs.

Table 5 Commissioning strategy and delivery formats

For more information concerning the delivery formats refer to the Installation Manual
(IMN).

2.2 Hardware and software prerequisites

The prerequisites vary depending on the delivery format of the NE. The commissioning of
each OLR in the hiT 7300 network requires a web-based craft terminal.

Prerequisites
All NEs are commissioned using @CT, the web-based craft terminal.

HDM-73R56070-11-0C Page 9 © Infinera 2022

OLR Commissioning Commissioning rules and preconditions

Table 6 lists the Hardware and Software requirements to run the hiT 7300 Element
Manager.

Hardware/Software Manufacturer Description

Notebook or PC - Processor 2.8GHz (or equivalent)
and 4 GB RAM
Ethernet cables - Crossover and straight cables
Operating system Microsoft MS Windows 7
MS Windows 10
Microsoft Internet Explorer
Internet browser
Edge
Java Installation1) Amazon Amazon Corretto 112) (Coriant’s rec-
ommended version)
Amazon Corretto 8
OpenJDK OpenJDK 112) (available at
https://jdk.java.net/java-se-ri/11)
Oracle J2SE Runtime Environment JRE 8
update 202
Planning application Coriant TransNet
Please refer to the Customer
Release Notes for information on the
appropriate release.
Management applica- Coriant @CT
tion

Table 6 General hardware and software requirements

1) Use one of the presented options for Java installation.
2) If using Java 11, JavaFX is required to run SOR Viewer tool. JavaFX is automat-
ically installed during EM installation.

t During Java installation on MS Windows 7 or MS Windows 10, install the JRE version (32-
bit or 64-bit) which is compatible to the OS in use.

HDM-73R56070-11-0C Page 10 © Infinera 2022

OLR Commissioning Commissioning overview

3 Commissioning overview
Each OLR in the hiT 7300 network has to be commissioned according with the sequence
of tasks described in Figure 1. Depending on the delivery format of the NE some of the
steps within this procedure are skipped.
Figure 1 shows the flowchart that contains the main blocks needed to complete the com-
missioning of an OLR. Each block contains the necessary tasks to complete each phase of
the commissioning procedure.

OLR Commissioning
Pre-commissioning tasks,
refer to section 3.1.

NE configuration part 1,
refer to section 3.2.

Network configuration,
refer to section 3.3.

NE configuration part 2,
refer to section 3.4.

Final commissioning tasks,

refer to section 3.5.

Post-commissioning tasks
refer to section 3.6.

The OLR
commissioning is
completed

Figure 1 OLR commissioning flowchart

3.1 Pre-commissioning tasks

The pre-commissioning tasks must be performed before beginning the commissioning of
the NE. In this block of tasks the commissioning strategy is defined and the pre-commis-
sioning checks are done.
Figure 2 shows the flowchart that contains the blocks needed to complete the pre-commis-
sioning of an OLR. Each block contains the necessary procedures to complete the pre-
commissioning phase.

HDM-73R56070-11-0C Page 11 © Infinera 2022

OLR Commissioning Commissioning overview

Pre-commissioning tasks
Defining the OLR commissioning
strategy, refer to section 4.1.

Factory Commissioning
pre-commissioned on-site
What is
the commissioning
strategy?

Checking the prerequisites, Checking the prerequisites,

refer to section 4.2. refer to section 4.2.

Checking if the NE is set to

factory default,
refer to section 4.3.

Pre-commissioning
tasks completed

Figure 2 Pre-commissioning tasks flowchart

To complete the OLR pre-commissioning tasks, perform the following steps:
1 Define the OLR commissioning strategy, as described in section 4.1 Defining the OLR
commissioning strategy on page 18.
2 Check if the prerequisites are fulfilled, as described in section 4.2 Checking the prereq-
uisites on page 18.
3 Depending on the commissioning strategy, select one of the following options:
a) In case of Factory pre-commissioned, the pre-commissioning is completed.
b) In case of Commissioning on-site, proceed to step 4.
4 Check if the NE is set to factory default, as described in section 4.3 Checking if the NE
is set to factory default on page 19.
The pre-commissioning tasks are completed.

3.2 NE configuration part 1

This section contains the first part of the NE commissioning tasks. In this block the initial
configurations are made. Depending on the commissioning strategy some options are
skipped.
Figure 3 shows the flowchart that contains the blocks needed to complete the first part of
the NE configuration. Each block contains the necessary procedures to complete the first
part of the NE configuration phase.

HDM-73R56070-11-0C Page 12 © Infinera 2022

OLR Commissioning Commissioning overview

Pre-commissioning
tasks completed

Connecting to the NE,

NE configuration
refer to section 5.1. part 1

Factory Commissioning
pre-commissioned on-site
What is the
commissioning
strategy?

No
Do you have a
Customer Code?

Yes

Configuring the NE with the

Customer Code,
refer to section 5.2.

Configuring the NE name and

location, refer to section 5.3.

No Yes
Do you
commission the NE parameters
via NCF?

Configuring the NE parameters

with an NCF, refer to section 5.4.

Configuring shelf parameters,

refer to section 5.5.

Configuring NE EOW telephone

number, refer to section 5.6.

NE configuration
part 1 completed

Figure 3 NE configuration part 1 flowchart

To complete the first part of NE’s configuration tasks, perform the following steps:
1 Connect on-site, as described in section 5.1 Connecting to the NE on page 20.
2 Depending on the commissioning strategy, select one of the following options:
a) In case of Factory pre-commissioned, skip to step 6.
b) In case of Commissioning on-site, proceed to step 3.
3 Depending on the existence of a Customer Code, select one of the following
options:
a) If the Customer Code is available, configure the NE with the Customer Code as

HDM-73R56070-11-0C Page 13 © Infinera 2022

OLR Commissioning Commissioning overview

described in section 5.2 Configuring the NE with the Customer Code on page 27
and proceed to step 4.
b) Otherwise, proceed to step 4.
4 Configure the NE name and location, as described in section 5.3 Configuring the NE
name and location on page 27.
5 Depending on the usage of an NCF to commission the NE, select one of the following
options:
a) In case of commissioning the NE via NCF, configure the NE type as described in
section 5.4 Configuring NE parameters with a Network Configuration File on page
28 and proceed to step 6.
b) Otherwise, skip to step 6.
6 Configure shelf parameters, as described in section 5.5 Configuring shelf parameters
on page 29.
7 Configure the NE EOW telephone number, as described in section 5.6 Configuring NE
EOW telephone number on page 32.
The first part of the NE configuration is completed.

3.3 Network configuration

This section contains the necessary tasks to configure network parameters.
Figure 4 shows the flowchart that contains the blocks needed to complete network config-
uration tasks. Each block contains the necessary procedures to complete the network con-
figuration phase.

NE configuration
part 1 completed

Network
Configuration
Do you use
RADIUS?
Yes

No

Configuring RADIUS,
refer to section 5.7.

Configuring NTP and NE time,

refer to section 5.8.

Network configuration
completed

Figure 4 Network configuration flowchart

Complete the network configuration tasks with the following steps:
1 In case of using RADIUS, configure as described in section 5.7 Configuring RADIUS on
page 32, in case RADIUS is not used, skip to step 2.
2 Configure the NTP and NE time, as described in section 5.8 Configuring the Network
Time Protocol and NE time on page 37.

HDM-73R56070-11-0C Page 14 © Infinera 2022

OLR Commissioning Commissioning overview

The network configuration tasks are completed.

3.4 NE configuration part 2

This section describes the second part of the NE’s parameters configuration. Depending on
the usage of an NCF some tasks are skipped.
Figure 5 shows the flowchart containing the procedures needed to complete the second
part of the NE’s parameters configuration.

Network configuration
completed

NE configuration
Do you No part 2
commission NE paremeters
via NCF

Yes

Configuring NE parameters
manually, refer to section 5.9.

NE configuration
part 2 completed

Figure 5 NE configuration part 2 flowchart

To complete the second part of the NE’s parameters configuration, perform the following
steps:
1 Depending on the usage of an NCF, select one of the following options:
a) In case of using an NCF, the NE configuration part 2 is completed.
b) Otherwise, proceed to step 2.
2 Configure NE’s parameters manually as described in section 5.9 Configuring NE
parameters manually on page 39.
The NE configuration part 2 tasks are completed.

3.5 Final commissioning tasks

The final commissioning tasks described in this section conclude the commissioning of the
NE. In this block the final configurations are completed and the NE is completely commis-
sioned.
Figure 6 shows the flowchart that contains the blocks needed to complete the service con-
figuration. This is the final commissioning block of tasks.

HDM-73R56070-11-0C Page 15 © Infinera 2022

OLR Commissioning Commissioning overview

NE configuration
part 2 completed

Final
commissioning
tasks
Configuring external interfaces,
refer to section 5.10.

Configuring a CFSU-x card,

refer to section 5.11.

Configuring fan filter maintenance

settings, refer to section 5.12.

Configuring MCP card settings,

refer to section 5.13.

Setting card user label,

refer to section 5.15.

Verifying NE DCN configuration,

refer to section 5.16.

Changing the administrator’s

password, refer to section 5.17.

Setting NE state to commissioned,

refer to section 5.18.

Final commissioning
tasks completed

Figure 6 Final commissioning tasks flowchart

To complete the final commissioning tasks, perform the following steps:
1 Configure the external interfaces, as described in section 5.10 Configuring external
interfaces on page 42.
2 Configure the CFSU-x card, as described in section 5.11 Configuring a CFSU-x card on
page 46.
3 Configure the fan filter maintenance settings, as described in section 5.12 Configuring
fan filter maintenance settings on page 46.
4 Configure the MCP card settings, as described in section 5.13 Configuring MCP4-x
cards on page 48.
5 Set the card user label, as described in section 5.15 Setting card user label on page 50.
6 Verify the NE DCN configuration, as described in section 5.16 Verifying NE DCN con-
figuration on page 50.
7 Change the administrator’s password, as described in section 5.17 Changing the
administrator’s password on page 50.

HDM-73R56070-11-0C Page 16 © Infinera 2022

OLR Commissioning Commissioning overview

8 Set the NE state to commissioned, as described in section 5.18 Setting NE state to

commissioned on page 51.
The final commissioning tasks are completed.

3.6 Post-commissioning tasks

The post-commissioning tasks described in this section are necessary steps to take
after the commissioning is successfully concluded. In this block the MIB is uploaded and
the Troubleshooting Manual (TSMN) is opened.
Figure 7 shows the flowchart that contains the blocks needed to complete the post-commis-
sioning tasks.

Final commissioning
tasks completed

Post-commissioning
tasks
Upload the MIB contents,
refer to section 6.1.

Opening the Troubleshooting

Manual, refer to section 6.2.

OLR commissioning
completed

Figure 7 Post-commissioning tasks flowchart

To complete the post-commissioning tasks, perform the following steps:
1 Upload the MIB contents as described in section 6.1 Uploading the MIB contents on
page 52.
2 Open the Troubleshooting Manual as described in section 6.2 Opening the Trouble-
shooting Manual on page 53.
The post-commissioning tasks are completed.

HDM-73R56070-11-0C Page 17 © Infinera 2022

OLR Commissioning Pre-commissioning tasks

4 Pre-commissioning tasks
This section contains all the necessary information to complete the OLR pre-commission-
ing.

4.1 Defining the OLR commissioning strategy

The commissioning strategy is defined depending on the type of the delivery format. Two
types of OLR commissioning strategy are distinguished:
• Factory pre-commissioned on page 18
• Commissioning on-site on page 18

Factory pre-commissioned
This type of strategy is used in case the delivered rack and shelf are pre-configured. The
entire assembly work is assured by Coriant in advance. In this case, all cards are plugged
in the shelves according to the commissioning reports and installed in the correct racks.
No further delivery items from Coriant are necessary except the Customer Code if delivered
to your company.

Commissioning on-site
This type of strategy is used in case of a bulk or a shelf pre-configuration delivery format.
In case of a shelf pre-configuration delivery format, all shelves are equipped with cards
according to the commissioning reports. In this case, the required software is installed to
the NE and the shelf ID (identifier) is configured.
Prior beginning with the OLR commissioning, ensure that the following items are available:
• Commissioning reports generated by TransNet.
• A DCN plan indicating the permanent gateway NEs and DHCP servers.
• A list with the DCN MAC addresses of all shelves that contain the NE controller cards
(CCEP/CCMP).
• The manufacturing numbers of the shelves that contain all shelf controller cards
(CCSP), and corresponding shelf ID according to commissioning reports.
• Optional: The customer code if a customer code is delivered.
• Optional: NCF (Network Configuration File) which must be available
• in the laptop if completing on-site commissioning with no File Transfer Protocol
(FTP) server access; or
• in the FTP server if completing remote commissioning with FTP server access.

4.2 Checking the prerequisites

Before starting the NE commissioning, to ensure that the prerequisites are fulfilled,
complete the following steps:
1 Check if the assembly and cabling are according with Installation Manual (IMN) and
Interconnect, Configuration and Mechanical Assembly (ICMA).
2 Check that no card fault LEDs are continuously lit.
3 Check if the NE is powered up and if the NE controller card has the OK LED lit.
For more information concerning the delivery formats refer to the Installation Manual (IMN).

g If the NE is factory pre-commissioned skip to section 5.1 Connecting to the NE on page

20.

HDM-73R56070-11-0C Page 18 © Infinera 2022

OLR Commissioning Pre-commissioning tasks

4.3 Checking if the NE is set to factory default

When commissioning on-site an NE with a CCEP or CCMP controller card already used
in another NE it is important that no previous configurations are set in the controller card. If
the CCEP or CCMP controller card was already used in another NE or in the uncertainty of
its use, a factory default must be performed before proceeding to the next task of the com-
missioning. A factory default is not needed if the CCEP or CCMP controller card is new.

g This procedure must not be used when commissioning a factory pre-commissioned NE.

Perform this procedure as described in section 7.2 Resetting the NE to factory default (Web
Service menu) on page 55.

HDM-73R56070-11-0C Page 19 © Infinera 2022

OLR Commissioning OLR commissioning procedures

5 OLR commissioning procedures

The commissioning procedures described in this section must be completed to bring the NE
into the Commissioned state. The commissioning status is displayed in the status bar of
the EM.
During the commissioning the NE may be in one of the following three states:
• Not commissioned: The NE is in the initial stage of the commissioning (the NCF is not
yet loaded to the system) or the NE is being configured manually (without NCF). This
is the NE’s initial state.
• Pre-commissioned: At least one valid NCF was downloaded and swapped. This state
is automatically set by the NE.
• Commissioned: The commissioning of the NE is complete. This state is set manually
by the user.

t In the EM window press the Update Active Window tool bar button (or press [F5] on the
keyboard) to refresh the EM data display. This ensures that the latest data is displayed by
the window.

t If an NE is forced into Recover Mode during the commissioning phase, please refer to the
Troubleshooting Manual (TSMN) how to clear Recover Mode.

5.1 Connecting to the NE

For the NE commissioning procedure a connection from the laptop must be established.
To establish a connection to the NE, select one of following:
a) Install the root certificate if a valid root certificate is not installed. Refer to
5.1.1 Installing the root certificate from the NE on page 21.
b) Connect to the NE on-site as described in section 5.1.2 Connecting on-site on page
23.
c) Connect remotely. Remote access to the NE is only possible when an ONN used as
permanent gateway is commissioned in the DCN, and the Optical Supervisory Channel
(OSC) connectivity is running. Refer to 5.1.3 Connecting remotely on page 26.

g The maximum number of opened EM sessions (that is, established connections to the NE
via EM) per NE is 20. However, optimum system performance can only be obtained with up
to a maximum of 10 sessions per NE. If an EM session crashes or loses connectivity:
• the session is still accountable and can only be removed by a user with administration
privileges or
• is automatically closed after one hour.

g Temporary files must be enabled on your computer.

To enable the temporary files on your computer please complete the following steps:
1 In the Control Panel > Java > Java Control Panel > General tab click on Settings...
button.
2 The Temporary Files Settings window is opened.
3 Select the Keep temporary files on my computer check box.
Click OK to confirm the settings.

t The SSL 3.0 in your computer must be disabled.

HDM-73R56070-11-0C Page 20 © Infinera 2022

OLR Commissioning OLR commissioning procedures

To disable the SSL 3.0 in your computer please complete the following steps:
1 Go to the Control Panel > Internet Options> Advanced tab.
2 In the advanced Settings list, scroll down to reach the Security settings.
3 Clear the Use SSL 3.0 check box.
4 Select the Use SSL 2.0, Use TLS 1.0, Use TLS 1.1 and Use TLS 1.2 check boxes.
Click Apply to confirm the settings.

5.1.1 Installing the root certificate from the NE

This procedure is only applicable when accessing the NE and a valid root certificate is not
installed. It is necessary to download a digital certificate presented by the NE and import it
to the browser when connecting to the NE.
All downloads can be performed using HTTP or HTTPS.
The HTTPS server authenticates itself using a Coriant proprietary server certificate. You
will be asked whether you accept the server certificate or not, because the browser is not
able to verify the server certificate.
The NE contains the root certificate used to sign the server certificate and makes it available
for download by HTTP(S). When installing the root certificate, you must verify the fingerprint
(or thumbprint) of the downloaded root certificate against the fingerprint given in this
manual.

g It is necessary to import the root certificate to the Trusted Root Certification Authorities
and Trusted Publishers storages on your PC.

To install the NE’s root certificate complete the following procedures in the displayed order:
1. 5.1.1.1 Downloading the NE’s root certificate on page 21
2. 5.1.1.2 Importing the NE’s root certificate to the Trusted Root Certification Authorities
storage on page 22
3. 5.1.1.3 Importing the NE’s root certificate to the Trusted Publishers storage on page 23
4. 5.1.1.4 Importing the NE’s root certificate to the Java Trusted Publishers storage on
page 23

5.1.1.1 Downloading the NE’s root certificate

To download the NE’s root certificate, complete the following steps:
1 Open a web browser on your PC and type one of the following URL:
• http://<NE’s IP address>;
• https://<NE’s IP address>;
• http://LocalQF.; or
• https://LocalQF..
Press [Enter].

g To establish a local Ethernet connection, the PC needs to be configured for either auto-
matic or manual IP addressing.
To establish a secure connection to an NE, use https instead of http.

2 Depending on the type of connection, select one of the following options:

HDM-73R56070-11-0C Page 21 © Infinera 2022

OLR Commissioning OLR commissioning procedures

a) In case of using a secure connection (https), the Coriant hiT 7300 5.60 @CT web
site window is opened and a certification security window is displayed against the
web site certificate.
Proceed to step 3.
b) Otherwise (http) the Coriant hiT 7300 5.60 @CT web site window is opened.
Proceed to step 6.
3 Check the security warning details by clicking More Information in the security warning
window.
The More information window opens.
4 Check the Root certificate fingerprint by clicking View Certificate Details.
The Details - Certificate window opens.
The correct Coriant root certificate fingerprint is:
95 CC CC 99 30 A9 4D F1 B3 FD 45 57 28 77 15 42 F8 13 DF A0.
5 Close Details - Certificate and More Information windows and click Continue to go
to the Coriant hiT 7300 5.60 @CT page.
6 Click Download the certificate.
The File Download - Security Warning dialog box opens.
7 Save the NE’s root certificate in your PC.
The NE’s root certificate is downloaded.

5.1.1.2 Importing the NE’s root certificate to the Trusted Root Certification
Authorities storage
To import the NE’s root certificate to the Trusted Root Certification Authorities storage,
proceed as follows:
1 Double-click on the NE’s root certificate file.
The Certificate window opens.
2 In the General tab, click Install Certificate... to install the certificate within your
browser.
The Certificate Import Wizard opens and a welcome message is displayed.
3 Click Next to continue, select Place all certificates in the following store radio button
and click Browse....
The Select Certificate Store window opens.
4 Select Trusted Root Certification Authorities folder and click Next.
5 Complete the wizard instructions by clicking Finish.
A Security Warning window opens displaying the root certificate fingerprint.
6 Verify the fingerprint and click Yes.
The correct Coriant root certificate fingerprint is:
95 CC CC 99 30 A9 4D F1 B3 FD 45 57 28 77 15 42 F8 13 DF A0.
The Certificate Import Wizard message opens displaying that the import was suc-
cessful.
7 Click Ok.
The certificate is imported to the Trusted Root Certification Authorities storage.

HDM-73R56070-11-0C Page 22 © Infinera 2022

OLR Commissioning OLR commissioning procedures

5.1.1.3 Importing the NE’s root certificate to the Trusted Publishers storage
To import the NE’s root certificate to the Trusted Publishers storage, proceed as follows:
1 Double-click on the NE’s root certificate file.
The Certificate window opens.
2 In the General tab, click Install Certificate... to install the certificate within your
browser.
The Certificate Import Wizard opens and a welcome message is displayed.
3 Click Next to continue, select Place all certificates in the following store radio button
and click Browse....
The Select Certificate Store window opens.
4 Select Trusted Publishers folder and click Next.
5 Complete the wizard instructions by clicking Finish.
The Certificate Import Wizard message opens displaying that the import was suc-
cessful.
6 Click Ok.
The certificate is imported to the Trusted Publishers storage.

5.1.1.4 Importing the NE’s root certificate to the Java Trusted Publishers
storage
To import the NE’s root certificate to the Java Trusted Publishers storage, proceed as
follows:
1 In the Start > Control Panel > Java > Java Control Panel > Security tab click on Cer-
tificates... button.
The Certificates window opens.
2 Select Signer CA option from the Certificate type drop-down menu.
3 Click Import.
The Open window opens.
4 Browse and select the Coriant Root certificate file.

t Select All Files option from the Files of type: drop-down menu.

Click Open.
The Coriant Root certificate is added to the Java Trusted Certificates list.
The certificate is imported to the Java Trusted Publishers storage.

5.1.2 Connecting on-site

This procedure provides the necessary steps to establish a connection on-site to an NE.
It is mandatory that the laptop is set to Dynamic Host Configuration Protocol (DHCP) client,
in order to be able to obtain an Internet Protocol (IP) address from the network.

t On-site access to EM is only possible via @CT, which cannot be launched via Telecommu-
nication Network Management System (TNMS) netservers and/or TNMS servers.

HDM-73R56070-11-0C Page 23 © Infinera 2022

OLR Commissioning OLR commissioning procedures

t Before starting to establish connection on-site to an NE, ensure your browser does not use
a proxy for the IP addresses 192.168.xxx.xxx (field Do not use proxy server for
addresses beginning with). If necessary, contact System Administrator. To configure
browser setting, complete the following steps:
1 On the Microsoft Windows task bar, select the Start > Programs > Internet Explorer
menu item.
The Internet Explorer window is opened.
2 Select Tools > Internet Options.
The Internet Options window opens.
3 In the Connections tab, click LAN settings and select the Use a proxy server for
your LAN check box.
4 Click Advanced and configure Do not use proxy server for addresses beginning
with field with the required IP addresses.
The Internet Explorer browser proxy setting is configured.

To establish a connection to an NE on-site, complete the following steps:

1 Connect the laptop to the QF Ethernet interface on the NE controller card (CCxP) via
standard Ethernet cable.
2 On the Microsoft Windows task bar, select the Start > Programs > Internet Explorer
menu item.
The Internet Explorer is opened.
3 Ensure your browser does not use a proxy for the IP addresses 192.168.xxx.xxx (field
Do not use proxy server for addresses beginning with).
4 On the web browser address bar, type one of the following URL:
• https://LocalQF. or
• http://LocalQF.
It is mandatory that a “.” is at the end of the address.
Press [Enter].
The NE Service Homepage is displayed.

t In case of a secure connection, a warning message is displayed against NE root certif-

icate. If the root certificate is not valid, import the valid root certificate fingerprint as
described in section 5.1.1 Installing the root certificate from the NE on page 21.

5 Click on Launch the @CT Installer.

A warning window is opened.
6 If the JavaFX Not Installed message is displayed, select one of the following options:
a) Install JavaFX by clicking Yes.
The JavaFX installation is required for some features such as SOR Viewer tool.
b) Skip the JavaFX installation by clicking No. In this case, the warning message is
displayed the next time the @CT is launched.
c) Skip the JavaFX installation permanently by clicking Never button. In this case, the
JavaFX Not Installed message is not displayed the next time the @CT is launched.
To revert this behavior, delete the launcher.txt file on the Launcher directory to reset

HDM-73R56070-11-0C Page 24 © Infinera 2022

OLR Commissioning OLR commissioning procedures

the stored settings. After deleting the launcher.txt file the JavaFX Not Installed
message reappears.
7 If a security warning message is displayed, check the Publisher: field. Depending on
the displayed information, select one of the following options:
a) If it displays UNKNOWN, import the root certificate to the Java Trusted Certificates
storage as described in section 5.1.1 Installing the root certificate from the NE on
page 21.
b) If it displays the expected publisher, select the I accept the risk and I want to run
the application check box and click Run.
A Login window is opened.

t If @CT is not launched, check if Keep temporary files on my computer is enabled

and launch @CT again.

8 Enter the following user account settings:

A default account is provided to access the NE for the first time.

Connection information Area

Host address: Displays/enter the DNS address of the target NE.
Port number: Displays/enter the default communication port.

g When connecting to the local NE, the port

number is, by default, 161.
Security information Area
Login name: Enter the login name for the user account.
Password: Enter a valid password.
Contact your next higher level of technical support
to obtain the default password. The default
password can be changed after the first login.
Remote login: Select the Remote login check box if you want to
login with a remote user name.
9 Do you need further configuration settings?
a) No: Skip to step 11.
b) Yes: Continue to step 10.
10 Click Options >> for further configuration settings.
Default values provided are correct for default operation.

Binding interface: Displays/select the IP address and the name of the

interface connected to the NE.
Security protocols Area
Authentication: Displays/select the default authentication protocol
(MD5).
Privacy: Displays/select the privacy protocol.
Connection options Area
Telegram timeout Display/enter the default connection telegram timeout
(1 to 30 minutes).

HDM-73R56070-11-0C Page 25 © Infinera 2022

OLR Commissioning OLR commissioning procedures

Telegram retries: Display/enter the default connection telegram retries

(2).
Pending telegrams: Display/enter the default pending telegrams (2).
It is strongly advised to change the default password after the first login.
11 Click Options << to return to the previous login screen and click Login to open the EM.
The connection to the NE is established.

5.1.3 Connecting remotely

This procedure provides the necessary steps to establish a remote connection to an NE
and start the EM. This procedure must be completed from the EM of a commissioned per-
manent gateway NE.
In order to reach/communicate with the complete DCN, the following requirements must be
fulfilled:
• An ONN configured as permanent gateway that supports a DHCP server must be com-
missioned.
• All the remaining ONNs in the DCN must be commissioned.
Once these requirements are fulfilled, the NEs designated as permanent gateway provide
a list with the available NEs in the DCN. This list is used to access other NEs.
If these requirements are not fulfilled, the list only displays the neighbor NEs, or only the
reachable NEs in the DCN.
To establish remote connection to an NE, complete the following steps:
1 In the EM main menu of a gateway NE, select Communication > Reachable Sys-
tems... menu item.
The Reachable Systems window is opened.
2 The NE name format after startup is derived from the DCN MAC address of the shelf
that contains the NE controller card. The commissioner must match that NE name with
the MAC address information noted down during installation.
Example of NE name assigned by the controller card for an NE commissioned for the
first time:
hiT-080006abcdef, where abcdef are bytes 4 to 6 of the shelf DCN MAC address in
hexadecimal notation.
According to the information above, select the correct NE name to be commissioned,
and then click Connect.
The Login window is opened.
3 A default account is provided to access the NE for the first time.
Enter the following settings of the default user account:

Connection information Area

Host address: Displays/enter the DNS address of the target NE.
Port number: Displays/enter the default communication port.
Protocol: Displays/enter the default transport protocol.
Security information Area
Login name: Administrator

HDM-73R56070-11-0C Page 26 © Infinera 2022

OLR Commissioning OLR commissioning procedures

Password: Enter the default password.

Contact your next higher level of technical support to
obtain the default password.
Click Login.
The connection to the NE is established.
It is strongly advised to change the default password after the first login.
The remote connection to the NE is complete.

5.2 Configuring the NE with the Customer Code

The Customer Code is a unique code assigned to a customer that sets many card related
and traffic related parameters to predefined customer values, thus avoiding the need to set
them during the commissioning phase.

g If a Customer Code is not available, skip this section.

To configure the NE with the Customer Code, complete the following steps:
1 In the Equipment tab, right-click the NE and select the Configuration... menu item.
The Network Element Configuration window is opened.
2 In the Management tab, under the Customer default values area, define the
Customer code.
Click Apply to confirm the settings.
The NE is configured with the Customer Code.
The system will reboot. This may take some minutes.

5.3 Configuring the NE name and location

The NE name is unique in all DCN domains and must be correct according to commission-
ing reports.
The NE physical and geographical location must display the actual location where the NE
is installed.
To set the NE name and location, complete the following steps:
1 In the Equipment tab, right-click the NE and select the Configuration menu item.
The Network Element Configuration window is opened.
2 According to commissioning reports enter the following settings:

Name: Enter the NE name.

Location: Enter the NE physical location. (max. 40 characters).
Latitude: Enter the NE geographical latitude º[-90.000000 ...
90.000000].
Longitude: Enter the NE geographical longitude º[-180.000000 ...
180.000000].
Click Apply to confirm the settings.

g The NE name must comply with strict naming convention as defined by RFC952 and
RFC1123. The NE name must comply with:

HDM-73R56070-11-0C Page 27 © Infinera 2022

OLR Commissioning OLR commissioning procedures

• minimum length: 1 character;

• maximum length: 63 characters;
• cannot begin or end with a space;
• allowed characters are A-Z, a-z, digits 0-9 and characters !”#$%&’()*+,-./:;<=>?@[\
]^_‘{|}~;.

The NE name and location is configured.

t If the NE parameters configuration is done via NCF skip to section 5.17 Changing the
administrator’s password on page 50

5.4 Configuring NE parameters with a Network Configuration

File
The Network Configuration File (NCF) contains basic settings of the NE parameters and it
is provided by TransNet. The NCFs are used for configuring new NEs or when changes in
existing installations are needed.
TransNet provides most of the configuration data, including the required equipping and the
card interconnections. Other parameters, such as DCN configurations, physical location
and specific transponder card settings have to be configured by the user.
At the initial commissioning, the NE state is set to “Not Commissioned” and the NE is in the
Service Provisioning via NCF mode. In this mode, core equipment and services configura-
tions are applied from the NCF. Depending on the NCF settings, the provisioning mode
remains the same or, it changes to the Service Provisioning via NMS or Core Provisioning
via NMS mode. For additional information on the provisioning modes, please refer to the
Operating Manual (OMN).
NCFs are only supported for OLRs and ONNs.

5.4.1 Downloading and swapping an NCF

Configuring the NE parameters with an NCF is done by downloading and swapping an
NCF.
During the initial commissioning, the NCF swap is unsynchronized.

Downloading and swapping an NCF

To download a new NCF to the NE, complete the following steps:
1 In the EM main menu, select the Configuration > Software/File Management >
NCF... menu item.
The Software/File Management window is opened.
2 Click the Download NCF... button.
The Network Element - FTP Download - NCF window is opened.
3 Depending on the desired FTP server, select one of the following radio buttons:
a) Element Manager internal server, to use the EM internal FTP server.
b) External server, to use an external FTP server.
4 The radio button selected in step 3 determines which fields are displayed on the
window, under FTP parameters. Configure the applicable fields as explained below:

HDM-73R56070-11-0C Page 28 © Infinera 2022

OLR Commissioning OLR commissioning procedures

Transfer Protocol: Select the protocol to upload the file. The available
protocols are: SFTP, FTP and FTPS.
Server address: Enter the address of the FTP/SFTP server from where
the file will be transferred.
Gateway address: Enter the NE name of the permanent gateway NE
where the file is stored.
User name: Enter the account user name of the remote server.
Password: Enter the account password of the remote server.
Host key: Enter the remote server host key.
File name: Enter the full path and name for the file.
(Please note that the file name must not have spaces).
Click Download to download the file.
The download status is displayed in a progress bar, located at the bottom of the window
and also in the MS Windows taskbar (the EM icon is colored with a green progress bar).
The NE performs an automatic NCF precheck.
5 According to the result of the automatic NCF precheck, select one of the following:
a) If the precheck succeeds, proceed to step 6.
b) If the automatic precheck is not successful, the NCF must be corrected and steps
3 to 5 must be repeated.
6 In the Software/File Management window, click the Swap NCF... button to swap the
inactive NCF to the active NCF. During the NCF swap it is not allowed to perform con-
figurations, any attempt to set NE parameters is rejected
7 A warning message, concerning traffic interruption is displayed.
Click Yes to swap the NCF.
8 A confirmation window concerning the NCF swap progress is displayed.
Click OK to proceed.
9 Click the Reset state button to set the NCF Swap state to Idle.
The NCF download and swap is complete.

t If the NCF download fails, the Swap NCF... button stays disabled. Repeat the download
procedure and if the download is successful, the Swap NCF... button is enabled and the
swapping procedure can be initiated.

g If the NE CCxP-x controller card is reset after a failed NCF download and a valid NCF is
present on the inactive bank the swap button is enabled. In this case, do not click the Swap
NCF... button. Instead, repeat the previously failed download process. Otherwise an unin-
tended downgrade will be initiated.

5.5 Configuring shelf parameters

This section contains the description for configuring shelf parameters. The following proce-
dures must be completed to achieve a successful system bring up:
• 5.5.1 Configuring shelf location on page 30
• 5.5.2 Configuring shelf display mode on page 30
• 5.5.3 Clearing the fan filter alarms on page 31

HDM-73R56070-11-0C Page 29 © Infinera 2022

OLR Commissioning OLR commissioning procedures

• 5.5.4 Disabling ILAN connector on page 31

5.5.1 Configuring shelf location

The shelf location attribute is for user information if the system is managed via SNMP.
The shelf location attribute indicates where the shelf is physically located in the office plant.
There are two possibilities to configure the shelf location field: either by directly configuring
the Location field in the shelf configuration window, or by configuring the Bay [0 ... 99] and
Shelf in Bay [0...8] fields in the same window.
Configuring the shelf location via the Location field, allows the customer to write down
where the shelf is located (for example, top shelf on the second rack from the right).
Configuring the shelf location via the Bay [0 ... 99] and Shelf in Bay [0...8] fields automat-
ically overwrites the existing Location field and displays a value like, “02-1”, which means
that the shelf is on the first shelf of bay #2. This solution requires that both fields are set,
and are unique in the same NE.
To configure the shelf‘s physical location complete the following steps:
1 In the Equipment tab, right-click the Shelf <shelf number> and select the Configura-
tion... menu item.
The <shelf number> Shelf Configuration window is opened.
2 Depending on how the shelf’s physical location must be configured, select one of the
following:
a) If configuring via the Location field, enter the desired location description in the
Location field at the top of the window and proceed to step 5.
b) If configuring via the Bay [0 ... 99] and Shelf in Bay [0...8], proceed to step 3.
3 In the Bay [0 ... 99] field, enter the number of the rack in which the shelf is physically
located.
4 In the Shelf in Bay [0 ... 8] field, enter the number of the physical location of the shelf
within the rack.
5 Click Apply to confirm the settings.
6 Repeat this procedure for all available shelves.

t To successfully use the Autogen feature of the Telcordia OSS, the Shelf in Bay [0 ... 8]
field needs to have a fixed value and therefore must be configured using the Shelf value
for this shelf. The Bay [0 ... 99] is automatically set to the value 1.
The Shelf in Bay attribute will be used to identify the shelf from then on.

The shelf‘s physical location is configured.

5.5.2 Configuring shelf display mode

Shelves can be displayed in the Shelves Configuration window ordered by their shelf id
or their physical location. The shelf display mode setting allows the customer to define
which display mode is used.
The two different settings for the Shelf display mode field are defined as follows:

Shelf ID: This is the default mode, and it means that the shelves will be dis-
played according to the order of their shelf IDs.

HDM-73R56070-11-0C Page 30 © Infinera 2022

OLR Commissioning OLR commissioning procedures

Bay Shelf: This value means that the shelves will be displayed according to
the order of their physical location.

t The fields Bay and Shelf in Bay in the <shelf number> Shelf Configuration window must
be configured for every shelf in order to be able to display them using the Bay Shelf order.

To define how the shelves will be displayed, complete the following steps:
1 In the EM main menu, select the Configuration > NE > Configuration... menu item.
The Network Element Configuration window is opened.
2 Select the Management tab.
3 In the Equipment area, select the desired mode in which the shelves will be displayed
in the Shelf display mode drop-down list.
The shelf display mode is configured.

5.5.3 Clearing the fan filter alarms

During commissioning the fan filter alarms become active for security reasons. They can
be cleared by setting the insertion date.
To set the insertion date, complete the following steps:
1 In the Equipment tab, right-click the NE, and then select the Shelves Fan Filter Con-
figuration... menu item.
The Shelves Fan Filter Configuration window is opened.
2 In the All shelves area, select the Maintenance interval between 06 and 12 months.
3 Set the Insertion date to today and click Set to All Shelves.
Click Apply to confirm the settings.
The fan filter alarms are cleared.

5.5.4 Disabling ILAN connector

All ILAN (Internal LAN) connectors on the CCxP controller card (that is, ILAN 1 and ILAN
2) which are not used in your configuration must be disabled for security reasons.

g All ILAN connectors are disabled by default.

To ensure an ILAN connector is disabled or to disable an ILAN connector, complete the fol-
lowing steps:
1 In the Equipment tab, double-click the shelf which contains the CCxP controller card.
The Shelf Equipment window is opened.
2 Right-click the controller card symbol and select the External Interfaces menu item.
The <shelf>-<slot number> <card name> External Interfaces window is opened.
3 In the tree, select the ILAN connector (ILAN 1 or ILAN 2).
4 Select Disabled from the Function drop-down list and click Apply.
The ILAN connector is disabled.

t Do not forget to enable the ILAN connectors again if this is necessary after a cabling
changed.

HDM-73R56070-11-0C Page 31 © Infinera 2022

OLR Commissioning OLR commissioning procedures

5.6 Configuring NE EOW telephone number

In addition to conference calls, it is possible to establish a selective call between NEs via
Engineering Order Wire (EOW). To achieve this it is necessary to assign a specific tele-
phone number composed of 3 digits to each NE, this number must belong to the 001-999
range. The default value for this field is 000, if this procedure is not completed the NE is
only capable of entering conference calls, or initiate a selective call to another NE, but never
receive a selective call.
To set the NE telephone number, complete the following steps:
1 In the Equipment tab, right-click the NE, and then select the Configuration menu item.
The Network Element Configuration window is opened.
2 Assign a 3 digit telephone number to the NE within the 001-999 range in the Telephone
Number [000...999] field.
The assigned telephone number must be unique within the DCN.
Click Apply to confirm the settings.
The NE telephone number is configured.

5.7 Configuring RADIUS

This section contains the necessary information to configure the RADIUS functionality in
hiT 7300 networks. The RADIUS functionality is optional in hiT 7300 networks.
The RADIUS is a networking protocol that provides the centralized authentication, authori-
zation and accounting management service. With RADIUS authentication, user accounts
are stored in any external database supported by RADIUS (for example, LDAP server, SQL
server) instead of being stored locally in the NE. The RADIUS accounting management is
not supported by hiT 7300.
The RADIUS architecture is composed of the following components:
• The RADIUS server is external to hiT 7300 networks.
• The RADIUS proxy functionality is only supported in GNEs.
• The RADIUS client functionality is supported in all NEs. The GNE may also have a
RADIUS client functionality.

g The RADIUS server is not part of the hiT 7300. The following must be observed on the cus-
tomer’s RADIUS server to achieve RADIUS functionality for hiT 7300 networks:
• On the RADIUS server the dictionary must be extended by the following vendor-specific
attributes:

VENDOR CORIANT 42229

BEGIN-VENDOR CORIANT

ATTRIBUTE HIT-System-Type 101 integer

ATTRIBUTE HIT-Service-Type 102 integer
ATTRIBUTE HIT-User-Level 103 integer
ATTRIBUTE HIT-Current-Logins 105 integer
ATTRIBUTE HIT-Available-Logins 106 integer

HDM-73R56070-11-0C Page 32 © Infinera 2022

OLR Commissioning OLR commissioning procedures

ATTRIBUTE HIT-LastLoginDateTime 107 string

ATTRIBUTE NMS-User-Groups 109 string

VALUE HIT-System-Type TNMS 0

VALUE HIT-System-Type hiT7300 7300
VALUE HIT-System-Type hiT7500 7500

VALUE HIT-Service-Type ManagementIF 1

VALUE HIT-Service-Type CET-CLI 2
VALUE HIT-Service-Type ServiceMenu 3
VALUE HIT-Service-Type WebIF 4
VALUE HIT-Service-Type TelnetIF 5

VALUE HIT-User-Level Administration 1

VALUE HIT-User-Level Configuration 2
VALUE HIT-User-Level Operation 3
VALUE HIT-User-Level Maintenance 4
VALUE HIT-User-Level Supervision 5

END-VENDOR CORIANT
• The maximum length of the user name configured at the RADIUS server is 29 charac-
ters.

g The following attributes are mandatory in the Access-Accept message, otherwise authen-
tication fails:
• HIT-Available-Logins
• HIT-User-Level

To achieve the RADIUS functionality in hiT 7300 networks, the following procedures must
be completed in the GNE with the DHCP primary role:
1 Configure the RADIUS DHCP settings as described in section 5.7.1 Configuring
RADIUS DHCP settings on page 34.
2 Configure the RADIUS proxy list as described in section 5.7.2 Configuring RADIUS
proxy list on page 35.
3 Configure the external RADIUS server settings as described in section
5.7.3 Configuring RADIUS server settings on page 36.
The RADIUS DHCP settings and RADIUS proxy list will be distributed to all NEs with
RADIUS client functionality within the DHCP domain.

To have access to the RADIUS server through the MCN router NE, the following proce-
dures must be completed at the NE with MCN router functionality:

HDM-73R56070-11-0C Page 33 © Infinera 2022

OLR Commissioning OLR commissioning procedures

1 Configure the MCN RADIUS settings as described in section 5.7.1 Configuring

RADIUS DHCP settings on page 34.
2 Configure the external RADIUS server settings as described in section
5.7.3 Configuring RADIUS server settings on page 36.

g If the hiT 7300 network is not completely migrated to R5.40 (or later APS releases), both
the NSN (for NEs with previous APS releases) and Coriant vendor specific attributes must
be configured at the RADIUS server. When configuring Coriant and NSN specific attributes,
it is advisable to use different attribute names for each vendor. For example:
NSN uses:

VENDOR NSN 28458

ATTRIBUTE User-Class 103 integer
And Coriant uses:

VENDOR CORIANT 42229

ATTRIBUTE HIT-User-Level 103 integer

5.7.1 Configuring RADIUS DHCP settings

The RADIUS DHCP settings are configured in the GNE with DHCP primary role. To config-
ure RADIUS DHCP settings, complete the following steps:
1 In the EM main menu, select the Security> Remote Authentication... menu item.
The Remote Authentication window is opened.
2 If necessary, to find the required entry from the RADIUS proxy list enter a keyword in
the window’s search field or click the Filter button (to use the hidden filter row).
3 Check the Domain Role. The RADIUS DHCP settings are configured in the GNE with
DHCP primary role.
4 Select the required table entry and click Modify....
The Remote Authentication - Modify window opens.
5 Select the authentication method from the Authentication method drop-down list:
a) Accept Local Login Only: to allow local users login only.
b) Accept Local and remote Login: to allow local and remote (RADIUS) users login.
c) Accept Remote Login Only: to allow remote users login only. In this case, the
authentication is done at the RADIUS server and when granted a temporary user
ending with RU alphabetic characters is created in the NE's user data base.
Confirm the warning message.

g To select Accept Remote Login Only authentication method, at least one RADIUS
server and one RADIUS proxy list must be available.

w NOTICE: In case of RADIUS server unavailability, setting the authentication method to

Accept Remote Login Only will cause loss of communication with all NEs of the corre-
sponding DHCP domain.

6 Select the authentication protocol from the Authentication protocol drop-down list:
a) use PAP: to configure PAP authentication protocol.
b) use CHAP: to configure CHAP authentication protocol.

HDM-73R56070-11-0C Page 34 © Infinera 2022

OLR Commissioning OLR commissioning procedures

t In domains connected via border NEs, the used Authentication protocol must be the
same: either PAP or CHAP.

7 Enter the Shared Secret.

8 Enter the Server retry timeout value.
9 Enter the Server retry count value.
10 Click Apply to confirm the settings.
11 Depending on the predicted worst RADIUS login timeout, select one of the following
options:
a) If the predicted worst RADIUS login timeout is lower than 120 seconds, the config-
uration is accepted and the procedure is completed.
b) If the predicted worst RADIUS login timeout is higher than 120 seconds, an error
message is displayed. Close the error message window and repeat steps 8 to 11 to
enter new values for Server retry timeout and Server retry count.

t The predicted worst RADIUS login timeout is obtained by performing the following cal-
culation: worst radius login timeout = (1 + Server retry count value) * Server retry
timeout value * number of RADIUS proxy entries.
The RADIUS DHCP settings are configured.

g The network element which acts as DHCP primary server has also to be configured as
RADIUS proxy including a RADIUS server table.

5.7.2 Configuring RADIUS proxy list

The RADIUS proxy list configuration is only applicable to the GNE with DHCP primary role.
It is possible to add up to 4 proxy entries.
To add a RADIUS proxy list complete section Adding a RADIUS proxy list entry on page 35.
To delete a RADIUS proxy list complete section Deleting a RADIUS proxy list entry on page
36.

Adding a RADIUS proxy list entry

To add a RADIUS proxy list entry, complete the following steps:
1 In the EM main menu, select the Security> Remote Authentication... menu item.
The Remote Authentication window is opened.
2 If necessary, to find the required entry from the RADIUS proxy list enter a keyword in
the window’s search field or click the Filter button (to use the hidden filter row).
3 Select the required table entry and click Modify... to configure the RADIUS proxy list.
The Remote Authentication - Modify window opens.
4 Click Add to add a new entry in the Proxy list.
The Proxy List - Add window is opened.
5 Configure the following settings:

Index: Enter the RADIUS proxy list entry index.

Name: Enter the RADIUS proxy list entry name.
6 Click Add to confirm the settings.

HDM-73R56070-11-0C Page 35 © Infinera 2022

OLR Commissioning OLR commissioning procedures

The Proxy List - Add window closes and a new RADIUS proxy list entry is listed in the
RADIUS proxy list.
7 Click Close to close the window.
The RADIUS proxy list entry is added.

Deleting a RADIUS proxy list entry

To delete a RADIUS proxy list entry, complete the following steps:
1 In the EM main menu, select the Security> Remote Authentication... menu item.
The Remote Authentication window is opened.
2 Select the required entry from the Proxy list.
3 Click Delete to delete the selected RADIUS proxy list entry.
Confirm the warning message.
4 Click Close to close the window.
The RADIUS proxy list entry is deleted.

5.7.3 Configuring RADIUS server settings

The RADIUS server settings must be configured in GNEs with RADIUS proxy running. The
maximum number of RADIUS servers allowed to configure per GNE is 3.
To add a RADIUS server complete section Adding a RADIUS server on page 36.
To delete a RADIUS server complete section Deleting a RADIUS server on page 36.

Adding a RADIUS server

To add a RADIUS server, complete the following steps:
1 In the EM main menu, select the Security > RADIUS Server... menu item.
The RADIUS Server Configuration window is opened.
2 Click Add to configure the RADIUS Server.
The RADIUS Server - Add window opens.
3 Configure the following settings:

IP address: Enter the RADIUS server IP address in IPv4 or IPv6 format.

Shared Secret: Enter shared secret of the RADIUS server. The shared secret
may be up to 128 octets as SNMP Display String.
4 Click Add to confirm the settings.
The RADIUS Server - Add window closes and a new RADIUS server is listed in the
RADIUS server list.
5 Click Add to confirm the settings.
6 Click Close to close the RADIUS Server Configuration window.
The RADIUS server is added.

t The newly added RADIUS server Accessibility state will remain unknown until the first
request to server.

Deleting a RADIUS server

To delete a RADIUS server, complete the following steps:

HDM-73R56070-11-0C Page 36 © Infinera 2022

OLR Commissioning OLR commissioning procedures

1 In the EM main menu, select the Security > RADIUS Server... menu item.
The RADIUS Server Configuration window is opened.
2 Select the RADIUS server from the RADIUS server list.
3 Click Delete to delete the selected RADIUS server.
Confirm the warning message.
4 Click Close to close the RADIUS Server Configuration window.
The RADIUS server is deleted.

5.8 Configuring the Network Time Protocol and NE time

The Network Time Protocol (NTP) is used for time synchronization of the NEs in the DCN.
When synchronized, all NEs use the same reference clock for optical link control and time
stamping of log entries, issued events, and so on.
The NEs configured as DHCP servers function as the NTP servers for the DCN. These NEs
should use external NTP servers in the customer network for time synchronization.
If no external NTP servers are available the primary DHCP server NE time must be set
manually and the secondary DHCP server should obtain the NE time from the primary
DHCP server.

t A primary DHCP server obtaining the NE time from the secondary DHCP server is not rec-
ommended. While configuring the NTP server ensure that this information is taken into
account.

In multi-domain topologies, border-NEs which are configured as DHCP clients, obtain time
synchronization from all the DHCP server NEs (that is, DHCP servers from all the network
domains) by selecting the best reference time.
The remaining NEs in the DCN rely on the DHCP server for time synchronization. If no
DHCP/NTP server is available/reachable in the DCN, the NE time must be set manually.
The NE time can only be configured if there is no NTP server available (SONs and ONNs
with primary DHCP server enabled). Once an NTP server is configured, the NE time is auto-
matically overridden.

t When the Time Zone settings of the PC running the TMN system and/or EM are changed
it is required to perform a full restart of the TMN system and/or EM (that is, close the window
and start the system again).

5.8.1 Configuring an external NTP server

t This procedure is only valid for primary or secondary DHCP server NEs.

To configure an external NTP server, complete the following steps:

1 In the EM main menu, select the Configuration > NE > NE Time > Configuration...
menu item.
The NTP Configuration window is opened.
2 In the Servers area, click Add... button.
The NTP Servers - Add window is opened.
3 Set the following parameters:

HDM-73R56070-11-0C Page 37 © Infinera 2022

OLR Commissioning OLR commissioning procedures

Server address: Enter the IP or DNS address of the NTP server.

Key ID: Enter the key ID [0 (=not authenticated), 1 ...65534].
To set NTP keys see section 5.8.3 Configuring NTP
keys on page 38.
Click Add. A new NTP server is added to the Manual NTP references table. If applica-
ble, it is possible to change the server address or the key ID in the respective table
entries and after clicking Apply.
The external NTP server is configured.

5.8.2 Configuring NE time

Prior configuring the NE time, take into consideration the following conditions:

• This procedure requires that no external NTP servers are configured in the DHCP
server NEs.
• The default NE time is 08-05-2013. While adjusting the NE time, the new date must not
be changed to a date previous to the default NE time. The maximum value for NE date
and Time is 07/02/2106 and 06:28:15 GMT.
• Setting NE time to a previous date and time will close the EM. Despite this behavior,
new NE time will be set correctly after EM restart.
To configure the NE time, complete the following steps:
1 In the EM main menu, select the Configuration > NE > NE Time > Configuration...
menu item.
The Network Element Time Configuration window is opened.
2 Select one of the following:
a) To configure the NE time with the PC time, proceed to step 3.
b) To configure the NE time manually, proceed to step 4.
3 In the Adjust NE Time to area, select the Adjust to PC time check box and proceed
to step 5.
4 In the Adjust NE Time to area, set the NE time and date in the UTC fields and select
the desired Universal Time Coordinated (UTC) from the Relative to UTC drop-down
list.
5 Click Apply to confirm the settings.
The NE time is configured.

5.8.3 Configuring NTP keys

The authentication to an external NTP server can be achieved using NTP keys. To enable
authentication the key ID must be configured with a numeric digit different than “0” and in
the range of [1... 65534].
In case of a DCN network, the authentication is provided between hit 7300 gateway NEs
and the external NTP servers. In case of an MCN network, the authentication is provided
between every hit 7300 NE connected to the MCN and the external NTP servers. The NTP
authentication is not applicable to the internal DCN network.

HDM-73R56070-11-0C Page 38 © Infinera 2022

OLR Commissioning OLR commissioning procedures

Adding an NTP key

To add an NTP key, complete the following steps:
1 In the EM main menu, select the Configuration > NE > NE Time > NTP Configura-
tion... menu item.
The NTP Configuration window is opened.
2 In the Keys area, click Add... button.
The NTP Keys - Add window is opened.
3 Set the following parameters:

Key ID: Enter a Key ID, a digit in the range of 1 to 65534.

Key: Enter the key. The key string may contain printable
ASCII characters and must not contain the following
characters: space, “#” and “€”.
Click Add.
A new entry is added to the NTP key table.

t After adding the new NTP Key ID, the corresponding Key is not visible in the Keys table.
If necessary, to change the Key of a Key ID, the affected Key ID must deleted and created
again.

Deleting an NTP key

To delete an NTP key, complete the following steps:
1 In the EM main menu, select the Configuration > NE > NE Time > NTP Configura-
tion... menu item.
The NTP Configuration window is opened.
2 In the Keys area, select the key entry to delete and click Delete... button.
The selected key entry is deleted from the NTP key table.

5.9 Configuring NE parameters manually

When an NCF is not available, the NE parameters must be configured manually. In this
case, the provisioning mode must be set to Core Provisioning via NMS. All manual config-
urations in the Core Provisioning via NMS mode must be done according to the commis-
sioning reports.

t If you configured the NE parameters with an NCF, continue to section 5.10 Configuring
external interfaces on page 42.

g If the Core Provisioning via NMS mode is chosen for manual configuration, future NE con-
figuration with NCF is only possible by changing the provisioning mode. For additional infor-
mation on provisioning modes and NE parameters configuration, please refer to the OMN.

f DANGER! In the Core Provisioning via NMS mode set parameter values always as given
in the commissioning reports. Any deviation bears the risk of exceeding the laser safety
hazard level of the hiT 7300 system as well as its malfunction.

The settings listed in the commissioning reports must be set according to the following
sections and order:
1. 5.9.1 Checking NE type on page 40

HDM-73R56070-11-0C Page 39 © Infinera 2022

OLR Commissioning OLR commissioning procedures

2. 5.9.2 Setting the core provisioning via NMS mode on page 40

3. 5.9.3 Adding a DCM tray on page 40
4. 5.9.4 Adding cards to shelves on page 41
5. 5.9.5 Setting THz decimal digits on page 42

5.9.1 Checking NE type

By default each network element is delivered as an OLR. This must be checked since it is
not possible to change the NE type after the core provisioning via NMS mode is set.
To check the NE type, complete the following steps:
1 In the Equipment tab, right-click the NE, and then select the Configuration menu item.
The Network Element Configuration window is opened.
2 Click the General tab and check whether OLR is set in the Type drop-down list.
If this is not the case select OLR from the Type drop-down list.
3 Click Close and Apply respectively.
The EM is restarted.
The NE type is checked.

5.9.2 Setting the core provisioning via NMS mode

At the initial commissioning the NE state is set to “Not Commissioned” and the NE is in the
Service Provisioning via NCF mode. To commission the NE manually via NMS, the Core
Provisioning via NMS mode has to be set. When this mode is set, NE parameters have to
be configured according to the commissioning reports.

f DANGER! Set parameter values always as given in the commissioning reports. Any devi-
ation bears the risk of exceeding the laser safety hazard level of the hiT 7300 system as
well as its malfunction.

To set the core provisioning via NMS mode, complete the following steps:
1 In the Equipment tab, right-click the NE, and then select the Configuration menu item.
The Network Element Configuration window is opened.
2 Click the General tab, then enter the following settings:

Name: Enter the NE name according to commissioning

reports.
Core provisioning: Select via NMS (default).
3 Click Apply to confirm the settings.
The core provisioning via NMS mode is set.

5.9.3 Adding a DCM tray

Complete this procedure if a Dispersion Compensation Module (DCM) tray is required in
the NE.
To complete this procedure the following parameters must be assured:
• The commissioning reports require that a shelf from the NE is extended by a DCM tray.
• The DCM tray is physically installed in the NE.

HDM-73R56070-11-0C Page 40 © Infinera 2022

OLR Commissioning OLR commissioning procedures

A shelf can be extended by the number of slots of a DCM tray (4 available slots). The DCM
tray will be considered an extension of the shelf and hold dispersion compensation cards.
The DCM tray shelf is managed by the associated shelf.
To configure a shelf to manage an external DCM tray, complete the following steps:
1 In the Equipment tab, right-click the shelf that will manage the DCM tray and select the
Configuration... menu item.
The <shelf> Configuration window is opened.
2 Select the Shelf Extended by DCM Tray check box, at the end of the window, and then
click Apply to confirm the selection.
The DCM tray shelf extension is configured.

5.9.4 Adding cards to shelves

To be able to add cards to the shelves via EM, it is mandatory that the same cards are phys-
ically installed in the NE according to the Installation Manual (IMN).
Please refer to the Installation Manual (IMN) to check the card availability for the correspon-
dent NE being installed. Only cards listed as possible for the correspondent NE ensure the
system’s correct functioning.
Prerequisite: The link direction of the shelf is set. This setting ensures that the card’s auto-
configuration function works properly.
To add a card via EM, complete the following steps:
1 In the Equipment tab, double-click the shelf with the card to be added.
The Shelf Equipment window is opened.
2 According to the commissioning reports select the correct shelf tab (for example, Shelf
001) to add the card.
3 According to the commissioning reports right-click the slot symbol (for example, 001)
where the card was installed, and select the correspondent card name, and if applica-
ble, the card subtype and the link direction from the displayed list.
While EM acquires all the necessary data from the card, the card symbol is displayed
in orange (that is, not ready to carry traffic). The card will be ready to carry traffic when
the card symbol is displayed in yellow.
The card is added to the shelf.

g Before adding a new card wait until the last command is acknowledged (can take up to 90
seconds) from the NE (that is, the “no pending jobs” symbol is displayed at the right-end of
the status bar).

Adding CCB-1 card and related OBDR8-1 and OTDR16-1 card modules
The CCB-1 module must be added before adding the OBDR8-1 and OTDR16-1 card
modules. To add CCB-1 card and related OBDR8-1 and OTDR16-1 card modules,
complete the following steps:
1 Verify if the shelf slot where the new module will be installed is equipped as empty or
empty-auto.
2 If not yet installed, physically install the CCB-1 card on the required slot of the shelf/NE,
as described in the Installation Manual (IMN).

HDM-73R56070-11-0C Page 41 © Infinera 2022

OLR Commissioning OLR commissioning procedures

3 In the corresponding Shelf Equipment window, right-click the slot symbol where the
CCB-1 was installed and select Other > CCB.
In the EM, the CCB-1 module symbol is displayed in the slot symbols area in orange
color.
4 Right-click on the newly added CCB-1 card slot symbol and click Equipment...
The <shelf>-<slot> CCB-1 Equipment window opens showing two empty sub-slots.
5 If not yet installed, physically install the OTDR16-1 and OBDR8-1 card modules on sub-
slots #1 and #2, respectively, of CCB-1 card, as described in the Installation Manual
(IMN).
6 If not yet installed, install all the necessary cabling, as described in the Interconnect,
Configuration and Mechanical Assembly (ICMA).
7 Right-click on the sub-slot #1 of CCB-1 Equipment window and select OTDR16.
In the EM, the OTDR16-1 card module symbol is displayed in the sub-slot #1.
8 Right-click on the sub-slot #2 of CCB-1 Equipment window and select OBDR8.
In the EM, the OBDR8-1 card module symbol is displayed in the sub-slot #2.
The CCB-1 card and related OBDR8-1 and OTDR16-1 card modules are added to the
shelf.

5.9.5 Setting THz decimal digits

The EM can display the DWDM frequency unit THz with 3 or 6 decimal digits. It is possible
to set the number of decimal digits to display the frequency (in THz unit) in the following
cases:
• the NE is in Not commissioned state (a user with supervision privileges can change
the THz decimal digits); or
• the NE is in Commissioned state and the user has power user privileges (power user
login is required).
To change the number of decimal digits to display the frequency (in THz unit) complete the
following steps:
1 If the NE is in Commissioned state, enter in Power User mode. Otherwise skip to step
2.
2 In the EM main menu, select File > Options... menu item.
The Options window is opened.
3 In the General tab, DWDM units area, select the THz decimal digits from the drop-
down menu (either #.### THz for 3 decimal digits or #.###### THz for 6 decimal digits).
4 Click Apply to confirm the settings.
5 If applicable, exit the Power User mode.
The number of decimal digits to display the THz frequency unit is set.

5.10 Configuring external interfaces

To use external interfaces it is necessary to configure via EM:
• the Ring Manager for EOW connections (refer to 5.10.1 Configuring Ring Manager on
page 43),

HDM-73R56070-11-0C Page 42 © Infinera 2022

OLR Commissioning OLR commissioning procedures

• User channels (refer to 5.10.2 Configuring user channels on page 44).

5.10.1 Configuring Ring Manager

The Ring Manager (when enabled for a shelf) interrupts the EOW connectivity between the
two OSC connections of the optical lines terminated in that shelf.
In a working ring configuration, the EOW connectivity is ensured via a redundant path in the
ring or network. Therefore, the separation of the two OSC connections is required to keep
the EOW network loop-free and prevent echo and feedback noise.
If the connectivity in the network is interrupted (for example, due to a fiber break) the Ring
Manager detects such interruption and connects the two OSC connections (that is, the
redundant EOW path is closed in order to maintain the EOW connectivity).
The Ring Manager does not supervise and cannot interrupt any 4-wire interface connection
on the CCSP-1, CCEP-2 or CCMP-2 card. It only affects EOW connections via OSC termi-
nations (optical line terminations) in the same shelf.
If CCSP-1, CCEP-2, CCMP-2 or CTIF is unplugged from the shelf, the EOW is bypassed
through the shelf via OSC channel (the EOW is not terminated in the shelf).
The following rules must be taken into consideration before a Ring Manager configuration:
• Multidegree NEs (that is, ONNs) terminating optical lines in different shelves must use
a 4-wire cable to connect the EOW interfaces of all the controller cards. Automatic con-
nection via OSC only exists if the optical lines are terminated on the same shelf.
• In networks where the optical lines are terminated on the same shelf of the ONN, the
EOW Ring Manager (if enabled) supervises the EOW connectivity.
• If the optical lines are terminated in different shelves the Ring Manager should be
disabled since it cannot supervise the EOW connectivity. The Optical Line Repeaters
(OLR) in the network should be used instead to supervise the EOW (that is, Ring
Manager must be enabled on OLRs).
• The Ring Manager must be activated in a particular shelf (or shelves) of the NE (or NEs)
such that no closed loops are formed within the network. The shelves/NEs configured
as Ring Manager should be strictly the necessary ones to maintain an EOW loop-free
network.
Figure 8 displays two examples of a ring and meshed networks with an EOW loop-free con-
figuration.

HDM-73R56070-11-0C Page 43 © Infinera 2022

OLR Commissioning OLR commissioning procedures

Ring

ONN

OLR

Ring
Meshed
manager
enabled

4-wire
cable
removal

Figure 8 Loop-free networks

For a simple ring network, the Ring Manager must be enabled at only one OLR (or ONN
where both optical lines are terminated in the same shelf). In a meshed network (for
example, with eight NEs), at least two Ring Managers must be enabled.
To enable EOW Ring Manager on a specific shelf, complete the following steps:
1 In the EM main menu, select the Configuration > NE > Shelves... menu item.
The Shelves Configuration window is opened.
2 In the Ring manager column, select the check box of the desired shelf and then click
Apply.
The EOW Ring Manager of the desired shelves is enabled.

5.10.2 Configuring user channels

User channels provide point-to-point Ethernet connections between the NEs via the OSC.
The OSC is received/transmitted via the line amplifier cards. It communicates with the con-
troller cards to provide access to the user channels via the User 1 and User 2 Ethernet con-
nectors.
For each span two user channels are available:
• per optical DWDM link via the OSC.
Each optical path provides two user channels and a DCN channel. NEs can be intercon-
nected by several optical paths. Per each optical path up to four user channels can be
carried (two for each link direction). Each user channel carries a distinct VLAN tag to differ-
entiate the user channels within the same span.
Up to two user channels can be terminated on each controller card. Transit user channels
(that is, transfer traffic routed to another span) are forwarded to the respective span by the
NE shelf controller.
The actual number of user channels that can be used in an NE depends on the number of
transponders and line amplifier cards configured with OTU-k. Per NE a maximum of 8 OSC
channels is supported. However, only two user channels can be terminated per shelf.
In the OLRs the user channels can be terminated or through connected (default), depend-
ing on the configuration in the EM.

HDM-73R56070-11-0C Page 44 © Infinera 2022

OLR Commissioning OLR commissioning procedures

g An user channel cannot be used to close external Ethernet rings because the STP of the
external ring will not work.

5.10.2.1 Configuring the User 1/User 2 interface

To configure the User 1 or User 2 interface, complete the following steps:
1 In the EM main menu, select the Communication > External Interfaces... menu item.
The External Interfaces window is opened.
2 Open the tree, search for the shelf and search for the controller card.
3 Select the controller card and select User 1 or User 2, respectively.
4 Select User Channel from the Function drop-down list and click Apply to confirm the
settings.
5 Configure the following settings:

Link direction: Select the link direction.

Channel ID: Select the channel.
6 Click Apply to confirm the settings.
The User 1/User 2 interface is configured.

5.10.2.2 Configuring user channels via OSC

Configuring user channels via OSC is not applicable in the following cases:

• in network topologies using SON NEs (for example, point-to-point passive solutions and
long single span using MPBC RMH07/1RU/2RU series),
• for multicontroller NEs.
To configure the user channels via OSC, complete the following steps:
1 In the EM main menu, select the Communication > User Channels Connections...
menu item.
The User Channel Connections window is opened.
2 Click the Add button.
The User Channels Connections - Add window is opened.
3 Configure the following settings:

Shelf: Select the shelf which contains the amplifier card.

User channel A Area
Link direction: Select the link direction.
Channel ID: Select the channel.
User channel B Area
Link direction: Select the link direction.
Channel ID: Select the channel.
4 Click the Add button.
The user channels via OSC are configured.

HDM-73R56070-11-0C Page 45 © Infinera 2022

OLR Commissioning OLR commissioning procedures

5.11 Configuring a CFSU-x card

The CFSU-x card performs airflow measurements in order to detect when the shelf's fan
filter is clogged. The result of the last successful airflow measurement is displayed in the
Measured air flow field. If this value is lower than the value displayed in the Air flow
threshold field, the LowCFSUFlow alarm is raised to indicate that the fan filter is clogged
and needs to be replaced.
Complete this procedure when a CFSU-x card is installed in the shelf.
It is possible to configure the CFSU-x card in order to perform predefined cyclic measure-
ments, or manual measurements upon customer request via a check air flow button.

t It is not possible to simultaneously have a CFSU-x and a CDMM-2 card in the same shelf.

To configure a CFSU-x card, complete the following steps:

1 In the Shelf Equipment window, right-click the CFSU-x card and select the Card >
Configuration... menu item.
The <shelf>-<slot number> CFSU-x Configuration window is opened.
2 In the Measurement area, select the type of measurement from the Type drop-down
box:
a) Cyclic: if the measurement intervals are to be cyclic, and proceed to step 3.
b) Manual: if the measurement is to be done upon customer request, and the proce-
dure is complete.
3 In the Measurement area, enter the desired time interval between measurement cycles
to the Interval h [1 ... 256] field.
This field is only effective if the Type field is set to cyclic (that is, the required measure-
ment is automatically started for every defined interval).
4 In the Measurement area, select the type of subrack from the Air flow profile drop-
down box.
5 Click Apply to confirm the settings.
The CFSU-x card is configured.

5.12 Configuring fan filter maintenance settings

The fan filter maintenance settings are responsible for monitoring the replacement period
of the fan filter units.
The user must define the actual status of the fan filter unit and the date of installation, this
information will then be used to raise correspondent alarms.
Depending on whether the fan filter maintenance settings are performed for a single shelf
NE or a multiple shelves NE, perform one of the following procedures:
• 5.12.1 Configuring fan filter maintenance settings for single shelf NEs on page 46
• 5.12.2 Configuring fan filter maintenance settings for multiple shelves NEs on page 47

5.12.1 Configuring fan filter maintenance settings for single shelf NEs

t To configure a single shelf only even if the NE has multiple shelves use this procedure also.

HDM-73R56070-11-0C Page 46 © Infinera 2022

OLR Commissioning OLR commissioning procedures

To configure a shelf fan filter parameters, complete the following steps:

1 In the Shelf Equipment window, right-click the Shelf <shelf number> (<shelf type>)
bar and select the Configuration... menu item.
The <shelf number> Shelf Configuration window is opened.
2 In the Fan Filter area, select the filter durability from the Maintenance interval drop-
down list:
a) Interval 12 Months: The fan filter does not need supervision, and must be replaced
after 12 months period.
b) Interval 10 Months: The fan filter does not need supervision, and must be replaced
after a 10 months period.
c) Interval 8 Months: The fan filter should be periodically checked, and must be
replaced after a 8 months period.
d) Interval 6 Months: The fan filter should be periodically checked, and must be
replaced after a 6 months period.
3 Select the day on which the fan filter was installed by selecting it from the ... button in
the Insertion date field, and then select the insertion hour in the following box.
Click Apply to confirm the settings.

t An equipment alarm will be raised if the NE actual date and time exceeds the fan filter
maintenance time.

t If the shelf contains the optional CFSU card, there is a button on the card’s front panel
named Restart. Press this button (a small tool is required) and hold the button for at
least 5 seconds. The CFSU will perform and airflow measurement and the filter replace-
ment timer will be reset. As a result, the new filter’s Insertion Date (visible on the
Element Manager Shelf - Configuration window) will be set to the current date and
time.
If the shelf does not contain a CFSU card, restart the timer via Element Manager. In the
Shelf Equipment window, right-click on the Shelf bar and select Configuration. On
the resulting window, click the Fan filter Configuration button, enter the current date
and time in the fields provided, and then click the Apply button.

The shelf fan filter settings are configured.

5.12.2 Configuring fan filter maintenance settings for multiple shelves NEs

t To configure a single shelf only, even if the NE has multiple shelves use the procedure
5.12.1 Configuring fan filter maintenance settings for single shelf NEs on page 46 instead.

To configure all the NE’s filter parameters, complete the following steps:
1 In the Equipment tab, right-click the NE and select the Shelves Fan Filter Confi-
guration... menu item.
The Shelves Fan Filter Configuration window is opened.
2 In the All shelves area, select the filter durability from the Maintenance interval drop-
down list:
a) Interval 12 Months: The fan filter does not need supervision, and must be replaced
after 12 months period.

HDM-73R56070-11-0C Page 47 © Infinera 2022

OLR Commissioning OLR commissioning procedures

b) Interval 10 Months: The fan filter does not need supervision, and must be replaced
after a 10 months period.
c) Interval 8 Months: The fan filter should be periodically checked, and must be
replaced after a 8 months period.
d) Interval 6 Months: The fan filter should be periodically checked, and must be
replaced after a 6 months period.
3 In the Insertion date field, configure the insertion date and time by updating the date
combo box and time spinner box.
4 Configure all the shelves with the same parameters by clicking the Set to All Shelves
button.
Click Apply to confirm the settings.

t An equipment alarm will be raised if the fan filter insertion date plus the fan filter main-
tenance time exceeds the NE actual date and time.

t If the shelf contains the optional CFSU card, there is a button on the card’s front panel
named Restart. Press this button (a small tool is required) and hold the button for at
least 5 seconds. The CFSU will perform and airflow measurement and the filter replace-
ment timer will be reset. As a result, the new filter’s Insertion Date (visible on the
Element Manager Shelf - Configuration window) will be set to the current date and
time.
If the shelf does not contain a CFSU card, restart the timer via Element Manager. In the
Shelf Equipment window, right-click on the Shelf bar and select Configuration. On the
resulting window, click the Fan filter Configuration button, enter the current date and
time in the fields provided, and then click the Apply button.

The NE’s fan filter settings are configured.

5.13 Configuring MCP4-x cards

The MCP4-x card can be installed in an OLR only if ONNs NEs at both ends are not ONN-
X96. Complete this procedure when an MCP4-x card is installed in the shelf. MCP404-x
cards cannot be installed in OLR NEs.
MCP4-x cards are used to measure and monitor the power of the optical channels in the
NE subsystem. By default the configuration is set for Standard APC and must be changed
via network element configuration file (NCF) or manually set the Peak picking parameter
according to TransNet commissioning report.
If the OLR is in an OTS transmitting in a flexible DWDM grid it is recommended to use
MCP4-2/F or MCP4-3/F card.
To configure the Peak picking parameter of an MCP4-x card, complete the following
steps:
1 In the Shelf Equipment window, right-click the MCP card and select the Card > Con-
figuration... menu item.
The <shelf>-<slot number> MCP Configuration window is opened.
2 Select the Peak picking parameter drop-down box, and choose one of the following
according to the commissioning report:
a) DPSK 40G
b) Standard

HDM-73R56070-11-0C Page 48 © Infinera 2022

OLR Commissioning OLR commissioning procedures

c) HBR1
d) HBR2
e) HBR3
Click Apply to confirm the settings.
The MCP card is configured.

5.14 Activating and deactivating the Mark card by slow flashing

of LEDs function
The Mark card by slow flashing of LEDs function is used to remotely highlight a defined
card by flashing the LEDs of the card faceplate. This function is automatically deactivated
if the card is rebooted.
CCSP-x controller cards and peripheral cards are highlighted in the following way:
• Locally, the CCSP-x controller card is highlighted with the slow flashing of its faceplate
FAULT and OK LEDs. When flashing, these LEDs are 1s switched on and 1s switched
off.
• Locally, the peripheral card is highlighted with the slow flashing of its faceplate FAULT
and OK LEDs. When flashing, these LEDs are 1.5s switched on and 1.5s switched off.
• In the GUI, peripheral and CCSP-x controller cards’ symbol displays a flashing red and
green colored LED.

t The Mark card by slow flashing of LEDs function is not supported for CCEP-x, CCMP-x,
CFS-x, all DCM cards, F04MDN-1, F04MDU-1, F08MR-1, F08SB-1, F16SB-1, F40-1,
F40MDS-1, F40MR-1, F80DCI-1, F80MDI-1, FCDI-1, O02CT-1 and O03CP-1 cards.

Activating the Mark card by slow flashing of LEDs function

To activate the Mark card by slow flashing of LEDs function complete the following steps:
1 In the Shelf Equipment window, right-click the card symbol and select the Card > Con-
figuration... menu item.
The <shelf>-<slot number> <card name> Configuration window is opened.
2 In the Mark card by slow flashing of LEDs area, click Start.
The card symbol, in the Shelf Equipment window, displays a flashing red and green
colored LED. In the shelf, the corresponding card’s faceplate LEDs start flashing.
The Mark card by slow flashing of LEDs function is activated.

Deactivating the Mark card by slow flashing of LEDs function

To deactivate the Mark card by slow flashing of LEDs function complete the following
steps:
1 In the Shelf Equipment window, right-click the card symbol and select the Card > Con-
figuration... menu item.
The <shelf>-<slot number> <card name> Configuration window is opened.
2 In the Mark card by slow flashing of LEDs area, click Stop.
In the Shelf Equipment window, the card symbol flashing LED is removed. In the shelf,
the corresponding card’s faceplate LEDs stop flashing.
The Mark card by slow flashing of LEDs function is deactivated.

HDM-73R56070-11-0C Page 49 © Infinera 2022

OLR Commissioning OLR commissioning procedures

5.15 Setting card user label

The user label field of each card is used to assign customer specific card information for
future tracking or control. To identify that this task is not completed the EM will surround the
user label field with a thin blue frame. After completion of this task the EM will remove the
blue frame.

t Cards from product releases before 4.30 will display blank spaces in the User label field.

To configure the card user label, complete the following steps:

1 In the Shelf Equipment window, right-click the selected card and select the Card >
Configuration... menu item.
The User label field is filled with dots by default, if configuring this field for the first time.

t Cards from product releases before 4.30 display blank spaces in the User label field.

2 Select the whole content of the User label field if it is not already selected, and delete
the content of the User label field to be able to enter a new value.
3 In the User label field enter the customer specific card information.
4 Click Apply to confirm the settings.
The user label is configured.

5.16 Verifying NE DCN configuration

This procedure can only be completed via a Gateway NE, in the same domain as the NE
being checked, and allows to verify if the NE is reachable via DCN.
In order to properly verify the NE DCN configuration, the following preconditions must be
met:
• no LAx equipment alarms can be active.
• no LOS alarms at the LAx cards can be active.
1 In the EM main menu from a Gateway NE, select the Communication > Reachable
Systems... menu item.
The Reachable Systems window is opened
2 Verify that the NE is listed with the correct NE name according to the commissioning
reports.
3 Verify that the DHCP Lease State for the NE is "Lease Granted”.

t If steps 2 and 3 are not verifiable, ensure that the preconditions at the top of the procedure
are achieved and repeat the procedure.

The NE is reachable via DCN.

5.17 Changing the administrator’s password

For security reasons, it is recommended to change the password of the default administra-
tion account Administrator after the initial login.
Coriant does not recommend modifying
• other attributes of the default administration account Administrator than the default
password.

HDM-73R56070-11-0C Page 50 © Infinera 2022

OLR Commissioning OLR commissioning procedures

• the default BackupAdmin account.

To change the administrator’s default password, complete the following steps:
1 In the EM main menu, select Security > Change Password - Administrator... menu
item.
The Change Password - Administrator window is opened.
2 Enter the following settings:

Current password: Enter the current account password.

Password: Enter the new account password.
Confirm Password: Confirm the new account password.
Click OK to confirm all settings, and confirm the security message.
The password of the Administrator account is changed.

5.18 Setting NE state to commissioned

Setting the NE state to commissioned means that the commissioner accepts that the
previous configurations are correct and the NE can be acknowledged as commissioned.
Completing this procedure concludes the NE commissioning phase.
To set NE state to commissioned, complete the following steps:
1 In the Equipment tab, right-click the NE, and then select the Configuration menu item.
The Network Element Configuration window is opened.
2 Click Set to Commissioned, and then click Apply.
The NE is in the commissioned state.

HDM-73R56070-11-0C Page 51 © Infinera 2022

OLR Commissioning Post-commissioning tasks

6 Post-commissioning tasks
This section contains all the necessary information to complete the post-commissioning of
an OLR.

6.1 Uploading the MIB contents

It is mandatory that the MIB contents are manually uploaded from the NE after the first com-
missioning and stored on a server or other computer drive. Doing so ensures that a copy of
the most recent MIB contents is available to manually download back to the NE in case the
NE loses its MIB contents.

g If Element Management Internal Server radio button is selected, the Transfer Protocol
is automatically set and cannot be changed.

To upload an NE’s MIB contents, complete the following steps:

1 In the EM main menu, select the Configuration > Software/File Management > MIB...
menu item.
The Software/File Management window will open in the MIB tab.
2 Click the Upload... button.
The Network Element - FTP Upload - MIB window will open.
3 Depending of the desired FTP server, select one of the following radio buttons:
a) Element Manager internal server: to use the EM internal FTP server.
b) External server: to use an external FTP server. An external FTP server must be
used when the computer from where the EM is started does not have direct access
to the Gateway NE (for example, TNMS in a client-server configuration).
4 The radio button selected in step 3 determines which fields are displayed on the
window. Configure the applicable fields as explained below:

Transfer protocol: Select the protocol to upload the file. The available
protocols are: SFTP, FTP and FTPS.
Server address: Enter the IP address of the remote FTP server. This
field is displayed only if “External Server” was
selected in step 3.
Gateway address: Enter the name of the Gateway NE from where the
FTP transfer will be routed. This field is active only if
“External Server” was selected in step 3.
User name: Enter the User Name of the log-in account for FTP
authentication. This field is displayed only if “External
Server” was selected in step 3.
Password: Enter the password of the log-in account for FTP
authentication. This field is displayed only if “External
Server” was selected in step 3.
Host key: Enter the SFTP server public key.
Target folder: Click the browse button and select the folder where
the uploaded file will be stored.

HDM-73R56070-11-0C Page 52 © Infinera 2022

OLR Commissioning Post-commissioning tasks

Target file name: Enter a name for the file to be uploaded. Choose a
unique name that is unmistakably correlated with this
NE. This will lessen the chance that the file could be
downloaded to the wrong NE in the future.
5 Click the Upload button to upload the file.
The upload status is displayed in a progress bar at the bottom of the window and also
in the MS Windows taskbar (the EM icon is colored with a green progress bar). You can
choose to automatically close the FTP Upload window after the upload is done by
selecting the appropriate check box.
The NE’s MIB contents are uploaded.

6.2 Opening the Troubleshooting Manual

This procedure provides the necessary steps to check if the Troubleshooting Manual
(TSMN) can be opened from the Element Manager. If the TSMN is not available in the
Element Manager, you are instructed in this procedure how to download the TSMN from
the Coriant Customer Portal website to a local drive in your PC and to perform the neces-
sary settings to launch the TSMN from the Element Manager.
To check whether the TSMN is available in the Element Manager, complete the following
steps:
1 In the EM main menu, select Help > Open Troubleshooting Manual... menu item.
a) If the Open Troubleshooting Manual... menu item is not available, please
continue with step 2.
b) If the TSMN is opened, this procedure is completed.
2 Download the docset from Coriant Customer Portal, please refer to the Documentation
Guide.
3 Unzip the docset file and store the TSMN on the local PC.
4 In the EM main menu, select File > Options... menu item.
The Options window is opened.
5 In the General tab, Troubleshooting manual location field, enter the location of the
TSMN.
6 Click Apply to confirm the settings.
7 In the EM main menu, select again Help > Open Troubleshooting Manual... menu
item.
The TSMN is opened.

HDM-73R56070-11-0C Page 53 © Infinera 2022

OLR Commissioning Glossary

7 Glossary
@CT @CT is a web-based craft terminal (that is, element manager) software which provides web
access to hiT 7300 network elements (NEs) in the customer network without the use of a
management system. It communicates via SNMP with the NEs and uses the FTPS for
upload/download of software or other data configuration (for example, log files).

10 Gigabit small A 10 Gigabit small Form-factor Pluggable (XFP) module is a swappable component
Form-factor Plugga- mounted at the faceplate of some types of hiT 7300 transponder cards. It acts as a
ble (XFP) boundary interface between the client signal and the DWDM line signal by performing the
bidirectional optical/electrical traffic conversion.

Add channel An active channel inserted (via multiplexing) into the DWDM transmission line at the head
end ONN NE of a pre-emphasis section.

Alarm An alarm is a management mechanism intended to inform the user that there is a standing
fault condition in the system.

Alarm log An alarm log provides a list of the alarms associated with a managed object/layer, and
provides the following information about each of the alarms:
• the identification of the affected object/layer
• the identification of the failed NE or the NE in which the failed unit resides
• the alarm severity
• the time the event occurred
• the indication whether the alarmed event is service affecting or not
• the location and the affected traffic

Alarm severity Each failure is assigned a severity. The following values are used:
• critical
• major
• minor
• warning
Element Manager (EM) can configure the severity which is assigned to each fault cause by
an alarm severity assignment profile. In addition, EM can specify that a fault cause shall not
be alarmed. These fault causes will be blocked, hence do not lead to any LED alarm indi-
cations, log entries or alarm reporting.

Alien wavelength A wavelength that originates on another vendor product, but is still allowed to be multi-
plexed into the aggregate line signal for transport as an optical channel by the hiT 7300
system.

Amplified Sponta- Amplified Spontaneous Emission (ASE) is produced when a laser gain medium is pumped
neous Emission to produce a population inversion. Feedback of the ASE by the laser's optical cavity may
produce laser operation if the lasing threshold is reached. Excessive ASE is an unwanted
effect in lasers, since it limits the maximum gain that can be achieved in the gain medium.
ASE enters the noise and affects directly the OSNR.

Amplifier card The line amplifier cards provide the optical signal amplification via a gain block with one or
more pump lasers, interstage access for dispersion compensation, a stage for connection
of external pumps, and gain control mechanisms.

Attenuator card A VOA card is a variable attenuator that can supply up to 8 EVOA channels. The VOA card
is applicable in pre-emphasis.

HDM-73R56070-11-0C Page 54 © Infinera 2022

OLR Commissioning Glossary

Automatic Laser Automatic Laser Shutdown (ALS) acts according with ITU-T G.664, by disabling the laser
Shutdown of the forward transmission side if the receiving line is inactive (that is, no signal is
detected). During service provisioning, the ALS checks for link restoration in small time
intervals and resumes the transmission (that is, enables the transmission laser) when the
line is restored.

Booster A Booster is an optical amplifier placed at the link section head end.

Booster-less card A booster-less line interface card is a unidirectional line interface card for the link direction
of a DWDM line interface without amplification functionality. The booster-less line interface
card can replace a booster amplifier card for short span applications.

C Form-factor Plug- A C Form-factor Pluggable (CFP) module is a swappable component mounted at the face-
gable plate of some types of hiT 7300 transponder cards. It acts as a boundary interface between
the client signal and the DWDM line signal by performing the bidirectional optical/electrical
traffic conversion.

C/DWDM filter pack C/DWDM filter pack is a passive filtering solution realized in a small filter pack shelf (SPF-
1) which allows up to 4 filter modules to be plugged-in.
The C/DWDM filter pack does not require power supply. It is completely independent from
the hiT 7300 system from a management point of view.

Card A card is a plug-in unit that occupies one (or multiple) shelf slots. Cards perform specific
electrical and/or optical functions within an NE.
Each card has a faceplate with information LEDs and, in most cases, several ports for inter-
connection of optical fibers and/or optical interfaces (for example, SFP).

Card faceplate All cards are equipped with individual faceplates in order to meet EMI/ESD requirements,
and ensure heat dissipation. The card faceplate contains LEDs, and in some cases optical
or electrical interfaces.

Card LEDs Card Light Emitting Diodes (LEDs) are luminous signals that can alert the user to:
• The state of the power supply.
• A card problem that requires card replacement.
• The existence of communication or equipment alarms.
• The presence or absence of traffic in the card.

Card slot A card slot is the insertion facility for a card in a shelf. Each card slot is designed for one or
several particular card types.
Mechanical coding elements make sure that each card can be fully inserted only into a card
slot that is suitable for the given card type. Therefore, fundamental shelf equipping errors
(which might cause hardware damage or fatal malfunctions) are impossible.

Chain network A chain network is a network topology characterized by a chain connection between several
NEs, that is, the optical signal is transmitted from one end-point NE to another but new
channels can be added, dropped or re-routed (to another optical path) along the optical
path.

Channel power Channel power monitor cards provide in-service monitoring of optical channel power levels
monitor card via an onboard Optical Spectrum Analyzer. The card has four input ports to monitor the
channel spectrum from four separate points in an NE.

Chromatic disper- Chromatic dispersion has the effect of spreading the signal pulse width, no longer allowing
sion an accurate recognition of a single “one” bit or a single “zero” bit.

HDM-73R56070-11-0C Page 55 © Infinera 2022

OLR Commissioning Glossary

Client interface A client interface is a transponder interface that faces the client side of the link. Contrast
with “line interface” which faces the transmission (line) side of the link.

Coarse Wavelength CWDM solution allows a simple and low-cost implementation of a passive optical multiplex-
Division Multiplex- ing system (with compact passive multiplexer modules), which can be used for data collec-
ing (CWDM) tion and aggregation of multiple client data from different remote locations within enterprise,
or small metropolitan networks.

Coherent Polariza- A digital modulation technique used in the transmission of optical signals with 40G and
tion - Quadrature 100G data rate. CP-QPSK combines quadrature phase shift keying (QPSK) with coherent
Phase Shift Keying detection which is sensitive to the phase as well as the amplitude of the optical wave
(CP-QPSK) offering ultra-narrow optical filtering capability. The coherent detection modulation format
uses 50 GHz channel spacing and works with intermixed 40G and 100G optical channels
in an existing optical network. CP-QPSK allows for DCM-free transmission and displays
high tolerance to polarization mode dispersion.

Commissioning Commissioning an network element (NE) is the process of taking an installed NE and
bringing it in to an operational state. The NE commissioning phase is performed after the
NE is installed and powered-up.

Commissioning Commissioning reports are generated by TransNet for each network element (NE) after the
report planning of an optical transmission network is completed. The commissioning reports
contain all necessary information for commissioning an NE and for service provisioning. To
achieve the system‘s well functioning it is recommended to perform all manual configuration
on the base of commissioning reports.

Controller card NE controller cards provide the central monitoring and controlling functions of the system,
as well as the MCF to operate the Q and QF Ethernet interfaces.
The controller card performs the following main functions: Fault Management, Performance
Management, Configuration Management, Security Management, Equipment Manage-
ment, Communication Management, Software Management (performing all software down-
loads, uploads, and software integrity functions) and controlling the NE alarm LEDs.

Core equipment hiT 7300 equipment which forms the DWDM infrastructure of the NE, such as amplifiers,
pumps and MUX/DEMUX structure of each nodal degree. (See also service-related
equipment).

Core Provisioning Provisioning mode in hiT 7300.

via NMS All core equipment and services are manually provisioned via the NMS, including internal
port connections and cross connections. Hence, the NEs are not dependant on NCFs to
configure relevant parameters for commissioning a link, adding services or expanding a
network. Some of these parameter values are specified in the commissioning reports.

CWDM patch-cord A CWDM patch-cord solution is provided by the add/drop patch-cord. The patch-cord is an
optical Y-cable with 3 LC/PC connectors, which allows the add/drop of a single CWDM
channel.

Data Communica- A DCN domain interconnects several NEs for the purpose of network management. The
tion Network (DCN) communication is established via the Optical Supervisory Channel (OSC) of the optical
links and an Ethernet/L2 switching network implemented by the NEs.

Dense Wavelength DWDM is a technology which simultaneously places a large number of optical signals (in
Division Multiplex- the 1550 nm band) on a single optical fiber.
ing (DWDM)

HDM-73R56070-11-0C Page 56 © Infinera 2022

OLR Commissioning Glossary

Differential Phase A digital modulation technique used in the transmission of optical signals.
Shift Keying (DPSK) DPSK transmits data by modulating the phase of a signal. The phase is changed if the
current data bit is different from its predecessor. At a receiving end, phase changes are
detected by comparing the phase of each signal element with the phase of a preceding
signal element.

Dispersion Compen- DCM cards counteract the chromatic dispersion of the signal traveling through the optical
sation Module (DCM) fiber.
card

Drop channel An active channel extracted (via demultiplexing) from the DWDM transmission line at the
tail end ONN NE of a pre-emphasis section.

Dual Protection Card A dual protection channel protection card is an active card with a double bidirectional optical
channel protection circuit. The card can provide client side protection, line side protection,
OTSP or OMSP depending of the planned network scenario.

Electrical Energy Electrical energy source is part of the electrical environment classification and, according
Source (ES) to IEC 62368-1, is divided into three classes:
• ES1: class 1 electrical energy source with levels not exceeding ES1 limits under normal
operating conditions, and abnormal operating conditions that do not lead to a single
fault condition, and not exceeding ES2 limits under single fault conditions. ES1 may be
accessible to an ordinary person (“user” in IEC 60950-1). Effects: not painful on the
body; ignition of combustible materials is not likely.
• ES2: class 2 electrical energy source with levels not exceeding ES2 limits under normal
operating conditions, abnormal operating conditions, and single fault conditions, but is
not ES1. ES2 may be accessible to an instructed person (“someone under supervision”
in IEC 60950-1). Effects: painful on the body, but not an injury; ignition of combustible
materials is possible, but with limited growth and spread of fire.
• ES3: class 3 electrical energy source with levels exceeding ES2 limits for prospective
touch voltage and touch current. The energy in ES3 may cause harmful physiological
effects under contact with a body part. Parts and circuits classed ES3 may be accessi-
ble to a skilled person (“service person” in IEC 60950-1). Effects: injury to the body;
ignition of combustible materials is likely and with rapid growth and spread of fire.

Element Manager hiT 7300 EM enables the user to perform operation, administration and maintenance tasks
(EM) with the hiT 7300 system in a GUI environment.

Engineering Order The EOW interface is located at the NE controller cards and is used to establish conference
Wire (EOW) and selective calls from one NE to another NE(s) using a handset.

Erbium Doped Fiber An EDFA is an optical fiber doped with a rare earth element (Erbium), which can amplify
Amplifier (EDFA) laser light in the 1550 nm region when pumped by an external laser source.

Error correction Error correction in a DWDM system is achieved with FEC and S-FEC functions. These func-
tions ensure the detection and correction of data errors carried by a channel or channels.

Ethernet Ethernet is a family of frame-based computer networking technologies for LANs. It defines
a number of wiring and signaling standards for the physical layer, through means of network
access at the MAC/Data Link Layer, and a common addressing format.

Express channels An express channel is an active channel that travels over an entire pre-emphasis section,
from ONN to ONN.

External pump card An external pump card can be connected to an amplifier card to increase its normal output
power, which is sometimes needed for longer spans, different fiber types.

HDM-73R56070-11-0C Page 57 © Infinera 2022

OLR Commissioning Glossary

Fan filter An fan filter is a one-piece replaceable element mounted in the shelf to protect the shelf
from ingesting environmental dust or other airborne contaminants.

Fan unit Each shelf is equipped with one or more fan units that provide cooling airflow for the cards.

Fault management Fault management reports all hardware and software malfunctions within an NE, and
monitors the integrity of all incoming and outgoing digital signals.

File Transfer FTP is a network protocol used to transfer files from one computer to an NE and vice-versa
Protocol (FTP) through the network.

Filter card Filter cards act as multiplexers/demultiplexers by providing the primary wave division or
aggregation of all the transponder signals and allowing access to a particular set of wave-
lengths from an optical fiber while passing the remaining wavelengths.

Flexible DWDM grid Flexible DWDM grid (flexi-grid) is a DWDM wavelength assignment plan with individually
definable frequency slot widths for each DWDM channel. Each DWDM channel is assigned
with a defined frequency slot width which may be different from the remaining DWDM
channels allocated in the frequency grid of the optical spectrum.

Forward Error Cor- FEC is a technique that optimizes signal performance by providing a better Optical Signal-
rection (FEC) to-Noise Ratio (OSNR) tolerance at the transponders, that is, FEC enables the system to
withstand more signal noise.
FEC is a coding algorithm that enables bit error detection and correction. FEC is a "forward"
scheme, that is, the receiver receives only the information needed to detect and correct bit
errors and never requests a re-transmission.

Frequency Frequency is a physical attribute of a wave (for example, an optical wave), defined as the
number of wave cycles per time unit. The frequency is directly related to the wavelength.

Friendly wavelength A wavelength that originates on another Coriant product, such as mTera UTP, 7100
Nano/Pico, etc., but is still allowed to be multiplexed into the aggregate line signal for trans-
port as an optical channel by the hiT 7300 system.

Gain control Gain control of hiT 7300 is provided by the EDFA modules in the line amplifier cards. Gain
control ensures a sufficiently fast response to transients and keeps constant the gain
between input and output of the EDFA line amplifier card.

Hairpinning Unlike a loopback (where traffic is sent to the same port it is received from), Hairpinning
refers to a use case where an ODU unprotected bidirectional Cross Connection is created
between two ODU TPs of different Client Ports of a muxponder card.

Interstage Loss Most hiT 7300 amplifier cards feature two ports to connect an “interstage” device (typically
a DCM). Interstage loss is the power loss experienced by the optical signal passing through
the interstage device.

Laser A laser is a device that generates an intense narrow beam of light by stimulating the
emission of photons from excited atoms or molecules.

Laser safety Laser safety rules are a group of mechanisms and actions necessary to protect all users
from harmful laser light emissions.

Laser Safety Bus hiT 7300 LSB rings provide a reliable communication between cards to ensure a safe NE
(LSB) operation via Automatic Power Shutdown (APSD) and Automatic Power Reduction Mode
(APRM) functions.

Line interface A line interface is a transponder interface that faces the line side of the link. Contrast with
“client interface” which faces the client equipment side of the link.

HDM-73R56070-11-0C Page 58 © Infinera 2022

OLR Commissioning Glossary

Link section See Optical Multiplex Section.

Long Haul (LH) hiT 7300 LH segment is a DWDM application characterized by a reach of more than 500
km and up to 1200 km.

Master agent Software component in multicontroller NEs that runs on the NE’s main controller card. The
master agent provides management interfaces and global NE functionality of the multicon-
troller NE.

Media Channel It provides the tunnel between two add/drop nodes of an optical network and is defined by
(MCh) the path through the network between these two add/drop nodes and by the frequency slot
which provides the bandwidth for the transport of one or several carriers (OTSi).

Mesh network A mesh network is a network topology which is characterized by the constant routing of the
optical channel between the NEs. It allows a continuous connection and a reconfiguration
around a broken or blocked optical path by "hopping" from NE to NE until the destination is
reached. A mesh network whose NEs are all connected to each other is a fully connected
network.

Metro hiT 7300 Metro segment is a DWDM application characterized by short path lengths of up
to 200 km.

MPB communica- The RMH07, 1RU and 2RU Long Reach Transport Series from MPB Communications
tions consists of amplifiers designed to transmit and receive signals over fiber optic links from
100 to more than 400 km in a single span using SON NEs.

Multicontroller A multicontroller NE is an NE with several controller cards, where a dedicated one of them
Network Element acts as the master agent, the other ones as subagents.
Only ONNs can be multicontroller NEs.

Network Craft NCT is a network management craft terminal (that is, element manager) software which is
Terminal (NCT) used for either local or remote network management.

Network Element A network element (NE) is a self-contained logical unit within the network. The NE can be
(NE) uniquely addressed and individually managed via software.
Each NE consists of hardware and software components to perform given electrical and
optical functions within the network.

Network Element A Network Element Configuration File (NCF) is a file to configure a network element (NE).
Configuration File It is generated by TransNet for each NE after the planning of an optical transmission
(NCF) network is completed. The configuration of the NE is performed automatically by download-
ing and swapping the NCF to the NE. The download and swap of NCFs can be done either
individually to each NE or simultaneously to all NEs using an NCF Archive file for distribu-
tion.

Network Manage- The network management layer includes all the required functions to manage the optical
ment network in an effective and user-friendly way, such as the visualization of the network topol-
ogy, creation of services, and correlation of alarms to network resources.

Network topologies A topology of a network is defined by the list of NEs included in the network and the list of
links that connect those NEs (for example, point-to-point, chain, ring, and so on).

Nodal degree The nodal degree of an NE is the number of NEs that are directly connected to the NE.

TransNet Planning of a hiT 7300 network is done by the TransNet tool. TransNet is a sophisticated
software simulation tool developed specifically for designing and/or upgrading optical

HDM-73R56070-11-0C Page 59 © Infinera 2022

OLR Commissioning Glossary

DWDM networks with hiT 7300. It runs on PCs using Microsoft Windows operating
systems.

Non-Return to Zero A data encoding technique used to transmit digital data over the line interface. In telecom-
(NRZ) munications, a Non-Return to Zero (NRZ) line code is a binary code in which 1's are repre-
sented by one significant condition (usually a positive voltage) and 0's are represented by
some other significant condition (usually a negative voltage), with no other neutral or rest
condition.

Optical Add-Drop OADM architectures refer to the capability of an OADM NE to perform some optical tasks
Multiplexer (OADM) within the hiT 7300 network. In hiT 7300 the following OADM architectures are available:
architectures • Terminal
• Flexible
• FullAccess
• Reconfigurable
• Photonic Cross Connect (PXC)

Optical Add-Drop An OADM is an optical node NE used for multiplexing and routing different optical channels
Multiplexer (OADM) of into or out of an optical fiber. An OADM NE is generally used for the construction of a
ring-based network. "Add" and "drop" refer to the capability of the NE to add one or more
channels to an existing DWDM signal, and/or to drop one or more channels and/or routing
those signals to another optical path.

Optical Channel Is an optical entity consisting of a Media Channel (MCh) and one Optical Tributary Signal
(OCh) (OTSi).

Optical channel Optical channel control manages the optical channel state information through the entire
control optical path. The optical channel control activates mechanisms to recover the normal oper-
ation of the optical path in a link failure scenario, or activate mechanisms to manage oper-
ations in case of an optical channel upgrade/ downgrade scenario. The activation of such
mechanisms, depends on the optical channel state information monitored on each NE. The
transmission of this information along the optical path, between NEs, is provided by the
Optical Supervisory Channel (OSC).

Optical channel pro- An optical channel protection card is a passive card which contains 6 optical splitters. Three
tection card of those splitters act as combiners to switch the traffic together with the transponder cards.
The remaining three are used for bridging the traffic for protection.
Up to three protection groups can be created and managed by the optical channel protec-
tion card (that is, three pairs of client interfaces).

Optical Line An Optical Line Repeater is an NE which is used for optical signal amplification and disper-
Repeater (OLR) sion compensation.

Optical link control Optical link control optimizes and maintains the operation of individual link sections and pre-
emphasis sections. Most of the optical link control functions are executed by the CCEP-2
card, and the time-critical functions are executed by the line amplifier cards.

Optical Multiplex An optical multiplex section (or link section) is the optical segment from the booster of a of
Section (OMS) a Wavelength Division Multiplexing Line Termination (WLT)/ONN to the preamplifier of the
next adjacent WLT/ONN.

Optical Network An ONN is an NE where the incoming channels are either dropped or routed to a line in a
Node (ONN) different direction, outgoing channels can also be added locally. Apart from multiplexing
and demultiplexing an ONN NE implements optical or 3R signal regeneration and disper-
sion compensation.

HDM-73R56070-11-0C Page 60 © Infinera 2022

OLR Commissioning Glossary

Optical path The path followed by an optical channel from the first multiplexer to the last demultiplexer.

Optical Signal to OSNR is the ratio of an optical signal power to the noise power in the signal.
Noise Ratio (OSNR)

Optical Spectrum An Optical Spectrum Analyzer is a device that measures properties of an optical signal
Analyzer (OSA) within a defined spectrum.

Optical Supervisory An Optical Supervisory Channel is a supervisory channel that is transmitted/received by the
Channel (OSC) line amplifier cards. It provides all the network management communication required to set-
up and maintain a DWDM system configuration, fault management, performance monitor-
ing, and software maintenance.

Optical Transmis- An Optical Transmission Section (or span) is any fiber segment between two adjacent
sion Section (OTS) amplifiers (that is, between two NEs).

Optical Tributary It represents the modulated carrier and is characterized by a central frequency.
Signal (OTSi)

Pass-through Active channels patched-through from the DWDM transmission line of a pre-emphasis
channels section to the DWDM transmission line of the next pre-emphasis section without being
locally dropped or added.

Pass-through traffic See Pass-through channels.

Performance man- Performance monitoring and signal quality analysis provide information for detecting and
agement alerting, a cause that could lead to a degraded performance before a failure is declared.

Point-to-point A point-to-point network is a network topology characterized by a connection between two

network end-point NEs, that is, the optical signal is transmitted from one end-point to another end-
point without add or drop of channels. Applications where the span length is considerably
big may require an amplification/regeneration (done by OLR NEs) along the optical path.

Power Distribution A Power Distribution Panel is the device responsible for the power distribution of all the
Panel (PDP) racks of an NE. It contains fuses (or circuit breakers) to protect all the dual-redundant power
supplies connected to each shelf in the rack.

Power meter An optical power meter is the equipment recommended to use in case of single optical
channel power measurement.

Power tilt Spectrum power tilt occurs when a flat DWDM signals travel through transmission fiber.
Due to stimulated Raman scattering, shorter wavelength channels will pump longer wave-
length channels, and so transfer their energy to longer wavelength channels.

Power User User mode which is necessary to set critical parameters of hiT 7300 at Core Provisioning
via NMS. The Power User mode is only allowed for the user groups “Operation”, “Configu-
ration”, and “Administration” and requires a specific password.

Preamplifier Preamplifier is an optical amplifier placed at the link section tail end.

Pre-emphasis The Pre-emphasis method is applied to pre-emphasis sections, and is used to optimize the
optical link by means of optical power adjustment (manual or automatic).

Pre-emphasis The pre-emphasis method is applied to pre-emphasis sections and is used to optimize the
method optical link by means of optical power adjustment.

Pre-emphasis A pre-emphasis section is the optical segment from the booster of a WLT/ONN to the pre-
section amplifier of the next adjacent WLT/ONN.

HDM-73R56070-11-0C Page 61 © Infinera 2022

OLR Commissioning Glossary

Provisioning mode Mode, which determines how the hiT 7300 equipment and services are setup. In hiT 7300
three different provisioning modes are distinguished: Service Provisioning via NCF,
Service Provisioning via NMS, and Core Provisioning via NMS.

Pump laser A pump laser is a laser with a wavelength different from the signal laser, used as the energy
source for signal amplification.

Rack A rack is the main unit of the hiT 7300, it carries all system devices in a specific arrange-
ment. The most important elements placed in the rack are the shelves and the Power Dis-
tribution Panel (PDP).

Raman amplification The basis of Raman amplification is the energy scattering effect called Stimulated Raman
Scattering (SRS). The SRS is a non-linear effect inherent to the fiber itself. SRS involves a
transfer of power from a signal at a higher frequency (lower wavelength) to one at a lower
frequency (higher wavelength), due to inelastic collisions in the fiber medium. It can be used
for optical amplification, in which the higher frequency laser serves as a pump source,
amplifying the lower frequency wave carrying the actual traffic signal to be amplified.

Raman pump card Raman pump cards must be inserted at the receiving line interface. They are normally used
in long span applications to ensure that the same amplifier spacing can be achieved with
lower EDFA output power per channel, allowing a higher total number of channels.
For certain links where the non-linear effects limit an increase in the number of spans, a
channel power reduction decreases the non-linear effects, and therefore allows a higher
number of spans. Raman amplifiers are preferably applied to bridge single extra long
spans.

Regenerator A regenerator is a device used to extend the reach of fiber-optic traffic communications, by
compensating the attenuation and the distortion of the optical signal.
The regenerator converts the received optical signal to an electrical signal, processes it,
reconverts it to an optical signal and retransmits it.

Regional hiT 7300 Regional segment is a DWDM application characterized by path lengths starting
at 200 km and for high traffic volumes. These networks are often used as regional collector
networks to feed into LH portions of the network. Regional DWDM networks have typical
path lengths of up to 500 km.

Remote Optically A ROPA module is a passive unit with a Erbium doped fiber to amplify the optical signal. It
Pumped Amplifier is placed in the transmission cable to extend the long single span length.
(ROPA)

Ring network A ring network is a network topology in which each NE connects to exactly two other NEs,
forming a circular optical path for signals (that is, a ring).

Security manage- Security Management controls the individual access to particular NE functions via the
ment network management system and/or via a craft terminal, using a hierarchical security man-
agement user ID, and password concept.

Shelf The rack-mountable housing into which cards are installed. The shelf contains terminals for
connection of the power supply voltage that is distributed to each card. Major components
of each shelf are card slots, backplane, LEDs, Connector Panel, Fan Unit(s) and Fan Filter.

Service Provisioning Provisioning mode in hiT 7300.

via NCF All core equipment and services are provisioned via NE-specific Network Element Config-
uration Files (NCFs). In this mode, an operator cannot provision shelves, cards, internal
port connections or cross connections via the Network Management System (NMS). NCFs

HDM-73R56070-11-0C Page 62 © Infinera 2022

OLR Commissioning Glossary

must be downloaded and swapped when commissioning an ONN/Optical Line Repeater

(OLR), adding new services (channel upgrade) or expanding an existing network.

Service Provisioning Provisioning mode in hiT 7300.

via NMS The core equipment is provisioned by downloading and swapping NCFs, while services
are manually provisioned via the NMS.
When adding new services or expanding an existing network, the relevant line cards, cross
connections and internal port connections between line cards and multiplexers/demultiplex-
ers are provisioned via the NMS.

Service-related hiT 7300 equipment which feed wavelengths into the optical link. Transponders, muxpo-
equipment nders and regenerators are service-related equipment. (See also core equipment).

Simple Network SNMP is used in network management systems to monitor network-attached devices for
Management conditions that warrant administrative control. It consists of a set of standards for network
Protocol (SNMP) management, including an application layer protocol, a database schema, and a set of data
objects.

Single-controller A single-controller NE is an NE with one controller card.

Network Element

Small Form-Factor An SFP module is a swappable component mounted at the front panel of some types of hiT
Pluggable (SFP) 7300 transponder cards. It acts as a boundary interface between the client signal and the
DWDM line signal by performing bidirectional optical/electrical traffic conversion.

Software manage- Software management performs all software downloads, uploads, and software integrity
ment functions.

Span See Optical Transmission Section.

Span loss Span loss is the optical power loss measured in dBs between two adjacent NEs.

Standalone Optical A Standalone Optical Node (SON) is a DWDM NE that can be used in passive DWDM (for
Node (SON) example, point-to-point and remote transponder solutions) and long single span applica-
tions.

Stimulated Brillouin Stimulated Brillouin Scattering (SBS) is the interaction of photons and optical phonons
Scattering (SBS) (acoustic phonons). The latter are the particles, which can be assigned to vibrations of the
array of atoms and electrons. The SBS acts in backward direction and it is especially
important when there is bidirectional transmission. In this case, a channel interferes with
itself causing significant distortion and loss in forward direction.

Subagent Software component in multicontroller NEs that runs on NE controller cards and that
controls a subsystem (= a set of assigned shelves and cards therein).

Subsystem A subsystem is a set of shelves and cards in multicontroller NE that is controlled by a sub-
agent. All subagents within a multicontroller NE are controlled by the master agent.

Tandem Connection TCMs are configurable parameters (via Element Manager) of the transponders. They
Monitoring (TCM) provide a Performance Management of all the Optical Transport Network (that is, end-to-
end connection) or specific sections only and implement an Optical channel Data Unit
(ODU) termination provisioned to support up to six TCM levels.

TNMS TNMS is an integrated solution designed for large, medium and small size networks. It
supports NEs with DWDM, OTH, SDH, PDH, Ethernet in line, star, ring and mesh network
configurations. TNMS can be used to manage networks in the access, edge, metro, core
and backbone levels.

HDM-73R56070-11-0C Page 63 © Infinera 2022

OLR Commissioning Glossary

Telemetry Interface TIF sensors (inputs) and TIF actors (outputs) can be found in the NEs’ controller cards as
(TIF) a separate module called TIF module or on a separate card named CTIF-1. TIF inputs and
outputs are used for traditional user-defined “housekeeping” purposes (for example, fire
alarm, over temperature alarm, door-open alarm, lights, air conditioning, and so on).

Trail Trace Identifier TTI is a transponder card parameter (configurable via Element Manager) of which is used
(TTI) to verify correct cabling or correct Tandem Connection Monitoring (TCM) configuration. The
basic principle is that specific overhead bytes are reserved for Trace Messages of the
user's choosing. By specifying the Actually Sent (transmitted) and the Expected (received)
trace messages, the system can automatically verify that fiber connections have been
made as intended. This is accomplished by comparing the expected Trace Message to that
actually received. If they differ, an alarm is raised, alerting personnel of the incorrect con-
nections.

Transponder card A transponder card receives an optical input signal and converts it to an optical output
signal suitable for DWDM multiplexing and transmission.

Transponder Loopbacks are diagnostic tests that can be activated via Element Manager. Loopbacks
loopback return the transmitted signal back to the sending device after the signal has passed across
a particular link. The returned signal can then be compared to the transmitted one. Any dis-
crepancy between the transmitted and the returned signal helps to trace faults.

UDCM tray An UDCM tray is a mechanical shelf mounted in a rack, which can hold up to 4 UDCMs.

Ultra Long Haul hiT 7300 ULH segment is a DWDM application characterized by long path lengths of up to
(ULH) 1600 km.

Unidirectional Dis- Unidirectional Dispersion Compensation Modules (UDCMs) provide a dispersion compen-
persion Compensa- sation of the DWDM signal. They are not supplied as shelf plug-in cards, being mounted in
tion Module (UDCM) a specific plug-in box inside the UDCM tray.
UDCMs are available in "single-height" UDCM and "double-height" UDCM. A blank
(dummy) UDCM is also available to be installed in those positions that do not have an actual
UDCM installed.

User Channel hiT 7300 user channels are used for bidirectional connections between NEs via the OSC
or GCC0, providing the customer with a point-to-point Ethernet connection for specific data
network or remote access to NEs not reachable via DCN.

VOA See Attenuator Card.

Wavelength Wavelength is a physical attribute of a wave (for example, an optical wave), defined as the
distance between corresponding points of two consecutive wave cycles.
The wavelength is directly related to the frequency of the wave.

Wrist strap A grounded anti-static strap worn on the wrist to prevent electrostatic discharge that may
damage electronic equipment.

HDM-73R56070-11-0C Page 64 © Infinera 2022

OLR Commissioning Abbreviations

8 Abbreviations
@CT Web-based Craft Terminal

3R Re-amplification, Re-shaping, Re-timing

AC Alternating Current

ADF Armored fiber Distribution Frame

AES Advanced Encryption Standard

AFG Air Flow Guide

AIS Alarm Indication Signal

ALS Automatic Laser Shutdown

AMP Asynchronous Mapping Procedure

ANSI American National Standards Institute

APC Advanced Power Control

APD Avalanche Photodiode

APR Address Resolution Protocol

APRM Automatic Power Reduction Mode

APS Application Program System

APSD Automatic Power Shutdown

ASE Amplified Spontaneous Emission

ASON Automatic Switched Optical Network

AWG Arrayed Waveguide Grating

B&S Broadcast & Select

BBE Background Block Error

BDI Backward Defect Indication

BER Bit Error Rate

BIP Bit Interleaved Parity

BMP Bit-synchronous Mapping Procedure

BOL Begin Of Life

BPDU Bridge Protocol Data Unit

Bps Bytes per second

bps Bits per second

C-AD Colorless Add/Drop

C/DWDM Coarse/Dense Wavelength Division Multiplexing

HDM-73R56070-11-0C Page 65 © Infinera 2022

OLR Commissioning Abbreviations

CAPEX Capital Expenditure

CARP Common Address Redundancy Protocol

CBS Committed Burst Size

CCAMP Common Control And Measurement Plane

CCM (1) Card Control Module

(2) Continuity Check Message

CD (1) Chromatic Dispersion

(2) Colorless Directionless

CD-AD Colorless Directionless Add/Drop

CD-ROM Compact Disc - Read-Only Memory

CD/FD-AD Colorless Directionless Add/Drop in combination with Fixed Frequency Directionless

Add/Drop

CDC Colorless Directionless Contentionless

CDC-AD Colorless Directionless Contentionless Add/Drop

CE Communauté Européenne

CEF Capability Extension File

CFM Connectivity Fault Management

CFP C Form-factor Pluggable

CIR Committed Information Rate

CLI Command Line Interface

CML Command and Message List

CMS Control plane Management Information Base Stub

COPA Connector Panel

COS Class Of Service

CP-QPSK Coherent Polarization - multiplexed Quadrature Phase Shift Keying

CPE Customer Premises Equipment

CSI Customer Service Instance

CST Common Spanning Tree

CT Craft Terminal

CTP Connection Termination Point

CV Code Violations

CVID Customer Virtual Local Area Network Identifier

CWDM Coarse Wavelength Division Multiplexing

HDM-73R56070-11-0C Page 66 © Infinera 2022

OLR Commissioning Abbreviations

DC (1) Direct Current

(2) Dispersion Compensation

DCF Dispersion Compensation Fiber

DCM Dispersion Compensation Module

DCN Data Communication Network

DEI Drop Eligible Indicator

DES Data Encryption Standard

DGD Differential Group Delay

DHCP Dynamic Host Configuration Protocol

DLF Destination Lookup Failure

DLI Delay Line Interferometer

DNS Domain Name Service

DOP Degree Of Polarization

DPSK Differential Phase Shift Keying

DSCP Differentiated Services Code Point

DSF Dispersion Shifted Fiber

DSLAM Digital Subscriber Line Access Multiplexer

DSR Dynamic Source Re-routing

DTMF Dual Tone Multifrequency

DWDM Dense Wavelength Division Multiplexing

E-LAN Ethernet Local Area Network

E-Line Ethernet Line

E-NNI External Network-Network Interface

E-Tree Ethernet Tree

EAM Electro Absorption Modulator

EBP Earth Bonding Point

EBS Excess Burst Size

EDF Erbium Doped Fiber

EDFA Erbium Doped Fiber Amplifier

EFEC Enhanced Forward Error Correction

EGB Elektrostatisch Gefährdetes Bauteil (electrostatically sensitive device)

EIR Excess Information Rate

EM Element Manager

HDM-73R56070-11-0C Page 67 © Infinera 2022

OLR Commissioning Abbreviations

EMC Electromagnetic Compatibility

EMI Electromagnetic Interference

EOCI External Optical Connection Indicator

EOL End Of Life

EOW Engineering Order Wire

EPC Enhanced Power Control

EPL Ethernet Private Line

ERO Explicit Route Object

ES (1) Errored Seconds

(2) Electrical Energy Source

ESD (1) Eletrostatic Discharge

(2) Electrostatically Sensitive Device

ESNR Electrical Signal-to-Noise Ratio

ETS European Telecommunications Standard

ETSI European Telecommunications Standards Institute

EVC Ethernet Virtual Connection

EVP-LAN Ethernet Virtual Private Local Area Network

EVPL Ethernet Virtual Private Line

EWS East West Separation

F-AD Fixed Frequency Add/Drop

FBG Fiber Bragg Grating

FC Fibre Channel

FD-AD Fixed Frequency Directionless Add/Drop

FDB Forwarding Database

FDI Forward Defect Indication

FEC Forward Error Correction

FIT Failures In Time

FPGA Field Programmable Gate Array

FTP File Transfer Protocol

FTPS File Transfer Protocol Secure

G-AIS Generic Alarm Indication Signal

GARP Generic Attribute Registration Protocol

GB Gigabyte

HDM-73R56070-11-0C Page 68 © Infinera 2022

OLR Commissioning Abbreviations

Gb Gigabit

GbE Gigabit Ethernet

GBps Gigabytes per second

Gbps Gigabits per second

GCC General Communication Channel

GFEC Generic Forward Error Correction

GFP Generic Framing Procedure

GFP-T Generic Framing Procedure - Transparent

GMP Generic Mapping Procedure

GMPLS Generalized Multiprotocol Label Switching

GMT Greenwich Mean Time

GNE Gateway Network Element

GPI Generic Physical Interface

GRE Generic Routing Encapsulation

GUI Graphical User Interface

GVRP Generic Attribute Registration Protocol (GARP) Virtual Local Area Network (VLAN)
Registration Protocol

HTTP Hypertext Transfer Protocol

HU Height Unit

HW Hardware

I-NNI Internal Network-Network Interface

I2C Inter-Integrated Circuit

ICMP Internet Control Message Protocol

ID Identifier

IEC International Electrotechnical Commission

IGMP Internet Group Management Protocol

ILAN Inter-shelf Local Area Network

IP Internet Protocol

ISL Interstage Loss

ITIM Internal Trace Identifier Mismatch

ITTI Internal Trail Trace Identifier

JRE Java Runtime Environment

KB Kilobyte

HDM-73R56070-11-0C Page 69 © Infinera 2022

OLR Commissioning Abbreviations

Kb Kilobit

KBps Kilobytes per second

Kbps Kilobits per second

L2 Layer 2

LA Line Amplifier

LACP Link Aggregation Control Protocol

LAG Link Aggregation Group

LAN Local Area Network

LBM Loopback Message

LC Lucent Connector

LEAF Large Effective Area Fiber

LED Light Emitting Diode

LH Long Haul

LLDP Link Layer Discovery Protocol

LOM List Of Material

LOS Loss Of Signal

LSB Laser Safety Bus

LSP Label Switch Path

LSR Label Switch Router

LWL Lichtwellenleiter (optical fiber)

MAC Media Access Control

MAN Metropolitan Area Network

MB Megabyte

Mb Megabit

MBps Megabytes per second

Mbps Megabits per second

MCF Message Communication Function

MCh Media Channel

MD5 Message Digest 5

MDF Medium Dispersion Fiber

MEF Metro Ethernet Forum

MEMS Microelectro Mechanical Systems

HDM-73R56070-11-0C Page 70 © Infinera 2022

OLR Commissioning Abbreviations

MEP Maintenance association End Point

MIB Management Information Base

MIP Maintenance domain Intermediate Point

MLSE Maximum Likelihood Sequence Estimator

MPBC MPB Communications Inc.

MPE Maximum Permissible Exposure

MPLS Multiprotocol Label Switching

MS-AIS Multiplex Section Alarm Indication Signal

MSA Multisource Agreement

MSI Multiplex Structure Identifier

MST Multiple Spanning Tree

MSTP Multiple Spanning Tree Protocol

MTU Maximum Transmission Unit

MZM Mach-Zehnder Modulator

NAPT Network Address Port Translation

NCF Network Element Configuration File

NCT Network Craft Terminal

NE Network Element

NEALI Network Element Alarm Interface

NMS Network Management System

NNI Network-Network Interface

NRZ Non-Return to Zero

NT Network Termination

NTP Network Time Protocol

NZDSF Non-Zero Dispersion Shifted Fiber

OA&M Operation, Administration and Maintenance

OADM Optical Add-Drop Multiplexer

OCh Optical Channel

OChP Optical Channel Protection

ODF Optical Distribution Frame

ODU Optical channel Data Unit

OEM Original Equipment Manufacturer

HDM-73R56070-11-0C Page 71 © Infinera 2022

OLR Commissioning Abbreviations

OLR Optical Line Repeater

OMS Optical Multiplex Section

OMSP Optical Multiplex Section Protection

ONN Optical Network Node

ONN-I Optical Network Node - Interconnect

ONN-I80 Optical Network Node - Interconnect 80 channels

ONN-R Optical Network Node - Reconfigurable

ONN-R2 Optical Network Node - Reconfigurable 2

ONN-R80 Optical Network Node - Reconfigurable 80 channels

ONN-T Optical Network Node - Terminal

ONN-T80 Optical Network Node - Terminal 80 channels

ONN-X Optical Network Node - Cross connect

ONN-X80 Optical Network Node - Cross connect 80 channels

ONN-X96 Optical Network Node - Cross connect 96 channels

OOB Out Of Band

OPEX Operational Expenditure

OPU Optical channel Payload Unit

OS Operating System

OSA Optical Spectrum Analyzer

OSC Optical Supervisory Channel

OSNR Optical Signal-to-Noise Ratio

OSPF Open Shortest Path First

OSPF-TE Open Shortest Path First - Traffic Engineering

OSU Optical Supervisory Unit

OTDR Optical Time Domain Reflectometer

OTH Optical Transport Hierarchy

OTN Optical Transport Network

OTS Optical Transmission Section

OTSi Optical Tributary Signal

OTSP Optical Transmission Section Protection

OTU Optical Transport Unit

PC (1) Permanent Connection

(2) Personal Computer

HDM-73R56070-11-0C Page 72 © Infinera 2022

OLR Commissioning Abbreviations

(3) Physical Contact

PCP Priority Code Point

PCS Physical Coding Sublayer

PDH Plesiochronous Digital Hierarchy

PDL Polarization Dependent Loss

PDP Power Distribution Panel

PDU Packet Data Unit

PHF Power High Failure

PIU Plug-In Unit

PLC Planar Light-wave Circuit

PLF Power Line Filter

PM Performance Management

PMD Polarization Mode Dispersion

PMP Performance Monitoring Point

PRBS Pseudo Random Binary Sequence

PSCF Pure Silica Core Fiber

PSU Power Supply Unit

PTP Physical Termination Point

PXC Photonic Cross Connect

QAM Quadrature Amplitude Modulation

QL Quality Level

QoS Quality of Service

RAM Random Access Memory

ROADM Reconfigurable Optical Add-Drop Multiplexer

ROPA Remote Optically Pumped Amplifier

RRO Recorded Rout Object

RSFEC Reed-Solomon Forward Error Correction

RSTP Rapid Spanning Tree Protocol

RSVP Resource Reservation Protocol

RSVP-TE Resource Reservation Protocol - Traffic Engineering

SFEC Standard Forward Error Correction

SAPI Source Access Point Identifier

HDM-73R56070-11-0C Page 73 © Infinera 2022

OLR Commissioning Abbreviations

SBS Stimulated Brillouin Scattering

SC Switched Connection

SCN Signaling Communication Network

SDH Synchronous Digital Hierarchy

SEFS Severely Errored Framing Seconds

SELV Safety Extra Low Voltage

SES Severely Errored Seconds

SFP Small Form-factor Pluggable

SINTF Stable Interface

SLA Service Level Agreement

SLH Span Loss High

SLL Span Loss Low

SLP Service Level Policy

SNC/I Subnetwork Connection protection with Inherent monitoring

SNC/N Subnetwork Connection protection with Non-intrusive monitoring

SNC/S Subnetwork Connection protection with Sublayer monitoring

SNCP Subnetwork Connection Protection

SNMP Simple Network Management Protocol

SON Standalone Optical Node

SONET Synchronous Optical Network

SPC (1) Soft Permanent Connection

(2) Standard Power Control

SPM Self Phase Modulation

SRLG Shared Risk Link Group

SRS (1) Stimulated Raman Scattering

(2) Single Row Shelf

SSMF Standard Single-Mode Fiber

STP Spanning Tree Protocol

SU System Unit

SVID Service Virtual Local Area Network Identifier

SW Software

TB Terabyte

Tb Terabit

HDM-73R56070-11-0C Page 74 © Infinera 2022

OLR Commissioning Abbreviations

TBps Terabytes per second

Tbps Terabits per second

TCA Threshold Crossing Alert

TCM Tandem Connection Monitoring

TCP Transmission Control Protocol

TDC Tunable Dispersion Compensation

TDM Time Division Multiplexing

TE Traffic Engineering

TID Target Identifier

TIF Telemetry Interface

TIM Trace Identifier Mismatch

TL Topological Link

TLS Transparent Local Area Network Service

TMN Telecommunications Management Network

TNA Transport Network Assigned

TP Termination Point

TPID Tag Protocol Identifier

TSCh Transient Suppression Channel

TSL Transitional Link

TTI Trail Trace Identifier

TTP Trail Termination Point

TTL Time To Live

UAS Unavailable Seconds

UDCM Unidirectional Dispersion Compensation Module

UDP User Datagram Protocol

UL Underwriters Laboratories

ULH Ultra Long Haul

UNI User-Network Interface

UNI-P User-Network Interface - Port-based

UNI-S User-Network Interface - Service-based

UPI User Payload Identifier

USM User-based Security Model

HDM-73R56070-11-0C Page 75 © Infinera 2022

OLR Commissioning Abbreviations

UTC Universal Temps Coordiné (=Coordinated Universal Time)

VACM View-based Access Control Model

VLAN Virtual Local Area Network

VOA Variable Optical Attenuator

WAN Wide Area Network

WDM Wavelength Division Multiplexing

WEEE Waste Electrical and Electronic Equipment

WLT Wavelength Division Multiplexing Line Termination

WRED Weighted Random Early Detection

WSS Wavelength Selective Switch

XFP 10 Gigabit small Form-factor Pluggable

XPM Cross Phase Modulation

HDM-73R56070-11-0C Page 76 © Infinera 2022