R19.0 DNA Fault Management and Diagnostics Guide

Infinera DNA
Fault Management and Diagnostics

Guide
Release 19.0
Version 002
Document ID 1900-001537
Infinera Corporation
140 Caspian Court
Sunnyvale, California 94089
www.infinera.com
- Please refer to the Infinera Customer Web Portal for the most recent version of this document. -
Copyright
Copyright © 2019 Infinera Corporation
This Manual is the property of Infinera Corporation and is confidential. No part of this Manual may be reproduced for any purposes
or transmitted in any form to any third party without the express written consent of Infinera.
Infinera makes no warranties or representations, expressed or implied, of any kind relative to the information or any portion thereof
contained in this Manual or its adaptation or use, and assumes no responsibility or liability of any kind, including, but not limited to,
indirect, special, consequential or incidental damages, (1) for any errors or inaccuracies contained in the information or (2) arising
from the adaptation or use of the information or any portion thereof including any application of software referenced or utilized in the
Manual. The information in this Manual is subject to change without notice.
Trademarks
Infinera, Infinera Intelligent Transport Networks, IQ NOS, FlexILS, DTN-X, DTN, ATN, FastSMP, FlexCoherent, What the Network
Will Be, iWDM, Enlighten and logos that contain Infinera are trademarks or registered trademarks of Infinera Corporation in the
United States and other countries.
All other trademarks in this Manual are the property of their respective owners.
Infinera DTN-X, DTN, FlexILS, Cloud Xpress, XT, and ATN Regulatory Compliance
FCC Class A
This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this device may not
cause harmful interference, and (2) this device must accept any interference received, including interference that may cause
undesired operation. Modifying the equipment without Infinera's written authorization may result in the equipment no longer
complying with FCC requirements for Class A digital devices. In that event, your right to use the equipment may be limited by FCC
regulations, and you may be required to correct any interference to radio or television communications at your own expense.
DOC Class A
This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus as set out in the
interference-causing equipment standard titled “Digital Apparatus," ICES-003 of the Department of Communications.
Cet appareil numérique respecte les limites de bruits radioélectriques applicables aux appareils numériques de Classe A prescrites
dans la norme sur le matériel brouilleur: "Appareils Numériques," NMB-003 édictée par le Ministère des Communications.
Class A
This is a Class A product based on the standard of the VCCI Council. If this equipment is used in a domestic environment, radio
interference may occur, in which case, the user may be required to take corrective actions.
Warning
This is a class A product. In a domestic environment this product may cause radio interference in which case the user may be
required to take adequate measures.
FDA
This product complies with the DHHS Rules 21CFR 1040.10 and 1040.11, except for deviations pursuant to Laser Notice No. 50,
dated June 24, 2007.
Contents
About this Document......................................................................................................................................i
Objective....................................................................................................................................................................i
Audience....................................................................................................................................................................i
Document Organization.............................................................................................................................................i
Documents for Release 19.0 ................................................................................................................................... ii
Document Revision History......................................................................................................................................iii
Conventions.............................................................................................................................................................iv
Technical Assistance............................................................................................................................................... iv
Documentation Feedback.........................................................................................................................................v
Chapter 1: Fault Management...................................................................................................................1-1

Overview............................................................................................................................................................... 1-2
Alarm Monitoring................................................................................................................................................... 1-6
Event Management............................................................................................................................................. 1-40
Chapter 2: Environmental Alarms and Control.......................................................................................... 2-1

Configuring Alarm Input Contacts for DTC/MTC-9/MTC-6/OTC/ATC...................................................................2-2
Configuring Alarm Input Contacts for MTC-6/MTC-9/OTC Third Party AC Rectifier.............................................2-4
Configuring Alarm Input Contacts for XTC............................................................................................................2-7
Configuring Alarm Input Contacts for XTC-10 Third Party AC Rectifier................................................................2-9
Configuring Alarm Input Contacts for XTC-2/XTC-2E.........................................................................................2-11
Configuring Alarm Output Contacts for DTC/MTC-6/MTC-9/OTC/ATC.............................................................. 2-13
Configuring Alarm Output Contacts for XTC....................................................................................................... 2-14
Configuring Alarm Output Contacts for XTC2/XTC-2E....................................................................................... 2-16
Alarm Cutoff........................................................................................................................................................ 2-18
Chapter 3: DTN/DTN-X/FlexROADM Diagnostics.....................................................................................3-1

Overview............................................................................................................................................................... 3-2
Loopbacks in DTN and DTN-X..............................................................................................................................3-3
Path Loss Check in FlexROADMs...................................................................................................................... 3-10
Trace Messaging in DTN and DTN-X................................................................................................................. 3-12
PRBS Test in DTN and DTN-X........................................................................................................................... 3-20
Test Signal Generation for Fiber Channel Clients in DTN.................................................................................. 3-34
GbE Client Termination Point Tests in DTN and DTN-X.....................................................................................3-35
Lamp Testing in DTN, DTN-X and FlexROADM................................................................................................. 3-39
Optical Time Domain Reflectometer (OTDR) Testing.........................................................................................3-40
Optical Test Access Ports................................................................................................................................... 3-41
Chapter 4: ATN Diagnostics...................................................................................................................... 4-1

Loopbacks in ATNs............................................................................................................................................... 4-2
Trace Messaging in ATNs...................................................................................................................................4-25
Infinera Corporation Fault Management and Diagnostics Guide Release 19.0 V002
Infinera Proprietary and Confidential

vi Contents
PRBS Tests in ATNs...........................................................................................................................................4-32

Test Signal Generation for Fibre Channel Clients in ATNs.................................................................................4-42
GbE Client Termination Point Tests in ATNs...................................................................................................... 4-45
Lamp Testing in ATNs.........................................................................................................................................4-48
Point Loss Adjustment Utility...............................................................................................................................4-49
Chapter 5: Cloud Xpress and XT Diagnostics........................................................................................... 5-1

Loopbacks in CXs................................................................................................................................................. 5-2
Trace Messaging in CXs....................................................................................................................................... 5-7
Loopbacks in XTs..................................................................................................................................................5-8
Trace Messaging in XTs..................................................................................................................................... 5-16
Lamp Testing in CX and XT................................................................................................................................ 5-17
Chapter 6: Diagnostics Applications.......................................................................................................... 6-1

ATN Digital Link Viewer........................................................................................................................................ 6-2
Digital Link Viewer...............................................................................................................................................6-13
Cloud Xpress Link Viewer................................................................................................................................. 6-122
XT Digital Link Viewer....................................................................................................................................... 6-135
Field Data Recorder Logs Collection................................................................................................................ 6-143
Circuit Diagnostic Manager............................................................................................................................... 6-146
SOAM Manager................................................................................................................................................ 6-234
Chapter 7: DNA Server Alarms..................................................................................................................7-1

DNA Server Unreachable Alarms......................................................................................................................... 7-2
DNA Server Performance Alarms....................................................................................................................... 7-11
DNA Security Alarm............................................................................................................................................ 7-14
Fiber Alarm..........................................................................................................................................................7-15
DNA-M Alarm...................................................................................................................................................... 7-16
Fault Management and Diagnostics Guide Release 19.0 V002 Infinera Corporation

List of Figures
Figure 1-1 Events and Notifications.................................................................................................................. 1-2
Figure 1-2 Node/Admin Domain Tool-tip Details.............................................................................................. 1-3
Figure 1-3 DNA Alarm Manager....................................................................................................................... 1-7
Figure 1-4 Alarm Manager: MSAM enabled..................................................................................................... 1-8
Figure 1-5 Alarm Manager: Filtering based on severity from the Alarm Count Summarization Panel............1-10
Figure 1-6 Alarm Manager: Quick Filter panel................................................................................................ 1-12
Figure 1-7 Alarm Manager showing XTM alarms........................................................................................... 1-17
Figure 1-8 View Customization....................................................................................................................... 1-18
Figure 1-9 Customized Toolbar Positions.......................................................................................................1-18
Figure 1-10 Default Toolbar.............................................................................................................................. 1-19
Figure 1-11 XTM alarm launching ENM............................................................................................................1-21
Figure 1-12 Manage Filters...............................................................................................................................1-25
Figure 1-13 Select Nodes/Select Object Types................................................................................................ 1-27
Figure 1-14 Filter Panel.................................................................................................................................... 1-29
Figure 1-15 Sort Order......................................................................................................................................1-31
Figure 1-16 Alarm Severity Profile Setting........................................................................................................1-33
Figure 1-17 Customize Alarm Settings............................................................................................................. 1-37
Figure 1-18 DNA Event Log..............................................................................................................................1-41
Figure 1-19 Event Log: Filtering based on severity from the Alarm Count Summarization Panel.................... 1-43
Figure 1-20 Event Log: Quick Filter panel........................................................................................................ 1-46
Figure 1-21 Event Log: View Customization.....................................................................................................1-50
Figure 1-22 Event Log: Customized Toolbar Positions.....................................................................................1-51
Figure 1-23 Event Log: Default Toolbar Positions............................................................................................ 1-51
Figure 1-24 EventThe Detailsimage is .............................................................................................................1-52
Figure 1-25 Export Events: Status Message.................................................................................................... 1-55
Figure 2-1 Launch Alarm Input Contact from XTC-2/XTC-2E.........................................................................2-11
Figure 3-1 J0/DTF Section/DTF Path Trace Messaging.................................................................................3-12
Figure 3-2 Digital Channel TTI on LM-80........................................................................................................3-13
Figure 3-3 Trace Messaging Supported by the TAM-2-10GT.........................................................................3-13
Figure 3-4 PRBS Tests Supported by the XTC.............................................................................................. 3-21
Figure 3-5 PRBS generation and monitoring are intrusive diagnostics.......................................................... 3-23
Figure 3-6 Digital Channel PRBS Test Supported by LM-80..........................................................................3-24
Figure 3-7 PRBS Tests Supported by TAM-2-10GT.......................................................................................3-25
Figure 3-8 OSA Ports on the BMM................................................................................................................. 3-42
Figure 3-9 OSA Ports on the OAM................................................................................................................. 3-43
Figure 4-1 Client CTP Facility Loopback.......................................................................................................... 4-3
Figure 4-2 Clear Channel Client CTP Facility Loopback.................................................................................. 4-4
Figure 4-3 DCH CTP Terminal Loopback......................................................................................................... 4-5
Figure 4-4 DCH CTP Terminal Loopback......................................................................................................... 4-8
Figure 4-5 Client CTP Facility Loopback........................................................................................................ 4-11
Figure 4-6 Client CTP Facility Loopback (SIM-T-1-10GM)............................................................................. 4-13
Figure 4-7 SONET/SDH/J0/OTUk Trace Messaging......................................................................................4-25
Figure 4-8 J0 and TTI Trace Messaging.........................................................................................................4-27
Figure 4-9 OTUk PRBS Tests.........................................................................................................................4-33
Figure 4-10 Test Signal Generation..................................................................................................................4-42
Figure 5-1 Client Loopbacks on CX-10E and CX-40E......................................................................................5-2

viii List of Figures
Figure 5-2 Client Loopbacks on CX-100E........................................................................................................ 5-3
Figure 5-3 Loopbacks in CX-1200F.................................................................................................................. 5-3
Figure 5-4 Line Loopback on CX-10E and CX-40E.......................................................................................... 5-4
Figure 5-5 Line Loopback on CX-100E.............................................................................................................5-4
Figure 5-6 OCG Loopback on CX-10E and CX-40E.........................................................................................5-5
Figure 5-7 OCG Loopback on CX-100E........................................................................................................... 5-5
Figure 5-8 Client Loopback in XT-500S-100.....................................................................................................5-8
Figure 5-9 Client loopback in XT-3300............................................................................................................. 5-9
Figure 5-10 Client loopback in XT-3600............................................................................................................. 5-9
Figure 5-11 Line Loopbacks in XT-500S-100................................................................................................... 5-10
Figure 5-12 Line Loopback in XT-3300.............................................................................................................5-10
Figure 5-13 Line Loopback in XT-3600.............................................................................................................5-11
Figure 5-14 OCG Loopback on XT-500S and SCG Loopback on XT-500F..................................................... 5-12
Figure 5-15 SCG loopback in XT-3300.............................................................................................................5-13
Figure 5-16 SCG loopback in XT-3600.............................................................................................................5-13
Figure 5-17 Trib ODUk loopback in XT-3600....................................................................................................5-14
Figure 6-1 ATN Digital Link Viewer...................................................................................................................6-3
Figure 6-2 OFM Trib Port - OFM PNTP configured at both ends..................................................................... 6-9
Figure 6-3 Enable ADAPT: Confirmation Message........................................................................................ 6-11
Figure 6-4 Enable ADAPT Operation Status.................................................................................................. 6-11
Figure 6-5 Disable ADAPT Operation Status..................................................................................................6-11
Figure 6-6 Enable ADAPT: Confirmation Message........................................................................................ 6-12
Figure 6-7 Enable ADAPT Operation Status.................................................................................................. 6-12
Figure 6-8 Disable ADAPT Operation Status..................................................................................................6-12
Figure 6-9 Digital Link Viewer......................................................................................................................... 6-14
Figure 6-10 DLV - Summary View for FlexROADM node.................................................................................6-15
Figure 6-11 DLV - Summary View for DTN/DTN-X/OA node........................................................................... 6-16
Figure 6-12 DLV - Graphical View for FlexROADM Node................................................................................ 6-17
Figure 6-13 DLV - Graphical View for DTN/DTN-X/OA Nodes......................................................................... 6-19
Figure 6-14 DLV - Graphical View for XTM Node.............................................................................................6-20
Figure 6-15 SCH number and Manual mode icon............................................................................................ 6-21
Figure 6-16 AD state in Graphical view............................................................................................................ 6-22
Figure 6-17 Turn-up tool: Warning message.................................................................................................... 6-47
Figure 6-18 DLV - Super Channel Layer.......................................................................................................... 6-48
Figure 6-19 TTI Diagnostics..............................................................................................................................6-50
Figure 6-20 DLV - OCG Layer.......................................................................................................................... 6-51
Figure 6-21 Optical Power Monitoring Charts...................................................................................................6-53
Figure 6-22 Optical Power Monitoring Charts (Mismatch of Base and Scan granularity).................................6-54
Figure 6-23 DLV - Super Channel Carrier Layer for FlexROADM Nodes.........................................................6-55
Figure 6-24 Channel Layer for Alien SCH........................................................................................................ 6-56
Figure 6-25 Channel Layer for DTN/DTN-X/OA Nodes.................................................................................... 6-57
Figure 6-26 DLV - Optical Channel Layer for XTM........................................................................................... 6-59
Figure 6-27 DLV representation for MXP-400 to FRM-20X via Passive Equipment (CO-D480D)................... 6-61
Figure 6-28 DLV representation for MXP-400 to FRM-20X via FMMC-12 and FBM for Dual Carrier............. 6-62
Figure 6-29 DLV representation for MXP-400 to FRM-20X and FRM-20X for Single Carrier.......................... 6-62
Figure 6-30 DLV representation of MXP-400 to FRM-20X and FRM-20X to Fiber via FMP-C.........................6-62
Figure 6-31 DLV representation of MXP-400 to BMM2 via FMM-C-12............................................................ 6-63
Figure 6-32 DLV representation of multiple third-party nodes between XT-3300 and FRM-20X..................... 6-63
Figure 6-33 DLV representation of two third-party nodes between two XT-3300 nodes ................................. 6-64

ix
Figure 6-34 DLV representation for FRM-9D to FRM-20X (with OTSPTP) and IAM with Pre-Amplier and
Booster Amplier............................................................................................................................. 6-64
Figure 6-35 DLV for FRM-20X (with OTSPTP) with Pre-Amplier and Booster Amplier....................................6-65
Figure 6-36 DLV for FRM-20X to RAM1........................................................................................................... 6-65
Figure 6-37 DLV support for FRM Cascade..................................................................................................... 6-66
Figure 6-38 XT-XT IGCC(L1 TE Link) DLV launch........................................................................................... 6-66
Figure 6-39 IGCC (L1 TE Link) DLV Launch.................................................................................................... 6-67
Figure 6-40 GEN2 SLTE Deployments With LMM............................................................................................6-67
Figure 6-41 DLV of IAM-B-ECH2......................................................................................................................6-68
Figure 6-42 Super Channel Switching view: FRM-20X with XT-3600.............................................................. 6-68
Figure 6-43 Super Channel Switching view: FRM-20X with FBM and XT-3600 with Multiple Super
Channels....................................................................................................................................... 6-69
Figure 6-44 Bi-directional association between XT-3600 and OPSM and FMPC and FRM-20X .................... 6-69
Figure 6-45 XT-3600 with SCHCTP and corresponding Carrier CTPs.............................................................6-70
Figure 6-46 XT-3600 with Multiple SCHCTP.................................................................................................... 6-70
Figure 6-47 ASE module connectivity to FRM-20X......................................................................................... 6-71
Figure 6-48 FRM-20X on Different Nodes with OPSM ................................................................................... 6-71
Figure 6-49 SLTE Terrestrial: OPSM Connected To FRM-20X Trib Without FSP ......................................... 6-72
Figure 6-50 SLTE Terrestrial: Unidirectional association from ASE Idler to FRMSCGPTP .............................6-73
Figure 6-51 SLTE Terrestrial: Unidirectional IAM PA connection between two FRMSCGPTP ....................... 6-74
Figure 6-52 SLTE Terrestrial: Bidirectional connection between two IAM PA, OPSMPTP and
FRMSCGPTP................................................................................................................................ 6-74
Figure 6-53 DLV connection of XT-3600 to FRM-20X via FBM and FRM-20X to XT-3600 .............................6-75
Figure 6-54 DLV connection of XT-3600 to FRM-20X and FRM-20X to XT-3600 ..........................................6-75
Figure 6-55 AOFX-1200 to XT-3600 interop and OTM-1200 Protection.......................................................... 6-76
Figure 6-56 DLV view to display AOFX-1200/SOFX-1200 cards on BMM....................................................... 6-76
Figure 6-57 DLV Source and Destination Node of AOFX-1200/SOFX-1200 SCHCTP and CarrierCTPs........6-77
Figure 6-58 SOFX-1200 with Multiple Super Channels with FSP.....................................................................6-77
Figure 6-59 AOFX-1200 with Single Super Channel with FSP on OCG plan...................................................6-78
Figure 6-60 Optical Express between FRM-9D and FRM-20X.........................................................................6-78
Figure 6-61 FRM-20X Express via FSP-CE-1LC..............................................................................................6-79
Figure 6-62 New Express Fiber Shuffle Panels FSP-EE-9D and 13MPO........................................................ 6-79
Figure 6-63 DLV Window for XTM network...................................................................................................... 6-80
Figure 6-64 Band and OCH View option for XTM.............................................................................................6-80
Figure 6-65 AOFX-100 via XTM line system.................................................................................................... 6-81
Figure 6-66 IRM-B-ECH1 as amplifier and pre-amplifier to FRM-20X..............................................................6-81
Figure 6-67 FRM-20X (SLTE-TLA) connected to a MFM module via WPLM Port ......................................... 6-82
Figure 6-68 FRM-20X (SLTE-TLA) connected to a MFM module via Sys-in Port .......................................... 6-83
Figure 6-69 WPLM with SLTE IAM and Idler Mux , TLA after WPLM .............................................................6-84
Figure 6-70 WPLM with SLTE IAM and Idler Mux , TLA before WPLM ..........................................................6-85
Figure 6-71 ASEM Direct connected to FRM-20X .......................................................................................... 6-86
Figure 6-72 ASEM Direct connected to FRM-20X via FSP-C ........................................................................6-87
Figure 6-73 Sample Topology...........................................................................................................................6-88
Figure 6-74 BMM - FRM Mixed Line System....................................................................................................6-89
Figure 6-75 Mixed Line System with Frequency slot plan OCG_50GHz_1/2/3 .............................................. 6-89
Figure 6-76 FRM MPO-MPO express connection without FSP-E .................................................................. 6-90
Figure 6-77 XT-3300 - Sliceable view ..............................................................................................................6-91
Figure 6-78 Super Channel view: XT-3300 with FRM-9D.................................................................................6-92
Figure 6-79 Super Channel view: XT-3300 with BMM2C and BMM2C express...............................................6-92
Figure 6-80 Super Channel view: XT-3300 with BMM2, FMP-C and FSP....................................................... 6-92

x List of Figures
Figure 6-81 Super Channel Switching view: FRM-20X with FBM and XT-3300...............................................6-93
Figure 6-82 Super Channel view: FRM-20X with FMM-C.................................................................................6-93
Figure 6-83 OPM charts in the Optical Power Monitoring tab...........................................................................6-94
Figure 6-84 Super Channel view: FMM-F250 Head-end configuration with IAM and LMM..............................6-94
Figure 6-85 Multiple DLV Instances launched through different links per client session.................................. 6-95
Figure 6-86 TTI Diagnostic from OLDP SCH...................................................................................................6-95
Figure 6-87 ALL OCH grouping inside OTUCni container................................................................................ 6-96
Figure 6-88 Some OCH grouping inside OTUCni container............................................................................. 6-97
Figure 6-89 SMFULL Fiber Type between two nodes...................................................................................... 6-98
Figure 6-90 XT-500F on ILS3 with XT-500F in another node...........................................................................6-98
Figure 6-91 Channel Layer representation for XT-500F on ILS3......................................................................6-99
Figure 6-92 XT-500F in Drop and Continue configuration in Graphical View................................................... 6-99
Figure 6-93 Super channel layer and Carrier layer for XT-500F in Drop and Continue configuration............ 6-100
Figure 6-94 XT-500S over ILS2 in Graphical View......................................................................................... 6-100
Figure 6-95 XT-500S in Drop and Continue configuration in Graphical view................................................. 6-100
Figure 6-96 OCG Layer and Channel layer for XT-500S in Drop and Continue configuration....................... 6-101
Figure 6-97 Alien over ILS3 representation in Graphical view........................................................................6-101
Figure 6-98 Super channel layer and Carrier layer for OTUCni......................................................................6-101
Figure 6-99 Alien over ILS2 representation in Graphical View....................................................................... 6-102
Figure 6-100 Representation of FMP in Graphical view................................................................................... 6-102
Figure 6-101 Repersentation of FMP-F in Graphical view................................................................................6-102
Figure 6-102 Representation of LMM in Graphical view...................................................................................6-103
Figure 6-103 Representation of OTP in Graphical view................................................................................... 6-103
Figure 6-104 AOFx-100 representation in Channel Layer................................................................................ 6-103
Figure 6-105 AOFX-100 and FMM-C-5-ECTR cards representation in graphical view.................................... 6-104
Figure 6-106 RBP and BPP cards representation in graphical view.................................................................6-105
Figure 6-107 End to End view of FRUs in ILS3 deployment.............................................................................6-105
Figure 6-108 End to End view FRUs in ILS2 deployment.................................................................................6-106
Figure 6-109 IAM and OPSM Representation.................................................................................................. 6-106
Figure 6-110 FMM-F250 Representation..........................................................................................................6-107
Figure 6-111 Channels Table with 100G OCG details......................................................................................6-108
Figure 6-112 Channels Table with 500G OCG details......................................................................................6-108
Figure 6-113 Configured Channels and Shutdown Channels Representation................................................. 6-109
Figure 6-114 Super Channels Representation................................................................................................. 6-109
Figure 6-115 Point Loss Offset for ORM...........................................................................................................6-110
Figure 6-116 Mid Stage DCM Representation..................................................................................................6-111
Figure 6-117 BMM2C Representation.............................................................................................................. 6-112
Figure 6-118 DLV: Fiber Cut Scenario..............................................................................................................6-113
Figure 6-119 LM80 and CMM with BMM.......................................................................................................... 6-114
Figure 6-120 Line In PAD and Line Out PAD Representation.......................................................................... 6-115
Figure 6-121 OCG Port Configuration.............................................................................................................. 6-116
Figure 6-122 Target Power Offset shown in OCG View only............................................................................6-117
Figure 6-123 SOFM/SOFX Representation...................................................................................................... 6-117
Figure 6-124 Super Channel Switching View................................................................................................... 6-118
Figure 6-125 End to End Super Channel Switching Traceability...................................................................... 6-118
Figure 6-126 Passive cards.............................................................................................................................. 6-119
Figure 6-127 Color coding for mismatch modulation........................................................................................ 6-120
Figure 6-128 Color coding for mismatch in Carrier Group Mode...................................................................... 6-120
Figure 6-129 Fiber Label displayed for OTSPTP..............................................................................................6-121
Figure 6-130 Cloud Xpress Link Viewer........................................................................................................... 6-123

xi
Figure 6-131 Cloud Xpress Link Viewer-Graphical View.................................................................................. 6-124
Figure 6-132 Cloud Xpress Link Viewer—Channel Tabular View.................................................................... 6-127
Figure 6-133 Graphical view of CX-500S node................................................................................................ 6-129
Figure 6-134 CX 100E BreakOut Mode............................................................................................................ 6-130
Figure 6-135 CX 100E Non BreakOut Mode.................................................................................................... 6-131
Figure 6-136 CX 100 Mix BreakOut Mode........................................................................................................6-132
Figure 6-137 CX 40-10E .................................................................................................................................. 6-133
Figure 6-138 CX 40-10E Non Breakout Mode.................................................................................................. 6-133
Figure 6-139 CX -1200F Breakout ...................................................................................................................6-134
Figure 6-140 XT Digital Link Viewer................................................................................................................. 6-136
Figure 6-141 XT Digital Link Viewer-Graphical View........................................................................................ 6-137
Figure 6-142 XT Digital Link Viewer—Channel Tabular View.......................................................................... 6-140
Figure 6-143 XT 10........................................................................................................................................... 6-142
Figure 6-144 FDR Collection Manager............................................................................................................. 6-144
Figure 6-145 Circuit Diagnostic Manager Layout..............................................................................................6-149
Figure 6-146 Short Details Window: CDM........................................................................................................ 6-154
Figure 6-147 Layer tab : XTM Services............................................................................................................ 6-157
Figure 6-148 Circuit Selection Dialog............................................................................................................... 6-160
Figure 6-149 CDM support for FRM Cascade on MXP-400............................................................................. 6-183
Figure 6-150 CDM support (Interleaver) for Passive Equipment on MXP-400................................................. 6-183
Figure 6-151 CDM support (AWG) for Passive Equipment on MXP-400......................................................... 6-184
Figure 6-152 CDM support for Dual Carrier SCH on MXP-400....................................................................... 6-184
Figure 6-153 CDM support for Single Carrier SCH on MXP-400......................................................................6-185
Figure 6-154 CDM support for FRM Cascade.................................................................................................. 6-186
Figure 6-155 CDM Summary Table for UAS PM.............................................................................................. 6-186
Figure 6-156 CDM for IAM-2-C.........................................................................................................................6-187
Figure 6-157 CDM for XT-3600 with SCHCTP................................................................................................ 6-187
Figure 6-158 CDM for XT-3600 Re-generation with Electrical TOM ................................................................6-188
Figure 6-159 SLTE Terrestrial : CDM for FRM-20X connected with OPSM ................................................... 6-188
Figure 6-160 CDM for FRM-20X with Add/Drop Xcon And On Different Nodes .............................................6-189
Figure 6-161 SLTE Terrestrial: Two uni-directional ports of IAM PA between two bi-directional OPSMPTP
and FRMSCGPTP ports.............................................................................................................. 6-189
Figure 6-162 SLTE Terrestrial: Uni-directional port of IAM PA between two bi-directional FRMSCGPTP’s
ports ............................................................................................................................................6-190
Figure 6-163 CDM for Circuit PM: XTM and DTN-X......................................................................................... 6-190
Figure 6-164 CDM for Show Diagnostics Filter: XTM and DTN-X.................................................................... 6-191
Figure 6-165 CDM for Node Filter: XTM and DTN-Xnodes.............................................................................. 6-191
Figure 6-166 CDM for TIM2-2-100GM/GX........................................................................................................6-191
Figure 6-167 CDM for interop connection of OTM-1200 and XT-3600.............................................................6-192
Figure 6-168 CDM connection for XT-3600 to FRM-20X via FBM and FRM-20X to XT-3600 ....................... 6-192
Figure 6-169 CDM connection for XT-3600 to FRM-20X and FRM-20X to XT-3600 ..................................... 6-193
Figure 6-170 CDM interop connection for AOFX-1200 to XT-3600.................................................................. 6-193
Figure 6-171 CDM for OTM-1200 Protection....................................................................................................6-194
Figure 6-172 CDM for AOFX-1200/SOFX-1200 FRUs with BMM card............................................................ 6-194
Figure 6-173 CDM support for XT-3300 regeneration with copper cable in same node...................................6-195
Figure 6-174 CDM with SOFX-1200 and AOFX-1200 in OCG Mode............................................................... 6-195
Figure 6-175 CDM with AOFX-1200 in Open mode with FRM-20x on a different node................................... 6-196
Figure 6-176 BMM – FRM Mixed Line System ............................................................................................... 6-196
Figure 6-177 CDM for XT-3300 with LMM and BMM2......................................................................................6-196
Figure 6-178 CDM for XT-3300 with FBM and FRM20X.................................................................................. 6-197

xii List of Figures
Figure 6-179 CDM for XT-3300 with BMM2C................................................................................................... 6-197
Figure 6-180 CDM for XT-3300 with BMM2C Digital wrapper.......................................................................... 6-198
Figure 6-181 CDM for FRM-20X express......................................................................................................... 6-198
Figure 6-182 CDM for CX-500S........................................................................................................................6-199
Figure 6-183 CDM for XTM: PM tab with Category filter.................................................................................. 6-200
Figure 6-184 CDM for XTM: Enable SAPI/DAPI on OTN cards....................................................................... 6-201
Figure 6-185 Summary Panel View: XTM.........................................................................................................6-201
Figure 6-186 Show Diagnostic: XTM................................................................................................................ 6-201
Figure 6-187 Facility Filter: XTM.......................................................................................................................6-202
Figure 6-188 SOLx2 With All OCHs Grouped .................................................................................................6-202
Figure 6-189 SOLx2 With Partial OCHs Grouped .......................................................................................... 6-203
Figure 6-190 CDM with Back to Back Intra and Inter Network Element Link....................................................6-204
Figure 6-191 CDM with AOFX-500 in Manual mode with Multi plexer on different node .................................6-205
Figure 6-192 CDM with XT-500F in Manual mode with Multiplexer on different node......................................6-205
Figure 6-193 CDM with XT-500F and FSM and FRM-9D.................................................................................6-206
Figure 6-194 CDM with XT-500S in Manual mode with FSM and FRM-9D......................................................6-207
Figure 6-195 CDM with OTUCni with SOFx-500 and FRM-9D.........................................................................6-207
Figure 6-196 Super Channel TTI on SCH facility for XT-500F......................................................................... 6-208
Figure 6-197 New counters for GFPTP............................................................................................................ 6-208
Figure 6-198 CDM with AOFx-100 and FMM-C5 over ILS2............................................................................. 6-209
Figure 6-199 CDM with AOFx-100 and FMM-C5 over ILS3............................................................................. 6-209
Figure 6-200 Express cross connect between AOFx-100................................................................................ 6-210
Figure 6-201 AOFx-100 and Tributary module in case of OTM2-500 and OTXM-600..................................... 6-210
Figure 6-202 FlexILS sites Representation.......................................................................................................6-211
Figure 6-203 XT and CX nodes........................................................................................................................ 6-211
Figure 6-204 CX/XT 100GbE Services............................................................................................................. 6-212
Figure 6-205 CX/XT 10GbE Services............................................................................................................... 6-212
Figure 6-206 Circuit Diagonistic Manager for CX-1200F ................................................................................. 6-212
Figure 6-207 Circuit PM for OCG CX/XT.......................................................................................................... 6-213
Figure 6-208 VCAT and Carrier CTP representation........................................................................................6-213
Figure 6-209 Multi OCG for ILS2 Links.............................................................................................................6-214
Figure 6-210 Multi OCG for BMM Express....................................................................................................... 6-214
Figure 6-211 Multi SCG.................................................................................................................................... 6-215
Figure 6-212 Multi SCG for FMM-F250............................................................................................................ 6-215
Figure 6-213 Multi SCG for FRM Express........................................................................................................ 6-216
Figure 6-214 Multi SCG for Multi FSM..............................................................................................................6-217
Figure 6-215 1GFC-CC and 2GFC-CC Payload Representation..................................................................... 6-218
Figure 6-216 Open Wave - Line Modules Representation................................................................................6-219
Figure 6-217 Optical Channels Representation................................................................................................6-220
Figure 6-218 Circuit Diagnostic Manager circuit through AOLM-500: DTN-X.................................................. 6-221
Figure 6-219 Circuit Diagnostic Manager for 4GFC Service: ATN................................................................... 6-222
Figure 6-220 Circuit Diagnostics Manager: Trail Trace Details........................................................................ 6-223
Figure 6-221 STM-64 with single carrier...........................................................................................................6-224
Figure 6-222 ODU Switching............................................................................................................................ 6-225
Figure 6-223 10GbE Network Mapping as ODU2e...........................................................................................6-226
Figure 6-224 100GbE Non VCAT..................................................................................................................... 6-227
Figure 6-225 100GbE VCAT.............................................................................................................................6-227
Figure 6-226 BMM2C-16-CH............................................................................................................................ 6-228
Figure 6-227 Multi OCG BMM Express............................................................................................................ 6-228
Figure 6-228 Multi SCG with FMMF250 and FRM Expressed..........................................................................6-229

xiii
Figure 6-229 Multi SCG With Multi FSM...........................................................................................................6-230
Figure 6-230 Graphical Stack display of FMMF250, FRM 4D, OPSM-2.......................................................... 6-231
Figure 6-231 SIM Local.....................................................................................................................................6-232
Figure 6-232 CDM - ATN as Sub-10G Feeder to DTN/DTN-X......................................................................... 6-232
Figure 6-233 CDM – OPSW Protected Multi-segment Circuit.......................................................................... 6-233
Figure 6-234 SOAM Manager...........................................................................................................................6-235

xiv List of Figures

List of Tables
Table 1-1 Alarm Manager: Action Panel toolbar icons.................................................................................. 1-10
Table 1-2 Color coding and alarm severity mapping..................................................................................... 1-14
Table 1-3 Alarm Categories...........................................................................................................................1-15
Table 1-4 Alarm Details................................................................................................................................. 1-19
Table 1-5 Filter Panel.................................................................................................................................... 1-30
Table 1-6 Alarm Severity Profile Settings: Profile Attributes..........................................................................1-33
Table 1-7 Customizable Alarm Settings: Table............................................................................................. 1-38
Table 1-8 Event Log: Action Panel toolbar icons...........................................................................................1-44
Table 1-9 Event Table: Page Traversal Keys................................................................................................ 1-45
Table 1-10 Color coding and severity mapping............................................................................................... 1-48
Table 1-11 Event Details................................................................................................................................. 1-52
Table 2-1 Input Alarm Contact Table...............................................................................................................2-2
Table 2-2 Input Alarm Contact Table...............................................................................................................2-8
Table 2-3 Input Alarm Contact Table.............................................................................................................2-12
Table 2-4 Output Alarm Contact Table.......................................................................................................... 2-14
Table 3-1 Loopbacks Supported on the XTC.................................................................................................. 3-4
Table 3-2 Loopbacks Supported on DTC and MTC........................................................................................ 3-7
Table 3-3 Connections Supporting Path Loss Check.................................................................................... 3-10
Table 6-1 Parameters displayed in the ATN Digital Link Viewer..................................................................... 6-5
Table 6-2 Right-click options from the Optical Layer of the ATN Digital Link Viewer...................................... 6-6
Table 6-3 Right-click options from the Graphical View.................................................................................. 6-36
Table 6-4 Parameters in TTI Diagnostics dialog............................................................................................6-50
Table 6-5 Right-click options from the Graphical View................................................................................ 6-126
Table 6-6 Right-click options from the Graphical View................................................................................ 6-139
Table 6-7 Circuit Summary Panel: CDM......................................................................................................6-149
Table 6-8 Node Filter Options: CDM........................................................................................................... 6-151
Table 6-9 Facility Filter Options: CDM.........................................................................................................6-153
Table 6-10 Node Status and Display String Mapping....................................................................................6-162
Table 6-11 Right-Click Options: DTN, DTN-X, ROADM, CX, XT ................................................................. 6-162
Table 6-12 Right-Click Options: ATN.............................................................................................................6-170
Table 6-13 Right-Click Option : XTM............................................................................................................. 6-174
Table 6-14 Export Data: CDM....................................................................................................................... 6-182
Table 6-15 SOAM Manager: Page Traversal Keys....................................................................................... 6-236
Table 6-16 SOAM Manager: MD Table......................................................................................................... 6-237
Table 6-17 SOAM Manager: MA Table......................................................................................................... 6-237
Table 6-18 SOAM Manager: MEP Table....................................................................................................... 6-238
Table 6-19 SOAM Manager: MD Properties Window.................................................................................... 6-240
Table 6-20 SOAM Manager: MA Properties Window.................................................................................... 6-240
Table 6-21 SOAM Manager: MEP Properties Window..................................................................................6-241
Table 6-22 MEP Properties: CCM Tab.......................................................................................................... 6-242
Table 6-23 MEP Properties: AIS Tab............................................................................................................ 6-243
Table 6-24 MEP Properties: CCM MEP Database Tab.................................................................................6-243
Table 6-25 MEP Properties: ETH CSF Tab...................................................................................................6-244
Table 6-26 MEP Properties: Diagnostics Tab................................................................................................6-244

xvi List of Tables
Table 7-1 DNA Server Unreachable Alarms....................................................................................................7-2
Table 7-2 DNA Server Performance Alarms..................................................................................................7-11
Table 7-3 DNA Security Alarm.......................................................................................................................7-14

About this Document
This section is an overview of the DNA Fault Management and Diagnostics Guide.
Objective
This guide describes the InfineraDigital Network Administrator (DNA) client user interface. It also provides
procedures to use the DNA to perform Fault Management and Diagnostics functions on the network
elements.
Audience
The primary audience for this guide includes network operation personnel who are responsible for
monitoring the network, configuring the network elements, and topology and provisioning services. This
guide assumes that the reader is familiar with the following topics and products:
■ Any one of the following operating system:
□ Microsoft Windows
□ Red Hat Linux
□ Macintosh
■ Supported Web Browsers
■ Basic internetworking terminology and concepts
■ Network topology and protocols
Document Organization
The following table describes each chapter in this guide.

ii Documents for Release 19.0
Chapter Number: Title Description

Fault Management Describes fault management tools provided by the DNA
and procedures to use them.
Environmental Alarms and Control Provides procedures to control environmental alarms by
configuring input and output closure contacts.
DTN/DTN-X/FlexROADM Diagnostics Describes troubleshooting tools used to troubleshoot the
network element and the Intelligent Transport Network.
ATN Diagnostics Describes troubleshooting tools used to troubleshoot the
ATN network element and the Intelligent Transport
Network.
Cloud Xpress and XT Diagnostics Describes troubleshooting tools used to troubleshoot the
Cloud Xpress and XT network elements and the
Intelligent Transport Network.
Diagnostics Applications Describes DNA troubleshooting tools used to
troubleshoot the network element and the Intelligent
Transport Network.
DNA Server Alarms Describes alarms and events generated by the DNA
server.
Documents for Release 19.0

The following documents are available for DNA:
Document Name Document ID Description

DNA Installation Guides Portfolio
DNA Installation Guide 1900-001532 Describes the DNA server installation and routine
maintenance procedures.
DNA Administrator Guide 1900-001533 Describes the DNA server administration and routine
maintenance procedures.
DNA Server Export File Format 1900-001534 Describes the DNA Export File Format.
DNA User Guides Portfolio
DNA Overview Guide 1900-001535 Describes the DNA user interface. It also describes the
new features, the hardware and software requirements
required to launch the DNA. It also provides procedures
to install and upgrade the software and database on the
network elements.
DNA Web Client User Guide 1900-001536 Describes the DNA web client user interface.

About this Document iii
Document Name Document ID Description

DNA Fault Management and 1900-001537 Describes the Fault Management inventories, Alarm
Diagnostics Guide Manager and Event Log. It also provides the
procedures to perform diagnostic tests on network
elements.
DNA Configuration 1900-001538 Describes the procedures to use the DNA to configure
Management Guide network elements and the network topology. It also
provides a description on the Equipment Manager and
Facility Manager.
DNA Performance 1900-001539 Describes the procedures to use DNA to view
Management Guide performance monitoring (PM) data and modify PM
thresholds for network elements. It also provides the
PM parameters details reported by the network
elements.
DNA Security Management 1900-001540 Describes the procedures to use DNA to view security
Guide management related procedures related the DNA and
the network elements.
DNA Service Provisioning 1900-001541 Describes the procedures to provision cross-connects,
Guide subnetwork connections (SNCs) and protected services
on network elements. It includes a description of the
various inventory managers displayed in the DNA.
License Management Guide 1900-001542 Describes procedures to use License Manager
application in DNA to perform licensing operations such
as assigning instant bandwidth license keys to a license
entity on a network element or Encryption licensing
operations on Cloud Xpress network elements. It also
includes an inventory of all licenses in the network.
Circuit Tracer Tool Guide 1900-001543 Describes the Circuit Tracer Tool which generates and
dumps the circuit trace for all the available digital/optical
circuits and cross-connects in the Digital Network
Administrator (DNA), into the output file.
SNMP FIS Reference Guides Portfolio
SNMP FIS Reference Guide 1900-001544 Describes the user interface for the Simple Network
Management Protocol (SNMP) Fault Integration Server
(FIS). It provides detailed instructions for how to install,
configure, and operate the SNMP Fault Integration
Server on the DNA Server.
Acronyms
Acronyms 1900-001550 Lists the acronyms used in documentation.
Document Revision History

The following table lists the changes made to the document since its previous revision:

iv Conventions
Document Version Document Updates Since Previous Revision

Number
002 Editorial Updates
Conventions
The table below lists the conventions used in this guide.
Convention Item Example

bold default font Menu command paths Select Fault Management-> Alarm
Manager
Button names Click Apply
User interface labels Click Summary panel
Window/dialog box titles In the Dial-Up Networking window
courier font User-entered text In the Label enter EastBMM

Command output Database restore from local or remote
machine?
Directory path /DNA/EMS
Note: If the directory path or

command is spanning across two
lines, copy the directory path or
command to notepad and execute
in editor.
default font, italic Document titles Refer to the CLI User Guide
Default font Icon names Click Node icon
Window names not in the user interface In the DNA Main View
Helpful suggestions
Note: Note: The window is refreshed only
after making all the changes.
Technical Assistance
Customer Support for Infinera products is available, 24 hours a day, 7 days a week (24x7). For
information or assistance with Infinera products, please contact the Infinera Technical Assistance Center
(TAC) using any of the methods listed below:

About this Document v
■ Email: techsupport@infinera.com
■ Telephone:
□ Direct within United States: 1-408-572-5288
□ Outside North America: +1-408-572-5288
□ Toll-free within United States: +1-877-INF-5288 (+1-877-463-5288)
□ Toll-free within Germany/France/Benelux/United Kingdom: 00-800-4634-6372
□ Toll-free within Japan: 010-800-4634-6372
■ Infinera corporate website: http://www.infinera.com
■ Infinera Customer Web Portal: https://support.infinera.com
Please see the Infinera Customer Web Portal to view technical support policies and procedures, to
download software updates and product documentation, or to create/update incident reports and
RMA requests.
Documentation Feedback
Infinera strives to constantly improve the quality of its products and documentation. Please submit
comments or suggestions regarding Infinera Technical Product Documentation using any of the following
methods:
■ Submit a service request using the Infinera Customer Web Portal
■ Send email to: techpubs@infinera.com
■ Send mail to the following address:
Attention: Infinera Technical Documentation and Technical Training
Infinera Corporation
140 Caspian Court
Sunnyvale, CA 94089
When submitting comments, please include the following information:
■ Document name and document ID written on the document cover page
■ Document release number and version written on the document cover page
■ Page number(s) in the document on which there are comments

vi Documentation Feedback

CHAPTER 1
Fault Management
This chapter describes the Fault Management applications provided by the DTN, DTN-X, FlexROADM
and the Optical Amplifier network elements (referred to as network element) in the following sections:
Overview on page 1-2
Alarm Monitoring on page 1-6
Event Management on page 1-40
SOAM Manager on page 6-234
Note: All the date and time parameters described/referred to in this document will be in the user
configured time zone unless otherwise specified.
Note: All references to the IRM will refer to the IRM-B-ECXH1, IRM-B-ECH1 and/or IRM-B-ECH2
interchangeably. Also note that all references to the IRM-1 will refer to the IRMB- ECXH1, all
references to the IRM-1-C will refer to the IRM-B-ECH1 and all references to IRM-2-C will refer to
IRM-B-ECH2.
Note: Multi-chassis configurations for Cloud Xpress are not supported.

1-2 Overview
Overview
The fault monitoring and management capabilities of Infinera Intelligent Transport Networks are modeled
after Telcordia and ITU standards. For a detailed description of these capabilities, refer to the DTN and
DTN-X System Description Guide.
Infinera DNA , hereinafter referred to as DNA GNM, allows:
■ Monitoring alarms and events detected by the network or the external sensors connected to it.
■ Retrieving alarms and events stored in the network element.
■ Assigning alarm severity through the Alarm Severity Profile Settings (ASPS) application.
■ Applying ASPS to multiple nodes.
■ Inhibiting (and allowing) alarm reporting on a per-managed-entity basis.
■ Restoring ASPS to factory default settings.
■ Customizing alarm settings.
DNA provides a central location for monitoring critical events and alarms generated by the target
network elements. The area of fault management covers all operations and functionality pertaining
to the reporting and testing of conditions in the target network elements. The Intelligent Transport
Network support two types of notifications, namely alarms and events.
Figure 1-1 Events and Notifications
Alarms
An alarm is an indication of a failure condition. Alarms are assigned severities as critical, major, minor and
warning, depending on the degree of service degradation or disruption.
Using the Alarm Severity Profile Settings tool, users can edit the assigned severities. Apart from the
above listed severities, alarms can be marked as Not Reported or as Events.

Fault Management 1-3
Note: Alarms with severity Clear are raised to notify cleared alarms. This functionality is enabled if the
Multi-Stage Alarm Management (MSAM) feature is enabled on the DNA server. These alarms can be
acknowledged by the users.
When a new alarm is raised on a node, the node and the corresponding Administrative domain icons start
blinking in the graphical topology view. The node color reflects the severity of the outstanding alarm and
not the severity of unacknowledged alarm. The Node/Administrative domain tool-tip displays the count of
unacknowledged alarms for CR, MJ, MN, WN and UR alarms.
Figure 1-2 Node/Admin Domain Tool-tip Details
If the alarm is cleared before it is acknowledged, then this alarm is removed from the unacknowledged
alarm list and the blinking stops.
The node icon stops blinking if:
■ all the alarms raised on this node are acknowledged or cleared.
The Administrative domain icon stops blinking if:
■ all the alarms raised on the nodes are acknowledged or cleared.
■ the node containing the unacknowledged alarms is moved out of the administrative domain.
■ the node containing the unacknowledged alarms is unmanaged or deleted.
To enable the Alarm Annotation Settings, refer to DNA Security Management Guide.

1-4 Overview
Events
Events identify changes to an entity in the network. Events indicate the operations performed through
DNA. Events are recorded within the system and are available to management applications for data-
model synchronization and reporting. Events are stored and can be viewed in the Event Log.
Network elements recognize the following types of notifications:
■ Conditions
Conditions are reported when anything other than the usual behavior of the managed network
element occurs. Conditions are further divided into the following categories:
□ Alarmed conditions—Conditions that require immediate action are reported as alarms. These
conditions require immediate attention, for example Loss of Light. They are differentiated by
the severity. These events are also available in the alarm list.
□ Non-alarmed conditions—Conditions that are mostly informational are reported as non-
alarmed conditions. For example, a port in loopback.
□ Threshold Crossing Alarms—These conditions are reported when there is a threshold
crossing.
■ Reporting Events
Reporting events are generated by the target network element when there is a state change in the
managed network element. Reporting events are divided into the following categories:
□ Security event—Events generated when there are security violations in the managed
network element.
□ Administrative event—Internal communication events between network elements and
management clients such as GNM and DNA. These events are used to communicate the
event queue status and processor activities (reboot, switchover, active).
□ Threshold crossing event— Events that report threshold crossing information.
□ Audit event—Records of user actions that modify the state of any of the managed objects
within the network element.
The DNA provides the following tools to view alarms and events generated in the network:
■ Alarm Manager
■ Event Log
These tools are useful for the following operations:
■ Displaying detailed information about events and alarms
■ Sorting and filtering alarms and events into categories
■ Creating and saving customized filters that contain a logical combination of user-defined criteria
■ Acknowledging alarms by including custom information (acknowledged text)

■ Launching applicable context-sensitive inventory managers like Facility Manager, Equipment

Manager, Cross Connect Manager, Circuit Manager, and Circuit Diagnostic Manager for the
selected alarm or event
■ Navigating to the source object with which the alarm/event is associated, using the Go To Source
option
■ Viewing the object event history

1-6 Alarm Monitoring
Alarm Monitoring
This section describes the various components of the Alarm Manager and provides detailed procedures
for using it:
Alarm Manager on page 1-6
Using the Alarm Manager on page 1-16
Alarm Severity Profile Settings on page 1-32
Customize Alarm Settings on page 1-37
Alarm Manager
The Alarm Manager displays all outstanding conditions (alarms) in a tabular form. All outstanding alarms
are maintained in the Alarm Table and displayed until the condition is cleared. Multiple Alarm Manager
instances can be launched simultaneously based on various contexts.
Note: Starting R16.1, alarms rasied by the XTM network elements are also visible in the Alarm
Manager.
Note: Launching Alarm Manager from the Fault Management menu launches the alarms for all the
administrative domains assigned to the current user.
Note: Re-ordering of columns remain in effect only for the current session.
Note: If the Multi-stage Alarm Management (MSAM) feature is enabled in DNA, the Alarm Manager
also displays all the cleared alarms with severity, Clear in the alarm table until the clear alarms are
acknowledged by the user.
The Alarm Manager is used:

■ To view alarm details
■ To get a list of alarms (Alarm Table) that match a specific context
■ To filter alarms based on various alarm attributes (criteria)
■ To create and modify customized alarm filters
■ To acknowledge alarms and add acknowledgment text to alarms
■ To go to the source of an alarm, launch respective context-sensitive inventory managers
■ To export alarms

To launch the Alarm Manager

Do one of the following:
■ In the DNA Main Menu, select Fault Management > Alarm Manager.
■ In the DNA Tree view, right-click the administrative domain icon and select Alarm Manager.
The Alarm Manager is displayed.
If the Alarm Manager is launched when the initialization process of the client is not complete, an
information message is displayed. Click Ok to close the prompt and re-launch the Alarm
Manager after the initialization is complete.
Figure 1-3 DNA Alarm Manager

Figure 1-4 Alarm Manager: MSAM enabled
Alarm Count Summarization Panel

The Alarm Count Summarization Panel displays the count of the number of alarms by severity.
The Category column in the Alarm Manager displays all alarms based on the alarm category as
selected in the Alarm Summary Panel.
Alarm Manager Panel Description

The Alarm Manager consists of the following panels:
■ Alarm Count Summarization Panel
□ The Alarm Count Summarization Panel displays the count of the total number of alarms
categorized by alarm severity. The count displayed corresponds to the instance of the Alarm
Manager launched. This is based on the context and the launch point. The number
embedded in these buttons indicate the number of alarms in the category. The Alarm Count
Summarization Panel is refreshed with a change in context and/or change in filter criteria.
Alarms can be filtered based on severity using the severity buttons on the Alarm Count
Summarization Panel.
This panel consists of the following buttons:
Total—When the Alarm Manager is launched, this button is activated by default
indicating the total number of alarms that match the context and the filter criteria
selected are displayed in the Alarm Table. The appearance of this button varies when

the alarms are filtered based on severity, indicating that only a subset of the total
number of alarms that match the context are displayed in the Alarm Table. The status
of this button varies with the status of the other buttons in the Alarm Manager.
CR—This button is indicative of the total number of alarms with severity Critical that
match the context and the filter criteria selected in the current Alarm Manager
instance. Clicking this button toggles the display of the Critical alarms in the Alarm
Table.
MJ—This button is indicative of the total number of alarms with severity Major, that
instance. Clicking this button toggles the display of the Major alarms in the Alarm
Table.
MN—This button is indicative of the total number of alarms with severity Minor, that
instance. Clicking this button toggles the display of the Minor alarms in the Alarm
Table.
WN—This button is indicative of the total number of alarms with severity Warning, that
instance. Clicking this button toggles the display of the Warning alarms in the Alarm
Table.
Clear—This button is indicative of the total number if Clear alarms that match the
context and the filter criteria selected in the current Alarm Manager instance. Clicking
this button toggles the display of the Clear alarms in the Alarm Table. This category of
alarms are listed in the Alarm Table only if the MSAM feature is enabled on the DNA
server.
UR—This button is indicative of the total number of Unreachable alarms that match
the context and the filter criteria selected in the current Alarm Manager instance.
Clicking this button toggles the display of the Unreachable alarms in the Alarm Table.
Table below shows the default settings of the Alarm Count Summarization Panel in a
network-wide instance of the Alarm Manager. Note that, by default, all the buttons are
selected in this panel indicating that the alarms are not filtered based on severity and
complete list of alarms are displayed in the Alarm Table. The numbers embedded in
the buttons matching the severity color-code of the alarms indicate the number of
alarms in the respective category. The sum of all these numbers is displayed in the
Total button indicating the total number of alarms that match the context and filtering
criteria.

Figure 1-5 Alarm Manager: Filtering based on severity from the Alarm Count Summarization Panel
□ The above figure shows the settings of Alarm Count Summarization Panel in a network-wide
instance of the Alarm Manager where Critical and Minor alarm buttons are de-selected. With
this, the Alarm Table is refreshed to display all alarms excluding CR (Critical) and MN
(Minor) alarms (CR and MN buttons are de-selected). Any change to the default settings in
the Alarm Count Summarization Panel highlights the Total button indicating the filter
selection or a change. Click the respective buttons to select or de-select them. Selecting the
buttons at any time refreshes the alarm table to include the alarms in the selected category.
Action Panel
The Action panel consists of icons mentioned in Table 1-1: Alarm Manager: Action Panel toolbar icons on
page 1-10:
Table 1-1 Alarm Manager: Action Panel toolbar icons

Toolbar Icon Description
Customize Columns—Icon used to customize the Alarm Table columns. The columns to be
displayed and the order of display can be configured from the View Customization window,
launched by clicking the Customize Columns icon. For details on how to customize columns, see
To customize Alarm Table view in Alarm Manager on page 1-18.
Restore Default Toolbar Positions—Icon used to reset the customized toolbar positioning to
default positions in the Alarm Manager. For details on changing or resetting the toolbar positions
in the Alarm Manager, see To change the toolbar positions in the Alarm Manager on page 1-
18.

Table 1-1 Alarm Manager: Action Panel toolbar icons (continued)

Manage Filters—Icon used to launch the Manage Filters window that aids in the definition and
modification of customized alarm filters. For details on working with Customized Alarm Filters,
see Filtering Alarm Data on page 1-23.
Acknowledge Alarms—Icon used to acknowledge single or multiple alarms selected from the
Alarm Table in the Alarm Manager. For details on acknowledging Alarms, see Acknowledging
Alarms on page 1-22.
Quick Filters Panel

The Quick Filter panel in the Alarm Manager consists of:
■ Quick Filters—Quick Filters are used to further filter the alarms in the alarm table. The Quick Filter
panel has a hierarchical tree with a check-box against each attribute to select the filtering criteria.
The Quick filter panel in the Alarm Manager is shown below:

Figure 1-6 Alarm Manager: Quick Filter panel
The hierarchical root for the Quick Filter is indicated by the label Quick Filters. Selecting or
deselecting the Quick Filters checkbox selects or deselects all the attributes in the Quick Filter
panel. Expanding a filtering attribute in the Quick Filter panel displays the associated categories for
further definition of the filter. By default, Severity criteria is checked in the Quick Filters panel
indicating that alarms of all severities are listed in the Alarm Table. The severity selection in the
Quick Filter panel matches the respective selection in the Alarm Count Summarization panel. With
the default selection in the Quick Filters panel, the Apply Filter(s) button is grayed-out unless there
is a change in the filter criteria selection. Click Apply Filter(s) button to apply the quick filter. Once a
Quick Filter is applied, the Apply Filter(s) button is grayed-out indicating the application of Quick
Filter.
Note: The filter option, Severity ->Clear is displayed only if the MSAM feature is enabled on the
DNA server.

Note: The filter option, Others->Outstanding alarms is displayed only if the MSAM feature is
enabled on the DNA server. Applying this filter option displays only the outstanding alarms in
the Alarm Table when the MSAM feature is enabled.
The Filter summary panel summarizes the filtering criteria selected for the view. The Alarm Table in
the Alarm Manager is refreshed only when the Apply Filter(s) button is clicked after the Quick Filter
selection.
To unapply a Quick Filter, de-select the quick filtering criteria check-box against each attribute
selected and click Apply Filter(s).
Selecting and de-selecting the check-box next to the hierarchical root, Quick Filters, selects and
de-selects all the filtering criteria attributes in the Quick Filter panel respectively.
Note: Clicking Apply Filter(s) button when no attributes are selected in the Quick Filters panel
will refresh the Alarm Table with a list of alarms that match the previously applied filter.
Note: A quick filter selection can be used to define a custom filter. See To define Advanced
Filter Criteria.
Note: The Quick Filters applied are applicable only for the current view.
■ Quick Filter Summary Panel—The Quick Filter Summary Panel summarizes the quick filtering
conditions selected for the view.
Alarm Context and Filter Panel
The Alarm Context and Filter panel displays the context and the filter applied. It provides a drop-down
menu to choose the context and filter to customize data displayed in the Alarm Manager. The Alarm
Table is refreshed based on the context and/or filter selection. The Alarm Context and Filter Panel
consists of:
■ Context—A drop-down menu that lists the current context of the data displayed in Alarm Manager
and the associated parent context. The alarm table displayed in the Alarm Manager will refresh
based on the context selection. The Alarm Table refreshes with the change in selection of the
context from the current to its parent and vise versa.
For example, if the launch point of the Alarm Manager is a Network Element belonging to an Admin
Domain, the current context indicates Node and the Context drop-down menu lists the Node and
Admin Domain options for selection.
■ Filter—A drop-down menu that lists the customized alarm filters that can be applied in the Alarm
Manager. If a customized alarm filter is applied, the filter name is displayed in this field. The Alarm
Table is refreshed based on the filter selection. The drop-down menu also provides an option None
to restore the current view with no active filters. Customized filters can be defined using the
Manage Filters window. For details on custom filter definition, refer to To create customized alarm
filters.
Note: The context and filter conditions chosen are applicable only for the current view.

Alarm Table
■ Alarm Table
The Alarm Table provides a list of all the alarms that are currently outstanding. By default, the
alarms are in chronological order with the most recent alarm at the top of the list. Alarms are
displayed in a tabular form and the view can be customized to include the desired fields. These
columns in the Alarm Table can be rearranged either by dragging and dropping the columns in the
desired order or using the View Customization window. For details on View Customization window,
see To customize Alarm Table view in Alarm Manager on page 1-18. Alarms can be sorted on any
of the columns. By default, they are sorted by the time at which the alarm was raised by the
network element that is the Source Date/Time attribute in the user configured time zone.
The following fields are displayed for alarms:
■ Sev
Sev (alarm severity) is a classification of alarms depending on the degree of perceived degradation
or disruption of service or product. The severity of alarms are indicated by the following color code:
Table 1-2 Color coding and alarm severity mapping

Color Severity Description
Red CR—Critical alarms indicate a severe, service-affecting condition for which immediate corrective
action is required to restore service.
Orange MJ—Major alarms indicate a serious disruption of service, malfunctioning or failure of important
circuits. These alarms require immediate response to restore or maintain system capability. Major
alarms indicate a lesser immediate or impending effect on service or system performance.
Yellow MN—Minor alarms are used for issues that do not have a serious effect on service.
Blue WN—Warning alarms are used to provide information regarding special precautions.
Grey Unreachable—Unreachable alarms are raised by the DNA when the DNA server is not able to
establish a session with the network element.
Green Clear—Clear alarms are raised by the DNA when an alarm is cleared. These alarms are raised only
if the MSAM feature is enabled on the DNA server. Users can acknowledge the clear alarms. The
acknowledged clear alarms are reported as events in the Event Log.
■ SA/NSA
The SA/NSA (Service affecting/Non-service affecting) flag indicates if the alarm is service-affecting
or non-service affecting. If an alarm is Service-affecting, it requires immediate corrective action to
restore service.
■ Ack
In order to keep track of which alarms are being worked on, alarms can be acknowledged.
Acknowledging alarms allow entry of user-defined text (acknowledged text) for the alarms. All users
who have access to the Alarm Manager can see these changes. Alarms can be re-acknowledged
at a later point, if needed.
■ Ack Text

Text entered by the user as part of acknowledging the clear alarms. This attribute is displayed
when MSAM feature is enabled.
■ Node
The node name specifies the name of the node with which the alarm is associated.
■ Node Label
The node label specified the label of the node with which the alarm is associated.
■ Category
Every alarm belongs to a category. The alarm categories available are listed below.
Table 1-3 Alarm Categories

Alarm Category Description Example
Communication Alarms Is associated with faults which impact the No Communication with OSC
communication between the modules within the Neighbor
network element and between network elements.
EMS Alarms An alarm generated by DNA. Node Unreachable
Environmental Alarms Is associated with the change in the state of the Temperature unacceptable
environmental alarm input contact.
Equipment Alarms Is associated with hardware faults. Equipment Failure
Facility Alarms Is associated with a termination point fault, the line Optical Loss of Signal
and tributary facilities, and incoming signal.
Quality of Service Alarms Is associated with the degradation in the quality of a Response time excessive
service.
Software Processing Alarms Is associated with a software or processing fault. Version mismatch
■ Object Type
The object type specifies the object with which this alarm is associated, such as, PEM, DTP CTP,
etc.
■ Source Object
The source object specifies the equipment identifier that indicates the object on which the alarm
has been raised, for example, 1-A3-T3-1, 1-NCT-2B.
■ Source Date/Time
The time indicates the time at which the alarm was raised by the network element. The time is
always displayed in the user configured time zone.
Note: If the user configured time zone is UTC, then both Source Date/Time and Source Date/
Time (UTC) will have the same values.
■ Source Date/Time (UTC)

The time indicates the time at which the alarm was raised by the network element. The time is
always displayed in UTC.
■ Probable Cause
The probable cause is the most likely reason for the occurrence of an alarm, for example, Optical
Loss of Signal. For more details on the various probable causes, refer to the respective network
element documents.
■ Ack User
Ack User indicates the ID of the user who acknowledged the alarm.
■ Circuit ID
The Circuit ID column in the Alarm Manager displays the user configured part of the Circuit ID for
the following object types: local SNC, remote SNC, local Sub SNC, remote Sub SNC, GbE Client
CTP, SDH Client CTP, SONET Client CTP, DTPCTP and VCG. For other alarms, this field is blank.
■ Direction
The direction from which the alarm has been received. The direction can be Transmit, Receive or
DirNA (Direction Not Applicable).
■ EMS Received Time
The time at which the alarm was received by the DNA. The received time here is displayed in the
user configured time zone.
Note: If the user configured time zone is UTC, then both EMS Received Time and EMS
Received Time (UTC) will have the same values.
■ EMS Received Time (UTC)

The time at which the alarm was received by the DNA. The received time here is displayed in UTC.
■ Correlation ID
Unique ID that helps in correlation of related alarms and events. This attribute is displayed when
MSAM feature is enabled.
For procedural details to use the Alarm Manager, see Using the Alarm Manager on page 1-16.
Using the Alarm Manager

For a description of attributes in the Alarm Manager, see Alarm Manager on page 1-6. The following tasks
can be performed on the Alarm Manager:
Customizing Alarm Manager View on page 1-17
Viewing Alarm Details on page 1-19
Go to Source on page 1-21
Viewing Alarm Clearing Procedure on page 1-22
Acknowledging Alarms on page 1-22

Exporting Alarms on page 1-22

Filtering Alarm Data on page 1-23
Sorting Alarm Data on page 1-31
Viewing Object Event History on page 1-32
Viewing Inventory Managers from Alarm Manager on page 1-32
Clearing Test Alarm on page 1-32
Alarm Severity Profile Settings on page 1-32
Customize Alarm Settings on page 1-37
Starting R16.1, Alarm Manager lists the alarms raised on both XTM nodes.
Figure 1-7 Alarm Manager showing XTM alarms
Right-click on a XTM alarm to perform the following:

■ Properties of the XTM alarm
■ To acknowledge alarms on page 1-22
■ Go to Source on page 1-21
■ Equipment Manager (specific to Alarms on Equipment)
■ Facility Manager (specific to Alarms on Facility)
Customizing Alarm Manager View

The Customize Columns icon in the Alarm Manager is used to select some of the alarm attributes to be
displayed in the alarm table. Alarm attributes such as EMS Received Time (UTC), Source Date/Time

(UTC), Direction, Circuit ID, Category, Ack and Ack User are displayed in the alarm table based on this
selection. Additionally, the columns displayed in the alarm table can be re-arranged in any order. These
settings are saved as part of user preferences.
To customize Alarm Table view in Alarm Manager

Step 1 In the Alarm Manager, click Customize Columns icon in the Action Panel.
The View Customization window is displayed.
Figure 1-8 View Customization
Step 2 Select the columns to be included or excluded and in the Alarm Table and move them accordingly to
the Selected Columns and UnSelected Columns area respectively using the Add-> and <-Remove
buttons.
Only EMS Received Time (UTC), Source Date/Time (UTC), Category, Circuit ID, Direction, Ack and
Ack User columns can be added or removed from the Alarm Table display.
Step 3 Re-arrange the columns in the Selected Columns area in the desired order using the Move Up and
Move Down buttons.
Step 4 Click Apply.
The Alarm Table in the Alarm Manager is refreshed to reflect the customization.
To change the toolbar positions in the Alarm Manager

In the Alarm Manager, drag and drop the toolbars to the desired position to rearrange the toolbar
positions.
Figure 1-9 Customized Toolbar Positions
Note: Changes to the toolbar positions are saved as user preferences and the settings will be
applied to all subsequent launches of Alarm Manager by the user.

Click the Restore Default Toolbar Positions icon to restore the default toolbar positions.
Figure 1-10 Default Toolbar
To change the width of the column in the Alarm Table

Step 1 Move the cursor to the column separator (the vertical line) on the right side of the column. The cursor
changes to a horizontal double-arrow.
Step 2 Click and hold while moving the mouse either left or right to adjust the column width. All columns to the
right are moved to accommodate the new column width.
The hover box displays the full content of the cells that are truncated.
Viewing Alarm Details

Alarm details are viewed from the Alarm Details window.
Note: Starting R16.1, XTM alarm properties can also be launched by right-clicking on the XTM alarm.
To view the details of an alarm
Step 1 In the Alarm Manager, select the alarm for which you would like to view the details.
Step 2 Do one of the following:
■ Double-click the alarm.
■ Right-click and select Properties.
The Alarm Details window is displayed.
Table 1-4 Alarm Details

Item Description
Summary
Source Object The name of the object associated with the alarm.
Service Affecting A field indicating if the alarm is service affecting or non-service affecting.
Severity The severity of the alarm. Can be critical, major, minor, warning, unreachable.
Source Date/Time The date and time (in user configured time zone) when the alarm was raised by
the network element or DNA.
EMS Received Time The time (in user configured time zone) at which the alarm was received by DNA.
Alarm Category The alarm category. See Alarm Categories for the alarm categories.
Node Name The name of the network element that raised the alarm.

Table 1-4 Alarm Details (continued)

Item Description
Node Label Unique identifier for the node.
Circuit Id User configured part of the Circuit ID associated with the alarm source.
Layer Rate The layer rate of the XTM alarm.
Note: This attribute is specific to XTM alarm.
Discovered Name The discoved name of the XTM node.
Note: This attribute is specific to XTM alarm.
Probable Cause The most likely reason for the occurrence of an alarm. For example, Loss of Light.
Description
Parameters
Alarm ID Unique identifier specific to an alarm, assigned by Infinera. For example,
FAC0004.
Correlation ID A system-generated ID that specifies the correlation identifier.
Direction The direction from which the alarm has been received. The direction can be
Transmit, Receive or DirNA (Direction Not Applicable).
Probable Cause A brief description of the most likely reason for the occurrence of the alarm. This
format of the probable cause matches with the TL1 description.
Custom Description The custom description of an alarm. It can be defined by the user whenever an
alarm is raised and the custom description is set on that alarm, it is displayed in
Alarm Properties.
Event Type The type of event. The type can be a Condition or Report.
Event SubType The subtype of the event. This varies based on the event type. The subtype can
be alarm or TCC.
Location The location where the alarm has been raised. For example, Near End, Far End,
Not Applicable.
Acknowledgment Information
User The login name of the user responsible for this acknowledgment.
Time The time at which the alarm was acknowledged.
Acknowledged Text
Acknowledgment User entered comments about the acknowledgment for both Infinera and XTM
Text alarms.
Additional Text
Additional Text Additional details about the alarm.

Table 1-4 Alarm Details (continued)

Item Description
Trouble-shoot Click this for a detailed description of the alarm and a procedure to clear the
alarm.
Acknowledge Click this to acknowledge the alarm. For details on how to acknowledge and
alarm, see To acknowledge alarms.
Go to Source
The source object associated with an alarm can be viewed.
Note: Starting R16.1, right-click on XTM alarm to launch ENM of that particular node on which the
alarm is present.
Figure 1-11 XTM alarm launching ENM
To go to the source of an alarm

In the Alarm Manager, right-click the alarm and select Go To Source.
The Chassis View is launched and the equipment that generated the alarm is out-lined in black. In the
equipment tree, the equipment that generated the alarm is highlighted.
When Go To Source is selected on a Trib DTF Path alarm, and only one TOM port is affected, the
alarmed TOM is highlighted. Else, a dialog is displayed, with options to choose between the affected
source objects.

Viewing Alarm Clearing Procedure

A detailed description and a procedure to clear the alarm can be viewed.
To view clearing procedure for an alarm

In the Alarm Manager, right-click the specific alarm and select Trouble-Shoot.
Acknowledging Alarms
In order to keep track of the Alarms that are being worked on, alarms can be acknowledged.
Acknowledging alarms allow entry of user-defined text (acknowledged text) for alarms.
To acknowledge alarms
■ In the Alarm Manager, right-click the alarm you want to acknowledge and select Acknowledge.
To select multiple alarms to be acknowledged, press the Ctrl key and select the alarms in the
Alarm Manager.
■ In the Alarm Manager, select the alarm you want to acknowledge and click the Acknowledge
Alarms icon in the Action Panel. To select multiple alarms to be acknowledged, press the Ctrl
key and select the alarms in the Alarm Manager.
Note: A maximum of 100 alarms can be acknowledged at once.
■ In the Alarm Details window for the specific alarm, click Acknowledge.
The Alarm Acknowledgment window is displayed.
Step 2 Enter the acknowledge text in the Acknowledged Text field and click Apply.
The Acknowledged Text can have a maximum of 256 characters.

Note: A confirmation dialog box is displayed to confirm the Acknowledgment as successful.

■ Click Replace. The previous acknowledged text, if any, is replaced with the new one.
■ Click Append. The append the acknowledged text to the previous one, if any.
Step 4 Click Ok.
The columns, Ack and Ack User are updated to indicate the alarm acknowledgment. The check-box in
the Ack column is selected and the user ID of the acknowledging user is displayed in the Ack User
column.
Exporting Alarms
Outstanding alarms on the DNA server can be exported to a tab separated value (TSV) file. This file can
be viewed using any standard text editor like vi, Notepad or Excel. There are two options to export
alarms:

■ Export Current Page—Using this option, all alarms displayed in the current page or view of the
Alarm Manager can be exported into a TSV file. In this option, only attributes that are selected to be
displayed are exported.
■ Export All Pages—Using this option, the complete list of alarms and their attributes that match the
context are exported into a TSV file. In this option, all alarm attributes (inclusive of the attributes
that are not displayed in the Alarm Manager as a result of view customization) are exported. The
attributes, Source Date/Time (user configured time zone) and EMS Received Time (user
configured time zone) are not exported.
■
Note: Irrespective of the sorting criteria in the current view of the Alarm Manager, the Alarms in
exported file are sorted by Source Date/Timeand/or EMS Received Time, by default.
To export alarms from current page

Step 1 In the Alarm Manager, click Export Current Page.
The Save dialog box is displayed.
Step 2 Navigate to the directory location where you would like to save the alarms information.
Step 3 Enter the name of the file and click Save.
A success message, indicating the directory location and the file name is displayed.
Step 4 Click Ok to close the prompt.
Note: The Export Current Page operation exports the Source Date/Time (user configured time
zone), Source Date/Time (UTC), EMS Received Time (user configured time zone) and EMS
Received Time (UTC) depending on the View Customization settings of the Alarm Manager.
To export alarms from all pages

Step 1 In the Alarm Manager, click Export All Pages.
A success message, indicating the directory location of the file is displayed.
Step 2 Click the link to download and save the file.
Step 3 Navigate to the directory location where you would like to save the alarms information.
The alarms information is now saved as a tsv file.
Step 5 Click Close to close the prompt.
Note: The Export All Pages operation does not export the Source Date/Time (user configured time
zone) and EMS Received Time (user configured time zone) attributes. The attributes, Source
Date/Time and EMS Received Time that are exported indicate the values in UTC.
Filtering Alarm Data

Filter conditions can be applied on an alarm table in the Alarm Manager. The sophisticated filter options
allow finer granularity of filtering outstanding alarms. Different instances of Alarm Managers can have

either the same filter or different filters applied. The applied filter preferences are not saved when the
Alarm Manager instance is closed.
The DNA provides two kinds of filtering options that can be used independently or in combination:
■ Custom-defined Filters—Custom-defined filters are filters defined and saved using the options
available from the Manage Filters window. For details on defining and saving custom filters, see To
create customized alarm filters. These filters are listed for selection in the Filter drop-down menu of
the Alarm Manager. The custom filters are stored in the database for application in successive
sessions unless they are deleted manually. For details on deleting custom filters, see To delete
custom-defined alarm filters on page 1-30.
Note: The customized filters will be available to the user who created them and can be used in
successive client sessions. The filters created by one user will not be accessible to the other
users.
■ Quick Filters—Quick Filters can be used to filter alarms based on specific selection from the
hierarchical tree of attributes in the Quick Filter Panel of the Alarm Manager. These filtering criteria
can be further edited and saved as a custom-defined filters that can be used in successive
sessions. Additionally, these options can be used to add to the filtering criteria of the an existing or
applied custom filter. See Quick Filters Panel on page 1-11 for a list of Quick Filtering attributes
listed in the Alarm Manager.
Note: Filtering conditions defined as part of a custom-defined filter cannot be modified using
the Quick Filter panel to exclude any of the filtering attributes; however it can be modified to
include additional filtering attributes to the custom-defined filter.
To apply custom-defined filters

The custom-defined filters are saved in the database and are listed as part of the Filter drop-down menu
in the Alarm Manager. Selection of the filter from the Filter drop-down menu refreshes the Alarm Table
after applying the selected filter.
In the Alarm Context and Filter Panel, select the filter to be applied from the Filter drop-down list.
The Alarm Table is refreshed to display the filtered alarm list. To unapply all filters, select None from
the Filter drop-down menu.
Using Manage Filters Window

Manage filters window is used to create, modify and delete custom filters. The custom filters thus defined
are saved in the database and can be used in that can be used in successive sessions.

Figure 1-12 Manage Filters
The Manage Filter window consists of:

■ Filter Name—Field used to give a name to the filter being defined. Type a name (an alpha numeric
string with no special characters; however space, - and _ are valid characters) to identify the
custom filter. While editing or deleting an existing filter, use this drop-down menu to select the filter
to be edited or deleted.
■ Quick Filters Panel— The Quick Filters panel in the manage filters window is similar to the one in
the Alarm Manager except that all alarm severities are selected by default in Quick Filters setting in
the Alarm Manager. The default setting of the Quick Filters in the Manage Filters window is none.
For further details regarding the Quick Filters panel, refer to
■ Quick Filter Summary Panel—The Quick Filter Summary Panel summarizes the quick filtering
conditions selected for the filter.
■ Advanced Filters Panel—The Advanced Filters panel is used to define granular filtering criteria for
the custom filters. It consists of:
□ Field—Select the attribute from the drop-down menu for filtering criteria definition. The drop-
down menu includes, Node Name, Probable Cause(Message), Source Date/Time, Object
Type, and Circuit Id as options for selection. The selection in this field consequently
determines the options for the other fields in the Advanced Filters panel.
□ Condition—The filtering condition in relation to the attribute selected for advanced filtering.

■ Filter Criteria—This field is used to enter or select the value of the attribute chosen in the filtering
criteria being defined. Depending on the values selected for the Field and Condition, the user can
enter or select the Filter Criteria.
For example, in case the Field is Node Name and Condition is Equals, then the Filter Criteria can
be chosen from the list generated by the system on clicking ... next to the Filter Criteria field. In
case Probable Cause is selected, then type the text in the Filter Criteria field.
If the Field is Source Date/Time and the Condition is Between, then a Date/Time range must be
selected for the Filter Criteria. Two fields for the Filter Criteria must be populated by clicking ... and
choosing the Date/Time range.
Advanced Filter Criteria

The value in the Filter Criteria field can either be selected or entered depending on the Field type
selected. In cases where a system generates a list of options from the database, the values can be
selected from this list. Else, the user can type the values in the Filter Criteria field.
Note: This procedure provides instructions to select the filtering criteria. This is only a part of the
procedure to create customized alarm filters. For a complete procedure to create customized alarm
filters or customized event filters, see To define Advanced Filter Criteria or To create customized
event filters on page 1-56 respectively.
To define Advanced Filter Criteria

Step 1 In the Manage Filters window, select appropriate values for Field and Condition.

Step 2 Click ... next to Field Criteria.

■ If the Field value is Node Name or Object Type, then the Select Nodes or Select Object Types
windows are displayed respectively.
Figure 1-13 Select Nodes/Select Object Types

Step 3 Select the desiremsadmined option(s) from the table.
To... Click...
Select an entry from the table The entry in the table and then click Select.
De-select an entry The entry in the table and then click UnSelect.
Select all entries Select All.
De-select all entries UnSelect All.
Step 4 After the selection of the Field Criteria, click Apply.

The Manage Filters window is displayed with the Field Criteria selection.
Step 5 Click Add to List to include the defined filtering criteria in the Advanced Filter Criteria Summary panel.
Step 6 Repeat Step 1 to Step 5 to include other advanced filtering criteria.
The advanced filtering criteria listed in the Advanced Filter Criteria Summary panel forms the complete list
of advanced filtering criteria for a customized alarm filter.
Note: To modify an advanced filtering criteria, select the respective entry in the Advanced Filters
Summary panel and then click Edit Criteria. The advanced filtering criteria is populated in the
Advanced Filters panel for editing. Edit the filtering criteria and click Add to List to list the modified
advanced filtering criteria in the respective summary panel. To save these changes in the customized
alarm filter, click Apply.
Note: To delete an advanced filtering criteria, select the respective entry in the Advanced Filters
Summary panel and then click Remove Criteria. To save these changes in the customized alarm
filter, click Apply.
■ Add to List—Click this after selecting the appropriate values in the advanced filters panel to
add the filtering criteria to the list.
■ Advanced Filter Summary Panel—Advanced filtering criteria for a custom filter are listed in this
panel. The advanced filters defined in the advanced filters panel are listed in this panel once
the Add to List button is clicked.
■ Advanced Filter Edit Buttons—The advanced filtering criteria can be edited or deleted by
performing the respective operation from this panel.
To delete an advanced filtering criteria, select the desired advanced filtering criteria by clicking
the respective row. Then, click Remove Criteria.
To edit an advanced filtering criteria, select the desired advanced filtering critters by clicking the
respective row. Then, click Edit Criteria. The Advanced Filters panel is populated with the values from the
selected advanced filtering criteria for editing. Edit the desired fields and click Add to List to include the
edited filtering criteria in the Advanced filter summary panel.
To create customized alarm filters

Customized alarm filters can be created using the Manager Filters window. These customized filters are
listed as part of the Filter drop-down menu in the Alarm Manager.
1. In the Alarm Manager click the Manage Filters icon in the Action Panel.
The Manage Filters window is displayed.
2. Define the filter conditions in the Quick Filters and Advanced Filters panels. For more information
regarding the Manage Filters window, see Using Manage Filters Window on page 1-24.
Note: Quick Filter section in the Alarm Manager can be saved to define a custom filter. Click the
Save As... button in the Quick Filter panel in the Alarm Manager to further define and/or save the
filter definition. The Manage Filters window is displayed. Go to Step 3 to complete the filter
creation.
3. Enter a name for the filter condition in the Filter Name field. Click Apply to save the filter condition.
A success message with a prompt to apply the filter in the Alarm Manager is displayed.
4. Do one of the following:
■ Click Yes.
The custom filter is saved and the filter is applied to the Alarm Table in the Alarm Manager. The
Alarm Table is refreshed to display the list of alarms that satisfy the filter criteria.
■ Click No. The custom filter is saved. Then, click Close to close the Manage Filters window.
The customized alarm filter is created and listed as part of the Filter drop-down menu in the Alarm
Manager.
Figure 1-14 Filter Panel
The Filter panel displays the fields as listed below:

Table 1-5 Filter Panel

Item Description
Filtered Count Specifies a count of the number of alarms filtered.
Filter drop-down menu Lists the alarm types or the connection type based on which alarms will be filtered.
Severity The severity of alarms that will be filtered. Only alarms with severity checked are
displayed.
To modify custom-defined alarm filters

The customized alarm filters can be modified from the Manage Filters window.
Step 1 In the Alarm Manager click Manage Filters icon in the Action Panel.
Step 2 Select the filter name from the drop-down menu in the Filter Name field.
Step 3 Modify the filtering criteria:
■ For more information on modifying Quick Filtering criteria, see Quick Filters Panel on page 1-11.
■ For more information on modifying Advanced Filtering criteria, see Advanced Filter Criteria on
page 1-26.
Step 4 Click Apply to save the changes.
A prompt to update the existing filter is displayed.
Step 5 Click Yes.
The filter is modified and saved. A success message with a prompt to apply the filter in the Alarm
Manager is displayed.
■ Click Yes to save and apply the filter.
The filter condition is applied and the Alarm Manager is displayed.
■ Click No to save the filter. Click Close to close the Manage Filters window.
The customized alarm filter is modified successfully.
To delete custom-defined alarm filters

The customized alarm filters can be deleted from the Manage Filters window.
Step 1 In the Alarm Manager click Manage Filters icon in the Action Panel.
Step 2 Select the filter to be deleted from the drop-down menu in the Filter Name field.
Step 3 Click Delete.
A success message is displayed.

Step 4 Click OK to exit the Manage Filters window.

The Alarm Manager is displayed.
■ If the deleted filter is active or applied in the Alarm Manager when the filter was deleted, an
additional informational message is displayed in the Alarm Manager.
Step 5 Click Ok to exit the prompt.
Sorting Alarm Data

The data displayed in the Alarm Manager can be sorted by all fields in both ascending and descending
order. Sorting is applied according to the following rules:
■ Numbers are sorted in numeric sequence.
■ Text is sorted alphabetically.
To sort alarms in tables
Figure 1-15 Sort Order

Sort Order
To sort alarms
When the Alarm Manager is launched for the first time, all the alarms are sorted on Source Date/Time
column and displayed with the latest alarms on the first page. If the Alarm Manager is closed and
subsequently re-opened without changing the sorting order, the latest alarms are displayed on first page
and the oldest alarms are displayed on the last page.
Step 1 Click any column heading to sort all the alarms based on the attribute listed in the respective column.
The sort order is identified by a triangle pointing in the direction of sort.
Step 2 To reverse the sort order, click the column heading again.
To view the latest alarms at any time, navigate to either the first page or the last page based on the
sort order.
If the Alarm Manager is closed and re-opened, the alarms will be displayed with the previously applied
sort criteria which would be saved as a preference for the current client session.

Viewing Object Event History
To view the object event history for the selected alarm

■ In the Alarm Manager, right-click on any alarm and select Object Event History.
The Event Log is displayed with the events corresponding to the selected alarm.
Viewing Inventory Managers from Alarm Manager
To launch inventory managers from the alarm manager

■ In the Alarm Manager, right-click any alarm and select the required inventory manager.
The selected inventory manager window is displayed.
Based on the selected alarm, one or more of the following inventory managers can be launched:
Cross-Connect Manager, Circuit Manager, Equipment Manager, Facility Manager, Protection
Group Manager.
Clearing Test Alarm

DNA supports triggering and clearing of a test alarm on Network elements to verify the reception of
alarms.
To clear the Test Alarm

■ In the Alarm Manager, right-click on any alarm and select Clear Test Alarm which was generated
on ME object.
The alarm is cleared from the displayed list of alarms.
Alarm Severity Profile Settings

The Alarm Severity Profile Setting (ASPS) feature allows users to modify the default severity of an alarm
type, threshold crossing alert (TCA), or threshold crossing condition (TCC) on a per managed object-type
basis. IQ NOS also supports alarms that indicate when an entity is put in the locked or maintenance
administrative state. The severity of these alarms can also be customized via the ASPS feature.
ASPS is configured via the management applications so that users can modify the default severities of
alarms according to their fault-handling strategies. Note that user modifications of severity level take
effect for the newly-generated alarms, TCAs, or TCCs; if an alarm, TCA, or TCC is currently active, its
severity is not changed by the user modification.
Note: The severity is modified per object type, and not on a per managed object basis. For example,
when the severity of OLOS of an OCG termination point is modified, the new severity is applied to
OLOS alarms reported by all OCG termination points.
Note: The severity of an environmental alarm is assigned by the user when the alarm is provisioned.
The ASPS feature cannot be used to modify the provisioned severity of environmental alarms.

However, the severity of an environmental alarm can be changed from the Alarm Input Contact
window in the management applications.
All alarms generated are assigned a factory-set default severity and service affecting value. The factory-
default values can be edited using the Alarm Severity Profile Settings (ASPS) feature.
Figure 1-16 Alarm Severity Profile Setting
The Alarm Severity Assignment Profile Settings window is divided into the following sections.
■ Profile Table—The Profile Table lists the factory set attributes as listed in Table 1-6: Alarm Severity
Profile Settings: Profile Attributes on page 1-33.
■ Profile Attributes—Attributes of the alarm selected in the Profile Table.
Table 1-6 Alarm Severity Profile Settings: Profile Attributes

Item Description
Probable Cause The most likely reason for the occurrence of an alarm.
Applies to Object The equipment that raised the alarm.
Alarm Unique ID The unique alarm ID to represent the alarm.
Category The alarm category. See Table 1-3: Alarm Categories on page 1-15 for the alarm
categories.
Type Parameter that indicates if the alarm affects service.
This field is read only. Valid values can be Service Affecting or Non-Service Affecting.
Severity The alarm severity. Alarm severity can be one of critical, major, minor, warning, event
or not reported.

Table 1-6 Alarm Severity Profile Settings: Profile Attributes (continued)

Item Description
Affects Chassis LED Check-box that enables the chassis level LED to be illuminated when this alarm is
raised.
Location The location of the network element from which the alarm has been raised. Valid
values can be one of the following: NearEnd, FarEnd, LocNA.
Direction The value can be one of: Receive, Transmit, NA.
Custom Description The custom description of an alarm. It can be defined by the user whenever an alarm
is raised and the custom description is set on that alarm, it is displayed in Alarm
Properties.
The ASPS feature can be used to do the following:

■ Customize Severity—Specifies the new alarm severity assigned to the alarm. Valid values are
Critical(CR), Major(MJ), Minor(MN), Warning(WN), Not Reported(NR) and Event(EVT).
Note: TCAs are configured as events, by default. The Severity of these TCAs can be suitably
set, to report them as alarms.
■ Affects Chassis LED—Indicates if the chassis level LED is lit or unlit when the alarm is raised. This
is not configurable for equipment alarms.
■ Restore Factory Defaults— Enables user to restore the system default setting for the Alarm
Severity Profiles. See To restore the system default setting for the Alarm Severity Profiles on page
1-35 for more details.
■ ASPS is edited from the Alarm Severity Assignment Profile Settings window.
A TCA is configured as Event, by default. The Severity of these TCAs can be suitably set, to report
them as alarms. When the severity of the TCA is changed back to an Event, a warning message
“Future TCAs will be reported as TCCs and any outstanding <TCA alarms for
TCA Type> will be cleared. Do you want to continue?” is displayed. On
confirmation, any outstanding alarms for those TCAs will be cleared from the Alarm Manager.
To edit the Alarm Severity Profile Settings

■ In the Network Topology View, right-click on the node icon. Select Admin > Alarm Severity
Profile Settings. The Alarm Severity Assignment Profile Settings window is displayed.
■ In the Node Manager, right-click a row and select Admin > Alarm Severity Profile Settings. The
Alarm Severity Assignment Profile Settings window is displayed.
Step 2 Select an alarm object. The attributes are displayed in the Profile Attributes panel.
Step 3 Select the new severity from the Severity list.
Step 4 If applicable, select Affects Chassis LED check box if the LED should be lit when the alarm is raised.
Otherwise, leave the check box blank.

Step 5 To save your changes, click Apply.

A message Alarm Severity Profile Updated Successfully is displayed.
Step 6 Click Ok to close the success message.
Step 7 Repeat Step3 to Step6 to edit other alarms to TCAs.
Step 8 Click Close to exit the Alarm Severity Assignment Profile Settings window.
Note: The Alarm Severity Assignment Profile Settings can be applied to multiple nodes using the
Multiple Node Alarm SAP Administration window. The Multiple Node Alarm SAP Administration
window is launched by clicking the Apply to Multiple Nodes in the Alarm Severity Assignment
Profile Settings window. See Multiple Node Alarm Severity Assignment Profile Settings on page 1-
35.
Note: Click Export All to save a copy of all the alarms locally in the desired location. It is saved in
the file with a extension as *.tsv.
To restore the system default setting for the Alarm Severity Profiles
■ In the Network Topology View, right-click on the node icon. Select Admin > Alarm Severity
Profile Settings. The Alarm Severity Assignment Profile Settings window is displayed.
■ In the Node Manager, right-click a row and select Admin > Alarm Severity Profile Settings. The
Alarm Severity Assignment Profile Settings window is displayed.
Step 2 Click Restore Factory Defaults. A Warning Message is displayed.
Step 3 Click Continue in the Warning Message dialog box to continue.
Multiple Node Alarm Severity Assignment Profile Settings

The DNA provides the capability for the network elements’ Alarm Severity Assignment Profile settings to
be applied to multiple network elements simultaneously. Any user with network administrative privileges
can perform this operation.
The user is allowed to choose the network elements to which the values can be applied. The list of
network elements displayed is dependent on the network elements and administrative domains
assignment. The user applying the template definition should have access to the network elements.
Note: It is recommended that this application be used for a maximum of 500 nodes to get optimal
performance.
To apply alarm severity assignment profile settings to multiple network elements

Step 1 Login to the DNA Client with network administrative privileges.
Step 2 In the Physical View, right-click the network element on which the alarm severity assignment profiles
settings have been configured and select Admin > Alarm Severity Profile Settings. The Alarm Severity
Assignment Profile Settings window is displayed. See Alarm Severity Profile Settings on page 1-32.

Step 3 In the Alarm Severity Assignment Profile Settings window, select the alarm object. The attributes are
displayed in the profile attributes panel. Select the following:
■ Select the new severity from the drop-down menu.
■ Select the Affects Chassis LED checkbox if the LED should be lit when this alarm is raised.
Otherwise leave the checkbox blank.
Step 4 Click Apply to save your changes.
Step 5 Click Apply to Multiple Nodes. The Multi Node Alarm SAP Administration window is displayed.
Step 6 The Reference ASAP Details panel displays the name of the network element from which this window
is launched. Additionally, it displays the managed objects for which the alarm severity profiles are set.
Select the managed objects whose settings is to be applied to multiple network elements. To filter the
list of managed objects, click the drop-down menu in the column heading and make the desired
selection.
Step 7 [Optional]To filter the list of network elements displayed in the Target nodes to Apply panel, select the
network element from the Filter drop-down menu. To search for a network element, enter the node
name, node type or the software version in the Search panel.
Step 8 Depending on the node type from which the dialog is launched, the Target nodes to Apply panel
displays similar type of network elements. For example, if the dialog is launched from a DTN, the
Target nodes to Apply panel displays only DTN nodes. In the Target nodes to Apply panel, select the
network elements to which the network element wide security settings or the RADIUS settings is to be
applied. Select the desired option(s) from the table:
1. To... 1. Click...
select an entry from the table ■ the entry in the table and click Select
■ the checkbox for the selected row
de-select an entry ■ the entry in the table and click UnSelect
■ the checkbox for the selected row
select all entries SelectAll
de-select all entries UnSelectAll
Step 9 Click Apply. The Bulk Configuration Status panel displays the status of the alarm severity settings on
the network elements. The information in the Bulk configuration Status panel can be filtered. Click the
drop-down arrow in the column heading based on which the filter is to be applied and make the
desired selection.
Note: If changes in an attribute present in Release 6.0 is applied to nodes running an older
release version, the Bulk configuration Status panel displays the status as In Sync.
Step 10 Repeat Step 2 to Step 9 for entries that failed.

Step 11 [Optional]To export the information displayed in the Bulk Configuration Status panel to a TSV file, click
Export Status. In the Save window, navigate to the location where the file is to be saved and click
Save.

Step 12 [Optional]To print the status of the operation just performed, click Print Status. The file status operation
can be printed to a PDF file or can be directed to the printer. The Print dialog is displayed. Select the
desired option from Name drop-down. Click Print.
Step 13 Click Close to close the Multi Node Alarm SAP Administration window.
Customize Alarm Settings

Customizable Alarm Settings feature provides the user with options to configure three timer alarms with
useful messages. The first customizable alarm is set to “Air Filter Replacement Required”, by default.
To launch the Customizable Alarm Settings window

■ In the Network Topology View, right-click on the node icon. Select Admin > Customize Alarm
Settings.
■ In the Equipment Tree, right-click a node and select Admin > Customize Alarm Settings.
■ In the Node Manager, right-click a row and select Admin > Customize Alarm Settings.
The Customizable Alarm Settings window is displayed.
Figure 1-17 Customize Alarm Settings
The Customizable Alarm Settings window is divided into the following sections.
■ Customizable Alarm Settings Table—The customizable alarm details are displayed in a tabular
form. See Table 1-7: Customizable Alarm Settings: Table on page 1-38.

Table 1-7 Customizable Alarm Settings: Table

Item Description
Probable Cause The most likely reason for the occurrence of an alarm. This can not be modified by the
user.
SA/NSA Parameter that indicates if the alarm affects service.
■ SA—Service affecting
■ NSA—Non-service affecting
Severity The alarm severity. Valid value can be one of critical, major, minor, warning or Not
Reported(NR). The default value is minor.
Alarm Declaration Time The time at which the new alarm is set to be raised. The default value is 180 days from
the current network element time.
This parameter will be displayed in the user configured time zone.
Description User defined text, up to a maximum of 64 characters, providing a description about the
alarm.
■ Description—User defined text, providing a description about the alarm.

■ Alarm Status—Parameter that indicates if the alarm is enabled or disabled. Valid values can be
Enabled, Disabled. By default, the alarm status is disabled.
■ Type—Parameter that indicates if the alarm affects service. Valid values can be Service Affecting
or Non-Service Affecting. By default, the type is Non-Service Affecting.
■ Severity—The alarm severity. Alarm severity can be one of critical, major, minor or warning. By
default, the severity is minor.
■ Affects Chassis LED—Check box that indicates if the chassis level LED is enabled, that is, if it will
be illuminated when this alarm is raised. This is disabled by default.
■ Declaration Offset Policy—Parameter that defines the number of days, from the current network
element time, when the alarm will be raised. The default value is 180 days.
■ Declaration Time—Time at which the new alarm should be raised. This can either be set to a
specific time or can be set relative to the current network element time (current network element
time plus the declaration offset policy).
■ Message—User configurable message up to a length of 128 ASCII characters, providing additional
information about the alarm.
To set and/or edit customizable alarm settings

Step 1 Launch the Customizable Alarm Settings window.
Step 2 In the Customizable Alarm Setting Table, select the alarm for which settings have to be edited.

Step 3 For a description of the attributes, see To launch the Customizable Alarm Settings window on page 1-
37. Enter or edit values for the following parameters:
■ Description—Enter a description for the alarm.
■ Alarm Status—Select the alarm status from the drop-down menu.
Note: Alarm Status must be set to Enabled, for the new alarm to be raised.
■ Type—Select the alarm type from the drop-down menu.

■ Severity—Select the alarm severity from the drop-down menu.
■ Affects Chassis LED—Select the check box to enable the chassis level LED to be illuminated
when this alarm is raised.
■ Declaration Offset Policy—Enter the value (in days) for declaration offset policy. The default
value is 180 days. On modifying this value, the second radio button in the Declaration Time
panel automatically gets updated with the new date and time.
■ Declaration Time—Time at which the new alarm should be raised. In this panel, do one of the
following:
Note: The Declaration Offset Policy value does not take effect if Choose Declaration Time
radio button is selected.
□ Select Choose Declaration Time radio button and click [...] to choose from the
calendar, a specific time at which the alarm should be raised. Here, the date and time
for selection will be in the user configured time zone.
□ Select the second radio button to raise the alarm relative to the current network
element time. The alarm will be raised at the current network element time plus the
number of days specified in the Declaration Offset Policy field. For example, if
Declaration Offset Policy is 180 days, the alarm will be raised 180 days from the
current network element time.
■ Message—Enter the required informational message to be displayed for the alarm.

Step 4 To save the changes, click Apply.
Step 5 To exit the Customizable Alarm Settings window, click Close.

1-40 Event Management
Event Management
This section describes the various components of the Event Log window and provides detailed
procedures to use it:
Event Log on page 1-40
Using the Event Log on page 1-49
Event Log
The Event Log displays the events generated by the network element and the DNA, in a tabular form.
Multiple Event Log instances can be launched simultaneously based on various contexts.
The Event Log displays up to a maximum of 2 million latest events generated by the network element and
the DNA, in a tabular form.
Note: Ensure that the configured time on the DNA Server machine is correct.
The Event Log window is used to view event details, get a list of events (Event Table) that match a
specific context, filter events based on various event attributes (criteria), create and modify customized
event filters, go to the source of an event, launch respective context-sensitive inventory managers, launch
Alarm Manager in case of alarms and export events.
To launch the Event Log

■ From the DNA Main Menu, select Fault Management > Event Log.
■ In the DNA Tree view, right-click the administrative domain icon and select Event Log.
The Event Log window is displayed. If the Event Log is launched when the initialization process
of the client is not complete, an informational message is displayed. Click Ok to close the
prompt and re-launch the Event Log after the initialization is complete.
This is a global context and all events raised in the Intelligent Transport Network are displayed.
The Event Log can also be launched from other applications, Administrative Domains or
network elements. When launched from Administrative Domains or network elements, only
events raised from the respective Administrative Domain or network element are displayed.

Figure 1-18 DNA Event Log
The Event Log consists of the following panels:

■ Event Count Summarization Panel
The Event Count Summarization Panel displays the count of the total number of events categorized
by event severity based. The count displayed corresponds to the instance of the Event Log
launched. This is based on the context and the launch point. The number embedded in these
buttons indicate the number of events in the category. The Event Count Summarization Panel is
refreshed with the change in context and/or change in filter criteria. Events can be filtered based on
the severity using the severity buttons on the Event Count Summarization Panel.
This panel consists of the following buttons:
□ Total—When the Event Log is launched, this button is activated by default indicating the total
number of events that match the context and the filter criteria selected are displayed in the
Event Table. The appearance of this button varies when the events are filtered based on
severity, indicating that only a subset of the total number of events that match the context are
displayed in the Event Table. The Event Log is dynamically refreshed.
□ CR—This button is indicative of the total number of events with severity, Critical that match
the context and the filter criteria selected in the current Event Log instance. Clicking this
button toggles the display of the Critical events in the Event Table.
□ MJ—This button is indicative of the total number of events with severity, Major, that match
button toggles the display of the Major events in the Event Table.

□ MN—This button is indicative of the total number of events with severity, Minor, that match
button toggles the display of the Minor events in the Event Table.
□ WN—This button is indicative of the total number of events with severity Warning, that match
button toggles the display of the Warning events in the Event Table.
□ Clear—This button is indicative of the total number of cleared events that match the context
and the filter criteria selected in the current Event Log instance. Clicking this button toggles
the display of the Cleared events in the Event Table.
□ Info—This button is indicative of the total number of informational events that match the
context and the filter criteria selected in the current Event Log instance. Clicking this button
toggles the display of the Informational events in the Event Table.
□ UR—This button is indicative of the total number of Unreachable events that match the
context and the filter criteria selected in the current Event Log instance. Clicking this button
toggles the display of the Unreachable events in the Event Table.
Figure 1-18: DNA Event Log on page 1-41 shows the default settings of the Event Count
Summarization Panel in a network-wide instance of the Event Log. Note that, by default, no
buttons are highlighted (selected) in this panel indicating that the events are not filtered
based on severity and complete list of events are displayed in the Event Log. The numbers
embedded in the buttons that match the severity color-code of the events indicate the
number of events in the respective category. The sum of all these numbers is displayed in
the Total button indicating the total number of events that match the context and filtering
criteria.

Figure 1-19 Event Log: Filtering based on severity from the Alarm Count Summarization Panel
Figure 1-19: Event Log: Filtering based on severity from the Alarm Count Summarization Panel on page
1-43 shows the settings of Event Count Summarization Panel in a network-wide instance of the Event
Log where Critical, Clear and Info event buttons are de-selected. With this, the Event Log is refreshed to
display all events excluding CR (Critical), Clear (Cleared) and Info (Informational events (CR, Clear and
Info buttons selected). Any change to the default settings in the Event Count Summarization Panel
highlights the Total button indicating the filter selection or a change. Click the respective buttons to select
or de-select them. Selecting the buttons at any time refreshes the Event Table to include the events in the
selected category.
■ Action Panel
The Action panel consists of shortcut icons mentioned in Table 1-8: Event Log: Action Panel
toolbar icons on page 1-44.

Table 1-8 Event Log: Action Panel toolbar icons

Customize Columns—Icon used to customize the Event Table columns. The columns to be
displayed and the order of display can be configured from the View Customization window,
launched by clicking the Customize Columns icon. For details on how to customize columns, see
To customize Event Table view in Event Log window on page 1-50.
Restore Default Toolbar Positions—Icon used to reset the customized toolbar positioning to
default positions in the Event Log window. For details on changing or resetting the toolbar
positions in the Event Log window, see To change the toolbar positions in the Event Log window
on page 1-51.
Manage Filters—Icon used to launch the Manage Filters window that aids in the definition and
modification of custom event filters. For details on working with Customized Alarm Filters, see
Filtering Event Data on page 1-55.
■ Event Context and Filter Panel

The Event Context and Filter panel displays the context and the filter applied. It provides a drop-
down menu to choose the context and filter to customize data displayed in the Event Log window.
The Event Table is refreshed based on the context and/or filter selection. The Event Context and
Filter Panel consists of:
□ Context—A drop-down menu that lists the current context of the data displayed in Event Log
window and the associated parent context. The Event Table displayed in the Event Log
window will refresh based on the context selection. The Event Table refreshes with the
change in selection of the context from the current to its parent and vise versa.
For example, if the launch point of the Event Log is a network element belonging to an
Admin Domain, the current context indicates Node and the Context drop-down menu lists the
Node and Admin Domain options for selection.
□ Filter—A drop-down menu that lists the customized event filters that can be applied in the
Event Log. If a customized event filter is applied, the filter name is displayed in this field. The
Event Table is refreshed based on the filter selection. The drop-down menu also provides an
option None to unapply the customized filters to the current view. Customized filters can be
defined using the Manage Filters window. For details on custom filter definition, refer to To
define Advanced filter criteria.
Note: The context and filter conditions chosen are applicable only to the current view.
■ Event Count and Navigation Panel

The Event Count and Navigation Panel displays the total number of events generated by the
network element, the range of number of events displayed in the current screen and allows to
customize the number of events displayed per page. Additionally, this panel includes the page
traversal buttons to ease the navigation between pages.

□ Event Count—The count of total number of events that match the selected context and filter
criteria.
□ Display Range —The event range displayed in the current page of the Event Table. The
display range can be set by typing the range in the fields next to Displaying tag in the event
count and navigation panel.
□ Page Length—A drop-down menu that allows to customize the page length is used to set the
maximum number of events to be displayed per page. The default value is 1500.
□ Page Traversal Keys—Buttons that allow to traverse between pages in the Event Log
window.
Table 1-9 Event Table: Page Traversal Keys

Buttons Description
First Page—Click this button to navigate to the first page of the Event Table.
Previous Page—Click this button to navigate to the previous page relative to the current page of the
Event Table.
Next Page—Click this button to navigate to the next page relative to the current page of the Event
Table.
Last Page—Click this button to navigate to the last page of the Event Table.
■ Suspend/Resume Updates Keys—Suspend Updates ( ) and Resume Updates ( ) buttons are

used to stop or start the Event Log from getting dynamically updated.
■ Quick Filter Panel
The Quick Filter panel in the Event Log consists of the following panels:
□ Quick Filters—Quick Filters is used to further filter the events in the Event Table. The Quick
Filter panel has a hierarchical tree with a check-box against each attribute to select the
filtering criteria.
The Quick filter panel in the Event Log is shown in Figure 1-20: Event Log: Quick Filter panel
on page 1-46:

Figure 1-20 Event Log: Quick Filter panel
The hierarchical root for the Quick Filter is indicated by the label Quick Filters. Selecting or de-selecting
the Quick Filters check-box selects or de-selects all the attributes in the Quick Filter panel. Expanding a
filtering attribute in the Quick Filter panel displays the associated categories for further definition of the
filter. By default, Severity criteria is checked in the Quick Filters panel indicating that event of all severities
are listed in the Event Table. The severity selection in the Quick Filters panel matches the respective
selection in the Event Count Summarization panel. With the default selection in the Quick Filters panel,
the Apply Filter(s) button is grayed-out unless there is a change in the filter criteria selection. Click Apply
Filter(s) button to apply the Quick Filter. Once a Quick Filter is applied, the Apply Filter(s) button is
grayed-out indicating the application of Quick Filter.
The Filter summary panel summarizes the filtering criteria selected for the view. The Event Table in the
Event Log window is refreshed only when the Apply Filter(s) button is clicked after the Quick Filter
selection.
To unapply the Quick Filter, de-select the quick filtering criteria check-box against each attribute selected
and click Apply Filter(s).

Selecting and de-selecting the check-box next to the hierarchical root, Quick Filters, selects and de-
selects all the filtering criteria attributes in the Quick Filter panel respectively.
Note: Clicking Apply Filter(s) button when no attributes are selected in the Quick Filters panel will
refresh the Event Table with a list of events that match the previously applied filter.
Note: A quick filter selection can be used to define a custom filter. See “To create customized alarm
filters” on page 1-37.
Note: The Quick Filters applied are applicable only for the current view.
■ Quick Filter Summary Panel—The Quick Filter Summary Panel summarizes the quick filter
conditions selected for the view.
■ Event Table
The Event Table provides a tabular list of events raised by the network element and the DNA
server. By default, the events are in chronological order with the most recent event at the top of the
list. The event list is displayed with the following fields: .Object Type, Circuit ID, Severity, Node
Name, Node Label, Source Object, Event Type, Event Sub Type, EMS Received Time, EMS
Received Time (UTC), Source Date/Time, Source Date/Time (UTC), Message, Changed Variables,
Node Id and Category. The view can be customized to include the desired fields. These columns in
the Event Table can be rearranged either by dragging and dropping the columns in the desired
order or using the View Customization window. For details on View Customization window, see To
customize Event Table view in Event Log window on page 1-50. Further, the column width can be
resized and the order of fields displayed can be rearranged for convenience. See Sorting Event
Data on page 1-57 and Viewing Object Event History on page 1-32 for detailed procedures.
■ Object Type
The object type specifies the type of equipment that initiated the alarm. For example, if the event is
a power failure, the object type is displayed as PEM.
■ Circuit ID
The Circuit ID column in the Event Log displays the user configured part of the Circuit ID for the
following object types: local SNC, remote SNC, local Sub SNC, remote Sub SNC, GbE Client CTP,
SDH Client CTP, SONET Client CTP, DTPCTP and VCG. For other events, this field is blank.
■ Sev
The severity of an event provides an indication of how the capability of the component affected is
perceived. Severity levels are represented from most severe to least severe as Critical, Major,
Minor, Warning, Clear, Information, and Unreachable.The severity of events are indicated by a
color code for easy differentiation between important alarms and information alarms. By default,
alarms are indicated by the colors as listed below.

Table 1-10 Color coding and severity mapping

Color Severity Description
Red CR—Critical alarms indicate a severe, service-affecting condition for which immediate corrective
action is required to restore service.
Orange MJ—Major alarms indicate a serious disruption of service, malfunctioning or failure of important
circuits. These alarms require immediate response to restore or maintain system capability. Major
alarms indicate a lesser immediate or impending effect on service or system performance.
Yellow MN—Minor alarms are used for issues that do not have a serious effect on service.
Blue WN—Warning alarms are used to provide information regarding special precautions.
White Info—Information on the events that are raised.
Grey Unreachable—Unreachable events are raised by the DNA when the DNA server is not able to
establish a session with the network element.
Green Clear—Clear events are raised when a clearing condition is met and an event is cleared.
White Info—Information events are raised by the DNA to provide information regarding events
generated. No corrective action is required when such events are raised.
■ Node
The node name specifies the name of the network element that raised the event.
■ Node Label
The node label specifies the label of the network element that raised the event.
■ Source Object
The source object is an equipment identifier that indicates where the event was generated. For
example, if the event is generated from PEM 1, the source object is displayed as 1-IOSHELF-
PEM1.
■ Object Type
The object type specifies the type of equipment that initiated the alarm. For example, if the event is
a power failure, the object type is displayed as PEM.
■ Event Type
The Event Type displays the event type based on the action performed.
■ Event Sub Type
The Event subtype displays the event sub type based on the action performed.
■ Source Date/Time
The time indicates the time at which the event was raised by the network element. The time is
always displayed in the user configured time zone.

Note: If the user configured time zone is UTC, then both Source Date/Time and Source Date/
Time (UTC) will have the same values.
■ Message
The Message column displays additional information about the event that briefly describes the
cause of the event.
■ Changed Variables
The Changed Variables column displays the attribute(s) that changed and the new value(s).
For example, the Changed Variable ‘AdministrativeState = Maintenance’ indicates that the
Administrative State of the circuit pack denoted as the Source Object has been changed to
Maintenance.
■ Circuit ID
User configured part of the Circuit ID, associated with the event, for the following object types: local
SNC, remote SNC, local Sub SNC, remote Sub SNC, GbE Client CTP, SDH Client CTP, SONET
Client CTP, DTPCTP and VCG. For other events, this field is blank.
■ User Name—The login name of the user.
■ Proxied User Name—The name of the proxy user.
■ EMS Received Time—The time at which the event was received by the DNA. The received time
here is displayed in the user configured time zone.
Note: If the user configured time zone is UTC, then both EMS Received Time and EMS
Received Time (UTC) will have the same values.
■ Source Date/Time (UTC)

The time indicates the time at which the event was raised by the network element. The time is
always displayed in UTC.
■ EMS Received Time (UTC)—The time at which the event was received by the DNA. The received
time here is displayed in UTC.
For procedures to use the Event Log, see Using the Event Log on page 1-49.
Using the Event Log

For description of attributes in the Event Log, see Event Log on page 1-40. The following tasks can be
performed on the event log:
Customizing Event Log View on page 1-50
Viewing Event Details on page 1-51
Go To Source on page 1-54
Exporting Events on page 1-54
Filtering Event Data on page 1-55

Using Manage Filters window for Event Logs on page 1-56

Sorting Event Data on page 1-57
Viewing Event-specific Alarm Details on page 1-58
Viewing Inventory Managers from Event Log on page 1-58
Go To Source Endpoint on page 1-58
Go To Destination Endpoint on page 1-59
Customizing Event Log View

The Customize Columns icon in the Event Log window is used to select some of the event attributes to be
displayed in the Event Table. Event attributes such as Event Type, Source Date/Time (UTC), EMS
Received Time (UTC), Event SubType, Message, Changed Variables, Circuit ID, User Name and Proxied
User Name are displayed in the Event Table based on this selection. Additionally, the columns displayed
in the Event Table can be re-arranged in any order. These settings are saved as part of user preferences.
To customize Event Table view in Event Log window

Step 1 In the Event Log window, click Customize Columns icon in the Action Panel.
Figure 1-21 Event Log: View Customization

Step 2 Select the columns to be included or excluded and in the Event Table and move them accordingly to
the Selected Columns and UnSelected Columns area respectively using the Add-> and <-Remove
buttons.
Only Event Type, EMS Received Time (UTC), Source Date/Time (UTC), Event SubType, Message,
Changed Variables, Circuit ID, User Name and Proxied User Name columns can be added or
removed from the Event Table display.
Move Down buttons.
Step 4 Click Apply.
The Event Table in the Event Log window is refreshed to reflect the customization.
To change the toolbar positions in the Event Log window

Step 1 In the Event Log window, drag and drop the toolbars to the desired position to re-arrange the toolbar
positions.
Figure 1-22 Event Log: Customized Toolbar Positions
Note: Changes to the toolbar positions are saved as user preferences and the settings will be
applied to all subsequent launches of Event Logs by the user.
Step 2 Click the Restore Default Toolbar Positions icon to restore the default toolbar positions.
Figure 1-23 Event Log: Default Toolbar Positions
To change the width of the columns in the Event Table

Viewing Event Details

Event details are viewed from the Event Details window.
To view the details of an event

Step 1 In the Event Log window, select the event for which you would like to view the details.


■ Double-click the event.
■ Right-click and select Properties.
The Event Details window is displayed.
Step 3 Click Close to close the Event Details window.
Figure 1-24 EventThe Detailsimage is
Table 1-1 Event Details

Item Description
Summary
Source Object The name of the identified object associated with the event.
Service Affecting A flag indicating if the current event can disrupt service or not. Value can be one of
SA, NSA, or Not Applicable.
Severity The severity of the event.
Source Date/Time The date and time (in user configured time zone) when the event was generated.
Received Time The date and time (in user configured time zone) when the event was received.
Alarm Category The alarm category. This is not applicable for informational events. For DNA raised
events, the alarm category is DNA Events.
Node Name The name of the network element that raised the event.
Node Label The label of the network element that raised the event.
Circuit ID User configured part of the Circuit ID, associated with the event, for specific object
types.
Message Information about the event that indicates the cause of event generation.

Table 1-1 Event Details (continued)

Item Description
Parameters
Event Type The type of event. Valid values can be one of Condition, Report, or Update Event
Event Sub Type The sub-type of the event. This varies based on the event type. Valid values can be
one of the following:
■ TCE, Admin, Audit or Security for Report Events
■ StandingConditions or TCC for Condition Events
■ Alarms
Operation Status The status of the operation that was performed. Status can be Success or Fail. It is
displayed only for Audit Events.
Operation Name The operation performed that resulted in event generation. Displayed only for audit
events.
Client Host Machine The terminal from which the DNA client is launched. It is displayed only for Audit
Events.
User Name The login name of the user.
Proxied User Name The name of the proxy user.
Changed Variables This tab lists the changed attributes with the new value(s).
Additional Text
Additional Text This tab displays additional details for the event.
Acknowledgment Information
Acknowledgment This tab displays the acknowledgment information for the event
Information
To change the width of the columns in the Event Table


Go To Source
To go to the source of an event

In the Event Log, right-click the event and select Go To Source. The Chassis View is launched and the
equipment that generated the event is highlighted.
When Go To Source is selected on a Trib DTF Path event, and only one TOM port is affected, the
corresponding TOM is highlighted. Otherwise, a dialog is displayed, with options to choose between
the source objects.
Exporting Events
Events in the Event Log can be exported to a tab separated value (TSV) file. This file can be viewed
using any standard text editor such as vi, Notepad or Excel. There are two options to export alarms.
■ Export Current Page—Using this option, all events displayed in the current page or view of the
Event Log can be exported into a TSV file. In this option, only attributes that are selected to be
displayed are exported.
■ Export All Pages—Using this option, the complete list of alarms and their attributes that match the
context are exported into a TSV file. In this option, all event attributes (inclusive of the attributes
that are not displayed in the Event Log as a result of view customization) are exported. The
attributes, Source Date/Time (user configured time zone) and EMS Received Time (user
configured time zone) are not exported.
■
Note: Irrespective of the sorting criteria in the current view of the Event Log window, the Events
in exported file are sorted by Source Date/Timeand/or EMS Received Time, by default.
To export events from current page

Step 1 In the Event Log window, click Export Current Page.
Step 2 Navigate to the directory location where you would like to save the events information.
A success message, indicating the directory location and the file name is displayed.
Note: The Export Current Page operation exports the Source Date/Time (user configured time
zone), Source Date/Time (UTC), EMS Received Time (user configured time zone) and EMS
Received Time (UTC) depending on the View Customization settings of the Event Log.

To export events from all pages

Step 1 In the Event Log window, click Export All Page.
A success message, indicating the directory location of the file is displayed.
Figure 1-25 Export Events: Status Message
Step 2 Click the link to download and save the file.

Step 3 Navigate to the directory location where you would like to save the events information.
The events information is now saved as a tsv file.
Step 5 Click Close to close the prompt.
Note: The Export All Pages operation does not export the Source Date/Time (user configured time
zone) and EMS Received Time (user configured time zone) attributes. The attributes, Source
Date/Time and EMS Received Time that are exported indicate the values in UTC.
Filtering Event Data
Note: Filter conditions can be applied to Event Tables in the Event Logs. The sophisticated filter
options allow finer granularity of events filtering. Different instances of Event Logs can have either the
same filter or different filters applied. Filters are automatically cleared when the event Log window is
closed. Custom-defined Filters—Custom-defined filters are filters defined and saved using the options
available from the Manage Filters window. These filters are listed for selection in the Filter drop-down
menu of the Event Log window. The customized filters are stored in the database for application in
successive sessions unless they are deleted manually. The customized filters will be available to the
user who created them and can be used in successive client sessions. The filters created by one user
will not be accessible to the other users.
■ Quick Filters—Quick Filters can be used to filter events based on specific selection from the
hierarchical tree of attributes in the Quick Filter Panel of the Event Log. These filtering criteria can
be further edited and saved as a customized filters that can be used in successive sessions.
Additionally, these options can be used to add to the filtering criteria of the an existing or applied
custom filter.
Note: Filtering conditions defined as part of a custom-defined filter cannot be modified using the
Quick Filter panel to exclude any of the filtering attributes; however it can be modified to include
additional filtering attributes.

To apply custom-defined filters

The custom-defined filters are saved in the database and are listed as part of the Filter drop-down menu
in the Event Log window. Selection of the filter from the Filter drop-down menu refreshes the Event Table
after applying the selected filter.
In the Event Context and Filter Panel, select the filter to be applied from the Filter drop-down list.
The Event Table is refreshed to display the filtered event list.
To unapply all filters, select None from the Filter drop-down menu.
Using Manage Filters window for Event Logs

Manage filters window associated with the Event Logs is used to create, modify and delete custom filters.
The custom filters thus defined are saved in the database and can be used in that can be used in
successive sessions. For details on working with the Manage Filter window see Using Manage Filters
Window on page 1-24.
Note: Working with Manage Filters window associated with the Events Log is similar to the one
associated with the Alarm Manager. Correlate instances of Alarm Manager to Event Logs in the
section.
To create customized event filters

Customized event filte,rs can be created using the Manager Filters window. These customized filters are
listed as part of the Filter drop-down menu in the Event Log.
Step 1 In the Event Log window, click the Manage Filters icon in the Action Panel.
Step 2 Define the filter conditions in the Quick Filters and Advanced Filters panels. For more information
regarding the Manage Filters window, see Using Manage Filters Window on page 1-24.
Note: Quick Filter selection in the Event Log window can be saved to define a custom filter. Click
the Save As... button in the Quick Filter panel in the Event Log window to further define and/or
save the filter definition. The Manage Filters window is displayed. Go to Step 3 to complete the
filter creation.
Step 3 Enter a name for the filter condition in the Filter Name field. Click Apply to save the filter condition.
A success message with a prompt to apply the filter in the Event Log window is displayed.
■ Click Yes.
The custom filter is saved and the filter is applied to the Event Table in the Event Log window.
The Event Table is refreshed to display the list of events that satisfy the filter criteria.
■ Click No. The custom filter is saved. Then, click Close to close the Manage Filters window.
The customized event filter is saved and listed as part of the Filter drop-down menu in the Event
Log window.

To modify custom-defined event filters

The customized event filters can be modified from the Manage Filters window.
Step 1 In the Event Log window click Manage Filters icon in the Action Panel.
Step 2 Select the filter name from the drop-down menu in the Filter Name field.
Step 3 Modify the filtering criteria:
■ For more information on modifying Quick Filtering criteria, see Quick Filters Panel on page 1-11.
■ For more information on modifying Advanced Filtering criteria, see Advanced Filter Criteria on
page 1-26.
Step 4 Click Apply to save the changes.
A prompt to update the existing filter is displayed.
Step 5 Click Yes.
The filter is modified and saved. A success message with a prompt to apply the filter in the Event Log
window is displayed.
■ Click Yes to save and apply the filter.
The filter condition is applied and the Event Log window is displayed.
■ Click No to save the filter. Click Close to close the Manage Filters window.
The customized event filter is modified successfully.
To delete custom-defined event filters

The customized event filters can be deleted from the Manage Filters window.
Step 1 In the Event Log window click Manage Filters icon in the Action Panel.
Step 2 Select the filter to be deleted from the drop-down menu in the Filter Name field.
Step 3 Click Delete.
A success message is displayed.
Step 4 Click OK to exit the Manage Filters window.
The Event Log window is displayed.
■ If the deleted filter is active or applied in the Event Log window when the filter was deleted, an
additional informational message is displayed in the Event Log window.
Step 5 Click OK to exit the prompt.
Sorting Event Data

The data displayed in the Event Log can be sorted by any column in either ascending or descending
order. Sorting is applied according to the following rules:

■ Numbers are sorted in numeric sequence.

■ Text is sorted by ASCII sequence.
To sort events
When the Event Log is launched for the first time, all the events (up to a maximum of 500,000) are sorted
on Source Date/Time (in the user configured time zone) and displayed with the latest events on the last
page. If the Event Log is closed and subsequently re-opened without changing the sorting order, the
latest events are displayed on first page and the oldest events are displayed on the last page, irrespective
of the network element time. Now, if the network element time is set back, newly occurring events on that
network element are displayed on the first page and would not appear sorted on Source Date/Time.
Step 1 Click any column heading to sort all the events. The sort order is identified by a triangle pointing in the
direction of sort.
Step 2 To reverse the sort order, click the column heading again.
To view the latest events at any time, navigate to either the first page or the last page based on the
sort order. If the sort order is ascending, the latest events are displayed on the last row of the last
page. If the sort order is descending, the latest events are displayed on the first row of the first page.
If the Event Log is closed and re-opened, the events will be displayed with the previously applied sort
criteria.
Viewing Event-specific Alarm Details

The alarm details corresponding to the alarms listed in the Event Log can be viewed. The Event Sub
Type field in the Event Log indicates if its an alarm. You can view the details of these alarms.
To view alarm details for an alarm listed in the Event Log

■ In the Event Log, right-click any alarm and select Alarms.
The Alarm Manager is displayed with the alarm corresponding to the selected event.
Viewing Inventory Managers from Event Log

Based on the selected event, one or more of the following inventory managers can be launched: Cross-
Connect Manager, Circuit Manager, Equipment Manager, Facility Manager, Protection Group Manager.
To launch inventory managers from the event log

■ In the Event Log, right-click any event and select the required inventory manager.
The selected inventory manager window is displayed.
Go To Source Endpoint
This option is applicable only to Cross-Connect events.
To go to the source endpoint of a Cross-Connect from the event log

■ In the Event Log, right-click the specific Cross-Connect event and select Go to Source Endpoint.
The Chassis View is displayed with

□ the source TOM highlighted, if the source endpoint of the Cross-Connect is a Trib PTP.
□ the source DLM or XLM highlighted, if the source endpoint of the Connect-Connect is a
Channel.
Go To Destination Endpoint
This option is applicable only to Cross-Connect events.
To go to the destination endpoint of a Cross-Connect from the event log

■ In the Event Log, right-click the specific Cross-Connect event and select Go to Destination
Endpoint.
The Chassis View is displayed with
□ the destination TOM highlighted, if the destination endpoint of the Cross-Connect is a Trib
PTP.
□ the destination DLM or XLM highlighted, if the destination endpoint of the Connect-Connect
is a Channel.


CHAPTER 2
Environmental Alarms and Control
Environmental alarms are those triggered by an abnormal condition at the network element site. The
network elements support input and output alarm contacts to monitor and control the customer’s
equipment. Alarm input contacts allow you to connect external equipment (reactors), such as fire, alarm
detector, high temperature detector, door open, and so on, to the network element. When the connected
equipment triggers an input contact point, it raises an alarm with an alarm message and severity as
configured by the user. Alarm output contacts allow you to connect external equipment to the network
element. The network element can trigger the operation of the connected external equipment. Refer to
the DTN and DTN-X System Description Guide for a description of the contacts provided by the network
elements.
Additionally, the network elements support Alarm Cutoff (ACO) to mute the current audible alarms. This
chapter describes procedures to configure alarm input contacts, alarm output contacts, and to enable the
Alarm Cutoff in the following sections:
Configuring Alarm Input Contacts for DTC/MTC-9/MTC-6/OTC/ATC on page 2-2
Configuring Alarm Input Contacts for MTC-6/MTC-9/OTC Third Party AC Rectifier on page 2-4
Configuring Alarm Input Contacts for XTC on page 2-7
Configuring Alarm Input Contacts for XTC-10 Third Party AC Rectifier on page 2-9
Configuring Alarm Input Contacts for XTC-2/XTC-2E on page 2-11
Configuring Alarm Output Contacts for DTC/MTC-6/MTC-9/OTC/ATC on page 2-13
Configuring Alarm Output Contacts for XTC on page 2-14
Configuring Alarm Output Contacts for XTC2/XTC-2E on page 2-16
Alarm Cutoff on page 2-18

2-2
Configuring Alarm Input Contacts for DTC/MTC-9/MTC-6/OTC/ATC

The DTN and Optical Line Amplifier supports sixteen user-configurable input contacts and MTC-6/MTC-9
supports six user-configurable input contacts while the ATN supports four user-configurable input contact
sets, with two contacts per set. Users can configure these input contacts which when activated, resulting
in the generation of a customized alarm. The contacts can be configured from the Alarm Input Contacts
Properties window.
In addition, DTC/MTC-9/MTC-6/OTC/ATC has one ACO input contact set, reserved for ACO input from
an external chassis.
Note: Though the hardware supports nineteen input alarm contacts in the DTN, FlexROADM and
Optical Amplifier, contacts 17, 18 and 19 are not being supported.
To launch Alarm Input Contacts Properties window

Perform one of the following:
■ In the Chassis View, right-click just below the title bar (next to the ACO-OFF button) and select
Alarm Input Contacts.
■ In the Equipment Tree of the Chassis View, right-click the chassis and select Alarm Input
Contacts.
The Alarm Input Contacts Properties window is divided into the panels as described below:
■ Input Alarm Contact Table
Table 2-1 Input Alarm Contact Table

Item Description
Label Assign an identifier, a character string with a maximum of 128 characters, to the input
contact.
Contact Unique identifier assigned to the input contact.
Probable Cause Message The probable cause to be used in the alarm report when an alarm input is triggered by
the external equipment. Users can give meaningful causes depending on the
connected external equipment. The Probable Cause Message is a string and can
have a maximum of 128 characters.
Enabled Flag that specifies if the input closure contact is enabled via management interface
like DNA. The value can be either True or False.
Severity The severity of the alarm. Can be one of critical, major, minor, informational or
indeterminate. Once the severity for the alarm has been assigned, it cannot be
modified using the Alarm Severity Profile Settings. See Fault Management on page 1-
1 for more information on alarm severities.
Position

Environmental Alarms and Control 2-3
Table 2-1 Input Alarm Contact Table (continued)

Item Description
Normal This is a user-defined field that specifies the position of the input contact under normal
condition. If the input contact position is different from the normal position, an alarm is
reported for this input contact. The value can be one of NormalyClosed or
NormallyOpen.
Current Current position of the input contact. Valid values can be one of Open or Closed.
Alarm Type The type of alarm displayed.
■ Configurable Parameters Panel—Fields in this panel are displayed only if a corresponding

selection is made in the Input Alarm Contact Table.
To configure input alarm contacts from DTC chassis

Step 1 Launch the Alarm Input Contacts Properties window.
Step 2 Select the input alarm contact that you want to configure in the Input Alarm Contact Table. The
configurable parameters are displayed.
Step 3 Enter and edit values for the parameters: Label and Probable Cause Message.
Step 4 Select values for the parameters Alarm Type, Enabled, Severity and Normal from the drop down
menu.
Step 6 Repeat Step 2 through Step 4 for each additional input contact.
Step 7 When you are done, click Close to exit the Alarm Input Contacts Properties window.

2-4 Configuring Alarm Input Contacts for MTC-6/MTC-9/OTC Third Party AC Rectifier
Configuring Alarm Input Contacts for MTC-6/MTC-9/OTC Third

Party AC Rectifier
The MTC-6/MTC-9 Third Party AC Rectifier is an AC-based solution with rectifiers with redundant output
that is distributed to individual PEMs in the chassis. The existing DC PEMs shall continue to be installed
on the chassis and the AC rectifiers are mounted outside the chassis and its rectified output fed into the
PEMs.
The AC rectifier unit alarm relay outputs shall be connected to the chassis general purpose alarm contact
inputs to be able to raise external control related alarms. The existing method of configuring the external
controls shall be used to report the alarms on the AC rectifier.
To configure input alarm contacts for PTIN-1 on MTC-6/MTC-9/OTC

Step 3 Enter the values for the following parameters:—
■ Label—Rectifier Power Major Alarm Shelf A
■ Probable Cause Message—Rectifier Power Major Alarm Shelf A
Step 4 Select values for the following parameters from the drop down menu:
■ Alarm Type—Rectifier Failure
■ Enable—True
■ Severity—Major
■ Normal—Closed
Step 6 Click Close to exit the Alarm Input Contacts Properties window.

Step 3 Enter the values for the following parameters:
■ Label—Rectifier Power Minor Alarm Shelf A
■ Probable Cause Message—Rectifier Power Minor Alarm Shelf A

■ Enable—True
■ Severity—Minor
■ Normal—Closed
Step 1 Launch the Alarm Input Contacts Properties window

■ Label—Rectifier/Controller Alarm Shelf A
■ Probable Cause Message—Rectifier/Controller Alarm Shelf A
■ Enable—True
■ Normal—Closed
Note: This alarm may be reported as either Major or Minor depending on the actual alarm
condition reported on the rectifier.


■ Label —Rectifier Power Major Alarm Shelf B
■ Probable Cause Message—Rectifier Power Major Alarm Shelf B

■ Enable—True
■ Normal—Closed

■ Label —Rectifier Power Minor Alarm Shelf B
■ Probable Cause Message—Rectifier Power Minor Alarm Shelf B
■ Enable—True
■ Normal—Closed

■ Label—Rectifier/Controller Alarm Shelf B
■ Probable Cause Message—Rectifier/Controller Alarm Shelf B

■ Enable—True
■ Normal—Closed
Note: This alarm may be reported as either Major or Minor depending on the actual alarm
condition reported on the rectifier.

Configuring Alarm Input Contacts for XTC

The DTN-X supports twenty alarm input contact sets, of which eighteen shall be user customizable and
three shall be reserved for driving the Critical/Major/Minor bay LEDs. Users can configure these input
contacts which when activated, resulting in the generation of a customized alarm. The contacts can be
configured from the Alarm Input Contacts Properties window.
In addition, DTN-X has one ACO input contact set, reserved for ACO input from an external chassis.
The alarm input pins on the XTC-10 for the critical, major and minor bay LED alarms are technically
unused, since there can be no other chassis present in the bay as the XTC-10 fits a single bay. It is also
recommended not to use those pins on a XTC-10 Chassis. The ACO pin can be used however.
Two XTC-4s on the other hand should be able to be fitted in a single bay and hence the alarm input of
one of the chassis can be used as the bay LED driver of the other.

Contacts.
The Alarm Input Contacts Properties window is displayed.


Item Description
contact.
Position
NormallyOpen.

To configure input alarm contacts

menu.

Configuring Alarm Input Contacts for XTC-10 Third Party AC

Rectifier
The XTC-10 Third Party AC Rectifier (PON ICS-RCTFR+) is an AC-based power supply option for
customer deployments that utilize AC input power. This third party power solution consists of two
individual rectifier shelves (A and B) and a rectifier switch box. Each rectifier shelf contains a rectifier shelf
controller card and up to four rectifiers. The rectifier shelf controller card controls the DC output, power
thresholds and the alarm functionality. Some units were shipped from the vendor in a default state without
the recommended Infinera specified configurations applied. Follow the recommended steps in this FSB to
prevent service impact in the XTC-10 chassis carrying traffic.
To configure input alarm contacts for PTIN-1

Step 3 Enter the values for the following parameters:—
■ Label—XTC-10 Rectifier Power Minor Alarm Shelf A
■ Probable Cause Message—XTC-10 Rectifier Power Minor Alarm Shelf A
■ Enable—True
■ Normal—Closed

■ Label—XTC-10 Rectifier Power Major Alarm Shelf A
■ Probable Cause Message—XTC-10 Rectifier Power Major Alarm Shelf A

2-10 Configuring Alarm Input Contacts for XTC-10 Third Party AC Rectifier
■ Enable—True
■ Normal—Closed
Step 1 Launch the Alarm Input Contacts Properties window

■ Label—XTC-10 Rectifier Power Minor Alarm Shelf B
■ Probable Cause Message—XTC-10 Rectifier Power Minor Alarm Shelf B
■ Enable—True
■ Normal—Closed

■ Label XTC—10 Rectifier Power Major Alarm Shelf B
■ Probable Cause Message—XTC-10 Rectifier Power Major Alarm Shelf B

■ Enable—True
■ Normal—Closed
Configuring Alarm Input Contacts for XTC-2/XTC-2E

The XTC-2/XTC-2E supports six general purpose alarm input contact sets. Users can configure these
input contacts which when activated, results in the generation of a customized alarm. The contacts can
be configured from the Alarm Input Contacts Properties window.
In addition, XTC-2/XTC-2E has one ACO input contact set, reserved for ACO input from an external
chassis.

Contacts.
The Alarm Input Contacts Properties window is displayed.
Figure 2-1 Launch Alarm Input Contact from XTC-2/XTC-2E

Configure Input Alarm Contacts for XTC-2/XTC-2E Chassis

Item Description
contact.
Position

Table 2-3 Input Alarm Contact Table (continued)

Item Description
NormallyOpen.

To configure input alarm contacts

menu.
Configuring Alarm Output Contacts for DTC/MTC-6/MTC-9/OTC/ATC

The DTN and Optical Line Amplifiers support ten user-configurable output contacts where as the MTC-6/
MTC-9 supports four user-configurable output contacts. Each output has the following contacts:
■ NO (normally open)
■ NC (normally closed)
■ CM (common)
Under normal conditions, the NO output is open and the NC output is closed. When the output
contact is enabled, the NO output is closed and the NC output is opened. Users can enable or
disable (normal condition) the output contacts either manually or automatically on occurrence of a
user-defined alarm condition. The Alarm Output Properties window is used to manually control the
output contacts or set the trigger for the automatic operation.

To launch Alarm Output Contacts Properties window

Alarm Output Contacts.
■ In the Equipment Tree of the Chassis View, right-click the chassis and select Alarm Output
Contacts.
The Alarm Output Contacts Properties window is divided into the panels as described below:
■ Output Alarm Contact Table
Table 2-4 Output Alarm Contact Table

Item Description
Contact Unique identifier assigned to each output contact.
Control Type An alarm with this probable cause triggers the output contacts if the operation
mode is set to Automatic.
Operation Mode The operational mode of operation. Valid values can be one of the following:
■ MAN_ON— Manual on. The output contact is enabled. NO output is
closed and NC output is opened.
■ MAN_OFF— Manual off. The output contact is disabled. NO is
opened and NC is closed.
Current Current position of the equipment. Valid values can be one of Open or Closed.
■ Configurable Parameters Panel — Fields in this panel are displayed only if a selection is made in
the Output Alarm Contact Table.
To configure output alarm contacts

Step 1 Launch the Alarm Output Contacts Properties window.
Step 2 Select the alarm contact you want to edit in the Output Alarm Contact table.
Step 3 Select values for the parameters: Control Type and Operation Mode form the drop down menu.
Step 5 Repeat Step 2 through Step 4 for each additional output contact.
Step 6 When you are done, click Close to exit the Alarm Output Contacts Properties window.
Configuring Alarm Output Contacts for XTC

The DTN-X supports 42 alarm output contact sets, of which twelve shall be user customizable and three
shall be reserved for driving the Critical/Major/Minor bay LEDs and one for ACO. Each output has the
following contacts:

■ CM (common)
In case of Bay LED alarm support for XTC-4, the system shall support the mapping of Critical,
Major and Minor Alarm output pins consistent with the support in a DTC chassis to maintain
consistency in the contact pins across different types of chassis. However it is also accepted if the
pin mapping with the DTC/MTC chassis is not mapped consistently.

Contacts.

Item Description


Configuring Alarm Output Contacts for XTC2/XTC-2E

The XTC-2/XTC-2E supports 14 alarm output contact sets, of which four shall be user customizable and
ten shall be reserved for driving the Critical/Major/Minor bay LEDs and one for ACO. Each output has the
following contacts:
■ CM (common)
In case of Bay LED alarm support for XTC-2/XTC-2E, the system shall support the mapping of
Critical, Major and Minor Alarm output pins consistent with the support in a DTC chassis to
maintain consistency in the contact pins across different types of chassis. However it is also
accepted if the pin mapping with the XTC-2/XTC-2E chassis is not mapped consistently.

Contacts.
The Alarm Output Contacts Properties window is displayed.

Item Description

Table 2-6 Output Alarm Contact Table (continued)

Item Description


2-18 Alarm Cutoff
Alarm Cutoff
The Intelligent Transport Network system provides a feature to acknowledge an alarm condition and turn
off the audible indicator. The ACO push button is used to mute the current audible alarms. Users can
manually operate the ACO button located on the IOTAP panel for the XTC-10, XTC-4 and MTC-9 chassis
or operate it remotely through the DNA interface. When the ACO is enabled, all outstanding audio alarms
are turned off and the ACO LED on the I/O panel is lit. The ACO LED indicates that one or more audible
alarms are present, but the audible indicators have been suppressed. The ACO LED is turned off when
the silenced audible alarms are cleared. The alarm acknowledgment by the user does not change the
ACO LED state.
Note: The ACO LED state is not shown in the DNA user interface.
Enabling ACO
To set ACO to ON
■ In the Chassis View, right-click just below the title bar (next to the ACO-OFF/ACO-ON button) and
select Switch on ACO State. A Warning Message is displayed prompting the user to confirm the
suppression of all current audible alarms.

CHAPTER 3
DTN/DTN-X/FlexROADM
Diagnostics
Network problems can severely damage the productivity of a network. Infinera Intelligent Transport
Networks provide troubleshooting tools to quickly and easily isolate network problems. All diagnostic tests
require the corresponding managed object to be in Maintenance state. This chapter describes the
troubleshooting tools that can be used to troubleshoot the network element and the Infinera Intelligent
Transport Network. This chapter is divided into the following sections:
Overview on page 3-2
Loopbacks in DTN and DTN-X on page 3-3
Path Loss Check in FlexROADMs on page 3-10
Trace Messaging in DTN and DTN-X on page 3-12
PRBS Test in DTN and DTN-X on page 3-20
Test Signal Generation for Fiber Channel Clients in DTN on page 3-34
GbE Client Termination Point Tests in DTN and DTN-X on page 3-35
Lamp Testing in DTN, DTN-X and FlexROADM on page 3-39
Optical Test Access Ports on page 3-41

3-2 Overview
Overview
Diagnostics is one of the key components of the overall fault management solution provided by Infinera
Intelligent Transport Networking systems. The diagnostics function helps in troubleshooting and isolating
the source of a problem. Operations personnel (users with Test and Turn up Access Privilege) can use
the Diagnostics function through the local craft interface or at the remote network element through the
DCN interface. Diagnostics can be run continually in the background to check the health of a circuit
pack(s), or can be scheduled to run at periodic intervals. Diagnostics accomplish the following:
■ Reduce network and service unavailability
■ Protect against silent failures
■ Ease maintenance
■ Provide the ability of remote accessibility
■ Reduce cost
Diagnostics is classified under the following types as described below.
Intrusive Diagnostics
Intrusive Diagnostics refers to diagnostic functions that affect traffic when they are executed. The
equipment must be in maintenance mode before applying intrusive diagnostics. Intrusive diagnostics
include POST, BPOST, and User Initiated diagnostics. Intrusive diagnostics also includes the insertion of
PRBS and monitoring signal for errors and applying termination points and terminal loopbacks.
Note: When PRBS generation, PRBS monitoring, and loopbacks are performed on a port, the
administrative status of the port is set to Maintenance. In such cases, the operational status of the
associated cross-connects will be reflected as out-of-service although no cross-connect related
alarms are reported.
Non-Intrusive Diagnostics
Non-intrusive diagnostics do not affect the flow of traffic. These types of diagnostics are applied to test
the performance of the data path by observing the PM data. Users can initiate the internal non-intrusive
diagnostics to monitor the overall health of the circuit pack before it comes into service. Non-intrusive
diagnostics includes the insertion and monitoring of Trail Trace Identifier (TTI) and J0 Section Trace.

DTN/DTN-X/FlexROADM Diagnostics 3-3
Loopbacks in DTN and DTN-X

Note: Unless specifically noted otherwise, all references to “line module” will refer interchangeably to
either the DLM, XLM, ADLM, AXLM, SLM, AXLM-80, ADLM-80 and/or SLM-80 (DTC/MTC only) and
AOLM, AOLM2, AOLX, AOLX2, SOLM, SOLM2, SOLX, SOFX, SOFM, SOLX2, AOFX, and/or AOFM
(XTC only). The term “LM-80” is used to specify the LM-80 sub-set of line modules and refers
interchangeably to the AXLM-80, ADLM-80 and/or SLM-80 (DTC/MTC only). Note that the term “line
module” does not refer to TEMs, as they do not have line-side capabilities and are used for tributary
extension.
Loopbacks are used to test newly created circuits before running live traffic or to logically locate the
source of a network failure on existing circuits. Loopbacks provide a mechanism where the signal under
test (either the user signal or the test pattern signal such as PRBS) is looped back at some location on
the network element in order to test the integrity and validity of the signal being looped back. Since
loopbacks affect normal data traffic flow, they must be invoked only when the associated facility is in
administrative maintenance state.
IQ NOS provides access to the loopback capabilities in the nodes, independent of the client signal
payload type. The loopbacks can be enabled or disabled remotely through the management applications.
The following sections describe the loopbacks supported to test each section of the network, as well as
the various hardware components along the data path. For more details on Loopbacks refer to Infinera IQ
Network Operating System Overview Guide.
Supported Loopbacks on the DTN/DTN-X

Loopbacks Supported on the XTC and Loopbacks Supported on the DTC/MTC mentions the loopbacks
supported by the DTN/DTN-X. Each of these loopbacks with the steps to configure are described in the
below sections.
Note: Loopbacks are not supported on an OTUk/ODUk when PRBS generation is enabled in either
direction (facility or terminal) on the ODUk.
Note: When a Client Trib Facility Loopback is operated on an OTUk, the ODUk facility does not
support alarms nor PMs on its incoming signal.
Note: Whenever the Trib-Gige Facility loopback is enabled on XT-3300 100GE service, both Trib-
Gige and Line-Gige alarms and PM parameters are being displayed. For more details refer the DTN
and DTN-X Alarm and Trouble Clearing Guide and DNA Performance Management Guide.
■ Configuring Loopbacks on the XTC on page 3-4

■ Configuring Loopbacks on the DTC/MTC on page 3-7

3-4 Loopbacks in DTN and DTN-X
Configuring Loopbacks on the XTC

XTC supports the following loopbacks which are described below.
■ To set a Client Tributary Loopback for a termination point on page 3-4
■ To set a ODUk Facility Loopback for a termination point on page 3-5
■ To set a SCG Terminal Loopback for a termination point on page 3-6
■ To set a OTUk Loopback for a termination point on page 3-5
XTC Loopbacks
Table 3-1 : Loopbacks Supported on the XTC shows the loopbacks supported by the XTC .
Table 3-1 Loopbacks Supported on the XTC

XTC Loopbacks Equipment To Configure
Client Tributary TIM-1-100GM/GX, TIM2-2-100GM/GX , TIM2-18- see To set a Client Tributary Loopback
Facility Loopback GM/GX TIM-5-10GM, TIM-1-100-GE, for a termination point on page 3-4
TIM2-2-100GM/GX , TIM2-18-GM/GX , DICM,
XICM, MXP-400
Client Tributary TIM-1-100GM/GX, TIM2-2-100GM/GX, TIM2-18- see To set a Client Tributary Loopback
Terminal Loopback GM/GX TIM-5-10GM, TIM-1-100-GE, for a termination point on page 3-4
TIM2-2-100GM/GX , TIM2-18-GM/GX , DICM,
XICM, MXP-400
Note: TIM-1-100GM/GX in 100GbE operating

mode supports Client Tributary Terminal
Loopback on GbE
ODUk Facility TIM-1-100GM/GX, TIM2-2-100GM/GX , TIM2-18- see To set a ODUk Facility Loopback
Loopback GM/GX AOLx-1200, SOLx-1200, AOLx-500, for a termination point on page 3-5
SOLx-500, AOFx-500, SOFx-500,AOFx-1200,
SOFx-1200, MXP-400
OTUk Facility TIM-1-100GM/GX, TIM2-2-100GM/GX , TIM2-18- seeTo set a OTUk Loopback for a
Loopback GM/GX, MXP-400 termination point on page 3-5
SCG Terminal AOFx-1200, SOFx-1200 see To set a SCG Terminal Loopback
Loopback for a termination point on page 3-6
Ethernet Interface PXM -
Facility Loopback
Ethernet Interface PXM -
Terminal Loopback
To set a Client Tributary Loopback for a termination point

The procedure to set the Client Tributary Loopback for a termination point is provided below:

Note: The facility under test is first switched to the maintenance mode before loopback can be
applied.
Step 1 Based on loopback you want to configure see Table 3-1 Loopbacks Supported on the XTC
Step 2 Perform one of the following:
■ In the Chassis View, right-click the TOM icon and select the required client termination point.
■ In the Equipment Tree of the Chassis View, right-click the TOM icon and select the required
client termination point > Client....
The Client Properties window is displayed.
Step 3 Select State tab. Change the Admin State to Maintenance. Click Apply.
Step 4 Select Diagnostics tab.
Step 5 From the Loopback drop-down menu, select the loopback type you want to apply.
Step 6 To save your changes, click Apply. A warning message is displayed.
Step 7 Click Continue.
Step 8 Click Close to exit window.
To set a OTUk Loopback for a termination point

The procedure to set the OTUk Loopback for a termination point loopbacks is provided below:
applied.
client termination point > OTUk client.
The OTUk Client Properties window is displayed.
To set a ODUk Facility Loopback for a termination point

The procedure to set the ODUk Loopback for a termination point loopbacks is provided below:

applied.
■ In the Chassis View, right-click the required equipment, icon and select ODUk CTP.
■ For line side, in the Equipment Tree of the Chassis View, right-click the required equipment and
select ODUk CTP.
■ For tributary side, in the Chassis View, right-click the required equipment and select Connection
TP
The ODUk CTP Properties window is displayed.
The Facility loopback cannot be applied on an individual ODUKi GTP constituent. To apply facility
loopback on all the GTP constituents, click Apply to All.
Note: The GTP constituents (ODU2i instances) can be in Facility loopback mode, without Group
Termination Point being in locked/maintenance state. For more details refer to DNA Configuration
Management Guide.

To set a SCG Terminal Loopback for a termination point

The procedure to set the SCG Loopback for a termination point loopbacks is provided below:
applied.
■ In the Chassis View, right-click the required equipment and select Super Channel Group.
select Super Channel Group.
The OFX SCG Port Properties window is displayed.
Step 3 Select State tab.

Step 4 Change the Admin State to Maintenance.

Step 5 [Optional] To save your changes, click Apply.
Step 7 From the Loopback drop-down menu, select loopback type you want to apply.
A warning message Turning On loopback will affect the traffic. Do you want to continue? is displayed
Configuring Loopbacks on the DTC/MTC

DTC/MTC supports the following loopbacks which are described below.
■ To set a Client Tributary Loopback for a termination point on page 3-4
■ To set a DTF Path Facility/Terminal Loopback for a termination point on page 3-8
DTC and MTC Loopbacks

Table 3-2 Loopbacks Supported on DTC and MTC mentions the loopbacks supported by the DTC and
MTC. Each of these loopbacks are described below.
Table 3-1 Loopbacks Supported on DTC and MTC

DTC/MTC Loopbacks Equipment To configure
Client Tributary Facility TAM-1-40G/GE/GR, see To set a Client Tributary Loopback for a
Loopback TAM-1-100GE/GR, DICM, termination point on page 3-4
XICM
Trib Digital Transport TAM-1-40G/GE/GR, see To set a DTF Path Facility/Terminal Loopback for
Frame (DTF) Path TAM-1-100GE/GR, DICM, a termination point on page 3-8
Terminal Loopback XICM
Client Tributary Terminal TAM-1-40G/GE/GR, see To set a Client Tributary Loopback for a
Loopback TAM-1-100GE/GR, DICM, termination point on page 3-4
XICM, LIM
Line DTF Path Facility DLM/XLM/ADLM-80/ see To set a DTF Path Facility/Terminal Loopback for
Loopback AXLM-80/SLM/SLM-80 a termination point on page 3-8
Line DTF Path Terminal AOLM, DLM, XLM, ADLM, see To set a DTF Path Facility/Terminal Loopback for
Loopback AXLM, SLM a termination point on page 3-8
DCh Client Facility TAM-2-10GT / DICM-T-2-10GT see To set a Client Tributary Loopback for a
Loopback termination point on page 3-4

Table 3-1 Loopbacks Supported on DTC and MTC (continued)

DTC/MTC Loopbacks Equipment To configure
DCh Client Terminal TAM-2-10GT / DICM-T-2-10GT see To set a Client Tributary Loopback for a
Loopback termination point on page 3-4
Tributary DTF Path Facility TAM-2-10GT / DICM-T-2-10GT see To set a DTF Path Facility/Terminal Loopback for
Loopback a termination point on page 3-8
To set a Client Tributary Loopback for a termination point

The procedure to set the Client Tributary Loopback for a termination point is provided below:
applied.
client termination point > Client....
The Client Properties window is displayed.
To set a DTF Path Facility/Terminal Loopback for a termination point

The procedure to set the DTF Path Loopback for a termination point is provided below:
applied.
■ In the Chassis View, right-click the required equipment and select Line/Trib DTF Path.
■ In the Equipment Tree of the Chassis View, right-click the required equipment and select Line/
Trib DTF Path.
The DTF Path Properties window is displayed.

Step 8 Click Close to exit the DTF Path Properties window.

3-10 Path Loss Check in FlexROADMs
Path Loss Check in FlexROADMs

To detect any faults or excessive loss in the dataplane connectivity over MPO connectors used between
SCG ports, the FBM, FRM-9D, FRM-20X, FSM, and FSE support unidirectional path loss check
operations. Once initiated by the user, the path loss check measures the difference between the
transmitted and received values (even if both Tx and Rx are on the same port in the case of a loopback).
The results of the path loss check are displayed in the SCG Properties window (Diagnostics tab) or in the
response parameters of the RTRV-SCG command via TL1.
A path loss check can be operated using an MPO loopback connector in order to detect cases where the
MPO cable itself needs to be replaced, or for cases where there is no peer SCG port connected, as
shown in the figures below.
Note: Path loss checks are not supported for SCG ports that are associated with an optical cross-
connect or an optical SNC.
For more details on Path Loss refer to Infinera IQ Network Operating System Overview Guide.
Table 3-1 lists the SCG connections for which path loss check is supported.
Table 3-3 Connections Supporting Path Loss Check

From SCG Port To SCG Port Description
FBM Line SCG Port FRM-9D or FRM-20X System Verify Connectivity between FBM and FRM-9D/
(FBM SCG PTP) SCG port (FRM SCG PTP) FRM-20X via FSP-CE-2MPO-1LC/FSP-CE-2MPO-2LC
or MPO-MPO connectors.
FRM-20X System SCG FRM-20X System SCG port on Verify FRM-20X to FRM-20X express connectivity via
port (FRM SCG PTP) another FRM (FRM SCG PTP) the FSP-E.
FRM-9D System SCG FRM-9D System SCG port on Verify FRM-9D to FRM-9D express connectivity via the
port another FRM-9D FSP-E.
(FRM-9D SCG PTP) (FRM SCG PTP)
FSM Line SCG port Verify connectivity between the FRM-9D and the FSM
(FSM SCG PTP) via the FSP-S.
FSE Line SCG port Verify connectivity between the FRM-9D and the FSE
(FSE SCG PTP) via the FSP-S.
FRM-9D System SCG port Verify connectivity between the FRM-9D and the FSP-E
(itself) via MPO loopback at the FSP-E.
(FRM SCG PTP)
Verify connectivity between the FRM-9D and the FSP-C
or FMP-C via LC loopback at the FSP-C/FMP-C.
Verify connectivity between the FRM and the FSP-S via
MPO loopback at the FSP-S.
FSM Line SCG port FRM System SCG port Verify connectivity between the FSM and the FRM-9D
(FSM SCG PTP) (FRM SCG PTP) via the FSP-S.
FSM Line SCG port (itself) Verify connectivity between the FSM and the FSP-S via
(FSM SCG PTP) MPO loopback at the FSP-S.

Table 3-3 Connections Supporting Path Loss Check (continued)

From SCG Port To SCG Port Description
FSM Base Port FSE Expansion Port Verify connectivity between the FSM and the FSE.
(FSM BASE SCG PTP) (FSE EXPN SCGPTP
FSE Line SCG port FRM System SCG port Verify connectivity between the FSE and the FRM via
(FSE SCG PTP) (FRM SCG PTP) the FSP-S.
FSE Line SCG port (itself) Verify connectivity between the FSE and the FSP-S via
(FSE SCG PTP) MPO loopback at the FSP-S.
FSE Expansion Port FSM Base Port Verify connectivity between the FSE and the FSM.
(FSE EXPN SCGPTP (FSM BASE SCG PTP)
To invoke a Path Loss Check for a termination point
Step 1 Perform any of the following:

■ In the Chassis View, right-click the line side SCG port on FSM / line side SCG port on FSE /
SCG add/drop port on FRM / SCG express port on FRM and select Properties.
■ In the Chassis View, right-click the Base SCG port on FSM and select Properties.
■ In the Chassis View, right-click the Expansion SCG port on FSE and select Properties.
The SCG Port Properties window is displayed.
Step 3 Click Invoke Path Loss Check button to invoke the path loss check for the selected SCG Port.
A warning message is displayed, if an optical cross-connect is associated with the selected add/drop
SCG port and the Path Loss Check fails.
Step 4 Click Refresh to update the Path Loss Check, Last Attempt Results and Last Successful Status panels
with the status and results.
Step 5 Click Close to exit the selected SCG Port Properties window.
To invoke a Path Loss Check for all termination points in a node

Step 1 In the Network Topology View, right-click on any ILS3 node icon. Select Tool > Path Loss Check.The
Path Loss Check window is displayed.
Step 2 Select the SCG port from the node drop-down list and click Ok.
The available SCG ports of the node is displayed.
Step 3 Click Invoke Path Loss Check button to invoke the path loss check for the selected SCG Port.
The Message Log panel displays the status.
Step 4 Click Print to print the Path Loss Check table information.
Step 5 Click Export to export the Path Loss Check table information in .tsv format.
Step 6 Click Close to exit the selected SCG Port Properties window.

3-12 Trace Messaging in DTN and DTN-X
Trace Messaging in DTN and DTN-X

Infinera Intelligent Transport Networking Systems provide trace messaging features. The following types
of trace messaging tools are supported. See Figure 3-2: Digital Channel TTI on LM-80 on page 3-13 and
Figure 3-1: J0/DTF Section/DTF Path Trace Messaging on page 3-12.
Note: TTI insertion toward the client side is not supported, and the tributary-side TTI cannot be
monitored when the line-side TTI transmission is enabled.
J0 Trace Messaging on page 3-13

Trail Trace Identifier on page 3-15
Optical Channel Trace Messaging on page 3-17
DTF Path Trace Messaging on page 3-18
J1 Path Trace Messaging over the OSC on page 3-19
Digital Channel Trace Messaging on LM-80 on page 3-19
Trace messaging tool is a diagnostic tool used to monitor the type and the accuracy of the traffic. It is also
used to determine commissioning problems such as wrongly connected fibers. Trace Messages:
■ must be enabled/disabled manually from management applications.
■ can be provisioned from management applications.
■ are trace bytes of ASCII encoded character set.
The network element compares the received trace message with the expected trace message and
if the two do not match, a mismatch alarm with a severity of Major is reported.
Figure 3-1 J0/DTF Section/DTF Path Trace Messaging

Figure 3-2 Digital Channel TTI on LM-80
The system also supports the following specialized TTI messaging on the TAM-2-10GT for Layer 1 OPNs:
■ TTI messaging at the Digital Channel (DCh) Section level (TAM-2-10GT only).
■ The TTI on the Digital Channel level supports TTI monitoring and insertion between TAM-2-10GTs
over a fiber.
■ TTI messaging at the Trib DTF Path level (TAM-2-10GT only). See Figure 3-18.
The DTF Path-level TTI supports monitoring and insertion between TAM-2-10GTs over the Layer 1
OPN.
Note: TTI insertion toward the client side is not supported, and the tributary-side TTI cannot be
monitored when the line-side TTI transmission is enabled.
Figure 3-3 Trace Messaging Supported by the TAM-2-10GT
J0 Trace Messaging
The DTN and DTN-X supports the SONET/SDH J0 trace messaging at the tributary ports. The DTN and
DTN-X provides J0 message transparency, that is, the option to forward the J0 message received from
the network or to overwrite it with the user defined J0 message. The DTN and DTN-X also provides the
ability to write to the J0 trace message received from the client equipment and transmit towards the client
equipment. This capability enables far-end continuity verification and simplifies the client to circuit
connectivity verification. The DTN and DTN-X can monitor 1, 16 and 64 byte J0 trace messages.
■ Is configured to insert ASCII characters from the management interfaces

■ Is provisioned from the management interfaces (DNA )

When configured the DTN and DTN-X compares the received J0 with the expected J0 and if the
two do not match, a Section Trace Mismatch alarm with severity Major is raised.
Note: In the J0 trace message (ASCII format) all characters after CR/LF are ignored.
Note: Modifying the J0 trace mode changes the J0 section overhead. If this change occurs
between SONET/ SDH frames the node can detect and increment the corresponding B1
statistics for this brief transition.
Note: For OC-768 and STM-256 services on the TIM-1-40GM, transparent J0 trace messaging
is supported; J0 overwrite is not supported.
Note: J0 trace messaging is not supported for SONET/SDH services on the TIM-16-2.5GM.
To enable the reporting of SONET J0 trace mismatch condition

■ In the Chassis View right-click the TOM icon and select Client Trib Termination Point > Sonet
client....
■ In the Equipment Tree of the Chassis View, right-click the TOM icon and select Client Trib
Termination Point > Sonet client....
The SONET Client Trib Properties dialog box is displayed.
Step 3 In the Section Trace (J0) panel, enter and select values for the following parameters:
■ Standard Compliance—Select ANSI_ITU or GR253R3 from the J0 message compliance
Standard drop-down menu. ANSI_ITU is the default.
■ Trace Mode—Select one of the following:
□ Transparent—Select this check box to ignore the configured ‘Transmit’ and transparently
forward the ‘Receive’ towards the client equipment. This is the default value for Trace
Mode.
□ Overwrite—Select this check box to overwrite the ‘Receive’ and forward the configured
‘Transmit’ towards the client equipment. Only when this check box is selected, Transmit is
enabled.
■ Length—Select the length of the J0 message. Valid values are 1, 16 and 64. The transmitted
and expected J0 messages will not exceed this length. The default value is 16.
■ Transmit—Enter a string of ASCII characters, no longer than the set length, for the Transmit J0
message. This value is sent towards the client equipment only if Trace Mode is set to Overwrite.
■ Expected—The expected J0 trace message at this network element. This may be entered. This
is an optional message.

■ Receive—The received trace message. This is a read-only message.

■ Mismatch Reporting—Flag that enables the reporting of mismatch alarms when the Receive
and Expected trace do not match. If you want a mismatch alarm to be reported, select Enabled
from the drop-down menu. This is disabled by default.
■ Click Refresh Received and Transmitted J0 to update the Section Trace (J0) Receive and
Transmit values.
Step 5 Click Close to exit the SONET Client Trib Properties window.
Trail Trace Identifier

Trail Trace Identifier (TTI) is an ASCII string passed at the Trib DTF, Line DTF, Digital Channel (DCh) or
Optical Channel within the DTN and ODUk, ODUki, OTUki within DTN-X. This capability enables the
detection of mis-connections between the equipment within the Intelligent Transport Network.
The TTI is used to verify a cross-connect or SNC:
■ Is a 64 byte ASCII string
■ Is configured to insert ASCII characters (Trib DTF, Digital Channel (DCh), Optical Channel, ODUk,
ODUki, OTUki only) from the management interfaces (DNA)
■ Is provisioned from the management interfaces (DNA)
When configured, the DTN/DTN-X compares the received TTI with the expected TTI and if the two
do not match, a Trail Trace Identifier Mismatch alarm with severity is raised.
Note: The TTI can only be monitored at the Line DTF. The Trib DTF TTI, Optical Channel TTI,
ODUk TTI, ODUki TTI, OTUki TTI allows for the Insert of ACSII characters, and monitor
functionality.
To enable Trail Trace Identifier

■ In the Chassis View, right-click the OLM/AOLM icon and select OTUki Section.
■ In the Equipment Tree of the Chassis View, right-click the OLM/AOLM/AOFM-500/AOFX-500/
AOFX-1200 icon and select OTUki Section.
The OTUki Section Properties window is displayed.
Step 2 Select the channel you want to enable trace messaging on.

Step 4 In the FEC panel, select the following values:

■ FEC Correction - This attribute enables FEC correction at the ingress of the OTUki client facility.
This field is read only and the default value is always “Enabled”.
■ FEC Generation - This attribute enables FEC generation handling at the OTUki client facility.
This field is read only and the default value is always “Enabled”.
■ FEC Decode Iteration - This attribute is the number of FEC decode iterations executed on the
received OTUki stream. The value range from 1 to 4.
Step 5 In the Trail Trace Identifier (TTI) panel, enter and select the following values:
■ Select the TTI format required as the system has the capability in handling both ASCII and HEX
values in both G.709 and normal formats. The formats are as follows:
□ G.709 format - It is a 64 byte string with the following attributes:
TTI[0] - Contains SAPI[0] character, that is user configurable
TTI[1..15] - 15 character source access point identifier
TTI[16] - Contains DAPI[0] character, that is fixed to all 0s
TTI[17..31] - 15 character destination point access identifier
TTI[32..63] - User specific
□ Normal format - It is a 16 byte string for SAPI, DAPI and 64 byte string for Transmit and
receive.
■ Transmit—The TTI string that will be transmitted.
■ Receive—The actual TTI received.
■ Expected SAPI—The expected SAPI value.
■ Expected DAPI—The expected DAPI value.
■ Alarm Reporting—Flag that enables alarm reporting if the expected TTI does not match the
received TTI.
■ Click Refresh to clear all the values entered for TTI.
Step 7 Click Close to exit the OTUki Section Properties window.
Source and Destination Access Point Identifiers (SAPI and DAPI)

The DTN supports configuration of the TTI mismatch detection mode for ODUk and OTUk clients and for
ODUkT Tandem Connections on the TAM-2-10GM and TAM-8-2.5GM, so that the Source Access Point
Identifier (SAPI) or the Destination Access Point Identifier (DAPI) or both can be used to compare the TTI
expected message with the TTI received message. Therefore, the expected SAPI and DAPI messages
are configurable independent of one another.
The TIM-5-10GE, TIM-5-10GM, TIM-1-100GE on the DTN-X supports the following SAPI and DAPI
directions for the following entities:

■ Trib ODUk terminal SAPI/DAPI (towards the network)

■ Line ODUk terminal and facility SAPI/DAPI (towards the trib and towards the network), when the
ODUk is in non-intrusion mode
■ Line ODUki facility SAPI/DAPI (towards the network)
■ Line OTUki facility SAPI/DAPI (towards the network)
Tandem Connection Monitoring (TCM)

The DTN supports user-created ODUk tandem connection monitoring (TCM) facilities, which are logical
facilities created by the user to retrieve performance monitoring in order to diagnose faults on segments
of an ODU path.
The monitoring mode of the TCM can be configured by the user:
■ Non-intrusive monitoring, in which PMs are monitored but nothing else is changed, signal is passed
on as-is.
■ Limited-intrusive monitoring, meaning that any monitoring attributes can be user set, including
transmit TTI, for which the user setting or the default blank string will be inserted by the node.
■ Intrusive monitoring, meaning that the whole overhead is removed, and replaced along with any
user-entered TTI overwrite.
Note the following limitations for TCM configuration on DTN:
■ DTC/MTC allows a maximum of 3 TCM CTPs per side (facility side and terminal side). As a result,
the node allows up to 6 total ODUkT CTPs per a given ODUk client CTP. So, for example, the user
can activate TCM IDs 1, 4, 6 on FAC side, and can activate 2, 3, 5 on TERM side (but no more
than three TCM CTPs per side).
Optical Channel Trace Messaging

The optical channel on the line modules support TTI monitoring and insertion between line modules over
a fiber. This test verifies the functioning of the optical channel between two line modules installed in the
network.
To enable Optical Channel trace messaging

■ In the Chassis View, right-click the DLM icon and select Optical Channels.
■ In the Equipment Tree of the Chassis View, right-click the DLM icon and select Optical
Channels.
The Optical Channel Properties window is displayed.
Step 2 Select the channel you want to enable trace messaging on.

■ Alarm Reporting—Flag that enables alarm reporting if the expected TTI does not match the
received TTI.
■ Expected—The expected TTI.
■ Insert—Flag that enables the TTI string to be entered and monitored at the far end.
Step 6 Click Close to exit the Optical Channel Properties window.
DTF Path Trace Messaging

The Line and Trib DTF Path trace messaging is utilized to detect any mis-connections in the circuit path
along the Intelligent Transport Network. The DTF trace messaging is independent of the client signal
payload type.
To enable DTF Path trace messaging

■ In the Chassis View, right-click the TOM icon and select Trib DTF Path.
■ In the Equipment Tree of the Chassis View, right-click the TOM icon and select Trib DTF Path.
The DTF Path Properties window is displayed.
■ Insert—Flag that enables the TTI string to be entered and monitored.
■ Alarm Reporting—Flag that enables alarm reporting if the received TTI does not match the
expected TTI.
Step 5 Click Close to exit the DTF Path Properties window.
Note: This feature should be active on both ends of the Trib DTF path, to operate correctly.

J1 Path Trace Messaging over the OSC

BMMs, OAMs, and ORMs support J1 Path trace messaging in order to discover and continuously monitor
the link connectivity between adjacent neighbor network elements. J1 Path trace messages are
continuously transmitted over the OSC, using the format “/<NodeID>/<OTS TP AID>” (64 characters in
length, padding unused bytes with ASCII null characters, and terminated with “<CR><LF>”). BMMs,
OAMs, and ORMs support J1 Path trace, even when the OSC IP address is not configured, when the
GMPLS is disabled, or the BMM/OAM/ORM is put in the maintenance or Locked state. J1 Path trace
information will not be available when there is fiber cut (OTS OLOS condition), OSC Loss of
Communication condition, or if the BMM/OAM/ORM is pre-provisioned. J1 Path trace is not supported on
RAMs, as RAMs do not terminate the OSC. J1 Path trace messaging is always enabled.
Digital Channel Trace Messaging on LM-80

The digital channel on the LM-80 supports TTI monitoring and insertion between LM-80s over a fiber.
This test verifies the functioning of the digital channel between two LM-80s installed in the network.
To enable Digital Channel trace messaging on LM-80

Step 1 In the Chassis View, right-click one of the optical channel ports of the specified LM-80 and select
Digital Channel....
The Digital Channel Properties window is displayed.
Step 2 Select the required channel you want to enable trace messaging on.
expected TTI.
Step 6 Click Close to exit the Digital Channel Properties window.

3-20 PRBS Test in DTN and DTN-X
PRBS Test in DTN and DTN-X

The Pseudo Random Binary Sequence (PRBS) is a test pattern used to diagnose and isolate the troubled
spots in the network, without requiring a valid data signal or customer traffic. This type of test signal is
used during the system turn-up or in the absence of a valid data signal from the customer equipment. The
test is primarily aimed to watch for and sectionalize the occurrence of bit errors in the data path. Since the
PRBS test affects normal data traffic flow, it must be invoked only when the associated facility is in
IQ NOS provides access to the PRBS generation and monitoring capabilities supported by the Infinera
nodes. The PRBS test can be enabled or disabled remotely through the management applications.
The PRBS tests can be coupled with loopback tests so that the pre-testing of the quality of the digital link
or end-to-end digital path can be performed without the need for an external PRBS test set. While this is
not meant as a replacement for customer-premise to customer-premise circuit quality testing, it does
provide an early indicator of whether or not the transport portion of the full circuit is providing a clean
signal.
The following sections describe the PRBS tests supported by the DTN-X and DTN:
■ PRBS Tests Supported by the XTC on page 3-20
■ PRBS Tests Supported by the DTC/MTC on page 3-22
■ Optical Channel PRBS Test on page 3-25
■ Trib DTF Path PRBS Test on page 3-27
■ Client Trib Termination Point PRBS Tests on page 3-29
■ Digital Channel PRBS Test on LM-80 on page 3-32
PRBS Tests Supported by the XTC

The DTN-X supports PRBS generation and monitoring for both the facility and terminal directions of
ODUk facilities on the XTC:
Note: PRBS generation and monitoring are intrusive diagnostics.
■ ODUk Client Facility PRBS test—A PRBS signal is generated (transmitted) by the Infinera tributary
towards the client network side and is monitored (received) by the tributary in the customer
equipment or the test set connected to the Infinera tributary.
■ ODUk Client Terminal PRBS test—A PRBS signal is generated (transmitted) by the Infinera
tributary towards the Infinera network side and is monitored (received) by the tributary at the far-
end node.
Figure 3-4: PRBS Tests Supported by the XTC on page 3-21 shows the PRBS support for
services on the XTC.

Figure 3-4 PRBS Tests Supported by the XTC
Note the following for PRBS support on the XTC:

■ For the following diagnostics, only one is supported at a time
□ OTUk Client Tributary Facility Loopback
□ OTUk Client Tributary Terminal Loopback
□ ODUk Facility Loopback
□ ODUk Client Facility PRBS generation
□ ODUk Client Facility PRBS monitoring
□ ODUk Client Terminal PRBS generation
□ ODUk Client Terminal PRBS monitoring
■ PRBS generation and PRBS monitoring can be enabled on an ODUk simultaneously, as long as
both the generation and monitoring are enabled in the same direction (facility or terminal). PRBS
monitoring can be enabled in two directions on the same ODUk as long as PRBS generation is not
enabled in either direction for the ODUk.
■ When PRBS generation is enabled in the terminal direction for ODUk services on the TIM-1-40G or
TIM-1-100G, the OTUk/ODUk facility does not support alarms nor PMs on its incoming signal
(receive direction PMs/alarms). The tributary physical termination point (PTP) will continue to
correctly report PMs, but the trib PTP will not generate an alarm in case of optical loss of signal
(OLOS).
■ For OTUk transport services, PRBS tests are not supported in the terminal direction. PRBS tests
are supported in the facility direction for OTUk transport services.
■ Also for ODU Multiplexing services on the XTC, note the following:
□ ODUk Facility Loopback
□ OTUk Client Tributary Facility Loopback
□ ODUk Client Facility PRBS generation

□ ODUj Client Facility PRBS generation

□ ODUj Client Terminal PRBS generation
Note: PRBS generation can be supported simultaneously in both the facility and terminal
directions on the ODUj facility if no other diagnostics are enabled (i.e., loopback on the
OTUk/ODUk/ODUj or PRBS generation on the ODUk). Simultaneous PRBS generation
in the facility and terminal directions is supported for ODUj PRBS tests only.
■ Also for ODU Multiplexing services on the XTC, note the following:
□ Client Facility PRBS generation is supported on only one ODUk/ODUj on the port.
□ Client Terminal PRBS generation is supported on only one ODUj on the port.
□ Client Facility PRBS monitoring is supported on only one ODUk/ODUj on the port.
□ Client Terminal PRBS monitoring is supported on only one ODUj on the port.
■ When PRBS generation is enabled in the terminal direction for ODUk services on the TIM-1-40G or
TIM-1-100G, the OTUk/ODUk facility does not support alarms nor PMs on its incoming signal
(receive direction PMs/alarms). The tributary physical termination point (PTP) will continue to
correctly report PMs, but the tributary PTP will not generate an alarm in case of optical loss of
signal (OLOS).
■ For OTUk transport services, PRBS tests are not supported in the terminal direction. PRBS tests
are supported in the facility direction for OTUk transport services.
Note the following for PRBS support for OC-768 and STM-256 clients on the TIM-1-40GM:
■ PRBS is not supported on the OC-768 and STM-256 client if a loopback is enabled on the client or
on the associated ODU3.
■ Trib PRBS generation and Line PRBS generation can be enabled simultaneously on the OC-768/
STM-256, provided that ODUk Client Terminal PRBS generation is not enabled on the associated
ODU3.
■ Trib PRBS generation on the OC-768/STM256 and ODUk Client Terminal PRBS generation on the
associated ODU3 can be enabled simultaneously, provided that Line PRBS generation is not
enabled on the OC-768/STM-256.
PRBS Tests Supported by the DTC/MTC

The DTC/MTC supports PRBS generation and monitoring for testing circuit quality at the client, the DTF
Section layer, or the DTF Path layer:
Note: PRBS generation and monitoring are intrusive diagnostics.

Figure 3-5 PRBS generation and monitoring are intrusive diagnostics
There are several types of PRBS tests (see Figure 3-4: PRBS Tests Supported by the XTC on page 3-21
through Figure 3-7: PRBS Tests Supported by TAM-2-10GT on page 3-25):
■ Client PRBS test (supported only for OC-768 and STM-256 interfaces)—A PRBS signal is
generated (transmitted) by the OC768/STM-256 tributary towards the client network side and is
monitored (received) by the OC768/STM-256 tributary in the customer equipment or the test set
connected to the Infinera tributary.
■ Trib (facility side) PRBS test (supported only for OTUk, SONET, and SDH interfaces on the
TAM-8-2.5GM and TAM-2-10GM)—A PRBS signal is generated (transmitted) by the Infinera
tributary towards the client network side and is monitored (received) by the tributary in the customer
equipment or the test set connected to the Infinera tributary.
■ Line (terminal side) PRBS test (supported only for OTUk, SONET, and SDH interfaces on the
TAM-8-2.5GM and TAM-2-10GM)—A PRBS signal is generated (transmitted) by the
Infineratributary towards the Infinera network side and is monitored (received) by the tributary at the
far-end TAM-8-2.5GM or TAM-2-10GM.
Note: Line PRBS test is not supported on OTUk clients that are configured for service type
adaptation.
Note: For OTUk clients on the TAM-2-10GM, Line PRBS generation must be disabled and re-
enabled upon either failure or recovery of the client signal.
■ DTF Section-level PRBS test—A PRBS signal is generated by the near-end line module and it is
monitored by the adjacent nodes. This test verifies the quality of the digital link between two
adjacent nodes.
■ DTF Path-level PRBS test—A PRBS signal is generated by the near-end TAM and it is monitored
at the far-end TAM where the digital path is terminated. This test verifies the quality of the end-to-
end digital path. Historical performance monitoring data is collected for PRBS sync errors and
PRBS errors on the Trib DTF Path.

Note: DTF Path-level PRBS test is not supported on the TAM-8-1G. The TAM-8-1G does
support the GbE Client Termination Point tests described in GbE Client Termination Point
Tests in DTN and DTN-X on page 3-35.
Note: When configuring DTF Path-level PRBS test between TAM-8-2.5GMs, the TOMs must
be physically present in the TAM-8-2.5GMs for PRBS to be generated. If the generating TOM
is pre-provisioned but not physically present, the PRBS signal will not be sent and so the DTP
on the monitoring TOM will report an PRBS-OOS alarm and the PRBS Error and PRBS Sync
Err PM counters will increment.
In addition to the above PRBS tests, the system also supports specialized PRBS tests on the line-
side Digital Channel (DCh) of the LM-80:
■ Digital Channel (DCh) PRBS test (LM-80 only)—A PRBS signal is generated by the near-end
LM-80 and it is monitored by the far-end LM-80. This test verifies the functioning of the optical
channel between two LM-80s (see Figure 3-6: Digital Channel PRBS Test Supported by LM-80 on
page 3-24).
Note: Digital Channel PRBS tests are not supported for 20Gbps wavelengths (PM-BPSK
modulation format). If a DCh PRBS test is enabled on a PM-BPSK wavelength, traffic will be
impacted in the adjacent DCh in the LM-80 optical channel. For LM-80 wavelengths that use
PM-BPSK modulation, use the DTF Path-level PRBS test on the TAM.
Figure 3-6 Digital Channel PRBS Test Supported by LM-80
Lastly, the system also supports specialized PRBS tests on the TAM-2-10GT for Layer 1 OPNs.
■ Digital Channel (DCh) Section-level PRBS test (TAM-2-10GT only)—A PRBS signal is generated
by the near-end TAM-2-10GT and it is monitored by the far-end TAM-2-10GT. This test verifies the
functioning of the Digital Channel between two TAM-2-10GTs installed in the customer network and
provider network (seeFigure 3-7: PRBS Tests Supported by TAM-2-10GT on page 3-25).
■ Tributary DTF Path-level PRBS test (TAM-2-10GT only)—A PRBS signal is generated by the near-
end TAM-2-10GT and it is monitored by the far-end TAM-2-10GT. This test verifies the digital path
in the Layer 1 OPN in the provider network (see Figure 3-7: PRBS Tests Supported by
TAM-2-10GT on page 3-25)

See Rules for Performing PRBS Tests on a Trib DTF Path (TAM-2-10GT) on page 3-25 for
information on performing PRBS tests on the TAM-2-10GT.
Figure 3-7 PRBS Tests Supported by TAM-2-10GT
Rules for Performing PRBS Tests on a Trib DTF Path (TAM-2-10GT)

The following rules apply to generating and monitoring PRBS test signals on a Trib DTF Path for
TAM-2-10GT:
■ These rules are applicable only for 2.5G DTPs.
■ The PRBS generation and monitoring on 2.5G DTP cannot be enabled unless all the DTPCTPs on
that facility are in maintenance. That is, to enable PRBS on 1-A-3-T1-1-1, each of 1-A-3-T1-1-1, 1-
A-3-T1-1-2, 1-A-3-T1-1-3, 1-A-3-T1-1-4 (if they are present) must be in maintenance.
■ The Administrative state on any 2.5G DTP can be set to Unlocked only if PRBS generation and
monitoring are disabled on all the DTPs on this facility.
■ If the PRBS generation/monitoring (and Maintenance state) is set from the template and then the
DTPCTP object is created, PRBS will be enabled only if the above mentioned rules are satisfied.
Otherwise, the created DTP object will be put into Maintenance.
■ If the PRBS (generation/monitoring) is enabled on the first DTP and a second facility is created
later, it will be forced to Maintenance state irrespective of template configuration.
Optical Channel PRBS Test

The PRBS signal is generated by the near end DLM in the DTN or in the expansion chassis of the DTN-X
node and it is monitored by the adjacent DTN network elements. This test verifies the quality of the digital
link between two adjacent DTN network elements. See Figure 3-5: PRBS generation and monitoring are
intrusive diagnostics on page 3-23.

To enable PRBS test on optical channel between Node1 and Node2

■ In the Chassis View of Node1, right-click the DLM icon and select Optical Channels.
■ In the Equipment Tree of the Chassis View of Node1, right-click the DLM icon and select Optical
Channels.
Step 2 Select the required channel.
Step 3 Select the State tab. Change the Admin State to Maintenance. Click Apply.
Step 4 Select the Diagnostics tab. In the PRBS Mode panel, select the following values:
■ Generation—Flag which enables the generation of PRBS data on the transmit side. The value
can be either Enabled or Disabled. Enable this option to generate PRBS data on Node1.
■ Monitoring—Flag which enables the monitoring of bit errors. The value can be either Enabled or
Disabled. Disable this option to disable monitoring of bit errors on Node1.
Note: Enabling PRBS generation prompts for confirmation with a warning of traffic disruption. Click
Continue at this prompt, to proceed.

Channels.
can be either Enabled or Disabled. Disable this option to disable generation of PRBS data on
Node2.
Disabled. Enable this option to monitor bit errors on Node2.

To disable PRBS test on optical channel between Node1 and Node2

Channels.
can be either Enabled or Disabled. Disable this option.
Disabled. Disable this option.
Step 4 Select the State tab. Change the Admin State to Unlocked. Click Apply.
Channels.
Step 8 Repeat Step 2 through Step 6.
Trib DTF Path PRBS Test

The PRBS signal is generated by the near end TAM and it is monitored at the far end TAM where the
digital path is terminated. This test verifies the quality of the end-to-end digital path. See Figure 3-40 on
page 3-45.
Note: TAM-8-1G does not support the DTF Path-level PRBS test. A warning message PRBS
Generation and Monitoring are not supported for Channelized_2x1GbE DTPCTP is
displayed, if you attempt to enable DTF Path-level PRBS generation or monitoring on TAM-8-1G.
TAM-8-1G does support the DTF Section-level PRBS test (See Optical Channel PRBS Test on page
3-25) and GbE Client Termination Point Tests (See GbE Client Termination Point Tests in DTN and
DTN-X on page 3-35).

To enable Trib DTF Path PRBS test between Node1 and Node3
Note: For a Trib DTF Path PRBS test, PRBS data generation at the local node (Node1) and
monitoring at the remote node (Node3) is supported for 10GbE LAN, 10G Clear Channel and 1GbE
service types and is not supported for OC48 and OC192 service types.

■ In the Chassis View of Node1, right-click the TOM icon and select Trib DTF Path.
■ In the Equipment Tree of the Chassis View of Node1, right-click the TOM icon and select Trib
DTF Path.
The Trib DTF Path Properties window is displayed.
Step 3 Select the Diagnostics tab. In the PRBS Mode panel, enter and select the following values:
Step 5 Click Close to exit the Trib DTF Path Properties window.
To enable Trib DTF Path PRBS test between Node1 and Node3 with a Line DTF Path Facility Loopback
enabled on Node3
Note: For a Trib DTF Path PRBS test, PRBS data generation and monitoring at the same node
(Node1) with a Line DTF Path Facility Loopback enabled on the remote node (Node3) is supported
for OC192, OC48, 10GbE LAN, 10G Clear Channel and 1GbE service types.

DTF Path.
Disabled. Enable this option to disable monitoring of bit errors on Node1.

Step 5 When you are done, click Close to exit the Trib DTF Path Properties window.
Step 6 In the Chassis View of Node1, enable the Line DTF Path Facility Loopback. See To set a GbE Client
Facility Loopback for a termination point for the procedure to enable Line DTF Path Facility Loopback.
To disable Trib DTF Path PRBS test between Node1 and Node3
DTF Path.
can be either Enabled or Disabled. Disable this option.
DTF Path.
Step 7 Repeat Step 2 through Step 5.
Client Trib Termination Point PRBS Tests

The DTN supports Synchronous Payload Envelope (SPE) encapsulated PRBS generation and monitoring
on the 40G tributary side interface. End-to-end PRBS test on a 40G client signal can be performed, with
the far end being looped back at the client interface.
Note: The Client Trib Termination Point PRBS Tests are applicable only for the OC-768 and STM-256
client termination points on the TAM-1-40G.

Note: Since the Client Trib Termination Point PRBS tests affect normal data traffic flow, it must be
performed only when the associated 40G TAM and the OC-768/STM-256 facility is in Maintenance
state.
To enable OC-768/STM-256 client trib PRBS generation and monitoring

■ In the Chassis View of the required node, right-click the required TAM icon and select
Properties.
■ In the Equipment Tree of the Chassis View of the required node, right-click the required TAM
icon and select Properties.
The TAM Properties window is displayed.
Step 2 In the State tab of the TAM Properties window, change the Admin State to Maintenance and click
Apply.
Step 3 Click Close to exit the TAM Properties window.
■ In the Chassis View of the required node, right-click the associated TOM icon and select Client
trib termination point > Sonet client....
■ In the Equipment Tree of the Chassis View of the required node, right-click the associated TOM
icon and select Client trib termination point > Sonet client....
The SONET Client Trib Properties window is displayed.
■ Trib PRBS Generation—Flag which enables or disables the trib PRBS generation. The value
can be either Enabled or Disabled. Select Enabled to enable the generation of PRBS.
■ Trib PRBS Monitoring—Flag which enables or disables the monitoring of bit errors on the
tributary side. The value can be either Enabled or Disabled. Select Enabled to enable the
monitoring of bit errors.
Note: This operation can be performed from the CDM application as well. See To disable PRBS
generation and monitoring on facilities on page 6-178 for a detailed procedure.

Client Trib Termination Point PRBS Tests on 10gig TIM

The DTN-X supports Synchronous Payload Envelope (SPE) encapsulated PRBS generation and
monitoring on the 40G Trib side interface. End-to-end PRBS test on a 10G client signal can be
performed, with the far end being looped back at the client interface.
Note: The Client Trib Termination Point PRBS Tests are applicable only for the OC-192 and STM-64
client termination points on the TIM- 5-10GM.
Note: Since the Client Trib Termination Point PRBS tests affect normal data traffic flow, it must be
performed only when the associated 10G TIM and the OC-192/STM-64 facility is in Maintenance
state.
To enable OC-192/STM-64 client trib PRBS generation and monitoring

■ In the of the required node, right-click the required TIM icon and select Properties.
■ In the Equipment Tree of the Chassis View of the required node, right-click the required TIM
icon and select Properties.
The TIM Properties window is displayed.
Step 2 In the State tab of the TIM Properties window, change the Admin State to Maintenance and click
Apply.
Step 3 Click Close to exit the TIM Properties window.
■ In the Chassis View of the required node, right-click the associated TOM icon and select Client
trib termination point > Sonet client....
■ In the Equipment Tree of the Chassis View of the required node, right-click the associated TOM
icon and select Client trib termination point > Sonet client....
■ Trib PRBS Generation—Flag which enables or disables the trib PRBS generation. The value
can be either Enabled or Disabled. Select Enabled to enable the generation of PRBS.
■ Trib PRBS Monitoring—Flag which enables or disables the monitoring of bit errors on the trib
side. The value can be either Enabled or Disabled. Select Enabled to enable the monitoring of
bit errors.

Note: This operation can be performed from the CDM application as well. See To enable PRBS
generation and monitoring on facilities on page 6-178 for a detailed procedure.
Digital Channel PRBS Test on LM-80

The PRBS signal is generated by the near-end LM-80 and it is monitored by the far-end LM-80. This test
verifies the functioning of the digital channel between two LM-80s.
To enable Digital Channel PRBS test between DTN Node1 and DTN Node2 connected through OTS
Fiber
Step 1 In the Chassis View of Node 1, right-click one of the optical channel ports of the specified LM-80 and
select Digital Channel....
Step 4 Select the Diagnostics tab. In the Line PRBS panel, select the following values:
■ PRBS Generation—Flag which enables the generation of PRBS data on the transmit side. The
value can be either Enabled or Disabled. Enable this option to generate PRBS data on Node1.
■ PRBS Monitoring—Flag which enables the monitoring of bit errors. The value can be either
Enabled or Disabled. Disable this option to disable monitoring of bit errors on Node1.

value can be either Enabled or Disabled. Disable this option to disable generation of PRBS data
on Node2.
Enabled or Disabled. Enable this option to monitor bit errors on Node2.

Note: If PRBS generation and monitoring is enabled on both the ends, PRBS - Out of Sync alarm
will get cleared. If PRBS generation and monitoring is enabled either on Node1 or on Node2, then
PRBS - Out of Sync alarm will be reported.
To disable Digital Channel PRBS test between DTN Node1 and DTN Node2 connected through OTS
Fiber
value can be either Enabled or Disabled. Disable this option.
Enabled or Disabled. Disable this option.
Repeat Step 2 through Step 6.
Note: This operation can be performed from the CDM application as well. See “To enable PRBS
generation and monitoring on facilities“ for a detailed procedure.

3-34 Test Signal Generation for Fiber Channel Clients in DTN
Test Signal Generation for Fiber Channel Clients in DTN

Fibre Channel services support tributary-side and line-side test signal generation:
■ Tributary-side test signal—A test pattern that is generated towards the client from the Infinera
network.
■ Line-side test signal—A test pattern that is generated towards Infinera network.
On the DTN, 1GFC, 2GFC, 8GFC, and 10GFC services on the TAM-8-2.5GM, TAM-2-10GM, and
DICMT- 2-10GM support test signal generation only. On the DTN, the test signal generation mode can be
set to Compliant Random Pattern (CRPAT) or it can be disabled.
On the DTN-X, 8GFC and 10GFC services on the TIM-5-10GX and TIM-5-10GM support both test signal
generation and monitoring.
Note: Since the Fiber Channel test signal affects normal data traffic flow, it must be used only when
the associated facility is in administrative maintenance state.

GbE Client Termination Point Tests in DTN and DTN-X

A GbE Client Termination Point (CTP) test signal is used to diagnose and isolate the troubled spots for
the GbE clients on Infinera nodes without requiring a valid data signal or customer traffic. The test signal
is a long continuous random test pattern that complies with the IEEE 802.3 Annex 36A.4 specification.
For DTC/MTC clients, the GbE CTP test signal is available only for the 1GbE ports on the TAM-8-1G and
TAM-8-2.5GM; for 10GbE ports on the TAM-2-10GM and DICM-T-2-10GM; for 40GbE ports on the
TAM-1-40GE and TAM-1-40GR; and for 100GbE ports on the TAM-1-100GE and TAM-1-100GR.
Note: For XTC clients, GbE CTP test signals are supported by all Ethernet ports.
Note: Since the GbE tests affect normal data traffic flow, it must be performed only when the
associated facility is in Maintenance state.
There are two types of GbE Client Termination Point Test Signals:
■ Tributary-Side Client Test—A test signal is generated by the GbE CTP toward the client equipment.
This test signal can be monitored by an external test set or by creating a loopback and enabling
tributary-side monitoring on the same GbE CTP.
■ Line-Side Client Test—A test signal is generated by the GbE CTP toward the Infinera network
where it is monitored by one of the following:
□ An external test set.
□ A corresponding GbE CTP on a far-end TAM, if the corresponding GbE CTP has been
enabled for line-side test signal monitoring.
□ The same GbE CTP that is generating the test signal, if the GbE CTP has been enabled for
line-side monitoring and if a loopback has been created at the far end.
Note the following limitations for GbE CTP tests:
■ The TIM-1-40GE and TIM-1-100GE/TIM-1B-100GE do not support monitoring of GbE client
termination point tests. These TIMs can generate GbE client termination point test signals, but an
external test set is required to monitor the signal. Alternatively, PCS faults and PCS PMs can be
used to verify end to end data path.
■ For monitoring of GbE client termination point tests for TIM-5-10GM, XICM-T-5-10GM,
TIM-5B-10GM, and TIM-5-10GX, note that PM counts for both Test Signal Sync Errors and Test
Signal Out of Sync Errors will increment at the same time.
■ The TAM-1-100GE, TAM-1-100GR, TAM-1-40GE, and TAM-1-40GR do not support monitoring of
line-side GbE client termination point tests. These TAMs can generate tributary-side GbE client
termination point test signals, but an external test set is required to monitor the signal.
■ The TAM-8-2.5GM, TAM-1-100GE, TAM-1-100GR, TAM-1-40GE, and TAM-1-40GR do not support
monitoring of tributary-side GbE client termination point tests. These TAMs can generate tributary-
side GbE client termination point test signals, but an external test set is required to monitor the
signal.

3-36 GbE Client Termination Point Tests in DTN and DTN-X
See Rules for performing GbE Client Termination Point tests on TAM-8-1G on page 3-36 for the
valid configurations of Line side and Tributary side Test Signal generation and monitoring for GbE
Client Termination Point in the group of ports (1a, 1b, 2a, 2b) and (3a, 3b, 4a, 4b).
See To enable/disable GbE Client Termination Point Test at a Node on page 3-37 for the
procedure to enable GbE client termination point PRBS test at a node.
See Lamp Testing in DTN, DTN-X and FlexROADM on page 3-39for the procedure to disable
GbE client termination point PRBS test at a node.
Rules for performing GbE Client Termination Point tests on TAM-8-1G

The ports on the TAM-8-1G are divided into two physical port sets: {1a, 1b, 2a, 2b} and {3a, 3b, 4a, 4b}.
Separate Line side and Tributary side test signal generation and monitoring functions are supported. The
following restrictions apply to PRBS tests on the TAM-8-1G port sets for:
“Monitoring Test Signals”
“Generating Test Signals”
“Monitoring and Generating Test Signals at the same time”
Note: Any attempt via the management interface to violate these rules is not permitted.
Monitoring Test Signals

■ Only one port in each port set can be configured to monitor the line-side test signal at any one time.
■ Only one port in each port set can be configured to monitor the tributary-side test signal at any one
time.
■ Although two ports in a port set can neither monitor their line side at the same time, nor monitor
their tributary side at the same time, it is possible to configure one port in a port set to monitor the
line-side test signal at the same time that another port (or even the same port) in the same port set
is configured to monitor the tributary-side signal.
Generating Test Signals

■ Any number of ports in a port set can simultaneously generate a line-side test signal, even while
one or more ports in the same port set are generating tributary-side test signals.
■ Any number of ports in a port set can simultaneously generate a tributary-side test signal, even
while one or more ports in the same port set are generating line-side test signals.
Monitoring and Generating Test Signals at the same time

■ It is possible for a port in a port set to monitor the test signal from one direction at the same time
that one or more ports in the same port set are generating test signals in the same direction.
Meaning that:
□ It is possible for a port in a port set to monitor the tributary-side test signal when one or more
ports in the same port set are generating tributary-side test signals.

□ It is possible for a port in a port set to monitor the line-side test signal when one or more
ports in the same port set are generating line-side test signals.
■ It is not possible for a port in a port set to monitor the test signal from one direction when one or
more ports in the same port set are generating test signals in the other direction. Meaning that:
□ It is not possible for a port in a port set to monitor the tributary-side test signal when one or
more ports in the same port set are generating line-side test signals.
□ It is not possible for a port in a port set to monitor the line-side test signal when one or more
ports in the same port set are generating tributary-side test signals.
To enable/disable GbE Client Termination Point Test at a Node

■ In the Chassis View of the required node, right-click the TOM icon (on TAM 8X1 GbE at Port 1a)
and select Client trib termination point > GbE Client.
■ In the Equipment Tree of the Chassis View of the required node, right-click the TOM icon (on
TAM 8X1 GbE at Port 1a) and select Client trib termination point > GbE Client.
The GbE Client Properties window is displayed.
Step 3 Select the Diagnostics tab. In the Line Test Signal Mode and Trib Test Signal Mode panels, enter and
select the following values, based on the valid configurations allowed:
Note: Line Test Signal Monitoring and Trib Test Signal Monitoring are not supported on 40GbE
clients on TAM-1-40GE/GR and on 100GbE clients on TAM-1-100GE/GR.
■ Line Test Signal Generation—Flag which enables the generation of test signal on the line side.
The value can be either Enabled or Disabled. Enable or disable depending on the requirement.
■ Line Test Signal Monitoring—Flag which enables the monitoring of bit errors on the line side.
The value can be either Enabled or Disabled. Enable or disable depending on the requirement.
■ Trib Test Signal Generation—Flag which enables the generation of test signal on the tributary
side. The value can be either Enabled or Disabled. Enable or disable depending on the
requirement.
■ Trib Test Signal Monitoring—Flag which enables the monitoring of bit errors on the tributary
side. The value can be either Enabled or Disabled. Enable or disable depending on the
requirement.
Note: Enabling the line and/or trib test signal generation prompts for confirmation with a warning of
traffic disruption. Click Continue at this prompt, to proceed.
Step 5 Click Close to exit the GbE Client Properties window.

3-38 GbE Client Termination Point Tests in DTN and DTN-X
Step 6 Repeat the above steps for each of the ports in the required nodes, based on the test you want to
perform.
Note: This operation can be performed from the CDM application as well. See “To enable Line
and/or Trib Termination Point Tests on GbE clients from CDM“ for a detailed procedure.

Lamp Testing in DTN, DTN-X and FlexROADM

The DTN, DTN-X, FlexROADM, Optical Amplifier and Optical Line Amplifier maintains a front panel alarm
indicator providing the alarm status at chassis level to provide the specific hardware and software status.
The DTN/DTN-X/FlexROADMs front panel also provides the bay level LEDs to indicate the hardware and
software status. A lamp test verifies that all the LEDs work.
Note: It is a mandatory diagnostic test that is run as part of the initial turn-up and test procedure for
DTN-X. It can also be performed as a periodic maintenance task.
The front panel contains a lamp test button for testing the LEDs. When the lamp test button is pressed, all
LEDs on the I/O panel and the circuit packs on the chassis are lit (power LEDs illuminate Green and fault
LEDs illuminate Red) and bi-color LEDs will toggle between two colors (Green and Yellow) until the lamp
test button is released. Once the lamp test button is released, all LEDs will return to the previous
condition.
Refer to Hardware Description Guides for more details.
Note: The lamp test requires XCM/MCM/IMM/IMM-B/OMM presence and the chassis to be powered.

3-40 Optical Time Domain Reflectometer (OTDR) Testing
Optical Time Domain Reflectometer (OTDR) Testing

Release 16.1.1 introduces the Optical Time Domain Reflectometer Module (OTDM), which performs
optical time domain reflectometer (OTDR) testing for line fibers on the FlexILS line system via the OTDR
ports on the IAM-2/IRM (OTDR ports are not supported on IAM-1). The OTDM OTDR PTP port can be
associated to the Amplifier OTDR PTP on an IAM-2/IRM, or the OTDM can operate in standalone mode.
The OTDR test is manually started and stopped by a user via the OTDM OTDR PTP object. The OTDR
test results are stored in the OTDRTESTRESULT and OTDRKEYEVENTLIST managed objects on the
node, and also in a “.sor” file which can be uploaded to an external server.
The parameters for OTDR test, such as acquisition mode, pulse width, and test detection range, can be
modified via the OTDM OTDR PTP object.
Note the following for OTDR tests:
■ There is no restriction on the IAM-2/IRM OTDR ports to which the OTDM’s four ports are
connected: The four OTDM ports can be connected to four different IAM-2/IRM modules, or two of
the OTDM ports can be connected to the same IAM-2/IRM. The connected IAM-2/IRM modules
can be on the same chassis as the OTDM, or on a different chassis.
■ OTDR tests can be started on any one of the four OTDM ports, provided that the OTDM is not in
the Locked administrative state.
■ If one port of an OTDM is running a test, the other ports cannot start a new test.
■ For tests where the OTDM OTDR PTP port is associated to an Amplifier OTDR PTP on an IAM-2/
IRM,the Internal Spool Length of the IAM-2/IRM is compensated in the test.
■ OTDR tests are aborted in case of control module switchover, physical removal of the OTDM, cold/
warm reboot of the OTDM, or chassis disconnectivity from the node controller.
To start OTDR test
Note: This procedure explains the method to start OTDR test on OTDR ports on the IAM-2 / IRM.
Step 1 In the Chassis View, right click on the L1 / L2 / L3 / L4 port of OTDM-4D , select Properties.
The OTDM OTDR Port Properties window is displayed. For more details on OTDM OTDR properties
refer to DNA Configuration Management Guide
Step 2 Click Start OTDR Test to start the test.
The OTDR Test is started and it stops automatically once completed.
Step 3 Click on Show Test Results to check the result of the OTDR Test.
All OTDR Test results are displayed with the latest result on top.
Step 4 Click Stop OTDR Test to stop the currently running OTDR Test.

Optical Test Access Ports

Optical Spectrum Analyzer (OSA) ports are provided on the BMM (see Figure 3-8: OSA Ports on the
BMM on page 3-42) and OAM (see Figure 3-9: OSA Ports on the OAM on page 3-43) for turn-up and
diagnostic purposes. These ports are provided for the aggregate line input and the receive Erbium Doped
Fiber Amplifier (EDFA) output. There are several monitoring ports to connect to an OSA to measure the
optical spectrum in the field without affecting the traffic. OSA ports monitors the:
■ Total optical power of the aggregated line signal
■ Power of the individual wavelengths carrying customer traffic
■ Optical Signal to Noise Ratio (OSNR) of the individual wavelengths carrying customer traffic
■ Frequency of the individual wavelengths carrying customer traffic
■ Spectral width of the individual wavelengths carrying customer traffic
The monitoring ports present on the BMM and the OAM are:
■ OSA Monitor In
■ OSA Monitor Out
■ RX Amplifier Out (BMM only)
The optical power at the OSA monitor port is measured using a optical power meter.
The network element collects Performance Monitoring (PM) data maintained in counters and is
retrievable by the user via the management interfaces (DNA, DNA, and/or TL1). It can also be
configured to periodically send a CSV file to designated File Transfer Protocol (FTP) server. The
retrieved PM data is studied for the following parameters:
■ OTS-OPT-OSA-TAP-RATIO - Expected ratio of OTS-OPT and the power measured at the Line Tx
OSA monitor port
■ OTS-OPR-OSA-TAP-RATIO - Expected ratio of OTS-OPR and the power measured at the
received port on the line OSA monitor port
■ CBand-Rx-Post EDFFA-OSA-TAP-RATIO - Expected ratio of CBand-Rx-Post EDFA-OPT to the
power measured at the RX Amplifier Out OSA monitor port
The system displayed data is compared with the actual power levels measured manually by
personnel onsite. In the event of a discrepancy, an alarm is raised.

3-42 Optical Test Access Ports
Figure 3-8 OSA Ports on the BMM

Figure 3-9 OSA Ports on the OAM
OWM-BLANK
OAM-CXH-A
INVISIBLE LASER
RADIATION
DO NOT VIEW
DIRECTLY WITH
OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT (IEC)
CLASS I LASER
PRODUCT (CDRH)
1550nm-50mW
OSA Monitor
Connectors
for Line Input
and Output infn_040

3-44 Optical Test Access Ports

CHAPTER 4
ATN Diagnostics
This chapter describes the troubleshooting tools that can be used to troubleshoot the ATN network
element and the Infinera Intelligent Transport Network. This chapter is divided into the following sections:
Loopbacks in ATNs on page 4-2
Trace Messaging in ATNs on page 4-25
PRBS Tests in ATNs on page 4-32
Test Signal Generation for Fibre Channel Clients in ATNs on page 4-42
GbE Client Termination Point Tests in ATNs on page 4-45
Lamp Testing in ATNs on page 4-48
Point Loss Adjustment Utility on page 4-49

4-2 Loopbacks in ATNs
Loopbacks in ATNs
Loopbacks are used to test newly created circuits before running live traffic or to logically locate the
source of a network failure on existing circuits. Loopbacks provide a mechanism where the signal under
test (either the user signal or the test pattern signal such as PRBS) is looped back at some location on
the network element in order to test the integrity and validity of the signal being looped back. Since
loopbacks affect normal data traffic flow, they must be invoked only when the associated facility is in
IQA NOS ATN provides access to the loopback capabilities in an ATN, independent of the client signal
payload type. This section describes the loopbacks supported to test each section of the network, as well
as the various hardware components along the data path. The loopbacks can be enabled or disabled
remotely through the management applications.
Loopbacks:
■ are provisioned on a per channel basis without affecting the traffic on the other channels.
■ are persistent, that is on power cycle or on a switch over, the loopback will be in place on the
managed object.
■ enable the generation of the following alarms:
□ Facility Loopback enabled
□ Terminal Loopback enabled
□ are agnostic to the client signal type and hence can be run for OC-192, STM-64, 10GbE,
OC3, OC12, 1GbE, 1/2/8 GFC.
■ allow performance monitoring data to be collected in parallel without interrupting the test.
■ must be released manually after the test is complete.
The ATN supports the following:
SIM-T-1-10G Loopbacks on page 4-3
SIM-T-2-2.5GM Loopbacks on page 4-4
SIM-T-1-10GT Loopbacks on page 4-5
SIM-A-8-2.5GMT Loopbacks on page 4-8
SIM-A-8-1GE Loopbacks on page 4-10
SIM-T-1-10GP and SIM-T-1-10GM Loopbacks on page 4-12
Note: Loopbacks are not supported on facilities that are Digital Subnetwork Connection
Protection (D-SNCP) protected. If loopbacks are required on these facilities, the loopback must
be performed prior to configuring the protection group. If the facilities are already protected,
then the protection group must be deleted and then loopbacks can be invoked.

ATN Diagnostics 4-3
SIM-T-1-10G Loopbacks
Figure 4-1: Client CTP Facility Loopback on page 4-3 through Fig: Client CTP Terminal Loopback
show the loopbacks on the SIM-T-1-10G. Each of these loopbacks are described below its figure.
■ Client CTP Facility Loopback
Figure 4-1 Client CTP Facility Loopback
A loopback is performed on the tributary-side TOM in the SIM-T-1-10G wherein the tributary port Rx on
the TOM is looped back to the Tx port on the same TOM. This loopback test verifies the operation of the
tributary side optics in the TOM and the SIM-T-1-10G.
■ Client CTP Terminal Loopback
Client CTP Terminal Loopback
A loopback is performed on the tributary-side of the SIM-T-1-10G wherein the signal received from the Rx
port on the line TOM is looped back to the Tx port on the same TOM via the G.709 Mapper and the line-
side SerDes. This loopback verifies the line side optics on the SIM-1-T-10G as well as the G.709 mapper.
■ Line OTU2 CTP Terminal Loopback
A loopback performed on the line-side TOM in the SIM-T-1-10G wherein the OTU2 signal received
from the Rx port on the line TOM is looped back to the Tx port on the same TOM. This loopback
verifies the line OTU2 connectivity and the G.709 encapsulation performed in the SIM-T-1-10G.

Line OTU2 CTP Terminal Loopback
SIM-T-2-2.5GM Loopbacks
ATN supports loopbacks on the 2.5G Multi-rate Service Interface Modules (SIM-T-2-2.5GMs). Figure 3-38
on page 3-61 and Figure 3-39 on page 3-62 show the supported loopbacks. Each of these loopbacks are
described below its figure.
■ Clear Channel Client CTP Facility Loopback
Figure 4-2 Clear Channel Client CTP Facility Loopback
A loopback is performed on the tributary-side TOM in the SIM-T-2-2.5GM wherein the signal received
from Rx port on the tributary-side TOM is looped back to the Tx port on the same TOM. This loopback
test verifies the operation of the tributary side optics in the TOM and the SIM-T-2-2.5GM.

ATN Diagnostics 4-5
Clear Channel Line CTP Terminal Loopback
■ Clear Channel Line CTP Terminal Loopback

A loopback is performed on the line-side TOM in the SIM-T-2-2.5GM wherein the signal received
from Rx port on the line TOM is looped back to the Tx port on the same TOM. This loopback test
verifies the operation of the line side optics in the TOM and the SIM-T-2-2.5GM.
SIM-T-1-10GT Loopbacks
Figure 3-40 on page 3-62 through Figure 3-45 on page 3-65 show the loopbacks on the SIM-T-1-10GT.
Each of these loopbacks are described below its figure.
■ DCH CTP Terminal Loopback
Figure 4-3 DCH CTP Terminal Loopback
A loopback is performed on the line-side of the SIM-T-1-10GT wherein the signal received from the Rx
port on the line TOM is looped back to the Tx port on the same TOM via the transponder processor. This
loopback verifies the line side optics on the TOM and the SIM-T-1-10GT.
■ DCH CTP Facility Loopback

DCH CTP Facility Loopback
SIM-T-1-10GT
Trib TOM Transponder IFC10 IFC10 SerDes Line TOM

Processor
infn_644
port on the tributary-side TOM is looped back to the Tx port on the same TOM via the transponder
processor, IFC10s and the line-side SerDes. The DTF signal about to be transmitted is looped back to
verify the DTF encapsulation performed in the IFC10 of the local SIM up to the SerDes.
■ Line DTP CTP Facility Loopback
Line DTP CTP Facility Loopback
port on the tributary-side TOM is looped back to the Tx port on the same TOM via the SerDes, tributary-
side IFC10 and the line-side IFC10. The DTF signal about to be transmitted is looped back to verify the
DTF encapsulation performed in the IFC10.
■ Trib DTP CTP Terminal Loopback

ATN Diagnostics 4-7
Trib DTP CTP Terminal Loopback
A loopback is performed on the tributary-side of the SIM-T-1-10GT wherein the signal received from the
Rx port on the line TOM is looped back to the Tx port on the same TOM via the transponder processor,
line-side IFC10 and the tributary-side IFC10. This loopback verifies the DTF de-encapsulation performed
in the IFC10.
A loopback is performed on the tributary-side of the SIM-T-1-10GT wherein the signal received from the
Rx port on the line TOM is looped back to the Tx port on the same TOM via the SerDes, line-side and the
tributary-side IFC10s and the tributary-side transponder processor. This loopback verifies the line side
optics on the TOM and the SIM-T-1-10GT.
Client CTP Facility Loopback

port on the tributary-side TOM is looped back to the Tx port on the same TOM via the transponder
processor. This loopback verifies the tributary-side optics on the TOM and SIM-1-T-10GT.
Note: In SIM-T-1-10GT regen mode, Client CTP is DCh CTP and all Client CTP loopbacks are
termed DCh CTP loopbacks.
SIM-A-8-2.5GMT Loopbacks
Figure 4-4: DCH CTP Terminal Loopback on page 4-8 through Fig: Client CTP Facility show the
loopbacks on the SIM-A-8-2.5GMT. Each of these loopbacks are described below its figure.
■ DCH CTP Terminal Loopback
Figure 4-4 DCH CTP Terminal Loopback
A loopback is performed on the line-side of the SIM-A-8-2.5GMT wherein the signal received from the Rx
port on the line TOM is looped back to the Tx port on the same TOM via the cross point switch and the
SerDes. This loopback verifies the line side optics on the TOM and the
SIM-A-8-2.5GMT.
■ DCH CTP Facility Loopback
DCH CTP Facility Loopback
port on the tributary-side TOM is looped back to the Tx port on the same TOM via the ISC10, IFC10 and

ATN Diagnostics 4-9
the line-side SerDes. The DTF signal about to be transmitted is looped back to verify the DTF
encapsulation performed in the IFC10 of the local SIM up to the SerDes.
■ Line DTP CTP Facility Loopback
Line DTP CTP Facility Loopback
port on the tributary-side TOM is looped back to the Tx port on the same TOM via the ISC10 and the line-
side IFC10. The DTF signal about to be transmitted is looped back to verify the DTF encapsulation
performed in the IFC10.
■ Trib DTP CTP Terminal Loopback
Trib DTP CTP Terminal Loopback
A loopback is performed on the tributary-side of the SIM-A-8-2.5GMT wherein the signal received from
the Rx port on the line TOM is looped back to the Tx port on the same TOM via the SerDes, line-side
IFC10 and the tributary-side ISC10. This loopback verifies the line side optics on the TOM and the
SIM-A-8-2.5GMT.

A loopback is performed on the tributary-side of the SIM-A-8-2.5GMT wherein the client signal received
from the Rx port on the line TOM is looped back to the Tx port on the same TOM via the SerDes, line-side
IFC10 and the tributary-side ISC10. This loopback verifies the line side optics on the TOM and the SIM-
A-8-2.5GMT.
Client CTP Facility
A loopback is performed on the line-side of the SIM-A-8-2.5GMT wherein the client signal received from
the Rx port on the tributary-side TOM is looped back to the Tx port on the same TOM via the ISC10. This
loopback verifies the tributary-side optics on the TOM and SIM-A-8-2.5GMT.
SIM-A-8-1GE Loopbacks
Figure 4-6: Client CTP Facility Loopback (SIM-T-1-10GM) on page 4-13 show the loopbacks on the SIM-
A-8-1GE. Each of these loopbacks are described below its figure.

ATN Diagnostics 4-11
Figure 4-5 Client CTP Facility Loopback
A loopback is performed on the tributary-side of the SIM-A-8-1GE wherein the signal received from the Rx
port on the tributary-side is looped back to the Tx port on the tributary-side via the Ethernet switch. This
loopback verifies the tributary-side optics.
A loopback is performed on the tributary-side of the SIM-A-8-1GE wherein the client signal received from
the Rx port on the line TOM is looped back to the Tx port on the same TOM via the OTU Mapper and the
Ethernet switch. This loopback verifies the line side optics on the SIM-A-8-1GE as well as the OTU
mapper.
■ OTU2e Line CTP Terminal Loopback

OTU2e Line CTP Terminal Loopback
A loopback is performed on the tributary-side of the SIM-A-8-1GE wherein the signal received from the Rx
port on the line TOM is looped back to the Tx port on the same TOM via the OTU Mapper. This loopback
verifies the line side optics on the TOM and the SIM-A-8-1GE.
SIM-T-1-10GP and SIM-T-1-10GM Loopbacks

Figure 4-6: Client CTP Facility Loopback (SIM-T-1-10GM) on page 4-13 through Fig: Client CTP
Terminal Loopback show the loopbacks on the SIM-T-1-10GP and SIM-T-1-10GM. Each of these
loopbacks are described below its figure.
The SIM-T-1-10GM, includes one Trib TOM and one Line TOM only. All loopbacks that can be performed
on the SIM-T-1-10GP are applicable for the SIM-T-1-10GM also.

Figure 4-6 Client CTP Facility Loopback (SIM-T-1-10GM)
A loopback is performed on the tributary-side of the SIM-T-1-10GP or SIM-T-1-10GM wherein the signal
received from the Rx port on the tributary-side is looped back to the Tx port on the tributary-side. This
loopback verifies the tributary-side optics.
■ Line OTUk CTP Facility Loopback
Line OTUk CTP Facility Loopback
A loopback is performed on the line-side of the SIM-T-1-10GP or SIM-T-1-10GM wherein the signal
received from the Rx port on the tributary-side is looped back to the Tx port on the tributary-side via the
line-side. This loopback verifies the tributary-side optics and OTUk signal on the line-side.
■ Line OTUk CTP Terminal Loopback

Line OTUk CTP Terminal Loopback
A loopback is performed on the line-side of the SIM-T-1-10GP or SIM-T-1-10GM wherein the signal
received from the Rx port on the line-side is looped back to the Tx on the line-side. This loopback verifies
the line side optics.

A loopback is performed on the tributary-side of the SIM-T-1-10GP or SIM-T-1-10GM wherein the signal
received from the Rx port on the line-side is looped back to the Tx port on the tributary-side. This
loopback verifies the optics on the tributary-side and line on the SIM-T-1-10GP or SIM-T-1-10GM.
Note: All of the above described SIM-T-1-10GP loopbacks can be performed through Line 1 or Line 2
of the SIM-T-1-10GP.
Note: In SIM-T-1-10GP regen mode, Client CTP is OTUk CTP and all Client CTP loopbacks are
termed OTUk CTP loopbacks.

Setting Loopbacks on a ATN Circuit Pack

Facility loopbacks are supported on a line port or a tributary port of the 2.5G or 10G SIM TOMs. These
circuit packs support same-port loopbacks that can be individually configured for each tributary and line
port. When enabled, this loopback directs the data received at the input of that port to be transmitted
unchanged to the output of that port.
Note: The facility under test must be placed in the Administrative Maintenance state, for loopback
settings to be enabled. The loopback must be removed prior to restoring the Administrative state to
Unlocked.This resumes normal reporting of alarms. Diagnostics can no longer be applied to that
termination point.
Note: Loopbacks are not supported on facilities that are Digital SNCP-protected. If loopbacks are
required on these facilities, the loopback must be applied prior to configuring the protection group. If
the facilities are already protected, then the protection group must be deleted and then loopbacks can
be invoked.
Note: Traffic Disruption Risk: Setting loopbacks on a network is potentially service affecting
Setting up Loopbacks on SIM-T-1-10G

Client CTP loopbacks can be set from the SONET, SDH and GbE Client Properties windows. See DNA
Configuration Management Guide for procedures to launch these windows. This section describes the
following procedures:
■ To set a Client CTP Facility Loopback for a termination point on page 4-15
■ To set a Client CTP Terminal Loopback for a termination point on page 4-16
■ To set a Client Line OTUk CTP Facility Loopback for a termination point on page 4-17
To set a Client CTP Facility Loopback for a termination point
Note: Client CTP facility loopbacks can be set from the SONET, SDH and GbE Client Properties
windows. This procedure explains the method to set a Client CTP Facility loopback from the SONET
Client Properties window.
Note: The process of placing the equipment which is under test, in the Administrative Maintenance
state can be performed either before enabling the loopback or simultaneously, while enabling the
loopback.


■ In the Equipment View right-click the tributary side SIM TOM and select Client trib termination
point.
■ In the Equipment Tree, right-click the tributary side SIM TOM icon and select Client trib
termination point.
■ In the Facility Manager, right-click the row for the required SONET and click Properties....
Step 2 Select State tab. Change the Admin State to Maintenance.
Step 5 From the Loopback drop-down menu, select Facility to set loopback.
A warning message Turning On loopback will affect the traffic. Do you want to
continue? is displayed.
To set a Client CTP Terminal Loopback for a termination point
Note: Client CTP terminal loopbacks can be set from the SONET, SDH and GbE Client Properties
windows. This procedure explains the method to set a Client CTP Terminal Loopback from the
SONET Client Properties window.
loopback.

■ In the Equipment View right-click the tributary side SIM TOM and select Client trib termination
point.
■ In the Equipment Tree, right-click the tributary side SIM TOM icon and select Client trib
termination point.
■ In the Facility Manager, right-click the row for the required SONET and click Properties.


Step 5 From the Loopback drop-down menu, select Terminal to set loopback.
To set a Client Line OTUk CTP Facility Loopback for a termination point
Note: This procedure explains the method to set a Client Line OTU2 CTP Facility Loopback from the
OTUk Client Properties window.
loopback.

■ In the Equipment View right-click the Line side SIM-T-1-10G/SIM-T-1-10GP/SIM-T-1-10GM
TOM and select Line Trib Termination Point.
■ In the Equipment Tree, right-click the Line side SIM-T-1-10G/SIM-T-1-10GP/SIM-T-1-10GM
TOM icon and select Line Trib Termination Point.
■ In the Facility Manager, right-click the row for the required OTUk Client and click Properties....
Step 8 Click Close to exit the OTUk Client Properties window.
Setting up Loopbacks on SIM-T-2-2.5GM

This section describes the following procedures:

■ To set a Client Facility Loopback for a termination point on page 4-18

■ To set a Line Facility Loopback for a termination point on page 4-18
To set a Client Facility Loopback for a termination point
Note: This procedure explains the method to set a Client Facility Loopback from the Properties
window.
loopback.

■ In the Equipment View right-click the tributary side SIM-T-2-2.5GM TOM and select Client trib
termination point.
■ In the Equipment Tree, right-click the tributary side SIM-T-2-2.5GM TOM icon and select Client
trib termination point.
■ In the Facility Manager, right-click the row for the required and click Properties.
The Properties window (for tributary side) is displayed.
Step 8 Click Close to exit the Properties window.
To set a Line Facility Loopback for a termination point
Note: This procedure explains the method to set a Line Facility Loopback from the Properties window.
loopback.


■ In the Equipment View right-click the Line side SIM-T-2-2.5GM TOM and select Line Trib
Termination Point.
■ In the Equipment Tree, right-click the Line side SIM-T-2-2.5GM TOM icon and select Line Trib
Termination Point.
■ In the Facility Manager, right-click the row for the required Line trib termination point and click
Properties....
The Properties window (for line side) is displayed.
Step 8 Click Close to exit the Properties window.
Setting up Loopbacks on SIM-T-1-10GT/SIM-A-8-2.5GMT

■ To setup Line DCH CTP Terminal Loopback on page 4-19
■ To setup Line DCH CTP Facility Loopback on page 4-20
■ To setup Line DTP CTP Facility Loopback on page 4-20
■ To setup Trib DTP CTP Terminal Loopback on page 4-21
To setup Line DCH CTP Terminal Loopback
loopback.

■ In the Equipment View right-click the Line side SIM-T-1-10GT/SIM-A-8-2.5GMT TOM and select
Digital Channel.
■ In the Equipment Tree, right-click the Line side SIM-T-1-10GT/SIM-A-8-2.5GMT TOM icon and
select Digital Channel.
■ In the Facility Manager, right-click the row for the required Digital Channel and click Properties.
The Digital Channel Properties window (for line side) is displayed.


To setup Line DCH CTP Facility Loopback
loopback.

Digital Channel.
■ In the Facility Manager, right-click the row for the required Digital Channel and click Properties.
The Digital Channel Properties window (for line side) is displayed.
To setup Line DTP CTP Facility Loopback
loopback.


Line DTF Path.
select Line DTF Path.
■ In the Facility Manager, right-click the row for the required Line DTF Path and click Properties.
The Line DTF Path Properties window (for line side) is displayed.
Step 8 Click Close to exit the line DTF Path Properties window.
To setup Trib DTP CTP Terminal Loopback
loopback.

■ In the Equipment View right-click the tributary side SIM-T-1-10GT/SIM-A-8-2.5GMT TOM and
select Trib DTF Path.
■ In the Equipment Tree, right-click the tributary side SIM-T-1-10GT/SIM-A-8-2.5GMT TOM icon
and select Trib DTF Path.
■ In the Facility Manager, right-click the row for the required Trib DTF Path and click Properties.
The Trib DTF Path Properties window (for line side) is displayed.


Setting up Loopbacks on SIM-A-8-1GE

Client CTP Loopbacks can be set from the GbE Client Properties windows.
To set a Client CTP Facility Loopback for SIM-A-8-1GE on page 4-22
To configure the Client CTP Terminal Loopback on page 4-22
To configure OTU2e CTP Terminal Loopback on page 4-23
To set a Client CTP Facility Loopback for SIM-A-8-1GE
loopback.

■ In the Equipment View right-click the tributary side SIM TOM and select Client Trib Termination
point.
■ In the Equipment Tree, right-click the tributary side SIM TOM icon and select Client Trib
Termination point.
■ In the Facility Manager, right-click the row for the required GbE Client and click Properties.
Step 9 Click Close to exit the GbE Client Trib Properties window.
To configure the Client CTP Terminal Loopback
loopback.


■ In the Equipment View right-click the tributary side SIM TOM and select Client Trib Termination
point.
■ In the Equipment Tree, right-click the tributary side SIM TOM icon and select Client Trib
Termination point.
■ In the Facility Manager, right-click the row for the required GbE Client and click Properties.
Step 9 Click Close to exit the GbE Client Trib Properties window.
To configure OTU2e CTP Terminal Loopback
loopback.

■ In the Equipment View right-click the Line side SIM TOM and select Line Trib Termination point.
■ In the Equipment Tree, right-click the Line side SIM TOM icon and select Line Trib Termination
point.
■ In the Facility Manager, right-click the row for the required OTU Client and click Properties.
The OTUk Line Properties window is displayed.


Step 9 Click Close to exit the OTUk Line Properties window.

Trace Messaging in ATNs

Trace messaging is a non-intrusive diagnostic tool. It can be used to determine commissioning problems
such as fiber mis-connections. Trace Messages are trace bytes of HEX (1 byte) or ASCII encoded
character set and can be of 16 or 64 bytes. They are provisioned from management applications like
InfineraATN GNM or CLI. When 1, 16 or 64 byte trace messaging is enabled, the ATN compares the
received trace message with the expected trace message and in case of a mismatch, reports an alarm.
IQA NOS ATN provides access to the trace messaging feature supported by the ATN. The ATN supports
the following trace messaging functions:
SONET/SDH J0 Trace Messaging on page 4-27
OTU Section TTI Trace Messaging on page 4-29
Digital Channel Section Level Trace Messaging on page 4-30
DTF Path Trace Messaging on page 4-31
■ Trace messaging at the SONET/SDH J0 on the tributary ports (see Figure 4-7: SONET/SDH/J0/
OTUk Trace Messaging on page 4-25).
The ATN provides the capability to monitor and transmit J0 messages received from the client
equipment. This capability enables the detection of mis-connections between the client equipment
and the ATN. The ATN can insert and monitor 1, 16 and 64 byte J0 trace messages. The ATN can
either transparently pass on the J0 message from the line side, or it can receive and overwrite the
incoming J0 message before transmitting the message toward the client interface. The J0 message
can be configured to comply with either the ANSI ITU (SDH) or the GR-253 (SONET) standard.
■ OTUk Trail Trace Identifier (TTI) trace messaging (see Figure 4-7: SONET/SDH/J0/OTUk Trace
Messaging on page 4-25).
Trail Trace Identifier (TTI) is an ASCII string passed at the OTUk on the line port of SIM-T-1-10G,
SIM-T-1-10GP, SIM-T-1-10GM and SIM-A-8-1GE. The ATN provides the capability to monitor the
TTI messages received from OTUk. This capability enables the detection of mis-connections
between the equipment within the ATN Network. The TTI is a 64 byte ASCII string and is
provisioned from the management applications like ATN GNM, or CLI.
Figure 4-7 SONET/SDH/J0/OTUk Trace Messaging
■ Digital Channel Section level (DChCTP) TTI trace messaging (see Fig: DChCTP and DTPCTP
Trace Messaging)

4-26 Trace Messaging in ATNs
Digital Channel Section level (DChCTP) TTI trace messaging This test is performed between any
of the following:
□ Two adjacent SIM-T-1-10GTs
□ Two adjacent SIM-A-8-2.5GMTs
□ A SIM-T-1-10GT and the adjacent SIM-A-8-2.5GMT
□ A SIM-T-1-10GT or SIM-A-8-2.5GMT and the adjacent DTN TAM-2-10GT
The Trail Trace Identifier (TTI) is passed between an IFC10 associated with the Digital
Channel (DCh) line CTP of one SIM and an IFC10 associated with the DCh line CTP of the
adjacent SIM or a DTN TAM-2-10GT.
ATN provides the capability to monitor received TTI messages and detect mis-connections
between the equipment within the ATN Network. The DChCTP TTI is a 64 byte ASCII string
and is provisioned from the management applications like ATN GNM, or CLI.
■ DTF Path level (DTPCTP) TTI trace messaging (see Fig: DChCTP and DTPCTP Trace Messaging)
Digital Channel Path level (DTPCTP) TTI trace messaging is performed between any of the
following:
□ Two SIM-T-1-10GTs at either end of a DTF Path Layer
□ Two SIM-A-8-2.5GMTs at either end of a DTF Path Layer
□ One SIM-T-1-10GT and one SIM-A-8-2.5GMT at either end of a DTF Path Layer
□ One SIM-T-1-10GT or SIM-A-8-2.5GMT and one DTN TAM-2-10GT at either end of a DTF
Path Layer
The Trail Trace Identifier (TTI) is passed between an IFC10 associated with the Digital
Transport Path (DTP) client CTP of one SIM and monitored at the IFC10 associated with the
DTP client CTP of the adjacent SIM or DTN TAM-2-10GT.
ATN provides the capability to monitor received TTI messages and detect mis-connections
between the equipment within the ATN Network. The DTPCTP TTI is a 64 byte ASCII string
and is provisioned from the management applications like ATN GNM, or CLI.
DChCTP and DTPCTP Trace Messaging
■ TOM auto-discovery trace

ATN supports automatic discovery of the TOM connectivity between the line ports of the two ATN
SIM modules or an ATN SIM and DTN TOM module, when the DTF line protocol is used between
the ATN SIM modules. ATN uses the DTF line protocol (DTL) based TTI trace overhead to auto-
discover ATN-ATN and ATN-DTN TOM connectivity. The DTL based TTI is a system provisioned
ASCII string that identifies the Port ID of the transmitting port. The expected value of the received
TTI can be configured from management applications like ATN GNM, or CLI.
Trace messaging tool is a diagnostic tool used to monitor the type and the accuracy of the traffic. It
is also used to determine commissioning problems such as wrongly connected fibers. Trace
Messages:
■ must be enabled/disabled manually from management applications like ATN GNM, CLI and DNA.
■ can be provisioned from management applications like GNM, CLI and DNA.
■ are trace bytes of ASCII encoded character set.
The network element compares the received trace message with the expected trace message, and
in case of a mismatch, reports a mismatch alarm.
Figure 4-8 J0 and TTI Trace Messaging
SONET/SDH J0 Trace Messaging

The ATN supports the SONET/SDH J0 trace messaging at the tributary ports on the 10G SIM and GMT
SIM.
The ATN provides J0 message transparency, that is, the option to forward the J0 message received from
the network or to overwrite it with the user defined J0 message. The ATN also provides the ability to write
to the J0 trace message received from the client equipment and transmit towards the client equipment.
This capability enables far-end continuity verification and simplifies the client to ATN circuit connectivity
verification. The ATN can monitor 1, 16 and 64 byte J0 trace messages. The J0 message can be
configured to comply with either the ANSI ITU or the GR-253 standard.
■ Client Facility side section/RS trace support (J0), including selection of
□ ITU or GR-253 format,
□ transparent or overwrite mode,
□ trace message length (1|16|64B), and
□ mismatch reporting option

■ An option to monitor the section/RS trace received from the facility receive direction for mismatch
(received through the client interface)
■ An option to overwrite the section/RS trace received from the system backplane interface, allowing
for a new section/RS trace to be inserted and sent out to the client interface)
Note: In the J0 trace message (ASCII format), all characters after CR/LF are ignored.
To enable the reporting of J0 trace mismatch condition

■ In the Equipment View, right-click the required tributary side SIM-A-8-2.5GMT/SIM-T-1-10G/
SIM-T-1-10GM/SIM-T-1-10GP/SIM-T-1-10GT SIM TOM and select Client Trib Termination
Point.
■ In the Equipment Tree, right-click the required tributary side SIM-A-8-2.5GMT/SIM-T-1-10G/
SIM-T-1-10GM/SIM-T-1-10GP/SIM-T-1-10GT SIM TOM icon and select Client Trib Termination
Point.
■ In the Facility Manager, right-click the row for the required SONET/SDH termination point and
click Properties.
The Client Trib Properties window for SONET/SDH (based on the selection) is displayed.
SONET Client Trib Properties window is displayed in this example.
Step 2 Select Diagnostics tab. Figure 4-13 on page 4-9 shows the Diagnostics tab for SONET.
Step 3 In the Section Trace (J0) panel, enter and select values for the following parameters:
■ Section Trace (J0) Standard Compliance—Select ANSI_ITU or GR253R3 from the J0 message
compliance Standard drop-down menu. ANSI_ITU is the default.
■ Section Trace (J0) Trace Mode—Select one of the following:
□ Transparent—Select this radio button to ignore the configured ‘Transmit’ and
transparently forward the ‘Receive’ towards the client equipment. This is the default value
for Trace Mode.
□ Overwrite—Select this radio button to overwrite the ‘Receive’ and forward the configured
‘Transmit’ towards the client equipment. Only when this option is selected, Transmit is
enabled.
Note: An informational message is displayed on switching between the transparent

and overwrite modes.
■ Section Trace (J0) Length—Select the length (in bytes) of the J0 message. Valid values are 1,
16 and 64. The transmitted and expected J0 messages will not exceed this length. The default
value is 16.
■ Section Trace (J0) Transmit—Enter a string of ASCII characters, no longer than the set length,
for the Transmit J0 message. This value is sent towards the client equipment only if Trace Mode
is set to Overwrite. This field is disabled if Trace Mode is set to Transparent.

■ Section Trace (J0) Expected—The expected J0 trace message at this network element. This
may be entered. This is an optional message.
■ Receive—The received J0 trace message. This is a read-only message.
■ Section Trace (J0) Mismatch Reporting—Flag that enables the reporting of mismatch alarms
when the Receive and Expected trace do not match. If you want a mismatch alarm to be
reported, select Enabled from the drop-down menu. This is disabled by default.
■ Click Refresh Received and Transmitted J0 to update the Section Trace (J0) Transmit and
Receive values.
OTU Section TTI Trace Messaging

ATN supports OTU section TTI trace messaging. Trail Trace Identifier (TTI) is an ASCII string passed at
the OTUk on the line port of the SIM. The ATN provides the capability to monitor the TTI messages
received from OTUk. This capability enables the detection of mis-connections between the equipment
within the ATN network. The TTI is a 64 byte ASCII string and is provisioned from the management
applications like ATN GNM or CLI.
To enable reporting of TTI trace mismatch condition

■ In the Equipment View right-click the Line side SIM-T-1-10G/SIM-T-1-10GM/SIM-T-1-10GP/
SIM-A-8-1GE SIM TOM and select Line Trib Termination Point.
■ In the Equipment Tree, right-click the Line side SIM-T-1-10G/SIM-T-1-10GM/SIM-T-1-10GP/
SIM-A-8-1GE SIM TOM icon and select Line Trib Termination Point.
■ In the Facility Manager, right-click the row for the required OTUk Line and click Properties....
Step 3 In the Trail Trace Identifier (TTI) panel, do the following:
■ In the Transmit sub-panel, enter and select values for the following parameters:
□ Insert TTI—Check box, which when selected, enables the TTI string to be entered and
monitored at the far end.
□ Tx SAPI—Enter the value for Transmitted TTI Source Access Point Identifier bytes.
□ Tx DAPI—Enter the value for Transmitted TTI Destination Access Point Identifier bytes.
■ In the Receive sub-panel, enter and select values for the following parameters:
□ Mismatch Alarm Reporting—Flag to enable or disable the reporting of TTI trace mismatch
condition.
OFF—Disable TTI mismatch alarm reporting. This is the default value.

SAPI—Enable TTI SAPI mismatch alarm reporting.

DAPI—Enable TTI DAPI mismatch alarm reporting.
DAPI_SAPI—Enable TTI mismatch alarm reporting for SAPI and DAPI.
□ Expected SAPI—Enter the value for Expected TTI Source Access Point Identifier bytes.
This is a string with a maximum of 15 characters.
□ Expected DAPI—Enter the value for Expected TTI Destination Access Point Identifier
bytes. This is a string with a maximum of 15 characters.
□ Received SAPI—The actual SAPI in the TTI message received. This is a string with a
maximum of 15 characters.
□ Received DAPI—The actual DAPI in the TTI message received. This is a string with a
maximum of 15 characters.
□ Click Refresh to update the Expected and Received SAPI and DAPI values.
Digital Channel Section Level Trace Messaging

To enable Digital Channel Section trace messaging

■ In the Equipment View, right-click the Line side SIM-T-1-10GT or SIM-A-8-2.5GMT TOM and
■ In the Equipment Tree, right-click the Line side SIM-T-1-10GT or SIM-A-8-2.5GMT TOM and
■ Insert—Flag that enables the TTI string to be entered and monitored at the far end.
■ TTI Alarm Reporting—Flag that enables alarm reporting if the expected TTI does not match the
received TTI.

DTF Path Trace Messaging

The Line and Trib DTF Path trace messaging is utilized to detect any mis-connections in the circuit path
along the Intelligent Transport Network.
To enable DTF Path trace messaging

■ In the Equipment View, right-click the Trib slide SIM-T-1-10GT or SIM-A-8-2.5GMT TOM icon
■ In the Equipment Tree, right-click the Trib slide SIM-T-1-10GT or SIM-A-8-2.5GMT TOM icon
Step 3 In the Trail Trace Identifier panel, enter and select the following values:
■ Insert—Flag that enables the TTI string to be entered and monitored.
expected TTI.
Note: This feature should be active on both ends of the Trib DTF path, to operate correctly.

4-32 PRBS Tests in ATNs
PRBS Tests in ATNs

ATN provides Pseudo Random Bit Sequence (PRBS) Test generation and monitoring capabilities.The
PRBS is a test pattern used to diagnose and isolate the troubled spots in the network, without requiring a
valid data signal or customer traffic. This type of test signal is used during the system turn-up or in the
absence of a valid data signal from the customer equipment. The test is primarily aimed to watch for and
sectionalize the occurrence of bit errors in the data path. Since the PRBS test affects normal data traffic
flow, it must be invoked only when the associated facility is in administrative maintenance state.
IQA NOS ATN provides access to the PRBS generation and monitoring capabilities supported by the
ATN. The PRBS test can be enabled or disabled remotely through the management applications.
Note: Since the PRBS test affects normal data traffic flow, it must be invoked only when the
associated facility is in Administrative Maintenance state. Once the PRBS tests are performed and
the PRBS modes are disabled, the associated facility may be reverted to Administrative Unlocked
state.
Note: The PRBS tests can be coupled with loopback tests so that the pre-testing of the quality of the
digital link or end-to-end digital path can be performed without the need for an external PRBS test set.
PRBS tests enable the generation of alarms when the PRBS generation is activated.
Note: Once the PRBS monitor acquires sync during PRBS testing using the SIM-A-8-1-GE, it does
not indicate an Out of Sync (OOS) condition again unless the PRBS monitor is disabled and re-
enabled. Therefore, if the transmit pattern changes, the receiver will detect bit errors but appear to
remain in sync. Disabling and then enabling the PRBS monitor will force the receiver to re-
synchronize.
The following PRBS tests are supported on the ATN:

OTUk Client CTP PRBS test on page 4-32
SONET Client CTP Facility PRBS Test on page 4-37
SDH Client CTP PRBS Test on page 4-38
Trib and Line DTP PRBS on page 4-40
OTUk Client CTP PRBS test

The ATN supports PRBS generation and monitoring for testing path quality at the following:
■ OTUk trib port on the SIM-T-1-10GP and SIM-T-1-10GM (applicable in case of OTU2/OTU2e regen
mode on the SIM-T-1-10GP or SIM-T-1-10GM) OR
■ OTUk line port on the SIM-T-1-10G, SIM-T-1-10GP, SIM-T-1-10GM and SIM-A-8-1GE

A PRBS signal is generated (transmitted) by the TOM in the OTUk trib port (towards the client side)
or OTUk line port (towards the line side) on the 10G Service Interface Module and is monitored
(received) by the TOM where the path is terminated.
Figure 4-9 OTUk PRBS Tests
■ Trib (facility side) PRBS test (supported for SONET and SDH interfaces on the SIM-A-8-2.5GMT)
— A PRBS signal is generated (transmitted) by the Infinera tributary towards the client network side
and is monitored (received) by the tributary in the customer equipment or the test set connected to
the Infinera tributary. PRBS generation and monitoring enables testing path quality at the SONET
Client CTP or SDH Client CTP on the SIM-A-8-2.5GMT
■ Line (terminal side) PRBS test (supported only for SONET and SDH interfaces on the
SIM-A-8-2.5GMT)— A PRBS signal is generated (transmitted) by the Infinera tributary towards the
Infinera network side and is monitored (received) by the tributary at the far-end SIM-A-8-2.5GMT.
SONET/SDH Trib and Line PRBS Tests
■ DTF Section-level PRBS test—This test is performed between any of the following:
□ Two adjacent SIM-T-1-10GTs
□ Two adjacent SIM-A-8-2.5GMTs
□ A SIM-T-1-10GT and the adjacent SIM-A-8-2.5GMT
□ A SIM-T-1-10GT or SIM-A-8-2.5GMT and the adjacent DTN TAM-2-10GT
This test is performed verify the quality of the digital link between two adjacent ATNs. A
PRBS signal is generated at an IFC10 associated with the Digital Channel (DCh) line CTP of
one SIM and monitored at an IFC10 associated with the DCh line CTP of the adjacent SIM or
DTN TAM-2-10GT.
■ DTF Path-level PRBS test—This test is performed between any of the following:
□ Two SIM-T-1-10GTs at either end of a DTF Path Layer
□ Two SIM-A-8-2.5GMTs at either end of a DTF Path Layer

□ One SIM-T-1-10GT and one SIM-A-8-2.5GMT at either end of a DTF Path Layer
□ One SIM-T-1-10GT or SIM-A-8-2.5GMT and one DTN TAM-2-10GT at either end of a DTF
Path Layer
A PRBS signal is generated at an IFC10 associated with the Digital Transport Path (DTP)
client CTP of one SIM and monitored at an IFC10 associated with the DTP client CTP of the
other SIM or TAM-2-10GT.
Note: DTF Path level skips any intermediate SIM-T-1-10GTs or SIM-A-8-2.5GMTs that
are in regen mode and considers the SIM at the actual termination of the DTF Path layer.
DTF Section/Path PRBS Tests
See Rules for Performing PRBS Tests on page 4-34 for information on performing PRBS tests.
Note: The PRBS tests can be coupled with loopback tests so that the pre-testing of the quality of the
link or end-to-end digital path can be performed without the need for an external PRBS test set. While
this is not meant as a replacement for customer-premise to customer-premise circuit quality testing, it
does provide an early indicator of whether or not the transport portion of the full circuit is providing a
clean signal.
Note: DTF Path-level PRBS tests cannot co-exist with SONET/SDH client CTP PRBS tests, GbE
client termination point tests (towards trib and line sides).
Rules for Performing PRBS Tests

The following rules apply to generating and monitoring PRBS test signals on the OTUk line port of the
SIM-T-1-10G, SIM-T-1-10GP, SIM-T-1-10GM and SIM-A-8-1GE:
■ The PRBS generation and monitoring on OTUk Client CTP cannot be enabled unless the OTUk
CTPs on that facility are in maintenance.
■ The Administrative state on any 10G OTU CTP can be set to Unlocked only if PRBS generation
and monitoring are disabled on all the OTU CTPs on this facility.
The following rules apply to generating and monitoring PRBS test signals on the SONET/SDH
Client CTP of SIM-A-8-2.5GMT:

■ The PRBS generation and monitoring on SONET/SDH Client CTP cannot be enabled unless the
SONET/SDH CTPs on that facility are in maintenance.
■ The Administrative state on any SONET/SDH Client CTP can be set to Unlocked only if PRBS
generation and monitoring are disabled on all the SONET/SDH CTPs on this facility.
The following rules apply to generating and monitoring DTF section-level and path-level PRBS test
signals on SIM-A-8-2.5GMT and SIM-T-1-10GT:
■ There rules are applicable for 2.5G DTP (in case of SIM-A-8-2.5GMT) and 10G DTP (in case of
SIM-T-1-10G)
■ The PRBS generation and monitoring cannot be enabled unless all the DTPCTPs or DChCTPs on
that facility are in maintenance
■ The Administrative state on any DTP can be set to Unlocked only if PRBS generation and
monitoring are disabled on all the DTPs on this facility
■ If the PRBS generation/monitoring (and Maintenance state) is set from the template and then the
DTPCTP object is created, PRBS will be enabled only if the above mentioned rules are satisfied.
Otherwise, the created DTP object will be put into Maintenance.
■ If the PRBS (generation/monitoring) is enabled on the first DTP and a second facility is created
later, it will be forced to Maintenance state irrespective of template configuration.
■ A 2.5G DTP in the SIM-A-8-2.5GMT cannot perform PRBS generation and monitoring at the same
time
The following rules apply to generating and monitoring PRBS test signals on the OTUk line port of the
10G SIM:
■ The PRBS generation and monitoring on OTUk Client CTP cannot be enabled unless the OTUk
client CTPs are in Administrative Maintenance state.
■ The Administrative state on the OTUk CTP can be set to Unlocked only if PRBS generation and
monitoring are disabled on all the OTUk CTPs on this facility.
To enable OTUk Client CTP PRBS test between Node1 and Node2
■ In the Equipment View of Node1, right-click the Line side SIM-T-1-10G/SIM-T-1-10GP/SIM-
T-1-10GM/SIM-A-8-1GE TOM and select Line Trib Termination Point.
■ In the Equipment Tree of Node1, right-click the Line side SIM-T-1-10G/SIM-T-1-10GP/SIM-
T-1-10GM/SIM-A-8-1GE TOM and select Line Trib Termination Point.
■ In the Facility Manager, right-click the row for the required OTUk Line and select Properties.
Step 2 Select the State tab. Change the Administrative State to Maintenance. Click Apply.

■ PRBS Generation Mode—Flag which enables the generation of PRBS data on the transmit
side. The value can be either Enabled or Disabled. Enable this option to generate PRBS data
on Node1.
■ PRBS Monitoring Mode—Flag which enables the monitoring of bit errors. The value can be
either Enabled or Disabled. Disable this option to disable monitoring of bit errors on Node1.
If PRBS generation is enabled, a warning message Enabling PRBS will affect the
traffic. Do you want to continue? is displayed.
Step 5 Click Continue to proceed with PRBS enabling.
■ In the Equipment View of Node2, right-click the Line side SIM-T-1-10G/SIM-T-1-10GP/SIM-
T-1-10GM//SIM-A-8-1GE TOM and select Line Trib Termination Point.
■ In the Equipment Tree of Node2, right-click the Line side SIM-T-1-10G/SIM-T-1-10GP/SIM-
T-1-10GM//SIM-A-8-1GE TOM and select Line Trib Termination Point.
■ In the Facility Manager, right-click the row for the required OTUk Client and select Properties.
■ PRBS Generation Mode—Flag which enables the generation of PRBS data on the transmit
side. The value can be either Enabled or Disabled. Disable this option to disable generation of
PRBS data on Node2.
■ PRBS Monitoring Mode—Flag which enables the monitoring of bit errors. The value can be
either Enabled or Disabled. Enable this option to monitor bit errors on Node2.

SONET Client CTP Facility PRBS Test

To enable SONET Client CTP Facility PRBS test between Node1 and Node2
■ In the Equipment View of Node1, right-click the tributary side SIM-A-8-2.5GMT TOM and select
Client trib termination point.
■ In the Equipment Tree of Node1, right-click the Line side SIM-A-8-2.5GMT TOM and select
■ In the Facility Manager, right-click the row for the required SONET Client and select Properties.
Step 3 Select the Diagnostics tab. In the Trib PRBS Mode panel, select the following values:
Step 4 In the Line PRBS Mode panel, select the following values:
■ Generation—Flag which enables the generation of PRBS data on the receive side. The value
■ In the Equipment View of Node2, right-click the Line side SIM-A-8-2.5GMT SIM TOM and select
■ In the Equipment Tree of Node2, right-click the Line side SIM-A-8-2.5GMT SIM TOM icon and
select Client trib termination point.

Step 11 Select the Diagnostics tab. In the Facility PRBS Mode panel, select the following values:
Node2.
SDH Client CTP PRBS Test

To enable SDH Client CTP Facility PRBS test between Node1 and Node2
■ In the Equipment View of Node1, right-click the tributary side SIM-A-8-2.5GMT TOM and select
■ In the Equipment Tree of Node1, right-click the Line side SIM-A-8-2.5GMT TOM and select
The SDH Client Trib Properties window is displayed.
Step 3 Select the Diagnostics tab. In the Trib PRBS Mode panel, select the following values:

Step 8 Click Close to exit the SDH Client Trib Properties window.
select Client trib termination point.
The SDH Client Trib Properties window is displayed.
Step 11 Select the Diagnostics tab. In the Facility PRBS Mode panel, select the following values:
Node2.
Step 16 Click Close to exit the SDH Client Trib Properties window.

Trib and Line DTP PRBS

To enable Trib and Line DTP PRBS test
■ In the Equipment View of Node1, right-click the tributary side SIM-A-8-2.5GMT or SIM-
T-1-10GT TOM and select Trib DTF Path.
■ In the Equipment Tree of Node1, right-click the Line side SIM-A-8-2.5GMT TOM and select Trib
DTF Path.
■ In the Facility Manager, right-click the row for the required Trib DTF Path Client and select
Properties.
Trib DTF Path.
select Trib DTF Path.
■ In the Facility Manager, right-click the row for the required Trib DTF Path Client and select
Properties.
Step 10 Select the Diagnostics tab. In the Line PRBS Mode panel, select the following values:



4-42 Test Signal Generation for Fibre Channel Clients in ATNs
Test Signal Generation for Fibre Channel Clients in ATNs

The SIM-A-8-2.5GMT support tributary-side and line-side test signal generation for the Fibre Channel
service types (1GF, 2GFC and 4GFC). Figure 4-10: Test Signal Generation on page 4-42 illustrates
Fibre Channel test signal generation. The test signal generation mode can be set to Compliant Random
Pattern (CRPAT) or it can be disabled.
Note: Test signal monitoring for Fibre Channel clients is supported only via an external test set.
■ Tributary-side test signal—A test pattern is generated by the Fibre Channel CTP toward the client
equipment. This test signal can be monitored by an external test set. See Rules for Performing
Fibre Channel Client Termination Point Tests on page 4-42 for information on generating Fibre
Channel CTP test signals.
■ Line-side test signal—A test pattern is generated by the Fibre Channel CTP toward the Infinera
network, where it is monitored by an external test set. See Rules for Performing Fibre Channel
Client Termination Point Tests on page 4-42 for information on generating Fibre Channel CTP test
signals.
Note: Since the Fibre Channel test signal affects normal data traffic flow, it must be used only when
Figure 4-10 Test Signal Generation
Rules for Performing Fibre Channel Client Termination Point Tests

■ Two 1G FC services multiplexed into a 2.5G DTP in the SIM-A-8-2.5GMT cannot undergo such a
signal test at the same time.
■ Both FC client termination point tests (towards trib and line sides) and DTP-level PRBS cannot be
applied at the same time. When DTP-level PRBS is activated, any FC client test signal generation
is disabled.

To enable Fibre Channel Client Termination Point Test at a Node

■ In the Equipment View, right-click the tributary side SIM-A-8-2.5GMT TOM and select Client Trib
Termination Point
■ In the Equipment Tree, right-click the TOM side SIM-A-8-2.5GMT TOM and select Client Trib
Termination Point.
The Fiber Channel Client Properties window is displayed.
Step 3 Select the Diagnostics tab. In the Trib Test Signal Mode and Line Test Signal Mode panels, enter and
■ Trib Test Signal Generation—Flag which enables the generation of test signal on the line side.
The value can be either Disabled or CRPAT.
■ Line Test Signal Generation—Flag which enables the generation of test signal on the tributary
side. The value can be either Disabled or CRPAT.
Note: Trib test signal and line test signal generation can be set only if the configured service
type is 1 GFC or 2 GFC. Signal monitoring is not supported for any service type.
Step 5 Click Close to exit the Fibre Channel Client Properties window.
perform.
To disable Fibre Channel Client Termination Point Test at a Node

■ In the Equipment View, right-click the right-click the tributary side SIM-A-8-2.5GMT TOM and
select Client Trib Termination Point.
■ In the Equipment Tree, right-click the SIM-A-8-2.5GMT TOM and select Client Trib Termination
Point.
The Fibre Channel Client Properties window is displayed.

4-44 Test Signal Generation for Fibre Channel Clients in ATNs
select the following values:
The value can be either Enabled or Disabled.
■ Line Test Signal Monitoring—Flag which enables the generation of test signal on the line side.
side. The value can be either Enabled or Disabled.
■ Trib Test Signal Monitoring—Flag which enables the generation of test signal on the tributary
Step 5 Click Close to exit the Fibre Channel Client Properties window.
perform.

GbE Client Termination Point Tests in ATNs

A GbE Client Termination Point (CTP) test signal is used to diagnose and isolate the troubled spots for
the GbE client on the SIM-A-8-2.5GMT, without requiring a valid data signal or customer traffic. The test
signal is a long continuous random test pattern that complies with the IEEE 802.3-2002 Annex 36A.4
specification. This type of test signal is available only for the 1GbE ports on the SIM-A-8-2.5GMT.
Note: Since the GbE test signal affects normal data traffic flow, it must be used only when the
associated facility is in administrative maintenance state.
There are two types of GbE CTP tests:

■ Tributary-Side Client Test—A test signal at the 1GbE level is generated by the GbE CTP toward
the client equipment. This test signal can be monitored by an external test set. See Rules for
Performing GbE Client Termination Point Tests on page 4-45.
■ Line-Side Client Test—A test signal at the 1GbE level is generated by the GbE CTP toward the
Infinera network where it is monitored by one of the following:
□ An external test set. See Rules for Performing GbE Client Termination Point Tests on page
4-45 for information on generating and monitoring GbE CTP test signals.
□ The same GbE CTP that is generating the test signal, if the GbE CTP has been enabled for
line-side monitoring and if a loopback has been created at the far end. See Rules for
Performing GbE Client Termination Point Tests on page 4-45 for information on generating
and monitoring GbE CTP test signals.
□ A corresponding GbE CTP on a far-end SIM-A-8-2.5GMT, if the corresponding GbE CTP
has been enabled for line-side test signal monitoring. SeeRules for Performing GbE Client
Termination Point Tests on page 4-45 for information on generating and monitoring GbE
CTP test signals.
Note: GbE client termination point tests (client and line sides) cannot co-exist with DTF
path-level PRBS tests.
Rules for Performing GbE Client Termination Point Tests

The following rules apply to generating and monitoring the test signals on the SIM-A-8-2.5GMT:
■ Two 1GbE services multiplexed into a 2.5G DTP in the SIM-A-8-2.5GMT cannot undergo such a
signal test at the same time.
■ Both client-side 1GbE Test Signal and DTP-level PRBS cannot be applied at the same time. When
DTP-level PRBS is activated, any 1GbE client test signal generation or monitoring is disabled.

4-46 GbE Client Termination Point Tests in ATNs
To enable GbE Client Termination Point Test at a Node

■ In the Equipment View, right-click the tributary side SIM-A-8-2.5GMT TOM and select Client Trib
Termination Point
■ In the Equipment Tree, right-click the TOM side SIM-A-8-2.5GMT TOM and select Client Trib
Termination Point.
■ Trib Test Signal Monitoring—Flag which enables the monitoring of test signal on the tributary
side. The value can be Enabled or Disabled.

Repeat the above steps for each of the ports in the required nodes, based on the test you want to
perform.
To disable GbE Client Termination Point Test at a Node

■ In the Equipment View, right-click the right-click the tributary side SIM-A-8-2.5GMT TOM and
select Client Trib Termination Point.
■ In the Equipment Tree, right-click the SIM-A-8-2.5GMT TOM and select Client Trib Termination
Point.
select the following values:
■ Trib Test Signal Monitoring—Flag which enables the monitoring of test signal on the tributary
side. The value can be Enabled or Disabled.

perform.

4-48 Lamp Testing in ATNs
Lamp Testing in ATNs

Lamp test is used to test the functioning of LEDs on all circuit packs, for a duration of 30 seconds. The
lamp test functionality is supported for each chassis individually.
To perform lamp test

■ Do one of the following to initiate a lamp test on a chassis:
□ In the Equipment Tree, right-click the chassis icon and select Initiate Lamp Test.
□ In the Equipment View, right-click just below the title bar (next to the ACO-OFF/ACO-ON
button) and select Initiate Lamp Test.
A success message is displayed. All the LEDs on all the circuit packs light up. Single-color
LEDs blink on and off, every 0.5 second. Multi-color LEDs toggle between all the colors, in a
round robin fashion, every 0.5 second. For example, if red, yellow, green are the three colors
of a multi-color LED, the color change sequence is red - yellow - green -red.

Point Loss Adjustment Utility

DNA Tools menu includes a Download Point Loss Adjustment Utility option that helps in downloading the
ORM turn-up script which can be executed via Infinera GNM on a single ORM module, or on all ORMs
along a digital span. This script can be downloaded to any desired location. Further, script can be
downloaded and executed on clients launched on both Microsoft Windows and Red Hat Linux operating
systems.
To download point loss adjustment script from a Microsoft Windows client

Step 1 From the DNA Main Menu, select Tools > Download Point Loss Adjustment Utility.
A prompt specifying the default location where the script will be downloaded to is displayed. Further,
an option to change the location to save the script is also provided.
■ If you intend to download the script to the default location, click Continue.
A prompt indicating the successful download of the script is displayed. Click Ok to exit the
prompt.
■ If you intend to change the location of the script or the name of the script, go to Step 3.
Step 3 Do the following:
Step 3a Click Change Location.
Step 3b In the Save... window, navigate to the desired location and edit the file name (optional) as desired.
Step 3c Click Save.
A prompt indicating the successful download of the script is displayed. Click Ok to exit the prompt.
To download point loss adjustment script from a Linux client

Step 1 From the DNA Main Menu, select Tools > Download Point Loss Adjustment Utility.
A prompt specifying the default location where the script will be downloaded along with the option to
choose either the 64 Bit or 32 Bit script is displayed. Further, an option to change the location to save
the script is also provided.
Step 2 Choose the 64 Bit or 32 Bit point loss adjustment script to be downloaded by selecting the appropriate
radio button.
Step 3 Select the appropriate option:
■ If you intend to download the script to the default location, click Continue.
A prompt indicating the successful download of the script is displayed. Click Ok to exit the
prompt.
■ If you intend to change the location of the script, go to Step 4.
Step 4 Do the following:
Step 4a Click Change Location.

4-50 Point Loss Adjustment Utility
Step 4b In the Save... window, navigate to the desired location and ensure that the file name is
ORMTurnup_Linux.
Note: The script is always downloaded as ORMTurnup_Linux irrespective of a user-triggered

change in the name.
Step 4c Click Save.

A prompt indicating the successful download of the script is displayed. Click Ok to exit the prompt.

CHAPTER 5
Cloud Xpress and XT Diagnostics
This chapter describes the troubleshooting tools that can be used to troubleshoot the Cloud Xpress and
XT network element and the Infinera Intelligent Transport Network. This chapter is divided into the
following sections:
■ Loopbacks in CXs on page 5-2
■ Trace Messaging in CXs on page 5-7
■ Loopbacks in XTs on page 5-8
■ Trace Messaging in XTs on page 5-16
■ Lamp Testing in CX and XT on page 5-17

5-2 Loopbacks in CXs
Loopbacks in CXs
The Cloud Xpress supports loopbacks to test new connections before running live traffic or to logically
locate the source of a failure on existing connections. Loopbacks provide a mechanism where the signal
under test is looped back at some location on the network element in order to test the integrity and validity
of the signal being looped back. Since loopbacks affect normal data traffic flow, they must be invoked
only when the associated facility is in administrative maintenance state.
IQ-CX NOS provides access to the loopback capabilities in the Cloud Xpress. The loopbacks can be
enabled or disabled remotely through the management interface.
The Cloud Xpress supports the following loopbacks:
■ Client Loopback in CXs on page 5-2
■ Line Loopback in CXs on page 5-4
■ OCG Loopback in CXs on page 5-5
Client Loopback in CXs

A loopback is performed on the client so that packets received on the client Ethernet interface are sent
back towards the connected customer equipment.
Figure 5-1 Client Loopbacks on CX-10E and CX-40E

Cloud Xpress and XT Diagnostics 5-3
Figure 5-2 Client Loopbacks on CX-100E
Figure 5-3 Loopbacks in CX-1200F
To set a Client loopback for a termination point in CX
Step 1 In the Facility Manager, right-click the row for the required trib side GbE Client and click Properties.
Step 4 [Optional] To save your changes, click Apply. Select Diagnostics tab.
A warning message Turning On loopback will affect the traffic. Do you want to continue? is displayed.


Line Loopback in CXs

A loopback is applied on the client so that packets received from the line side are sent back towards the
line.
Figure 5-4 Line Loopback on CX-10E and CX-40E
Figure 5-5 Line Loopback on CX-100E
To set a Line loopback for a termination point in CX
Step 1 In the Facility Manager, right-click the row for the required line side GbE Client and click Properties.

Step 4 [Optional] To save your changes, click Apply. Select Diagnostics tab.
A warning message Turning On loopback will affect the traffic. Do you want to continue? is displayed.
OCG Loopback in CXs

A loopback is applied at the OCG level so that all packets received on all client Ethernet interfaces are
sent back towards the connected customer equipment.
Figure 5-6 OCG Loopback on CX-10E and CX-40E
Figure 5-7 OCG Loopback on CX-100E
To set a OCG loopback for a termination point in CX


■ In the Equipment View, right-click the CX OCG Port and select Properties.
■ In the Facility Manager, right-click the row for the required CX OCG Port and click Properties.
■ The CX OCG Properties window is displayed.
Step 8 Click Close to exit the CX OCG Properties window.
SCG Loopback in CXs

A loopback is applied at the SCG level so that all packets received on all client Ethernet interfaces are
sent back towards the connected customer equipment. Refer to Figure 5-3: Loopbacks in CX-1200F on
page 5-3
To set a SCG loopback for a termination point in CX

■ In the Equipment View, right-click the CX SCG Port and select Properties.
■ In the Facility Manager, right-click the row for the required CX SCG Port and click Properties.
■ The CX SCG Properties window is displayed.
Step 8 Click Close to exit the CX SCG Properties window.

Trace Messaging in CXs

Trace messaging is a non-intrusive diagnostic tool that provides the Trail Trace Identifier functionality to
allow detection and validation of peer CX devices connected over the fiber. The CX supports OCG layer
TTI with the following extensions: Transmit TTI, Expected TTI and Received TTI. If a mismatch is
detected on the transmitted/expected and received TTI, an alarm is raised to indicate the mismatch.
To enable reporting of Trace messaging CX

■ In the Equipment View, right-click the CX OCG Port and select Properties.
■ In the Facility Manager, right-click the row for the required CX OCG Port and click Properties.
■ The CX OCG Properties window is displayed.
Step 8 Click Close to exit the CX OCG Properties window.

5-8 Loopbacks in XTs
Loopbacks in XTs
The XT supports loopbacks to test new connections before running live traffic or to logically locate the
source of a failure on existing connections. Loopbacks provide a mechanism where the signal under test
is looped back at some location on the network element in order to test the integrity and validity of the
signal being looped back. Since loopbacks affect normal data traffic flow, they must be invoked only when
IQ-XT NOS and IQNOS provide access to the loopback capabilities in the XT. The loopbacks can be
enabled or disabled remotely through the management interface.
Note: Unless specifically noted otherwise, all references to the XT will refer to the XT(S)-3600,
XT(S)-3300, XT-500S-100, and/or XT-500F-100 interchangeably.
The XT supports the following loopbacks:

■ Client Loopback in XTs on page 5-8
■ Line Loopback in XTs on page 5-10
■ OCG Loopback in XTs on page 5-11
■ SCG Loopback in XTs on page 5-12
■ Trib ODUk Loopback in XT(S)-3600 on page 5-14
Client Loopback in XTs

A loopback is performed on the client so that packets received on the client Ethernet interface are sent
back towards the connected customer equipment.
Figure 5-8 Client Loopback in XT-500S-100

Figure 5-9 Client loopback in XT-3300
Figure 5-10 Client loopback in XT-3600
To set a Client loopback for a termination point in XT
Step 1 In the Facility Manager, right-click the row for the required trib side Client and click Properties.
■ The Client Properties window is displayed.

Step 8 Click Close to exit the Client Properties window.
Line Loopback in XTs

A loopback is applied on the client so that packets received from the line side are sent back towards the
line.
Figure 5-11 Line Loopbacks in XT-500S-100
Figure 5-12 Line Loopback in XT-3300

Figure 5-13 Line Loopback in XT-3600
To set a Line Loopback for a termination point
applied.

■ In the Chassis View, right-click the the required equipment, icon and select the line (for
example; LO ODUk CTP).
selectthe required line (for example; LO ODUk CTP).
The line side (for example; LO ODUk CTP) window is displayed.
OCG Loopback in XTs

A loopback is applied at the OCG level so that all packets received on all client Ethernet interfaces are
sent back towards the connected customer equipment.

Figure 5-14 OCG Loopback on XT-500S and SCG Loopback on XT-500F
To set a OCG loopback for a termination point in XT

■ In the Equipment View, right-click the XT OCG Port and select Properties.
■ In the Facility Manager, right-click the row for the required XT OCG Port and click Properties.
■ The XT OCG Properties window is displayed.
Step 10 Click Close to exit the XT OCG Properties window.
SCG Loopback in XTs

A loopback is applied at the SCG level so that all packets received on all client interfaces are sent back
towards the connected customer equipment.

Figure 5-15 SCG loopback in XT-3300
Figure 5-16 SCG loopback in XT-3600
To set a SCG loopback for a termination point in XT

■ In the Equipment View, right-click the XT SCG Port and select Properties.
■ In the Facility Manager, right-click the row for the required XT SCG Port and click Properties.
■ The XT SCG Properties window is displayed.


Step 10 Click Close to exit the XT SCG Properties window.
Trib ODUk Loopback in XT(S)-3600

A loopback is performed on the Trib ODUk so that packets received on the client interface are sent back
towards the connected customer equipment.
Figure 5-17 Trib ODUk loopback in XT-3600
To set a Trib ODUk CTP loopback for a termination point in XT(S)-3600

Step 1 In the Facility Manager, right-click the row for the required trib side ODUk Client CTP and click
Properties.
■ The ODUk Client CTP Properties window is displayed.

Step 8 Click Close to exit the ODUk Client CTPProperties window.

5-16 Trace Messaging in XTs
Trace Messaging in XTs

Trace messaging is a non-intrusive diagnostic tool that provides the Trail Trace Identifier functionality to
allow detection and validation of peer XT devices connected over the fiber. The XT supports OCG layer
TTI with the following extensions: Transmit TTI, Expected TTI and Received TTI. If a mismatch is
detected on the transmitted/expected and received TTI, an alarm is raised to indicate the mismatch.
To enable reporting of Trace messaging XT

■ In the Equipment View, right-click the XT OCG Port and select Properties.
■ In the Facility Manager, right-click the row for the required XT OCG Port and click Properties.
■ The XT OCG Properties window is displayed.
Step 5 Enter the values for Expected TTI, Transmitted TTI, and Target Tx OCG Power.
Step 8 Click Close to exit the XT OCG Properties window.

Lamp Testing in CX and XT

The Cloud Xpress and XT maintains a front panel alarm indicator providing the alarm status at chassis
level to provide the specific hardware and software status. The CX/XTs front panel also provides the
LEDs to indicate the hardware and software status.
Note: It is a mandatory diagnostic test that is run as part of the initial turn-up and test procedure for
CX/XT. It can also be performed as a periodic maintenance task.
The front panel contains a lamp test button for testing the LEDs. When the lamp test button is pressed, all
LEDs on the I/O panel and the circuit packs on the chassis are lit (power LEDs illuminate Green and fault
LEDs illuminate Red) and bi-color LEDs will toggle between two colors (Green and Yellow) until the lamp
test button is released. Once the lamp test button is released, all LEDs will return to the previous
condition.
Note: The lamp test requires XMM presence and the chassis to be powered.
Note: Unless specifically noted otherwise, all references to the XT will refer to the XT(S)-3600,
XT(S)-3300, XT-500S-100, and/or XT-500F-100 interchangeably.
To invoke lamp testing in CX/XTs
Step 1 In the Network Topology View, right-click on the CX/XT node icon and select Chassis View.
Step 2 In the Equipment Tree of the Chassis View, right-click the chassis and select Lamp Test.
Step 3 The Lamp Test dialog is diplayed.
Step 4 Select Enable from Action drop-down.
Step 5 Enter time in the Time field in seconds.
Note: The time value should range from 60 secs to 3600secs.
Step 6 Click Apply to view the Success Message pop-up.

Step 7 Click Ok.
Step 8 Click Close to close the Lamp Test dialog.

5-18 Lamp Testing in CX and XT

CHAPTER 6
Diagnostics Applications
This chapter describes the troubleshooting tools that can be used to troubleshoot the network element
and the Infinera Intelligent Transport Network. This chapter is divided into the following sections:
ATN Digital Link Viewer on page 6-2
Digital Link Viewer on page 6-13
Cloud Xpress Link Viewer on page 6-122
XT Digital Link Viewer on page 6-135
Field Data Recorder Logs Collection on page 6-143
Circuit Diagnostic Manager on page 6-146
SOAM Manager on page 6-234

6-2 ATN Digital Link Viewer
ATN Digital Link Viewer

The ATN Digital Link Viewer displays the ATN digital link details graphically in the Optical Layer, the OFM
details in the OFM Table and the channel PM parameters in the Channel Layer.
The ATN Digital Link Viewer provides the capability to enable or disable ADAPT on Links and selected
route.
This section provides the following details:
Representation in ATN Digital Link Viewer on page 6-2
Launching the ATN Digital Link Viewer on page 6-10
Enabling and Disabling ADAPT from ATN Digital Link Viewer on page 6-10
Representation in ATN Digital Link Viewer

This section provides information on the details represented in the ATN Digital Link Viewer. The ATN
Digital Link Viewer consists of the following regions:
■ Display Options on page 6-3
■ Optical Layer on page 6-4
■ OFM Table on page 6-7
■ Channel Layer on page 6-7
■ Actions Panel on page 6-9

Diagnostics Applications 6-3
Figure 6-1 ATN Digital Link Viewer
Display Options
■ Channel Group selection drop-down menu
Drop-down menu to select the channel from the channel group. The channel groups are listed
based on the end nodes of the channel. The channels that have the fiber patch configured on at
least one side, between the OFM Trib termination point and the SIM Trib termination point will be
shown in the ATN Digital Link Viewer.
■ Reverse Link Direction
Check-box to reverse the display of the link direction or flip the current view.
■ Direction Filter
Drop-down menu to filter the data displayed in the ATN Digital Link Viewer based on the direction.
The values include, West-->East, West<--East and Both. The default value is Both.

Optical Layer
The Optical Layer in the ATN Digital Link Viewer provides a graphical representation of the selected
Channel based on the Display Options configured. All nodes connected in the selected network will be
represented graphically in the ATN Digital Link Viewer. However the link and the associated source and
destination nodes are highlighted to identify the launch context. It displays ATN span characteristics. It
displays the AAM and OFM-1-OSC and CWDM OFMs power and gain details at each node in the span.
The west and east blocks of OFMs and AAMs for each node is displayed. The data represented in this
layer depends on the OTS trace which is dependant on the configured fiber patches. If there is an alarm
on any of the equipment, the equipment is highlighted with the highest severity alarm color code.
The Node Name for all nodes within the span is displayed. The Table 5-1 provides details of the
parameters displayed for each equipment type in the Optical layer.

Table 6-1 Parameters displayed in the ATN Digital Link Viewer

Equipment Attributes
AAM ■ Chassis and Slot
■ Equipment type
■ Admin State
■ Operational State
■ Maximum Number of Channels
■ Add Channel Target Power
■ Gain Low
■ Gain High
■ Target Gain
■ Transmit and Receive Power
■ Line In and Line Out Pads
■ In line DCM Types
OFM ■ Chassis and Slot
■ Equipment type
■ Admin State
■ Transmit and Receive Power
■ Line In and Line Out Pads
■ In line DCM Types
OFM-40-D-M-1859 ■ Chassis and Slot
■ Equipment type
■ Admin State
ATN Digital Link Viewer also provides right-click options to support various operations on the equipment
displayed in the Optical Layer. The Table 5-2 on page 5-5 provides details of all the right-click options
supported from the Optical Layer.

Table 6-2 Right-click options from the Optical Layer of the ATN Digital Link Viewer
Equipment RIght-click options
AAM ■ Properties
■ Show Alarms
■ Show Facilities
■ Fiber Connectivity Manager
■ Add Fiber Connectivity
■ Admin State
■ Alarm Reporting
■ Delete
■ Reset
■ Span
■ Band
■ Calibration Data
■ OFM Calibration Data - This option is displayed if the AAM is
connected to the OFM.
■ Enable ADAPT
■ Disable ADAPT
OFM ■ Properties
■ Show Alarms
■ Show Facilities
■ Fiber Connectivity Manager
■ Add Fiber Connectivity
■ Admin State
■ Alarm Reporting
■ Delete
■ Span
■ OFM Calibration Data - This option is displayed if the OFM is
connected to another OFM.
■ Enable ADAPT
■ Disable ADAPT
Link ■ View Link
■ Enable ADAPT on Link

Table 6-2 Right-click options from the Optical Layer of the ATN Digital Link Viewer (continued)
Equipment RIght-click options
■ Disable ADAPT on Link

■ Enable ADAPT on Route
■ Disable ADAPT on Route
OFM Table
The OFM Table lists all the OFMs that are part of the digital link in the order of the trace. The OFM Table
provides the following details:
■ Direction
■ Node Name
■ Equipment AID
■ Equipment Type
■ Band OPT
■ Band OPR
■ VOA Attenuation
■ Band Power Offset
■ OCG OPR
■ Add Channel OPR
□ Pre-VOA and Post VOA for each of the channels
■ OPSW Trib OPR and OPSW Line OPR (In case of a Band protection scenario)
Note: The values for the attributes in the OFM table are populated depending on the channels
being added or dropped at the OFM.
Channel Layer
The Channel Layer lists all the channels traced from the selected launch point. The number of channels
listed vary based on the launch point and is dependent on the configured fiber patches.
For example, if nodes A, B and C are connected and the channel details are as mentioned below:
■ A <- -> B <- -> C
■ Channel1 is between A and C.
■ Channel2 and Channel3 are between B and C.

Note: ATN DLV shows the channel details for following setups:
OFM Trib Port ->PNTP
OFM Trib Port ->OPSW Line ->PNTP
If the ATN Digital Link Viewer is launched from:

■ Link between A and B, then the number of channels will be one and the channel group will be one.
■ Link between B and C, then the number of channels will be three and the channels will be grouped
into two as mentioned below:
□ Channel Group1: A <- -> C = Channel1
□ Channel Group2: B <- -> C = Channel2 and Channel3
The Channel Layer also provides details of the PM parameters associated with each channel
from the selected launch point. In case of a clear channel, the channel PM data is not
displayed.
The Channel Layer displays the following parameters:
■ Channel #/Wavelength—Displays the channel number or the wavelength associated with the
channel.
■ SIM Trib Line/Client AID—Displays the AID of the trib or line-side SIM Trib.
■ SIM trib service state and OPT and OPR attributes.
■ OFM Trib Ports
■ OPSW Trib AID, OPSW Trib OPR in case of channel protection.
■ OPSW Line AID, OPSW Line OPR in case of channel protection.
■ OFM Trib AID—Displays the AID of the OFM trib.
■ VOA Offset
■ Conf VOA
■ Add Channel OPR
■ Pre-FEC BER(10 Sec)—The Pre-FEC BER averaged over a period of 10 secs. If there are no
errors or just one error in the 10 sec bin, a BER of 9e-12 is displayed.
■ Post-FEC BER(10 Sec)—The Post-FEC BER averaged over a period of 10 secs. If there are no
For a description of all the performance monitoring attributes and their default values, see DNA
Performance Management Guide.
The right-click options available on these channels include:

□ Property (West Channel and East Channel)—Select this option to launch the respective
properties window. This option is disabled if it is not applicable in setups such as OFM Trib
Port -> PNTP and OFM Trib Port ->OPSW Line -> PNTP.
□ Show Alarms—Select this option to launch the Alarm Manager listing the alarms associated
with the channel. This option is disabled if neither side is connected to a SIM in a setup like
OFM Trib Port -> PNTP and OFM Trib Port ->OPSW Line -> PNTP.
□ Export All Channels—Select this option to export all the channels information into a .tsv file.
□ Circuit Manager (West Channel and East Channel)—Select this option to launch the Circuit
Manager listing the circuits associated with the channel. This option is disabled if both sides
PNTP is configured for OFM Trib Port in a setup like OFM Trib Port -> PNTP and OFM Trib
Port ->OPSW Line -> PNTP.
Figure 6-2 OFM Trib Port - OFM PNTP configured at both ends
OFM Trib Port ->OPSW Line -> PNTP Sample Setup
Actions Panel
The action panel in the ATN Digital Link Viewer consists of the following buttons:
■ Collect Logs—Click to launch the wizard to collect FDR logs for the digital link. For more
information related to FDR logs, refer to DNA Administrator Guide.
■ Refresh—Click to refresh the Digital Link Viewer.
■ Export—Click to export the ATN Digital Link Viewer session data into a .zip file. This .zip file
contains all the data displayed in the Channel layer (.tsv format) and a .png file of the Optical layer.
■ Print—Click to print the graphical representation of the digital link as seen in the Optical layer of the
ATN Digital Link Viewer.

■ Close—Click to close the instance of the ATN Digital Link Viewer.

■ Help—Click to launch context sensitive help related to the ATN Digital Link Viewer.
Launching the ATN Digital Link Viewer

The ATN Digital Link Viewer can be launched from various launch points from the DNA. The following
procedure provides details on various launch points.
To launch the ATN Digital Link Viewer
Note: Only one instance of the ATN Digital Link Viewer can be launched per client session.

■ In the Physical View, right-click the link and select Digital Link Viewer.
■ In the Provisioning View, right-click the ATN provisioning link and select Digital Link Viewer.
■ Dragging and dropping links (from the Topology View) on to an active session of the Link
Viewer, refreshes the session with the selected link data. To drag and drop links on to an active
session, ensure that the ‘Assign nodes to admin domain or Drag node or link to set context icon’
is selected.
The ATN Digital Link Viewer is displayed.
Note: The order in which the nodes in the ATN Digital Link Viewer are displayed is derived
from the order of nodes in the OTS trace.
Step 2 To refresh the complete view, click Refresh.

Step 3 To print the complete view, click Print.
Step 4 Click Close to exit the ATN Digital Link Viewer window.
Enabling and Disabling ADAPT from ATN Digital Link Viewer

This section provides details on enabling and disabling ADAPT from the ATN Digital Link Viewer. The
ATN Digital Link Viewer provides options to enable or disable ADAPT from the AAMs and/or OFM-1-OSC
equipment. Additionally, ADAPT on selected links and route can be enabled and disabled as well.
■ To enable or disable ADAPT from equipment on page 6-11
■ To enable ADAPT on a Link on page 6-11
■ To disable ADAPT on a link on page 6-11
■ To enable ADAPT on a route on page 6-12
■ To disable ADAPT on a route on page 6-12

To enable or disable ADAPT from equipment

Step 1 In the ATN Digital Link Viewer, right-click the desired equipment (AAM or OFM-1-OSC) on which you
want to enable or disable ADAPT.
Step 2 Do any of the following as desired:
■ Select Enable ADAPT to enable ADAPT. A confirmation message is displayed. Further, click
Start ADAPT to enable ADAPT.
■ Select Disable ADAPT to disable ADAPT.
To enable ADAPT on a Link

Step 1 In the ATN Digital Link Viewer, right-click the desired link and select Enable ADAPT on Link.
A confirmation message is displayed.
Figure 6-3 Enable ADAPT: Confirmation Message
Step 2 Click Start ADAPT to continue.

The Enable ADAPT operation status window is displayed.
Figure 6-4 Enable ADAPT Operation Status
Step 3 Click Ok to exit the status window.
To disable ADAPT on a link

Step 1 In the ATN Digital Link Viewer, right-click the desired link and select Disable ADAPT on Link.
The Disable ADAPT operation status window is displayed.
Figure 6-5 Disable ADAPT Operation Status

To enable ADAPT on a route

Step 1 In the ATN Digital Link Viewer, right-click the desired link and select Enable ADAPT on Route.
A confirmation message is displayed.
Figure 6-6 Enable ADAPT: Confirmation Message
Step 2 Click Start ADAPT to continue.

The Enable ADAPT operation status window is displayed.
Figure 6-7 Enable ADAPT Operation Status
To disable ADAPT on a route

Step 1 In the ATN Digital Link Viewer, right-click the desired link and select Disable ADAPT on Route.
The Disable ADAPT operation status window is displayed.
Figure 6-8 Disable ADAPT Operation Status

Digital Link Viewer

A digital link is a composite representation of a link between two directly connected DTNs, DTN-Xs,
FlexROADMs, or between DTNs, DTN-Xs, FlexROADMs and Optical Line Amplifiers.
The digital link viewer displays the DTNs, DTN-Xs, FlexROADMs and Optical Line Amplifiers, circuit
packs (FRMs, FSMs, IAMs, IRMs, BMMs, OAMs, ORMs, Raman modules, line modules, GAMs and
CMMs) and termination points which constitute the digital link, in the OTS, OCG and Channel layers as
shown in Figure 6-9: Digital Link Viewer on page 6-14. Further, the Digital Link Viewer can graphically
represent the OSC status and termination details within the span.
The tool displays details such as fiber type, span length, span loss, net span loss (if applicable), expected
span loss, gain measurements, optical power levels, channel-level BER data and other parameters that
help in troubleshooting. See Figure 6-9: Digital Link Viewer on page 6-14 for details of parameters
displayed for each equipment in the Optical layer of the Digital Link Viewer.
Starting Release 18.0.1, the Digital Link Viewer for XTM services can be launched from the Map View/
Topoloical View.
Use the Digital Link Viewer to:
■ turn-up digital/optical spans.
■ isolate faults in digital and optical link/channel(s) within a selected digital span at Optical and Digital
layers.
■ monitor the performance of a digital/optical link, with the help of the displayed attributes.
■ monitor the status of nodes that constitute the digital link.
■ monitor the gain parameters (Current and Expected) at each equipment (as applicable) across the
digital link.
■ view the Line In PAD and Line Out PAD as applicable.
■ view the fiber type and distance as applicable.
■ identify fiber cuts.
■ view the C-Band, termination points, OSC and OTS details as applicable.
■ perform various operations on the circuits packs associated with the link using the right-click
options provided.
Representation in a Digital Link Viewer on page 6-13
Launching the Digital Link Viewer on page 6-60
Sample Digital Link Viewer on page 6-61
Representation in a Digital Link Viewer

This section provides information on the details represented in a Digital Link Viewer.

6-14 Digital Link Viewer
■ Summary View on page 6-14

■ Graphical View on page 6-16
■ Super Channel Layer/Channel Number/OCG Layer on page 6-47
■ Super Channel Carrier/Channel Layer on page 6-54
■ Digital Link Viewer Action Panel on page 6-59
Figure 6-9 Digital Link Viewer
Summary View
The Summary View in the Digital Link Viewer provides a graphical representation of all the nodes in the
entire network. Each node displays the following information:
■ Node Name
■ Node Type Icon
■ Span Loss, Expected Span Loss and Net Span Loss in each direction
■ OTS Power levels in entry and exit points

■ Highest severity alarm in line system equipment and facilities (if applicable)
■ Fiber Cut (if applicable)
The Summary Graphical view also indicates the following:
□ OADM for FRM and BMM
□ EDFA for IAM and OAM
□ ORM Pump for ORM and IRM
□ RAMAN Pumps for RAM and REM
Note: Select any node in Summary View to auto scroll to the same node in Optical Layer.
The Summary View options change based on the launch point of DLV.
If the selected segment to launch DLV has a FlexROADM node or DTN-X node with MTC-9/
MTC-6 as expansion chassis or a Optical Line Amplifier node with MTC-9/MTC-6 chassis,
the summary view is displayed as below.
Figure 6-10 DLV - Summary View for FlexROADM node
■ Select Super Channel Group drop-down menu

Based on the launch point and the super channels traced, this menu provides a list of super
channels grouped by source and destination nodes. It is possible that one or more of the Super
channels traced, may not terminate on the next node, and may be expressed further along to other
nodes, upstream or downstream. The required super channels can be selected from the drop-down
menu and the Optical layer is updated based on this selection.
Select Super Channel Group drop-down menu also includes the ManualMode_1 Super Channels.
The tooltip provides the full string of ManualMode_1 super channel.
Select the check-box to reverse the direction of the link displayed in the Digital Link Viewer. The
OTS, Super channels and Channel layers are updated to reverse the direction based on the
selection. By default, this option is un-checked.
■ Auto Refresh

Select the auto-reverse intervals to auto-refresh the Digital Link Viewer. The intervals supported to
auto-refresh the Digital Link Viewer are 5minutes, 10minutes and 15mins. By default, this option is
NA.
If the selected segment to launch DLV has a DTN node with DTC/MTC as main chassis or DTN-X node
with XTC as main chassis and DTC/XTC as expansion chassis or a Optical Amplifier node with OTC
chassis or XTM chassis, the summary view is displayed as below.
Figure 6-11 DLV - Summary View for DTN/DTN-X/OA node
■ Select OCG Group/Select Channel Group(for XTM only) drop-down menu

Based on the launch point and the OCGs traced, this menu provides a list of OCGs grouped by
source and destination nodes. It is possible that one or more of the OCGs traced, may not
terminate on the next node, and may be expressed further along to other nodes, upstream or
downstream. The required OCGs can be selected from the drop-down menu and the Optical layer
is updated based on this selection.
Select the check-box to reverse the direction of the link displayed in the Digital Link Viewer. The
OTS, OCG, and Channel layers are updated to reverse the direction based on the selection. By
default, this option is un-checked.
■ Auto-Refresh
Select the auto-reverse intervals to auto-refresh the Digital Link Viewer. The intervals supported to
auto-refresh the Digital Link Viewer are 5, 10 and 15 minutes. By default, this option is NA.
Graphical View
The Graphical View in the Digital Link Viewer provides a graphical representation of the selected OCG or
Super Channel Group (Select OCG/Super Channel Group drop-down menu) based on the Display
options configured. The Digital Link Viewer displays all parameters associated with the nodes and
equipment within the digital link. Users can choose to either hide or display the OCG/Super Channel
termination points in this layer. The alarms are also indicated with its relevant colors on a card or port as
applicable. The Node Name and Node Type details for all nodes within the digital link is displayed.
The following states of the nodes are indicated by a water mark across the node:
■ Unreachable
■ Discovering

■ Errored
■ Out of sync
If the selected optical link to launch DLV has a FlexROADM node or DTN-X node with MTC-9/
MTC-6 as expansion chassis or a Optical Line Amplifier node with MTC-9/MTC-6 chassis, the
segment view is displayed as below:
Figure 6-12 DLV - Graphical View for FlexROADM Node
■ View drop-down menu

Select the appropriate option from the View drop-down menu to display appropriate details in the
Graphical View of the Digital Link Viewer. The various options include:
□ Band and Super Channel: Displays the existing Physical View with Band PM values along
with the line module and IRM configurations in the terminal nodes of the digital span. This
option also displays the super channel termination point details.
□ Band: Displays the existing Physical View with Band PM values. This is the default option.
□ OSC: Displays the OSC details with OSC PM values. This option also displays the OSC IP
Address, OSC Subnet Mask for IRMs, IAMs and OSC termination points in the terminal
cards with cross-cover in Optical Line Amplifiers along with Laser Bias Current value.
□ Band + OSC (OTS): Displays the existing Physical View with OTS PM values instead of
Band PM values in the cards.
□ Super Channel Switching: Displays the super channel termination point details.
■ Super Channel Number

Super Channel Number drop-down is enabled only if the view is set to Band and Super Channel or
Super Channel Switching. Select any SCH number from the Super Channel Number drop down
menu. The default selection is always ALL.
The Super Channel Number drop-down lists all Infinera ManualMode_1 and native super channels.
Note: The Super Channel Number drop-down is a multi selection filter, where selecting All
selects all super channels in the filter, but de-selecting All de-selects only All option and not
any other selected super channels in the filter.
■ Show FP
This check-box is enabled only when FRM 9D FRU is connected in the span and can be viewed
with only Band and Super Channel View and Super Channel Switching View.
Note: Show FP checkbox toggles between the view which shows FSPs and which does not
show FSPs.
■ Show Peripheral Nodes and Equipment

This check-box is enabled only to trace and display the Alien Nodes in Digital Link Viewer, so that it
is easier to diagnose the optical layer.
Note: Digital Viewer by default will be launched without any Peripheral Nodes & Equipment.
■ Zoom Slider
Move the slider to Zoom in and zoom out the Graphical View.
Graphical representation of ManualMode_1 SCH
Note: ManualMode_1 Super Channel is represented by its frequency spectrum slots in the Optical
Spectrum. Super channels of OCG channel plan are represented by respective OCG numbers

chassis or XTM node, the Graphical View is displayed as below.
Figure 6-13 DLV - Graphical View for DTN/DTN-X/OA Nodes

Figure 6-14 DLV - Graphical View for XTM Node
■ View drop-down menu

Select the appropriate option from the View drop-down menu to display appropriate details in the
Graphical View of the Digital Link Viewer. The various options include:
□ Band and OCG: Displays the existing Physical View with Band PM values along with the line
module and GAM configurations in the terminal nodes of the digital span. This option also
displays the CMM OCG termination point details.
□ Band: Displays the existing Physical View with Band PM values. This is the default option.
□ OSC: Displays the OSC details with OSC PM values. This option also displays the OSC IP
Address, OSC Subnet Mask for BMMs, OAMs, and ORMs and OSC termination points in the
terminal cards with cross-cover in Optical Line Amplifiers.
□ Band + OSC (OTS): Displays the existing Physical View with OTS PM values instead of
Band PM values in the cards.
□ OCG: Displays only the OCG termination point details and hides all Optical Amplifier Nodes,
OAM, ORM and RAMAN FRUs. Target Power Offset is shown in this view.
□ ROADM View: Displays the nodes with ROADM unit, boards, and channel grid (optical
spectrum) view indicating all active or provisioned channels in the selected context. This is
applicable nly for ROADM network. i.e. when channels passing through ROADM units.
□ Band and OCH: Displays all nodes and boards through which O-SNC/OCh trails which are
being passed.

Note: Band and OCH view is applicable is only for XTM node.
■ OCG Number: OCG Number drop-down is enabled only if the view is set to Band and OCG option
or OCG option. Select any OCG number as listed in the OCG Number drop-down. The default
selection is always ALL.
Note: The OCG Number drop-down is a multi selection filter, where selecting All selects all
OCGs in the filter, but de-selecting All de-selects only All option and not any other selected.
■ Zoom Slider
Move the slider to Zoom in and zoom out the Graphical View.
Note: Starting release 15.4, equipment display name in the graphical view is based on the
selection in Security > DNA Settings. The Equipment Display Name is either Provisioned
Equipment Type or Product Ordering Number. By default, Provisioned Equipment Type is
diaplyed. Refer to DNA Security Management Guide for more information.
Starting release 16.2 the OCG number or Super channel number will be shown in the Graphical
view on the LMs. The AD state icon will be shown on the Line PTP of the card. An icon is used to
indicate equipment operating in Manual Mode. See Figure 6-15: SCH number and Manual mode
icon on page 6-21 and Figure 6-16: AD state in Graphical view on page 6-22 for more.
Figure 6-15 SCH number and Manual mode icon

Figure 6-16 AD state in Graphical view
The Table 5-3 provides details of the parameters displayed for each equipment types in the Graphical
View.
Parameters displayed in the Digital Link Viewer

FMM-F250 ■ Equipment AID
■ Equipment type
■ Admin State
■ Service State
■ Alarm indication for this FRU and termination points
■ Optical Power of FMMFSCGPTP
FRM-9D ■ Equipment AID
FRM 4D
FRM-20X ■ Equipment type
■ Admin State
■ Service State
■ Gain Tilt Offset—This attribute is displayed if the selected view is either
Band or OTS.
■ EDFA Power Offset—This attribute is displayed if the selected view is
either Band or OTS.
■ Current Gain—This attribute is displayed if the selected view is either
Band or OTS.
■ Target Gain—This attribute is displayed if the selected view is either
Band or OTS.
■ Gain Adjusted Time—This attribute is displayed if the selected view is
either Band or OTS.
■ Optical Power of BANDPTP—This attribute is displayed if the selected
view is either Band or OTS for FRM-9D, FRM-4D and FRM-20X.
■ Optical Power of SCGPTP—This attribute is displayed if the selected
view is either Band or OTS.
■ — Super Channel oval with darker gray color: Super Channel with
protection group enabled and has a protecting Super Channel (ASE).
■ Working Super Channel without protecting Super Channel.
■ — Super Channel in Active state.
■ — Super Channel in StandBy state.
■ SR — Super Channel in SwitchRequest state .

FSM (and FSE) ■ Equipment AID
■ Equipment type
■ Admin State
■ Service State
■ Optical Power of Line Side SCGPTP—This attribute is displayed if the
selected view is either Band or OTS.
■ Optical Power of Trib Side SCGPTP—This attribute is displayed if the
selected view is either Band and Super Channel or Super Channel
Switching.
■ O-X-CON Trace of FSM SCHCTP via SCGPTP —This attribute is
displayed if the selected view is either Band and Super Channel or
Super Channel Switching. Also, this attribute is displayed only if it is
provisioned and only for SCHCTPs selected via Select Super Channel
Group and Super Channel Number.
■ FSE details if provisioned—This attribute is displayed if the selected
view is either Band or OTS.

IAM ■ Equipment AID
■ Equipment type
■ Admin State
■ Service State
Band and Super Channel or Band or OTS.
either Band and Super Channel or Band or OTS.
view is either Band and Super Channel or Band or OTS.
■ Optical Power of BANDCTP / OTSPTP—This attribute is displayed if the
selected view is either Band and Super Channel or Band or OTS.
■ Launch Power Offset—This attribute is displayed if the selected view is
■ Gain Tilt Offset (Applicable only in Optical Line Amplifier nodes)—This
attribute is displayed if the selected view is either Band and Super
Channel or Band or OTS.
■ OSC IP—This attribute is displayed if the selected view is OSC.
■ Subnet Mask—This attribute is displayed if the selected view is OSC.
■ Laser Bias Current—This attribute is displayed if the selected view is
OSC.
■ Optical Power of OSCCTP—This attribute is displayed if the selected
view is OSC.
■ Fiber Label——This attribute is displayed if the Tx Fiber Label is
configured in the Span/C-Band tab of the Span Properties dialog. This
attribute is visible if the selected view is either Band and Super Channel,
Band and OCG, Band or Band + OSC (OTS).

IRM ■ Equipment AID
■ Equipment type
■ Admin State
■ Service State
view is either Band and Super Channel or Band or OTS.
■ Optical Power of BANDCTP / OTSPTP—This attribute is displayed if the
selected view is either Band and Super Channel or Band or OTS.
■ Launch Power Offset—This attribute is displayed if the selected view is
■ Point Loss Offset—This attribute is displayed if the selected view is
■ Gain Tilt Offset (Applicable only in Optical Line Amplifier nodes)—This
attribute is displayed if the selected view is either Band and Super
Channel or Band or OTS.
■ OSC IP—This attribute is displayed if the selected view is OSC.
■ Subnet Mask—This attribute is displayed if the selected view is OSC.
■ Laser Bias Current—This attribute is displayed if the selected view is
OSC.
■ Optical Power of OSCCTP—This attribute is displayed if the selected
view is OSC.
■ Fiber Label—This attribute is displayed if the Tx Fiber Label is
configured in the Span/C-Band tab of the Span Properties dialog. This
attribute is visible if the selected view is either Band and Super Channel,
Band and OCG, Band or Band + OSC (OTS).

FMP-C ■ Indicates the line side FMP SCGPTP in Band and Super Channel or
Super Channel Switching views.
■ Indicates the trib side FMP SCGPTP in Band and Super Channel or
■ Indicates the muxing of T1A and T1B to L1 and so on in Band and Super
Channel or Super Channel Switching views.
FSP-S ■ Indicates the line side of FSP-S MPO in Band and Super Channel or
■ Indicates the trib side FSP-S MPO in Band and Super Channel or Super
Channel Switching views.
FSP-E ■ Indicates the line side of FSP-E MPO in Band and Super Channel or
■ Indicates the trib side FSP-E MPO in Band and Super Channel or Super
FSP-C ■ Indicates the line side of MPO in Band and Super Channel or Super
■ Indicates the trib side 4 LC Connectors in Band and Super Channel or

OPSM-2 ■ Equipment AID
■ Equipment type
■ Admin State
■ Service State
■ PG State
■ Active and Standby is shown as the status of the port nearby
■ SMF
■ SL
■ ESL
■ Optical Power of OPSMPTP
Note: OPSM-2 shows only one port among its 2 ports and hence
represented with dotted lines.
■ OPSM always shows Line Port A at the top and Line Port B at the
bottom
■ The Fiber drawn between OPSMs is not port to port connection but a
node to node connection.
OFx-100/OFx-500/ ■ Equipment AID

OFx-1200/XT-500F
■ Equipment type
■ Admin State
■ Service State
■ Line System Mode
■ SCGPTP Auto Discovery State (if applicable)—This attribute is displayed
if the selected view is either Band and Super Channel or Super Channel
Switching.
■ Optical Power of SCGPTP—This attribute is displayed if the selected
view is either Band and Super Channel or Super Channel Switching.
■ Optical Power of SCHCTP —This attribute is displayed if the selected
■ Provisioned Super Channel Number—This attribute is displayed if the
Switching. OCG number is displayed for OCG channel.

FMM-C5-ECTR ■ Equipment AID
■ Equipment type
■ Admin State
■ Service State
■ Optical Power in FMMCSCGPTP —This attribute is displayed if the
Switching.
■ Auto Discovery state applicable only for Line Port —This attribute is
displayed if the selected view is either Band and Super Channel or
Super Channel Switching.
RBP and BPP ■ Trib and Line Port indication —This attribute is displayed if the selected
■ Supports:
□ RBP-49-EC
□ BPP-1600-1-EC
□ BPP-1600-33-EC
□ BPP-1600-65-EC

BMM ■ All Cards
■ Equipment type
■ Number of channels
■ Admin State
■ Operating Mode—This attribute is displayed only if this attribute is set to
SLTE Mode 1. However, this is not displayed if the selected view is OSC
Only.
■ EDFA in both directions—This attribute is not displayed if the selected
view is OSC Only.
■ Current Gain/Current VOA—This attribute is not displayed if the selected
view is OSC Only.
■ Target Gain/Target VOA—This attribute is not displayed if the selected
view is OSC Only.
■ Launch Power Offset and Gain Tilt Offset—This attribute is not displayed
if the selected view is OSC Only.
■ Target Power Offset—This attribute is displayed for BMM OCG OPT and
OPR in all the express nodes except in OSC view.
■ Gain Adjustment Time in the user configured time zone—This attribute is
not displayed if the selected view is OSC Only.
■ Midstage value—This attribute is not displayed if the selected view is
OSC Only.
■ OSC IP Address—This attribute is displayed only if the selected view is
OSC only.
■ OSC Subnet Mask—This attribute is displayed only if the selected view
is OSC only.
■ Alarm indication for all FRUs and termination points.
■ PM parameters:
□ BandCTP OPT and OPR—These attribute are displayed only if
the selected view is C-Band or C-band with Termination Points.
□ BMM OCG OPT and OPR—These attribute are displayed for all
views except OSC only view.
□ OSC OPT and OPR—These attributes are displayed only if the
selected view is OSC Only.
□ LBC—Laser Bias Current is displayed only if the selected view is
OSC Only.

□ OTS OPT and OPR—These attributes are displayed only if the

selected view is C-Band + OSC (OTS).
□ DCF PTP - These attributes are displayed for all views except
OSC only view and only if DCF PTP is connected to a DSE

OAM/ORM ■ Chassis and Slot
■ Equipment type
■ Admin State
■ Alarms with mismatched modulation scheme
■ Operating Mode—This attribute is displayed only if this attribute is set to
SLTE Mode 1. However, this is not displayed if the selected view is OSC
Only.
■ EDFA/EDFA with ORM Pump—This is not displayed if the selected view
is OSC Only.
■ Current Gain/Current VOA—This attribute is not displayed if the selected
view is OSC Only.
■ Target Gain/Target VOA—This attribute is not displayed if the selected
view is OSC Only.
■ Launch Power Offset and Gain Tilt Offset—This attribute is not displayed
if the selected view is OSC Only.
■ Gain Adjustment Time in the user configured time zone—This attribute is
not displayed if the selected view is OSC Only.
■ Midstage value—This attribute is not displayed if the selected view is
OSC Only.
■ OSC IP Address—This attribute is displayed only if the selected view is
OSC only.
■ OSC Subnet Mask—This attribute is displayed only if the selected view
is OSC only.
■ PM parameters:
□ BandCTP OPT and OPR—These attribute is displayed only if the
selected view is C-Band or C-band with Termination Points.
□ OSC OPT and OPR—These attributes are displayed only if the
selected view is OSC Only.
□ OTS OTP and OPR—These attributes are displayed only if the
selected view is OTS Only
□ LBC—Laser Bias Current is displayed only if the selected view is
OSC Only.
□ XPR—Crossover Power Received is displayed only if the selected
view is OSC only.
□ DCF PTP - These attributes are displayed for all views except
OSC only view and only if DCF PTP is connected to a DSE.

RAM/REM ■ Chassis and Slot
■ Equipment type
■ Admin State
■ PM Parameters
□ RAM BandCTP OPT and OPR
□ REM BandCTP OPT and OPR
□ OSC OPT and OPR
□ OTS OTP and OPR
Line Modules ■ Chassis and Slot
■ FRU AID
■ Provisioned Equipment type
■ Admin State
■ OCH Port ID (L1 or L2 accordingly)
■ Auto-discovery state
■ Power Levels of the OCH Port
■ Used channel and corresponding OCG details
■ Alarms for OCH with mismatched modulation scheme
■ LM-80 is represented in Dashed boundaries, if only it is partially
equipped.
■ PM Parameters:
□ LM/CMM OCG OPT and OPR, LM-80 OCH OPT and OPR
□ Pre-FEC BER, Post-FEC BER and Q Val of all the four digital
channels associated to each LM-80 OCH

GAM ■ Chassis and Slot
■ Equipment type
■ Admin State
■ EDFA - in the direction, T1 -> L1 or P1 -> P2
■ PM Parameters: GAM OCG T1 or GAM OCG P1 OPR, GAM OCG L1 or
GAM OCG P2 OPT
CMM The lower edge or the upper edge of the CMM block is represented using dashed lines
to indicate that there is another OCG belonging to the same CMM.
■ Chassis and Slot
■ Provisioned Equipment type
■ FRU AID
■ Admin State
■ OCG Port ID (L1 or L2 accordingly)
■ Power Levels - OCG Port, Corresponding OCH Ports
■ Alarms - Equipment Alarm, OCG Port Alarm, OCH Port Alarm
■ CMM is represented in Dashed boundaries, if only it is partially
equipped.
■ Target power offset of CMM OCH
■ One or more CMM OCGs on a specific CMM
■ PM Parameters: LM/CMM OCG OPR and OPT, CMM OCH OPR and
OPT

DSE ■ Chassis and Slot
■ Equipment type
■ Admin State
■ PM Parameters: OPR and OPT
XTM Equipment ■ Equipment AID
■ Equipment Type
■ Admin State
■ Service State
■ Alarms- Port and Card
Note: Digital Link Viewer samples provide more details on reading the data from the Graphical View
of the Digital Link Viewer. See Sample Digital Link Viewer on page 6-61
Digital Link Viewer also provides right-click options to support various operations on the equipment
displayed in the Graphical View. The Table 6-3: Right-click options from the Graphical View on page 6-
36 provides details of all the right-click options supported from the Graphical View.

Table 6-3 Right-click options from the Graphical View

Equipment Right-click options
FSM SCG port ■ Properties
■ Show Alarms
■ Show Events
■ Admin State
■ Alarm Reporting
■ Provisioning
FSM ■ Properties
■ Show Alarms
■ Show Events
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Reset
■ Provisioning
FRM-4D ■ Properties
■ Show Alarms
■ Show Events
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Reset
■ Provisioning
■ Protection Group
■ Automatic Laser Shutdown
■ GMPLS Link
■ OSC
■ Span
■ Connectivity Verification Tools
■ Digital Link Viewer
■ Upload Debug Info

Table 6-3 Right-click options from the Graphical View (continued)

FRM-9D ■ Properties
■ Show Alarms
■ Show Events
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Reset
■ Provisioning
■ Protection Groups
FRM-20X ■ Properties
■ Show Alarms
■ Show Events
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Reset
■ Provisioning
■ Protection Groups
■ GMPLS Link
■ OSC
■ Span


FRM SCG Port ■ Properties
■ Show Alarms
■ Show Events
■ Admin State
■ Alarm Reporting
■ Provisioning
FRM Super Channel ■ Properties
■ Show Alarms
■ Show Events
■ Admin State
■ Alarm Reporting
■ Provisioning
■ Protection Group Manager
FMM-F250 ■ Properties
■ Show Alarms
■ Show Events
■ Admin State
■ Alarm Reporting
■ Delete
■ Reset
OPSM-2 ■ Properties
■ Show Alarms
■ Show Events
■ Admin State
■ Alarm Reporting
■ Provisioning
■ Reset
■ Delete


IAM Band Port ■ Properties
■ Show Alarms
■ Show Events
■ Alarm Reporting
IRM Band Port ■ Properties
■ Show Alarms
■ Show Events
■ Alarm Reporting
IRM Span Port ■ Properties
■ Show Alarms
■ Show Events
OFx-100/OFx-500/OFx-1200 ■ Properties
■ Show Alarms
■ Show Events
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Delete
■ Reset
■ Provisioning
■ Super Channel
■ Super Channel Group
■ Carrier
■ Optical Channels
■ OTUki/OTUCni Section
■ HO ODUki/ODUCni CTP
■ LO ODUkCTP
■ ODUkT


FMM-C-5-ECTR ■ Properties
■ Show Alarms
■ Show Events
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Delete
■ Reset
■ Provisioning
RBP and BPP ■ Properties
■ Delete
■ Show Events
BMM ■ Properties
■ Show Alarms
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Delete
■ Reset
■ GMPLS Link
■ OSC
■ Span
■ Expansion Band Port
■ Optical Carrier Group
■ Circuit Manager
■ Cross-Connect Manager
BMM Span Port ■ Properties
■ Show Alarms


BMMOCG Port ■ Properties
■ Show Alarms
■ Admin State
■ Admin Reporting
■ Provisioning
BMMOSC Port ■ Properties
■ Show Alarms
■ Admin State
■ Admin Reporting
■ Provisioning
This can be viewed only when OSC Only option is selected in the
View drop-down box.
BMM Expansion Band Port ■ Properties

■ Show Alarms
BMM Mid Stage Port ■ Properties
■ Show Alarms
OAM/ORM ■ Properties
■ Show Alarms
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Delete
■ Reset
■ GMPLS Link
■ OSC
■ Span
■ LPump Port (ORM only)
■ Adjust Point Loss


OAM/ORM OSC Port ■ Properties
■ Show Alarms
View drop-down box.
OAM/ORM Mid Stage Port ■ Properties

■ Show Alarms
OAM/ORM Span Port ■ Properties
■ Show Alarms
RAM/REM ■ Properties
■ Show Alarms
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Delete
■ Reset
■ Transparent OSC
■ Span
■ Adjust Point Loss (for RAM modules)
RAM/REM C-Band Port ■ Properties
■ Show Alarms
RAM/REM OSCT Port ■ Properties
■ Show Alarms
View drop-down box.


Line Modules ■ Properties
■ Show Alarms
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Delete
■ Reset
■ Provisioning
■ Line DTF Path (Not for OLM)
■ Back Plane Viewer
AOLMs and AXLMs OCG Port ■ Properties
■ Show Alarms
■ Alarm State
■ Alarm Reporting
■ Start Auto Discovery
LM-80 OCH Port ■ Properties
■ Digital Channel
■ Show Alarms
■ Admin State
■ Alarm Reporting
■ Provisioning


GAM ■ Properties
■ Show Alarms
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Delete
■ Reset
■ Provisioning
GAM OCG Port ■ Properties
■ Show Alarms
■ Provisioning
CMM ■ Properties
■ Show Alarms
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Delete
■ Reset
■ Provisioning
■ Optical Channel Ports
CMM OCH Port ■ Properties
■ Show Alarms
■ Admin State
■ Alarm Reporting
■ Provisioning


CMM OCG Port ■ Properties
■ Show Alarms
■ Admin State
■ Alarm Reporting
■ Provisioning
DSEXT ■ Properties
■ Show Alarms
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Delete
■ Reset
■ DSE Port
■ OSA Port
DSE Port ■ Properties
■ Show Alarms
XTM Equipment ■ Properties
■ Show Alarms
■ Show Events


XT-3300 SCG Port ■ Properties
■ Show Alarms
■ Show Events
■ Provisioning
■ Admin State
■ Alarm Reporting
■ Super Channel
■ Carrier CTP
■ Digital Wrapper CTP
XT-3600 SCG Port ■ Properties
■ Show Alarms
■ Show Events
■ Show Facilities
■ Provisioning
■ Admin State
■ Alarm Reporting
■ Super Channel
■ Carrier CTP
■ OTUk/OTUCni section
■ HO ODUki/ODUCni CTP
■ LO ODUkCTP
Note: Right-click action can be performed on each port of the equipment. For more information on the
termination points on each equipment, refer to the .
Point Loss Offset (PLO) Adjustment from Digital Link Viewer

DNA supports to configure Point Loss Offset (PLO) on RAM, IRM and ORM cards by launching the
Raman/IRM/ORM Turn-up tool from the Digital Link Viewer.

To Launch Raman/IRM/ORM Turn-up Tool from Digital Link Viewer

The following procedure describes launching the Raman/IRM/ORM Turn-up tool from the Digital Link
Viewer.
Step 1 Launch the Digital Link Viewer for the required span. For more information see “Launching the Digital
Link Viewer” on page 5-51.
Step 2 Right click the RAM/IRM/ORM displayed in the Digital Link Viewer for which point loss offset is to be
adjusted and select Adjust Point Loss > Span or Adjust Point Loss > Link.
Change the admin state to Unlock or Maintenance if RAM/IRM/ORM are pre-provisioned, to be able to
view Adjust Point Loss option.
Step 3
Note: The Span menu option provides point loss offset adjustment for all RAMs/IRMs/ORMs
installed in the same direction of the optical span in a sequential order. The turn up action is taken
in only one direction of the span (the direction that is facing the RAM/IRM/ORM) and must be
repeated for the opposite direction of the span. The Link menu option provides point loss offset
adjustment for a single RAM/IRM/ORM.
The RAM/IRM/ORM Turn-up window is displayed. The details displayed in the window are based on
the Span or Link option selected.
Note: —The IRM Turn-up tool is displayed if the Adjust Point Loss option was launched from an
IRM
—The RAM Turn-up tool is displayed if the Adjust Point Loss option was launched from a RAM
—The ORM Turn-up tool is displayed if the Adjust Point Loss option was launched from an ORM
Step 4 For further steps to be performed on the Turn-up Tool, refer to DTN Turn-up and Test Guide.
Step 5 Figure 6-17 Turn-up tool: Warning message
Super Channel Layer/Channel Number/OCG Layer

The Super Channel/Channel Number/OCG Layer in the Digital Link Viewer provides details of all super
channels/OCGs associated with the digital link. This layer displays all performance monitoring parameters
associated with super channels/channel/number/OCGs.
This Panel attributes change based on the launch point of DLV.
Note: Starting release DNA 16.2, OFX SCHCTP and OFX SCHCTP OPT in the Super Channel Layer
have been renamed to Prov SCHCTP and Prov SCHCTP OPT respectively. See Figure 6-18: DLV -
Super Channel Layer on page 6-48 for details.

The Super Channel Layer table changes based on the launch point of DLV. If the selected segment to
launch DLV has a FlexROADM node or DTN-X node with MTC-9/MTC-6 as expansion chassis or a
Optical Line Amplifier node with MTC-9/MTC-6 chassis, the Super Channel Layer table is displayed as
below:
Figure 6-18 DLV - Super Channel Layer
■ Direction Filter
Drop-down menu to filter the data displayed in the Super channel layer and Channel layer of the
Digital Link Viewer based on the direction. The values include, West-->East, East-->West and Both.
The default value is Both.
The Super Channel layer lists all super channels associated with the optical link, that is, all the
FSM super channels from both from source and destination end points. ‘-’ indicates that there is no
super channels data to display. When the user selects a super channel in the Super Channel
Layer, the corresponding row is highlighted, indicating the current selection. The details displayed
for each super channel in this layer are categorized based on the configuration of source and
destination nodes that are part of the digital link. Also, the direction can be filtered to display only
the west-->east or east-->west or both. The table header includes the direction and the Node
Name. The following details associated with the super channels are displayed in this layer of the
Digital Link Viewer:
If OFx is provisioned, the following attributes for the OFx are displayed:
■ Super Channel Number: The Super Channel Numbers.
■ Passband list/ITU Frequency Slot: The Passband List and ITU frequency slot for the selected super
channel.
Note: Passband list is displayed only when protection is enabled on a super channel.
■ Modulation: The available modulation for the selected OFx.

■ Baud Rate: The available baud rate for the selected OFx.
■ Frequency Slot Plan Type : The available frequency slot plan type for the selected OFx.
■ Encoding Mode: The available encoding mode for the selected super channel.
Super channel table lists all the ManualMode_1 super channels for selected channel group. ITU
frequency Slot provides the ManualMode_1 super channels string. If ITU frequency Slot cell in red
indicates a mismatch.

The Super Channel layer includes the following performance monitoring related information for
each of the OCGs:
■ Sch Aid
■ Sch Opt
■ Trib Sch/Scg Aid
■ Trib Sch/Scg Opr
■ Line Sch/Scg Aid
■ Line Sch/Scg Opt
■ Line Sch Offset
■ Line Sch Opr
■ Trib Sch Opt
■ LM Scg Rx Power Offset
Note: All the displayed channel level values are for the provisioned line module.
The right-click options available on these super channels include:

■ Properties—Select this option to launch the respective properties window. For more information,
refer to DNA Configuration Management Guide.
■ Show Alarms—Select this option to launch the Alarm Manager listing the alarms associated with
the super channel.
■ Show Events—Select this option to launch the Event Log listing the events associated with the
super channel.
■ Optical Cross-Connect Manager—Select this option to launch the Optical Cross-Connect Manager
listing the optical cross-connects associated with the super channels. For more information, refer to
DNA Service Provisioning Guide.
■ Optical Circuit Manager—Select this option to launch the Optical Circuit Manager listing the optical
circuits associated with the super channels. For more information, refer to DNA Service
Provisioning Guide.
■ TTI Diagnostics—Select this option to launch the TTI Diagnostics dialog listing the TTI associated
with the super channels.

Figure 6-19 TTI Diagnostics
The Table 5-5 provides details of the parameters displayed in TTI Diagnostics dialog.
Table 6-4 Parameters in TTI Diagnostics dialog

Parameters Description
Node Name Indicates the node names associated with the selected super channel.
Super Channel AID Indicates the AID of the selected Super Channel.
Service State Indicates the service state.
Transmit TTI Indicates the transmit TTI value.
Expected SAPI Indicates the Source Access Point Identifier (SAPI) that is expected from
the Facility side.
Expected DAPI Indicates the Destination Access Point Identifier (DAPI) that is expected
from the Facility side.
Received TTI Indicates the received TTI value.
Trace Identifier Mismatch Indicates if Trace Identifier Mismatch is turned on or off.
Monitoring Mode Indicates the monitoring mode of the selected super channel.
The OCG Layer table changes based on the launch point of DLV.
chassis, the OCG Layer table is displayed as below:

Figure 6-20 DLV - OCG Layer
The OCG layer lists all OCGs associated with the optical link, that is, all the BMM OCGs from source and
destination endpoints. That is OCG 1, 3, 5, 7 for a 40-channel BMM and OCG 1, 2, 3, 4, 5, 6, 7, 8 for an
80-channel BMM. ‘-’ indicates that there is no OCG data to display. When the user selects an OCG in the
OCG Layer, the corresponding row is highlighted, indicating the current selection. The details displayed
for each OCG in this layer are categorized based on the nodes that are part of the digital link. Also, the
direction can be filtered to display only the west-->east or east-->west or both. The table header includes
the direction and the Node Name. The following details associated with the OCGs are displayed in this
layer of the Digital Link Viewer:
If LM association is provisioned, then the following attributes for the LM are displayed:
■ Max BW—The maximum bandwidth available for the provisioned line module.
■ Prov. AID—The provisioned line module AID.
■ Serv. St.—The service state of the associated line module for each BMM OCG.
■ Auto Disc.—The auto-discovery state of the line module. If auto-discovery is successful, a green
check-mark is displayed.
■ Configured Channels—The configured channels is the difference between the total channels and
shutdown channels. (Configured Channels = Total Channels – Shutdown Channels)
Note: If the LM is not provisioned or if the provisioned LM is deleted, then the data associated
with the LM is set to ‘-’ in the OCG layer.
The OCG layer includes the following performance monitoring related information for each of the
OCGs:
■ Configured Channels
■ BMM OCG OPR: OPT
■ LM/CMM OCG OPR: OPT
■ GAM OCG OPR (T1 of GAM-1 or P1 of GAM-2, if GAM is connected)
■ GAM OCG OPT (L1 of GAM-1 or P2 of GAM-2, if GAM is connected)

■ Target Power Offset - This attribute is a read-write attribute for Gen1 and Gen2 Add/ Drop, and
Gen2 Express. It is read-only for Gen1 Express. The range is -4 to 0. For more information, refer to
the DTN and DTN-X System Description Guide.
■ Pre-FEC BER[min - max]—The range of the minimum and the maximum channel Pre-FEC BER
from all the 10 channels in the selected OCG.
■ Post-FEC BER[min - max]—The range of the minimum and the maximum channel Post-FEC BER
from all the 10 channels in the selected OCG.
■ Q Val[min - max]—The range of the minimum and the maximum channel Q factor from all the 10
channels in the selected OCG.
The right-click options available on these OCGs include:

■ Properties—Select this option to launch the respective properties window.
the OCG.
■ Cross-Connect Manager—Select this option to launch the Cross-Connect Manager listing the
cross-connects associated with the OCG.
■ Circuit Manager—Select this option to launch the Circuit Manager listing the circuits associated
with the OCG.
Optical Power Monitoring charts

Optical Power Monitoring charts display the optical power values of the spectrum. The Optical Power
charts are displayed for the LM OPT of Carrier CTP, FRM Line Flex OPT, FRM Line Flex OPR from
Source to Destination.
Note: At the time of the release, Optical Power Monitoring is supported only on FRM-4D, FRM-9D,
FRM-20X and Gen4 Line Modules.

Figure 6-21 Optical Power Monitoring Charts
■ Select Equipment: Select Equipment filter allows selection of equipment for which the Optical
Power data will be displayed. By default, only FRMs are selected. Line modules can be selected.
■ Optical Power Transmitted and Received charts:
For FRMs operating in Terrestrial mode, Optical power monitoring data is shown as part of Flex
Carrier CTPs. For FRMs operating in SLTE mode, Optical power monitoring data is shown as part
of Optical Power Monitoring Scan from Band PTP. For Line modules, PM data of Carrier CTPs are
plotted for the Super Channels which belong to the span as displayed in the Graphical view of the
Digital Link Viewer
X-Axis representation is in line with the Graphical view and based on the IQNOS version. Y-Axis is
the Optical power transmitted(OPT) or Optical power received(OPR) in the Transmit and Receive
charts respectively.
1. For NEs with installed software version R17.0 and above, the X-Axis is in MHz and taken from
□ Carrier list of Flex Carrier CTP for FRMs
□ Carrier Central Frequency of Carrier CTP for XT-3300
2. For NEs with installed software version below IQNOS R17.0, the X-Axis is in (n,m) format and
taken from Frequency slot list of Flex Carrier CTP.
X-Axis representation is in line with the Graphical view and based on the IQNOS version. Y-Axis is
the Optical power transmitted(OPT) or Optical power received(OPR) in the Transmit and Receive
charts respectively.
If there is a mismatch between the baseline granularity & the scan granularity matches, the values
will be displayed in dotted red color.

Figure 6-22 Optical Power Monitoring Charts (Mismatch of Base and Scan granularity)
■ Tool Tip: Tool tip displays information about the Slice Frequency / ITU Frequency, AID, Power
Level and Super Channel Number at that point.
■ Zoom Slider: Zoom Slider allows the user to Zoom-in or Zoom-out the view in the entire charts
panel
■ Mousewheel zoom: Mousewheel zoom is supported on individual charts to zoom-in or zoom-out
the view of a particular chart.
Note: The Super Channel Number drop-down list available in the Graphical view can be used
to select the Super Channel Number(s) for which the Optical Power Monitoring charts will be
displayed.
Super Channel Carrier/Channel Layer

The Super Channel Carrier table changes based on the launch point of DLV.
If the selected segment to launch DLV has a FlexROADM node or DTN-X node with MTC-9/MTC-6 as
expansion chassis or a Optical Line Amplifier node with MTC-9/MTC-6 chassis, the Super Channel
Carrier table is displayed as below:
When a super channel is selected in the Super Channel layer, all the carriers contained in that super
channel are listed in a tabular format. The super channel number of the carrier with an alarm is
highlighted with the respective alarm severity color-code. Also, the direction can be filtered to display only
the west-->east or east-->west or both.

Figure 6-23 DLV - Super Channel Carrier Layer for FlexROADM Nodes
This layer includes the following PM information for the selected super channel.
■ Carrier Number—The carrier associated with super channel.
■ Optical Channel—The optical channel associated with super channel.
■ Serv. St. Carrier—Service State carrier of the super channel.
■ Serv. St. OCH—Service State OCH of the super channel.
■ Serv. St. OTUki—Service State OTUki of the super channel.
■ Carrier Aid—Carrier AID of the associated super channel
■ Carrier Rate—Carrier rate of the associated super channel.
■ Carrier OPT (dBM)—The Optical carrier power transmitted.
■ Flex Carrier OPT (dBM)—The Optical Power Transmitted through Flex carrier.
■ Flex Carrier OPR (dBM)—The Optical Power Received via Flex carrier.
■ Wavelength (nm)—The wavelength of the associated super channel.
Note: This attribute is displayed, if the option is set to Wavelength in Security > DNA Settings >
General tab, DLV Optical Channel Wavelength/Frequency Setting Option. By default, the
option is set to Wavelength. For more information, refer to the DNA Administrator Guide.
Note: The same wavelength is displayed in DLV for dual super channel ports (P27 and P28),
when dual carrier super channel is created on an MXP-400.
■ Frequency (THz)—The frequency of the associated super channel.
Note: This attribute is displayed, if the option is set to Frequency in DNA Settings > General
tab, DLV Optical Channel Wavelength/Frequency Setting Option. For more information, refer to
the DNA Administrator Guide.
■ Carrier Pre-FEC-BER (10-Sec)—The carrier Pre-FEC BER averaged over a period of 10 secs. If
there are no errors or just one error in the 10 sec bin, a BER of 9e-12 is displayed.
■ Carrier Q Val (dB)—The current Q factor of the carrier.
■ Pre-FEC-BER (10-Sec)—The Pre-FEC BER averaged over a period of 10 secs. If there are no
■ Post-FEC-BER (10-Sec)—The Post-FEC BER averaged over a period of 10 secs. If there are no
■ Q Val (dB)—The current Q factor of the super channel.

For a description of all the performance monitoring attributes and their default values, refer to DNA
Performance Management Guide for more information.
Note: In case of insertion/removal of nodes on the digital link or change in super channel
association, after the Digital Link Viewer is launched, an informational message is displayed.
Click Refresh to discover the changes.

■ Properties (West Carrier and East Carrier)—Select this option to launch the respective properties
window.
the channel.
■ Export All Carriers—Select this option to export all the carrier information into a .tsv file.
■ Cross-Connect Manager (West Carrier and East Carrier)—Select this option to launch the Cross-
Connect Manager listing the cross-connects associated with the carrier.
■ Circuit Manager (West Carrier and East Carrier)—Select this option to launch the Circuit Manager
listing the circuits associated with the carrier.
The Channel Layer table for Alien SCH is displayed when clicked on valid SCH provisioned in east
and west FRM add/drop ports. ITU Frequency Slot for each Flex carrier CTP is populated.
Figure 6-24 Channel Layer for Alien SCH
The Channel Layer table changes based on the launch point of DLV.
chassis, the Channel Layer table is displayed as below:
When an OCG is selected in the OCG layer, all the channels contained by that OCG are listed in a
tabular format. The channel number of the channel with an alarm is highlighted with the respective alarm

severity color-code. Also, the direction can be filtered to display only the west-->east or east-->west or
both. The AID of the LM OCH PTP associated to the CMM OCH PTP corresponding to the selected OCG
is displayed.
Figure 6-25 Channel Layer for DTN/DTN-X/OA Nodes
This layer includes the following PM information for 40G, 100G and 500G bandwidth OCG:
For 100G:
■ OCG Layer—The channel associated with the OCG
■ Serv. St.—Service State of the OCG channel.
■ OPT(dBm)—The Optical channel power transmitted.
■ OPR(dBm)—The Optical channel power received.
■ Wavelength (nm) — The wavelength associated with the OCG.
■ Pre-FEC BER(10-Sec)—The Pre-FEC BER averaged over a period of 10 secs. If there are no
■ Post-FEC BER(10-Sec)—The Post-FEC BER averaged over a period of 10 secs. If there are no
■ Q Val(dB)—The current Q factor of the channel.
For 500G:
■ Optical— The optical channel associated with the OCG.
■ Digital— The digital channel associated with the OCG.
■ Modulation— The modulation associated with the OCG.
■ Serv. St. OCH—Service State of the optical channel.
■ Serv. St. OTUKi—Service State of the Digital channel.
■ OPT(dBm)—The Optical channel power transmitted.

■ OCH Pre-FEC BER (10 Sec)—The current Pre-FEC BER value of the OCH channel.
■ OCH Q Val (dB)—The current Q factor of the OCH channel.
■ Wavelength (nm) — The wavelength associated with the OCG.
Note: While creating a dual carrier SCH on MXP, Digital Link Viewer displays the same
wavelenth for both the SCH ports.
■ Pre-FEC BER(10-Sec)—The Pre-FEC BER averaged over a period of 10 secs. If there are no
■ Post-FEC BER(10-Sec)—The Post-FEC BER averaged over a period of 10 secs. If there are no
■ Q Val(dB)—The current Q factor of the channel.
For LM-80 OCH, the above details are displayed for all the four digital channels associated to each
LM-80 OCH. The channel wavelength is displayed for LMs. The target power offset is displayed for
CMM OCH.
Note: In case of insertion/removal of nodes on the digital link or change in OCG association,
after the Digital Link Viewer is launched, an informational message is displayed. Click Refresh
to discover the changes.

■ Property (West Channel and East Channel)—Select this option to launch the respective properties
window.
the channel.
■ Export All Channels—Select this option to export all the channels information into a .tsv file.
■ Cross-Connect Manager (West Channel and East Channel)—Select this option to launch the
Cross-Connect Manager listing the cross-connects associated with the channel.
■ Circuit Manager (West Channel and East Channel)—Select this option to launch the Circuit
Manager listing the circuits associated with the channel.
Optical Channel Table for XTM node

The Optical Channel Table in the Digital Link Viewer provides details of all Optical Channel associated
with the digital link. This table displays all performance monitoring parameters associated with Optical
Channel.
The Optical Channel table changes based on the launch point of DLV. If the selected segment to launch
DLV has a XTM node, the Optical Channel table is displayed as below:

Figure 6-26 DLV - Optical Channel Layer for XTM
■ OCH ID: Displays the Optical Channel ID.

■ OCh End Point: Displays the Optical Channel End Point
■ Direction: Displays the Optical Channel layer of the Digital Link Viewer based on the direction. The
values include, West-->East, East-->West.
The Optical Channel layer includes the following performance monitoring related information for
each of the OCHs
■ Tx Power dBm
■ Rx Power dBm
■ ROADM Attenuation
■ Tx Power dBm
■ Rx Power dBm
Digital Link Viewer Action Panel

The action panel in the Digital Link Viewer consists of the following buttons:
■ Collect Logs—Click to launch the wizard to collect FDR logs for the digital link. For more
information related to FDR logs, refer to DNA Administrator Guide.
■ Refresh—Click to refresh the Digital Link Viewer.
■ Export Current View—Click to export the current View as zip in .PNG Format.
□ Supports Highlight View
□ Provides .tsv file along with snapshots
■ Export All Views—Click to export all the view as zip in SVG Format.
□ Does not export Highlight Views
□ Provides .tsv file along with snapshots
□ SCHCTPs in FRM are populated based on sorted order of spectral slices
□ Infinera Alien waves are also represented in the snapshots.
■ Print—Click to print the graphical representation of the digital link as seen in the Graphical View of
the Digital Link Viewer.

■ Close—Click to close the instance of the Digital Link Viewer.

■ Help—Click to launch context sensitive help related to the Digital Link Viewer.
Launching the Digital Link Viewer

The digital link viewer can be launched from various launch points from the DNA. The following procedure
provides details on various launch points.
To launch the Digital Link Viewer
Note: Starting Release 16.3, multiple Digital Link Viewer instances can be launched for different links
per client session.

■ In the Provisioning View, right-click the DTN/DTN-X link and select Digital Link Viewer.
■ In the Provisioning View, right-click the Digital TE link and select Digital Link Viewer.
■ In the Provisioning View, right-click the Optical TE link and select Digital Link Viewer.
■ In the Provisioning View, right-click the L1 TE Links/IGCC based Digital TE Links and select
Digital Link Viewer.
Note: For launching XTM in Digital Link Viewer Physical View and Provisioning (Digital TE
Link and Optical TE Link)select option is supported.
■ In the Chassis View, right-click the BMM/OAM/ORM and select Digital Link Viewer.
■ In the Chassis View of XT-500F/XT-3300/XT-3600/OFx-1200 chassis, right-click on the
SCGPTP and select Digital Link Viewer.
Note: Sliceable view will not be applicable.
■ In the Chassis View of XT-500S/DLM/XOLM chassis, right-click on the OCGPTP and select
Digital Link Viewer
■ In the Equipment Manager, right-click the row for BMM/OAM/ORM/IAM/IRM and select Digital
Link Viewer. Right-click on FRM 4D if it is in stand alone mode with OSC and select Digital Link
Viewer.
■ In the Circuit Manager, select the Optical tab and right-click the desired circuit and select Digital
Link Viewer.
■ In the Link Manager, go to Menu--> Configuration--> Link Manager--> Link Type and L1 TE
Links/IGCC based Digital TE Links
■ Dragging and dropping links (from the Topology View) on to an active session of the Digital Link
Viewer, refreshes the session with the selected link data. To drag and drop links on to an active
session, ensure that the ‘Assign nodes to admin domain or Drag node or link to set context icon’
is selected.

A warning message is displayed, if AGC is in progress at the bottom of the DLV window. The
warning icon is provided with a tooltip that indicates AGC update cycle is in progress. Please
refresh again to get latest data. See Figure 6-9: Digital Link Viewer on page 6-14. This warning
message is displayed till the AGC update cycle is in progress.
Step 2 Click Ok in the Warning Message window.
The Digital Link Viewer is displayed.
Note: The order in which the nodes in the Digital Link Viewer are displayed is derived from the order
of nodes in the OCG trace.
Note: Click Refresh to refresh the label indication.
The Digital Link Viewer is not launched successfully if:

■ the DTN is stand-alone.
■ there is no DTN in the link.
■ the user does not have security privileges to view either one or more of the nodes that comprise the
digital link.
Sample Digital Link Viewer

This section provides some Digital Link Viewer samples in various configurations:
Figure 6-27 DLV representation for MXP-400 to FRM-20X via Passive Equipment (CO-D480D)

Figure 6-28 DLV representation for MXP-400 to FRM-20X via FMMC-12 and FBM for Dual Carrier
Figure 6-29 DLV representation for MXP-400 to FRM-20X and FRM-20X for Single Carrier
Figure 6-30 DLV representation of MXP-400 to FRM-20X and FRM-20X to Fiber via FMP-C

Figure 6-31 DLV representation of MXP-400 to BMM2 via FMM-C-12
Figure 6-32 DLV representation of multiple third-party nodes between XT-3300 and FRM-20X

Figure 6-33 DLV representation of two third-party nodes between two XT-3300 nodes
Figure 6-34 DLV representation for FRM-9D to FRM-20X (with OTSPTP) and IAM with Pre-Amplier and
Booster Amplier

Figure 6-35 DLV for FRM-20X (with OTSPTP) with Pre-Amplier and Booster Amplier
Figure 6-36 DLV for FRM-20X to RAM1

Figure 6-37 DLV support for FRM Cascade
Figure 6-38 XT-XT IGCC(L1 TE Link) DLV launch

Figure 6-39 IGCC (L1 TE Link) DLV Launch
Figure 6-40 GEN2 SLTE Deployments With LMM
The Modular Idler configuration of (SI-MFM, SI-ASEM, and SI-CWM ) are enhanced to display the
connected LMMs in Digital Link Viewer.

Figure 6-41 DLV of IAM-B-ECH2
The Digital Link Viewer displays the connection between two FRM-20X via IRM-B-ECH1 and IAM-B-
ECH2.
Figure 6-42 Super Channel Switching view: FRM-20X with XT-3600

Figure 6-43 Super Channel Switching view: FRM-20X with FBM and XT-3600 with Multiple Super
Channels
Figure 6-44 Bi-directional association between XT-3600 and OPSM and FMPC and FRM-20X
The Digital Link Viewer displays bi-directional association between XT-3600 and OPSM , OPSM and
FMPC, FMPC and FRM-20X

Figure 6-45 XT-3600 with SCHCTP and corresponding Carrier CTPs
The Digital Link Viewer displays the SCHCTP and corresponding Carrier CTPs with XT-3600 from source
to destination node.
Figure 6-46 XT-3600 with Multiple SCHCTP
The Digital Link Viewer span view is extended to display XT-3600 with multiple SCHCTP.

Figure 6-47 ASE module connectivity to FRM-20X
The Digital Link Viewer displays the ASE modules connectivity to FRM-20X port
Figure 6-48 FRM-20X on Different Nodes with OPSM
The Digital Link Viewer displays the FRM-20X with different node connected via FSP and OPSM.

Figure 6-49 SLTE Terrestrial: OPSM Connected To FRM-20X Trib Without FSP
The Digital Link Viewer displays the OPSM connected to FRM-20X Trib without FSP.

Figure 6-50 SLTE Terrestrial: Unidirectional association from ASE Idler to FRMSCGPTP

Figure 6-51 SLTE Terrestrial: Unidirectional IAM PA connection between two FRMSCGPTP
Figure 6-52 SLTE Terrestrial: Bidirectional connection between two IAM PA, OPSMPTP and
FRMSCGPTP

Figure 6-53 DLV connection of XT-3600 to FRM-20X via FBM and FRM-20X to XT-3600
The digital link viewer displays the connection of XT-3600 to FRM-20X via FBM and FRM-20X to XT-3600
Figure 6-54 DLV connection of XT-3600 to FRM-20X and FRM-20X to XT-3600
The digital link viewer displays the connection between XT-3600 to FRM-20X and FRM-20X to XT-3600

Figure 6-55 AOFX-1200 to XT-3600 interop and OTM-1200 Protection
The DLV displays the interop connection between AOFX-1200 to XT-3600
Figure 6-56 DLV view to display AOFX-1200/SOFX-1200 cards on BMM
The Digital Link Viewer displays the OCGs carried from SOFx-1200 over BMM2C-16-CH

Figure 6-57 DLV Source and Destination Node of AOFX-1200/SOFX-1200 SCHCTP and CarrierCTPs
Figure 6-58 SOFX-1200 with Multiple Super Channels with FSP

Figure 6-59 AOFX-1200 with Single Super Channel with FSP on OCG plan
Figure 6-60 Optical Express between FRM-9D and FRM-20X

Figure 6-61 FRM-20X Express via FSP-CE-1LC
FRM-20X Express is supported via FSP-C , FSP-CE-1LC and FSP-CE-2LC .
Figure 6-62 New Express Fiber Shuffle Panels FSP-EE-9D and 13MPO

Figure 6-63 DLV Window for XTM network
Figure 6-64 Band and OCH View option for XTM

Figure 6-65 AOFX-100 via XTM line system
Figure 6-66 IRM-B-ECH1 as amplifier and pre-amplifier to FRM-20X

Figure 6-67 FRM-20X (SLTE-TLA) connected to a MFM module via WPLM Port

Figure 6-68 FRM-20X (SLTE-TLA) connected to a MFM module via Sys-in Port

Figure 6-69 WPLM with SLTE IAM and Idler Mux , TLA after WPLM

Figure 6-70 WPLM with SLTE IAM and Idler Mux , TLA before WPLM

Figure 6-71 ASEM Direct connected to FRM-20X

Figure 6-72 ASEM Direct connected to FRM-20X via FSP-C
Below sample topology is used to explain the mixed line systems.

Figure 6-73 Sample Topology
Ctrl Link 1 - In this context, BMM2C is present in the data-path with fixed OCGs . DLV shows the FRM
representation in the path. The View drop-down shows both OCG, Band and OCG options.
Ctrl Link 3 - In this context, FRM is present and on the basis of SCHCTPs data-paths will be calculated.
So, both Pure Flex ILS (towards CtrlLink4) and Mixed ILS (towards CtrlLink1) are shown in DLV. In this
case also, DLV shows the FRM representation in the path.
Ctrl Link 4 - In this context, data-path has only pure Flex ILS SCHCTP’s.
Starting Release 17.2, click on SCH and only FRM based path is highlighted when OCG option is
selected from the View drop-down. Also, the OCG table for a mixed line system has a generic column
header for both BMM and FRM TPs.

Figure 6-74 BMM - FRM Mixed Line System
Figure 6-75 Mixed Line System with Frequency slot plan OCG_50GHz_1/2/3

Figure 6-76 FRM MPO-MPO express connection without FSP-E

Figure 6-77 XT-3300 - Sliceable view
In the figure Figure 6-77: XT-3300 - Sliceable view on page 6-91 two SCHs originate on XT_2. One SCH
is between XT_2 - XT_1, the second SCH is between XT_2 - XT_3. The graphical view will display the
selected SCH based on the selection in the Super Channel Group drop-box.

Figure 6-78 Super Channel view: XT-3300 with FRM-9D
Figure 6-79 Super Channel view: XT-3300 with BMM2C and BMM2C express
Figure 6-80 Super Channel view: XT-3300 with BMM2, FMP-C and FSP

Figure 6-81 Super Channel Switching view: FRM-20X with FBM and XT-3300
Figure 6-82 Super Channel view: FRM-20X with FMM-C

Figure 6-83 OPM charts in the Optical Power Monitoring tab
Figure 6-84 Super Channel view: FMM-F250 Head-end configuration with IAM and LMM

Figure 6-85 Multiple DLV Instances launched through different links per client session
Figure 6-86 TTI Diagnostic from OLDP SCH
Note: Starting releases 16.3, TTI Diagnostic information is obtained from OLDP SCH instead of Line
SCH.

Figure 6-87 ALL OCH grouping inside OTUCni container
Note: Starting release 16.3, all OCHs are grouped together into single OTUCni container.

Figure 6-88 Some OCH grouping inside OTUCni container

Figure 6-89 SMFULL Fiber Type between two nodes
Note: Starting Release 16.3, DLV shows new fiber type between two nodes. They are:
■ SMFULL, SMFUltra
Note: Starting release 16.2, the OCG number or Super channel number will be shown in the
Graphical view on the LMs. The AD state icon will be shown on the Line PTP of the card. An icon is
used to indicate equipment operating in Manual Mode. Refer Graphical View on page 6-16 for more
details.
Figure 6-90 XT-500F on ILS3 with XT-500F in another node
Note: For LMs in ManualMode_1, user has to configure ProvisionedOpenwaveRemoteTP on the

FRM/ FSM/ FMM Add/Drop Port in the format NodeID/PortID to be able to view End-to-End DLV. For
multiple LMs connected through a mux the values can be provided separated by commas.

Figure 6-91 Channel Layer representation for XT-500F on ILS3
Figure 6-92 XT-500F in Drop and Continue configuration in Graphical View

Figure 6-93 Super channel layer and Carrier layer for XT-500F in Drop and Continue configuration
Figure 6-94 XT-500S over ILS2 in Graphical View
Figure 6-95 XT-500S in Drop and Continue configuration in Graphical view

Figure 6-96 OCG Layer and Channel layer for XT-500S in Drop and Continue configuration
Figure 6-97 Alien over ILS3 representation in Graphical view
Figure 6-98 Super channel layer and Carrier layer for OTUCni

Figure 6-99 Alien over ILS2 representation in Graphical View
Figure 6-100 Representation of FMP in Graphical view
Figure 6-101 Repersentation of FMP-F in Graphical view

Figure 6-102 Representation of LMM in Graphical view
Figure 6-103 Representation of OTP in Graphical view
Figure 6-104 AOFx-100 representation in Channel Layer

Figure 6-105 AOFX-100 and FMM-C-5-ECTR cards representation in graphical view

Figure 6-106 RBP and BPP cards representation in graphical view
Figure 6-107 End to End view of FRUs in ILS3 deployment

Figure 6-108 End to End view FRUs in ILS2 deployment
Figure 6-109 IAM and OPSM Representation

Figure 6-110 FMM-F250 Representation

Figure 6-111 Channels Table with 100G OCG details
Figure 6-112 Channels Table with 500G OCG details

Figure 6-113 Configured Channels and Shutdown Channels Representation
Figure 6-114 Super Channels Representation

Figure 6-115 Point Loss Offset for ORM

Figure 6-116 Mid Stage DCM Representation

Figure 6-117 BMM2C Representation

Figure 6-118 DLV: Fiber Cut Scenario

Figure 6-119 LM80 and CMM with BMM

Figure 6-120 Line In PAD and Line Out PAD Representation

Figure 6-121 OCG Port Configuration

Figure 6-122 Target Power Offset shown in OCG View only
Figure 6-123 SOFM/SOFX Representation

Figure 6-124 Super Channel Switching View
Figure 6-125 End to End Super Channel Switching Traceability

Click on the SCHCTP (Oval) to highlight the super channel path and click on any other equipment or
facility to remove the highlighted path.

Figure 6-126 Passive cards
Any mismatch in the modulation is represented in Red text with White background. Refer to Figure 6-127:
Color coding for mismatch modulation on page 6-120.
When there is mismatch in Carrier Group mode, OTUKi columns are represented in Grey color.
The Shutdown channels are grayed out in the Channel Layer.

Figure 6-127 Color coding for mismatch modulation
Figure 6-128 Color coding for mismatch in Carrier Group Mode

Figure 6-129 Fiber Label displayed for OTSPTP

6-122 Cloud Xpress Link Viewer
Cloud Xpress Link Viewer

The Infinera Cloud Xpress network element is a 500G transport network element deployed as part of a
point-to-point network configuration. The Cloud Xpress provides Ethernet client access to the Dense
Wavelength Division Multiplexing (DWDM) transport bandwidth.
A digital link is a composite representation of a link between two directly connected Cloud Xpress Nodes.
The Cloud Xpress Link Viewer displays the Cloud Xpress nodes, circuit packs (CX and TOMs) and
termination points which constitute the digital link as shown in Figure 6-130: Cloud Xpress Link Viewer on
page 6-123.
The tool displays details such as:
■ Nodes with node name, status and icon.
■ Chassis with admin state, service state and AID.
■ TOM, OCHCTP and CXOCGPTP details
■ Power levels in entry and exit points from the facility facing the fiber plant
■ Indication of highest severity alarm in equipment and facilities (if applicable)
Use the Cloud Xpress Link Viewer to:
■ monitor the performance of a digital link, with the help of the displayed attributes.
options provided.
Representation in a Cloud Xpress Link Viewer on page 6-122
Launching the Cloud Xpress Link Viewer on page 6-128
Representation in a Cloud Xpress Link Viewer

This section provides information on the details represented in a Cloud Xpress Link Viewer.
Graphical View on page 6-123
Channel Tabular View on page 6-126
Cloud Xpress Link Viewer Action Panel on page 6-128

Figure 6-130 Cloud Xpress Link Viewer
Graphical View
The Graphical View in the Cloud Xpress Link Viewer provides a graphical representation of all the nodes
corresponding to the selected link.

Figure 6-131 Cloud Xpress Link Viewer-Graphical View
The Graphical View displays the following information:

■ Node Name
■ Node Type Icon
■ Node Status— The following states of the nodes are indicated by a water mark across the node:
□ Unreachable
□ Discovering
□ Errored
□ Out of sync
■ CX-10E, CX-40, CX 100E or CX-1200F Chassis
■ CX Chassis AID
■ CX Chassis Admin state and service rate
■ TOM cards in the CX chassis
■ CX OCG PTP and OCH PTP
■ CX SCG PTP and SCH PTP

■ OTS Power levels in entry and exit points from facility facing fiber plant
■ Highest severity alarm in equipment & facilities (if applicable)
■ Any mismatch in TOMs or OCGs
■ Zoom Slider—Move the slider to Zoom in and zoom out the graphical view
■ Reverse Link Direction—Check this option to reverse the display of the link directions.
The Table 5-6 provides details of the parameters displayed in the Graphical view.
Parameters displayed in the Cloud Xpress Link Viewer-Graphical View
TOM ■ TOM Type:
— 40G TOMs with one TribPTP are indicated as TOM_40G

— 10G TOMs with four TribPTPs are indicated as TOM_4_10G
— 100G TOMs with two TribPTPs of TOM 2_10G in breakout mode on ports 4 and 5 in
100G CX
■ TOM Mismatch: This is indicated by a ? symbol on the TOM. This
mismatch is seen:
— If a TOM is present on one end of the link and not at the other end.
— If a TOM_40G is on one end and a TOM_4_10G is on the other end.
■ Admin State
■ Access Identifier (AlD)
CXOCG PTP/CXSCGPTP ■ Optical Power Received
■ Optical Power Transmitted
■ Alarm indication (if any)
OCH PTP/SCH PTP ■ Optical Power Transmitted
■ Modulation Type (such as PM-QPSK etc.)
Cloud Xpress Link Viewer also provides right-click options to support various operations on the
equipment displayed in the Graphical View. The Table 5-7 on page 5-79 provides details of all the right-
click options supported from the Cloud Xpress Link Viewer Graphical View.


TOM ■ Properties
■ Show Alarms
■ Show Events
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Delete
■ Trib Port
CX OCG PTP/CX SCG PTP ■ Properties
■ Show Alarms
■ Show Events
■ Show Facilities
■ Admin State
■ Alarm Reporting
Chassis ■ Properties
■ Show Alarms
■ Show Events
■ Admin State
■ Alarm Reporting
■ Switch on ACO State
■ Tools > Equipment Manager/Facility Manager
termination points on each equipment, refer to the DNA Configuration Management Guide.
Channel Tabular View

The Channel Tabular View displays composite channel properties for all channels (at source and
destination ends).

Figure 6-132 Cloud Xpress Link Viewer—Channel Tabular View
This table includes the following information for a channel.

■ Channel ID—The ID associated with the channel.
■ Source and Destination Node Names
■ AID—The Access Identifier (AID) of the channel.
■ Serv. St.—Service State of the channel.
■ CG Mode—Indicates the Carrier Group mode. This value is set to Single for all Cloud Xpress
network elements.
■ Modulation—Indicates the modulation type for the channel (such as PM_QPSK, PM_BPSK)
■ OPT (dBM)—The Optical power transmitted.
■ Frequency (THz)—The frequency of the associated channel.
■ Wavelength (nm)—The wavelength of the associated channel.
■ Pre-FEC-BER (10-Sec)—The Pre-FEC BER averaged over a period of 10 secs.
■ Q Val (dB)—The current Q factor of the channel.
■ Properties (West Channel and East Channel)—Select this option to launch the respective
properties window.
the channel.
■ Export All Channels—Select this option to export all the channel information into a .tsv file.

Cloud Xpress Link Viewer Action Panel

The action panel in the Cloud Xpress Link Viewer consists of the following buttons:
■ Refresh—Click to refresh the Graphical View and Channel Tabular View displayed in the Cloud
Xpress Link Viewer.
■ Export—Click to export the Cloud Xpress Link Viewer session data into a .zip file. This .zip file
contains:
□ all the data displayed in the channels in .tsv format
□ graphical representation of all the relevant spans in .png format
■ Print—Click to print the graphical representation of the link as seen in the Graphical View of the
Cloud Xpress Link Viewer.
■ Close—Click to close the instance of the Cloud Xpress Link Viewer.
■ Help—Click to launch context sensitive help related to the Cloud Xpress Link Viewer.
Launching the Cloud Xpress Link Viewer

The following procedure provides details on launching the Cloud Xpress Link Viewer.
To launch the Cloud Xpress Link Viewer
Note: Only one instance of the Cloud Xpress Link Viewer can be launched per client session.
■
1. In the Physical View or Provisioning View, right-click the link between two Cloud Xpress nodes and
select Cloud XP Link Viewer.
2. In Circuit Diagnostic Manager, right-click on the link between two CX nodes and select the Cloud
Xpress Link Viewer.
3. In the Chassis View of CX-1200F chassis, right-click on the OCGPTP and select Digital Link Viewer
4. In the Chassis View of CX-1200F chassis, right-click on the SCGPTP and select Digital Link Viewer
The Cloud Xpress Link Viewer is displayed.
The Cloud Xpress Link Viewer is not launched successfully if:
■ the Cloud Xpress node is stand-alone.
■ the links between the CX nodes are not created.
digital link.

Sample Cloud Xpress Link Viewer

Supported Configurations :
■ CX 10E Chassis – 480G: All 48 TOM Slot will be of 10G – mapping One Trib to One OCH
■ CX 40E Chassis – 480G
□ Non Breakout Mode: Twelve 40 G TOM - mapping 4 Trib of TOM to 4 OCH
□ Break Out Mode: Twelve Slots filled with combination of 40G and 4_10G TOM’s
40E - mapping 4 Trib of TOM to 4 OCH
4_10E – mapping 1 Trib to 1 OCH
■ CX100E Chassis – 500G (CX-500S)
□ Non Breakout Mode - 21 slots: First 5 Slots with 100G TOM each rest empty.
Each TOM Trib is mapped to 10 OCH
□ Break Out Mode: First 3 Slots with 100G TOM, Slot 4 , 5 can be 100G or 2_10G, and Slot 6 -
21 will be 10G each.
■ CX-1200F in breakout and non-breakout mode
Figure 6-133 Graphical view of CX-500S node

Figure 6-134 CX 100E BreakOut Mode

Figure 6-135 CX 100E Non BreakOut Mode

Figure 6-136 CX 100 Mix BreakOut Mode

Figure 6-137 CX 40-10E
Figure 6-138 CX 40-10E Non Breakout Mode

Figure 6-139 CX -1200F Breakout

XT Digital Link Viewer

Note: This section is applicable for XT nodes with IQNOS R15.3 and below. For DLV for XT nodes
with IQNOS 16.1 and above, refer Digital Link Viewer on page 6-13
The Infinera XT network element is a 500G transport network element deployed as part of a point-to-point
network configuration. The XT provides Ethernet client access to the Dense Wavelength Division
Multiplexing (DWDM) transport bandwidth.
A digital link is a composite representation of a link between two directly connected Infinera XT Nodes.
The Digital Link Viewer displays the XT nodes, circuit packs (XT and TOMs) and termination points which
constitute the digital link .
The tool displays details such as:
■ Nodes with node name, status and icon.
■ Chassis with admin state, service state and AID.
■ TOM, OCHCTP and XTOCGPTP details
■ Power levels in entry and exit points from the facility facing the fiber plant
■ Indication of highest severity alarm in equipment and facilities (if applicable)
Use the XT Digital Link Viewer to:
■ monitor the performance of a digital link, with the help of the displayed attributes.
options provided.
Representation in an XT Digital Link Viewer on page 6-135
Launching the XT Digital Link Viewer on page 6-141
Sample XT Digital Link Viewer on page 6-141
Representation in an XT Digital Link Viewer

This section provides information on the details represented in an XT Digital Link Viewer.
Graphical View on page 6-136
Channel Tabular View on page 6-139
XT Digital Link Viewer Action Panel on page 6-141

6-136 XT Digital Link Viewer
Figure 6-140 XT Digital Link Viewer
Graphical View
The Graphical View in the XT Digital Link Viewer provides a graphical representation of all the nodes
corresponding to the selected link.

Figure 6-141 XT Digital Link Viewer-Graphical View
The Graphical View displays the following information:

■ Node Name
■ Node Type Icon
■ Node Status— The following states of the nodes are indicated by a water mark across the node:
□ Unreachable
□ Discovering
□ Errored
□ Out of sync
■ XT-10 chassis
■ XT-100 Chassis
■ XT Chassis AID
■ XT Chassis Admin state and service rate
■ TOM cards in the XT chassis
■ XT OCG PTP and OCH PTP
■ OTS Power levels in entry and exit points from facility facing fiber plant
■ Highest severity alarm in equipment & facilities (if applicable)
■ Any mismatch in TOMs or OCGs

■ Zoom Slider—Move the slider to Zoom in and zoom out the graphical view
■ Reverse Link Direction—Check this option to reverse the display of the link directions.
The Table 5-8 provides details of the parameters displayed in the Graphical view.
Parameters displayed in the XT Digital Link Viewer-Graphical View
TOM ■ TOM Type:
— 10G TOMs are indicated as TOM_10G

— 100G TOMs with two TribPTPs of TOM 2_10G in breakout mode on ports 4 and 5 in
100G XT
■ TOM Mismatch: This is indicated by a ? symbol on the TOM. This
mismatch is seen if a TOM is present on one end of the link and not at
the other end.
■ Admin State
XT OCG PTP ■ Optical Power Received
■ Optical Power Transmitted
■ Alarm indication (if any)
OCH PTP ■ Optical Power Transmitted
■ Modulation Type (such as PM-QPSK etc.)
XT Digital Link Viewer also provides right-click options to support various operations on the equipment
displayed in the Graphical View. The Table 5-7 on page 5-79 provides details of all the right-click options
supported from the XT Digital Link Viewer Graphical View.


TOM ■ Properties
■ Show Alarms
■ Show Events
■ Show Facilities
■ Admin State
■ Alarm Reporting
■ Delete
■ Trib Port
XT OCG PTP ■ Properties
■ Show Alarms
■ Show Events
■ Show Facilities
■ Admin State
■ Alarm Reporting
Chassis ■ Properties
■ Show Alarms
■ Show Events
■ Admin State
■ Alarm Reporting
■ Switch on ACO State
■ Tools > Equipment Manager/Facility Manager
termination points on each equipment, refer to the DNA Configuration Management Guide.
Channel Tabular View

The Channel Tabular View displays composite channel properties for all channels (at source and
destination ends).

Figure 6-142 XT Digital Link Viewer—Channel Tabular View
This table includes the following information for a channel.

■ Channel ID—The ID associated with the channel.
■ Source and Destination Node Names
■ AID—The Access Identifier (AID) of the channel.
■ Serv. St.—Service State of the channel.
■ CG Mode—Indicates the Carrier Group mode. This value is set to Single for all XT network
elements.
■ Modulation—Indicates the modulation type for the channel (such as PM_QPSK, PM_BPSK)
■ OPT (dBM)—The Optical power transmitted.
■ Frequency (THz)—The frequency of the associated channel.
■ Wavelength (nm)—The wavelength of the associated channel.
■ Pre-FEC-BER (10-Sec)—The Pre-FEC BER averaged over a period of 10 secs.
■ Q Val (dB)—The current Q factor of the channel.
■ Properties (West Channel and East Channel)—Select this option to launch the respective
properties window.
the channel.
■ Export All Channels—Select this option to export all the channel information into a .tsv file.

XT Digital Link Viewer Action Panel

The action panel in the XT Digital Link Viewer consists of the following buttons:
■ Refresh—Click to refresh the Graphical View and Channel Tabular View displayed in the Cloud
Xpress Link Viewer.
■ Export—Click to export the Digital Link Viewer session data into a .zip file. This .zip file contains:
□ all the data displayed in the channels in .tsv format
□ graphical representation of all the relevant spans in .png format
■ Print—Click to print the graphical representation of the link as seen in the Graphical View of the XT
■ Close—Click to close the instance of the XT Digital Link Viewer.
■ Help—Click to launch context sensitive help related to the XT Digital Link Viewer.
Launching the XT Digital Link Viewer

The following procedure provides details on launching the XT Digital Link Viewer.
To launch the XT Digital Link Viewer
Note: Only one instance of the XT Digital Link Viewer can be launched per client session.
■ In the Physical View or Provisioning View, right-click the link between two XT nodes and select
The XT Digital Link Viewer is not launched successfully if:

■ the XT node is stand-alone.
■ the links between the XT nodes are not created.
digital link.
Sample XT Digital Link Viewer

Supported configurations in R15.3:
■ XT 10E Chassis – 480G: All 48 TOM Slot will be of 10G – mapping One Trib to One OCH
■ XT100E Chassis – 500G
□ Non Breakout Mode - 21 slots: First 5 Slots with 100G TOM each rest empty.
Each TOM Trib is mapped to 10 OCH

□ Break Out Mode: First 3 Slots with 100G TOM, Slot 4 , 5 can be 100G or 2_10G, and Slot 6 -
21 will be 10G each.
Figure 6-143 XT 10

Field Data Recorder Logs Collection

The DNA provides the ability to collect field data recorder (FDR) logs for selected set of network elements
in a span (DTN, DTN-X and FlexROADM). The collection of these logs provides valuable information for
troubleshooting. FDR logs can be collected on the following cards:
■ Circuit Packs - BMM, FRM, MFM, CWM, ASEM, FMM-F250, OPSM-2, IAM, IRM, OAM, ORM,
Raman, and DSE
■ Management Cards - XCM, MCM,IMM, AMM and OMM.
Note: If the FTP server is a Linux machine, ensure the home directory on the FTP server is set
to /. For more information, refer to DNA Administrator Guide.
Note: A periodic move or delete of files and directories created as part of FDR Collection
operation is recommended to save disk space if the FTP directory is present on the same
machine on which the DNA Server is installed.
To collect Field Data Recorder logs

Step 1 Log into the DNA Client with network administrative privilege.
Step 2 Launch the Digital Link Viewer using one of the options below:
■ In the Provisioning View, right-click the DTN link and select Digital Link Viewer.
■ In the Provisioning View, right-click the TE link and select Digital Link Viewer.
■ In the Chassis View, right-click the BMM and select Digital Link Viewer.
■ In the Equipment Manager, right-click the row for BMM and select Digital Link Viewer.
■ In the Network Wide Circuit PM window, right-click a row and select Digital Link Viewer.
■ In the Digital Channel Map Viewer table, right-click the row for a channel and select Digital Link
Viewer.

6-144 Field Data Recorder Logs Collection
Step 3 Click Collect Logs. The Digital Link Viewer for the entire span is displayed.
Figure 6-144 FDR Collection Manager
Step 4 In the FTP Settings panel, enter the following:

■ Server IP—IP address of the FTP server where the logs will be copied
■ User Name—User account information that enables FTP transfer
■ Password—Password for the user name.
■ Confirm Password—Confirm the password for the user name.
■ SFTP Port—The SFTP Port that is used for the FTP transfer of the debug files.
Note: The network element must be enabled for secure file transfer via SFTP. For more
information, refer to DNA Administrator Guide.

Step 5 In the FDR Details panel, enter the following:

■ File Path—Directory on the FTP server where the log files will be copied. If no path is specified,
the logs are copied to the directory <ticket id> under the directory <DNA_Home>.
■ Request ID—Non-editable text field. This will set the auto-generated Request ID when the
“Initiate Transfer” button is clicked.
Step 6 The Collect debug information for panel, displays a tree view of the selected nodes and the available
circuit packs. Select the required circuit packs from the tree view.
Step 7 Confirm the information and click Initiate Transfer.
Step 8 The status of the transfer is displayed in the Status panel.
Step 9 Click Close to close the FDR Collection Manager window.

6-146 Circuit Diagnostic Manager
Circuit Diagnostic Manager

The Circuit Diagnostic Manager (CDM) is a GUI-based application for performing rapid debugging and
fault isolation on circuits (both signaled and manual) in the DNA. The Circuit Diagnostics Manager is
enhanced to support ATN circuits as well.
CDM for DTN, DTN-X, and FlexROADM services can be launched from the Circuit Manager, the Cross-
Connect Manager, the Alarm Manager, Event Log or Facility Manager. CDM for ATN circuits can be
launched from the Circuit Manager.
CDM for Cloud Xpress and XT services can be launched from the tribPTP of Chassis view and Facility
Manager.
Starting Release 16.3, Circuit Diagnostic Manager (CDM) for XTM services can be launched from the
DNA circuit manager.
CDM has the following key features:
■ Displays the end-to-end topology of the selected circuit.
■ Highly configurable circuit and data display with various node, facility, and PM data filtering options
to streamline the troubleshooting procedures.
■ Highlights the highest severity alarm on the facilities and equipments that form a part of the chosen
circuit.
■ Shows the administrative and service states, AINS and diagnostic operations on the constituent
TPs of the circuit graphically.
■ Facilitates the circuit diagnostic operations such as trail trace verification, PRBS generation and
monitoring, section trace monitoring and loopbacks on various facilities that a circuit traverses.
■ Provides historical and real-time PM statistics for the relevant facilities.
■ Provides an option to retrieve alarms, if any on:
□ a facility.
□ a facility and its peer.
□ all facilities and equipments that constitute the circuit.
■ Provides an option to retrieve the diagnostic properties of a facility and its peer.
The administrative status, operational status, diagnostic operations, and alarms on the facilities and
alarms on equipments are dynamically updated.
CDM for ATN network elements supports the following functionalities:
■ Single Node Circuits
□ SIM Local
□ OPSW Local
□ SIM-OPSW Local
■ Multi Node Circuits

□ SIM Local
□ OPSW Local
□ SIM-OPSW Local
□ SIM to OPSW
□ OPSW to SIM
□ OPSW to OFM
□ OFM to OPSW
□ OPSW to OPSW
Launching Circuit Diagnostic Manager

The Circuit Diagnostic Manager (CDM) can be launched from various launch points such as the Circuit
Manager, Cross-Connect Manager, Alarm Manager, Event Log and the Facility Manager. ATN CDM can
be launched from the Circuit Manager.
A maximum of three instances of CDM can be launched per client session. An attempt to launch the
fourth CDM instance prompts the user to close one of the active instances.
Click Ok to exit this prompt. Close one of the active instances of CDM and re-launch the desired instance.
To launch Circuit Diagnostic Manager for DTN, DTN-X and FlexROADM services
Do any of the following to launch CDM:
■ In the Circuit Manager, right-click the desired DTN/DTN-X/FlexROADM circuit and select Circuit
Diagnostic Manager.
■ In the Cross-Connect Manager, right-click the desired cross-connect and select Circuit Diagnostic
Manager.
■ In the Alarm Manager, right-click the circuit related alarms and select Circuit Diagnostic Manager.
■ In the Event Log, right-click the circuit related events or alarms and select Circuit Diagnostic
Manager.
■ In the Facility Manager, right-click the facility associated with the desired circuit and select Circuit
Diagnostic Manager.
■ In the Chassis View, right-click on any Trib port and select Circuit Diagnostics Manager.
■ In the Service Inventory, right-click on any service objects and select Circuit Diagnostics Manager.
Note: A Circuit Selection Dialog with a list of all circuits traced is displayed if multiple circuits
are traced from the launch point. Select the desired circuit and click Apply. For more
information on Circuit Selection Dialog, see Working with Circuit Selection Dialog on page 6-
161.
Note: The Circuit Diagnostic Manager is displayed.

To launch Circuit Diagnostic Manager for ATN circuits

In the Circuit Manager, right-click the desired ATN circuit and select Circuit Diagnostic Manager.
Note: A Circuit Selection Dialog with a list of all circuits traced is displayed if multiple circuits are
traced from the launch point. Select the desired circuit and click Apply. For more information on
Circuit Selection Dialog, see “Working with Circuit Selection Dialog” on page 5-116.
Note: The Circuit Diagnostic Manager is displayed.
Note: ATN CDM uses trace data that is derived from the fiber patches. Hence, in case of missing
fiber patches the trace will be partial.
To Launch Circuit Diagnostics Manager for CX and XT services

Do any of the following to launch CDM:
■ In the Chassis View, right-click on any Trib port and select Circuit Diagnostics Manager.
■ In the Facility Manager, right-click the facility associated with the desired circuit and select Circuit
Diagnostics Manager.
■ For XT nodes with IQNOS R16.1, in the Cross-Connect Manager, right-click the desired cross-
connect and select Circuit Diagnostics Manager for XT services.
■ For XT nodes with IQNOS R16.1, in the Circuit Manager, right-click the desired circuit and select
Circuit Diagnostics Manager for XT services.
To launch Circuit Diagnostic Manager for XTM services
Do the following to launch CDM:

In the Circuit Manager, right-click the desired XTM circuit and select Circuit Diagnostic Manager.
Auto-refresh of Circuit Diagnostic Manager

CDM auto-refreshes every three minutes. When CDM refreshes (either automatically or manually), the
circuits and the launch points are validated. During this operation, if a change is detected, user is notified
of the change and prompted to choose to re-launch or close the prompt and continue to view the old data.
If the user opts to continue with the old data, then:
■ None of the operations from the CDM instance are supported.
■ None of the right-click options are supported.
■ Auto or manual refresh of CDM is also not supported.

Figure 6-145 Circuit Diagnostic Manager Layout
CDM consists of the following panels:

■ Title Bar—The Title bar displays the source and destination node endpoints along with the
configured protection state of the selected circuit at both the end nodes.
■ Circuit Summary Panel—The Circuit Summary panel consists of the following attributes:
Table 6-7 Circuit Summary Panel: CDM

Item Description
Circuit ID Displays the source segment Circuit Identifier of the selected circuit.
Click the [...] to launch the Circuit Selection Dialog window which lists all the circuits
deduced from the launch point. For more information on the Circuit Selection Dialog,
see Circuit Selection Dialog on page 6-159.
This is not applicable to CX/XT.
Service Displays the payload type of the selected circuit.
In End to End CDM:
■ Displays a single value when the payload type is same for both source
and destination segments of the selected circuit.
■ Displays a comma separated value when the payload type is different for
both source and destination segments of the selected circuit.

Table 6-7 Circuit Summary Panel: CDM (continued)

Item Description
Auto Restorable Check-box indicative if the selected circuit is auto restorable.This is not applicable to
CX, XT or XTM.
In End to End CDM:
Tri-State Check-box indicative if the selected circuit is auto restorable.
■ Displays the blank check-box if both Source and Destination segments
are not Auto-Restorable.
■
■ Displays the tick marked check-box if both Source and Destination

segments are Auto-Restorable
■
■ Displays the dot marked check-box if only Source or Destination

segments is Auto-Restorable
■
Route Status Displays the route status of the selected circuit.This is not applicable to CX, XT or XTM.
In End to End CDM:
■ Displays a single value when the route status is same for both source
and destination segments of the selected circuit.
■ Displays a comma separated value when the route status is different for
both source and destination segments of the selected circuit.
The valid values are:
■ OnWorkingRoute—Indicates that the circuit is created and no restoration
has taken place.
■ OnRestoratedRoute—The restoration route computed and switched to
restoration route.
■ AttemptingRestore—Circuit received dataplane failure and restoration is
in progress.
■ OnRestoration_WTR—Work path is healed and the wait to revert timer is
active before switching to the work path.
Protection Status Displays the current protection status of the circuit with respect to both source and
destination endpoints. It indicates the Protection Group status at the node endpoints.
Valid protection status values are Active, ColdStby (Cold Standby), HotStby (Hot
Standby), Unkn (Unknown) and NA (Not Applicable). The protection status at both
source and destination are separated by ‘-’. For example, Active-Hoststdby, where
Active and Hotstdby indicate the protection status at the source and destination ends
respectively.

■ Circuit Overview Panel—The Circuit Overview panel provides a graphical representation with the
details of Nodes and end point segment.
In case of End to End CDM, the Circuit Overview panel provides a graphical representation with the
details of Nodes from source to the destination endpoints. By default, All Segments check-box is
selected. Each segment has a check-box which can be used in filtering the only required segments.
■ Filters Panel—The Filters panel provides the following filter options:
□ Node Filter—Node Filter provides an option to filter the nodes in the circuit topology. The
supported Node Filter options are described in Table 5-11. The default Node Filter selection
is Src & Dest Nodes.
Table 6-8 Node Filter Options: CDM

Filter Option Description
All Nodes When this option is selected all the nodes will be displayed in Circuit Topology panel.
Src & Dest Nodes When this option is selected only source and destination nodes are displayed in the Circuit
Topology. This is the default selection. With this selection, the PM statistics of the client
ports at the source and destination nodes are displayed in a separate window in the Circuit
Topology panel.
Nodes with Alarms When this option is selected all the nodes having Alarms on any of the facilities is displayed
along with the source and destination nodes.
Node Type ■ ATN Nodes—When this option is selected only the ATN nodes are
displayed in Circuit Topology panel
■ DTN Nodes—When this option is selected only the DTN nodes are
displayed in Circuit Topology panel.
■ DTN-X Nodes—When this option is selected only the DTN-X nodes are
■ XTM Nodes—When this option is selected only the XTM nodes are
displayed in Cicuit Topology panel.
■ OA—When this option is selected only the Optical Amplifier and Optical
Line Amplifier nodes are displayed in Circuit Topology panel.
■ ROADM—When this option is selected only the FlexROADM nodes are
■ CX—When this option is selected only the Cloud Xpress nodes are
■ XT—When this option is selected only the XT nodes are displayed in Circuit
Topology panel.
Note: This is not applicable to XTM.

Table 6-8 Node Filter Options: CDM (continued)

Filter Option Description
Digital Function ■ Add/Drop——When this option is selected, all the digital add/drop nodes
are displayed in the Circuit Topology panel.
■ Express——When this option is selected, all the digital express nodes are
displayed in the Circuit Topology panel. This is not applicable to XTM.
Optical Function ■ Add/Drop——When this option is selected, all the optical add/drop nodes
are displayed in the Circuit Topology panel.
■ Express——When this option is selected, all the optical express nodes are
displayed in the Circuit Topology panel
Node Function ■ Nodes in Regen Mode——When this option is selected only the ATN nodes
in Regen mode are displayed in Circuit Topology panel.
■ Segment End Nodes——When this option is selected only the edge node of
each Segment End nodes are displayed in Circuit Topology panel.
Nodes with ■ Loopback——When this option is selected all the nodes having loopbacks
Diagnostics on any of the facilities is displayed along with the source and destination
nodes.
■ PRBS——When this option is selected all the nodes having PRBS enabled
on any of the facilities is displayed along with the source and destination
nodes. This is not applicable to CX/XT/XTM.
■ TTI——When this option is selected all the nodes having TTI on any of the
facilities is displayed along with the source and destination nodes.
■ TCM——When this option is selected all the nodes having TCM are
displayed along with the source and destination nodes. This is not
applicable to CX/XT/XTM.
The selected Node Filter is applied to the Circuit Topology panel, and the Circuit PM tab is updated to
display the PM statistics based on the filter selection.
■ Facility Filter—Facility Filter provides an option to filter the facilities associated with the circuit. By
default, Client CTP Facility Filter is selected. To select a facility, click the desired facility in the
Facility Filter panel. To make multiple selections, press the Ctrl key and select multiple facilities.
Alternatively, click Ctrl + A in the active Facility Filter panel to select all the listed facilities.

Table 6-9 Facility Filter Options: CDM

Filter Option Applicable to Card Type
Client
Trib Client XTC, DTC, ATC, CX, XT, XTM
Client CTP XTC, DTC, ATC, CX, XT, XTM
VCG XTC
SubClient DTC(40G circuits only)
Digital
Trib Line ATC
DTF/ODU Path XTC, DTC, ATC, XTM
Group TP XTC (for VCAT services only)
ODU TCM DTC
OTU Section XTC, XTM
Digital Channel XTC, DTC
Optical Channel XTC, DTC, CX, XT
DLM Optical Channel DTC
Carrier CTPs XTC
CMM OCH Port DTC
LM OCH Port DTC
Super Channel XTC
CMM OCG Port DTC
LM OCG Port XTC, DTC
LM SCG Port XTC
CX OCG Port CX
XT OCG Port XT
Optical
Optical Switch Path MTC-9, MTC-6
GAM OCG Port XTC, DTC
BMM OCG Port XTC, DTC
ATN OCG PTP ATC
Band DTC, ATC, MTC-9, MTC-6
Band Port DTC, ATC, MTC-9, MTC-6

Table 6-9 Facility Filter Options: CDM (continued)

Filter Option Applicable to Card Type
OMS XTM
Others XTM
■ Show Diagnostics—CDM supports a quick view of the diagnostic attributes of the operations such
as Client Port Section Trace (J0), Client Port Test Signal, Client Port PRBS, Client Port TTI,
DTF/ODU Path PRBS, DTF/ODU Path TTI, OTU TTI, ODUkT TTI, Super Channel TTI, XTM. The
Show Diagnostics drop-down menu lists these circuit diagnostic options. By default None is
selected.
The short details window has Close button to close the Short Details window.
Note: For XTM services, only client port TTI , DTF/ODu path TTI and OTU TTI are supported.
Figure 6-146 Short Details Window: CDM
Client Port Section Trace (J0)—Selecting this diagnostic option displays the section trace details in the
short details window next to the client ports in the topology. A mismatch in the expected and received
values will be indicated by an icon in this window. The attributes, Trace Mode, Transmit, Receive,
Expected, Received and Length are displayed in this window.
Client Port Test Signal - Selecting this diagnostic option displays the GbE client test signal diagnostic for
GbE and FC details in the short details window next to the client ports in the topology. Any mismatch in
the expected and received values will be indicated by an icon in this window. The attributes, Trace Mode,
Transmit, Receive, Expected, Received and Length are displayed in this window.
Client Port PRBS - Selecting this diagnostic option displays the PRBS details of OTU and ODU client
facilities in the short details window next to the client ports in the topology. Any mismatch in the expected
and received values will be indicated by an icon in this window. The attributes, Generation Enabled/
Disabled, Monitoring Enabled/Disabled, PRBS Sync Errors and PRBS Errors are displayed in this
window.

Client Port TTI - Selecting this diagnostic option displays the TTI details in the short details window next
to the client ports in the topology. Any mismatch in the expected and received values will be indicated by
an icon in this window. The attributes, Insert TTI (Enabled/Disabled), Transmit TTI, Expected TTI and
Received TTI are displayed in this window.
DTF/ODU Path PRBS - Selecting this diagnostic option displays the PRBS details of Trib DTF Path
facilities for source and destination nodes in short detail window next to channel in the topology. The
attributes, Generation Enabled/Disabled, Monitoring Enabled/Disabled, PRBS Sync Errors and PRBS
Errors are displayed in this window.
CDM also supports the display of Trib and Line side Test Signal Generation, Monitoring status and Errors
for client Port facility for 8*1GbE circuits. The attributes, Line Test Signal Generation Enabled/Disabled,
Line Test Signal Monitoring Enabled/Disabled, Line Test Signal Sync Errors, Line Test Signal Errors, Trib
Test Signal Generation Enabled/Disabled, Trib Test Signal Monitoring Enabled/Disabled, Trib Test Signal
Sync Errors and Trib Test Signal Errors are displayed in this window.
DTF/ODU Path TTI—Selecting this diagnostic option displays the TTI details of DTF for all the digital
nodes having DTF path and line side ODUki in the circuit path in short detail window next to DTF Path in
the topology. Any mismatch in the expected (when configured) and received TTI is indicated in this
window. The attributes, Insert TTI (Enabled/Disabled), Transmit TTI, Expected TTI and Received TTI are
displayed in this window. The details displayed for Line DTF Path include the channel attributes,
Expected TTI and Received TTI.
Channel PRBS—Selecting this diagnostic option displays PRBS details of channel facilities for all the
spans in short detail window next to channel in the topology. The attributes, Generation Enabled/
Disabled, Monitoring Enabled/Disabled, PRBS Sync Errors and PRBS Errors are displayed in this
window.
Channel TTI—Selecting this diagnostic option displays the TTI details of channel facilities for all the
spans in short detail window next to channel in the topology. Any mismatch in the expected (when
configured) and received TTI is indicated by an icon in this window. The attributes, Insert TTI (Enabled/
Disabled), Transmit TTI, Expected TTI and Received TTI are displayed in this window.
OTU TTI—Selecting this diagnostic option displays the TTI details of Line Side OTUki in short detail
window in the topology. Any mismatch in the expected (when configured) and received TTI is indicated in
this window. The attributes, Insert TTI (Enabled/Disabled), Transmit TTI, Expected TTI and Received TTI
are displayed in this window. The details displayed for OTU TTI include the channel attributes, Expected
TTI and Received TTI.
ODUkT TTI—Selecting this diagnostic option displays the CTTI details of Line Side OTUkT in short detail
window in the topology. Any mismatch in the expected (when configured) and received CTTI is indicated
in this window. The attributes, Insert TTI (Enabled/Disabled), Transmit TTI, Expected TTI and Received
TTI are displayed in this window. The details displayed for ODUkT TTI include the channel attributes,
Expected TTI and Received TTI.
Super Channel TTI—Selecting this diagnostic option displays the super channel TTI details in short detail
window in the topology. Any mismatch in the expected (when configured) and received super channel TTI
is indicated in this window. The attributes such as AID, Monitoring Mode and TIM-S Reporting Mode are
displayed in this window.
OCG TTI—Selecting this diagnostic option displays the transmitted, expected and received TTI for the
corresponding CX/XTOCG.

OCG TTI for CX/XT
■ Reverse Circuit Direction—Check-box used to reverse the direction on the circuit from West to East
and East to West in the circuit topology. By default CDM displays the circuits from West to East
direction in the topology.
The PM statistics dashboard will be refreshed to display the PM statistics in the reverse direction if
the Reverse Circuit Direction check-box is selected or de-selected.
■ Circuit Topology Panel—CDM provides a graphical representation of the selected circuit in this
panel. All the circuit components are displayed in this panel based on the Node and Facility filter
selections. This panel also provides information on the Node reachability status. Various operations
including the diagnostic operations on the circuit can be initiated from this panel.
The following types of unidirectional cross-connects are displayed in this panel: Add, Drop,
Express, Hairpin.
The following types of bidirectional cross-connects are displayed in this panel: Add/Drop, Hairpin,
Express.
The cross-connect type and directionality are indicated by symbols. The tool-tip displays the list of
DTP CTPs associated with the cross-connect.
For more information on this panel, see Working with the Circuit Topology Panel on page 6-162.
■ Other tabs
□ Peer Properties—CDM provides an option to compare the diagnostic properties of peer
facilities. Right-click the desired facility in the topology and select Peer Properties. The
respective diagnostic properties of the facility and its peer are displayed in the Peer
Properties tab. The Peer Properties tab is selected by default. This tab is populated with
appropriate values only when Peer Properties on facilities is invoked in the topology.
Note: Starting Release 16.3, In the Peer Properties section, Layer tab is displayed for
XTM services . The Layer tab provides option to view active layer wise properties.

Figure 6-147 Layer tab : XTM Services
□ Circuit PM—The circuit Performance Monitoring Data associated with the Trib PTP, Client
CTP, Trib DTF and Line DTF are displayed in the Circuit PM tab. This data can be grouped
by Hop and Time for all circuits.
In case of 40G circuits, this data can be grouped by Hop, Time or Circuit. Carrier CTP, OPT,
OPR and Laser Bias Current performance data are displayed. The historical (Min, Max, Avg)
data is shown for Pre-FEC Q, OPT, Rx LBC, BER Pre-FEC, PMD, SOPMD.
In case of Super Channels only OFX SCH CTP historical PM data is displayed. The historical
(Min, Max, Avg) data is shown for Optical Power Transmitted. In case of Circuit Performance
Matrix combined for DTN-X and XTM the OPR, OPT and Laser Bias current performance
data is displayed.
All the date and time parameters are displayed in the user configured time zone.
Note: Time Interval—Radio button to select the time interval. CDM provides 24 Hours
(24 Hrs) and 15 Minutes (15 Mins) time interval options for selection for PM data
collection. Click the appropriate radio button to select the Time Interval. Depending on
this selection, the respective time slider is displayed.
Time Slider—If the Time Interval chosen is 24 Hours, then the Time Slider is divided into
eight slots, each representing a day. Where, the one to the extreme right represents the
current day and the label indicates the current time interval. The other six slots represent
the last 6 days with reference to the current day. The two pointers on the scale can be
moved to navigate through the time intervals for the last 7 days. The position of the two
pointers drive the circuit PM data displayed in the Circuit PM tab.
If the Time Interval chosen is 15 Mins, then the Time Slider is divided into 26 slots, each
representing an hour (60 minutes). The one to the extreme right represents the current
hour and the label indicates the current time interval. The other 24 slots represent the
elapsed 24 hours with reference to the current hour. The two pointers on the scale can
be moved to navigate through the time intervals for the last 24 hours. The position of the
two pointers drive the circuit PM data displayed in the Circuit PM tab.
Time Slider

Group—Group historical PM data can be set to either Hop or Time.

Select the appropriate radio button to group and sort the PM data accordingly. Hop is selected by default.
For more information on Performance Monitoring data, see DNA Performance Management Guide .
■ PRBS Test PM—CDM supports collection of real-time PRBS statistics for Optical Channel, Line
Digital Channel, Trib DTF facilities, SONET CTP on GM TAM and SDH CTP on GM TAM. Line
Digital Channel is applicable only to circuits that originate/terminate on LM-80 circuit packs. This
data can be retrieved from the PRBS Test PM tab. The PRBS Test PM tab has two drop-down
menu options, Facility and Refresh Interval for the selection of the facility and the time interval for
retrieving PRBS statistics respectively. This tab displays a maximum of 15 sets of test results
(entries). In cases where more than 15 sets of PRBS test results are recorded, these entries will be
appended following the deletion of earliest of the entries.
Facility: This drop-down menu provides an option to select the Channel or DTF path to view real-
time PRBS data for all channels or DTF paths that are part of the selected circuit respectively.
Refresh Interval: This drop-down menu provides an option to select the Refresh Interval. The
available options are, 15 sec, 30 Sec, 1 Min, 5 Min and None.
Local Reset: Click this to locally reset the PRBS PM data in the PRBS Test PM tab. The PRBS
Test PM tab is refreshed to clear the older data.
The PRBS real-time statistics is displayed following the selection of the refresh interval. CDM
displays the PRBS Sync Errors and PRBS Errors for the selected facility type. The PRBS data for
each refresh interval is appended. If the Refresh Interval is changed, the old PRBS data is cleared
from the table and data for the current refresh interval is populated.
■ Client Signal Test—The Client Signal Test tab is displayed in case of a 1GbE, 10 GbE, 100GbE, 40
GbE circuit and Fiber Channel client. The client signal test results are displayed in this tab. This tab
has a facility Refresh Interval drop-down menu to select the time interval. The available options are,
15 sec, 30 Sec, 1 Min, 5 Min and None. The Line errors, line sync errors, trib errors and trib sync
errors for the facilities at the source and destination nodes are displayed. This tab displays a
maximum of 15 sets of test results (entries). In cases where more than 15 sets of Client Signal test
results are recorded, these entries will be appended following the deletion of earliest of the entries.
■ All Peers Properties — CDM provides an option to compare the diagnostic properties of FRM Line
SCH facility. Right-click the FRM line SCH facility in the topology and select All Peers Properties.
The respective diagnostic properties of the FRM line SCH and its peer is displayed in the All Peer
Properties tab.
All Peers Properties Tab

Note: In Figure 5-72, FRM Line SCH CTP Peer properties is compared along the optical SNC Path.
For example: N1_G and N2_G have used Super channel 3; and N2_G and N3_M have used Super
channel 1.
■ Buttons Panel
The buttons panel include the following buttons at the bottom of the CDM.
□ Refresh Now—Click Refresh Now to refresh Peer Properties tab and the Circuit PM tab.
□ Print—Click Print to print the Circuit Topology as displayed in the Circuit Topology panel.
□ Export—Click Export to export all the data related to the selected circuit. The exported
data includes Circuit Details, Circuit PM, Alarms, network element information, facility
details, PRBS test results, traced circuits, and circuit topology image.
□ Close—Click Close to close the CDM instance.
□ Help—Click Help to display context sensitive help information for CDM.
Circuit Selection Dialog

The Circuit Selection Dialog lists the all circuits traced from the launch point. This window is launched in
either of the cases:
■ When more than one circuit is found for the selected launch point.
■ When the [...] next to the Circuit ID field in the Circuit Summary panel of the Circuit Diagnostic
Manager is clicked.

A list of all circuits traced is listed for selection. The the circuit details for the selected circuit is
shown in the CDM instance.
If the circuit trace identifies circuits with Protection Groups (PGs), then, the configured PG
information and protection status for the circuits is displayed.
Figure 6-148 Circuit Selection Dialog
The Circuit Selection Dialog consists of:

■ Trace Type—Following are the Trace Types supported:
□ Launch Point—Selecting this option enables tracing:
All bi-directional circuits traversing the identified trace point.
All uni-directional circuits traversing the identified trace point and away from the
source endpoint.
□ Full Trace—Select this option to trace all circuit paths originating from source endpoint(s) of
the service. If the source endpoint contributes to a bi-directional circuit, then the circuit trace
tries to find a bi-directional destination endpoint. All the circuit paths originating from both
ends of the bi-directional circuit are displayed.
The default selection is Launch Point.
Note: The Trace type is not applicable in case of ATN circuits.
■ Filter—Used to filter the traced circuits by circuit type. The filter options include:
□ Working—Selecting this option lists all traced circuits that are configured as a working PU for
a PG at either the source or the destination end.
□ Protected—Selecting this option lists all traced circuits that are configured as a protection PU
for a PG at either the source or the destination end.
□ Multicasts—Selecting this option lists all traced circuits that are unidirectional. (Not
applicable in case of ATN Circuits).
□ Current—Selecting this option lists the traced circuit in the current path of the revertive
circuit. (Not applicable in case of ATN Circuits).
□ All—Selecting this option lists all traced circuits.
The default selection is All.

■ Circuit Details Table—The traced circuits are listed in the Circuit Details Table with the following
attributes:
□ Route Status—Displays the Route status of the circuit. For more information on this attribute,
see Table 5-10 on page 5-104.
□ Circuit—Displays the circuit details in the following format:
<NodeName>%<AID of Trib><Directionality><NodeName>%<AID of Trib>[<Configured
protection status at the source end>-<Configured protection status at the destination end>]
For example, Node104%1-A-5-T5-1<-- >Node101%1-A-3-T5-1[W-P]
□ Protection Type—Configured protection type for the circuit/cross-connect. Valid values are 1
Port DSNCP, 2 Port DSNCP and NA.
□ Protection State—Current protection state of the circuit. For more information on this
attribute, see Table 5-10 on page 5-104.
□ Service/Rate—The payload type of the circuit. For more information on this attribute, see
Table 5-10 on page 5-104.
□ Circuit ID (CID)—Circuit Identifier of the traced circuit.
Working with Circuit Selection Dialog

The circuit selection dialog is used to select the circuits traced from the launch point to be displayed in the
Circuit Diagnostic Manager. The circuit selection dialog provides options to:
■ Set the Trace Type to Full Trace or Launch Point by selecting the respective radio buttons.
■ Filter the circuits traced, based on the Circuit Type (Working, Protected, Multicast, and Current) by
selecting the appropriate option from the Filter drop-down menu.
■ Select the circuit listed in the circuit details table for display in the CDM window. Select the desired
circuit from the table and click Apply to display the selected circuit details.
Note: Trace Type is not applicable in case of ATN, CX and XT circuits.
Circuit Topology Panel

CDM provides a graphical representation of the circuit in this panel. All the circuit components are
displayed in this panel based on the Node and Facility filter selections. Various operations including the
diagnostic operations on the circuit can be initiated from this panel. This panel also provides information
on the Node reachability status. If the user launching CDM does not have access privileges to the
intermediate nodes, then such nodes are masked in the Circuit Topology Panel. See Table 5-13 on
page 5-117 for a mapping of display string to node status.

Table 6-10 Node Status and Display String Mapping

Display String Node Status
REA Reachable
URE Unreachable
ERR Errored
OOS Out of Sync
DIS Discovering
Note: Node Status is not applicable to XTM.
In case of a 40G circuit where one of the 10G constituents uses a different equipment (Line Module) a
drop-down menu is displayed in the Circuit Topology panel with a list all 10G components for selection.
Select the desired 10G component to be displayed in this panel.
Working with the Circuit Topology Panel

Various operation such as launching the respective properties window, alarms, events, peer properties,
peer alarms, and other diagnostic operations can be initiated using the right-click options on the circuit
components in the Circuit Topology panel. The various right-click options are listed in Table 5-14 on
page 5-117.
Table 6-11 Right-Click Options: DTN, DTN-X, ROADM, CX, XT

Interface Options
Circuit Topology Panel ■ Properties
■ Show Alarms
■ Trib Port ■ Properties

■ DLM OCG ■ Peer Properties
■ BMM OCG ■ Show Alarms
■ Band ■ Show All Peer Alarms
■ OTS ■ Show Events
■ SubClient
■ SCG Port
■ SCH PTP

Table 6-11 Right-Click Options: DTN, DTN-X, ROADM, CX, XT (continued)

Interface Options
SDH Client Port ■ Properties
■ Peer Properties
■ Show Alarms
■ Show All Peer Alarms
■ Show Events
■ Loopback —None, Facility, Terminal
■ PRBS Generation—Enable, Disable (STM256 only)
■ PRBS Monitoring—Enable, Disable (STM256 only)
Note: PRBS Generation and PRBS Monitoring is applicable only for DTN
SONET Client Port ■ Properties

■ Peer Properties
■ Show Alarms
■ Show Events
■ PRBS Generation—Enable, Disable (OC768 only)
■ PRBS Monitoring—Enable, Disable (OC768 only)
Note: PRBS Generation and PRBS Monitoring is applicable only for DTN
GbE Client Port ■ Properties

■ Peer Properties
■ Show Alarms
■ Show Events
■ Line Test Signal Generation—Enable, Disable
■ Line Test Signal Monitoring—Enable, Disable (not applicable to GbE
Clients present on 40 GE/GR and 100GE/GR TAMs)
■ Trib Test Signal Generation—Enable, Disable
■ Trib Test Signal Monitoring—Enable, Disable (not applicable to GbE
Clients present on 40 GE/GR and 100GE/GR TAMs)


Interface Options
Trib DTF ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
■ Loopback —None, Terminal
■ PRBS Generation—Enable, Disable
■ PRBS Monitoring—Enable, Disable
Line DTF ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
■ LoopBack —None, Facility, Terminal
DLM Optical Channel ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
OLM Optical Channel ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events


Interface Options
Digital Channel ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
DLM OCG, BMM OCG, ■ Properties
Band, OTS, GAM OCG,
LM OCG, SCH ■ Peer Properties
■ Show Alarms
■ Show Events
LM OCH, CMM OCH, ■ Properties
CMM OCG
■ Peer Properties
■ Show Alarms
■ Show Events
CX/XT OCG ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
■ Loopback - None, Facility
FRM-4D OTS ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events


Interface Options
FMM-C5 - Trib SCG and ■ Properties
Line SCG
■ Peer Properties
■ Show Alarms
■ Show Events
OFx-100/OFx-500/ ■ Properties
OFx-1200:
■ Peer Properties
■ SCG Port
■ Show Alarms
■ SCH Port
■ Optical Channel
Port ■ Show Events
■ Carrier CTPs
OFx-100/OFx-500/ ■ Properties
OFx-1200:
■ Peer Properties
■ ODU2 port
■ Show Alarms
■ OTUki Port
■ Show Events
■ Facility Monitoring Mode - Unused, Non Intrusive
Group TP ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
■ Terminal Monitoring Mode - Unused
■


Interface Options
Link ■ Show Alarms
■ Digital Link Viewer —(Visible when Node filter is set to All Nodes)
■ Digital Bandwidth Manager —(Visible when Node filter is set to All
Nodes)
Cross-Connect ■ Properties
ODUk Path ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
ODUki Path ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
OTUki Section ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
■ Facility Monitoring Mode - Intrusive


Interface Options
ODUkTi Path ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
OTU Client ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
■ Loopback - None, Facility, Terminal
■ Terminal PRBS Generation - Enable, Disable
■ Terminal PRBS Monitoring - Enable, Disable
■ Facility PRBS Generation - Enable, Disable
■ Facility PRBS Monitoring - Enable, Disable
■ Facility Monitoring Mode - Unused, Non Intrusive, Limited Intrusive
■ Terminal Monitoring Mode - Unused, Non Intrusive, Limited Intrusive


Interface Options
ODU Client ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
■ Loopback - None, Facility, Terminal
■ Terminal PRBS Generation - Enable, Disable
■ Terminal PRBS Monitoring - Enable, Disable
■ Facility PRBS Generation - Enable, Disable
■ Facility PRBS Monitoring - Enable, Disable
Note: Terminal/Facility PRBS Generation/Monitoring are applicable only
for DTN-X
■ Facility Monitoring Mode - Unused, Non Intrusive, Limited Intrusive
■ Terminal Monitoring Mode - Unused, Non Intrusive, Limited Intrusive
Note: Facility/Terminal Monitoring Mode as Limited Intrusive is
applicable only for DTN.
ODUkT Client ■ Properties

■ Peer Properties
■ Show Alarms
■ Show Events
Fiber Channel ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events


Interface Options
■ Trib SCG ■ Properties

■ Super Channel ■ Peer Properties
CTP
■ Show Alarms
■ Line SCG
■ Band Port
■ Show Events
■ Band PTP
■ Band CTP
■ OTS Port
■ Line SCG
■ Base SCG
■ Expn SCG
Optical Cross-Connect ■ Properties
■ Show Alarms
Line SCH CTP (FRM) ■ Properties
■ Peer Properties
■ All Peers Properties
■ Monitoring Mode - Non Intrusive, Intrusive
■ Show Alarms
■ Show Events
Table 6-12 Right-Click Options: ATN

Interface Options
■ Show Alarms
■ Trib Client ■ Properties

■ Trib Line ■ Peer Properties
■ OTS ■ Show Alarms
■ Show Events

Table 6-12 Right-Click Options: ATN (continued)

Interface Options
Band Port ■ Peer Properties
SDH Client Port ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
SONET Client Port ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
■ Peer Properties
■ Show Alarms
■ Show Events
■ Line Test Signal Generation—Enable, Disable
■ Line Test Signal Monitoring—Enable, Disable


Interface Options
Trib DTF ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
Line DTF ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
■ Loopback —None, Facility
Optical Channel ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
Digital Channel ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
■ Line PRBS Generation—Enable, Disable
■ Line PRBS Monitoring—Enable, Disable


Interface Options
Clear Channel ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
FC Client ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
Otuk Line ■ Properties
■ Peer Properties
■ Show Alarms
■ Show Events
■ Line PRBS Generation—Enable, Disable
■ Line PRBS Monitoring—Enable, Disable
Link ■ Show Alarms
■ Digital Link Viewer — (Visible when Node filter is set to All Nodes)

Table 6-1 Right-Click Option : XTM

Interface Options
■ Show Alarm
SONET/SDH Client port ■ Properties
■ Peer-Properties
■ Show Alarm
■ Show All Peer Alarm
■ Show Events
■ Loop Back
■ TTI Diagnostic Monitoring
OTN Layer Ports ( MXP10GOTN, TPHEX10GOTN, TP100GOTN, ■ Properties
TP100GOTNII, MXP100GOTN, TM100TP, TM100MXP Cards)
■ Peer-Properties
■ Show Alarm
■ Show Events
■ Loop Back
■ Peer-Properties
■ Show Alarm
■ Show Events
Fiber Channel Client ■ Properties
■ Peer-Properties
■ Show Alarm
■ Show Events
■ Loop Back

Table 6-1 Right-Click Option : XTM (continued)

Interface Options
■ iWDM Client ■ Properties

■ iWDM Line ■ Peer-Properties
■ Show Alarm
■ Show Events
OS Port ■ Properties
■ Peer-Properties
■ Show Alarm
■ Show Events
OTS Port ■ Properties
■ Peer-Properties
■ Show Alarm
■ Show Events
TDM Line ■ Properties
■ Peer-Properties
■ Show Alarm
■ Show Events
OCH CTP ■ Properties
■ Peer-Properties
■ Show Alarm
■ Show Events

Table 6-1 Right-Click Option : XTM (continued)

Interface Options
OMS CTP ■ Properties
■ Peer-Properties
■ Show Alarm
■ Show Events
■ Trib Ethernet CTP ■ Properties

■ Line Ethernet CTP ■ Peer-Properties
■ Show Alarm
■ Show Events
■ Trib iWDM ODUk CTP ■ Properties

■ Line iWDM ODUk CTP ■ Peer-Properties
■ Show Alarm
■ Show Events
■ Trib TDM CTP ■ Properties

■ Line TDM CTP ■ Peer-Properties
■ Show Alarm
■ Show Events
TM Xcon ■ Properties
Optical Xcon ■ Properties
■ Show Alarms
To launch properties window for facilities associated with a circuit

Complete this procedure to launch the properties window for the facilities associated with the circuit from
the Circuit Diagnostic Manager.

Right-click the desired facility in the Circuit Topology panel and select Properties.
The respective properties window is displayed. For a description of attributes displayed in the
properties window, refer to the DNA Configuration Management Guide for more information.
To view diagnostic attributes of the peer facilities

Complete this procedure to view the diagnostic attributes of the peer facilities from Circuit Diagnostic
Manager.
Right-click the desired facility in the Circuit Topology panel and select Peer Properties.
The diagnostic attributes of the facility and that of its peer is displayed in the Peer Properties tab below
the Circuit Topology panel.
To retrieve alarms associated with the facilities

CDM provides an option to retrieve the alarms associated with a facility and its peer. Complete the
following procedure to retrieve the alarms associated with the facility.
Right-click the desired facility in the Circuit Topology panel and select Show Alarms.
An instance of the Alarm Manager is launched and the alarms associated with the facility are
displayed. For more information on working with the Alarm Manager, see “Alarm Manager” on
page 1-4.
To retrieve alarms associated with the peer facility, right click the facility and select Show All Peer
Alarms. Alarm Manager is launched and all the alarms associated with the facility and its peer are
displayed.
To retrieve events associated with the facilities

CDM provides an option to retrieve the events associated with a facility and its peer. Complete the
following procedure to retrieve the events associated with the facility.
Right-click the desired facility in the Circuit Topology panel and select Show Events.
An instance of the Event Log window is launched and the events associated with the facility are
displayed. For more information on working with the Event Log, see “Event Log” on page 1-23.
To launch Digital Channel Map Viewer

The Digital Channel Map Viewer for DTN, DTN-X and FlexROADM circuits can be launched from the
CDM instance. Complete this following procedure to launch the Digital Channel Map Viewer.
Note: Ensure that All Nodes option is selected from the Node Filter drop-down menu.
Note: This is not supported for XTM .
Right-click the link in the Circuit Topology panel and select Digital Channel Map Viewer.
The corresponding Digital Channel Map Viewer is launched. For more information on working with the
Digital Channel Map Viewer, see DNA Service Provisioning Guide.

To launch Digital Link Viewer

The Digital Link Viewer can be launched from the CDM instance. Complete this following procedure to
launch the Digital Link Viewer.
Note: Ensure that All Nodes option is selected from the Node Filter drop-down menu.
Right-click the link in the Circuit Topology panel and select Digital Link Viewer.
The corresponding Digital Link Viewer is launched. For more information on working with the Digital
Link Viewer, see “ATN Digital Link Viewer” on page 5-2 or “ATN Digital Link Viewer” on page 5-2 as
applicable.
To enable PRBS generation and monitoring on facilities

PRBS generation and monitoring on facilities that are part of a circuit or cross-connect can be performed
from the Circuit Diagnostic Manager. PRBS generation and monitoring requires that the facility be
switched to the Maintenance State before initiation. CDM facilitates this change in administrative status of
the facilities with a single click to confirm the operation.
Complete the following procedure to enable PRBS generation and monitoring using CDM.
Step 1 Right-click the appropriate TP in the Circuit Topology panel and select PRBS Generation > Enable or
PRBS Monitoring > Enable to enable PRBS generation or monitoring respectively.
A warning message indicating that this operation is traffic affecting is displayed.
Step 2 Click Continue to confirm this operation.
The administrative status of the facility is changed to Maintenance and PRBS generation and/or
monitoring is enabled. This change in administrative status and initiation of the PRBS generation
and/or monitoring is indicated graphically in the Circuit Topology panel by appropriate icons displayed
on the facility.
To disable PRBS generation and monitoring on facilities
Complete the following procedure to disable PRBS generation and monitoring using CDM.
Step 1 Right-click the appropriate TP in the Circuit Topology panel and select PRBS Generation > Disable or
PRBS Monitoring > Disable to disable PRBS generation or monitoring respectively.
A prompt to optionally change the administrative state of the facility is displayed.


■ Select Unlocked to change the administrative state of the facility to Unlocked and click
Continue.
■ Select Maintenance to retain the facility in maintenance state and click Continue.
■ Click Abandon to retain the facility in maintenance state.
Note: Change in the administrative state from Maintenance to Unlocked from this prompt
cannot be completed if either of the operations is still enabled.
Note: PRBS generation and/or monitoring is disabled on the facility and the icon indicating
PRBS generation and monitoring on the facility is deleted in the Circuit Topology panel.
To enable Line and/or Trib Termination Point Tests on GbE clients from CDM
CDM provides options to enable Line and/or Trib Test signal generation and/or monitoring on the GbE
interface.The various options supported are listed in Table 5-14 on page 5-117. Enabling generation
and/or monitoring the Line and/or Trib Termination Point tests requires that the facility be switched to the
Maintenance State. CDM facilitates this change in administrative state of the facilities with a single click to
confirm the operation.
Note: Line Test Signal Monitoring and Trib Test Signal Monitoring are not supported on 40GbE clients
on TAM-1-40G/GE/GR and on 100GbE clients on TAM-1-100GE/GR.
Complete the following procedure to enable Line/Trib Test signal generation/monitoring on GbE client
from the CDM application:
Step 1 Right-click the appropriate GbE client object in the CDM application and select the appropriate option:
■ Line Test Signal Generation > Enable—to enable the generation of test signal on the line side.
■ Line Test Signal Monitoring > Enable—to enable the monitoring of bit errors on the line side.
■ Trib Test Signal Generation > Enable—to enable the generation of test signal on the tributary
side.
■ Trib Test Signal Monitoring > Enable—to enable the monitoring of bit errors on the tributary
side.
A warning message is displayed indicating that the operation test signal generation/monitoring
is service affecting.
The administrative status of the facility is changed to Maintenance and test signal generation and/or
monitoring is enabled. This change in administrative status and initiation of the test signal generation
and/or monitoring is indicated graphically in the Circuit Topology panel by appropriate icons displayed
on the facility.

To disable Line and/or Trib test signal generation and/or monitoring on GbE client from CDM
Complete the following procedure to disable PRBS generation and monitoring using CDM.
Step 1 Right-click the appropriate GbE client object in the CDM application and select the appropriate option:
■ Line Test Signal Generation > Disable—to enable the generation of test signal on the line side.
■ Line Test Signal Monitoring > Disable—to enable the monitoring of bit errors on the line side.
■ Trib Test Signal Generation > Disable— to enable the generation of test signal on the tributary
side.
■ Trib Test Signal Monitoring > Disable—to enables the monitoring of bit errors on the tributary
side.
Continue.
Note: Change in the administrative state from Maintenance to Unlocked from this prompt
cannot be completed if either of the operations is still enabled.
Note: Test signal generation and/or monitoring is disabled on the facility and the icon
indicating test signal generation and/or monitoring on the facility is deleted in the Circuit
Topology panel.
To enable loopback on facilities

CDM provides options to set loopbacks on facilities. The various options supported are listed in
Table 5-14 on page 5-117 and Table 5-15 on page 5-123. Setting loopback on a facility requires that the
facility be switched to the Maintenance State. CDM facilitates this change in administrative state of the
facilities with a single click to confirm the operation.
In case of a 40G circuit:
■ loopback can be enabled on individual TPs (10G circuit constituents).
■ loopback can be enabled on all four components at the Group TP level. This operation requires that
loopback is not enabled on any of the constituent TPs. If loopback is enabled on any of the
constituent TPs, enabling loopback at the Group TP level prompts the user to disable the active
loopback on the constituent TP(s) and retry.
Complete the following procedure to enable loopback using CDM.

Step 1 Right-click the appropriate client CTP in the Circuit Topology panel and select Loopback > Facility or
Loopback > Terminal to enable respective loopback on the facility.
A warning message indicating that this operation is traffic affecting is displayed.
Note: For XTM Services, no warning message is displayed.

The administrative status of the facility is changed to Maintenance and loopback is enabled. This
change in administrative status and loopback operation is indicated graphically in the Circuit Topology
panel by appropriate icons displayed on the facility.
For more information on loopbacks, see “Loopbacks in DTN and DTN-X” on page 3-3.
To disable loopback on facilities
Complete the following procedure to disable loopback using CDM.
Step 3 Right-click the appropriate client CTP in the Circuit Topology panel and select Loopback > None to
disable loopback on the facility.
Note: For XTM Services, no prompt is displayed.

Continue.
Loopback is disabled on the facility and the icon indicating active loopback on the facility is
deleted in the Circuit Topology panel.
To Enable TTI Monitoring

CDM provides option to enable TTI Monitoring facility. . Do the following to enable TTI Monitoring:
■ In the Circuit Diagnostic Manager window, right-click appropriate client CTP in the Circuit Topology
panel and select TTI Monitoring> Enable to enable respective TTI Monitoring facility.
To Disable TTI Monitoring

CDM provides option to disable TTI Monitoring facility. Do the following to disable TTI Monitoring:
■ In the Circuit Diagnostic Manager window, right-click appropriate client CTP in the Circuit Topology
panel and select TTI Monitoring> Disable to disable respective TTI Monitoring facility.
Exporting data from Circuit Diagnostic Manager

CDM provides an option to export all data related to the circuit from the CDM instance. The exported data
include:

Table 6-14 Export Data: CDM

Exported Data Details
Circuit Details CircuitDetails.tsv
Circuit PM PM15Min.tsv and PM24Hr.tsv for 15 minutes and 24 hours PM data.
Alarms Alarms.tsv
In case of a 40G circuit, where the 10G constituents use different Line
Modules, the alarms associated with each of the 10G components are
exported into individual tsv files.
Network element information TopoNodesInfo.tsv
Modules, the network element information associated with each of the 10G
components are exported into individual tsv files.
Facility details Facilities.tsv
Modules, the facility details associated with each of the 10G components are
exported into individual tsv files.
PRBS Test results PRBS_Test.tsv
Note: This is not supported for XTM.
Traced circuits Circuit Trace.tsv

Circuit Topology (Graphical CircuitTraceImage.png
representation of the circuit) In case of a 40G circuit, where the 10G constituents use different Line
Modules, the circuit topology of each of the 10G components are exported
into individual png files.
To export data from Circuit Diagnostic Manager

Complete the following procedure to export circuit information from CDM:
Step 1 Click Export at the bottom of the CDM window.
The Save dialog is displayed.
Step 2 Navigate to the directory location to save the circuit information and enter the name of the file and click
Save.
A prompt indicating the success of the export operation along with the location of the file is displayed.
The circuit data is exported in separate files and bundled into a .zip file. Unzip the file to view individual
files containing the circuit information.
Sample Circuit Diagnostic Manager

This section provides some Circuit Diagnostic Manager samples in various scenarios:

Figure 6-149 CDM support for FRM Cascade on MXP-400
Figure 6-150 CDM support (Interleaver) for Passive Equipment on MXP-400

Figure 6-151 CDM support (AWG) for Passive Equipment on MXP-400
Figure 6-152 CDM support for Dual Carrier SCH on MXP-400
Circuit Diagnostic Manager for P27-1 carrier Trace in Dual Carrier Super Channel.

Figure 6-153 CDM support for Single Carrier SCH on MXP-400
Circuit Diagnostic Manager displays the Single Carrier Super Channel connected to the assembled stack
of MXP-400, FMMC-12, FRM and IAM.

Figure 6-154 CDM support for FRM Cascade
Figure 6-155 CDM Summary Table for UAS PM

Figure 6-156 CDM for IAM-2-C
Figure 6-157 CDM for XT-3600 with SCHCTP
CDM assembled with the SCHCTP (SCH 1) which is used as part of the current trace, when multiple SCH
are present on an XT-3600.

Figure 6-158 CDM for XT-3600 Re-generation with Electrical TOM
CDM allows the assembling of XT-3600s as ‘Intra Node Link’ which is connected using copper
regeneration cable.
Figure 6-159 SLTE Terrestrial : CDM for FRM-20X connected with OPSM
The Circuit Diagnostic Manager supports the FRM-20X connected with OPSM.

Figure 6-160 CDM for FRM-20X with Add/Drop Xcon And On Different Nodes
The Circuit Diagnostic Manager supports the FRM-20X Add/Drop Xcon and on Different Nodes.
Figure 6-161 SLTE Terrestrial: Two uni-directional ports of IAM PA between two bi-directional OPSMPTP
and FRMSCGPTP ports
The Circuit Diagnostic Manager displays the assembled unidirectional OTSport and Bandportof IAM PA
between two bi-directional OPSMPTPand FRMSCGPTPports.

Figure 6-162 SLTE Terrestrial: Uni-directional port of IAM PA between two bi-directional FRMSCGPTP’s
ports
The Circuit Diagnostic Manager displays the assembled un-idirectional OTSport and Bandport of IAM PA
between two bi-directional FRMSCGPTP’s ports.
Figure 6-163 CDM for Circuit PM: XTM and DTN-X

Figure 6-164 CDM for Show Diagnostics Filter: XTM and DTN-X
Figure 6-165 CDM for Node Filter: XTM and DTN-Xnodes
Figure 6-166 CDM for TIM2-2-100GM/GX

Figure 6-167 CDM for interop connection of OTM-1200 and XT-3600
Figure 6-168 CDM connection for XT-3600 to FRM-20X via FBM and FRM-20X to XT-3600

Figure 6-169 CDM connection for XT-3600 to FRM-20X and FRM-20X to XT-3600
The circuit diagonistic manager displays connection of XT-3600 to FRM-20X and FRM-20X to XT-3600
Figure 6-170 CDM interop connection for AOFX-1200 to XT-3600
The Circuit Diagnostic Manager displays the interop connection of AOFX-1200 to XT-3600

Figure 6-171 CDM for OTM-1200 Protection
Figure 6-172 CDM for AOFX-1200/SOFX-1200 FRUs with BMM card

Figure 6-173 CDM support for XT-3300 regeneration with copper cable in same node
Figure 6-174 CDM with SOFX-1200 and AOFX-1200 in OCG Mode

Figure 6-175 CDM with AOFX-1200 in Open mode with FRM-20x on a different node
Figure 6-176 BMM – FRM Mixed Line System
Figure 6-177 CDM for XT-3300 with LMM and BMM2

Figure 6-178 CDM for XT-3300 with FBM and FRM20X
Figure 6-179 CDM for XT-3300 with BMM2C

Figure 6-180 CDM for XT-3300 with BMM2C Digital wrapper
Figure 6-181 CDM for FRM-20X express

Figure 6-182 CDM for CX-500S

Figure 6-183 CDM for XTM: PM tab with Category filter

Figure 6-184 CDM for XTM: Enable SAPI/DAPI on OTN cards
Figure 6-185 Summary Panel View: XTM
Figure 6-186 Show Diagnostic: XTM

Figure 6-187 Facility Filter: XTM
Figure 6-188 SOLx2 With All OCHs Grouped

Figure 6-189 SOLx2 With Partial OCHs Grouped

Figure 6-190 CDM with Back to Back Intra and Inter Network Element Link

Figure 6-191 CDM with AOFX-500 in Manual mode with Multi plexer on different node
Figure 6-192 CDM with XT-500F in Manual mode with Multiplexer on different node

Figure 6-193 CDM with XT-500F and FSM and FRM-9D

Figure 6-194 CDM with XT-500S in Manual mode with FSM and FRM-9D
Figure 6-195 CDM with OTUCni with SOFx-500 and FRM-9D

Figure 6-196 Super Channel TTI on SCH facility for XT-500F
Figure 6-197 New counters for GFPTP
Note: Starting DNA release R16.2, the Circuit Diagnostic Manager is enhanced to display the AID of
the equipment on the equipment. The Shelf and Slot details of the equipment are displayed as a tool-
tip on the equipment. Refer Figure 6-145: Circuit Diagnostic Manager Layout on page 6-149 for the
updated view in Circuit Diagnostic Manager.

Figure 6-198 CDM with AOFx-100 and FMM-C5 over ILS2
Figure 6-199 CDM with AOFx-100 and FMM-C5 over ILS3

Figure 6-200 Express cross connect between AOFx-100
Figure 6-201 AOFx-100 and Tributary module in case of OTM2-500 and OTXM-600

Figure 6-202 FlexILS sites Representation
Figure 6-203 XT and CX nodes

Figure 6-204 CX/XT 100GbE Services
Figure 6-205 CX/XT 10GbE Services
Figure 6-206 Circuit Diagonistic Manager for CX-1200F

Figure 6-207 Circuit PM for OCG CX/XT
The graphical view of Multiple ODUPaths, OTU Section TPs, Carrier CTPs and 100GbE ODU2i-10V
Service is represented as shown below in the CDM:
Figure 6-208 VCAT and Carrier CTP representation

Figure 6-209 Multi OCG for ILS2 Links
Figure 6-210 Multi OCG for BMM Express

Figure 6-211 Multi SCG
Figure 6-212 Multi SCG for FMM-F250

Figure 6-213 Multi SCG for FRM Express

Figure 6-214 Multi SCG for Multi FSM

Figure 6-215 1GFC-CC and 2GFC-CC Payload Representation
Note: The above sample screenshot is taken pre release 10.0, and hence the R10.0 GUI
enhancements are not reflected. However, working with CDM remains the same. For all UI
enhancements of R10.0, refer to Figure 5-65 on page 5-101.
The line module open wave is represented as shown below in the CDM where the topology node stack
includes all the TPs from Trib to LM OCGs.

Figure 6-216 Open Wave - Line Modules Representation
The optical channel with dual carrier is represented as shown below in the CDM:

Figure 6-217 Optical Channels Representation

Figure 6-218 Circuit Diagnostic Manager circuit through AOLM-500: DTN-X

Figure 6-219 Circuit Diagnostic Manager for 4GFC Service: ATN

Figure 6-220 Circuit Diagnostics Manager: Trail Trace Details

Figure 6-221 STM-64 with single carrier

Figure 6-222 ODU Switching

Figure 6-223 10GbE Network Mapping as ODU2e

Figure 6-224 100GbE Non VCAT
Figure 6-225 100GbE VCAT

Figure 6-226 BMM2C-16-CH
Figure 6-227 Multi OCG BMM Express

Figure 6-228 Multi SCG with FMMF250 and FRM Expressed

Figure 6-229 Multi SCG With Multi FSM

Figure 6-230 Graphical Stack display of FMMF250, FRM 4D, OPSM-2

Figure 6-231 SIM Local
Figure 6-232 CDM - ATN as Sub-10G Feeder to DTN/DTN-X

Figure 6-233 CDM – OPSW Protected Multi-segment Circuit

6-234 SOAM Manager
SOAM Manager
The Service Operations Administration and Maintenance (SOAM) Manager is an inventory of
performance and connectivity fault monitoring functionality for Layer2 Ethernet Service (EVC). Ethernet
OAM supports protocols used for installing, monitoring and troubleshooting Ethernet networks to increase
management capability. Currently, only connectivity fault management is supported.
The SOAM Manager is used to view, create, update, export and delete EVC(s). This section provides the
following details:
■ Launching the SOAM Manager on page 6-234
■ SOAM Manager Layout on page 6-235
■ Viewing MD/MA/MEP Properties on page 6-239
■ Creating Maintenanace Domain on page 6-244
■ Creating Maintenanace Association on page 6-246
■ Creating Maintenance End Point on page 6-249
Launching the SOAM Manager

The SOAM Manager can be launched from various launch points. The data displayed in the SOAM
Manager depends on the Context set determined by the launch point. These launch points are provided
as right-click options on various objects such as, Network level, Node level.
To launch the SOAM Manager

■ From the Main Menu, select Fault>SOAM Manager
■ In the Topology View or Network Tree View, right-click the node and select SOAM Manager
■ In the Topology View or Network Tree View, right-click the admin domain and select SOAM
Manager
The SOAM Manager is displayed.

Figure 6-234 SOAM Manager
SOAM Manager Layout

This section provides details on the layout of the SOAM Manger.
The SOAM Manager consists of the following panels/regions:
■ Context Panel—The Context panel displays the context from which the SOAM Manager is
launched. If the SOAM Manager is launched from the main menu, the Context panel displays
‘Network Wide’.
For each instance of SOAM Manager, besides ‘Node’, the latest five contexts are displayed in the
Context drop-down menu. When the sixth context is launched, the oldest context is replaced.
■ Search Panel
The search panel provides a small window to enter the search string. The SOAM table is refreshed
to display the entries that match the search string entered.

6-236 SOAM Manager
The Apply Search check-box, if selected is indicative that the SOAM Table is refreshed to display
the entries that match the search criteria only. To clear the search criteria on the SOAM Table,
uncheck this check-box. To re-apply the search criteria on the SOAM Table, select this check-box.
The Clear button is used to delete or clear the search string entered. Clicking the clear button when
the search criteria is active clears the search criteria on the SOAM Table and also the search string
entered.
Note: The search criteria is applied to the current page only.
■ Count
This indicates the total count of the number of services listed in the SOAM Table of the SOAM
Manager.
■ Page Length and Navigation Panel
This panel provides details of the range of number of services displayed in the current screen and
allows to customize the number of services displayed per page. Additionally, this panel includes the
page traversal buttons to ease the navigation between pages.
This Panel is divided into the following panels:
□ Display Range —The (count) range of services displayed in the current page of the SOAM
Table. The display range can be set by typing the range in the fields next to Displaying tag in
the page length and navigation panel. It also provides an option for the user to directly
navigate to a specific offset by entering the offset value in this field.
□ Page Length—A drop-down menu that allows to customize the page length of the SOAM
Table. It is used to set the maximum number of SOAM to be displayed per page. The default
value is 250.
□ Page Traversal Keys—Buttons that allow to traverse between SOAM Table pages in the
SOAM Manager.
Table 6-15 SOAM Manager: Page Traversal Keys

Buttons Description
First Page—Click this button to navigate to the first page of the SOAM Table.
Previous Page—Click this button to navigate to the previous page relative to the current page of the
SOAM Table.
Next Page—Click this button to navigate to the next page relative to the current page of the SOAM
Table.
Last Page—Click this button to navigate to the last page of the SOAM Table.
Suspend/Resume Updates Keys—Suspend Updates and Resume Updates buttons are used to stop or
start the SOAM Manager from getting dynamically updated.
■ Customize Columns

Icon used to customize the SOAM Table columns. The columns to be displayed and the order of
display can be configured from the View Customization window, launched by clicking the
Customize Columns icon.
■ Restore Default Toolbar Positions
Icon used to reset the customized toolbar positioning to default positions in the SOAM Manager.
■ Quick Filters Summary Panel: The Filter summary panel summarizes the filtering criteria selected
for the view. The SOAM Table in the SOAM Manager is refreshed only when the Apply Filter(s)
button is clicked after the Quick Filter selection.
■ SOAM Table—The SOAM Table displays existing services and associated details in a tabular
format.
Table 6-16 SOAM Manager: MD Table

Item Description
Node Displays the node name on which the MD is created.
Node Label Displays the identifier of the node.
ID Displays the assigned MD ID.
Label Displays the identifier of the MD.
MD Name Displays the assigned name of the MD.
MD Level Displays the assigned MD Level. The valid values is between 0 to 7.
Name Format Displays the name format of the MD. The valid value is CharString and None.
MHF Criteria Displays whether the MIPs are automatically created or not.
Note: In Release 16.2, this parameter is set to NONE.
Sender Permission Displays the sender ID TLV. This parameter is set to NONE.
OAM Entity In Use Displays whether the OAM Entity is in use or not. The valid value is True or False.
Table 6-17 SOAM Manager: MA Table

Item Description
Node Displays the node name on which the MA is created.
ID Displays the assigned MA ID
Label Displays the identifier of the MA.
MA Name Displays the assigned name of the MA.
MD Name Displays the associated MD name
MD Level Displays the MD level. The valid value is between 0 to 7.

6-238 SOAM Manager
Table 6-17 SOAM Manager: MA Table (continued)

CCM Interval Displays the CCM Transmission Interval. The valid value can be one of the following:
□ 3.33MS
□ 10MS
□ 100MS
□ 1S
□ 10S
.
Sender Permission Displays the sender ID TLV. This parameter is set to NONE.
OAM Entity In Use Displays whether the OAM Entity is in use or not. The valid value is True or False.
Table 6-18 SOAM Manager: MEP Table

Item Description
Admin State Displays the administartive state of the MEP service
Node Displays the node on which the MEP is created
ID Displays the assigned MEP ID. The valid value can be between 1 to 8191.
Label Displays the identifier of the MEP
Direction Displays the direction of the MEP. The valid values are UP and DOWN
MEP ID Displays the MEP ID
CCM Enabled Displays whether the CCM Transmission Interval is enabled or disabaled. The valid
value is True or False.
MD Level Displays the assigned MD level. The valid value is between 0 to 7.
Associated Interface Displays the AID of the AC or Ethernet Interface with which this MEP is associated.
Role Indicates the role performed by the MEP. The valid value is Fault Monitoring.
ETH-CSF Support Indicates if Ethernet Client Signal Failure messaging is enabled or disabled. Supported
values include:
□ Enabled - Ethernet CSF messaging is enabled
□ Disabled - Ethernet CSF messaging is not enabled
□ NA - Ethernet CSF messaging is not supported. This is displayed for
MEPs corresponding to network elements running IQ NOS R16.1 or
lower.
■ New—Click New to create a new MD/MA/MEP.

■ Delete—Use the Delete button to delete a MD/MA/MEP.

■ Export Current Page

This functionality supports exporting the SOAM inventory information displayed in the current page
(SOAM information that matches the current context, the quick filtering criteria and search criteria)
to a .tsv file.
■ Export All Pages
This functionality supports exporting the complete SOAM information (SOAM information that
matches the current context) from the database to a .tsv file, irrespective of the filtering criteria or
the search criteria that is active.
■ Close—Click Close to close the SOAM Manager.
■ Help—Click Help to launch context-sensitive help associated with the SOAM Manager.
Customizing SOAM Manager View

The Customize Columns icon in the SOAM Manager is used to select some of the SOAM table attributes
to be displayed in the SOAM table. Additionally, the columns displayed in the SOAM table can be re-
arranged in any order. These settings are saved as part of user preferences.
To customize SOAM Table view in SOAM Manager
Step 1 In the SOAM Manager, click Customize Columns icon.

Note: AID column cannot be removed.
Step 2 Select the columns to be included or excluded in the SOAM Table and move them accordingly to the
Selected Columns and UnSelected Columns area respectively using the Add-> and <-Remove
buttons.
Move Down buttons.
Step 4 Click Apply.
The SOAM Table in the SOAM Manager is refreshed to reflect the customization.
Viewing MD/MA/MEP Properties

The properties of a selected MD/MA/MEP can be viewed from the MD/MA/MEP Properties window.
To launch the MD/MA/MEP Properties

■ In the MD/MA/MEP Table, right-click the MD/MA/MEP and select Properties.
■ In the MD/MA/MEP Table, double-click the MD/MA/MEP.
The MD/MA/MEPProperties is displayed.
The MD/MA/MEP Properties includes these panels and attributes:

6-240 SOAM Manager
■ MD Properties Window—The window includes the following attributes:
Table 6-19 SOAM Manager: MD Properties Window

Attribute Description
General
Node Displays the node name on which the MD is created. This field is read-only.
Name Format Displays the name format of the MD. Valid value is CharString or None.
Note: This field is editable only when there is no MA attached to the MD.
MD Name Displays the assigned name of the MD. The MD name and MA name together forms
a 48- bit MA ID used in CCM messages.
ID Displays the assigned MD ID. This field is read-only.
MD Level Displays the assigned MD level. The valid value is between 0 to 7. This field is read-
only.
Label Displays the optional identifier of the MD.
OAM Entity In Use This field is read-only. When the MAs are attached to MD, the value is shown as
True.
Advanced
Sender ID Permission Displays the selected Sender ID Permission value. This field is read-only.
MHF Creation Criteria Specify if MIPs can be automatically created.
Note: In Release 16.2, this parameter is set to NONE.
■ MA Properties Window—The window includes the following attributes:
Table 6-20 SOAM Manager: MA Properties Window

General
Node Displays the node name on which the MA is created. This field is read-only.
Name Format Displays the name format of MA. The valid value is CharString or None.
Label Displays the optional label for the entity. The valid value is Character string.
MA Name Specifies the name of the MA. The MD name and MA name together forms a 48- bit
MA ID used in CCM messages.

Table 6-20 SOAM Manager: MA Properties Window (continued)

CCM Interval CCM Transmission Interval. The valid value can be one of the following:
□ 3.33MS
□ 10MS
□ 100MS
□ 1S
□ 10S
VLAN ID List of VLAN IDs used for operation administration and maintenance by this MA.
The first entry in this list is used as the Primary VLAN ID. By default, all MEPs
associated with this MA uses Primary VLAN ID for CCM OAM messaging, unless
explicitly overriden at a MEP level to some other VLAN ID from this list. The valid
range is 0 to 4095.
Sender ID Permission Specifies the sender ID TLV. This parameter is set to sendIdNone.
OAM Entity In Use Displays whether the OAM Entity is in use. The valid value is True or False.
Age Out Interval Displays the age out interval for RMEPs. Valid range is 0 to 86400 sec. The default
(seconds) value is 0.
MD
MD Name Displays the name of the MD with which this MA is associated.
■ MEP Properties Window—The window includes the following attributes:
Table 6-21 SOAM Manager: MEP Properties Window

General
Node Displays the node on which the MEP is created. This field is read-only.
MEP ID Displays the assigned MEP ID. The valid value can be between 1 to 8191.
Label Displays the identifier of the MEP.
Direction Displays the MEP direction. The valid value is UP or DOWN.
Administrative State Displays the administartive state of the MEP. The valid value is Locked or Unlocked.
MA
MA Name Specifies the name of the MA. The MD name and MA name together forms a 48- bit
MA ID used in CCM messages.
MD Level Displays the MD Level. The valid value is between 0 to 7.
Interface

6-242 SOAM Manager
Table 6-21 SOAM Manager: MEP Properties Window (continued)

Interface ID Specifies the ID of the associated interface.
Outer VLAN ID Specifies the primary VID of the MEP. The value 0 indicates that the Primary VID is
taken from the MEP's MA. If this parameter is set to non-zero value, it must be part of
the MA’s VlanIdList and that MEP uses that VID for CCM OAM instead of the
PrimaryVID configured in the MEP’s MA. The value of -1 is used for untagged frames
for OAM PDUs if the MA’s primary VID is >0.
MAC Address Specifies the MAC address of the interface to which this MEP it is attached.
Inner VLAN ID Specifies the Inner Primary VID used as the VLAN ID for the inner VLAN tag, when
double tagged CCM PDUs must be generated. If the value is set to 0, then there is no
inner TAG for the CCM OAM PDUs generated.
■ CCM Tab —The tab includes the following attributes:
Table 6-22 MEP Properties: CCM Tab

CCM Enabled Specifies whether CCM Transmit status is Enabled or Disabled.
CCM Role Displays the Fault Monitoring role. This is a read-only attribute.
Drop Eligibility Specifies the drop eligibility indicator (DEI) for CCM PDUs. Valid value is True
or False.
Port Status The Port Stats TLV value set in the CCM PDU of the transmitted CCM frame.
Low Priority Defect Specifies the lowest priority defect.
Interface Status Contains the interface status TLV in last CCM PDU received from the remote
MEP.
CCM Priority Specifies the CCM PDU PCP field value. Valid range is 0 to 7. The default
value is 7.
CFM Actions
RMEP Defect Specifies the action to perform, if the MEP detects loss Of Continuity Check
Message (CCM ) with any of its configured Remote MEP(s).
XCON Defect Specifies the action to perform, if the MEP detects DefXconCCM defect.
CCM Defect Valid value is Notify Defect and Block DataFrames
MAC Status Defect Specifies the action to perform if MEP receives CCM PDUs with port status
blocked in any of the CCM PDU’s port status TLV or detects interface status
down in any of the CCM PDU’s interface status TLV.
■ AIS Tab—The tab includes the following attributes:

Table 6-23 MEP Properties: AIS Tab

AIS Capability Specifies the ETH-Client Signal Failure (AIS) transmission capability of given
MEP.
AIS Settings
Client MD Level Defines the client layer MD level.
Note: This value should be higher than MD level of the domain to which
this MEP belongs to.
Frame Priority Displays the frame priority value. This is a read-only value.
Interval The time interval after which AIS must be sent till the fault is cleared.
Frame Drop Eligibility Specifies if Drop Eligibility Indicator (DEI) is enabled for AIS PDUs.
AIS Frame Tag
Add Click this button to add AIS Frame
Delete Click this button to delete AIS Frame
■ CCM MEP Database Tab—The tab includes the following attributes:
Table 6-24 MEP Properties: CCM MEP Database Tab

RMEP Cross Check Specifies whether the Remote Maintenance End Points (RMEPs) discovered are
verified with the manually provisioned list of the RMEP(s) for unknown MEP.
Create RMEP Click this button to create RMEP.
MEP ID Displays the assigned MEP ID.
MEP State Displays the administrative state of MEP.
RDI Specifies the state of the RDI bit in the last received CCM PDU from the RMEP.
Local MEP ID AID of the Local MEP with which this RMEP is associated with, either through
manual association or discovered association.
Creation Type Displays the creation type of CCM MEP Database
Port Status The Port Stats TLV value set in the CCM PDU of the transmitted CCM frame.
Interface Status Contains the interface status TLV in last CCM PDU received from the remote MEP.
Sender ID Permission Specifies the sender ID TLV. This parameter is set to sendIdNone.
■ ETH-CSF tab : Starting IQ NOS R16.2, Ethernet CSF messaging is introduced on OAM MEP. CSF
Messaging is applicable only on EP Line EVCs (i.e. port based E-Line services) on an IQ NOS
R16.2 network element, where both associated Attachment Circuits have ingress Match Type as

6-244 SOAM Manager
MatchIntf. Creating or updating ETH CSF attributes is supported only on UP MEPs associated with
the EP Line service. The attributes displayed in the ETH-CSF tab are described below
Table 6-25 MEP Properties: ETH CSF Tab

ETH-CSF Support Indicates the Ethernet Client Signal Failure transmission capability of given
MEP. Supported values include:
□ Enabled - Ethernet CSF messaging is enabled
□ Disabled - Ethernet CSF messaging is not enabled
Note: CSF attributes can be edited only when ETH-CSF

Support is set to Enabled.
Frame Priority Displays the frame priority value. The supported range of values is from 0
through 7.
Default Value : 7
Interval The time interval after which CSF must be sent till the fault is cleared.
Supported values include:
□ 1 sec (Default value)
□ 1 min
Drop Eligibility Specifies if Drop Eligibility Indicator is enabled for ETH CSF PDUs.
■ Diagnostics Tab: Includes the following attributes
Table 6-26 MEP Properties: Diagnostics Tab

Enable PM Collection Check-box to enable the PM collection.
■ Real Time PM Tab: The Real Time PM tab displays the real time performance statistics. For a
description of the Real Time PM attributes, refer to the DNA Performance Management Guide.
■ 15 Minute History: The 15Min History tab displays the performance statistics for 15 minute
intervals. For a description of the attributes, refer to the DNA Performance Management Guide.
■ 24 Hour History: The 24 Hour History tab displays the performance statistics for 24 Hour intervals.
For a description of the attributes, refer to the DNA Performance Management Guide.
■ PM Chart: For a description of the attributes, refer to the DNA Performance Management Guide.
Creating Maintenanace Domain

Maintenance Domain (MD) is defined as a sub-network over which a given EVC is monitored and are
defined by operational/contractual boundaries.
MD can be created using the Create Maintenanace Domain window.

To create Maintenanace Domain

Step 1 Launch the SOAM Manager. See Launching the SOAM Manager on page 6-234 for various options to
launch the SOAM Manager.
Step 2 Click on the New button in the MD tab under the SOAM Manager. The Create Maintenanace Domain
Step 3 Click ... next to the Node field to select the nodes from the Select Node window. Select the desired
node from the list and click Ok or double-click the desired node to return to the Home screen.
Step 4 The ID field is auto-populated based on the selected node.
Step 5 Select the Name Format from the Name Format drop-down menu. The valid values is None or
CharString.
Step 6 Enter a label for the MD. This attribute is optional.
Step 7 Enter the name of the MD in the MD Name field.
Step 8 Select the MD Level from the MD Level drop-down menu. The valid value is between 0 to 7.
Step 9 Click Create.
A prompt with the message indicating that the MD creation is Successful is displayed.
To create MD on Multiple Nodes
Step 2 Click on the New button in the MD tab under the SOAM Manager.
The Create Maintenance Domain window is displayed.
Step 3 Click on the Create on Multiple Nodes button.
The Create Maintenance Domain on Multiple Nodes window is displayed.
Step 4 Select the Name Format from the Name Format drop-down menu. The valid value is CharString or
None.
Step 6 Enter a label for the MD. This is an optional attribute.
Step 7 Select the MD Level from the MD Level drop-down menu. The valid value is between 0 to 7.
Step 8 Under the Target nodes to Apply panel, select the check-box against the listed nodes on which MD
needs to be created. Click Select All to select all the listed nodes. Click UnSelect All to unselect all the
listed nodes.
Step 9 Click on the Validate button to validate that the selected nodes does not have a MD with the given
name and Level.
The nodes which already have a MD with the given name and level cannot be selected.

6-246 SOAM Manager

The Bulk Configuration Status panel displays the status of the creation operation. The Status column
displays whether the MD creation on a particular node is Successful or not. In case of a failure, the
reason is shown in the Failure Reason column.
To Apply MD on Multiple Nodes
Step 2 Double-click or right-click and select Properties on an existing MD listed in the MD tab under the
SOAM Manager.
The MD Properties window is displayed.
Step 3 Click on the Apply to Multiple Nodes button.
The Apply Maintenance Domain on Multiple Nodes window is displayed.
Step 4 Select the Name Format from the Name Format drop-down menu. The valid value is CharString or
None.
The Node attribute is read-only.
Step 6 Enter a label for the MD. This is an optional attribute.
The MD Level attribute is read-only. The valid value is between 0 to 7.
Step 7 Under the Target nodes to Apply panel, select the check-box against the listed nodes on which MD
needs to be created. Click Select All to select all the listed nodes. Click UnSelect All to unselect all the
listed nodes.
Step 8 Click on the Validate button to validate that the selected nodes does not have a MD with the given
name and Level.
The nodes which already have a MD with the given name and level cannot be selected.
displays whether the MD creation on a particular node is Successful or not. In case of a failure, the
Creating Maintenanace Association

Maintenance Association (MA) is defined as a service monitoring session between two MEPs with in a
domain.
MA can be created using the Create Maintenanace Association window.
To create Maintenanace Association


Step 2 Click on New button in the MA tab under the SOAM Manager. The Create Maintenanace Association
Step 4 Click ... next to the MD Name field to select the nodes from the Select Maintenanace Domain window.
Select the desired node from the list and click Ok or double-click the desired node to return to the
Home screen.
Step 5 The ID field is auto-populated based on the selected MD.
Step 6 The Name Format is auto-populated based on the selected MD. The valid value is None or
CharString.
Step 7 Enter a label for the MD.
Step 9 The MD Level is auto-populated based on the selected MD. The valid value is between 0 to 7.
Step 10 Enter the VLAN ID. The valid range is between 0 to 4095.
Step 11 Select the CCM Interval from the CCM Interval drop-down menu.
Step 12 Enter the Age Out Interval in seconds.
A prompt with the message indicating that the MA creation is Successful is displayed.
To create MA on Multiple Nodes
Step 2 Click on the New button in the MA tab under the SOAM Manager.
The Create Maintenance Association window is displayed.
The Create Maintenance Association on Service Nodes window is displayed.
Step 4 Under the General Panel, click ... next to the Node field to select the nodes from the Select Node
window. Select the desired node from the list and click Ok or double-click the desired node to return to
the Home screen.
Step 5 Click ... next to the MD Name field to select the nodes from the Select Maintenanace Domain window.
Select the desired node from the list and click Ok or double-click the desired node to return to the
Home screen.
Step 6 The Name Format is auto-populated based on the selected MD. The valid value is None or
CharString.
Step 7 Enter a label for the MD.
Step 8 Enter the name of the MA in the MA Name field.

6-248 SOAM Manager
Step 9 The MD Level is auto-populated based on the selected MD. The valid value is between 0 to 7.
Step 10 Enter the VLAN ID. The valid range is between 0 to 4095.
Step 11 Under the AdvancedPanel, select the CCM Interval from the CCM Interval drop-down menu.
Step 13 Under the Target nodes to Apply panel, click ... next to the Node field to select the nodes from the
Select Node window. Select the desired node from the list and click Ok or double-click the desired
node to return to the Home screen.
Step 14 Click ... next to the Select EVC field to select the EVC from the Select EVC window.
Step 15 Select the check-box against the listed nodes on which MA needs to be created. Click Select All to
select all the listed nodes. Click UnSelect All to unselect all the listed nodes.
Step 16 Click on the Validate button to verify whether selected MD and MA exists on the selected nodes or not.
MD name should be unique in the node and MA name should be unique with in a MD. These names
are used to verify the existence of MD and MA during validation.
displays whether the MA creation on a particular node is Successful or not. In case of a failure, the
To Apply MA on Multiple Nodes
Step 2 Double-click or right-click and select Properties on an existing MEP listed in the MA tab under the
SOAM Manager.
The MA Properties window is displayed.
The Apply Maintenance Association on Service Nodes window is displayed.
Step 4 Under the General panel, enter a Label for the MA.
All other attributes under the General panel are read-only.
Step 8 Select the check-box against the listed nodes on which MA needs to be created. Click Select All to

Step 9 Click on the Validate button to verify whether selected MD and MA exists on the selected nodes or not.
MD name should be unique in the node and MA name should be unique with in a MD. These names
are used to verify the existence of MD and MA during validation.
displays whether the MA creation on a particular node is Successful or not. In case of a failure, the
Creating Maintenance End Point

Maintenance End Point (MEP) is an end point of a MA and also defines the boundary of the MD for a
given ethernet service.
MEP can be created using the Create Maintenance End Point window.
To create Maintenance End Point

Step 2 Click on the New button in the MEP tab under the SOAM manager. The Create Maintenance End
Point window is displayed.
Step 4 Click ... next to the MA Name field to select the nodes from the Select Maintenanace Association
window. Select from the list and click Ok or double-click to return to the Home screen.
Step 5 Depending upon the MA selection, the MD Level is auto-selected.
Step 6 Select the Direction from the Direction drop-down menu.
Step 7 MEP ID field is auto-defined based on the MA selection. Optionally, user can also define the value of
the the MEP ID.
Note: All MEPs under one MA should be either UP MEPs or Down MEPs.
Step 8 From the Interface Type drop-down menu,select AC (Service OAM) or Ethernet Interface (Link OAM).
Step 9 Click ... next to the Interface ID field to select the interface. Interface ID Selection window lists the
entries depending upon the selected Interface type.
Note: Based on the selected AC, the Outer VLAN ID and Inner VLAN ID fields will be enabled. If
the selected AC match criteria is MathcIntfOuterVlan then only Outer VLAN ID is required for the
MEP. In case it is MathcIntfOuterVlanInnerVlan then both Outer and Inner VLAN ID fields gets
enabled.
Step 10 Under the CCM tab, CCM related attributes needs to be defined to create the MEP. For the description
and values of the attributes, refer to the Table 6-22: MEP Properties: CCM Tab on page 6-242
Step 11 Under the AIS tab, AIS related attributes needs to be defined to create the MEP. For the description
and values of the attributes, refer to the Table 6-23: MEP Properties: AIS Tab on page 6-243

6-250 SOAM Manager
Step 12 Under the CCM MEP Database tab, CCM MEP Database related attributes needs to be defined to
create the MEP. For the description and values of the attributes, refer to the Table 6-24: MEP
Properties: CCM MEP Database Tab on page 6-243
Note: Only the fields which are enabled can be edited.
Step 13 Under the ETH-CSF tab, CSF transmission related attributes needs to be defined to create the MEP.
For the description and values of the attributes, refer to the Table 6-25: MEP Properties: ETH CSF
Tab on page 6-244
Note: Creating or updating ETH CSF attributes is supported only on UP MEPs associated with the
EP Line service and when the selected Attachment Circuit has ingress Match Type as MatchIntf.
Ensure that the selected Node is running IQ NOS R16.2
Step 14 Click Create to create the MEP.

A prompt with the message indicating that the MEP creation is Successful is displayed.
To create MEP on Multiple Nodes
Step 2 Click on the New button in the MEP tab under the SOAM Manager.
The Create Maintenance End Point window is displayed.
The Create Maintenance End Point on Service Nodes window is displayed.
Step 5 Click ... next to the MA Name field to select the nodes from the Select Maintenanace Association
window. Select from the list and click Ok or double-click to return to the Home screen.
Step 6 Depending upon the MA selection, the MD Level is auto-selected.
Step 7 Select the Direction from the Direction drop-down menu.
Step 8 MEP ID field is auto-defined based on the MA selection. Optionally, user can also define the value of
the the MEP ID.
Note: All MEPs under one MA should be either UP MEPs or Down MEPs.
Step 9 From the Interface Type drop-down menu,select AC (Service OAM) or Ethernet Interface (Link OAM).
Step 10 Click ... next to the Interface ID field to select the interface. Interface ID Selection window lists the
entries depending upon the selected Interface type.
Note: Based on the selected AC, the Outer VLAN ID and Inner VLAN ID fields will be enabled. If
the selected AC match criteria is MathcIntfOuterVlan then only Outer VLAN ID is required for the
MEP. In case it is MathcIntfOuterVlanInnerVlan then both Outer and Inner VLAN ID fields gets
enabled.

and values of the attributes, refer to the CCM Tab section.
and values of the attributes, refer to the AIS Tab Section.
create the MEP. For the description and values of the attributes, refer to the CCM Tab Database
Section .
Note: Only the fields which are enabled can be edit.
For the description and values of the attributes, refer to the ETH-CSF Tab Section .
Note: ETH-CSF tab is enabled for edit only when EP Line EVC is selected and the associated ACs
have ingress Match Type as MatchIntf and are running IQ NOS R16.2. Creating or updating ETH
CSF attributes is supported only on UP MEPs associated with the EP Line service.
Step 17 Select the check-box against the listed nodes on which MEP needs to be created. Click Select All to
Step 18 Click on the Validate button to validate that the selected nodes does not have a MD, MA and MEP with
the given name and Level.
The nodes which already have a MEP with the given name and level cannot be selected.
displays whether the MEP creation on a particular node is Successful or not. In case of a failure, the
To Apply MEP on Multiple Nodes
Step 2 Double-click or right-click and select Properties on an existing MEP listed in the MEP tab under the
SOAM Manager.
The MEP Properties window is displayed.
The Apply Maintenance End Point on Service Nodes window is displayed.
Step 4 Under the General tab, edit the Label.

6-252 SOAM Manager
and values of the attributes, refer to the CCM Tab section.
and values of the attributes, refer to the AIS Tab Section.
create the MEP. For the description and values of the attributes, refer to the CCM Tab Database
Section .
Note: Only the fields which are enabled can be edit.
For the description and values of the attributes, refer to the ETH-CSF Tab Section .
Note: ETH-CSF tab is enabled for edit only when EP Line EVC is selected and the associated ACs
have ingress Match Type as MatchIntf and are running IQ NOS R16.2. Creating or updating ETH
CSF attributes is supported only on UP MEPs associated with the EP Line service.
Step 11 Select the check-box against the listed nodes on which MEP needs to be created. Click Select All to
Step 12 Click on the Validate button to validate that the selected nodes does not have a MD, MA and MEP with
the given name and Level.
The nodes which already have a MEP with the given name and level cannot be selected.
displays whether the MEP creation on a particular node is Successful or not. In case of a failure, the
Creating RMEP ( Remote Maintenance EndPoint )
Step 1 Launch the MEP Properties window. For details to launch MEP Properties window, refer to Viewing
MD/MA/MEP Properties on page 6-239.
Step 2 Click Create RMEP. The Create RMEP window is displayed.
Step 3 Enter the RMEP ID.
Step 4 Optionally, provide a label for the RMEP.

CHAPTER 7
DNA Server Alarms
The DNA server generates alarms indicating the failure condition so that users can take corrective
actions. The alarms generated by the DNA server are displayed in the Alarm Manager window in which
the network element generated alarms are displayed. Refer to the DNA Fault Management and
Diagnostics Guidefor procedures to use the Alarm Manager. The DNA server generated alarms include:
■ The alarms caused by the DNA server to network element connectivity problems. These alarms are
categorized as unreachable alarms. See DNA Server Unreachable Alarms on page 7-2.
■ The alarms related to the DNA server performance. See DNA Server Performance Alarms on page
7-11.
■ The alarms related to DNA security. See DNA Security Alarm on page 7-14.
■ The alarms related to DNA Fiber Alarms. See Fiber Alarm on page 7-15
■ The alarms related to DNA DNA-M Alarms. See DNA-M Alarm on page 7-16

7-2 DNA Server Unreachable Alarms
DNA Server Unreachable Alarms

The DNA server reports the alarms listed in Table 7-1: DNA Server Unreachable Alarms on page 7-2
when it is unable to establish connectivity to the network element. In the table,
■ <DNA server account> refers to the login name used by the DNA server to log into the network
element.
■ <Network Element ID> refers to the network element the DNA is attempting to connect.
Table 7-1 DNA Server Unreachable Alarms

Redundant path from Server to <Network Element ID> not found on page -3
<Network Element ID> is in Errored state. Please contact System Administrator on page -3
<Network Element ID> is in Errored State as EMS queue overflowed on page -3
<Network Element ID> is in Errored state as overflow event got detected during deep discovery on page -4
<Network Element ID> is in Errored State. Detected Loss of Events: Resynchronization initiated on page -4
<DNA server account> on <Network Element ID> does not have all security privileges on page -6
<DNA server account> on <Network Element ID> no longer has all security privileges - terminating Server
connection to the NE on page -6
All Server login attempts to <Network Element ID> failed - update key ring with correct user name/passwords on
page -6
Server login attempt to <Network Element ID> failed - maximum sessions limit reached on page -7
<Network Element ID> unreachable - check connectivity from Server on page -7
Server failed to retrieve XML agent version from <Network Element ID> on page -7
Incompatible Server and NE versions - cannot manage <Network Element ID> on page -8
Minor Server and NE Version mismatch - some functionality may not be available on page -8
Server Lost connection to <Network Element ID> on page -8
Server cannot use <DNA server account> on <Network Element ID> - change password on the NE and then update
the key ring on page -9
Server login attempt to <Network Element ID> failed - <Error Message> on page -9
<Network Element User Account Name> on <Network Element ID> has inactivity timeout enabled, EMS cannot use
this account on page -9
Host Key Verification Failed on Network Element <Network Element IP Address> on page -9
Discovery key ring is either empty or corrupt - reconfigure the key ring on page -10

DNA Server Alarms 7-3
EMS0001
Redundant path from Server to <Network Element ID> not found
■ Severity - Minor
Description and Causes

This alarm takes a maximum of one hour to be generated when the DNA server does not detect an
alternate DCN connectivity to the network element. (DNA does not connect; it just pings using the
secondary path).
Clearing Procedure
■ Verify the DCN configuration in the network element and the DNA server
■ Verify the DCN network configuration has at least two GNEs in a signaling domain.
EMS0002
■ “<Network Element ID> is in Errored state. Please contact System Administrator“
■ “<Network Element ID> is in Errored State as EMS queue overflowed“
■ “<Network Element ID> is in Errored state as overflow event got detected during deep discovery“
■ “<Network Element ID> is in Errored State. Detected Loss of Events: Resynchronization initiated“
<Network Element ID> is in Errored state. Please contact System Administrator

■ Severity - Warning

This alarm is generated when DNA server cannot discover the network element due to some failure such
as database operation failure. Under such a circumstance, the DNA will back off for 5 minutes. During this
5 minute period the color of the network element icon in the physical and provisioning views of the DNA is
turquoise. At the end of 5 minutes, the DNA attempts to synchronize with the network element.
Clearing Procedure
■ Wait for at least 5 minutes till the DNA starts synchronizing with the network element.
■ If the alarm still persists after waiting for 5 minutes collect all logs in the directory
<DNA_Home>/EMS/logs where <DNA_Home> is the installed directory of DNA server and contact
the System Administrator.
<Network Element ID> is in Errored State as EMS queue overflowed



This alarm is generated when the DNA is in the process of deep discovery of a network element and it
receives more that 300 events from the network element resulting in the EMS queue to overflow. Under
such a circumstance, DNA backs off for 90 seconds for the network element. During this 90 second
period there will be no exchange of data between the DNA and network element and no operation can be
performed on the network element. During this 90 second period the color of the network element icon in
the physical and provisioning views of the DNA is turquoise. At the end of 90 seconds, DNA attempts to
synchronize with the network element.
Clearing Procedure
■ Wait for at least three minutes till the DNA starts synchronizing with the network element.
■ If the alarm still persists after waiting for three minutes, collect all logs in the directory
<Network Element ID> is in Errored state as overflow event got detected during deep discovery

This alarm is generated when the DNA server is in the process of synchronizing with the network element
and detects the overflow event. Under such a circumstance, DNA backs off for 90 seconds for the
network element. During this 90 second period there will be no exchange of data between the DNA and
network element and no operation can be performed on the network element. During this 90 second
period the color of the network element icon in the physical and provisioning views of the DNA is
turquoise. At the end of 90 seconds, DNA attempts to synchronize with the network element.
Clearing Procedure
■ If the alarm still persists after waiting for three minutes, collect all logs in the directory
<Network Element ID> is in Errored State. Detected Loss of Events: Resynchronization initiated

This alarm is generated when DNA server detects packet loss with the network element due to some
network problems. Under such a circumstance, DNA backs off for 90 seconds for the network element.
During this 90 second period there will be no exchange of data between the DNA and network element
and no operation can be performed on the network element. During this 90 second period the color of the
network element icon in the physical and provisioning views of the DNA is turquoise. At the end of 90
seconds, DNA attempts to synchronize with the network element.

Clearing Procedure
■ If the alarm persists after waiting for three minutes, collect all logs in the directory
<Network Element ID> is in Errored State. Buffer Overflow


This alarm is generated when DNA server receives an overflow event from the network element. Under
such a circumstance, DNA backs off for 90 seconds for the network element. During this 90 second
period there will be no exchange of data between the DNA and network element and no operation can be
performed on the network element. During this 90 second period the color of the network element icon in
the physical and provisioning views of the DNA is turquoise. At the end of 90 seconds, DNA attempts to
synchronize with the network element.
Clearing Procedure
■ If the alarm persists after waiting for three minutes, collect all logs in the directory
EMS0009
■ “<DNA server account> on <Network Element ID> does not have all security privileges“
■ “<DNA server account> on <Network Element ID> no longer has all security privileges - terminating
Server connection to the NE“
■ “All Server login attempts to <Network Element ID> failed - update key ring with correct user name/
passwords“
■ “Server login attempt to <Network Element ID> failed - maximum sessions limit reached“
■ “<Network Element ID> unreachable - check connectivity from Server“
■ “Server failed to retrieve XML agent version from <Network Element ID>“
■ “Incompatible Server and NE versions - cannot manage <Network Element ID>“
■ “Minor Server and NE Version mismatch - some functionality may not be available“
■ “Server Lost connection to <Network Element ID>“
■ “Server cannot use <DNA server account> on <Network Element ID> - change password on the
NE and then update the key ring“

■ “Server login attempt to <Network Element ID> failed - <Error Message>“

■ “<Network Element User Account Name> on <Network Element ID> has inactivity timeout enabled,
EMS cannot use this account“
■ “Host Key Verification Failed on Network Element <Network Element IP Address>“
<DNA server account> on <Network Element ID> does not have all security privileges
■ Severity - Unreachable

This alarm indicates that the DNA server cannot connect to the specified network element using the
specified DNA server account because the account does not have all access privileges.
Clearing Procedure
■ On the network element enable all access privileges for the specified DNA server account.
■ Delete this account in the DNA server discovery key ring. However, ensure that there is one DNA
server account created on the network element and also configured in the DNA server discovery
key ring so that DNA server can connect to the network element.
<DNA server account> on <Network Element ID> no longer has all security privileges - terminating Server
connection to the NE

This alarm indicates that the DNA server cannot reconnect to the specified network element using the
specified DNA server account because the account does not have all access privileges which was
previously enabled. It is most likely caused by a user changing the access privileges of this account.
Clearing Procedure
■ On the network element enable all access privileges for the specified DNA server account
■ Delete this account in the DNA server discovery key ring. However, ensure that there is one DNA
server account created on the network element and also configured in the DNA server discovery
key ring so that DNA server can connect to the network element.
All Server login attempts to <Network Element ID> failed - update key ring with correct user name/
passwords

This alarm is generated after DNA server has tried all the DNA server accounts specified in the key ring to
connect to the network element, but did not succeed. It is caused by the incompatibility between the DNA

server account information configured in the nework element and the information specified in the
discovery key ring.
Clearing Procedure
■ Update the key ring with the correct DNA server account name and password which is configured
in the network element.
■ Fix the DNA server account name and password in the network element to match the one specified
in the key ring.
Server login attempt to <Network Element ID> failed - maximum sessions limit reached

This alarm is generated when DNA server cannot log into the network element because the maximum
active sessions allowed on the network element has exceeded.
Clearing Procedure
■ Log into the nework element with the security administrator privilege and forcefully terminate one of
the active sessions.
<Network Element ID> unreachable - check connectivity from Server


This alarm is generated only when the DNA server fails to connect to the network element using the
primary DCN path.
Clearing Procedure
■ Verify the DCN configuration in the network element and the DNA server
■ Verify the DCN network configuration.
Server failed to retrieve XML agent version from <Network Element ID>

This alarm is generated when the DNA server cannot retrieve the XML agent version running on the
network element. This alarm occurs when the network element is not responding to the DNA server.
Clearing Procedure
■ Check the status of the network element and make sure that it is in normal state.

Incompatible Server and NE versions - cannot manage <Network Element ID>


This alarm is generated when the DNA server version is not compatible with the network element
software version. The DNA server cannot be used to manage this network element. For the list of
compatible DNA server and network element software versions, refer to the
Clearing Procedure
■ Upgrade the software image on the network element to be compatible with the DNA server version.
■ Upgrade the DNA server version to be compatible with the network element software version.
Minor Server and NE Version mismatch - some functionality may not be available

This alarm is generated when the DNA server minor version is not compatible with the network element
software minor version. The DNA server can be used to manage the network element, however some
functions may not be available.
Clearing Procedure
■ Contact Infinera Technical Support for the list of compatible DNA server and network element
software minor versions. Upgrade the DNA software or the network element software to ensure the
compatibility.
Server Lost connection to <Network Element ID>


This alarm is generated when DNA server loses connection to the specified network element. It could be
caused by any of the following reasons:
■ The network element is reset or unavailable
■ There is a problem in the connectivity (customer network) between the DNA server and the network
element.
Clearing Procedure
■ Ensure that the network element is available. Troubleshoot and fix problems in the network
connectivity.

Server cannot use <DNA server account> on <Network Element ID> - change password on the NE and
then update the key ring

This alarm is generated when the DNA server account password has expired on the network element and
DNA server cannot log into the network element.
Clearing Procedure
■ Log into the network element and disable the password expiration for this DNA server account.
Server login attempt to <Network Element ID> failed - <Error Message>


This alarm is generated when DNA server cannot log into the network element. The <Error Message>
describes the reason for the failure.
Clearing Procedure
■ Ensure that the DNA server account is properly configured in the network element and the DNA
discovery key ring.
<Network Element User Account Name> on <Network Element ID> has inactivity timeout enabled, EMS
cannot use this account

This alarm is generated when the DNA server cannot log into the network element because the user
account specified in the key ring to connect to the DNA server has inactivity time enabled.
Clearing Procedure
Any one of the following:
■ Do not specify this user account in the key ring to connect the DNA server to the network element.
■ Disable inactivity time out for the user account specified in the key ring to connect the DNA server
to the network element.
Host Key Verification Failed on Network Element <Network Element IP Address>



This alarm is generated when the Host Key Validation that is performed at the beginning of each
connection for the network element fails.
Clearing Procedure
■ Ensure the host key is updated and the path to the host key is correct. Refer to DNA Administrator
Guide for the detailed procedure.
EMS0010
Discovery key ring is either empty or corrupt - reconfigure the key ring
■ Severity - Critical

This alarm is generated when the discovery key ring is empty or corrupt.
Clearing Procedure
■ Configure the key ring correctly.

DNA Server Performance Alarms

DNA server monitors the resource utilization on the workstation on which it is run (referred to as DNA
server workstation). When resources are utilized beyond predetermined thresholds, the alarms are
reported so that users can take corrective actions.
Note: These alarms are displayed in the Alarm Manager only if the user has SA privileges.
Table 7-2 DNA Server Performance Alarms

CPU usage of EMS Server: <% Used> on page -11
Disk usage of EMS Server: <% Used> on page -12
CPU usage of EMS Server High: <% Used> on page -11
Disk usage of EMS Server High: <% Used> on page -12
Memory Usage of EMS Server: <-% Used> on page -12
Memory Usage of EMS Server High: <-% Used> on page -13
EMS0003
CPU usage of EMS Server High: <% Used>
■ Severity - Major

This alarm is generated when the CPU usage on the DNA server workstation exceeds 95%. The <%
Used> indicates the current CPU usage.
Clearing Procedure
Contact your System Administrator to manage the applications run on the DNA server workstation.
EMS0004
CPU usage of EMS Server: <% Used>

This alarm is generated when the CPU usage on the DNA server workstation exceeds 80%. The <%
Used> indicates the current CPU usage.

7-12 DNA Server Performance Alarms
Clearing Procedure
Contact your System Administrator to manage the applications run on the DNA server workstation.
EMS0005
Disk usage of EMS Server High: <% Used>

This alarm is generated when the disk usage on the DNA server workstation exceeds 95%. The <%
Used> indicates the current disk usage.
Clearing Procedure
Perform the following actions:
■ Back up the DNA server database.
■ Upgrade the hard disk.
EMS0006
Disk usage of EMS Server: <% Used>

This alarm is generated when the disk usage on the DNA server workstation exceeds 80%. The <%
Used> indicates the current disk usage.
Clearing Procedure
Perform the following actions:
■ Back up the DNA server database.
■ Delete unwanted files, temp directory and logs in the DNA server workstation.
■ If alarm persists, upgrade the hard disk.
EMS0007
Memory Usage of EMS Server: <-% Used>


This alarm is generated when the memory usage on the DNA server workstation exceeds 80%. The <%
Used> indicates the current memory usage.
Clearing Procedure
Increase the memory size of the DNA server workstation.
EMS0008
Memory Usage of EMS Server High: <-% Used>

This alarm is generated when the memory usage on the DNA server workstation exceeds 95%. The <%
Used> indicates the current memory usage.
Clearing Procedure
Increase the memory size of the DNA server workstation.

7-14 DNA Security Alarm
DNA Security Alarm

The following section describes the DNA Security Alarm.
Table 7-3 DNA Security Alarm

Maximum allowed invalid Login attempt is reached on page -14
EMS0011
Maximum allowed invalid Login attempt is reached
■ Severity - Warning (User configurable)
This alarm is raised when the number of unsuccessful attempts exceeds the system configured
value for maximum invalid login attempts. The account is locked for the time period as set by the
administrator. This alarm is visible in the Alarm Manager only during this time period.
Clearing Procedure
This alarm is automatically cleared in one of the following scenarios:
■ A successful login after the lockout interval
■ If the DNA user account is deleted
■ The temporary lockout is removed for the DNA user account
■ Change the Account Status Disabled
Note: This alarm is displayed in the Alarm Manager only if the user has SA privileges.

Fiber Alarm
The following section describes the Fiber Alarm. See:
Optical Loss of Signal on page -15
EMS0012
Optical Loss of Signal
■ Severity - Severity of this alarm is same as the highest severity of all the individual end point (TRIB/
OTS) OLOS alarms.
This alarm is aggregation of the individual OLOS alarm conditions present on Link End points (For
Control Link end point corresponding to OTSPTP and B2B Link end points are TRIBPTP).
Clearing Procedure
This alarm is automatically cleared if the underlying OTS/TRIB OLOS alarms are cleared.

7-16 DNA-M Alarm
DNA-M Alarm
The following section describes the Fiber Alarm. See EMS0013 on page 7-16
EMS0013
DNA-M Connection Loss
■ Severity - Critical

This alarm is generated when:
■ DNA-M is unreachable
■ login to DNA-M is invalid
■ DNA-M heartbeat is failed
Clearing Procedure
■ This alarm is automatically cleared when:
□ DNA-M server is reachable
□ correct login credentials are provided
□ DNA-M gets back the heartbeat

R19.0 DNA Fault Management and Diagnostics Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

R19.0 DNA Fault Management and Diagnostics Guide

Uploaded by

Copyright:

Available Formats

Infinera DNA

Fault Management and Diagnostics

Chapter 1: Fault Management...................................................................................................................1-1

Chapter 2: Environmental Alarms and Control.......................................................................................... 2-1

Chapter 3: DTN/DTN-X/FlexROADM Diagnostics.....................................................................................3-1

Chapter 4: ATN Diagnostics...................................................................................................................... 4-1

Infinera Corporation Fault Management and Diagnostics Guide Release 19.0 V002

Infinera Proprietary and Confidential

PRBS Tests in ATNs...........................................................................................................................................4-32

Chapter 5: Cloud Xpress and XT Diagnostics........................................................................................... 5-1

Chapter 6: Diagnostics Applications.......................................................................................................... 6-1

Chapter 7: DNA Server Alarms..................................................................................................................7-1

Fault Management and Diagnostics Guide Release 19.0 V002 Infinera Corporation

Infinera Proprietary and Confidential

Infinera Corporation Fault Management and Diagnostics Guide Release 19.0 V002

Infinera Proprietary and Confidential

Fault Management and Diagnostics Guide Release 19.0 V002 Infinera Corporation

Infinera Proprietary and Confidential

Infinera Corporation Fault Management and Diagnostics Guide Release 19.0 V002

Infinera Proprietary and Confidential

Fault Management and Diagnostics Guide Release 19.0 V002 Infinera Corporation

Infinera Proprietary and Confidential

Infinera Corporation Fault Management and Diagnostics Guide Release 19.0 V002

Infinera Proprietary and Confidential

Fault Management and Diagnostics Guide Release 19.0 V002 Infinera Corporation

Infinera Proprietary and Confidential

Infinera Corporation Fault Management and Diagnostics Guide Release 19.0 V002

Infinera Proprietary and Confidential

Fault Management and Diagnostics Guide Release 19.0 V002 Infinera Corporation

Infinera Proprietary and Confidential

Infinera Corporation Fault Management and Diagnostics Guide Release 19.0 V002

Infinera Proprietary and Confidential

Fault Management and Diagnostics Guide Release 19.0 V002 Infinera Corporation

Infinera Proprietary and Confidential

Infinera Corporation Fault Management and Diagnostics Guide Release 19.0 V002

Infinera Proprietary and Confidential

Chapter Number: Title Description

Documents for Release 19.0

Document Name Document ID Description

Fault Management and Diagnostics Guide Release 19.0 V002 Infinera Corporation

Infinera Proprietary and Confidential

Document Name Document ID Description

Document Revision History

Infinera Corporation Fault Management and Diagnostics Guide Release 19.0 V002

Infinera Proprietary and Confidential

Document Version Document Updates Since Previous Revision

Convention Item Example

courier font User-entered text In the Label enter EastBMM

Note: If the directory path or

Fault Management and Diagnostics Guide Release 19.0 V002 Infinera Corporation

Infinera Proprietary and Confidential

Infinera Corporation Fault Management and Diagnostics Guide Release 19.0 V002

Infinera Proprietary and Confidential

Fault Management and Diagnostics Guide Release 19.0 V002 Infinera Corporation

Infinera Proprietary and Confidential

Note: Multi-chassis configurations for Cloud Xpress are not supported.

Infinera Corporation Fault Management and Diagnostics Guide Release 19.0 V002

Infinera Proprietary and Confidential

Figure 1-1 Events and Notifications

Fault Management and Diagnostics Guide Release 19.0 V002 Infinera Corporation

Infinera Proprietary and Confidential

Figure 1-2 Node/Admin Domain Tool-tip Details

Infinera Corporation Fault Management and Diagnostics Guide Release 19.0 V002

Infinera Proprietary and Confidential