Release 2.0
Version 003 Document ID 1900-593
Copyright
Copyright 2011 Infinera Corporation. All rights reserved. This Manual is the property of Infinera Corporation and is confidential. No part of this Manual may be reproduced for any purposes or transmitted in any form to any third party without the express written consent of Infinera. Infinera makes no warranties or representations, expressed or implied, of any kind relative to the information or any portion thereof contained in this Manual or its adaptation or use, and assumes no responsibility or liability of any kind, including, but not limited to, indirect, special, consequential or incidental damages, (1) for any errors or inaccuracies contained in the information or (2) arising from the adaptation or use of the information or any portion thereof including any application of software referenced or utilized in the Manual. The information in this Manual is subject to change without notice.
Trademarks
Infinera, Infinera Digital Optical Networks, I-PIC, IQ, DTN, ATN and logos that contain Infinera are trademarks or registered trademarks of Infinera Corporation in the United States and other countries. All other trademarks in this Manual are the property of their respective owners.
Infinera ATN, DTN and Infinera Optical Line Amplifier 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 numrique respecte les limites de bruits radiolectriques applicables aux appareils numriques de Classe A prescrites dans la norme sur le matriel brouilleur: "Appareils Numriques," NMB-003 dicte par le Ministre des Communications.
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 21 CFR Subchapter J, Section 1040.10, Applicable at date of manufacture.
Contents
About this Document
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Documents for Release 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Document Revision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Technical Assistance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Infinera Digital Optical Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Infinera ATN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Infinera Dispersion Management Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Infinera DTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Infinera Optical Line Amplifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 1-2 1-3 1-3 1-3
IQA Networking Operating System ATN Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Infinera Management Suite (IMS) Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Release 2.0 Feature Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 ATN Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 ATN Terminal Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 ATN Add/Drop Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Network Topologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Point-to-Point Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linear Add/Drop Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ring Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 2-4 2-4 2-5
Infinera Corporation
Release 2.0
Page ii
Contents
ATN Hardware Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATN Transport Chassis (ATC-A) Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATC Transport Chassis-Passive (ATC-P) Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit Packs for the ATC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dispersion Management Chassis (DMC) Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30 Dispersion Compensation Module (DCM) Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31 System Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transport Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multi-chassis Interconnect Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input/Output Alarm Contacts and Relays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Data Plane Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optical Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Data Plane Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Plane Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Control Plane Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-chassis Control Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-chassis Control Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-node Control Plane (over OSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32 3-32 3-33 3-35 3-36 3-37 3-38 3-38 3-42 3-45 3-47 3-48 3-48 3-49 3-51
System Management Plane Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52 Multi-Chassis Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53 Multi-Chassis Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53 ATN Site Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATN Terminal Site Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATN Add/Drop Site Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATN Amplifier Only Site Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATN Regeneration Site Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59 3-59 3-60 3-60 3-61
Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Alarm Surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 Maintenance and Troubleshooting Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 Equipment Management and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managed Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Discovery and Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . State Modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tributary Disable Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30 4-30 4-31 4-33 4-34 4-39
Performance Monitoring and Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41 PM Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42 Security and Access Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Infinera Corporation
Contents
Page iii
Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Secure Shell (SSHv2) and Secure FTP (SFTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Authentication Dial-In User Service (RADIUS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintaining Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintaining the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uploading Debug Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ADAPT Power Management Control Plane Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optical Power Management using ADAPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ADAPT Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ADAPT Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ADAPT Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ADAPT Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ADAPT Resiliency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IQA NOS ATN Management Plane Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCN Communication Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single DCN Subnet Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dual DCN Subnet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Layer 2 Switch and Spanning Tree Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCN-only communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time-of-Day Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-46 4-48 4-48 4-49 4-49 4-51 4-52 4-54 4-56 4-56 4-56 4-59 4-62 4-64 4-65 4-66 4-66 4-67 4-68 4-70 4-70 4-71 4-71 4-71 4-73 4-75 4-76 4-77 4-77
IQA NOS ATN Digital Protection Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79 Digital Subnetwork Connection Protection (D-SNCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79 Optical Subnetwork Connection Protection (O-SNCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89 Infinera ATN Graphical Node Manager (GNM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Launching Infinera ATN GNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Topology Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inventory Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software and Database Configuration Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment Configuration and Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 5-3 5-4 5-5 5-5 5-6 5-6 5-7 5-7 5-8
Infinera Corporation
Release 2.0
Page iv
Contents
Infinera Digital Network Administrator (DNA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Infinera SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10 Command Line Interface (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Infinera Network Planning System (NPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Appendix D - Acronyms
List of Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Infinera Corporation
Figures
Figure 1-1 Figure 1-2 Figure 2-1 Figure 2-2 Figure 2-3 Figure 2-4 Figure 3-1 Figure 3-2 Figure 3-3 Figure 3-4 Figure 3-5 Figure 3-6 Figure 3-7 Figure 3-8 Figure 3-9 Figure 3-10 Figure 3-11 Figure 3-12 Figure 3-13 Figure 3-14 Figure 3-15 Figure 3-16 Figure 3-17 Figure 4-1 Figure 4-2 Figure 4-3 Infinera ATN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Infinera Management Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 ATN Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Point-to-Point Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Linear Add/Drop Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Ring Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 ATC-A Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 ATC-P Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 DMC-B with Two Half-Width DCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30 DMC-B with One Full-Width DCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31 ATC Digital and Optical Transport Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38 Optical Transport Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40 Optical Transport Unit (OTUk) Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41 DTF Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43 Digital Transport Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44 Intra-chassis communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49 Inter-chassis communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50 Inter-node control plane over OSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51 ATN Multi-chassis System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55 Hardware Logical Configuration of an ATN Terminal Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59 Hardware Logical Configuration of an ATN Add/Drop Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60 Hardware Logical Configuration of an ATN Amplification Node . . . . . . . . . . . . . . . . . . . . . . . . . 3-61 Hardware Logical Configuration of an ATN Regeneration Node . . . . . . . . . . . . . . . . . . . . . . . . . 3-62 ARC Behavior (Leave Outstanding Alarms vs. Clear Outstanding Alarms). . . . . . . . . . . . . . . . . . 4-8 SIM-T-1-10G: Client CTP Facility Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 SIM-T-1-10G: Client CTP Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Infinera Corporation
Release 2.0
Page vi
Figures
Figure 4-4 Figure 4-5 Figure 4-6 Figure 4-7 Figure 4-8 Figure 4-9 Figure 4-10 Figure 4-11 Figure 4-12 Figure 4-13 Figure 4-14 Figure 4-15 Figure 4-16 Figure 4-17 Figure 4-18 Figure 4-19 Figure 4-20 Figure 4-21 Figure 4-22 Figure 4-23 Figure 4-24 Figure 4-25 Figure 4-26 Figure 4-27 Figure 4-28 Figure 4-29 Figure 4-30 Figure 4-31 Figure 4-32 Figure 4-33 Figure 4-34 Figure 4-35 Figure 4-36 Figure 4-37 Figure 4-38 Figure 4-39 Figure 4-40 Figure 4-41 Figure 4-42 Figure 4-43 Figure 4-44 Figure 4-45 Figure 4-46 Figure 5-1
SIM-T-1-10G: Line OTU2 CTP Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-13 SIM-T-2-2.5GM: Clear Channel Client CTP Facility Loopback . . . . . . . . . . . . . . . . . . . . . . . . . .4-13 SIM-T-2-2.5GM: Clear Channel Line CTP Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . .4-14 SIM-T-1-10GT: DCH CTP Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-14 SIM-T-1-10GT: DCH CTP Facility Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-15 SIM-T-1-10GT: Line DTP CTP Facility Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-15 SIM-T-1-10GT: Trib DTP CTP Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-16 SIM-T-1-10GT: Client CTP Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-16 SIM-T-1-10GT: Client CTP Facility Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17 SIM-A-8-2.5GMT: DCH CTP Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17 SIM-A-8-2.5GMT: DCH CTP Facility Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-18 SIM-A-8-2.5GMT: Line DTP CTP Facility Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-18 SIM-A-8-2.5GMT: Trib DTP CTP Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-19 SIM-A-8-2.5GMT: Client CTP Terminal Loopback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-19 SIM-A-8-2.5GMT: Client CTP Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-20 SIM-T-1-10GM/SIM-T-1-10-GP: Client CTP Facility Loopback . . . . . . . . . . . . . . . . . . . . . . . . .4-20 SIM-T-1-10GM/SIM-T-1-10-GP: OTUk CTP Facility Loopback . . . . . . . . . . . . . . . . . . . . . . . . . .4-21 SIM-T-1-10GM/SIM-T-1-10-GP: OTUk CTP Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . .4-21 SIM-T-1-10GM/SIM-T-1-10-GP: Client CTP Terminal Loopback. . . . . . . . . . . . . . . . . . . . . . . . .4-22 OTUk PRBS Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-23 SONET/SDH Trib and Line PRBS Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-23 DTF Section/Path PRBS Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-24 Test Signal Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-26 SONET/SDH/J0/OTUk Trace Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-28 DChCTP and DTPCTP Trace Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-29 Managed Objects and Hierarchy (ATC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-31 SSHv2-secured Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-53 Infinera Network with RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-55 ADAPT Control Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-64 Power Control Loop between SIM and OFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-65 One ATN connected to a Single DCN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-72 Multiple ATNs Connected to a Single DCN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-73 ATNs Connected to Two DCNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-74 Layer 2 Ethernet-switch in a ring network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-76 ATN Network with only DCN connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-76 NTP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-78 ATN acting as NTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-78 Two-port D-SNCP with SIM-T-1-10G. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-81 Two-port D-SNCP with SIM-T-2-2.5GM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-82 One-port D-SNCP with SIM-T-2-2.5GM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-83 Functional block diagram of OPSW modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-90 OSNCP per optical channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-91 OSNCP per optical band . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-91 Infinera Management Suite and Nodal Management Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . .5-2
Infinera Corporation
Figures
Page vii
NPS Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-13 DWDM 40-Channel Wavelength Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2 CWDM and Mixed CWDM/DWDM Channel Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Infinera Corporation
Release 2.0
Page viii
Figures
Infinera Corporation
Tables
Table 1-1 Table 3-1 Table 3-2 Table 3-3 Table 3-4 Table 3-5 Table 4-1 Table 4-2 Table 4-3 Table 4-4 Table 4-5 Table 4-6 Table A-1 Table B-1 Table B-2 Table B-3 Table B-4 Table B-5 Table B-6 Table B-7 Table B-8 Table B-9 Table B-10 Table C-1 Table C-2 Table C-3 New Features and Hardware for Release 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 ATC-A Hardware Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 SIM-TOM Compatibility Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13 Tributary Optical Modules for ATN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18 OFM Product Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24 Multi-chassis Functional Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56 Access Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47 ADAPT Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67 ADAPT Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68 D-SNCP Switching Requests and Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86 D-SNCP Protection on SIMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87 O-SNCP Switching Requests and Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93 Alarm Masking Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Optical PM Parameters Supported on the ATN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 OTUk PM Parameters and Thresholds Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7 DTF PM Parameters and Thresholds Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9 DCh PM Parameters and Thresholds Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12 SONET Client Signal PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14 SDH Client Signal PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-17 Ethernet Client Signal PM Parameters Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-19 Fibre Channel Client Signal PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-35 OSC PM Parameters Supported on the AMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-38 Additional PM Parameters Supported on the ATN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-39 ATN DWDM Optical Channel Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3 ATN CWDM Channel Plan: 8-channel band . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5 ATN CWDM Channel Plan: 2-channel sub-band . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
Infinera Corporation
Release 2.0
Page x
Tables
Infinera Corporation
Objective
This guide provides an introduction and reference to the Infinera ATN product, which is one of the network elements that are used to build an Infinera Digital Optical Network. This guide also describes the Infinera IQA Network Operating System ATN that runs on the ATNs that enable network-wide intelligent control and operations, and the Infinera Management Suite that provides remote management of the entire Infinera network.
Audience
The primary audience for this guide includes network architects, network planners, network operations personnel, and system administrators who are responsible for deploying and administering the Digital Optical Network. This guide assumes that the reader is familiar with the following topics and products:
Basic internetworking terminology and concepts Coarse Wavelength Division Multiplexing (CWDM) technology and concepts Dense Wavelength Division Multiplexing (DWDM) technology and concepts
Infinera Corporation
Release 2.0
Page xii
Document Organization
Document Organization
The following table describes each chapter in this guide.
Chapter CHAPTER 1: Introduction CHAPTER 2: Network Applications CHAPTER 3: Digital Optical Networking Systems CHAPTER 4: IQA Network Operating System ATN CHAPTER 5: Infinera Management Suite Description Provides an introduction to the Infinera Digital Optical Network, ATN, IQA NOS ATN and Infinera Management Suite products. This chapter also includes a list of Release 2.0 hardware and software features. Describes various configurations and network topologies supported by the ATN. Describes the ATN hardware architecture. This chapter also includes a description of the data plane architecture, control plane architecture, the transport interfaces and the circuit packs. Describes the operation, administration, maintenance and provisioning (OAM&P) functions provided by the IQA Network Operating System ATN. Provides an introduction to the Infinera Management Suite, which includes the Infinera Digital Network Administrator (DNA) and Infinera Graphical Node Manager (GNM) applications. It also describes the ATN SNMP Agent and the ATN CLI. Describes the alarm masking hierarchy, in which a network element masks (suppresses) reporting of higher layer failures associated with the same root cause as a higher priority, lower layer, failure. Describes the Performance Monitoring (PM) parameters reported by Infinera ATNs. Provides the optical channel plan supported by the ATN. Provides a list of acronyms and their definitions used in Infinera Technical Publications.
Appendix A: Alarm Masking Hierarchy Appendix B: ATN PM Parameters Appendix C: Optical Channel Plan Appendix D: Acronyms
Infinera Corporation
Page xiii
Infinera ATN Alarm and Trouble Clearing Guide Infinera ATN CLI User Guide
Infinera ATN GNM User Guide Infinera ATN Hardware Description Guide
1900-589
1900-590
Infinera ATN Site Preparation and Hardware Installation Guide Infinera ATN SNMP Agent Reference Guide
1900-591
1900-592
1900-593
Infinera Corporation
Release 2.0
Page xiv
Document Name
Document ID 1900-594
Description Provides the routine maintenance and alarm troubleshooting procedures for the Infinera ATN network elements. It includes the routine hardware and software maintenance procedures and various troubleshooting tools. Describes procedures for turning up, commissioning and testing the installed Infinera ATN network elements. Includes the description of circuit activation and end-end system testing procedures.
1900-595
Infinera Corporation
Page xv
Document Updates Since Previous Version Edited SIM-TOM compatibility matrix: Included support for TOM-10G-Dn-LR2 and TOM-10G-DT-LR2 on the client-side of the SIM-T-1-10G and the TOM-10G-SR1 on the line-side of the SIM-T-1-10G. ADAPT Section: Updated the ADAPT Timer range to 400-86400 seconds. The user cannot set this timer to a value of zero. PM Appendix: Updated defintions of Band CTP Layer Parameters (Facility Signal Output Power and Optical Power Transmitted).
002
Edited the feature summary table Changed all instances of ASPS to ASAP Changed the acronym ASAP to Alarm Severity Assignment Profile Setting Rack Mounting Ears section: Added information on the 2-inch recessed mid-mount rack option on a 19-inch, 23-inch or ETSI rack Dispersion Management Chassis section: Added information on Dispersion Compensation Modules (DCMs) Loopbacks section: Updated loopback descriptions for Client CTP Facility loopback on SIM-A-8-2.5GMT, Line DTP CTP Facility Loopback on SIM-T-1-10GT PRBS section: Updated the note on in the DTF Path-level PRBS test section Trace messaging section: Added a note that a length 1/16/64 bytes is retained only for SONET/SDH J0 signals. Test signal section: Added a note that Fibre channel test signal monitoring is not supported Intra-chassis control plane section: Added Figure 3-10 Intra-chassis communication Inter-chassis control plane section: Added Figure 3-11 Inter-chassis communication Inter-node control plane (over OSC) section: Added Figure 3-12 Inter-node control plane over OSC Multi-chassis section: Added Figure 3-13 ATN Multi-chassis system ATN Site Operation section: Added information on ATN regeneration site IQA NOS ATN Management Plane overview section: Added information on ATN networks with DCN-only connectivity
Infinera Corporation
Release 2.0
Page xvi
Technical Assistance
Technical Assistance
Customer Support for Infinera products is available, 24 hours a day, 7 days a week (24x7). For information or assistance with Infinera products, please contact the Infinera Technical Assistance Center (TAC) using any of the methods listed below:
Email: techsupport@infinera.com Telephone: Direct within United States: +1-408-572-5288 Outside North America: +1-408-572-5288 Toll-free within United States: +1-877-INF-5288 (+1-877-463-5288) Toll-free within Germany/France/Benelux/United Kingdom: 00-800-4634-6372 Toll-free within Japan: 010-800-4634-6372 Fax: +1-408-572-5454 Infinera corporate website: http://www.infinera.com Infinera Customer Web Portal: https://customersupport.infinera.com
Infinera Corporation
Page xvii
In addition, the Infinera FTP server allows you to upload debug log files and other information to the Infinera TAC. To download more information about using the Infinera FTP server, perform the following: Step 1 Step 2 Step 3 Log in at: https://customersupport.infinera.com. Click How to Guides. Under Online Resource Guides, click FTP_Server_Overview.pdf.
You can also track and update Infinera CSM cases by contacting the Infinera TAC via phone or email.
Information to Provide
When submitting service request(s), have the following information available:
Caller Name, Company, and/or Contact Information Priority (for example, High, Medium, Low, and/or Informational) Network Impact (for example, service-affecting, non-service affecting, and/or intermittent)
Infinera Corporation
Release 2.0
Page xviii
Technical Assistance
Network Status (for example, deployment in progress, field trial, and/or production live) Software Version (if relevant) Affected Hardware Chassis/Module/Cable Type Description of the problem and symptoms Network topology and configuration Supporting information (for example, data logs, troubleshooting steps taken, etc.)
Incident Classification/Handling/Response
All service requests are immediately assigned to an Infinera Tier 3+ TAC specialist, who ensures proper and timely handling of your request through closure. To facilitate flawless handling of customer-reported incidents, the Infinera TAC utilizes a customer relationship management (CRM) system called the Infinera Customer Service Module (CSM) to track and manage all reported incidents and service requests including RMAs. Every service request is tracked as a unique case within the Infinera CSM, and is classified in accordance with the table below. The table below also describes the standard Service Level response and resolution targets supported by the Infinera TAC.
Targeted Maximum Time for Resolution 4 hours to find resolution, or 4 hours to attain workaround and downgrade to Major (if acceptable to customer). For software incidents with workaround, maintenance release to be issued as soon as possible with high priority engagement of Infinera engineering resources. 8 hours to attain workaround and downgrade to Minor (if acceptable to customer). 8 hours for root cause identification. For software incidents, maintenance release to be issued at time of next scheduled maintenance release.
Priority 1High
Definition Network service is down, or extended (>30 minutes) loss of network management.
Handling and Escalation Infinera TAC coordinates all necessary resources, around-the-clock, to bring incident to closure. Engagement of higher-level specialists and management with highest level of priority, within 2 hours after incident report.
2Medium
Network operation is degraded, or unacceptable levels of network performance. Significant impact on business operations.
Infinera TAC coordinates all necessary resources, around-the-clock, to bring incident to closure. Engagement of higher-level specialists and management within 4 hours after incident report.
Infinera Corporation
Page xix
Priority 3Low
Definition Network operation is impaired, but causes little/no impact on business operations.
Handling and Escalation Infinera TAC coordinates all necessary resources during normal business hours. Engagement of higher-level specialists and management within 2.5 days after incident report. Infinera will commit resources and address during normal business hours.
Targeted Maximum Time for Resolution 72 hours for root cause identification. Fix issue in next major release, if committed by Infinera development resources. Varies, depending upon nature of request.
4Informational
Escalation
You may escalate your service request to higher levels of attention if you are not satisfied with its current handling. All service requests are routed to management within 15 minutes of receiving your notification. To escalate by phone or email: Step 1 Step 2 Step 1 Step 2 Step 3 Step 4 Step 5 Contact the Infinera TAC. Provide your Infinera CSM case number. Log in at: https://customersupport.infinera.com. Click Link to CSM. Click on your incident title or ID. Enter your escalation request within the Notes field. Click Submit.
To request a Return for Credit RMA, contact your Infinera Account Manager.
Infinera Corporation
Release 2.0
Page xx
Documentation Feedback
To request all other types of RMA, submit your RMA request to the Infinera TAC. To download additional information on the Infinera RMA Handling Policy and Procedures, including returnmodule packing instructions: Step 1 Step 2 Step 3 Log in at: https://customersupport.infinera.com. Click How To Guides. Under RMA Procedures, click one of the following documents:
RMA Procedure - Customer Quick Reference.pdf RMA Procedure.pdf
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 169 Java Drive 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
Infinera Corporation
CHAPTER 1
Introduction
This chapter provides an introduction to the Infinera Digital Optical Network, Infinera Management Suite, and Release 2.0 features in the following sections:
Infinera Digital Optical Network on page 1-2 IQA Networking Operating System ATN Overview on page 1-4 Infinera Management Suite (IMS) Overview on page 1-5 Release 2.0 Feature Summary on page 1-7
Infinera Corporation
Release 2.0
Page 1-2
Infinera ATN
The Infinera ATN is a Coarse Wavelength Division Multiplexing (CWDM) and Dense Wavelength Division Multiplexing (DWDM) multi-service platform that provides add/drop and bandwidth management capabilities. The Infinera Digital Optical Network is shown in Figure 1-1, with ATNs deployed anywhere client access is desired. The links between the ATNs isolate analog engineering and impairments within that link. Users can progressively deploy the transport network with ATNs at more points of presence, interconnected by links, when and where capacity is required. Figure 1-1 Infinera ATN
The Infinera ATN has DWDM and CWDM capabilities and provides support for up to 40 DWDM channels and eight CWDM channels. It provides the means for direct access to client data at any of the client signal rates supported (see Transport Interfaces on page 3-33), allowing flexible selection of whether to add/ drop, amplify, or optically express individual data streams. The ATN can be equipped in a variety of network configurations using a common set of circuit packs. Refer to ATN Configurations on page 2-2 for a detailed description of the various configurations supported by the ATN. The ATN hardware is housed in the ATN Transport Chassis (ATC). A description of the ATN hardware is provided in the ATN Hardware Overview on page 3-2.
Infinera Corporation
Introduction
Page 1-3
Infinera DTN
The Infinera DTN is a Digital Optical Networking System which provides digital add/drop and bandwidth management capabilities. The DTN provides digital bandwidth management within a Digital Optical Network. It provides the means for direct access to client data at any of the supported signal rates, allowing flexible selection of whether to multiplex, add/drop, amplify, groom, optically express, or switch individual data streams. For more information on the Infinera DTN, refer to the Infinera DTN System Description Guide.
Infinera Corporation
Release 2.0
Page 1-4
hierarchical alarm correlation, configurable alarm severity assignment profile, event logging, environmental alarms, and export of alarm and event data
Network diagnostics capability including digital level loopbacks, circuit-level Pseudo Random Bit
Sequence (PRBS) 31 and detection, Trail Trace Identifier (TTI) and synchronous optical network (SONET)/synchronous digital hierarchy (SDH) J0 monitoring and insertion at the tributaries
Automatic equipment provisioning and equipment pre-provisioning Fully automated neighbor discovery Topology discovery in a subnet Flexible software and configuration database management including remote software upgrade/roll-
back, configuration database backup and restore, and File Transfer Protocol (FTP) transfers
Analog and digital performance monitoring at every ATN node and native client signal performance
monitoring at tributaries
Supports Network Timing Protocol (NTP) to synchronize the timestamps on all alarms, events and
Service (RADIUS)
Hitless software upgrades Multi-chassis configurations utilizing the Nodal Control (NC) ports, located on the front panel of the
ATN Management Module (AMM) placed in the ATC-A. Control plane communication path utilizing the ATN Management Module (AMM)
Open integration interfaces including the CLI and CSV formatted flat files that can be exported using
secure FTP Refer to Chapter 4, IQA Network Operating System ATN for a detailed description of the features.
Infinera Corporation
Introduction
Page 1-5
The IMS architecture employs a network-is-master model, allowing the network itself to asynchronously inform and update all registered management servers and mitigate any synchronization or accuracy issues. The network state and status is automatically discovered and reported to the management servers and users. This network-is-master model enables each network element to be managed by multiple management applications, allowing for full management redundancy and allowing each management application to maintain synchrony with what is occurring within its purview.
Infinera Corporation
Release 2.0
Page 1-6
The following applications that are included in the IMS are used to manage the ATN:
Infinera ATN Graphical Node Manager (see Infinera ATN Graphical Node Manager (GNM) on
page 5-3)
Infinera Digital Network Administrator (see Infinera Digital Network Administrator (DNA) on page 5-
9)
Infinera SNMP Agent (see Infinera SNMP Agent on page 5-10) Infinera CLI (see Command Line Interface (CLI) on page 5-11) Infinera NPS (see Infinera Network Planning System (NPS) on page 5-12)
Infinera Corporation
Introduction
Page 1-7
Feature
Network Topologies
ATN supports point-to-point, linear add/drop multiplexing (ADM), hub-and-spoke, and ring topologies. See Network Topologies on page 2-4 for more information. ATN sites can be deployed as a: Terminal SiteWhen deployed as a terminal node, all optical channels terminate at the ATN and there are no express or pass through channels. Add/Drop SiteWhen deployed as an Add/Drop node, the ATN can be configured to selectively add/drop specific channels and optically express the remaining channels. Amplifier-only siteWhen deployed as an amplifier-only site, the ATN performs only amplification function and add or drop of channels is not supported. Regeneration siteATN nodes can be used to perform regeneration of 2.5G and 10G signals. Release 2.0 ATN introduces 10G DTF regeneration, OTU2/OTU2e/OTU2f regeneration, 10GbE LAN regeneration in low latency mode and regeneration of video services. X
ATN-DTN Interworking
Release 2.0 of ATN introduces support for ATN-DTN inter-operability. The ATN SIM-T-2-2.5GM, SIM-T-1-10GP, SIM-T-1-10GM, SIM-T-1-10GT and SIM-A-8-2.5-GMT modules can interface with the DTN TAM modules as follows: SIM-T-2-2.5GM to TAM-8-1G, TAM-4-2.5G or TAM-8-2.5GM SIM-T-1-10GM to TAM-2-10GM SIM-T-1-10GP to TAM-2-10GM SIM-T-1-10GT to TAM-2-10GT SIM-A-8-2.5GMT to TAM-2-10GT Interfacing between the SIM and TAM modules (as listed above) , allows ATN-DTN inter-connections to be created with the elimination of back-to-back SIMs at hub site for almost all supported services. Use of bandwidth virtualization through DTN offers additional flexibility. (Continued...)
Infinera Corporation
Release 2.0
Page 1-8
Description
The following interfaces are supported for ATN-DTN networks: OC-3 / STM-1 OC-12 / STM-4 OC-48 / STM-16 OC-192/ STM-64 1GbE 10GbE 1G Fibre Channel 2G Fibre Channel 8G Fibre Channel OTU1 OTU2 OTU2e SD-SDI HD-SDI DVB-ASI Neighbor Connectivity ATN nodes use the Optical Supervisory Channel (OSC) over the line fibers to discover neighboring ATNs. The network neighborhood displays the neighbor connectivity along with discovered node ID and provisioned node ID for the neighbor node. Hardware Modules Infinera ATN ATN is a Digital Optical Networking System which provides add/ drop capabilities. Multi-chassis ATNs include ATC-As and/or ATC-Ps stacked together. ATC-A is a 3RU, 11-slot service shelf that can be mounted in a 19-inch or 23-inch ANSI or ETSI rack. The ATC-A includes the following: One slot for the management module (AMM-A) Two slots for Power Conversion Modules (PCMs) One slot for the Fan tray Two slots for EDFA amplifiers (AAMs) or OFM-1-OSC modules Eight flexible slots that can house Optical Filter Modules (OFMs), Service Interface Modules (SIMs) or Optical Protection Switch Modules (OPSWs). X X
Infinera Corporation
Introduction
Page 1-9
Description ATC-P is a 2RU, eight-slot chassis that can be mounted in a 19-inch or 23-inch ANSI or ETSI rack. The ATC-P includes slots for up to eight passive OFMs. The ATCP and its modules are not managed by any software interface. Up to two ATC-Ps can be added to a node in a multi-chassis configuration.
AMM is the main node controller and also functions as a shelf controller in a multi-chassis configuration .It performs management and control functions for the ATN. It supports a database branding mechanism that prevents the installation of an incorrect or outdated control module into a chassis.
AAMs are EDFA based optical amplifier modules. An ATN may be equipped with AAMs when optical amplification is required to extend the optical reach between the ATNs. There are four types of AAMs: AAM-B1, which is used as a booster amplifier, with support for up to +13dBm total output power AAM-P1, which is used as a pre-amplifier and in-line amplifier, with support for up to +13dBm total output power Release 2.0 adds the following higher power AAMs: AAM-B2, which is used as a booster amplifier, with support for up to +17dBm total output power AAM-P2, which is used as a pre-amplifier and in-line amplifier, with support for up to +17dBm total output power
Infinera Corporation
Release 2.0
Page 1-10
Description OFM performs optical multiplexing and de-multiplexing of optical channels to/from SIMs as well as AAMs. There are several types of DWDM and CWDM OFMs. DWDM OFMs Four 10-channel OFMs, ten 4-channel OFMs, ten 4-channel OFMs with active Variable Optical Attenuators (VOAs) and twenty 2-channel OFMs with active VOAs CWDM OFMs One 8-channel OFM, four 2-channel OFMs, and eight 1-channel OFMs Mixed OFMOne 6-channel CWDM/DWDM OFM with one DWDM Expansion Port 1310nm OFMOFM that multiplexes or de-multiplexes a 1310nm signal with OSC and CWDM or DWDM channels
Infinera Corporation
Introduction
Page 1-11
Description
SIM-A-8-2.5GMT is an eight port, any-service any-port muxponder with DTF framing on the line side. The SIM-A-8-2.5GMT aggregates multiple service interfaces into a 10G DTF signal which can interface with the TAM-2-10GT. OPSWs are stand-alone, Layer 1 optical protection switch modules that offer cost-effective path protection (Optical-Subnetwork Connection Protection, O-SNCP) without the need for two SIMs in CWDM and DWDM networks. There are two types of OPSWs: OPSW-1One client port, two line ports module to provide one protection service OPSW-2Two client ports, four line ports module to provide two protection services X
TOM is a client-side and line-side field-replaceable optical interface module. A TOM converts an incoming client optical signal into a serial electrical signal for further processing in the SIMs. The TOM also converts out-going signals from electric to optical for line-side transport. The following TOMs are supported in the ATN. All TOMs marked with a * indicate that they are newly introduced in this release
Line TOMs
Tributary Optical Module-10G, DWDM XFP (TOM-10G-Dn-LR2) Tributary Optical Module-10G (TOM-10G-Cn-LR2)* Tributary Optical Module-10G Tunable (TOM-10G-DT-LR2)* Tributary Optical Module-2.5G Multi Rate, DWDM SFP (TOM-MR-Dn-LR2) Tributary Optical Module-2.5G Multi Rate, CWDM SFP (TOM-MR-Cn-LR2)
Client TOMs
Tributary Optical Module-10G-SR0 (TOM-10G-SR0) Tributary Optical Module-10G-SR1 (TOM-10G-SR1) Tributary Optical Module-10G-IR2 (TOM-10G-IR2)* Tributary Optical Module-10G-LR2 (TOM-10G-LR2)* (continued..)
Infinera Corporation
Release 2.0
Page 1-12
Description
Tributary Optical Module-8G (TOM-8G-XSM-LC-L)* Tributary Optical Module-2.5G-SR1 (TOM-2.5G-SR1) Tributary Optical Module-2.5G-IR2 (TOM-2.5G-IR2)* Tributary Optical Module-2.5G-LR2 (TOM-2.5G-LR2)* Tributary Optical Module-2.5G-SR1 Multi Rate (TOM-2.5GMR-SR1) Tributary Optical Module-2.5G-IR1 Multi Rate (TOM-2.5GMR-IR1) Tributary Optical Module-1G-LX (TOM-1G-LX) Tributary Optical Module-1G-SX (TOM-1G-SX) Tributary Optical Module-1G-ZX (TOM-1G-ZX)*
OSC TOM
Tributary Optical Module-100M-C45-L2 (TOM-100M-C45-L2)
Electrical TOMs
Tributary Optical Module (Video TOM) High-definition Serial Digital Interface (HD-SDI) 1.485G receiver (TOM-1.485HD-RX)* Tributary Optical Module (Video TOM) 1.485G high-definition (HD) transmit (TOM-1.485HD-TX)* Tributary Optical Module (Video TOM) 1.4835G high-definition (HD) receiver (TOM-1.4835HD-RX)* Tributary Optical Module (Video TOM) 1.4835G high-definition (HD) transmit (TOM-1.4835HD-TX)* Tributary Optical Module (Electrical TOM) RJ-45 interface, 1GbE (TOM-1G-BASE-T)* Power Conversion Modules (PCMs) There are two dedicated power conversion module slots in each ATC-A. Release 2.0 ATN introduces support for an AC Power Conversion module, PCM-AC that receives AC power input. Each PCM slot (PCM-A/PCM-B) in the ATC-A can accommodate either a DC power conversion module (PCM-48V DC) or an AC power conversion module (PCM-AC). Dispersion Management Chassis (DMC) DMC is a passive chassis that does not require management. Depending on the span characteristics, the DMC is optionally included in ATNs to house Dispersion Compensation Modules (DCMs). X
Infinera Corporation
Introduction
Page 1-13
Description DCM houses the dispersion compensating fiber that can be optically connected in-line with an AAM. The DCM equalizes chromatic dispersion of different frequency components having different propagation speeds and reverses the dispersion effect of transmission fiber, to restore the optical signal. System Interfaces
Transport Interfaces
ATN supports the following client/tributary interfaces: SONET OC-3, OC-12, OC-48 and OC-192 signals SDH STM-1, STM-4, STM-16 and STM-64 signals Fibre Channel 1G (1G FC), Fibre Channel 2G (2G FC), FICON Express, Fibre Channel 8G (8G FC) and Fibre Channel 10G (10G FC) signals Ethernet 10GbE LAN Phy, 10GbE WAN Phy, and 1GbE signals OTU1, OTU2, OTU2e, OTU2f and OTU2v (DTF) signals ESCON and FICON signals SD-SDI (270 Mbps), SDTI (270 Mbps), HD-SDI (1.4835 Gbps and 1.485 Gbps), DVB-ASI (270 Mbps) and DV6000 The supported line interfaces are: Up to 40 DWDM line-side channels in combination with an Optical Supervisory Channel (OSC) to provide up to 400Gbps transport and in-band communications between network elements. The line-side channels include 10GbE, OTU2 (10.7Gbps), OTU2e (11.1Gbps), OTU2f (11.3Gbps), OTU2v/ DTF and 3R output of 2.7Gbps and lower client signals. Up to eight CWDM line-side channels in combination with an OSC to provide transport and in-band communications between network elements. The line-side channels include 10GbE, OTU2 (10.7Gbps), OTU2e (11.1Gbps), OTU2f (11.3Gbps), OTU2v/DTF and 3R output of 2.7Gbps and lower client signals.
ATN includes the following RJ-45 management interfaces: One DCN port (RJ-45 interface) One Craft Ethernet port (RJ-45 interface) One Craft Serial DCE port (RJ-45 interface)
The ATN provides two 10/100 Base-T auto-negotiating interchassis interconnect RJ-45 Ethernet interfaces labeled as Nodal Control (NC1 and NC2), for inter-chassis control in a multi-chassis system.
Infinera Corporation
Release 2.0
Page 1-14
Description ATC-A supports five external alarm inputs and ten alarm control outputs. These opto-isolator contacts enable integration with parallel telemetry systems, and provide office-level alarming. Of the five external alarm inputs, four can be configured by the user (one is dedicated for ACO). Of the ten external alarm outputs, four can be configured by the user and the remaining six are based on system alarms (three each for visual and audible).
ATN includes OSC which is a 100Mbps ethernet channel for internode communication. System Architecture
ATN transports 10G client signals using ITU-T G.709 Optical Transport Units (OTU2, OTU2e, OTU2f). The ATN supports forty (40) DWDM wavelengths with 100GHz spacing and eight CWDM channels. Modeled after ITU G.709 digital wrapper architecture, the DTF or OTU2v is used within the DTF-based SIMs (SIM-T-1-10GT and SIM-A-8-2.5GMT) in the Infinera Digital Optical Network Enables users to scale system capacity of deployed network equipment in new or existing systems by allowing for multi-chassis configurations. For more information, see Multi-Chassis Systems on page 3-53. In Release 2.0, the Infinera ATN network element can be installed in a multi-chassis configuration that consists of up to ten ATCs (consisting of up to eight ATC-A chassis and up to two ATC-P chassis) installed on a single rack or multiple racks being managed as a single ATN node. One ATC-A is termed the main chassis and houses the node controller AMM. The remaining ATC-A or ATC-P chassis are termed expansion chassis. The AMMs included in the expansion chassis are termed as shelf controllers. The chassis are interconnected through the NC ports on the AMM front panel.
Hardware Scalability
Infinera Corporation
Introduction
Page 1-15
Description In Release 1.0 ATN includes only passive optical filter modules (OFMs) that require the optical power in any network to be balanced manually by using fixed optical attenuators i.e. PADs. Infinera ATN Release 2.0 introduces a power management control plane called ADAPT that enables automatic optical power management with Variable Optical Attenuator (VOA) enabled active OFM modules and variable gain optical amplifiers (AAMs). For more information, see ADAPT Power Management Control Plane Overview on page 4-64. ADAPT provides the following benefits: Allows setting correct optical power levels via ATN IQA NOS software Power management with VOA-enabled active OFM modules and variable gain optical amplifiers: Minimizes usage of fixed attenuators/pads Maximizes system performance Simplifies network activation, operation and growth Fault Management
Alarm Surveillance
ATN provides the following alarm surveillance functions (see Alarm Configuration on page 4-7 for more information): Provides detection and user-customized reporting of defects in the ATN. Features alarm masking. Includes an Alarm Reporting Control (ARC) feature that allows users to prevent a managed object from reporting alarms during maintenance procedures. The system can be configured to clear or to maintain all out-standing alarms when ARC is enabled. ATN Release 2.0 introduces customizable timer-based alarms, customizable severity levels for Threshold Crossing Alerts (TCAs) and the option to export alarm data.
Event Log
ATN provides a wrap-around historical event log that tracks the reports of all changes that occur within the system. Users can retrieve event log data through the network management user interfaces. See Event Log on page 4-9 for more details.
Infinera Corporation
Release 2.0
Page 1-16
Description The Alarm Severity Assignment Profile (ASAP) 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. The ASAP feature can also be used to customize the severity of the alarms that indicate when an entity is put in the Locked or Maintenance administrative state. See Alarm Severity Assignment Profile Setting (ASAP) on page 4-9 for more information.
For comprehensive maintenance and troubleshooting, the system supports loopbacks, trace messaging, pseudo random binary sequence (PRBS) generation and detection. In addition, the system also supports GbE and Fibre Channel (FC) Client Termination Point tests on the SIM-A-8-2.5GMT. See Maintenance and Troubleshooting Tools on page 4-10 for more information. ATN Release 2.0 introduces: Support for loopbacks on the newly introduced SIM-T-1-10GP, SIM-T-1-10GM, SIM-T-1-10GT and SIM-A-8-2.5GMT modules OTUk Client CTP PRBS test support on the trib and line ports on the SIM-T-1-10GM and SIM-T-1-10GP (in addition to the OTUk Client CTP PRBS test support on line port of SIM-T-110G) SONET/SDH trib and line PRBS support on SIM-A-8-2.5GMT DTF section-level PRBS and DTF path-level PRBS support on SIM-A-8-2.5GMT and SIM-T-1-10GT Fibre Channel test signal generation support on trib and line side of SIM-A-8-2.5GMT GbE test signal generation support on trib-side of SIM-A-8-2.5GMT and GbE test signal generation and monitoring support on line-side of SIM-A-8-2.5GMT OTUk TTI support extended to SIM-T-1-10GM and SIM-T-110GP (in addition to SIM-T-1-10G) DChCTP and DTPCTP TTI support on SIM-T-1-10GT and SIM-A-8-2.5GMT
Infinera Corporation
Introduction
Page 1-17
Feature
All hardware equipment, physical ports and logical termination points are represented through the network management interfaces as managed objects, according to the Telcordia, ITU-T and TMF general information modeling standards. Users can export inventory information in Tab Separated Value (TSV) and Comma Separated Value (CSV) format. See Managed Objects on page 4-30.
System resources, including the circuit-packs, multi-chassis and TOM-TOM optical connections, are automatically discovered. This inventory is maintained and viewed through the network management interfaces. See System Discovery and Inventory on page 4-31 for more information. ATN also supports auto-discovery for optical connections between: Two TOMs placed on SIMs in an ATN network A TOM on a TAM-2-10GT on a DTN and a TOM on a SIM-T-110-GT or SIM-A-8-2.5GMT on an ATN. See Data Plane Discovery on page 4-33 for more information
ATN supports configuration of the tributary behavior upon trib disabling (disabling because of locked or maintenance state, or because of autonomous trib disabling due to detection of Trib Path LOF or Trib Path AIS). ATN supports None, Send AIS, Insert Idle, Turn-off Laser, Disable Transmitter, Send NOS and Send All Zeroes Trib Disable Actions. ATN also supports configuration of the line behavior upon line disabling on the SIM-T-1-10G, SIM-T-1-10GP and SIM-T-1-10GM. None and Turn-off Laser are the supported Line Disable Actions
State Modeling
ATN implements a standard state model, compliant with TMF814, and GR-1093, for all the managed objects.
Infinera Corporation
Release 2.0
Page 1-18
Feature
ATN enables 1+1 protection of diverse circuit paths through the Digital Optical Network for sub-50ms switching. Digital SNCP increases the overall reliability and service up-time of the optical path, and provides fault escalation, which enables Digital SNCP protection on services that are transported through foreign WDM or SONET/SDH networks that originate and terminate on Infinera ATNs. Infinera ATN provides 2-port DSNCP and 1-port DSNCP protection. For more information, see Digital Subnetwork Connection Protection (D-SNCP) on page 4-79.
O-SNCP offers service protection on all interface points within the optical network. It protects against SIM failures by using standalone Optical Protection Switch (OPSW) modules that offers cost-effective path protection in both CWDM and DWDM networks without the need for two SIMs. For more information, see Optical Subnetwork Connection Protection (O-SNCP) on page 4-89. Performance Monitoring
ATN supports optical and digital PM data collection. SONET/ SDH/Ethernet/OTN/Fibre Channel client PM data collection is supported in the ATN for the tributary interfaces. Both current and historical PM reset counters are supported, as is automatic notification of user-defined-threshold crossings for early detection of problems. See ATN PM Parameters on page B-1 for more details. ATNs support customizable severity levels for Threshold Crossing Alerts (TCAs). See Alarm Severity Assignment Profile Setting (ASAP) on page 4-9 for more information on setting alarm/ TCA severities. Release 2.0 adds support for collection of the following: Optical and digital PMs for both the client and line side interfaces of SIM-T-1-10GP, SIM-T-1-10GM, SIM-T-1-10GT and SIM-A-8-2.5GMT Optical PMs for AAMs, OFMs, Active OFMs and OPSW modules OSC packet counter PM Fan Inlet Temperature PM
Infinera Corporation
Introduction
Page 1-19
Description Provides automatic and periodic transfers of PM data in Comma Separated Value (CSV) format, for integration with external applications. See PM Data Export on page 4-44 for more information. Security and Access Management
Standards-based Security Model with Network-wide User Administration Security Audit Log
Based on the Telcordia GR-815-CORE standard, the security model provides sup-port for user identification, authentication, and access control with user customized access privileges. The ATN features a persistent circular audit log that records all system configuration activities and security related events, such as unauthorized attempts and excessive authentication attempts. The audit log provides traceability of all system-impacting changes. This feature secures management plane communications using the Secure Shell version 2 (SSHv2) and Secure File Transfer Protocol (SFTP) protocols. Users may dynamically configure SSHv2 security on a per-network element basis. In Release 2.0, the SFTP port number can be configured by the user (the default port number is 22). X
SSHv2 Security
In Release 2.0, the Infinera Digital Optical Network introduces support for RADIUS, a standard for remote authentication and storage of user name and password information in a centralized location. An Infinera network element can be configured to authenticate users according to the local settings or via the configured RADIUS servers. In addition, the network element can be configured to authenticate users first according to the RADIUS settings, and then according to the local settings on the network element if no RADIUS server can be contacted. Software and Database Management
Software Management
ATN allows users to remotely download the software image from a user specified FTP server to the AMM of the ATC-A. Each network element can store three images of the software, which users may selectively activate. The system provides the option to gracefully "fall-back" or "down-grade" to a prior release in the rare event that a failure is experienced during the upgrade process. Software images can be managed across multiple network elements from a centralized location. Users can backup, download and restore database versions. Each network element can store three versions of a database, which users may selectively activate.
Database Management
Infinera Corporation
Release 2.0
Page 1-20
Description ATC-As contain database versions that are branded - or marked as belonging to a specific chassis - in order to prevent activation of the wrong controller within a given chassis. The ATN hardware modules that support the ability to be remotely upgraded include all types of AAMs, OFMs and SIMs. System Management
In Release 2.0, IQA NOS ATN provides an embedded SNMPv2c agent on Infinera network elements in order to meet the management requirements of third party EMS/NMS systems that are based on the SNMP protocol. Network Management User Interfaces
ATN GNM is a web browser-launched Graphical User Interface (GUI) to manage a single network element. The Infinera GNM provides all of the relevant network element-level Operations, Administration, Maintenance, and Provisioning (OAM&P) functions. Release 2.0 includes updates to the ATN GNM to support all features listed above. For more information, see Infinera ATN Graphical Node Manager (GNM) on page 5-3.
Infinera Corporation
Introduction
Page 1-21
Description An element management system that, in addition to all the network element-level functionality found in the Infinera ATN GNM, provides network-level OAM&P functions. For more information, see Infinera Digital Network Administrator (DNA) on page 5-9. In addition to DTN and Optical Line Amplifier support, DNAs multi-platform support has been expanded to include Infinera ATN network elements: DNA supports provisioning services and fiber patch configuration for ATN nodes, in addition to ATN features such as Alarm Severity Assignment Profile Setting (ASAP), FTP, PM upload scheduling, and security applications for ATN nodes. DNA supports the ATN Link Viewer, ATN Channel Map Viewer, ATN Fiber Connectivity Manager, and ATN Graphical Fiber Connectivity Manager. The Multiple Node Administration feature has been expanded to include ATNs (note that a DTN cannot be used as a reference node for ATNs and vice-versa).
A command line interface (CLI) provides full Fault-management, Configuration, Accounting, Performance, and Security (FCAPS) support for ATNs. Release 2.0 includes updates to the ATN CLI to support all features listed above. For more information, see Command Line Interface (CLI) on page 5-11
Infinera Corporation
Release 2.0
Page 1-22
Infinera Corporation
CHAPTER 2
Network Applications
This chapter describes the configurations and network topologies supported by the ATN in the following sections:
ATN Configurations on page 2-2 Network Topologies on page 2-4
Infinera Corporation
Release 2.0
Page 2-2
ATN Configurations
ATN Configurations
The Infinera ATN provides terminal, add/drop and amplification functions by using a common set of circuit packs and allowing the terminal, add/drop or regeneration functions to be selected on a per-channel or a per-node basis. The ATN provides a flexible and granular network design. Utilizing a wide variety of Optical Filter Modules (OFMs), the ATN transports up to 40 DWDM optical channels, and provides 0% to 100% add/drop capability of the optical channels at any site. For ATN sites that do not terminate or drop 100% of the optical channels, the remaining channels are optically expressed though the site. In addition, the ATN provides digital and optical performance monitoring for fault isolation and troubleshooting. Figure 2-1 shows the possible ATN configurations, which are described in the following sections:
ATN Add/Drop Configuration on page 2-2 ATN Terminal Configuration on page 2-2
Infinera Corporation
Network Applications
Page 2-3
express the remaining channels. Each ATN can perform add/drop in each direction, for up to a total of 40 channels. Performance monitoring and fault monitoring is performed for each add/drop channel. At ATN Add/Drop nodes, only the configured optical channels will terminate. The remaining optical channels that do not drop will be optically expressed though the node into the network. See ATN Add/Drop Site Operation on page 3-60 for information on configuring add/drop sites.
Infinera Corporation
Release 2.0
Page 2-4
Network Topologies
Network Topologies
The ATNs can be arranged to support a broad range of network topologies uniquely meeting the implementation needs of metro applications. The flexibility of the ATNs supports a number of possible network topologies, the most typical of which are highlighted in the following sections:
Point-to-Point Network on page 2-4 Linear Add/Drop Network on page 2-4 Ring Network on page 2-5
Point-to-Point Network
In its simplest form, a point-to-point network consists of two ATNs, each configured as an ATN Terminal node, connecting two sites in the network (see Figure 2-2). Figure 2-2 Point-to-Point Network
Infinera Corporation
Network Applications
Page 2-5
Ring Network
A ring network is essentially the linear add/drop topology with a diverse path. Consequently, it is a widely used network topology in Metro networks. A typical ATN configuration consists of one ATN configured in the terminal configuration at the hub and add/drop nodes at remote sites (see Figure 2-4). Figure 2-4 Ring Network
Infinera Corporation
Release 2.0
Page 2-6
Network Topologies
Infinera Corporation
CHAPTER 3
The system interfaces, data plane, control plane and management plane functions as described in the following sections.
System Interfaces on page 3-32 System Data Plane Functions on page 3-38 System Control Plane Functions on page 3-48 System Management Plane Functions on page 3-52 Multi-Chassis Systems on page 3-53
As described in Chapter 2, the ATN supports multiple configurations. The different configurations are described in the following section:
ATN Site Operation on page 3-59
Infinera Corporation
Release 2.0
Page 3-2
Infinera Corporation
Page 3-3
Line TOMs
Tributary Optical Module-10G, DWDM XFP (TOM-10G-Dn-LR2) Tributary Optical Module-10G (TOM-10G-Cn-LR2) Tributary Optical Module-10G (TOM-10G-DT-LR2) Tributary Optical Module-2.5G Multi Rate, DWDM SFP (TOM-MR-Dn-LR2) Tributary Optical Module-2.5G Multi Rate, CWDM SFP (TOM-MR-Cn-LR2)
Client TOMs
Tributary Optical Module-10G-SR0 (TOM-10G-SR0) Tributary Optical Module-10G-SR1 (TOM-10G-SR1) Tributary Optical Module-10G-IR2 (TOM-10G-IR2) Tributary Optical Module-10G-LR2 (TOM-10G-LR2) Tributary Optical Module-8G (TOM-8G-XSM-LC-L) Tributary Optical Module-2.5G-SR1 (TOM-2.5G-SR1) Tributary Optical Module-2.5G-IR2 (TOM-2.5G-IR2) Tributary Optical Module-2.5G-LR2 (TOM-2.5G-LR2) Tributary Optical Module-2.5G-SR1 Multi Rate (TOM-2.5GMR-SR1) Tributary Optical Module-2.5G-IR1 Multi Rate (TOM-2.5GMR-IR1) Tributary Optical Module-8G (TOM-8G-SM-LC-L) Tributary Optical Module-1G-LX (TOM-1G-LX) Tributary Optical Module-1G-SX (TOM-1G-SX) Tributary Optical Module-1G-ZX-A (TOM-1G-ZX-A) (continued..)
Infinera Corporation
Release 2.0
Page 3-4
OSC TOM
Tributary Optical Module-100M-C45-L2 (TOM-100M-C45-L2)
Electrical TOMs
Tributary Optical Module (Video TOM) High-definition Serial Digital Interface (HD-SDI) 1.485G receiver (TOM-1.485HD-RX) Tributary Optical Module (Video TOM) 1.485G high-definition (HD) transmit (TOM-1.485HD-TX) Tributary Optical Module (Video TOM) 1.4835G high-definition (HD) receiver (TOM-1.4835HD-RX) Tributary Optical Module (Video TOM) 1.4835G high-definition (HD) transmit (TOM-1.4835HD-TX) TOM-1G-BASE-T
The ATC-A houses the common equipment required for operations and the circuit packs that transport and terminate optical signals. Each ATN supports up to eight CWDM channels or forty DWDM channels of line capacity. It provides the means for direct access to client data in the form of SONET/SDH, Gigabit Ethernet, Fibre Channel, ESCON, FICON, OTU1 and video signals at any site.
Infinera Corporation
Page 3-5
The ATC-A includes the following common equipment that provides power, performs system supervision, and enables system-level communication:
Rack Mounting Ears (see ATC Rack Mounting Ears on page 3-5) Two Power Conversion Modules (see ATC Power Conversion Module (PCM) on page 3-6) External Indicators and Connectors (see ATC Alarm Panel on page 3-6) One Fan Tray (see ATC Fan Tray on page 3-6) One Air Filter (see ATC Air Filter on page 3-6) One Fiber management guide and cable guide (see Fiber Management Guide and Cable Guide on
page 3-6)
One Card cage (see ATC Card Cage on page 3-7)
Infinera Corporation
Release 2.0
Page 3-6
verts to 12V DC output to the backplane at a capacity of 350W. It also creates a +3.3V DC at a capacity of 10W and distributes it to the backplane.
contact sets corresponding to user alarms and office alarms. Of the five external alarm inputs, four are user configurable (one is dedicated for ACO). Of the ten external alarm outputs, four are user configurable and the remaining six are based on system alarms (three each for visual and audible).
Infinera Corporation
Page 3-7
pinching of cables in addition to providing correct cable bend radius. This ensures the systems continual integrity and protection against signal loss or degradation.
and/or Optical Filter Modules (OFMs) of any type in slots 1 to 8 Note: Double-width circuit packs can be inserted in slots 1, 3, 5, and 7.
Up to two ATN Amplifier Modules (AAMs) of any type or up to two Passive OSC Add/Drop Module
Note: ATC-P chassis cannot be used as the Main Chassis For more information on Optical Filter Modules, see Optical Filter Module (OFM) on page 3-24.
Infinera Corporation
Release 2.0
Page 3-8
Infinera Corporation
Page 3-9
from the local AMM-A through a removable memory module (NAND Flash)
Provides a local serial port for initial AMM and system commissioning Communicates with other AMMs via Nodal Control (NC) ports located on the AMM
The AMM-A supports rebranding or recommissioning, a process by which a user may take an AMM with a known database and overwrite the database onto a chassis that is not branded to work with the AMM. See Database Branding on page 4-61 for more information on AMM rebranding.
Infinera Corporation
Release 2.0
Page 3-10
Excellent transient response and flat gain over wide dynamic range
wrapped into G.709 framing and FEC/EFEC encoded before sending out to the line side.
Infinera Corporation
Page 3-11
Signals received on the line-side TOM are converted from optical to electrical and the received
data will be FEC/EFEC decoded and G.709 de-framed before sending out to the client transmitter.
Can be configured to use FEC or Enhanced FEC (EFEC) for extra gain. Provides performance monitoring for both the line and client interfaces. It supports multiple applications including 10GbE LAN, 10GbE WAN, OC-192 and STM-64 SIM-T-2-2.5GM Two-port multi-rate transponder module Both client and line interfaces utilize Small Form-factor Pluggable (SFP) transceivers (TOMs) Line side TOMs utilize DWDM or CWDM transceivers Two client-side TOMs support the OC-3, OC-12, OC-48, STM-1, STM-16, STM-64, 1GbE, 1G
FC, 2G FC, ESCON, FICON, OTU1, HD-SDI (1.485G and 1.4835G), SD-SDI and DVB-ASI client signals
Two line-side TOMS provide 3R regeneration of the client signals listed above. Supports clock and data recovery (CDR) only and does not map the client signal into any other
format
Supports 1-Port D-SNCP and 2-Port D-SNCP SIM-T-1-10GP Single tributary port, dual line-side port, 10G transponder Client and line side optical modules using pluggable XFP transceivers Client side incoming data is wrapped into G.709 framing and FEC/EFEC encoded before send-
WAN, 8G FC, 10G FC client signals, OTU2/2e to OTU2/2e regeneration and OTU2f to OTU2f regeneration
Supports 10GbE LAN 3R Regeneration for low latency applications Provides fully transparent transport for TDM, Ethernet, SAN and Regen services Supports 1-Port D-SNCP and 2-Port D-SNCP SIM-T-1-10GM Single tributary port, single line-side port, 10G transponder Client and line side optical modules using pluggable XFP transceivers Client side incoming data is wrapped into G.709 framing and FEC/EFEC encoded before send-
WAN, 8G FC, 10G FC client signals, OTU2/2e to OTU2/2e Regen and OTU2f to OTU2f regeneration
Infinera Corporation
Release 2.0
Page 3-12
Provides fully transparent transport for TDM, Ethernet, SAN and Regen services Supports 2-Port D-SNCP SIM-T-1-10GT 10G DTF transponder with one tributary port and one line port equipped TOMs Supports OTU2v Digital Transport Frame (DTF) line-side WDM digital wrapper. Provides 10G
Transponder functionality in the ATN platform enabling WDM line-side interworking with Infinera DTN by connecting directly to the 10GT Tributary Adaptor Module, TAM-2-10GT.
Provides support for 10GbE LAN PHY, 10GbE WAN PHY, SONET OC-192 and SDH STM-64
and the client interfaces can support one of the following: Up to eight ports of 1GbE Up to four ports of SONET OC-3, OC-12, OC-48 and SDH STM-1, STM-4, STM-16 Up to four ports of 2G FC Up to eight ports of 1G FC
Note: Only odd-numbered ports can support client signals of 2Gbps and above.
Supports 2-Port DSNCP and O-SNCP
Infinera Corporation
Page 3-13
Table 3-2 on page 3-13 provides details on SIMs supported by the ATN, the TOMs that can be housed in each of the SIMs and the supported service types. Table 3-2 SIM-TOM Compatibility Matrix
SIM Type Client/Line TOM Type Supported Services
SIM-T-1-10G
Line TOMs
TOM-10G-Dn-LR2 TOM-10G-Cn-LR2 TOM-10G-DT-LR2 TOM-10G-SR1 SONET OC-192 SDH STM-64 10GbE WAN Phy 10GbE LAN Phy 10GbE WAN Phy 10GbE LAN Phy SONET OC-192 SDH STM-64
Client TOMs
TOM-10G-SR0 TOM-10G-Dn-LR2 TOM-10G-DT-LR2 TOM-10G-SR1 TOM-10G-IR2 TOM-10G-LR2
SIM-T-1-10GT
Line TOMs
TOM-10G-Dn-LR2 TOM-10G-Cn-LR2 TOM-10G-DT-LR2 DTF (OTU2v)
Client TOMs
TOM-10G-SR0 TOM-10G-SR1 TOM-10G-IR2 TOM-10G-LR2 TOM-10G-Dn-LR2 TOM-10G-Cn-LR2 TOM-10G-DT-LR2 10GbE WAN Phy 10GbE LAN Phy SONET OC-192 SDH STM-64 10GbE WAN Phy 10GbE LAN Phy DTF (OTU2v)
Infinera Corporation
Release 2.0
Page 3-14
Line TOMs
TOM-10G-Cn-LR2 TOM-10G-Dn-LR2 TOM-10G-DT-LR2 OTU2 OTU2e OTU2 OTU2e OTU2f
Client TOMs
TOM-10G-SR0 10GbE WAN Phy 10GbE LAN Phy 10G Fibre Channel TOM-10G-SR1 SONET OC-192 SDH STM-64 10GbE WAN Phy 10GbE LAN Phy 10G Fibre Channel
TOM-10G-IR2 TOM-10G-LR2
SONET OC-192 SDH STM-64 10GbE WAN Phy 10GbE LAN Phy 10G Fibre Channel OTU2 OTU2e
TOM-8G-XSM-LC-L TOM-10G-Cn-LR2
8G Fibre Channel SONET OC-192 SDH STM-64 10GbE WAN Phy 10GbE LAN Phy OTU2 OTU2e
Infinera Corporation
Page 3-15
SIM-T-2-2.5GM
Line TOMs
TOM-MR-Dn-LR2 TOM-MR-Cn-LR2 SONET OC-48 SONET OC-12 SONET OC-3 SDH STM-16 SDH STM-4 SDH STM-1 OTU1 1GbE ESCON FICON 1G FC 2G FC SD-SDI HD-SDI DVB-ASI
SIM-T-2-2.5GM
Client TOMs
TOM-1G-SX TOM-1G-LX TOM-1G-ZX TOM-1G-BASE-T TOM-2.5G-SR1 SONET OC-48 SDH STM-16 1GbE 1G FC 2G FC 1GbE
Infinera Corporation
Release 2.0
Page 3-16
SIM-T-2-2.5GM
SIM-A-8-2.5GMT
Line TOMs
TOM-10G-Dn-LR2 TOM-10G-Cn-LR2 TOM-10G-DT-LR2 DTF (OTU2v)
Client TOMs
TOM-1G-SX TOM-1G-LX TOM-1G-ZX 1GbE 1G FC 2G FC 1GbE
Infinera Corporation
Page 3-17
SIM-A-8-2.5GMT
Infinera Corporation
Release 2.0
Page 3-18
TOM Type
XFP
Field-replaceable, long-reach, 10G SONET OC-192 Small Form Factor Pluggable SDH STM-64 (XFP) optical transceiver. 10GbE WAN Phy The TOM-10G-Dn-LR2 supports Dense Wavelength Division Multi- 10GbE LAN Phy plexing (DWDM) 10Gbps SONET/ 10G Fibre Channel SDH interfaces and DWDM OTU2 10Gbps Ethernet applications. OTU2e There are up to forty variations of OTU2f this TOM, but the value TOM10G-Dn-LR2 is used to pre-provi- OTU2v (DTF) sion this TOM type in the management interfaces. The variations are named TOM-10G-Dn-LR2 (where the n equals 18-37 and 40-59). Each variation of the TOM-10GDn-LR2 transmits at a wavelength spaced at 100GHz on the Cband9. Field-replaceable, long-reach, 10G SONET OC-192 Small Form Factor Pluggable SDH STM-64 (XFP) optical transceiver. 10GbE WAN Phy The TOM-10G-Cn-LR2 supports Coarse Wavelength Division Multi- 10GbE LAN Phy plexing (CWDM) wavelengths. OTU2 There are six variations of this TOM type. The variations are named TOM-10G-Cn-LR2 (where the n equals 47,49,51,53,55 and 57). Each variation of the TOM10G-Cn-LR2 has a 20nm wavelength spacing, covering wavelengths 1471nm to 1571nm. OTU2e OTU2v (DTF)
XFP
Infinera Corporation
Page 3-19
Description
Field-replaceable, long-reach, 10G SONET OC-192 Small Form Factor Pluggable SDH STM-64 (XFP) tunable optical transceiver. 10GbE WAN Phy The TOM-10G-DT-LR2 is tunable across the the DWDM channels in 10GbE LAN Phy the ITU 100GHz grid as well as 10G Fibre Channel channels that have a 50GHz offset OTU2 from the ITU 100GHz grid. OTU2e ITU Channels 17.5 through 59 (with the exception of channels 38, OTU2f 38.5, 39 and 39.5) are supported OTU2v (DTF) on the TOM-10G-DT-LR2.
SFP
SIM-T-2-2.5GM
SONET OC-3 The 2.5G Multi-rate DWDM TOM converts client side optical signals 1G Fibre Channel to and from serial electrical sig 2G Fibre Channel nals. 1GbE There are forty variations of this ESCON TOM type. The variations are named TOM-MR-Dn-LR2 (where FICON the n equals 18-37 and 40-59). OTU-1 Each variation of the TOM-MR SD-SDI DWDM-LR2 transmits at a specific wavelength spaced at 100GHz on HD-SDI the C-band, covering channels 18 DVB-ASI to 37 and channels 40 to 59 TOM-MR-Cn-LR2 (n=47,49,51,53,55,57, 59,61) SFP Field-replaceable, 2.5G Small Form Factor Pluggable (SFP) module. SONET OC-48 SONET OC-12 SIM-T-2-2.5GM
SONET OC-3 The 2.5G Multi-rate CWDM TOM converts client side optical signals 1G Fibre Channel to and from serial electrical sig 2G Fibre Channel nals. 1GbE There are eight variations of this ESCON TOM type. The variations are named TOM-MR-Cn-LR2 (where FICON the n equals 47, 49, 51, 53, 55, 57, OTU-1 59, 61). Each variation of the SD-SDI TOM-MR-CWDM-LR2 has a 20nm HD-SDI wavelength spacing, covering wavelengths 1471nm to 1611nm. DVB-ASI
Infinera Corporation
Release 2.0
Page 3-20
TOM Type
TOM-10G-SR0
XFP
Field-replaceable, short-reach, 10GbE LAN Phy 10G XFP optical transceiver oper- 10G Fibre Channel ating at 850nm. The TOM-10GSR0 is intended for use with multimode fiber. Field-replaceable, short-reach SONET OC-192 10G XFP optical transceiver oper- SDH STM-64 ating at 1310nm. 10GbE WAN Phy 10GbE LAN Phy 10G Fibre Channel
SIM-T-1-10G SIM-T-1-10GP SIM-T-1-10GM SIM-T-1-10GT SIM-T-1-10G SIM-T-1-10GP SIM-T-1-10GM SIM-T-1-10GT SIM-T-1-10G SIM-T-1-10GP SIM-T-1-10GM SIM-T-1-10GT
TOM-10G-SR1
XFP
TOM-10G-IR2
XFP
SONET OC-192 SDH STM-64 10GbE WAN Phy 10GbE LAN Phy 10G Fibre Channel OTU2 OTU2e
TOM-10G-LR2
XFP
Field-replaceable, long-reach 10G SONET OC-192 XFP optical transceiver operating SDH STM-64 at 1550nm 10GbE WAN Phy 10GbE LAN Phy 10G Fibre Channel OTU2 OTU2e
TOM-8G-XSM-LC-L
XFP
Field-replaceable Single Mode, 8G 8G Fibre Channel Long Wavelength Laser, Long Distance
SIM-T-1-10GP SIM-T-1-10GM
Infinera Corporation
Page 3-21
Description Field-replaceable, short-reach, 2.5G multi-rate SFP optical transceiver operating at 1310nm.
Infinera Corporation
Release 2.0
Page 3-22
TOM-1G-LX
SFP
Field-replaceable, long-reach, 1Gb 1GbE Ethernet SFP optical transceiver 1G Fibre Channel operating at 1310nm. 2G Fibre Channel
Infinera Corporation
Page 3-23
Description Field-replaceable, extended distance 1Gb Ethernet SFP optical transceiver operating at 1550nm. OSC TOM
TOM-100M-C45-L2
SFP
Field-replaceable, supports the ATN Optical Supervisory Channel (OSC) operating at OSC at 1451nm. Electrical TOMs
Fast Ethernet
AMM-A
Note: The following TOMs have electrical interfaces, unlike all of the above TOMs, which are optical interfaces. In
addition, all of these electrical TOMs are uni-directional, meaning they either receive or transmit but not both. TOM-1.485HD-RX BNC Field-replaceable Small Form Fac- HD-SDI: tor Pluggable (SFP), High-definiSMPTE 292M tion Serial Digital Interface (HD SD-SDI: SDI) 1.485G receiver. SMPTE 259M-C, SMPTE 344M DVB-ASI: EN 50083-9 TOM-1.485HD-TX BNC Field-replaceable Small Form Fac- HD-SDI: tor Pluggable (SFP), High-definiSMPTE 292M tion Serial Digital Interface (HD SD-SDI: SDI) 1.485G transmitter. SMPTE 259M-C, SMPTE 344M DVB-ASI: EN 50083-9 TOM-1.4835HD-RX BNC Field-replaceable Small Form Fac- HD-SDI: tor Pluggable (SFP), High-definiSMPTE 292M tion Serial Digital Interface (HD SD-SDI: SDI) 1.4835G receiver. SMPTE 259M-C, SMPTE 344M DVB-ASI: EN 50083-9 SIM-T-2-2.5GM SIM-T-2-2.5GM SIM-T-2-2.5GM
Infinera Corporation
Release 2.0
Page 3-24
Description
Field-replaceable Small Form Fac- HD-SDI: tor Pluggable (SFP), High-definiSMPTE 292M tion Serial Digital Interface (HD SD-SDI: SDI) 1.4835G transmitter. SMPTE 259M-C, SMPTE 344M DVB-ASI: EN 50083-9
TOM-1G-BASE-T
RJ-45
Field-replaceable Small Form Fac- 1GbE tor Pluggable (SFP) converts electrical analog signals to SFP compatible output.
SIM-T-2-2.5GM
Infinera Corporation
Page 3-25
OFM-4-D-AV-5255
Photo Diodes
OFM-4-D-AV-4851 4-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-4-D-AV-4447 4-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-4-D-AV-4043 4-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
Infinera Corporation
Release 2.0
Page 3-26
Photo Diodes
OFM-4-D-AV-3033 4-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-4-D-AV-2629 4-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-4-D-AV-2225 4-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-4-D-AV-1821 4-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-5657 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-5455 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-5253 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-5051 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-4849 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-4647 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-4445 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
Infinera Corporation
Page 3-27
Photo Diodes
OFM-2-D-AV-4041 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-3637 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-3435 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-3233 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-3031 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-2829 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-2627 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-2425 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-2223 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-2021 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
OFM-2-D-AV-1819 2-Channel DWDM OADM Module with Express Port, Variable Optical Attenuators (VOAs) and
Photo Diodes
CWDM OFMs (Passive OFMs)
Infinera Corporation
Release 2.0
Page 3-28
Infinera Corporation
Page 3-29
OFM-1-C-A-51
OFM-1-C-A-53
OFM-1-C-A-55
OFM-1-C-A-57
OFM-1-C-A-59
OFM-1-C-A-61
Infinera Corporation
Release 2.0
Page 3-30
OUT
IN
OUT
IN
infn_029
Infinera Corporation
Page 3-31
infn_028
(DCM) through a front panel, duplex optical cable Note: The length of the dispersion compensation fiber depends upon the DCM type
Equalizes chromatic dispersion of different frequency components having different propagation
speeds
Reverses the dispersion effect of transmission fiber and restores the optical signal
Infinera Corporation
Release 2.0
Page 3-32
System Interfaces
System Interfaces
The ATNs provide several external interfaces as described in the following sections:
Management Interfaces on page 3-32 Transport Interfaces on page 3-33 Multi-chassis Interconnect Interfaces on page 3-35 Input/Output Alarm Contacts and Relays on page 3-36 System LEDs on page 3-37
Management Interfaces
Infinera network elements provide multiple craft interfaces for local user access to network management and Operations, Administration, Maintenance and Provisioning (OAM&P) functions. A Data Communication Network (DCN) interface for remote access is also provided. Note: In case of a multi-chassis system, the physical ports (corresponding to the various management interfaces) on the AMM of the main chassis (and not the expansion chassis) must be used for connecting management devices to the ATNs. For more information on Multi-chassis systems, see Multi-Chassis Systems on page 3-53. Following is a list of external interfaces that can be used to facilitate the connection of management devices to the ATNs.
DCNAn auto-negotiating 10/100Mbps Ethernet RJ-45 interface. There is one DCN interface per
network element that can be used by Operations Support System (OSS) personnel to manage the network element remotely. OSS personnel can use any of Infinera Network Management Software applications, such as the Infinera DNA, Infinera ATN GNM, SNMP agent or the CLI, to manage the local network element or any subtending network elements utilizing this network element as a gateway. The DCN interface is located on the front panel of the ATN Management Module (AMM). Note: The DCN port is an auto-negotiating 10/100Mbps Ethernet RJ-45 interface. Hence for its physical connectivity to the Ethernet switch/router/hub, please ensure that the port on the Ethernet switch/hub/router is also configured to perform auto-negotiation. If the peer port is not configured for auto-negotiation, then it can lead to Spanning Tree protocol failure due to duplex mismatch, which may lead to loss of management connectivity.
Craft serial DCEAn RJ-45 port that provides a serial interface to access the network element. The
Craft serial DCE provides access to the Commissioning Command Line Interface (CCLI) for initial commissioning of the network element, as well as the Command Line Interface (CLI) for OAMP functions. Maintenance personnel can use this interface for managing the local network element or any
Infinera Corporation
Page 3-33
subtending network elements utilizing this network element as a gateway. This interface is located on the front panel of the AMM.
Craft EthernetA 10Mbps Ethernet RJ-45 interface. This interface can be used to locally access
the network element through the Infinera GNM or CLI. Maintenance personnel can use this interface for managing the local network element or any subtending network elements utilizing this network element as a gateway. This interface is located on the front panel of the AMM. Note: Managing subtending network elements is supported from ATN CLI, but not from ATN GNM. Maintenance personnel can telnet to a local node and then perform a nested telnet to the subtending network elements.
OSCThe OSC is a 100Mbps Ethernet signal at 1451nm. There are two OSC interfaces, OSC-E
and OSC-W, corresponding to the East and West directions respectively that facilitate inter node communication. The OSC interfaces are implemented on the front panel of the AMM and are accessible via two SFP ports. Note: DCN, Craft Ethernet and OSC ports are disabled on an ATC-A configured as an expansion chassis. Refer to Infinera ATN GNM User Guide and Infinera ATN CLI User Guide for more details on how to use these interfaces to access the corresponding network management applications.
Transport Interfaces
The transport interfaces carry the user data. Two types of transport interfaces are provided as described below:
Infinera Corporation
Release 2.0
Page 3-34
System Interfaces
Client/Trib Interfaces
The client/trib interfaces are the ingress/egress points of the customer signals into/out of the ATN. These signals can be added/removed at a terminal site, or an Add/Drop site. The following client/trib signals are supported:
SONET OC-192 SONET OC-48 SONET OC-12 SONET OC-3 SDH STM-64 SDH STM-16 SDH STM-4 SDH STM-1 10GbE LAN Phy 10GbE WAN Phy 1GbE 1G Fibre Channel 2G Fibre Channel 8G Fibre Channel 10G Fibre Channel Enterprise Systems Connection (ESCON) 200M Fibre Connectivity (FICON) 1G Video High Definition 1.485G (HD-SDI) Video High Definition 1.4835G (HD-SDI) Video Standard Definition 270M (SD-SDI) Digital Video Broadcasting 270M (DVB-ASI) DV6000 OTU1 OTU2 OTU2e OTU2f DTF or OTU2v
Infinera Corporation
Page 3-35
Line Interface
The supported line interfaces are:
Up to 40 DWDM line-side channels in combination with an OSC to provide up to 400Gbps transport
and in-band communications between network elements. The line-side channels include:
OTU2 (10.7G) OTU2e (11.1G) OTU2f (11.3G) 10GbE DTF or OTU2v 3R output of 2.7Gbps and lower client signals Up to eight CWDM line-side channels in combination with an OSC to provide transport and in-band
The line side optical interface carries the aggregate signal coming into/out of the ATNs. The line side signal has the following characteristics:
Supports up to 40x10Gbps channels and the 100Mbps OSC Enhanced FEC for 1E-15 end-to-end BER Transport of client signals ranging from 155Mbps to 10Gbps.
For more details on the optical characteristics of the line interfaces, refer to Infinera ATN Hardware Description Guide.
Infinera Corporation
Release 2.0
Page 3-36
System Interfaces
The NC ports allow controller cards (AMMs) to communicate with controllers present on other chassis. Note: See Multi-chassis Functional Components on page 3-55 for details on the number and types of chassis allowed in a multi-chassis system.
Parallel Telemetry
The ATC provides five external alarm inputs of which four are user-customizable environmental alarm input contact sets (through opto-isolators) and one is dedicated to the ACO. Each alarm input contact set consists of a signal and return contact (two contacts). When activated, a user-customized alarm set will generate a customized alarm. The status of all customizable alarms are accessible through the management applications. The ATC provide ten alarm output contact sets of which four are user-customizable parallel telemetry output contact sets using latching, form-c relays. The control relays are latching, meaning they maintain their relay position (open or closed) even during a power failure. Each output contact set consists of normally-closed (NC), normally-open (NO) and common contacts (three contacts). The alarm outputs are controlled by the AMM. Three alarm output contact sets each are reserved for visual and audible indicators.
Office Alarms
The ATN reserves the following office dry alarm output contact sets for connection to the alarm grid:
Critical Audible Critical Visual Major Audible Major Visual Minor Audible Minor Visual
Infinera Corporation
Page 3-37
Each set consists of normally-closed (NC), normally-open (NO) and common contacts.
Alarm Cutoff
The ATC provides an alarm cutoff (ACO) function so that users can mute audible alarms while other types of alarm indications persist. The ACO is implemented with a front panel push button and a front panel LED. When the front panel ACO push button is pressed, all the current outstanding audible alarms (of all severities) are silenced and the ACO LED is illuminated. The illuminated ACO LED indicates that one or more audible alarms are present, but the audible indicators have been suppressed. Any subsequent alarms will trigger audible alarms. Alarm acknowledgement does not change the ACO LED state. The activation and de-activation of ACO for a single alarm is simple. When an alarm occurs, and a user triggers ACO, the audible alert becomes mute and the ACO LED is lit. When the alarm clears, the ACO LED is dimmed. When multiple alarms occur while ACO is in effect, the ACO activation/de-activation behavior is more complex. Consider the case in which an initial alarm, called Alarm X, is silenced by a user via ACO. At this point, the audible alarm is mute, and the ACO LED is lit. Now, if another alarm, called Alarm Y, is subsequently raised before Alarm X clears, the audible alert becomes audible again and the ACO LED dims. At this point, there are two possible scenarios:
If the initial Alarm X clears, but Alarm Y remains active, the audible alert remains audible and the
ACO LED remains dim. This is because Alarm Y was not explicitly silenced with the ACO feature. The user may trigger ACO once again to silence the audible alarm and light the ACO LED. The ACO LED will dim once Alarm Y clears
If Alarm Y clears, but Alarm X remains active, the audible alarm returns to a mute state and the ACO
LED relights. This reflects the fact that the initial Alarm X was muted with ACO. The ACO LED will dim once Alarm X clears. In addition to the front panel push button, ACO can also be triggered remotely through management applications, or through the reserved ACO input alarm contact set. Note: The ACO function is local to the chassis. It does not affect the audible alarm state in other chassis.
System LEDs
The Infinera ATN features a complete set of chassis-level LEDs that convey the operational status of the network element. Each chassis houses Critical, Major, and Minor LEDs that convey the severities of current outstanding alarms within the chassis. All field-replaceable modules (except passive OFMs and OFM-1-OSC) house LEDs to indicate its power and fault status. For further details about the system LEDs, see Local Alarm Summary Indicators on page 4-6.
Infinera Corporation
Release 2.0
Page 3-38
Optical Transport
The ATC and corresponding circuit packs provide optical transport capability. Figure 3-5 illustrates the traffic flow and major components along the data path. Figure 3-5 illustrates an example configuration of the ATC. The inter-connectivity between the circuit packs could vary based on the network element configuration and customer application. Figure 3-5 ATC Digital and Optical Transport Architecture
Tributary Adaptation
As shown in Figure 3-5, the ATC data plane performs a tributary adaptation function where any variety of 10Gbps client signals are adapted to an ITU-compliant optical signal for transmitting on the line fiber. The tributary adaptation includes conversion of clients optical signals into electrical signals (performed in the TOMs), encapsulation of 10Gbps payload into a G.709 Optical Transport Unit referred to as the OTU2 or OTU2e frame, (performed in the SIMs) and conversion of the OTU signals into ITU-compliant DWDM optical signals.
Infinera Corporation
Page 3-39
Use of the ITU channel plan allows the ATN to terminate up to 40 channels (in a DWDM system) or eight channels (in a CWDM system) in increments of 10G. For more information on the list of supported client interfaces, see Client/Trib Interfaces on page 3-34.
client signal format The OTU frame is designed to accommodate 10Gbps payload formats (see the list of supported client interfaces in Client/Trib Interfaces on page 3-34).
Infinera Corporation
Release 2.0
Page 3-40
A client signal (such as SONET OC-192, 10GbE etc) is adapted at the optical channel payload unit
(OPU) layer by adding an overhead (OH) and adjusting the client signal rate to the OPU rate.
Once adapted, the OPU is mapped into the optical channel data unit (ODU) by adding an overhead
(OH).
The ODU is then mapped into an optical channel transport unit (OTU) by adding an overhead and
lengths, which then form the optical multiplexing sections (OMS). The Optical Multiplex Section (OMS) layer corresponds to the signal between two multiplexers.
Several optical channels can be mapped into the optical multiplexing section (OMS) and then trans-
ported via optical transmission sections (OTS) layer. The Optical Transport Section (OTS) is an optical layer corresponding to a set of wavelengths.
The OCh, OMS and OTS layers each have their own overhead for management purposes at the
optical level. The overhead of these optical layers is transported outside of the ITU grid in an out-ofband channel, the optical supervisory channel (OSC).
64 signals.
OTU2e format which provides a line rate of 11. 1Gbps and can be adapted to service 10GbE LAN
signals.
OTU2f format which provides a line rate of 11.3Gbps and can be adapted to service 10G Fibre
Channel
Infinera Corporation
Page 3-41
Figure 3-7 shows the generalized OTUk structure. Figure 3-7 Optical Transport Unit (OTUk) Frame Structure
functions to support transport through one or more optical channels. It facilitates transmission of information between OTU termination points.
Optical Data Unit k Overhead (ODUk-OH) The ODUk-OH is added to the ODUk information pay-
load to create the ODUk. It consists of sections dedicated to end-to-end ODUk path and six levels of Tandem Connection Monitoring (TCM). It also includes necessary overhead bytes to provide performance monitoring, maintenance and operational functions.
Optical Path Unit k Overhead (OPUk-OH) The OPUk-OH is added to the OPUk information pay-
load to create the OPUk. It includes information that supports adapting of client signals.
Optical Path Unit k Payload (OPUk payload)The OPUk is the information structure used to adapt
client information for transport over an optical channel. It comprises client information together with any overhead needed to perform rate adaptation between the client signal rate and the OPUk payload rate and other OPUk overhead supporting the client signal transport. The OPUk capacity for 10Gbps is supported.
Optical Transport Unit k Forward Error Correction (OTUk-FEC)The OTUk-FEC is used to support
Forward Error Correction and corresponds to the ITU G.709 standard OTUk FEC. The ITU G.709 standard supports Forward Error Correction (FEC) in the OTU frame and is the last part added to the frame. FEC provides a method to significantly reduce the number of transmitted errors due to noise, as well as other optical phenomena that occur at high transmission speeds. The Infinera ATN supports ITU G.709 standard eFEC (enhanced FEC) along with the OTUk-FEC.
Infinera Corporation
Release 2.0
Page 3-42
Digital Transport
The SIM-T-1-10GT and SIM-A-8-2.5GMT circuit packs in an ATN provide digital transport capability. Figure 3-5 on page 3-38 illustrates the traffic flow and major components along the data path. The sections that follow describe the data plane functions.
Tributary Mapping
As shown in Figure 3-5 on page 3-38, the ATC data plane performs a tributary adaptation function where any variety of client signals (see Client/Trib Interfaces on page 3-34) are adapted to an ITU-compliant signal for transmitting on the line fiber. The tributary adaptation includes conversion of clients optical signals into electrical signals (performed in the TOMs), encapsulation of the payload into a Digital Transport Frame, referred to as the DTF, (performed in the SIM-T-1-10GT or SIM-A-8-2.5GMT) and conversion of the electrical signals into the ITU-compliant optical signals. The DTF architecture (see Digital Transport Frame on page 3-42) is designed to support transport for a variety of client signals (i.e. all signal rates supported by the SIM-T-1-10GT and SIM-A-82.5GMT on the ATN) through the network, irrespective of the actual payload format.
client signal format The DTF is designed to accommodate a mix of payload formats, for example, 155Mbps, 1GbE, 10Gbps or any other signal rate supported by the SIM-T-1-10GT or SIM-A-8-2.5GMT modules of an ATN. The DTF accommodates the network layers as described in the sections that follow. The DTF framing is performed in the SIM-T-1-10GT or SIM-A-8-2.5GMT modules of an ATN.
Infinera Corporation
Page 3-43
DTF Line Layer on page 3-43 DTF Path Layer on page 3-43
Figure 3-8 below shows the digital transport network layers, and illustrates the network segments over which each layer is carried. Figure 3-8 DTF Layers
Infinera Corporation
Release 2.0
Page 3-44
and maintenance alarms. The DTP layer corresponds to the digital optical segments shown in Figure 3-8 on page 3-43
14 15
16
4080
The DTF overhead contains the characteristic information for the DTF Section, DTF Line, and DTF Path layers of the network. The DTF Overhead is segmented into the following groups:
Digital Transport Frame Alignment Overhead (DTFA-OH)The DTFA-OH provides frame and multi-
responds to the G.709 OTUk and to the SONET Section Layer overhead and SDH Multiplex Section Layer overhead. It includes necessary overhead bytes to provide the performance monitoring and maintenance functions at the section layer.
DTF Line Overhead (DTL-OH) The DTL-OH supports DTF Line layer. This information corre-
sponds to the G.709 ODUk Tandem Connection (ODUkT) and to the SONET Line overhead. The G.709 supports six ODUkTs; Infinera Digital Frame Structure supports one DTL. It also includes necessary overhead bytes to provide performance monitoring, maintenance and APS functions at the line layer.
DTF Path k Overhead (DTPk-OH) The DTPk-OH is used to support a DTF DTPk. This information
corresponds to the G.709 ODUk Path (ODUkP) and to the end-to-end portion of the SONET/SDH path overhead. The Digital Frame Structure supports 2.5Gbps and 10Gbps DTPks corresponding to k=2.5 and k=10 respectively. The DTPk-OH contains necessary overhead bytes to provide end-toend performance monitoring and path level tracing.
Digital Transport Payload Envelope k (DTEk)The DTEk is the information structure used to adapt
client information for transport over a DTF Path k. It comprises Digital Transport Payload Envelope k Payload (DTEk-Payload) together with any Digital Transport Payload Envelope k Overhead (DTEkOH) needed to perform rate adaptation between the client signal rate and the DTEk-Payload rate,
Infinera Corporation
Page 3-45
and other overhead supporting the client signal transport. This overhead is adaptation specific. The DTEk capacities for 2.5Gbps and 10Gbps are supported.
FEC Overhead (FEC-OH)The FEC-OH is used to support Forward Error Correction. This informa-
tion corresponds to the G.709 OTUk FEC and is on the 10Gbps digital channel.
Add/Drop
The ATN supports a wide variety of optical add/drop modules for granular and flexible network design engineering. Depending on add/drop modules used, 0% to 100% add/drop capability can be achieved at any given site, while any remaining channels are optically expressed through the site.
Regeneration
The ATN system data plane implements optical regeneration on the following SIMs:
SIM-T-1-10GM Supports OTU2, OTU2e, and OTU2f regeneration. OTU2f is only supported for a
SIM configured for G.709 FEC, and is not supported with EFEC.
SIM-T-1-10GP Supports OTU2, OTU2e, and 10GbE LAN (supported in low latency mode) regen-
eration
SIM-T-1-10GT Supports OTU2v (DTF) regeneration SIM-T-2-2.5GM Supports regeneration of all signals from 155Mbps to 2.7Gbps
Digital Conditioning
The ATN system data plane includes FEC encoder/decoder for every channel that is digitally add/dropped or regenerated at every ATN (for all SIMs with the exception of SIM-T-2-2.5GM) to improve the overall BER. For the SIM-T-1-10G, SIM-T-1-10GP and SIM-T-1-10GM, Infinera implements standard G.709 FEC and an enhanced FEC algorithm (which has a higher coding gain than required by the standard G.975.1 Appendix
Infinera Corporation
Release 2.0
Page 3-46
I.4). The Enhanced FEC algorithm provides a coding gain of greater than 8.0dB at 10Gbps at BER of 1e-15 with a 7% overhead ratio. For the SIM-T-1-10GT and SIM-A-8-2.5GMT, Infinera implements standard G.709 FEC and an enhanced FEC algorithm which has a higher coding gain than required by the standard G.709 RS(255,239) algorithm. The Enhanced FEC algorithm provides a coding gain of 8.7dB at 10Gbps at BER of 1e-15 with the same 7% overhead ratio as the standard G.709 FEC algorithm. Note: FEC and enhanced FEC are not supported on the interfaces of the SIM-T-2-2.5GM.
Optical Conditioning
The ATN supports optical conditioning via Dispersion Compensation Modules (DCMs) for fine-tuning of the optical signals along the link. The ATN provides in-line access to DCMs, for compensation of the line signal. See Dispersion Management Chassis (DMC) Overview on page 3-30 for more information.
Optical Amplification
The ATN Amplifier Modules (AAMs) in the ATN provide optical amplification of an aggregate optical signal and enable extended reach between ATN units. Infinera ATN offers low power amplifiers (with up to +13dBm of output power) and high power amplifiers (with up to +17dBm of output power).
OTU frame in OTU-based line cards to transport across the Digital Optical Network. The OTU architecture provides digital performance data that is independent of the client signal payload type and that can be monitored at circuit termination locations in the network. The OTU overhead bytes are designed to provide performance monitoring capabilities at transport layers analogous to SONET/ SDH layering. Also, the OTU includes FEC overhead bytes, providing FEC performance data for BER computation on each link and on each end-to-end channel. For more information on the supported PM parameters, see OTU PM Parameters on page B-7.
As described in Digital Transport Frame on page 3-42, client signals are encapsulated within a
DTF to transport across the Digital Optical Network. The DTF architecture provides digital performance data that is independent of the client signal payload type and that can be monitored both at circuit terminations and at intermediate locations in the network. The DTF overhead bytes are designed to provide users performance monitoring capabilities at transport layers analogous to SONET/SDH layering. Also, the DTF includes FEC overhead bytes, providing FEC performance data for BER computation on each digital link and on each end-to-end digital channel. The DTF architecture includes the DTF Section and DTF Path (DTP) layers. Digital performance monitoring is supported at each of these layers, thereby enhancing troubleshooting and fault isolation in the transport domain.
Infinera Corporation
Page 3-47
For more information on the supported PM parameters, see DTF PM Parameters on page B-9 and DCh PM Parameters on page B-12 Note: The digital PM data is available for all SIMs except the SIM-T-2-2.5GM.
protection (includes a working and protection facility) for line services as described in Optical Subnetwork Connection Protection (O-SNCP) on page 4-89.
Infinera Corporation
Release 2.0
Page 3-48
Control Plane (over OSC) on page 3-51) The intra-chassis and inter-chassis control planes provide redundant control paths to enhance the overall reliability of the network element. The following sections describe the redundancy provided at the hardware level. The IQA NOS ATN software utilizes the hardware features and enables system level redundancy.
Infinera Corporation
Page 3-49
Infinera Corporation
Release 2.0
Page 3-50
Infinera Corporation
Page 3-51
Infinera Corporation
Release 2.0
Page 3-52
Infinera Corporation
Page 3-53
Multi-Chassis Systems
As discussed in Inter-chassis Control Plane on page 3-49, the inter-chassis control path enables the configuration of a multi-chassis system. The chassis are interconnected through the NC ports on the AMM front panel. There are two NC ports corresponding to uplink and downlink directions. This allows for multiple chassis to be interconnected. The Infinera ATN network element can be installed in a multi-chassis configuration that consists of up to ten ATCs (consisting of up to eight ATC-A chassis and up to two ATC-P chassis) installed on a single rack or multiple racks being managed as a single ATN node. One ATC-A is termed the main chassis and houses the node controller AMM. The remaining ATC-A or ATC-P chassis are termed expansion chassis. The AMMs included in the expansion chassis are termed as shelf controllers. Note: A Multi-Node configuration consists of multiple ATNs (each consisting of one ATC-A and optionally one or more ATC-Ps) connected together or stacked at a common location. Each ATN has a unique IP address and is managed individually. Multiple ATNs can be connected together to represent a single data path. Multi-node configurations are supported in ATN Release 1.0 only. In ATN Release 2.0, all multi-node configurations created in ATN Release 1.0 need to be migrated to a multi-chassis configuration.
Multi-Chassis Configuration
In a multi-chassis configuration, up to eight ATC-A chassis and two ATC-P chassis installed on a single rack or multiple racks, are managed as a single node. The active chassis (ATC-A) is the only chassis that is managed and has an IP address. The passive chassis (ATC-Ps) are purely a passive extension of the ATC-A, and are used to house passive Optical Filter Modules (OFMs). The ATC-P is a managed object, but there is no management connectivity between the ATC-A and the ATC-Ps The Multi-Chassis configuration consists of
One ATC-A chassis designated as the Main Chassis and housing the controller (AMM) that acts as
the node controller. Note: ATC-P chassis can only be used as expansion chassis. Only ATC-As can be used as the main chassis.
The remaining chassis (can be an ATC-A or ATC-P chassis) are referred to as Expansion Chassis.
ATC-A expansion chassis house AMMs that act as shelf controllers. The node controller is responsible for terminating management requests and for managing the configuration database. Each of the shelf controllers provides a management view to the cards within its own chassis (the Expansion Chassis). The shelf controllers do not hold their own configuration databases. Up to two ATC-Ps can be provisioned as expansion chassis by using the ATN CLI, ATN GNM or DNA. The provisioned ATC-Ps are reflected in the management interface, but are not managed objects.
Infinera Corporation
Release 2.0
Page 3-54
Multi-Chassis Systems
The installation of a multi-chassis system requires some degree of planning in terms of the physical location of the racks and chassis within those racks.
Infinera Corporation
Page 3-55
Infinera Corporation
Release 2.0
Page 3-56
Multi-Chassis Systems
This includes the management interface ports (NC, DCN, craft), fan, PCMs, alarm input/output contacts, alarm LEDs, ACO, and lamp test. Table 3-5 summarizes whether each functional component is enabled or disabled on the Main or Expansion Chassis. In particular, note the following:
Alarm inputs and outputs operate on a per-chassis basis. ACO operates on a per-chassis basis. To silence any alarms, press the ACO button on each chassis
separately, or use the management interface to trigger ACO for each individual chassis.
The chassis-level LEDs operate on a per-chassis basis, and reflect the state of Critical, Major, and
Port/Interface Name Alarm Inputs Alarm Outputs PCM Fan Chassis-level LEDs NC Craft DCE Port Craft Ethernet Port DCN Port OSC ports ACO Lamp Test
Infinera Corporation
Page 3-57
Multi-chassis Provisioning
Provisioning a multi-chassis system is a simple extension to provisioning a single-chassis system. Detailed instructions on provisioning a multi-chassis system are provided in the Infinera ATN Turn-up and Test Guide. Some important provisioning constraints are listed below: Note: See Multi-Chassis Systems on page 3-53 for details on the number and types of chassis and line modules allowed in a multi-chassis system.
Only one chassis in a multi-chassis system may act as the Main Chassis. The Main Chassis is the first chassis to be commissioned in a multi-chassis system. The user can
set an ATC-A as a Node Controller (NC) during the initial commissioning of the node using the CCLI, however, the main chassis cannot be pre-provisioned through any software interface.
The Main Chassis must be installed and provisioned before installing and provisioning an Expansion
Chassis.
The Expansion chassis are pre-provisioned via the management interfaces (ATN CLI, ATN GNM, or
DNA) from the main chassis. During the initial commission of the Expansion Chassis, the ATC-As are defined as Shelf Controllers (SCs) via the CCLI.
Chassis are interconnected through the NC ports on the AMM using unshielded twisted pair
(straight-through) CAT5 Ethernet cables that conform to 100BaseTX (IEEE 802.3) specifications. The NC cables must not exceed 100 meters (328 feet) in length. Further details on interconnecting multiple chassis through the NC ports are provided in NC Cable Provisioning on page 3-57.
Each chassis has an ID number. The system automatically assigns the Main Chassis with the ID
number 1 during auto-creation. For Expansion Chassis, the user must assign each chassis with a unique chassis ID number from 2 to 10.
External management interfaces always communicate to the AMM on the Main Chassis through the DCN port or the OSC TOMs on the AMM. If an AMM on the Main Chassis is out-of-service or unreachable, then the entire network element is not reachable. This is true even if there are in-service AMMs present on the Expansion Chassis.
NC Cable Provisioning
Because redundancy is supported in a multi-chassis system, there are a number of possible configurations when interconnecting the NC ports between chassis. Depending on the level of redundancy at each chassis and the NC port connectivity topology, different levels of failure protection are provided. See the
Infinera Corporation
Release 2.0
Page 3-58
Multi-Chassis Systems
Infinera ATN Turn-up and Test Guide for recommended NC port configurations that offer varying levels of failure protection. Note: For more information on planning a Multi-Chassis or Multi-Node configuration, refer to the Infinera ATN Site Preparation and Hardware Installation Guide.
Infinera Corporation
Page 3-59
Infinera Corporation
Release 2.0
Page 3-60
Infinera Corporation
Page 3-61
SIM configured for G.709 FEC, and is not supported with EFEC.
SIM-T-1-10GP Supports OTU2, OTU2e, and 10GbE LAN (supported in low latency mode) regen-
eration
SIM-T-1-10GT Supports OTU2v (DTF) regeneration SIM-T-2-2.5GM Supports regeneration of all supported signals (from 155Mbps to 2.7Gbps)
Infinera Corporation
Release 2.0
Page 3-62
Infinera Corporation
CHAPTER 4
The OAM&P functions are accessible to both human and machine clients through a variety of management interfaces and applications, referred to as management applications in the rest of this chapter. In addition to OAM&P functions, IQA ATN provides intelligent power management control plane and management plane functions as described in the following sections:
ADAPT Power Management Control Plane Overview on page 4-64 IQA NOS ATN Management Plane Overview on page 4-71
Finally, IQA NOS ATN provides digital protection services based on industry standards, as described in the following section:
IQA NOS ATN Digital Protection Services on page 4-79
Infinera Corporation
Release 2.0
Page 4-2
Fault Management
Fault Management
IQA NOS ATN provides extensive fault monitoring and management capabilities that are modeled after Telcordia and ITU standards. All these capabilities are independent of the client signal payload type and provide the ability to identify, correlate and correct faults based on actual digital and optical performance indicators, leading to quicker problem resolution. Additionally, IQA NOS ATN communicates all state and status information of the network element automatically and asynchronously to all the registered management applications, thus maintaining synchrony within the network. IQA NOS ATN provides the following fault management capabilities to help users in managing and maintaining the network element:
Alarm surveillance functions that detect and report degraded conditions in the network element (see
ing the detection and clearing of defects (see Event Log on page 4-9).
In-service and out-of-service maintenance and troubleshooting tools (see Maintenance and Trou-
Alarm Surveillance
Alarm surveillance functions include:
Detection of defects in the ATNs and the incoming signals (see Defect Detection on page 4-2). Declaration of defects as failures (see Failure Declaration on page 4-3). Reporting failures as alarms to the management applications (see Alarm Reporting on page 4-3). Masking low priority alarms in the presence of high priority alarms (see Alarm Masking on page 4-
5).
Reporting alarms through local alarm indicators (see Local Alarm Summary Indicators on page 4-
6).
Configuring alarm reporting (see Alarm Configuration on page 4-7).
Defect Detection
IQA NOS ATN detects all hardware and software defects within the system. A defect is defined as a limited interruption in the ability of an item to perform a required function. The detected defects are analyzed and localized to the specific network site, network element, facility (or incoming signal) and circuit pack.
Infinera Corporation
Page 4-3
Failure Declaration
Defects associated with facilities/incoming signal are soaked for a pre-defined period before they are declared as failures. This measure prevents spurious failures from being reported. So, when a defect is detected on a facility, it is soaked for a time interval of 2.5 seconds (+/- 1 second) before the corresponding failure is declared. Similarly, when a facility defect clears, it is soaked for 10 seconds (+/- 2 seconds) before the corresponding failure is cleared. This eliminates pre-mature clearing of the failure. Defects associated with hardware equipment and temperature-related alarms are not soaked. The failure condition is declared as soon as the defect is detected. Similarly, the failure condition is cleared as soon as the defect is cleared.
Alarm Reporting
IQA NOS ATN reports hardware and software failures as alarms. Detection of a failure condition results in an alarm being raised which is asynchronously reported to all the registered management applications. The clearing of a failure results in clearing the corresponding alarm, which is again reported asynchronously to all registered management applications. IQA NOS ATN stores the outstanding alarm conditions locally and they are retrievable by the management applications. Thus, at any given time users see only the current standing alarm conditions. Alarm reporting is also dependent on the administrative state (see Administrative State on page 4-34) of the managed object and presence of other failure conditions and the user configuration, as described below:
Administrative StateAlarms are reported when the administrative state of a managed object and
its ancestor objects are unlocked. When the administrative state of an object or any of its ancestor objects are locked or in maintenance, alarms are not reported (except for the Loopback related alarms). IQA NOS ATN also supports alarms that indicate when a managed object is put in the Locked or Maintenance administrative state. The severity of these alarms can be customized via the ASAP feature (see Alarm Severity Assignment Profile Setting (ASAP) on page 4-9).
Alarm HierarchyAn alarm is reported only if no higher priority alarms exist for the managed object.
Thus, only alarms corresponding to the root cause of the fault condition are reported. This capability prevents too many alarms being reported for a single fault condition (see Alarm Masking on page 4-5).
User ConfigurationIQA NOS ATN provides users the ability to selectively inhibit alarm reporting
(see Alarm Reporting Control (ARC) on page 4-7). IQA NOS ATN reports each alarm with sufficient information, as described below, so that the user can take appropriate corrective actions to clear the alarm. For a detailed description of all the parameters of alarms
Infinera Corporation
Release 2.0
Page 4-4
Fault Management
reported to the management applications, refer to the corresponding user guide (the Infinera ATN GNM User Guide).
Alarm CategoryThis information isolates the alarm to a functional area of the system (see Alarm
(see Alarm Severity on page 4-5 for the list of supported severities).
Probable CauseThis information describes the probable cause of the alarm. This is a short
description of the detected problem. A detailed description is provided as Probable Cause Description.
Probable Cause DescriptionThis information is an elaboration of the Probable Cause, providing a
detailed description of the alarm and isolating the alarm to a specific area.
Service AffectingThis information indicates whether the given alarm condition interrupts data
plane services through the system or network. The two possible values are: SA for service affecting and NSA for non-service affecting. An alarm is reported as service-affecting if the alarm condition affects a hardware or software entity in the data plane, and the affected hardware or software entity is administratively enabled.
Source ObjectThis information identifies the managed object on which the failure is detected. LocationThis information identifies the location of the managed object as near end or far end,
when applicable.
DirectionThis information indicates whether the alarm has occurred in the receive direction or in
is derived from the system time. IQA NOS ATN provides users the ability to manually configure the system time or enable Network Timing Protocol (see Time-of-Day Synchronization on page 4-77) so that an accurate and synchronized time is reported for all alarms. The time and date information allows a root cause analysis of failures across network elements and networks.
TypeAs described in PM Thresholding on page 4-43, IQA NOS ATN supports performance mon-
itoring and thresholds, enabling early detection of degradation in system and network performance. The threshold crossing conditions are handled utilizing the same mechanism as alarms. The type field indicates whether the reported condition is an alarm or a threshold crossing condition. IQA NOS ATN records all the current alarms with alarm details, as described above, in an alarm table. The alarms are persisted in the AMM across reboots. After a system reboot or an AMM reboot, the alarms in persistent storage are compared to the current system status in order to remove any cleared alarms and maintain only the current outstanding alarms. Upon reboot of the AMM, all alarms that were asserted before the reboot are reasserted after the AMM recovers. Eight minutes after the system becomes active, any alarms not re-detected by the system are remitted. This ensures that fault conditions which cleared during the AMM reset are cleared if the conditions that originally caused the alarms are no longer present. Refer to the Infinera ATN Maintenance and Troubleshooting Guide for the detailed description of all the alarms reported by IQA NOS ATN and the corresponding clearing procedures.
Infinera Corporation
Page 4-5
Alarm Category
IQA NOS ATN categorizes the alarms into the following types:
Facility AlarmAlarms associated with the line and tributary incoming signals. For example: Optical
Unknown Equipment.
Communications AlarmAlarms associated with communication failures within the network ele-
ment and between network elements. For example: Loss of Ethernet Link.
Software Processing AlarmAlarms associated with software processing errors. For example, Soft-
Alarm Severity
Each alarm and TCA generated by IQA NOS ATN has one of the following default severity levels:
CriticalIndicates that a service affecting condition has occurred and an immediate corrective
action is required. This severity is reported, for example, when a managed object is rendered out-ofservice by a failure and must be restored to operation in order to recover lost system functionality.
MajorIndicates that a service affecting condition has developed and an urgent corrective action is
required. This severity is reported, for example, when there is a severe degradation in the capability of the managed object and full capability must be restored in order to recover lost system functionality.
MinorIndicates the existence of a non-service affecting fault condition and that corrective action
should be taken in order to prevent a more serious (for example, service affecting) fault. Such a severity is reported, for example, when the detected alarm condition is not currently degrading the capacity of the managed object.
WarningIndicates the detection of a potential or impending service affecting fault, before any sig-
nificant effects have been felt. Action should be taken to further diagnose (if necessary) and correct the problem in order to prevent it from becoming a more serious service affecting fault. Users can customize the severity associated with an alarm or Threshold Crossing Alert (TCA) through the management applications (see Alarm Severity Assignment Profile Setting (ASAP) on page 4-9.)
Alarm Masking
IQA NOS ATN provides an alarm masking feature that complies with, and extends, GR-253 Section 6.2.1.8.2 and GR-474 Section 2.2.2.1. The network element masks (suppresses) lower layer alarms associated with the same root cause as a higher priority alarm. This prevents logs and management applications from being flooded with redundant information. Suppression is based on a logical hierarchy. For instance, when a network element experiences an Optical Loss of Signal (OLOS) failure, the network element will report the OLOS alarm, but the associated Channel - Loss of Frame (LOF) alarms, and all other associated lower layer alarms, are suppressed. These conditions are still retrievable by request. The masked condition is neither reported to the management applications nor recorded in the alarm table.
Infinera Corporation ATN System Description Guide Infinera Proprietary and Confidential Release 2.0
Page 4-6
Fault Management
alarm conditions of the chassis. A chassis level visual alarm indicator is lit if there is at least one corresponding outstanding alarm condition within the chassis. The following bay level LED indicators are provided:
Critical LEDWhen lit, indicates the presence of critical alarm(s) within the chassis. Major LEDWhen lit, indicates the presence of major alarm(s) within the chassis. Minor LEDWhen lit, indicates the presence of minor alarm(s) within the chassis. Chassis Level Office Alarm IndicatorsAs described in Office Alarms on page 3-36, the ATNs pro-
vide alarm output contacts to support chassis level visual and audio indication of critical, major and minor alarms. As described in Alarm Cutoff on page 3-37, ACO buttons and ACO LEDs are also supported.
Card Level Visual IndicatorsAll circuit packs include LEDs to indicate the card status. In general,
Note: By default all critical, major, and minor alarms affect the corresponding chassis LED status.
Infinera Corporation
Page 4-7
Alarm Configuration
The following features are used to customize the alarm reporting to the management applications and interfaces:
Alarm Reporting Control (ARC) (see below) Alarm Severity Assignment Profile Setting (ASAP) on page 4-9 Customizable Timer-Based Alarms on page 4-9
Infinera Corporation
Release 2.0
Page 4-8
Fault Management
Figure 4-1 ARC Behavior (Leave Outstanding Alarms vs. Clear Outstanding Alarms)
Figure 4-1 indicates that the ARC behavior is the same for alarm events that are raised during the ARC period (Scenario #1 and Scenario #2), regardless of whether ARC is set to Leave Outstanding Alarms or Clear Outstanding Alarms. When alarm conditions are raised and cleared during the ARC period (Scenario #1), the alarms are not reported to the management interfaces.
When alarm conditions are raised during the ARC period but are not cleared during the ARC period
(Scenario #2), the alarms are reported to the management interfaces only at the end of the ARC period, and the clearing event is reported to the management interfaces when the alarm is cleared. However, the ARC behavior is different when alarm events are raised before the beginning of the ARC period (Scenario #3 and Scenario #4), depending on whether ARC is set to Leave Outstanding Alarms or Clear Outstanding Alarms:
When ARC is configured to Leave Outstanding Alarms, any pre-existing alarms will remain outstand-
ing and a clearing event will be reported to the management interfaces when the alarm condition is cleared. In Scenario #3 the clearing event happens during the ARC period, and in Scenario #4 the clearing event happens after the ARC period.
When ARC is configured to Clear Outstanding Alarms, any pre-existing alarms are cleared when
alarm reporting is disabled and a clearing event is sent to the management interfaces at the start of the ARC period. If the alarm is cleared during the ARC period, the management interfaces will not receive another clearing event. If the alarm is still outstanding at the end of the ARC period, the manATN System Description Guide Release 2.0 Infinera Proprietary and Confidential Infinera Corporation
Page 4-9
agement interfaces will receive a new alarm event for the alarm, and then will receive a clearing event when the alarm is cleared.
Event Log
IQA NOS ATN provides an historical event log that tracks all significant events in the system (including alarms) and stores the events in a wrap-around buffer. Management interface sessions can retrieve the full history and track ongoing events in real time. Synchronization is maintained between the connected management interface and the network element. If a session communication failure occurs, the reconnected management interface can query the events that occurred during session failure.
Infinera Corporation
Release 2.0
Page 4-10
Fault Management
IQA NOS ATN records the following types of events in the event log:
Alarm related events, which include alarm raise and clear events. PM data thresholding related events, which include threshold crossing alerts. For more information,
or changes in the operation capability of the managed object. Event logs are stored in the persistent storage on the network element so that event logs are available after restarts and reboots. IQA NOS ATN stores up to 2000 events that are persisted across AMM reboots. Users can export the event log information in TSV format using management applications. Following are some of the important information stored for each event log record:
The managed object that generated the event. The time at which IQA NOS ATN generated the event. The event type indicating the event category, including: Update Event, which includes managed object create and delete events. Report Event, which includes security administration related event, network administration
Refer to the Infinera ATN Maintenance and Troubleshooting Guide for a list of events logged in an event log on ATNs.
Infinera Corporation
Page 4-11
page 4-11).
PRBS generation and detection (see PRBS Tests on page 4-22). Fibre Channel (FC) test signal generation (see Test Signal Generation for Fibre Channel Clients
on page 4-25)
GbE client termination point test signal generation and detection for the SIM-A-8-2.5GMT (see GbE
Client Termination Point Tests on page 4-26) In-service troubleshooting tools include:
Trace messaging, including OTU section TTI, DchCTP TTI, DTPCTP TTI, SONET/SDH J0 byte
insertion and monitoring (see Trace Messaging on page 4-27). The troubleshooting tools are accessible through the management applications by users with the Turn-up and Test (TT) access privilege.
Loopbacks
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. 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. Infinera ATN supports the following:
SIM-T-1-10G Loopbacks on page 4-12 SIM-T-2-2.5GM Loopbacks on page 4-13 SIM-T-1-10GT Loopbacks on page 4-14 SIM-A-8-2.5GMT Loopbacks on page 4-17 SIM-T-1-10GP and SIM-T-1-10GM Loopbacks on page 4-20
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. For
Infinera Corporation
Release 2.0
Page 4-12
Fault Management
more information on D-SNCP protection, see Digital Subnetwork Connection Protection (D-SNCP) on page 4-79.
SIM-T-1-10G Loopbacks
Figure 4-2 on page 4-12 through Figure 4-4 on page 4-13 show the loopbacks on the SIM-T-1-10G. Each of these loopbacks are described below its figure.
Client CTP Facility Loopback
A loopback is performed on the trib-side of 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
A loopback is performed on the trib-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
Infinera Corporation
Page 4-13
A loopback performed on the line-side of 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.
SIM-T-2-2.5GM Loopbacks
ATN supports loopbacks on the 2.5G Multi-rate Service Interface Modules (SIM-T-2-2.5GMs). Note: Electrical TOMs supported on the SIM-T-2-2.5GM are uni-directional TOMs and so loopbacks cannot be applied on them. Figure 4-5 on page 4-13 and Figure 4-6 on page 4-14 show the loopbacks supported on SIM-T-2-2.5GM. Each of these loopbacks are described below its figure.
Clear Channel Client CTP Facility Loopback
A loopback is performed on the trib-side of the SIM-T-2-2.5GM wherein the signal received from Rx port on the trib-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.
Infinera Corporation
Release 2.0
Page 4-14
Fault Management
A loopback is performed on the line-side of 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 4-7 on page 4-14 through Figure 4-12 on page 4-17 show the loopbacks on the SIM-T-1-10GT. Each of these loopbacks are described below its figure.
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
Infinera Corporation
Page 4-15
A loopback is performed on the line-side of the SIM-T-1-10GT wherein the signal received from the Rx port on the trib-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
A loopback is performed on the line-side of the SIM-T-1-10GT wherein the signal received from the Rx port on the trib-side TOM is looped back to the Tx port on the same TOM via the SerDes, tribside 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
Infinera Corporation
Release 2.0
Page 4-16
Fault Management
A loopback is performed on the trib-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 trib-side IFC10. This loopback verifies the DTF de-encapsulation performed in the IFC10.
Client CTP Terminal Loopback
A loopback is performed on the trib-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 trib-side IFC10s and the trib-side transponder processor. This loopback verifies the line side optics on the TOM and the SIM-T-1-10GT.
Client CTP Facility Loopback
Infinera Corporation
Page 4-17
A loopback is performed on the line-side of the SIM-T-1-10GT wherein the signal received from the Rx port on the trib-side TOM is looped back to the Tx port on the same TOM via the transponder processor. This loopback verifies the trib-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-13 on page 4-17 through Figure 4-18 on page 4-20 show the loopbacks on the SIM-A-8-2.5GMT. Each of these loopbacks are described below its figure.
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
Infinera Corporation
Release 2.0
Page 4-18
Fault Management
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 trib-side TOM is looped back to the Tx port on the same TOM via the ISC10, IFC10 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
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 trib-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
Infinera Corporation
Page 4-19
A loopback is performed on the trib-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 trib-side ISC10. This loopback verifies the line side optics on the TOM and the SIM-A-8-2.5GMT.
Client CTP Terminal Loopback
A loopback is performed on the trib-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 trib-side ISC10. This loopback verifies the line side optics on the TOM and the DTF encapsulation and de-encapsulation on the IFC10 and SerDes of the SIM-A-8-2.5GMT.
Client CTP Facility Loopback
Infinera Corporation
Release 2.0
Page 4-20
Fault Management
A loopback is performed on the trib-side of the SIM-A-8-2.5GMT wherein the client signal received from the Rx port on the trib-side TOM is looped back to the Tx port on the same TOM via the ISC10. This loopback verifies the trib-side optics on the TOM and SIM-A-8-2.5GMT.
Figure 4-19
A loopback is performed on the trib-side of the SIM-T-1-10GP or SIM-T-1-10GM wherein the signal received from the Rx port on the trib-side is looped back to the Tx port on the trib-side. This loopback verifies the trib-side optics.
Line OTUk CTP Facility Loopback
Infinera Corporation
Page 4-21
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 trib-side is looped back to the Tx port on the trib-side via the lineside. This loopback verifies the trib-side optics and OTUk signal on the line-side.
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.
Client CTP Terminal Loopback
Infinera Corporation
Release 2.0
Page 4-22
Fault Management
A loopback is performed on the trib-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 trib-side. This loopback verifies the optics on the trib-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.
PRBS Tests
The Pseudo Random Bit 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 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. The following PRBS tests are supported on the ATN:
OTUk Client CTP PRBS testThe ATN supports PRBS generation and monitoring for testing path
Infinera Corporation
Page 4-23
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-23 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 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. Figure 4-24 SONET/SDH Trib and Line PRBS Tests
DTF Section-level PRBS testThis 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
Infinera Corporation
Release 2.0
Page 4-24
Fault Management
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 TAM2-10GT. Note: DTF Path level skips any intermediate SIM-T-1-10GTs that are in regen mode and considers the SIM at the actual termination of the DTF Path layer. Figure 4-25 DTF Section/Path PRBS Tests
See Rules for Performing PRBS Tests 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: In a SIM-A-8-2.5GMT, 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).
Infinera Corporation
Page 4-25
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
eration 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 the DTPCTPs or DChCTPs on that
DTPCTP object is created, PRBS will be enabled on the newly created object only if the above mentioned rules are satisfied.
If the PRBS (generation/monitoring) is enabled on the first DTP and a second facility is created later,
time
ment. This test signal can be monitored by an external test set. See Rules for Performing Fibre
Infinera Corporation
Release 2.0
Page 4-26
Fault Management
Channel Client Termination Point Tests on page 4-26 for information on generating Fibre Channel CTP test signals.
Line-side test signalA test pattern is generated by the Fibre Channel CTP toward the Infinera net-
work, where it is monitored by an external test set. See Rules for Performing Fibre Channel Client Termination Point Tests on page 4-26 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 the associated facility is in administrative maintenance state. Figure 4-26 Test Signal Generation
applied at the same time. When DTP-level PRBS is activated, any FC client test signal generation is disabled.
Infinera Corporation
Page 4-27
equipment. This test signal can be monitored by an external test set. See Rules for Performing GbE Client Termination Point Tests on page 4-27.
Line-Side Client TestA test signal at the 1GbE level is generated by the GbE CTP toward the Infin-
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-27 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. See Rules for Performing GbE Client Termination Point Tests on page 4-27 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.
DTP-level PRBS is activated, any 1GbE client test signal generation or monitoring is disabled.
Trace Messaging
Trace messaging is a non-intrusive diagnostic tool. It can be used to determine commissioning problems such as fiber misconnections. Trace Messages are trace bytes of HEX (1 byte) or ASCII encoded character set and can be of 1, 16 or 64 bytes. They are provisioned from management applications like Infinera ATN 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
Trace messaging at the SONET/SDH J0 on the tributary ports (see Figure 4-27 on page 4-28).
The ATN provides the capability to monitor and transmit J0 messages received from the client equipment. This capability enables the detection of misconnections between the client equipment and the
Infinera Corporation
Release 2.0
Page 4-28
Fault Management
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-27 on page 4-28).
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 or SIM-T-1-10GM. 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 Infinera ATN GNM, or CLI. Figure 4-27 SONET/SDH/J0/OTUk Trace Messaging
Digital Channel Section level (DChCTP) TTI trace messaging (see Figure 4-28 on page 4-29)
Digital Channel Section level (DChCTP) TTI trace messaging 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 Infinera ATN GNM, or CLI.
DTF Path level (DTPCTP) TTI trace messaging (see Figure 4-28 on page 4-29)
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
Infinera Corporation
Page 4-29
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 Infinera ATN GNM, or CLI. Figure 4-28 DChCTP and DTPCTP Trace Messaging
Release 2.0 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 cannot be configured from management applications like Infinera ATN GNM, or CLI.
Infinera Corporation
Release 2.0
Page 4-30
including:
Circuit pack auto-discovery (see Circuit Pack Discovery on page 4-32) Data plane auto-discovery (see Data Plane Discovery on page 4-33) Circuit pack configuration (see Equipment Configuration on page 4-33) including: Circuit pack pre-configuration Circuit pack auto-configuration GR-1093 and TMF-814 compliant state management (see State Modeling on page 4-34)
Managed Objects
IQA NOS ATN defines software abstraction of all the hardware equipment, physical ports and logical termination points, referred to as managed objects which are administered through the management applications. Managed objects are modeled after the ITU-T and TMF general information modeling standards, which provide an intuitive and convenient means to reference the managed objects. Figure 4-29 illustrates the most commonly used managed objects, number of instances of each managed object and the hierarchical relationship between them. As shown, there are three major categories: hardware equipment which represents the hardware manageable by the user, physical ports and logical termination points which represent the termination of signals. Users can create and delete equipment managed objects while the physical port and logical termination points are created and defined with default attributes when the equipment is physically installed. Users can modify the attributes of the auto-created managed objects through the management applications. Note that multi-chassis network elements are managed as single objects. User operations, such as modifying the administrative state (see Administrative State on page 4-34) and modifying the alarm reporting state (see Alarm Reporting Control (ARC) on page 4-7), of a given managed object impact the behavior of the corresponding contained and supported/supporting managed objects. For example, when a user modifies the administrative state of a SIM to locked, the service state of the contained and supported managed objects such as TOM, Trib PTP (line), OTUk CTP, Clear Channel CTP, etc., is changed to out-of-service. Similarly, when ARC is enabled on a SIM, alarm reporting is inhibited for all the corresponding contained and supported managed objects. Figure 4-29 shows the hierarchy of managed objects on an ATC.
Infinera Corporation
Page 4-31
page 4-33) IQA NOS ATN maintains the inventory of all the automatically discovered resources, as described above, and also the protection groups that have been provisioned.
Infinera Corporation
Release 2.0
Page 4-32
Multi-chassis Discovery
IQA NOS ATN provides the ability to automatically detect multiple chassis in the ATN, along with detailed information for each chassis, including:
Label name CLEI code Product ordering name (PON) Manufacturing part number Serial number Hardware version Manufacturing date Internal temperature Rack name Provisioned serial number Location in rack Alarm Cutoff (ACO) state (enabled or disabled)
The manufacturing information and firmware version are maintained in the inventory, and are retrievable by the management applications.
Infinera Corporation
Page 4-33
ATN supports automatic discovery of the TOM connectivity between the line ports of the two ATN SIM modules on different ATN nodes when DTF line protocol is used between the ATN SIM modules.
ATN to DTN TOM Connections
ATN and DTN network elements support automatic discovery of the TOM connectivity between an ATN and DTN network when DTF line side protocol is used between the ATN TOM and the DTN TOM. In Release 2.0, ATN supports auto-discovery for optical connections between the following:
A TOM installed in a SIM-T-1-10-GT of an ATN and a TOM installed in the TAM-2-10GT of a
DTN
A TOM installed in a SIM-A-8-2.5-GMT of an ATN and a TOM installed in the TAM-2-10GT of a
DTN
Equipment Configuration
IQA NOS ATN supports two modes of equipment configuration as described in the following sections:
Equipment Auto-configuration Equipment Pre-configuration on page 4-34
Equipment Auto-configuration
As described in System Discovery and Inventory on page 4-31, IQA NOS ATN automatically discovers the equipment installed in the network element, enabling users to bring up a circuit packs without manual configuration. The auto-configuration is performed when a circuit pack is installed in a slot which is not already configured. IQA NOS ATN discovers the installed circuit pack and also creates and configures the corresponding circuit pack managed object using default configuration parameters. The default administrative state of an automatically created circuit pack is unlocked so the circuit pack can start operation without manual configuration. However, users can modify this default state through management applications.
Infinera Corporation
Release 2.0
Page 4-34
Once a slot is populated and the circuit pack auto-configuration completes, the slot is configured and any attempt to replace the circuit pack with a different circuit pack type will raise an alarm. To enable autoconfiguration of a different circuit pack in the same slot, the circuit pack configuration for the slot must first be deleted through management applications.
Equipment Pre-configuration
IQA NOS ATN supports circuit pack pre-configuration where users can configure the slots to house a specific circuit pack before physically installing it in the chassis. Such slots are displayed as pre-configured but unpopulated through the management applications. For multi-chassis systems, the Expansion Chassis may be pre-configured. The equipment placed in the pre-configured chassis also can be configured. When the circuit pack is installed in a pre-configured slot, the circuit pack becomes operational using preconfigured data. Once a slot is pre-configured for a circuit pack type, insertion of a different circuit pack type causes the network element to generate an equipment mismatch alarm.
State Modeling
IQA NOS ATN implements state modeling that meets the various needs of all the supported management applications and interfaces, and also provides comprehensive communication on the state of the equipment and termination points. IQA NOS ATN defines a standard state model for all the managed objects, which includes equipment as well as termination points as described in Managed Objects on page 4-30. IQA NOS ATN defines the following states:
Administrative StateRepresents the users operation on an equipment or termination point
administrative state and operational state. See Service State on page 4-38.
Administrative State
The administrative state allows the user to allow or prohibit the managed object from providing service. The administrative state of the managed object can be modified only by the user through the management applications. Also, a change in the administrative state of a managed object results in an operational state
Infinera Corporation
Page 4-35
change of the contained and supported managed objects. However, the administrative states of the contained and supported managed objects are not changed. Note: IQA NOS ATN 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 ASAP feature (see Alarm Severity Assignment Profile Setting (ASAP) on page 4-9). IQA NOS ATN defines three administrative states as described in the following sections:
Unlocked State on page 4-35 Maintenance State on page 4-35 Locked State on page 4-36
Unlocked State
The managed object in unlocked state is allowed to provide services. Using management applications, users can change the state of a managed object to unlocked state from either locked state or maintenance state. This action results in the following behavior:
If there are any outstanding alarms on the managed object they are reported. The managed object is available to provide services (provided its operational state is enabled). This action causes the contained and supported objects to re-evaluate their states as follows: This action may trigger an operational state change on all objects that are contained or sup-
ported by this object (called dependent objects), depending on existing fault conditions. The operational state of those dependent objects will transition to the Enabled state, if no fault conditions exist and no other ancestors or supporting objects are administratively locked.
This action does not impact the operational state of the managed object itself. Its operational
state is determined autonomously by fault conditions that might arise, or by administrative locking actions on ancestors.
This action causes all contained objects to remove the ANCESTOR_LOCKED or
ANCESTOR_MAINTENANCE operational state qualifier and may cause alarm reporting to be enabled, if no ancestors are silenced.
This action causes all supported objects to remove the SUPPORTING_LOCKED or
SUPPORTING_MAINTENANCE operational state qualifier and may cause alarm reporting to be enabled, if no ancestor or supporting objects are currently silenced.
Maintenance State
The managed object avails itself to management operations, such as trace messaging, loopbacks, PRBS testing, etc. Users can change the state of a managed object to the maintenance state from either locked state or unlocked state. This section results in the following behavior:
Maintenance state can be applied to either Equipment or Termination Point objects. The opera-
tional state of the object is not impacted by a transition into Maintenance state.
Infinera Corporation ATN System Description Guide Infinera Proprietary and Confidential Release 2.0
Page 4-36
All outstanding alarms (except alarms that cannot be suppressed) are cleared on the managed
object and all new alarm reporting and alarm logging are suppressed until the managed object is administratively unlocked again. However, currently observable fault conditions can still be retrieved.
Users can perform service-impacting maintenance operations, such as loopback tests, PRBS
that are contained or supported by this managed object). The operational state of the dependent objects transition to a disabled state, their service state is changed to OOS-MT (out-of-servicemaintenance) state, the oerational state qualifier value is set to ANCESTOR_MAINTENANCE or SUPPORTING_MAINTENANCE and alarms transition to Inhibited (i.e. silenced) state.
PM monitoring and historical PM collection of the resource and its contained and supported
objects shall continue, if PM collection is enabled, but the data shall be marked as suspect or invalid.
Locked State
The managed object is prohibited from providing services to its users. Service affecting provisioning, such as modifying attributes or deleting objects are allowed. Users can change the administrative state of a managed object to the locked state from either unlocked state or maintenance state through all management applications. Changing the administrative state to the locked state results in the following behavior:
Depending on the type of managed object, the Locked state may or may not provide services to
users:
Passive cards, Power Conversion Modules (PCMs) and Fan are not impacted by a locked state AAMThe AAM EDFA is shut down, ADAPT control loops associated with AAM are stopped OFMThe OFM is shut down, ADAPT control loops associated with OFM are stopped SIMAll client and line TOMs are shut down Active OFMs All Variable Optical Attenuators (VOAs) are set to maximum attenuation TOMThe TOM laser is shut down, the TOM input is ignored and is not sent to the other side for
encapsulation or de-encapsulation. An LOS or all zero bits are sent for encapsulation/de-encapsulation instead
Client/Line TOM trib PTPTrib Disable Action is applied
The payload/service type can be changed when the Trib PTP is in the Locked or Maintenance state. For all payload types, traffic on the Trib PTP will be impacted when the facility is put in the Locked state. Furthermore, the behavior of the Trib PTP in the Locked state is determined by the Tributary Disable Action setting of the Trib PTP: If the Tributary Disable Action is set to Turn-off Laser, the trib laser is shut down (applicable for all payloads).
Infinera Corporation
Page 4-37
If Tributary Disable Action is set to Send AIS, AIS signal is sent by the trib (applicable for SONET/SDH only; this setting does not apply to GbE, Clear Channel, Fibre Channel, Video services, etc.) If the Tributary Disable Action is set to Do Nothing, the trib laser does not shut down or transmit any maintenance signal such as AIS. The trib laser continues to transmit a signal. If the Tributary Disable Action is set to Insert Idle, the trib sends an idle signal (applicable for Fibre Channel services only)
All outstanding alarms (except alarms that cannot be suppressed) on the managed object are
cleared and all new alarm reporting and alarm logging are suppressed until the object is administratively unlocked again. However, currently observable fault conditions can still be retrieved.
The operational state of this managed object is not changed, since the operational state is deter-
mined by the objects ability to provide service. The service state of this managed object is changed to OOS.
This action triggers an operational state change on all dependent managed objects (i.e. objects that
are contained or supported by this managed object). The operational state of the dependent objects transition to a disabled state, their service state is changed to OOS-MT (out-of-service-maintenance) state, the operational state qualifier is set to a value of ANCESTOR_LOCKED or SUPPORTING_LOCKED and alarms transition to Inhibited (i.e. silenced) state.
PM monitoring and historical PM collection of the resource and its contained and supported objects
shall continue, if PM collection is enabled, but the data shall be marked as suspect or invalid.
Operational State
The operational state indicates the operational capability of a managed object to provide its services. It is determined by the state of the hardware and software, and by the state of the supporting/containing object; it is not configurable by the user. Two operational states are defined:
EnabledThe managed object is able to provide service. This typically indicates that the corre-
the corresponding hardware has detected some faults or is not installed. For example, when a provisioned circuit pack is removed, the operational state of the corresponding managed object becomes disabled.
Infinera Corporation
Release 2.0
Page 4-38
Each operational state may be further characterized by the following operational state qualifiers that indicate an operational state due to the operational state of the supporting/containing (ancestor) objects:
FAULTEDThe equipment has a fault due to a diagnostic failure or there is a service affecting fault
like OLOS
EQUIPMENT_NOT_PRESENTThe equipment is not present EQUIPMENT_MISMATCHThere is a mismatch between the installed equipment type and the
fault on the line-side. This qualifier is applicable on the client TOM Trib PTP and line TOMs on the SIM-T-1-10GP, SIM-T-1-10GM, and SIM-T-1-10G SIM due to line disable action or admin lock operation.
ANCESTOR_FAULTED, SUPPORTING_FAULTEDThe parent or supporting managed object is
faulted
ANCESTOR_UNAVAILABLE, SUPPORTING_UNAVAILABLEThe parent or supporting managed
object is unavailable
ANCESTOR_LOCKED, SUPPORTING_LOCKEDThe parent or supporting managed object is in
Service State
The service state represents the current functional state of the managed object which is dependent on the operational state and the administrative state. The service state is not maintained by IQA NOS ATN. It is
Infinera Corporation
Page 4-39
derived by the Infinera ATN GNM and Infinera DNA management applications based on the operational and administrative states of an object and its ancestors. The following states are defined:
In-service (IS)Indicates that the managed object is functional and providing services. Its opera-
because its operational state is disabled, the administrative state of its ancestor object is locked, or the operational state of its ancestor object is disabled.
Out-of-service Maintenance (OOS-M)Indicates that the managed object is not providing normal
end-user services, but it can be used for maintenance test purposes. Its operational state is enabled and its administrative state is maintenance.
Out-of-service Maintenance, Locked (OOS-MT, Locked)Indicates that the managed object is not
providing normal end-user services, but it can be used for maintenance test purposes. Its operational state is enabled and its administrative state is locked.
action is applicable for all payloads. Turn-off laser is the only trib disable action supported on a 10GbE service on a SIM-T-1-10G. Note: For electrical transmit TOMs (TOM-1.485HD-TX and TOM-1.4835HD-TX), this setting is called Disable Transmitter. Also note that because the transmitter on electrical transmit TOMs cannot be disabled, when an electrical TOM is configured for Disable Transmitter setting, the TOM will transmit all zeroes.
Send AISWhen tributary disable action is in effect, the trib sends an AIS signal. This trib disable
action is applicable for SONET/SDH only; this setting does not apply to GbE, Clear Channel, Fibre Channel, Video services, etc.
Insert IdleWhen tributary disable action is in effect, the trib sends an idle signal. This trib disable
Sequence i.e. NOS signal. This trib disable action is applicable for Fibre Channel interfaces only.
Send All ZeroesWhen tributary disable action is in effect, the trib sends all zeroes in the entire
frame, which results in a PCS Loss of Sync alarm on the downstream equipment or test set. This trib
Infinera Corporation
Release 2.0
Page 4-40
disable action is applicable for Fibre Channel interfaces and clear channel interfaces, with the exception of 8G FC on a SIM-T-1-10GP or SIM-T-1-10GM.
Do Nothing When tributary disable action is in effect, the trib laser is not shut down and it does not
transmit any maintenance signal such as AIS. The trib laser continues to transmit a signal. This trib disable action is applicable for all payloads. ATN also supports configuration of the line behavior upon line disabling on the SIM-T-1-10G, SIM-T-1-10GP and SIM-T-1-10GM when the line is locked, or when a LOF or AIS is detected for the line path. The line disabling actions can be any of the following:
Turn-off LaserWhen tributary disable action is in effect, the trib laser is shut down. This trib disable
transmit any maintenance signal such as AIS. The trib laser continues to transmit a signal. This trib disable action is applicable for all payloads. Note: Infinera recommends setting Trib Disable Action and Line Disable Action to Turn-off laser for OTU2, OTU2e and OTU2f regen modes.
Infinera Corporation
Page 4-41
page B-9)
Digital Channel (DCh) PM data at every SIM-T-1-10GT and SIM-A-8-2.5GMT (see DTF PM
page B-38)
Fan Inlet Temperature PM (see Additional PM Parameters on page B-39) Comprehensive PM data collection functions, including, Real-time PM data collection for real-time troubleshooting (see Real-time PM Data Collection
on page 4-42)
Historical PM data collection for service quality trend analysis (see Historical PM Data Collec-
page 4-44)
Performance monitoring event logging for troubleshooting (see PM Logging on page 4-45)
A complete list of PM data collected by IQA NOS ATN is provided in ATN PM Parameters on page B-1.
Flexible PM data reporting and customizing options to meet diverse customers needs, including, Automatic and periodic transfer of PM data in CSV format enabling customers to integrate with
Infinera Corporation
Release 2.0
Page 4-42
PM Data Collection
IQA NOS ATN collects digital PM data and optical PM data.
For the optical PM data, IQA NOS ATN utilizes gauges to collect the PM data. As defined in ITU
X.721 specification, the gauge indicates the current value of the PM parameter. The gauge attribute type is a float value. The gauge value may increase or decrease by an arbitrary amount and it does not wrap around. It is a read-only attribute.
For the digital PM data, IQA NOS ATN uses counters to collect the PM data. The counter value is a
non-negative integer that is set to zero at the beginning of every collection interval. The counter size is selected in a such a way that the counter does not rollover within the collection period.
The historical PM data is not asynchronously reported to the management applications. It must be retrieved by the users through management applications. Note: Historical counters/gauges are supported only for some PM parameters. The historical (current and previous) optical PM data is derived by taking several snapshots of the hardware status. The optical PM parameter value is read from the hardware every five seconds within a
ATN System Description Guide Release 2.0 Infinera Proprietary and Confidential Infinera Corporation
Page 4-43
PM period, and minimum, maximum and average values are derived from all the readings. The duration of the reading itself is one second. Thus the historical optical PM data is the minimum, maximum and average of the PM parameter values within a given period. The historical digital PM data is essentially the value of the counter at the end of the given PM period.
PM Thresholding
PM thresholding provides an early detection of faults before significant effects are felt by the end users. Degradation of service can be detected by monitoring error rates. Threshold mechanisms on counters and gauges allow the monitoring of such trends to provide a warning to users when the monitored value exceeds, or is outside the range of, the configured thresholds. IQA NOS ATN supports thresholding for both optical PM gauges and digital PM counters. During the PM period, if the current value of a performance monitoring parameter reaches or exceeds corresponding configured threshold value, threshold crossing notifications are sent to the management applications.
Optical PM Thresholding
IQA NOS ATN performs thresholding on some optical PM parameters by utilizing high and low threshold values. Note that the thresholds are configurable for some PM parameters; for others, the system utilizes pre-defined threshold values. An alarm is reported when the measured value of an optical PM parameter is outside the range of its configured threshold values. The alarms are automatically cleared by IQA NOS ATN when the recorded value of the optical PM parameter is within the acceptable range.
Digital PM Thresholding
IQA NOS ATN performs thresholding on some digital PM data utilizing high threshold values which are user configurable. A Threshold Crossing Alert (TCA) is reported when a PM counter, within a collection period, exceeds the corresponding threshold value. When a threshold is crossed, IQA NOS ATN continues to count the errors during that accumulation period. TCAs are transient in nature and are reported as events which are logged in the event log as described in Event Log on page 4-9. The TCAs do not have corresponding clearing events since the PM counter is reset at the beginning of each period. Note: Threshold Crossing Alerts (TCAs) are reported for SONET/SDH, GbE and Fibre Channel signals only on SIM-T-1-10GP, SIM-T-1-10GM, SIM-T-1-10GT and SIM-A-8-2.5GMT. TCAs for DTF and DCh signals are reported only on SIM-T-1-10GT and SIM-A-8-2.5GMT. PM thresholding is supported for some of the PM parameters, but not for all. When a PM threshold value is modified, the new threshold will be used for generating associated TCAs in the next complete PM interval. The current PM interval will not use the new threshold.
Infinera Corporation
Release 2.0
Page 4-44
count, TCAs are not raised in the current PM interval. The new threshold will be used only in the next complete PM interval.
If TCA reporting is enabled before a PM threshold is modified to a value lower than the current PM
PM Data Export
Users can export PM data, in CSV format flat files to a user specified external FTP server. Users can use these flat files to integrate PM data analysis into their management applications or simply view the PM data through spreadsheet applications. For the PM data flat file format, see the Infinera DNA User Guide. The following methods of PM data upload are supported:
ManualUse the manual mode to immediately upload the PM data to the specified FTP server. ScheduledUse scheduled upload to automatically upload the data at regular intervals, hourly,
every 4hours, every 8 hours or every 12 hours as configured. Users can schedule the TOD (time of day) at which the network element automatically transfers the PM data to the user specified server. Users can configure primary and secondary server addresses. If the data transfer to the primary server fails, the PM data is transferred to the secondary FTP server.
Infinera Corporation
Page 4-45
PM Data Configuration
IQA NOS ATN allows users to customize PM data collection on the network element. Users can configure PM data collection through management applications. IQA NOS ATN supports the following configuration options:
Reset the current 15-minute and 24-hour counters at any time per managed object. Change the default threshold values according to the customers error monitoring needs. Enable or disable the PM threshold crossing alarm and TCA reporting per attribute per managed
object.
Set the severity level of TCA notifications. Enable or disable PM data collection per managed object entity.
PM Logging
As described in Event Log on page 4-9, IQA NOS ATN maintains a wrap-around historical event log that tracks all changes that occur within the system. Following are some PM related events that are logged in the event buffer:
User changes PM thresholds User resets PM counters Threshold crossing alert (TCA) is generated
Infinera Corporation
Release 2.0
Page 4-46
on page 4-48).
User access control to prevent intrusion (see Access Control on page 4-49). Security audit logs to monitor unauthorized activities (see Security Audit Log on page 4-49). Security functions and parameters to implement site-specific security policies (see Security Admin-
Authorization
Multiple access privileges are defined to restrict user access to resources. Each access privilege allows a specific set of actions to be performed. One or more access privileges is assigned to each user account. For the description of the managed objects, see Managed Objects on page 4-30. There are six levels of access privileges as described in Table 4-1 on page 4-47:
Infinera Corporation
Page 4-47
Allows the user to perform network element security management and administration related tasks such as:
Creating new user accounts with appropriate user access privileges Modifying user accounts Monitoring security alarms and events raised and taking appropriate actions Disabling user accounts due to intrusion detection or inactivity Monitoring the security audit log Configuring system wide security parameters such as inactivity time-out period, maximum number of invalid logins etc.
Allows the user to monitor the network element. The user cannot modify anything on the network element and has read-only privileges. Monitoring Access is provided to all users by default.
The actions the user can perform include: Monitoring PM data Viewing event logs Monitoring provisioning data for network resource usage
Allows the user to maintain the network infrastructure by performing tasks such as:
Monitoring the network element Managing equipment Turning-up the network element Administering various network-related functions, such as, auto-discovery The Network Administrator has full read/write access to the system commands.
Allows the user to monitor the network element and manage equipment. Allows the user to monitor the network element and configure facility endpoints.
The Provisioning user has read/write permission to the provisioning database.
Allows the user to monitor, turn-up, and troubleshoot the network element and fix network problems.
Infinera Corporation
Release 2.0
Page 4-48
User Identification
Each network element user is assigned a unique user ID. The user ID is case-sensitive and contains 4 to 10 alphanumeric characters. The user specifies this ID (referred to as user login ID) to log into the network element. By default, IQA NOS ATN creates three user accounts with the following user login IDs:
secadmin
An account with the security administrator privilege enabled. The default password is Infinera1 and the user is required to change the password at first login. This user login ID is used for initial login to the network element.
netadmin
An account with the network administrator privilege enabled. The default password is Infinera1 and the user is required to change the password at first login. Additionally, this account is disabled by default. It must be enabled by the user with security administrator privilege through the Infinera ATN GNM. This account is used to turn-up the network element.
emsadmin
An account with all privileges enabled. The default password is Infinera1. This account is disabled by default. It must be enabled by the user with security administrator privilege through the Infinera ATN GNM. The Infinera DNA server communicates with the network element using this account, referred to as the Infinera DNA account, when it is started without requiring additional configuration. Users can create additional Infinera DNA accounts which the Infinera DNA server can use to connect to the network element. These accounts must have the Infinera DNA access capability enabled during creation. A single user can open multiple sessions. IQA NOS ATN maintains a list of all current active sessions. Note: IQA NOS ATN supports a maximum of 13 active user sessions at any given time. All login attempts beyond 13 sessions will be denied and a warning message is displayed.
Authentication
IQA NOS ATN supports standards-based authentication features. These features ensure that only authorized users log into the network element through management interfaces. Each time the user logs in, the user must enter a user ID and password. For the initial login, the user specifies the default password set by the security administrator. The user must then create a new password based on the following requirements.
The password must contain Six to ten alphanumeric characters
Infinera Corporation
Page 4-49
At least one alphabetic and one numeric or one special character The password may contain these special characters: ! @ # $ % ^ ( ) _ + | ~ { } [ ] ? The password must not contain: The associated user ID Blank spaces The passwords are case-sensitive and must be entered exactly as specified.
The password is stored in the network element database in a one-way encrypted form. Password rotation is implemented to prevent users from re-using the same password. The users are forced to use passwords different from the previously used passwords. The number of history passwords stored is configurable.
Access Control
In addition to user login ID validation and password authentication, IQA NOS ATN supports access control features to ensure that the session requester is trusted, such as:
An unsuccessful user login is detected and if the number of unsuccessful login attempts exceeds
the configured maximum number of attempts, the session is terminated and a security event is logged in the security audit log.
The user session is automatically terminated when the cable connecting the user computer and the
network element is physically removed. The user must follow the regular login procedure after the cable is reconnected.
The activity of each user session is monitored. If, for a configurable period of time, no data is
exchanged between the user and the network element, the user session is timed-out and the session is automatically terminated.
Infinera Corporation
Release 2.0
Page 4-50
The audit logs include system configuration activities and security related activities performed by the user. These activities include:
Creating and deleting managed objects Updating an attribute of the managed object Invalid login attempts Unauthorized attempts to access resources due to restrictions imposed by the user access privilege Updates to the user's security parameters, such as the password, user access privilege, password
attempts, and inactivity time-out interval Each audit log entry includes the following minimum set of information:
User login ID of the user who performed the action, along with terminal, port and network address
information
Date and Time of the operation Action performed Instance of the managed object on which the action was performed
The audit logs are maintained in a circular buffer andthe oldest records are overwritten once the buffer reaches its limit. Audit logs are preserved when system reboots. Although users cannot modify audit logs, users with any access privilege can view the audit logs through the management applications.
Infinera Corporation
Page 4-51
Security Administration
IQA NOS ATN defines a set of security administration functions and parameters that are used to implement site-specific policies. Security administration can be performed only by users with security administrator privilege. The supported features include:
View all users currently logged on Disable and enable a user account (this operation is allowed only when the user is not logged on) Modify user account parameters, including access privilege and password expiry time Delete a user account and its attributes, including password Reset any user password to system default password Set the password change policy to allow users to change their own passwords, or to require all
Secure
Perform network-wide user administration, including: View user accounts cross the managed network Add new user accounts to multiple nodes, in a single operation Update user account information on multiple nodes, in a single operation View and modify attributes common to multiple user accounts, in a single operation Clone multiple user accounts (with the same privileges, associations and permissions as that of
an existing user account) to one or more network elements, or to all network elements within an administrative domain
Export multiple user account information Import multiple user account information that was previously exported
Infinera Corporation
Release 2.0
Page 4-52
Note: For maximum management traffic protection, configure the network element and DCN ports behind a firewall.
Infinera Corporation
Page 4-53
The IQA NOS ATN implementation of SSHv2 is based on the IETF SSHv2 OpenSSH Toolkit solution. It provides the following types of communication protection:
Data EncryptionSymmetric data encryption is based on the Advanced Encryption Standard (AES)
SSHv2 to ensure data integrity between the management client and the network element. The 128 bit key hmac-sha1 algorithm is supported. Note: The following SSHv2 Clients are supported by the Infinera node: - PuTTY - OpenSSH Client - F-Secure SSH Client - Tera Term Pro Users with the secadmin privilege can selectively enable SSHv2-based security on a per-node basis for each of the management interface ports (that is, to protect communications via CLI, Telnet, file transfer, or XML). By default, enhanced security is not enabled. Note: The SSH enhanced security feature may be enabled at any time. However, if the enhanced security flag is updated during run-time, existing sessions continue to function in its earlier mode. Any new established sessions will operate according to the new security setting. You must perform a warm or cold reboot of the AMM in order to effect the security changes to existing sessions.
Infinera Corporation
Release 2.0
Page 4-54
Note: The user account names and passwords on the RADIUS server(s) must comply with the same rules and constraints for user names and passwords on the ATN (see User Identification on page 4-48 and Authentication on page 4-48 for the requirements for valid user names and passwords on the ATN). In addition, all user accounts must have a privilege level of MA or higher in order to be compatible with Infinera nodes (see Authorization on page 4-46 for information on privilege levels). An Infinera network element can be configured to authenticate users according to the local settings or via the configured RADIUS servers. In addition, the network element can be configured to authenticate users first according to the RADIUS settings, and then according to the local settings on the network element if no RADIUS server can be contacted. Figure 4-31 shows an example Infinera network with redundant RADIUS servers.
Infinera Corporation
Page 4-55
Infinera Corporation
Release 2.0
Page 4-56
Downloading Software
IQA NOS ATN is packaged into a single software image. The software image includes the software components required for all the circuit packs in the ATN. Users can remotely download the software image from a user specified FTP server, to the controller (AMM) of one or more network elements within an administrative domain. Once users download the software image to the AMM and then separately initiate the software upgrade procedure, the software is automatically distributed to the remaining circuit packs within the chassis. A network element can store up to three versions of the software image (including the current version), at the same time. When upgrading a network element storing three versions of software, the user is prompted to reduce the number of software images residing on the network element by deleting any of the currently inactive software versions.
Maintaining Software
The network elements support in-service software upgrade. The software upgrade procedure lets users activate a different software version from the one currently active. The following software upgrade operations are supported:
Install New SoftwareThis operation lets users activate the new software image version with an
empty database. The software image may be older or newer than the active version. Note: Do not attempt to reboot the system while it is coming up with an default database. This may corrupt the database and cause the AMM to re-boot repeatedly.
Upgrade SoftwareThis operation lets users activate the new software image version with the pre-
viously active database. The previously active database version must be compatible or migratable with the new software image version. Note: For detailed traffic, EDFA Firmware (AAM only), Field Programmable Gate Array (FPGA) upgrade, Complex Programmable Logical Device (CPLD) upgrade (for AMM only), and
Infinera Corporation
Page 4-57
operational effects associated with upgrading to a specific software image version, refer to the applicable Software Release Notes.
Activate Software and DatabaseThis operation lets users activate a software image version and a
database version. The database version and the software version must be the same to activate the software and database. Before upgrading the software, the new database image must be downloaded to the network element.
Restart Software with Empty DatabaseThis operation lets users activate the current software
image with an empty database. Note: Do not attempt to reboot the system while it is coming up with an empty database. This may corrupt the database and cause the AMM to re-boot repeatedly. In general, upgrading the software does not affect existing service. However, if the new software image version includes a different Firmware/Field Programmable Gate Array (FPGA) version than the one currently active, it could impact existing services. If this occurs, a warning message is displayed. Users must upgrade software on a node-by-node basis. Therefore, at any given time, the network elements within a network may be running at least two software image versions. These different images must be compatible. In the presence of multiple software versions, the network provides functions that are common to all the network elements. The software upgrade procedure executes in the following steps: 1. 2. 3. 4. Verifies that the software and database versions are compatible. If they are not compatible, the upgrade procedure is not allowed. Validates the uncompressed software image. If the software image is invalid, the upgrade procedure is not allowed. Decompresses the software image. If there is not enough memory on the network element to store the decompressed image, software decompression will not occur at all. Reboots the network element so that the new software image becomes active. If the reboot fails, the upgrade procedure is aborted and software image reverts to the previously active software image version. When the new software image is activated, the software upgrade procedure updates the format of the Event Log and Alarm table alarms, if necessary. Note: When the software is upgraded, the PM historical data is not converted to the new format (if there is a change in the format) and it is not persisted. Therefore, before you upgrade the software, you must upload and save the PM data in your local servers. In general, if the upgrade procedure is aborted, the software reverts to the previously active version. The procedure reports events and alarms indicating the cause of the failure. During the upgrade process, communication with the clients and other network elements within the network is interrupted.
5.
Infinera Corporation
Release 2.0
Page 4-58
Note: Do not interrupt AAMs while they are undergoing a firmware upgrade. If an AAM is interrupted during a firmware upgrade, the AMM will have an equipment fault and will need a Return Material Authorization (RMA). Critical information about FPGA or CPLD image upgrades is provided in the Software Release Notes. Specifically, the Software Release Notes identify:
If the release contains any FPGA or CPLD upgrades, and if so, for what modules The functional changes made by each FPGA or CPLD upgrade Whether the FPGA or CPLD upgrade is service impacting If the FPGA or CPLD upgrade is recommended, required, or optional
When a user performs a software upgrade, all non-service affecting FPGA and CPLD upgrades are automatically activated. Service-affecting FPGA and CPLD upgrades are not activated until the user targets each individual module with a cold-reboot, warm-reboot or removes/reinserts the module into the chassis. After performing a software upgrade, users may check for pending FPGA or CPLD upgrades using the Equipment Manager tool in the Infinera ATN GNM before activating FPGA or CPLD upgrades on a per-module basis. This allows users to perform hardware upgrade operations within a planned maintenance and service disruption window. Note: If there is an incompatibility between the firmware version on a given module compared to what the current version of the software can support, no new services may be added to the node. If all firmware versions are compatible with the current software image version (even if the software image contains firmware upgrades) then users may use, add, and subtract services indefinitely.
Infinera Corporation
Page 4-59
The current database image can be transferred to a specified FTP server or can be stored locally on the network element.
Scheduled Database BackupUsers can schedule automatic database backups to occur at a spec-
ified time on a specified day, at either daily or weekly intervals. For example, users can schedule database backups to occur every day at 5pm. Users can also specify a primary and secondary FTP server to store the backup file. By default, the database is backed up to the primary server; however, if that server is not available, the database is backed up to the secondary server. In both modes, the current active database is backed up, not any previously saved database files. The database file that has been backed up contains:
Database file, which includes configuration information stored in the persistent memory on the net-
work element.
Alarm table stored in the persistent memory of the network element. Event Log stored in the persistent memory of the network element.
Infinera Corporation
Release 2.0
Page 4-60
database may differ from the current hardware configuration. In such scenarios, in general, the configuration data takes precedence over the hardware.
Restores the alarms in the Alarm table by verifying the current alarm condition status. For example,
if there is an alarm entry in the restored Alarm table but the condition is cleared, that alarm is cleared from the current Alarm table. On the other hand, if the alarm condition still exists, the corresponding alarm entry is stored in the current Alarm table with the original timestamp. Note: The data in the Event Log is not restored. The database image can be restored at system reboot time or at any time during normal operation. Following is the description of some scenarios where the configuration data in the restored database differs from the current hardware configuration and how they are handled:
Scenario 1: If the restored database does not contain a managed equipment object, but the hard-
ware is present in the network element, the managed equipment object is created in the database as in equipment auto-configuration (refer to Equipment Auto-configuration on page 4-33). For example, consider the following sequence of operations:
Backup database Install a new circuit pack Restore the previously backed up database
In this case, after database restoration, the newly inserted circuit pack is auto-configured.
Scenario 2: If the managed equipment object exists in the database and the corresponding hard-
ware equipment is present in the network element, but there is a configuration mismatch, an equipment mismatch alarm is reported and the operational state of the equipment is changed to out-ofservice (see Operational State on page 4-37).
Infinera Corporation
Page 4-61
Database Branding
Both the IQA NOS ATN software and database are stored within the AMM flash memory, and persist in the AMM even when the module is not powered or installed within the system. To prevent a system from operating off an AMM with an inappropriate version of IQA NOS ATN and/or database, the IQA NOS ATN software and hardware work together to brand the AMMs. Database Branding is a process by which the software and database residing on an AMM are marked as belonging to a specific network element. This prevents the chassis from booting off an inappropriate AMM - that is, an AMM that was not specifically configured to work with the given chassis.
base restore
Re-brand the system so that the chassis accepts the AMM database. Re-branding is supported
from the start-up CCLI that can be accessed through the Craft DCE port.
If there is no database present on the AMM, the user may perform one of the following actions: Create a default database Perform a local or remote database restore
Note: Do not attempt to reboot the system while it is coming up with a default database. This may corrupt the database and cause the AMM to re-boot repeatedly. Re-branding enables emergency chassis replacement without requiring re-configuration. Note: Re-branding will overwrite the configuration of a system and should be used only by experienced personnel. For further details on the procedure to re-brand" or re-commission an AMM, refer to the Infinera ATN Turn-up and Test Guide.
Infinera Corporation
Release 2.0
Page 4-62
matically to the specified FTP server. This upload is triggered ten minutes after a successful reboot of the AMM.
Manual UploadThe debug information can be manually uploaded to the specified FTP server at
any time.
Infinera Corporation
Page 4-63
network element and forwards it to the appropriate SNMP Manager that is registered to receive traps. The SNMP Manager(s) and the SNMP Agent maintain a copy of the management information base (MIB) that is kept in sync at all times. The ATN SNMP Agent provides the following benefits:
Ability to integrate the Infinera network elements with third party network management system
based on SNMP.
Ease of integration with third party off-the-shelf value added tool-kits spanning various applications.
process. The network element performs the authentication for each SNMP request made to the SNMP agent. A community string is configured on the SNMP Manager and the network element. Only if both of them match, the requests are processed.
Provides the capability to configure the list of SNMP Managers to which the traps can be forwarded.
Infinera Corporation
Release 2.0
Page 4-64
The following topics describe how optical power management is performed using ADAPT protocol, ADAPT operation and parameters associated with ADAPT:
Optical Power Management using ADAPT on page 4-65 ADAPT Operation on page 4-66 Network Support on page 4-66 ADAPT Requirements on page 4-67 ADAPT Configuration Parameters on page 4-68 ADAPT Triggers on page 4-70 ADAPT Resiliency on page 4-70
Infinera Corporation
Page 4-65
dow The Power Control Loop between the SIM modules and the active OFM modules is performed in order to balance the per channel power when channels are added from the SIMs to the OFM modules and when the channels are dropped from the OFM to the SIM modules. This is accomplished by setting the VOA accordingly at the OFMs. Figure 4-33 Power Control Loop between SIM and OFM
Gain control of AAMs across spansAAM gain adjustment to achieve the desired per-channel
launch power as determined by the network design The Gain Control loop across the spans is used to adjust the gain targets on the AAM on a span-byspan basis. Each of the digital span links runs the Adapt Protocol instance in a uni-directional mode, identified by the Head End (source of the link) and Tail End (destination of the link). ADAPT protocol can be triggered during the addition/removal of new channels. If the hub-site is passive, then it is recommended that a manual method be followed at such hub-site.
Infinera Corporation
Release 2.0
Page 4-66
ADAPT Operation
ADAPT uses a state protocol to distribute information to all network elements. It is run on an OSC
based control channel and nodal information is exchanged via this protocol.
ADAPT is run on a per link basis, where a link is defined as one or more fiber spans starting or end-
ing at a hub node, terminal node or OADM node.When ADAPT is enabled and is run in a network with multiple links, link details such as channel number and ASE ratio of express channels are passed from the uplink to the downlink at the link boundary. If the uplink is broken (e.g. if there is an Optical Loss of Signal i.e. OLOS at the express port on the OFM), the down link will still continue to run, and the add channel power is dictated by the local add channel target power.
The user can configure an ADAPT Timer (i.e. the time period that ADAPT is to be run) from the ATN
GNM. Various ADAPT triggers such as enabling ADAPT, VOA adjustment or AAM gain adjustment performed by ADAPT, etc. start an ADAPT cycle and sets the value of a "commit pending flag" on the link as true. A commit pending flag that is set to true indicates that one or more network changes are present. Even without any triggers, ADAPT is run at a pre-defined interval (400 seconds).
A commit pending flag indicates if any network changes are to be committed or not. If the ADAPT "commit pending flag" on the link is set as "false", it means that there are no pend-
ing network changes to be commited OR ADAPT has run and commit is complete.
If the ADAPT "commit pending flag" on the link is set as "true", it means that ADAPT has been
enabled and a commit is pending i.e. the pre-defined cycle is not yet complete OR ADAPT calculations were made, but changes were not applied succesfully and so network settings such as channel numbers, fiber connections, SIM to OFM connections etc. need to be verified.
Once the ADAPT Timer expires, ADAPT is automatically disabled and any new pending network
change commits are also disabled. During the period the timer is active, ADAPT can be disabled manually.
Network Support
ADAPT power management is supported on the following equipment: AAM-P1, AAM-B1, AAM-P2 and AAM-B2 Amplifier modules 4-channel and 2-channel Active OFMs (i.e. OFMs with Variable Optical Attenuators) ADAPT power management is supported on the following networks: Amplified linear or ring DWDM networks Networks with active OFMs used as edge nodes and Passive OFMs used at hub nodes Networks with active OFMs used as edge nodes and active OFMs used at hub nodes Networks with up to six amplifier sites between two OFM sites Networks with a mix of 2-channel and 4-channel active OFMs Networks with OPSW modules
Infinera Corporation
Page 4-67
ATN-DTN networks i.e. networks between an ATN active OFMand a DTN TAM-2-10GT or DTN
TOM
ADAPT power management is not supported on the following networks: Non-amplified DWDM networks CWDM networks Networks with passive OFMs used on edge nodes ATN-DTN networks between an ATN passive OFM and a DTN TAM-2-10GT or DTN TOM
ADAPT Requirements
Table 4-2 on page 4-67 describes the system requirements, inter-nodal and intra-nodal connection information required for ADAPT to run. Table 4-2 ADAPT Requirements
Requirement System Requirements AMM and OSC connectivity OSC connectivity is required to carry ADAPT information AMM is required to run ADAPT protocol and perform link discovery Maximum of 12 nodes in a ring network Bi-directional connectivity ADAPT is supported on ring networks with up to 12 nodes only ADAPT calculations are uni-directional and independent of the other direction, but bi-directional OSC connectivity is required. Intra-nodal Link Connectivity SIM to OFM connections OFM-1-OSC or AAM to OFM connections OFM-1-OSC or AAM OSC to AMM OSC connections Connections between two OFMs This connection is configured on manual fiber patch creation This connection is configured on manual fiber patch creation This connection is configured on manual fiber patch creation This connection is configured on manual fiber patch creation Inter-nodal Link Connectivity ATN to ATN connections ATN OFM to DTN TOM connections This connection is auto-discovered via OSC This connection is configured manually on the Trib port Description
Infinera Corporation
Release 2.0
Page 4-68
Infinera Corporation
Page 4-69
Infinera Corporation
Release 2.0
Page 4-70
ADAPT Triggers
The following trigger an ADAPT cycle:
C-band OLOS cleared OSC LOL cleared Change in maximum number of channels configured Change in Received Power Change in number of Effective Channels Change in active OFM VOA offset Change in Add channel target power Change in AAM launch power offset Change in transmit fiber type Enable ADAPT
ADAPT Resiliency
ADAPT operations are resilient and ADAPT protocol can be run under the following conditions:
Any service affecting fault on other modules or links Recovery from service affecting faults on other links Addition of add/drop or express channels Removal of add/drop or express channels Control plane failure Control plane recovery Cold resets of other modules Un-plugging an AMM module while an ADAPT cycle is active Power cycle scenarios
Infinera Corporation
Page 4-71
element through a DCN network which is typically an IP-based network. The DCN is designed in such a way that there is no single point of failure within the DCN network. (See DCN Communication Path on page 4-71.)
In-band access through Layer 2 Switch and Spanning Tree Protocol. (See Layer 2 Switch and
on page 4-77.) IQA NOS ATN management plane supports Network Timing Protocol (NTP) to provide accurate time stamping of alarms, events and reports from the network element. (See Time-of-Day Synchronization on page 4-77.)
Infinera Corporation
Release 2.0
Page 4-72
The Primary DCN IP addresses of each ATN connected in the same optical network must be in the
Spanning Tree Protocol does not have to be enabled on the AMM DCN port (see Figure 4-34 on page 4-72).
If more than one ATN will be physically connected to the DCN, Spanning Tree Protocol must be
enabled on all of the AMM DCN ports prior to connecting to the DCN (see Figure 4-35 on page 473).
If the DCN is also using a private address, the Craft IP Address should use a different prefix from the
DCN.
Use the same Craft IP Address for all network elements in the Infinera Digital Optical Network.
Infinera Corporation
Page 4-73
Infinera Corporation
Release 2.0
Page 4-74
10.0.0.0 - 10.255.255.255 (10/8 prefix) 172.16.0.0 - 172.31.255.255 (172.16/12 prefix) 192.168.0.0 - 192.168.255.255 (192.168/16 prefix) If the DCN is also using a private address, the Craft IP Address should use a different prefix from the
DCN.
Use the same Craft IP Address for all network elements in the Infinera Digital Optical Network.
Infinera Corporation
Page 4-75
which can cause loops to be formed in the Layer 2 topology and also to reach all the nodes in the topology
STP runs on Layer 2 nodes, periodically synchronizes the Layer 2 topology database, maintains a
loop-free network, and also helps in recovery from link failures The ATN AMM includes a Layer 2 Ethernet Switch. For unicast frames, if the forwarding switch interface is determined from the MAC address table, the frames are forwarded directly to their destination. Otherwise, the frames are forwarded out all of the other switch interfaces. All broadcast or multicast frames received by a node on any interface are forwarded to all other switch interfaces.
Infinera Corporation
Release 2.0
Page 4-76
DCN-only communication
Infinera ATNs can be connected via DCN only and may not have OSC connectivity or Layer 2 switching. Figure 4-38 on page 4-76 shows an ATN network with DCN connectivity only. Figure 4-38 ATN Network with only DCN connectivity
Infinera Corporation
Page 4-77
In case of networks with DCN-only connectivity, the following operations can be performed from the Infinera ATN GNM and Infinera DNA:
Configuring the network element Configuring and Pre-provisioning cards for that node Viewing inventories and alarms pertaining to that node Viewing PM data
Since OSC connectivity is not present, network neighborhood information cannot be obtained and due to this the following related functions are not supported via management applications such as ATN GNM and DNA:
Neighboring Node information is not available Control Links and ATN-DTN links cannot be configured or discovered Network tools such as Digital Link Viewer, Circuit Manager, Circuit Diagnostic Manager are not
available
ATN circuits and ATN-DTN circuits cannot be created ADAPT cannot be run on the network
For more information on operations that can be performed without OSC connectivity, refer to Infinera ATN GNM User Guide and Infinera DNA User Guide.
Static Routing
IQA NOS ATN provides static routing capability. One application of static routes is to enable the network elements to reach external networks that are not part of the DCN network. For example, if the NTP Server is located in an external network, outside of the DCN network, users can configure the static routes to connect to the NTP server in the external network. Another application of static routing is to enable the routing of the management traffic between two topology partitions. There might be a need to create topology partitions within a single physical network. In such situations, users can still have the management communication path between two topology partitions by configuring static routes to reach network elements in other topology partitions. In the Infinera ATN, the configured static routes cannot be assigned weights and users cannot configure the ability to advertise static routes.
Time-of-Day Synchronization
IQA NOS ATN provides accurate and synchronized timestamps on events and alarms. The synchronized timestamp eases the network-level debugging and eliminates the inaccuracies caused by the manual configuration of system time on each network element. Additionally, the timestamp complies with Universal Coordinated Time (UTC) format, found in ISO 8601, and includes granularity down to seconds.
Infinera Corporation
Release 2.0
Page 4-78
IQA NOS ATN supports both NTP Client and Server for Time-of-Day synchronization. Time of day synchronization can be manually updated by setting the clock to UTC, or automatically by implementing the local NTP client and synchronizing it with an external NTP server. Figure 4-39 NTP Server Configuration
IQA NOS ATN also implements NTP Server, so that one network element may act as an NTP Server to the other network elements that do not have access to the external NTP Server (see Figure 4-40 on page 478). Figure 4-40 ATN acting as NTP Server
The ATNs also provide a local clock with the accuracy of 23ppm or about a minute per month. If an ATN with NTP enabled fails to access an external NTP server, the IQA NOS ATN NTP will use the local clock as a reference for both the Client and Server. When the connectivity to the external NTP Server is restored, IQA NOS ATN NTP Client and Server re-synchronizes with the external NTP Server, and the new synchronized time is propagated to all the network elements within the routing domain. Following are some recommendations for configuring the NTP Server within a Digital Optical Network:
Configure an external NTP Server with Stratum Level 4 or higher clock for each routing domain of a
Infinera Corporation
Page 4-79
Digital Subnetwork Connection Protection (D-SNCP) defines and provisions a working and protection facility for client services. Digital SNCP services are based on the SONET/SDH-like characteristics of the OTN overhead, and very closely mirror GR-1400/G.841 UPSR/SNCP protection architectures. In this protection architecture, a dedicated protection path is provisioned for each protection group. D-SNCP has optical and digital protection triggers.
Optical Subnetwork Connection Protection (O-SNCP) on page 4-89
Optical Subnetwork Connection Protection (O-SNCP) defines and provisions a working and protection facility for line services. O-SNCP has only optical triggers.
Note: Loopbacks are not supported on facilities that are 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. For more information on loopbacks, see Loopbacks on page 4-11.
Two-Port D-SNCP
Two-port D-SNCP offers the highest level of service protection on all interface points within the optical network. Two-port D-SNCP provides end-to-end fiber and equipment protection of optical services. It protects against SIM failures and line-side failures by using two SIMs connected to client equipment at
Infinera Corporation
Release 2.0
Page 4-80
each end of the network path. Two-port DSNCP is supported by the SIM-T-1-10G, SIM-T-2-2.5GM, SIM-T1-10GT, SIM-T-1-10GP, SIM-T-1-10GM and SIM-A-8-2.5GMT. In Two-port D-SNCP, Y-cables (optical signal splitter/combiners) are connected to the client equipment at either end of the network. As shown in Figure 4-41 on page 4-81 and Figure 4-42 on page 4-82, the Ycables at the ingress point directs two identical copies of the client signal to two different SIM interfaces on the originating ATN. These two interfaces receive the duplicate client signals and transmit them through the network. Each signal is transported independently to the destination node, typically along diverse routes. Note: In two-port D-SNCP, the ingress endpoints must be on the same physical chassis of the originating node. Likewise, the egress endpoints must be on the same chassis of the terminating node. In other words, a Y-cable used for two-port D-SNCP cannot be connected to termination points on two different chassis or paired slots. At the destination node, the ATN monitors both signal paths and, depending on signal quality, switches the appropriate signal towards the client equipment. Only one of the two digital path-level signals is enabled at the egress. In the event of a datapath failure (due to facility or equipment failures), an automatic protection switch mechanism at the destination node switches the redundant copy of the client signal to transmit on the Ycable at the egress, with sub-50ms switching speeds. User-generated switching requests are also supported. Protection switching on an ATN is not auto revertive. If the user wants to switch traffic back to the working unit after a protection switch, and the working unit comes back into service, the user must issue a Manual Switch. Figure 4-41 on page 4-81 displays an example of two-port D-SNCP protection with SIM-T-1-10G.
Infinera Corporation
Page 4-81
Figure 4-42 on page 4-82 displays an example of two-port D-SNCP protection with SIM-T-2-2.5GM.
Infinera Corporation
Release 2.0
Page 4-82
The ATN chassis provides paired-slot protection interconnect, enabling faster hardware-assisted protection switch-over. The slot and TOM pairing for two-port D-SNCP protection in the ATN is as follows:
Slot1-Port1 and Slot3-Port-1 Slot1-Port2 and Slot3-Port2 Slot2-Port1 and Slot4-Port1 Slot2-Port2 and Slot4-Port2 Slot5-Port1 and Slot7-Port1 Slot5-Port2 and Slot7-Port2 Slot6-Port1 and Slot8-Port1 Slot6-Port2 and Slot8-Port2
Infinera Corporation
Page 4-83
Infinera Corporation
Release 2.0
Page 4-84
Unit (PU). To configure Digital SNCP services, PGs must be defined on each ATN at both ends of the network (origin and destination). In Digital SNCP, one PU in each PG is identified as the Working PU, and the remaining PU is identified as the Protect PU. This designation, called the PU Configured State, identifies the Working path - the path used in the absence of network failures - and the Protect path - the path used in the event of a network failure. When the system is running, and at the origin node, both Working and Protect PUs send any datapath traffic they receive from the client side to the network interfaces of the ATN, resulting in two transmission circuits through the Digital Optical Network. The Working and Protect paths are generally routed through completely diverse paths through the network. At the destination node, the receiving ATN terminates both paths on the far-end Working and Protect PUs. The receiving ATN evaluates the quality of both paths received on the PG, and enables either of the two PUs to actively transmit traffic to the far-end client. In the absence of any prior protection switch activity, the Working PU is the active PU at the destination node. The other PU exists in a standby state (in Two-port DSNCP, the Protect PU will power off its transmission laser in the standby state).
The configured state reflects the user-preferred Working/Protect designation for the PU. During the creation of each protection group, users must designate one protection unit as the Working PU and the other protection unit as the Protect PU. The Working PU is the preferred PU for transmitting the traffic signal to the client in the absence of network failure. The Protect PU provides protection functionality in that it only transmits the traffic signal to the client when a protection switch occurs.
Actual State
The actual state of a protection unit is a system-derived state that reflects the actual operating state of the PU. The actual state of a PU may be one of the following:
ActiveThe PU is currently providing full service, carrying datapath traffic in both directions. Hot StandbyThe PU is not active, but is healthy and able to provide protection service if called
upon.
Cold StandbyThe PU is not active, and its operational state renders it unable to provide protec-
Infinera Corporation
Page 4-85
types
There must not be any loopbacks on any of the tributary or line TOMs that are a part of the Protec-
tion Group
The SIM slot numbers must match the protection paired slot numbers The Tributary TOM numbers must be the same. For example, Tributary TOM 1 on Slot #1 and Trib-
utary TOM 1 on Slot #3. This rule is not applicable for two-port D-SNCP on a SIM-A-8-2.5GMT.
Infinera Corporation
Release 2.0
Page 4-86
Switching requests are part of a switching hierarchy and can be escalated by the status of the received path, or assigned by the user at the tail-end of the PG. Requests supported within a PG are escalated with the priority specified in Table 4-4. Table 4-4 D-SNCP Switching Requests and Priority
Priority Level (1 = Highest, 3 = Lowest) 1
Description User generated request to prevent a PU (within a PG) from ever becoming active. A supported type of lockout request is Lockout on Protect. Users can also issue a request to clear a Lockout. Network or service-generated fault are escalated to a service state (LOS, BER, etc.), causing a protection switch request. User generated, non-latching (no associated state) protection switch request.
WARNING All switches (manual, automatic, lockout) cause a 50ms (or less) interruption to traffic.
Infinera Corporation
Page 4-87
Figure 4-5 describes protection types supported on a SIM and the protection triggers. Table 4-5 D-SNCP Protection on SIMs
SIM Type SIM-T-1-10G D-SNCP Protection Type 2-Port (1+1) Uni-directional D-SNCP Protection Triggers Line Side OLOS, Line Side LOL, Line Side OTU LOF, Post-FEC BER SF, Module Absent, DE-ENCAP-LOSYNC, DEENCAP-LOF, DE-ENCAP-AIS, Client Side OLOS, Client Side LOS, Client Side LOF, Client Side LOSYNC Line Side OLOS, Line Side LOL, Line Side DCH LOF, DTP LOF, Post-FEC DTP BER SF, DTP AIS, Module Absent, DEENCAP-LOS, DE-ENCAP-LOF, DEENCAP-AIS, Client Side OLOS, DEENCAP-LOSYNC, Client Side OLOS, Client Side LOS, Client Side LOF, Client Side LOSYNC Line Side OLOS, Line Side LOL, Line Side OTU LOF, Post-FEC BER SF(When FEC is enabled), Module Absent, DE-ENCAPLOS, DE-ENCAP-LOSYNC, DE-ENCAPLOF, DE-ENCAP-AIS, Client Side OLOS, Client Side LOS, Client Side LOF, Client Side LOSYNC Line side OLOS, Line side LOL Line Side OLOS, Line Side LOL, Line Side OTU LOF, Post-FEC BER SF(When FEC is enabled), Module Absent, DE-ENCAPLOS, DE-ENCAP-LOSYNC, DE-ENCAPLOF, DE-ENCAP-AIS, Client Side OLOS, Client Side LOS, Client Side LOF, Client Side LOSYNC Line Side OLOS, Line Side LOL, Client Side OLOS, Client Side LOS Line side OLOS, Line side LOL, Client Side OLOS, Client Side LOS
SIM-T-1-10GT
SIM-T-1-10GP
SIM-T-2-2.5GM
Infinera Corporation
Release 2.0
Page 4-88
For both two-port D-SNCP and one-port D-SNCP, the path chosen as the working path is a local decision. This means that each end of the circuit chooses which signal to use independently. Each end of the circuit may pick a different path as the working path. Equipment faults on modules in the terminating PU's datapath (AAM, SIM, or TOM) may also generate path or line-level faults, escalating the switching request on the remote end as well. Additionally, other equipment related defects/failures that generate switching requests include:
A module removal defect Any defect that (after integration) maps to an EQPTFAIL alarm Any defect that (after integration) maps to an EQPT-PARTFAIL alarm and that affects a PU's datap-
ath traffic
This is supported if the Working PU is on stand-by Note: If a failure occurs on the Working circuit while a Lockout of Protect is in effect, traffic cannot switch to the Protect circuit until the lockout is cleared. This will result in loss of traffic. The lockout commands are useful in supporting maintenance operations by an operator.
Page 4-89
No events are logged during the period when the AMM is absent or inactive.
Clear Lockout
There is no dependency on the AMM for auto-switching operations On activating an inactive AMM, it re-synchronizes with the protection status of the ATN
Infinera Corporation
Release 2.0
Page 4-90
O-SNCP using OPSW modules provides path protection through the network. The OPSW-1 is a one client port two line ports module and OPSW-2 is a two client ports fours line ports module that provide protection switch capability on the ATN platform. OPSW-1 provides one protection service, while OPSW-2 provides two protection services.
O-SNCP using SIM-A-8-2.5GMT
The SIM-A-8-2.5GMT is an eight client ports and two line ports muxponder. It aggregates multiple service interfaces into OTU2v/DTF waves. It has dual line ports for built-in O-SNCP protection.
ATN supports automatic O-SNCP protection switching due to optical triggers. For example, if the active line port detects an optical trigger, such as OLOS failure, and the standby port is neither locked out nor has
Infinera Corporation
Page 4-91
OLOS failure, automatic switching to the standby port. takes place. However, if the standby port has either OLOS failure or is locked out, the active line port does not switch. OPSW modules can be used to provide to provide the following types of path protection services:
Protection per optical channel (i.e. service)
One OPSW-1 or OPSW-2 is used per SIM to provide protection on a per optical channel basis (see Figure 4-45 on page 4-91) Figure 4-45 OSNCP per optical channel
One OPSW-1 or OPSW-2 is used for all SIMs to provide protection on a per optical band basis (see Figure 4-46) Figure 4-46 OSNCP per optical band
Infinera Corporation
Release 2.0
Page 4-92
designated client tributary port is called a Protection Unit (PU). To configure Optical SNCP services, PGs must be defined on each ATN at both ends of the network (origin and destination). In Optical SNCP, one PU in each PG is identified as the Working PU, and the remaining PU is identified as the Protect PU. This designation, called the PU Configured State, identifies the Working path - the path used in the absence of network failures - and the Protect path - the path used in the event of a network failure. When the system is running, and at the origin node, both Working and Protect PUs send any datapath traffic they receive from the client side to the network interfaces of the ATN, resulting in two transmission circuits through the Digital Optical Network. The Working and Protect paths are generally routed through completely diverse paths through the network. At the destination node, the receiving ATN terminates both paths on the far-end Working and Protect PUs. The receiving ATN evaluates the quality of both paths received on the PG, and enables either of the two PUs to actively transmit traffic to the far-end client. In the absence of any prior protection switch activity, the Working PU is the active PU at the destination node.
The configured state reflects the user-preferred Working/Protect designation for the PU. During the creation of each protection group, users must designate one protection unit as the Working PU and the other protection unit as the Protect PU. The Working PU is the preferred PU for transmitting the traffic signal to the client in the absence of network failure. The Protect PU provides protection functionality in that it only transmits the traffic signal to the client when a protection switch occurs.
Actual State
The actual state of a protection unit is a system-derived state that reflects the actual operating state of the PU. The actual state of a PU may be one of the following:
ActiveThe PU is currently providing full service, carrying datapath traffic in both directions. Hot StandbyThe PU is not active, but is healthy and able to provide protection service if called
upon.
Cold StandbyThe PU is not active, and its operational state renders it unable to provide protec-
Infinera Corporation
Page 4-93
is provisioned, one or two O-SNCP protection groups (PGs) are respectively created.
The tributary and line TOMs that are a part of the protection group must be provisioned There must not be any loopbacks on any of the tributary or line TOMs that are a part of the Protec-
tion Group
Description User generated request to prevent a PU (within a PG) from ever becoming active. A supported type of lockout request is Lockout on Protect. Users can also issue a request to clear a Lockout. Network or service-generated fault are escalated to a service state (LOS, BER, etc.), causing a protection switch request. User generated, non-latching (no associated state) protection switch request.
WARNING All switches (manual, automatic, lockout) cause a 50ms (or less) interruption to traffic.
Infinera Corporation
Release 2.0
Page 4-94
This is supported if the Working PU is on stand-by Note: If a failure occurs on the Working circuit while a Lockout of Protect is in effect, traffic cannot switch to the Protect circuit until the lockout is cleared. This will result in loss of traffic. The lockout commands are useful in supporting maintenance operations by an operator.
No events are logged during the period when the AMM is absent or inactive.
Infinera Corporation
Page 4-95
Clear Lockout
There is no dependency on the AMM for auto-switching operations On activating an inactive AMM, it re-synchronizes with the protection status of the ATN
Infinera Corporation
Release 2.0
Page 4-96
Infinera Corporation
CHAPTER 5
page 5-3)
Infinera Digital Network Administrator (see Infinera Digital Network Administrator (DNA) on page 5-
9)
Infinera SNMP Agent (see Infinera SNMP Agent on page 5-10) Command Line Interface (CLI) (see Command Line Interface (CLI) on page 5-11) Infinera Network Planning System (NPS) (see Infinera Network Planning System (NPS) on
page 5-12) Figure 5-1 on page 5-2 below shows how the various applications in the Infinera Management Suite work together in the Infinera Digital Optical Network.
Infinera Corporation
Release 2.0
Page 5-2
Infinera Corporation
Page 5-3
Refer to the Infinera ATN GNM User Guide for a detailed description of the graphical user interface and detailed procedures for managing Infinera network elements.
Infinera Corporation
Release 2.0
Page 5-4
Graphical representation of the ATN in the Equipment View window A drill-down tree view of the network element, chassis and circuit packs in Equipment Tree window A Quick View Browser that summarizes information on hardware equipment selected in the Equip-
Infinera Corporation
Page 5-5
Filter and search capabilities across inventory views Refresh and freeze inventory data Support for 1024 x 768 square pixel wide view high resolution screens
ated by another ATN GNM user via another ATN GNM session.
Users can right-click on the nodes in the topology view and launch Infinera ATN GNM for those net-
work elements. Note: Unreachable network elements are not displayed in the Network Neighborhood view.
Inventory Management
Infinera ATN GNM includes Inventory Manager applications through which users can monitor and also manage various resources in the network element. The following inventory applications are provided:
Equipment ManagerTo view and manage the equipment inventory including chassis and circuit
packs.
Facility ManagerTo view and manage the inventory of termination points including physical ports
Digital Protection Services on page 4-79. The inventory information is displayed as a table from which users can perform context-sensitive launching of other applications.
Infinera Corporation
Release 2.0
Page 5-6
Fault Management
Infinera ATN features fault monitoring and management capabilities that provide real-time information on the status of all the managed entities. Developed in accordance with Telcordia and ITU standards, the fault management features include a standards-based current alarm table that tracks outstanding alarm conditions within the target network element, and a wrap-around historical event log that tracks all changes that occur within the target network element including user-initiated state and attribute change events. Infinera ATN GNM provides two fault management tools:
Alarm ManagerDisplays outstanding alarm conditions. Alarm conditions display category, sever-
ity, source, time of occurrence, acknowledgement check, service-affecting or non-service affecting and probable cause.
Event LogDisplays historical event logs. Events display event type, severity, source, time of
Infinera Corporation
Page 5-7
(ASAP) feature.
control environmental alarms by configuring output closure contacts and input closure contacts. clear or leave outstanding alarms, using the Alarm Reporting Control (ARC) feature. export all alarms and events. export current view of alarms and events. filter alarms and events. sort alarms and events based on all the fields, in both ascending and descending order.
cedures.
Graceful handling of the scenarios where multiple users access and configure the same managed
object. When a user tries to modify a managed object which is modified by another user at the same time, the network element warns the user of possible overwriting and it performs the action only if user accepts the overwriting.
Performance Management
Infinera ATN GNM provides a user interface to support the IQA NOS ATN performance management functions described in Performance Monitoring and Management on page 4-41. It provides extensive digital and analog performance monitoring and flexible performance parameter management. These features can help reduce overall operational costs associated with fault isolation and troubleshooting in the transport domain.
Infinera Corporation
Release 2.0
Page 5-8
The system provides an extensive collection of performance monitoring (PM) data, including:
Forward Error Connection (FEC) PM data at the ATN Native Client (such as SONET/SDH/GbE/FC/DTP/OTN/DchCTP) PM data at tributary ports Optical PM parameters (such as Trib, Line, Band, OSC, OCG and OTS PTP PM data) Optical Transport Unit (OTU) PM data Digital Transport Frame (DTF) PM data
Security Management
Infinera ATN GNM provides control of the network element security features in compliance with the GR815-CORE standard. This includes support for multiple-user access privileges, the ability to create/delete/ modify user accounts, user ID and password authentication. For more information, see Security and Access Management on page 4-46. The Infinera ATN GNM security administration capabilities enable users to:
manage network element user accounts, including the ability to add new users, modify user attri-
privilege to:
configure the security parameters. configure Remote Authentication Dial-In User Service (RADIUS) server settings configure Secure Shell (SSH)
Infinera Corporation
Page 5-9
Alarm Severity Assignment Profile Setting (ASAP), FTP, RADIUS, PM upload scheduling, and security applications support for ATN nodes, as well as support for the ATN Fiber Connectivity Manager and for ATN Link Viewer and DTN Link Viewer, and for ATN Channel Map Viewer and DTN Channel Map Viewer. Refer to the Infinera DNA Administrator Guide and the Infinera DNA User Guide for a detailed description of the DNA and detailed procedures for managing the Infinera Digital Optical Network.
Infinera Corporation
Release 2.0
Page 5-10
Infinera Corporation
Page 5-11
Infinera Corporation
Release 2.0
Page 5-12
protect, as well as graphical circuit trace and nodal flow while allowing assignment of circuit to equipment.
Allow for global or specific constraints, such as controller redundancy or multi-chassis configura-
tions.
Create an economic model for carrying larger quantities of traffic. Evaluate overall utilization of an existing network from the perspective of bandwidth capacity as well
demands between nodes (route and distance), and equipment count reports.
Produce a list of all field-replaceable units (FRUs) required to support the network design, along with
information about how each node is to be configured (e.g., slot assignments, cross-connects, etc.).
Produce quotes and customized reports. Use incremental capacity modeling to design a network that adds new equipment in incremental
phases. Figure 5-3 on page 5-13 below shows the NPS main window.
Infinera Corporation
Page 5-13
The NPS tool works by taking user specified input through the GUI or importing information in the form of comma-separated values (.csv) files, tab-separated values (.tsv) files or excel (.xls or .xlsx) files that contain the parameters of the network, such as available nodes, links, demands, and processing these files to create output files and reports that detail the network topology and equipment configuration. The input can be used to generate a greenfield network design or establish a baseline network plan using output from existing greenfield network designs or an Infinera Digital Network Administrator (DNA) export. Then, a user can make incremental network design changes beyond the baseline. NPS has an interactive GUI to enable the user to analyze results and provides detailed site and nodal equipment configuration such as optical line system requirements by defining optical module types, DCF, pads, and OSNR as well as layout configuration requirements. It allows a user to make global or specific constraints such as single/redundant MCM or multi-chassis configurations. NPS provides traffic routing and data path flow information by detailing circuit layout record, working and protect as well as graphical circuit trace and nodal flow while allowing circuit assignment to equipment. It can provide site engineering details such as space, power, fiber connectivity in a report, create demand summary reports detailing traffic demands between nodes (route and distance) and circuit pack count. For a detailed description of how to use the Infinera NPS, refer to the Infinera Network Planning System (NPS) User Guide.
Infinera Corporation
Release 2.0
Page 5-14
Infinera Corporation
Appendix A
Alarm in the Alarm Type column. For a complete description of each alarm, refer to the Infinera ATN Alarm and Trouble Clearing Guide.
Infinera Corporation
Release 2.0
Page A-2
AIS-L AIS-MS BANDOPT-TOO-LOWa BDI-DCH BDI-DTP DE-ENCAP-AIS-L DE-ENCAP-AIS-MS DE-ENCAP-LOF DE-ENCAP-LOS DE-ENCAP-LOSYNC DROPBAND-OLOSb DROPBAND-OPT-TOOLOWb DROP-CHAN-PWR-OORH DROP-CHAN-PWR-OORL EQPTCPUR
c
Client LOF Client LOF EQPTCPUR-AAM, EQPTFAIL-AAM, IMPROPRMVL-AAM LOF-DCH LOF-DTP, BDI-DCH, AIS-DTP DE-ENCAP-LOF, DE-ENCAP-LOS DE-ENCAP-LOF, DE-ENCAP-LOS DE-ENCAP-LOS OTUk LOF, AIS-DTP, LOF-DTP, LOFDCH OTUk LOF, AIS-DTP, LOF-DTP, LOFDCH EQPTCPUR-OFM, EQPTFAIL-OFM, IMPROPRMVL-OFM DROPBAND-OLOS,EQPTCPUROFM, EQPTFAIL-OFM, IMPROPRMVL-OFM DROPBAND-OPT-TOO-LOW DROPBAND-OPT-TOO-LOW IMPROPRMVL IMPROPRMVL IMPROPRMVL
EQPTCPUR - OPSWf
IMPROPRMVL
Infinera Corporation
Page A-3
Alarm Type EQPTCPUR - SIM/AMM EQPTFAIL EQPTFAIL - SIM/AMM EQPTDEGRADE - AAM EQPTDEGRADE - OFM EQPTFAIL EQPTFAIL - OFM
Masked Alarm(s) EQPTFAIL-TOM, IMPROPRMVLTOM UNKNOWNFW EQPTFAIL-TOM, IMPROPRMVLTOM None None UNKNOWNFW EQPT-DEGRADE OFM, OLOS Trib PTP, DROPBAND-OLOS, OLOSATNOCGPTP, INSUFFICIENTATTENUATION OLOS Trib PTP EQPTFAIL-TOM, IMPROPRMVLTOM BANDCTP-OLOS, BANDPTP-OLOS OLOS TRIBPTP IMPROPRMVLg None None None None EQPTCPUR, EQPTFAIL, EQPTMSMT, UNKNOWNFW, TEMPOORH, TEMP-OORL, TEMP-OORDEVICE-SHUTDOWN BANDCTP-OLOS, BANDPTP-OLOS EQPT-DEGRADE OFM, OLOS Trib PTP, DROPBAND-OLOS, OLOSATNOCGPTP, INSUFFICIENTATTENUATION OLOS Trib PTP EQPTFAIL-TOM, IMPROPRMVLTOM OLOS Trib PTP, OLOS OSC PTP, LOSYNC None
Masking Alarm(s) IMPROPRMVL IMPROPRMVL, EQPTCPUR IMPROPRMVL, EQPTCPUR OPT-OORH - BandCTP, IMPROPRMVL, EQPTCPUR IMPROPRMVL, EQPTCPUR IMPROPRMVL, EQPTCPUR None
EQPTFAIL - OPSW EQPTFAIL - SIM/AMM EQPTFAIL - AAM EQPTFAIL - TOM EQPTMSMT EXCHAN FP-MIS-CONNh GAIN-OORH GAIN-OORL IMPROPRMVL
None IMPROPRMVL, EQPTCPUR IMPROPRMVL, EQPTCPUR EQPTFAIL - SIM/AMM, IMPROPRMVL IMPROPRMVL IMPROPRMVL, EQPTCPUR OLOS - Trib PTP IMPROPRMVL, EQPTCPUR IMPROPRMVL, EQPTCPUR None
None None
Infinera Corporation
Release 2.0
Page A-4
Masked Alarm(s)
Masking Alarm(s) OLOS Trib PTP LOS - OTUk CTP LOF DCH
PRE-FEC-BER-SD, PRE-FEC-BERSF, TIM-OTU-S, DE-ENCAP-LOF AIS-DTP, PLM-DTP, TIM-DTP, DEENCAP-LOS, DE-ENCAP-LOSYNC, BDI-DTP LOF-DTP, POST-FEC-BER-SFDCH, PRE-FEC-BER-SD-DCH, TIMDTS, DE-ENCAP-LOS, DE-ENCAPLOSYNC, BDI-DCH RFI-L Client CTP, RFI-MS Client CTP, AIS-L Client CTP, AIS-MS Client CTP None LOF - OTUk CTP LOF - DCH LOF - Client CTP PLM None None EQPTDEGRADE - AAM OPT-OORH - BandCTP None LOS-SONET/SDH/OTUk/ClearChan Client CTP, LOSYNC, MIS-CONN FP-MIS-CONN, INSUFFICIENTCHAN-PWR, ADD-CHAN-PWROORH/L Trib PTP FP-MIS-CONN LOLINK None None PRE-FEC-BER-SD-DCH None
LOF - DCH
LOS DCH
LOLINK - OSC PTP LOS - OTUk CTP LOS - DCH LOS - Client CTP LOSYNC MIS-CONNi OLOS ATNOCGPTPj OPT-OORH - BandCTP OLOS Band CTP OLOS BAND PTPk OLOS Trib PTPl OLOS Trib PTPm
OLOS - OSC PTP OLOS - Trib PTP OLOS - Trib PTP OLOS - Trib PTP OLOS - Trib PTP OLOS - Trib PTP EQPTCPUR-OFM, EQPTFAIL-OFM, IMPROPRMVL-OFM OLOS - BANDCTP EQPTCPUR-AAM, EQPTFAIL-AAM, IMPROPRMVL-AAM EQPTCPUR-AAM, EQPTFAIL-AAM, IMPROPRMVL-AAM EQPTFAIL - TOM, IMPROPRMVLTOM EQPTCPUR-OFM, EQPTFAIL-OFM, IMPROPRMVL-OFM EQPTCPUR-OPSW, EQPTFAILOPSW, IMPROPRMVL-OPSW EQPTFAIL - TOM, IMPROPRMVL TOM LOSYNC - Clear Channel Client CTP LOF-DTP, AIS-DTP, TIM-DTP LOF-DCH POST-FEC-BER-SF - DCH, LOFDCH
OLOS Trib PTPn OLOS OSC PTP PLM PLM - DTP POST-FEC-BER-SF - DCH PRE-FEC-BER-SD - DCH
Infinera Corporation
Page A-5
Alarm Type POST-FEC-BER-SF PRE-FEC-BER-SD RFI-L Client CTP RFI-MS Client CTP TEMP-OORH TEMP-OORL TIM-OTU-S TIM-S TIM-DTP TIM-DTS UNKNOWNFW
a. b. c. d. e. f. g. h. i. j. k. l. m. n.
Masked Alarm(s) PRE-FEC-BER-SD None None None None None None None PLM-DTP None None
Masking Alarm(s) LOF-OTUk CTP POST-FEC-BER-SF, LOF - OTUk CTP LOF - Client CTP LOF - Client CTP IMPROPRMVL IMPROPRMVL LOF - OTUk CTP LOF - Client CTP LOF-DTP, AIS-DTP LOF-DCH EQPTFAIL, IMPROPRMVL
Applicable for AAM-B2 only Applicable for active OFMs only Applicable for all modules Applicable for all AAMs Applicable for all OFMs Applicable for all OPSWs An EQPTMSMT alarm suppresses an existing IMPROPRMVL alarm Applicable for active OFM's Trib PTP or OPSW Trib PTP if no OLOS and no Fiber patch are associated Applicable for GT/GM SIM TOMs due to auto-discovery failure Applicable for Express ports on active OFMs only Applicable for AAM-P2 only Applicable for SIM TOMs Applicable for Trib PTPs on active OFMs Applicable for Trib PTPs on OPSWs
Infinera Corporation
Release 2.0
Page A-6
Infinera Corporation
Appendix B
ATN PM Parameters
Infinera ATNs collect extensive PM data, including
Optical performance monitoring (PM) data within the optical domain (see Optical PM Parameters
Infinera Corporation
Release 2.0
Page B-2
The optical PM parameters are essentially gauges, snapshot of the current condition. The optical PM parameters, such as Optical Power Received (OPR) and Optical Power Transmitted (OPT), are the measures of the average optical power of the received and transmitted optical signals, respectively, in dBm. Table B-1 on page B-3 captures the optical PM parameters supported at each layer. The historical data is maintained for some PM parameters. Historical data is provided in both 15 minute and 24 hour capture periods. Real Time, or Intermediate, PM data is a valuable troubleshooting tool as it provides the user a snapshot of the current performance for the particular PM parameter. The user can set the Real Time PM
Infinera Corporation
ATN PM Parameters
Page B-3
refresh rate to automatically refresh the count at various increments from 5 seconds to never (thus locking the current view). Table B-1 Optical PM Parameters Supported on the ATN
Real-time Data Support Real-time TCA Support 15-min and 24-hr Data Support 15-min and 24-hr TCA Support
PM Parameter
Description
Unit
Client TribPTP and Line TribPTP Optical Parameters (collected on all SIM TOMs) Optical Power Received Optical Power Transmitted Laser Bias Current Average optical power received from trib TOM input or line TOM input Average optical output power transmitted onto the Trib TOM output or Line TOM output Laser bias current dBm Yes No Yes No
dBm
Yes
No
Yes
No
mA
Yes
No
Yes
No
Client TribPTP and Line TribPTP Optical Parameters (collected on OPSW-1 and OPSW-2) Optical Power Received Average optical power received from trib input or line input dBm Yes Yes Yes No
Optical Parameters (TribPTP) (collected in the 4-Channel DWDM Active OFM and 2-Channel DWDM Active OFM) Add Channel OPR PreVOA Add Channel OPR Optical power received from the Add Channel input Estimated Optical power received from the Add Channel input before the VOA dBm Yes Yes Yes No
dBm
Yes
No
Yes
No
ATN OCG PTP layer parameters (collected in the 4-Channel DWDM Active OFM and 2-Channel DWDM Active OFM) Express OPR Optical power received from the Express input dBm Yes Yes Yes No
Infinera Corporation
Release 2.0
Page B-4
PM Parameter
Description
Unit
OTS Layer Parameters (collected in the AAM-B1, AAM-B2 and AAM-P2) Line OPT to OSA Tap Ratio Expected TAP ratio of the Optical Power Transmitted (without OSC) and the power measured at the OSA Monitor Out port dB Yes No No No
Band PTP Layer Parameters (collected in the AAM-P1, AAM-P2, AAM-B2, OFM-1-OSC, 4-Channel DWDM OFMs, 4-Channel Active DWDM OFMs and 2-Channel Active DWDM OFMs)
AAM-B2 and AAM-P1 Band PTP Layer PM Note: Only the Band OPT to OSA Tap Ratio PM parameter is available for the AAM-P1
Optical Power Transmitted Band OPT to OSA TAP Ratio Average optical output power transmitted from the Facility output Expected TAP ratio of the Optical Power Transmitted and the power measured at the OSA Monitor Out port Insertion Loss between the power received at the Line IN port to the power transmitted from the Facility OUT port Expected TAP ratio of the Optical Power Received at the Facility IN port and the power measured at the OSA Monitor Out port Average optical power received at the Facility input dBm Yes Yes Yes No
dB
Yes
No
No
No
dB
Yes
No
No
No
Infinera Corporation
ATN PM Parameters
Page B-5
Description Expected TAP ratio of the Optical Power Transmitted and the power measured at the OSA Monitor Out port Insertion Loss between the power received at the FacilityIN port to the power transmitted from the Line OUT port Expected TAP ratio of the Optical Power Received at the Facility IN port and the power measured at the OSA Monitor Out port Expected TAP ratio of the Optical Power Transmitted from the Facility OUT port and the power measured at the OSA Monitor Out port Measured loss between the facility input and the express output Measured loss between the express input and the band output
Unit dB
dB
Yes
No
No
No
dB
Yes
No
No
No
Band OPR to Express OPT Loss Express OPR to Band OPT Loss
dB
Yes
No
No
No
dB
Yes
No
No
No
Band Layer Parameters (collected in 4-channel DWDM Active OFMs and 2-channel DWDM Active OFMs)
Band OPR to Express OPT Loss Express OPR to Band OPT Loss Drop Band OPT Measured loss between the facility input and the express output Measured loss between the express input and the band output Average optical power transmitted at the drop band. dB Yes No No No
dB
Yes
No
No
No
dBm
Yes
Yes
Yes
No
Infinera Corporation
Release 2.0
Page B-6
Unit dBm
Band CTP Layer Parameters (collected in the AAM-B1, AAM-B2, AAM-P1 and AAM-P2) Optical Power Received Optical Power Transmitted Total optical power received at the EDFA input. Total optical power transmitted from the EDFA output. It is the sum of the output signal power and the accumulated ASE power. Facility Signal Output Power plus the accumulated ASE power from previous AAM modules. Laser bias current (Pump 1) dBm Yes Yes Yes No
dBm
Yes
Yes
Yes
No
dBm
Yes
No
Yes
No
mA
Yes
No
Yes
No
Infinera Corporation
ATN PM Parameters
Page B-7
OTU PM Parameters
Infinera ATN supports extensive PM data collection at OTUk layer. The OTU PM data is collected on the client side and line side of the SIM-T-1-10G, SIM-T-1-10GP and SIM-T-1-10GM in the ATN. Table B-2 on page B-7 describes the supported OTUk PM data: Table B-2 OTUk PM Parameters and Thresholds Supported
Real-time data support 15-min and 24-hr data support
PM Parameter
Description
Unit
TCA Support
OTU PM Parameters Collected in the Cient side and Line side of SIM-T-1-10G, SIM-T-1-10GP and SIM-T-1-10GM FEC Corrected Zeros FEC Corrected Ones FEC Uncorrectable Codewords FEC Corrected BER FEC Uncorrected BER PRBS Error Corrected number of zeros Corrected number of ones Uncorrected number of codewords Post-FEC Bit Error Rate (Corrected bit error rate) Uncorrected bit error rate prior to FEC correction Count of the number of bits not matching the expected pattern (whether synch has been achieved or not). Incremented only when PRBS monitoring is enabled Rx CV Rx BEI Count FEC Total Codewords Payload Type SIM Type Count of BIP errors detected at the OTU layer. Count of BEI detected at the OTU layer Total number of codewords received Rate of payload Type of SIM Count Count Count Integer Integer Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No No No No No Count Count Count Yes Yes Yes Yes Yes Yes No No No
Float
Yes
Yes
No
Float
Yes
Yes
No
Count
Yes
Yes
No
Infinera Corporation
Release 2.0
Page B-8
OTU PM Parameters
The thresholding is supported only for the pre-FEC BER (the FEC Uncorrected BER parameter). If the BER before error correction is equal to or greater than the user configured value over an interval associated with the configured value, a Pre-FEC BER-based Signal Degrade alarm is reported. The alarm is cleared when the pre-FEC BER is below the threshold.
Infinera Corporation
ATN PM Parameters
Page B-9
DTF PM Parameters
Infinera ATN supports DTF PM data collection on the client side and line side of the DTF SIMs i.e. SIM-T1-10GT and SIM-A-8-2.5GMT in the ATN. TCAs are reported when DTF PM parameters exceed the provisioned threshold values within a collection period. Table B-3 on page B-9 describes the supported DTF path level PM data: Table B-3 DTF PM Parameters and Thresholds Supported
15-min and 24-hr data and TCA Support Data TCA
PM Parameter
Description
Unit
Trib Digital Transport Path Layer (Trib DTPCTP) Rx PM Parameters Collected in the SIM-T-1-10GTand SIM-A-8-2.5GMT
Note: The below PM parameters are only supported in the receive direction of the DTF SIMs
DTP BIP8 DTP ES Count of BIP errors detected at the Digital Transport Path (DTP) layer. Count of the number of seconds during which (at any point during the second) at least one DTF path layer BIP error was detected or an AIS-P defect was present Count of the seconds during which K (= 2,400 as specified in GR-253CORE Issue 3 specification) or more DTF Path layer BIP errors were detected or an AIS-P defect was present Count of the seconds during which the DTF Path considered unavailable. A DTF Path becomes unavailable at the onset of 10 consecutive seconds that qualify as DTP-SES, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as DTP-SES Count of the number of times re-sync has been attempted after initial sync was achieved. Incremented only when PRBS monitoring is enabled. Count Count Yes Yes Yes Yes Yes Yes 1500 120 15000 1200
DTP SES
Count
Yes
Yes
Yes
DTP UAS
Count
Yes
Yes
Yes
10
10
Count
Yes
Yes
No
N/A
N/A
Infinera Corporation
Release 2.0
Page B-10
DTF PM Parameters
Description Count of the number of bits not matching the expected pattern (whether synch has been achieved or not). Incremented only when PRBS monitoring is enabled.
Unit Count
Trib Digital Transport Path Layer (Trib DTPCTP) Tx PM Parameters Collected in the SIM-T-1-10GT DTP Tx BIP 8 DTP Tx ES Count of BIP errors detected at the Digital Transport Path (DTP) layer at the signal de-encapsulation point Count of the number of seconds during which (at any point during the second) at least one DTF path layer BIP error was detected or an AIS-P defect was present at the signal deencapsulation point Count of the seconds during which K (= 2,400 as specified in GR-253CORE Issue 3 specification) or more DTF Path layer BIP errors were detected or an AIS-P defect was present at the signal de-encapsulation point Count of the seconds during which the DTF Path considered unavailable at the signal de-encapsulation point. A DTF Path becomes unavailable at the onset of 10 consecutive seconds that qualify as DTP-SES, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as DTP-SES Count Yes Yes Yes N/A N/A
Count
Yes
Yes
Yes
N/A
N/A
DTP Tx SES
Count
Yes
Yes
Yes
N/A
N/A
DTP Tx UAS
Count
Yes
Yes
Yes
N/A
N/A
Line Digital Transport Path Layer (Line DTPCTP) Rx PM Parameters Collected in the SIM-T-1-10GTand SIM-A-8-2.5GMT DtpBip8 Count of BIP errors detected at the Digital Transport Path (DTP) layer Count Yes Yes Yes 1500 15000
Infinera Corporation
ATN PM Parameters
Page B-11
PM Parameter DtpES
Description Count of the number of seconds during which (at any point during the second) at least one DTF path layer BIP error was detected or an AIS-P defect was present Count of the seconds during which K (= 2,400 as specified in GR-253CORE Issue 3 specification) or more DTF Path layer BIP errors were detected or an AIS-P defect was present Count of the seconds during which the DTF Path considered unavailable. A DTF Path becomes unavailable at the onset of 10 consecutive seconds that qualify as DTP-SES, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as DTP-SES
Unit Count
DtpSES
Count
Yes
Yes
Yes
DtpUAS
Count
Yes
Yes
Yes
10
10
Infinera Corporation
Release 2.0
Page B-12
DCh PM Parameters
DCh PM Parameters
Infinera ATN supports Digital Channel (Dch) PM, FEC and PRBS data collection on the client side and line side of the SIM-T-1-10GT and line-side of SIM-A-8-2.5GMT in the ATN. Table B-4 on page B-12 describes the supported Digital Channel (Dch) PM, FEC and PRBS PM data. : Table B-4 DCh PM Parameters and Thresholds Supported
15-min and 24-hr data and TCA Support Data TCA
PM Parameter
Description
Unit
Trib and Line Digital Transport Section Layer (Trib and Line Digital Channel CTP) PM Parameters collected in the SIM-T-1-10GT and Line Digital Transport Section Layer (Line Digital Channel CTP) PM Parameters collected in the SIM-A-82.5GMT DTS BIP 8 DTS ES Count of BIP errors detected at the Digital Transport Section (DTS) layer Count of the number of seconds during which (at any point during the second) at least one DTF section layer BIP error was detected or an AIS-P defect was present Count of the seconds during which K (= 2,400 as specified in GR-253CORE Issue 3 specification) or more DTF Section layer BIP errors were detected or an AIS-P defect was present Count of the number of times re-sync has been attempted after initial sync was achieved. Incremented only when PRBS monitoring is enabled. DTS PRBS (bit) Error (line-side) Count of the number of bits not matching the expected pattern (whether synch has been achieved or not). Incremented only when PRBS monitoring is enabled. Count Yes Yes No N/A N/A Count Count Yes Yes Yes Yes Yes Yes 1500 120 15000 1200
DtsSES
Count
Yes
Yes
Yes
Count
Yes
Yes
No
N/A
N/A
Infinera Corporation
ATN PM Parameters
Page B-13
PM Parameter FEC Corrected Zeroes FEC Corrected Ones FEC Uncorrectable Codewords Post-FEC BER Pre-FEC BER FEC Total Codewords
Description Corrected number of zeros Corrected number of ones Uncorrected number of codewords
Unit Count
Count
Yes
Yes
No
N/A
N/A
Count
Yes
Yes
No
N/A
N/A
Post-FEC Bit Error Rate (Corrected bit error rate) Uncorrected bit error rate prior to FEC correction Total number of codewords received
No No No
The thresholding is supported only for the pre-FEC BER (the FEC Uncorrected BER parameter). If the BER before error correction is equal to or greater than the user configured value over an interval associated with the configured value, a Pre-FEC BER-based Signal Degrade alarm is reported. The alarm is cleared when the pre-FEC BER is below the threshold.
Infinera Corporation
Release 2.0
Page B-14
Note: Only TOM PM parameters are available for the SIM-T-2-2.5GM. This SIM is transparent and no client signal PM parameters are available.
PM Parameter
Description
Unit
SONET Section Parameters Collected in the SIM-T-1-10G, SIM-T-1-10GP, SIM-T-1-10GM, SIM-T-1-10GT and SIM-A-8.2.5GMT for SONET OC-192/OC-48/OC-12/OC-3 Interfaces Rx CV-S Count of BIP errors detected at the Section layer on the incoming clients SONET signal. Up to eight Section BIP errors can be detected per STS-N frame, with each error incrementing the Sonet-Rx-CV-S current second register Count Yes Yes Yes 1500 15000
Infinera Corporation
ATN PM Parameters
Page B-15
PM Parameter Tx CV-S
Description Count of BIP errors detected at the Section layer on the outgoing clients SONET signal. Up to eight Section BIP errors can be detected per STS-N frame, with each error incrementing the Sonet-Rx-CV-S current second register Count of the number of seconds during which (at any point during the second) at least one Section layer BIP error was detected or an LOF or SEF defect was present Count of the number of seconds during which (at any point during the second) at least one Section layer BIP error was detected or an LOF or SEF defect was present at the signal de-encapsulation point Count of the seconds during which K or more Section layer BIP errors were detected or an SEF or LOF defect was present Count of the seconds during which K or more Section layer BIP errors were detected or an LOF or SEF defect was present at the signal de-encapsulation point. Count of seconds during which an SEF defect is present Count of seconds during which an SEF defect is present at the signal deencapsulation point. Circuit Identifer (CID) associated with the SONET client termination point (CTP) Payload Rate Type of SIM
Unit Count
Rx ES-S
Count
Yes
Yes
Yes
120
1200
Tx ES-S
Count
Yes
Yes
Yes
120
1200
Rx SES-S
Count
Yes
Yes
Yes
Tx SES-S
Count
Yes
Yes
Yes
Rx SEFS-S Tx SEFS-S
Count Count
Yes Yes
Yes Yes
Yes Yes
3 3
7 7
System CID
String
Yes
Yes
No
N/A
N/A
Integer Integer
Yes Yes
Yes Yes
No No
N/A N/A
N/A N/A
Infinera Corporation
Release 2.0
Page B-16
PM Parameter
Description
Unit
PRBS Parameters Collected for SONET OC-48/OC-12/OC-3 Interfaces (in SIM-A-8.2.5GMT only) PRBS (bit) Error (lineside) Count of the number of bits not matching the expected pattern (whether synch has been achieved or not). Incremented only when PRBS monitoring is enabled. PRBS Sync Error (lineside) Count of the number of times re-sync has been attempted after initial sync was achieved. Incremented only when PRBS monitoring is enabled. PRBS (bit) Error (tribside) Count of the number of bits not matching the expected pattern (whether synch has been achieved or not). Incremented only when PRBS monitoring is enabled. PRBS Sync Error (tribside) Count of the number of times re-sync has been attempted after initial sync was achieved. Incremented only when PRBS monitoring is enabled. Count Yes Yes No N/A N/A Count Yes Yes No N/A N/A Count Yes Yes No N/A N/A Count Yes Yes No N/A N/A
Infinera Corporation
ATN PM Parameters
Page B-17
Description
Unit
SDH Regenerator Section Parameters Collected in the SIM-T-1-10G, SIM-T-1-10GP, SIM-T-1-10GM, SIM-T-1-10GT and SIM-A-8.2.5GMT for SDH STM-64/STM-16/STM-4/STM-1 Interfaces Rx BE-RS Count of the number of errors within a block in the incoming clients SDH signal. Count of the number of errors within a block in the SDH signal received from the network and to be transmitted to the receiving client. Count of the number of seconds during which (at any point during the second) at least one RS block error was detected or an LOS or LOF defect is present. Count of the number of seconds during which (at any point during the second) at least one Tx RS block error was detected or a de-encap (Tx) LOS or LOF defect was present. Count of the seconds during which 30% or more RS block errors (BE) were detected or an LOF or LOS defect was present. Count of the seconds during which 30% or more Tx RS block errors (BE) were detected or a de-encap (Tx) LOF or LOS defect was present. Regenerator Section - Out of Frame Seconds. Count of seconds during which an OOF defect is present (at any point in the second). Regenerator Section - Out of Frame Seconds. Count of seconds during which a de-encap (Tx) OOF defect was present. Count Yes Yes Yes 1500 15000
Tx BE-RS
Count
Yes
Yes
Yes
1500
15000
Rx ES-RS
Count
Yes
Yes
Yes
120
1200
Tx ES-RS
Count
Yes
Yes
Yes
120
1200
Rx SES-RS
Count
Yes
Yes
Yes
Tx SES-RS
Count
Yes
Yes
Yes
Rx OFS-RS
Count
Yes
Yes
Yes
Tx OFS-RS
Count
Yes
Yes
Yes
Infinera Corporation
Release 2.0
Page B-18
Description Regenerator Section - Loss of Signal Seconds. Count of seconds during which any LOS defect existed. Circuit Identifer (CID) associated with the SDH client termination point (CTP) Payload Rate Type of SIM
Unit Count
15-min and 24-hr Data and TCA Support Data Yes TCA Yes
No No No
PRBS Parameters Collected for SDH STM-16/STM-4/STM-1 Interfaces (in SIM-A-8.2.5GMT only) PRBS Sync Error (lineside) Count of the number of times re-sync has been attempted after initial sync was achieved. Incremented only when PRBS monitoring is enabled. PRBS (bit) Error (lineside) Count of the number of bits not matching the expected pattern (whether synch has been achieved or not). Incremented only when PRBS monitoring is enabled. PRBS Sync Error (tribside) Count of the number of times re-sync has been attempted after initial sync was achieved. Incremented only when PRBS monitoring is enabled. PRBS (bit) Error (tribside) Count of the number of bits not matching the expected pattern (whether synch has been achieved or not). Incremented only when PRBS monitoring is enabled. Count Yes Yes No N/A N/A Count Yes Yes No N/A N/A Count Yes Yes No N/A N/A Count Yes Yes No N/A N/A
Infinera Corporation
ATN PM Parameters
Page B-19
SIM-A-8-2.5GMT
PM Parameter
Description
Unit
Ethernet Parameters Collected in the SIM-T-1-10G, SIM-T-1-10GP, SIM-T-1-10GM, SIM-T-1-10GT and SIM-A-8.2.5GMT for 1GbE/10GbE Interfaces
Note: Real Time and 15-min/24-hr TCAs are not supported on the SIM-T-1-10G. The 15-min and 24-hr TCA
Support listed below is applicable for the other SIMs listed above. Rx Broadcast Packets A count of frames that are successfully received and are directed to the broadcast group address. Count Yes Yes Yes No Yes Yes
15-Min Default:
0
24-hr Default:
0 Count Yes Yes Yes No Yes Yes
Tx Broadcast Packets
A count of the frames that were successfully transmitted, as indicated by the transmit status transmit OK, to the broadcast address. Frames transmitted to multicast addresses are not broadcast frames and are excluded. A count of multi-cast frames that are successfully received and are directed to an active nonbroadcast group address.
15-Min Default:
0
24-hr Default:
0
Rx Multicast Packets
Count Yes
Yes
Yes
No
Yes
Yes
15-Min Default:
0
24-hr Default:
0
Infinera Corporation
Release 2.0
SIM-T-1-10GT
SIM-T-1-10G
Page B-20
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
Description
Unit
A count of multi-cast Count Yes frames that are successfully transmitted, as indicated by the status value transmit OK, to a group destination address other than broadcast. A count of uni-cast frames that are successfully received and are directed to an active nonbroadcast group address. Count Yes
No
Yes
Yes
15-Min Default:
0
24-hr Default:
0 Yes No No Yes No
Rx Unicast Packets
15-Min Default:
0
24-hr Default:
0 Yes No No Yes No
Tx Unicast Packets
A count of uni-cast Count Yes frames that are successfully transmitted, as indicated by the status value transmit OK, to an active nonbroadcast group address. Number of received data octets. Count Yes
15-Min Default:
0
24-hr Default:
0 Yes Yes Yes Yes Yes
Rx Octets
15-Min Default:
N/A
24-hr Default:
N/A
Infinera Corporation
SIM-T-1-10GT
SIM-T-1-10G
ATN PM Parameters
Page B-21
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
PM Parameter Tx Octets
Unit
Count Yes
Yes
Yes
Yes
15-Min Default:
N/A
24-hr Default:
N/A Rx Errors Number of received erroneous frames Count Yes Yes No No Yes No
15-Min Default:
N/A
24-hr Default:
N/A Tx Errors Number of transmitted erroneous frames Count Yes Yes No No Yes No
15-Min Default:
N/A
24-hr Default:
N/A Rx Discards Number of received frames discarded due to various errors Count Yes Yes No No Yes No
15-Min Default:
N/A
24-hr Default:
N/A
Infinera Corporation
Release 2.0
SIM-T-1-10GT
SIM-T-1-10G
Page B-22
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
PM Parameter Tx Discards
Unit
Count Yes
No
Yes
No
15-Min Default:
N/A
24-hr Default:
N/A Rx PCS ICG Physical Coding Sublayer (PCS) Invalid Code Group -Receive Count Yes Yes Yes Yes No Yes
15-Min Default:
1500
24-hr Default:
15000 Tx PCS ICG Physical Coding Sublayer (PCS) Invalid Code Group -Transmit Count Yes Yes Yes Yes No Yes
15-Min Default:
1500
24-hr Default:
15000 Rx PCS ES PCS Errored Seconds The number of seconds in which at least one ICG was detected, or the TP was in ingress LOSS OF SYNC (defect) state (including when an ingress optical LOS defect was present). Count Yes Yes Yes Yes No Yes
15-Min Default:
120
24-hr Default:
1200
Infinera Corporation
SIM-T-1-10GT
SIM-T-1-10G
ATN PM Parameters
Page B-23
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
PM Parameter Tx PCS ES
Description PCS Errored Seconds The number of seconds in which at least one de-encapsulation ICG was detected, or the TP was in deencap LOSS OF SYNC (defect) state (including when an de-encap LOS defect was present).
Unit
Count Yes
Yes
No
Yes
15-Min Default:
120
24-hr Default:
1200
Rx PCS SES
PCS Severely Errored Seconds Number of seconds in which at least 1250 ICGs (for 1GbE) or 12500 ICGs (for 10GbE) were detected, or the TP was in ingress LOSS OF SYNC (defect) state (including when an ingress optical LOS defect was present).
Count Yes
Yes
Yes
Yes
No
Yes
15-Min Default:
3
24-hr Default:
7
Tx PCS SES
PCS Severely Errored Seconds Number of seconds in which the TP was in the de-encap LOSS OF SYNC (defect) state (including when a de-encap LOS defect was present).
Count Yes
Yes
Yes
Yes
No
Yes
15-Min Default:
3
24-hr Default:
7
Infinera Corporation
Release 2.0
SIM-T-1-10GT
SIM-T-1-10G
Page B-24
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
PM Parameter Rx Packets
Unit
Count Yes
Yes
No
Yes
15-Min Default:
N/A
24-hr Default:
N/A Tx Packets Number of transmitted MAC Layer data packets. Count Yes Yes Yes Yes No Yes
15-Min Default:
N/A
24-hr Default:
N/A Rx Err Octets Errored octet Number of data octets that are part of an Errored Packet on the receive client interface. Count Yes Yes Yes Yes No No
15-Min Default:
256
24-hr Default:
512 Count Yes Yes Yes Yes No No
Tx Err Octets
Errored octet Number of data octets that are part of an Errored Packet at the signal de-encapsulation point before the client-side transmit interface.
15-Min Default:
256
24-hr Default:
512
Infinera Corporation
SIM-T-1-10GT
SIM-T-1-10G
ATN PM Parameters
Page B-25
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
PM Parameter Rx Jabber
Description Jabber count Number of packets received that are longer than the maximum frame length octets (excluding framing bits, but including FCS octets) and has either a bad FCS with an integral number of octets (FCS error) or a bad FCS with a non-integral number of octets (alignment error). Jabber count Number of packets transmitted that are longer than the maximum frame length octets (excluding framing bits, but including FCS octets) and has either a bad FCS with an integral number of octets (FCS error) or a bad FCS with a nonintegral number of octets (alignment error).
Unit
Count Yes
Yes
No
Yes
15-Min Default:
1
24-hr Default:
2
Tx Jabber
Count Yes
Yes
Yes
Yes
No
Yes
15-Min Default:
1
24-hr Default:
2
Infinera Corporation
Release 2.0
SIM-T-1-10GT
SIM-T-1-10G
Page B-26
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
PM Parameter Rx Fragment
Description
Unit
Fragment packet count Count Yes Number of packets received that are less than 64 octets long (excluding framing bits, but including FCS octets) and have either a bad FCS with an integral number of octets (FCS error) or a bad FCS with a non-integral number of octets (alignment error) Fragment packet count Count Yes Number of packets transmitted that are less than 64 octets long (excluding framing bits, but including FCS octets) and have either a bad FCS with an integral number of octets (FCS error) or a bad FCS with a non-integral number of octets (alignment error)
Yes
No
Yes
15-Min Default:
1
24-hr Default:
2
Tx Fragment
Yes
Yes
Yes
No
Yes
15-Min Default:
1
24-hr Default:
2
Infinera Corporation
SIM-T-1-10GT
SIM-T-1-10G
ATN PM Parameters
Page B-27
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
Description Cyclical redundancy check align error count Number of packets received that have a length (excluding framing bits, but including FCS octets) of between 64 and MaxFrameLength octets, inclusive, but have either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error)
Unit
Count Yes
Yes
No
Yes
15-Min Default:
1
24-hr Default:
2
Tx CRC Aligned
Cyclical redundancy check align error count Number of packets transmitted that have a length (excluding framing bits, but including FCS octets) of between 64 and MaxFrameLength octets, inclusive, but have either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error)
Count Yes
Yes
Yes
Yes
No
Yes
15-Min Default:
1
24-hr Default:
2
Infinera Corporation
Release 2.0
SIM-T-1-10GT
SIM-T-1-10G
Page B-28
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
PM Parameter Rx Undersized
Description Undersize packet count Number of received packets that are less than 64 octets long (excluding framing bits, but including FCS octets) and are otherwise well formed.
Unit
Count Yes
Yes
No
Yes
15-Min Default:
1
24-hr Default:
2 Count Yes Yes Yes Yes No Yes
Tx Undersized
Undersize packet count Number of transmitted packets that are less than 64 octets long (excluding framing bits, but including FCS octets) and are otherwise well formed.
15-Min Default:
1
24-hr Default:
2 Count Yes Yes Yes Yes No Yes
Rx Oversize
Oversize packet count Number of received packets that are longer than the maximum frame length (excluding framing bits, but including FCS octets) and are otherwise well formed, on the receive client interface.
15-Min Default:
1
24-hr Default:
2
Tx Oversize
Oversize packet count Number of transmitted packets that are longer than the maximum frame length (excluding framing bits, but including FCS octets) and are otherwise well formed, on the receive client interface.
Count Yes
Yes
Yes
Yes
No
Yes
15-Min Default:
1
24-hr Default:
2
Infinera Corporation
SIM-T-1-10GT
SIM-T-1-10G
ATN PM Parameters
Page B-29
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
PM Parameter Rx JS
Description Jabber Seconds Number of seconds in which a jabber state was detected sometime in that second.
Unit
Count Yes
Yes
No
Yes
15-Min Default:
1
24-hr Default:
2 Count Yes Yes Yes Yes No Yes
Tx JS
Jabber Seconds Number of seconds in which a jabber state was detected sometime in that second on the de-encapsulated signal.
15-Min Default:
1
24-hr Default:
2 Count Yes Yes Yes Yes No Yes
Rx MAC SES
15-Min Default:
3
24-hr Default:
7 Tx MAC SES MAC Severely Errored Seconds - Transmit Count Yes Yes Yes Yes No Yes
15-Min Default:
3
24-hr Default:
7
Infinera Corporation
Release 2.0
SIM-T-1-10GT
SIM-T-1-10G
Page B-30
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
Description A count of MAC Control frames received on this interface with an opcode indicating the PAUSE operation.
Unit
Count Yes
Yes
No
Yes
15-Min Default:
0
24-hr Default:
0 Count Yes Yes Yes No No Yes
Tx OutPause Frame
A count of MAC Control frames transmitted on this interface with an opcode indicating the PAUSE operation.
15-Min Default:
0
24-hr Default:
0 Float Yes No No Yes No Yes
Rx LU
15-Min Default:
N/A
24-hr Default:
N/A TxLU Link Utilization - Transmit Float Yes No No Yes No Yes
15-Min Default:
N/A
24-hr Default:
N/A
Infinera Corporation
SIM-T-1-10GT
SIM-T-1-10G
ATN PM Parameters
Page B-31
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
Unit
Count Yes
Yes
No
Yes
15-Min Default:
0
24-hr Default:
0 Rx Packets Size 64 Transmitted packets of 64 octets Count Yes Yes Yes Yes No Yes
15-Min Default:
0
24-hr Default:
0 Rx Packets Received packets Size 65 to 127 (including bad packets) from 65 to 127 octets. Count Yes Yes Yes Yes No Yes
15-Min Default:
0
24-hr Default:
0 Tx Packets Transmitted packets Size 65 to 127 from 65 to 127 octets. Count Yes Yes Yes Yes No Yes
15-Min Default:
0
24-hr Default:
0
Infinera Corporation
Release 2.0
SIM-T-1-10GT
SIM-T-1-10G
Page B-32
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
Description Received packets (including bad packets) from 128 to 255 octets.
Unit
Count Yes
Yes
No
Yes
15-Min Default:
0
24-hr Default:
0 Tx Packets Size 128 to 255 Transmitted packets Count Yes from 128 to 255 octets. Yes Yes Yes No Yes
15-Min Default:
0
24-hr Default:
0 Rx Packets Size 256 to 511 Received packets (including bad packets) from 256 to 511 octets. Count Yes Yes Yes Yes No Yes
15-Min Default:
0
24-hr Default:
0 Tx Packets Size 256 to 511 Transmitted packets from 256 to 511 octets. Count Yes Yes Yes Yes No Yes
15-Min Default:
0
24-hr Default:
0
Infinera Corporation
SIM-T-1-10GT
SIM-T-1-10G
ATN PM Parameters
Page B-33
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
Description Received packets (including bad packets) from 512 to 1023 octets.
Unit
Count Yes
Yes
No
Yes
15-Min Default:
0
24-hr Default:
0 Tx Packets Size 512 to 1023 Transmitted packets from 512 to 1023 octets. Count Yes Yes Yes Yes No Yes
15-Min Default:
0
24-hr Default:
0 Rx Packets Size 1024 to 1518 Received packets (including bad packets) from 1024 to 1518 octets. Count Yes Yes Yes Yes No Yes
15-Min Default:
0
24-hr Default:
0 Tx Packets Size 1024 to 1518 Transmitted packets from 1024 to 1518 octets. Count Yes Yes Yes Yes No Yes
15-Min Default:
0
24-hr Default:
0
Infinera Corporation
Release 2.0
SIM-T-1-10GT
SIM-T-1-10G
Page B-34
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
Unit
Count Yes
Yes
No
Yes
15-Min Default:
0
24-hr Default:
0 Tx Packets Size 1519 to Jumbo Transmitted packets of 1519 or more octets. Count Yes Yes Yes Yes No Yes
15-Min Default:
0
24-hr Default:
0 Line Test Sig- Count of the number of nal Sync Error times re-sync has been attempted after initial sync was achieved. Incremented only when line test is enabled. Line Test Signal Error Count of the number of bits not matching the expected pattern (whether synch has been achieved or not). Incremented only when line test is enabled. System CID Circuit Identifer (CID) String associated with the Ethernet client termination point (CTP) Yes Yes No Yes Yes Yes Count Yes Yes No Yes No No Count Yes Yes No Yes No No
15-Min Default:
N/A
24-hr Default:
N/A
Infinera Corporation
SIM-T-1-10GT
SIM-T-1-10G
ATN PM Parameters
Page B-35
1GbE 15-min and 24-hr Data Support with Default Threshold Values Yes
10GbE
SIM-A-8-2.5GMT
Unit Integer
Yes
Yes
Yes
15-Min Default:
N/A
24-hr Default:
N/A SIM Type Type of SIM Integer Yes Yes No Yes Yes Yes
15-Min Default:
N/A
24-hr Default:
N/A
PM Parameter
Description
Unit
Fibre Channel Parameters Collected in the SIM-A-8.2.5GMT, SIM-T-1-10GP and SIM-T-1-10GM for FC 1G/FC 2G/FC 8G/FC 10G Interfaces Rx PCS ICG Rx PCS SESS Physical Coding Sublayer Invalid Code Group - Receive. Physical Coding Sublayer Severely Errored Sync Seconds - Receive. Count Count Yes Yes Yes Yes Yes Yes 1500 3 15000
Infinera Corporation
Release 2.0
SIM-T-1-10GT
SIM-T-1-10G
Page B-36
Description Physical Coding Sublayer Severely Errored Sync Seconds - Transmit. Physical Coding Sublayer Severely Errored Seconds- Receive.
15-min and 24-hr data and TCA support Data Yes Yes Yes Yes Yes TCA Yes Yes Yes Yes Yes
Tx PCS SES Physical Coding Sublayer Severely Errored Seconds- Transmit. Rx PCS ES Tx PCS ES Physical Coding Sublayer Errored Seconds - Receive Physical Coding Sublayer Errored Seconds - Transmit Circuit Identifer (CID) associated with the SDH client termination point (CTP) Payload Rate Type of SIM
No No No
FC PM Parameters Collected for 1G FC/2G FC Interfaces (in SIM-A-8.2.5GMT only) Tx PCS ICG Rx FC Frames Physical Coding Sublayer Invalid Code Group - Receive. Number of received Fibre Channel Frames. FC frames of any size are counted, including valid and errored frames. Tx FC Frames Number of transmitted Fibre Channel Frames. FC frames of any size are counted, including valid and errored frames. Rx FC Errored Frames Tx FC Errored Frames Number of received Fibre Channel Errored Frames Number of transmitted Fibre Channel Errored Frames Count Yes Yes Yes 256 512 Count Yes Yes Yes 120 1200 Count Count Yes Yes Yes Yes Yes Yes 1500 120 15000 1200
Count
Yes
Yes
Yes
256
512
Infinera Corporation
ATN PM Parameters
Page B-37
PM Parameter Rx FC Octets
Description Number of received Fibre Channel Octets Number of octets includes octets inside errored frames.
Unit Count
15-min and 24-hr data and TCA support Data Yes TCA Yes
Tx FC Octets
Number of transmitted Fibre Channel Octets Number of octets includes octets inside errored frames.
Count
Yes
Yes
Yes
120
1200
Number of received Fibre Channel Errored Octets. Includes FC octets that are part of an errored frame Number of transmitted Fibre Channel Errored Octets. Includes FC octets that are part of an errored frame Fibre Channel Severely Errored Seconds- Receive. Fibre Channel Severely Errored Seconds- Transmit.
Count
Yes
Yes
Yes
256
512
Count
Yes
Yes
Yes
256
512
Count Count
Yes Yes
Yes Yes
Yes Yes
3 3
7 7
Infinera Corporation
Release 2.0
Page B-38
OSC PM Parameters
OSC PM Parameters
Infinera ATN support OSC, a dedicated 1510nm optical channel, to carry traffic and management traffic between adjacent network elements. The OSC is terminated on the AMM on the ATN. The PM parameters supported for the OSC are described in Table B-9 on page B-38. Table B-9 OSC PM Parameters Supported on the AMM
Real-time Data Support 15-min and 24-hr Data Support 15-min and 24-hr TCA Support
PM Parameter Displayed
Description
Unit
OSC Optical PM Parameters Laser Bias Current Optical Power Transmitted Optical Power Received Transmitted Bytes Transmitted Packets Packets Dropped at Transmitter Received Bytes Received Packets Packets Dropped at Receiver Measured laser bias current of the OSC optical transmitter. Average optical output power transmitted by the OSC optical transmitter. Average optical power received by the OSC optical receiver from the Line input. The number of bytes transmitted by this network element on the OSC channel. The number of packets transmitted by this network element on the OSC channel. The number of transmit packets dropped by this network element. The number of bytes received by this network element on the OSC channel. The number of packets received by this network element on the OSC channel. The number of received packets dropped by this network element. mA dBm Yes Yes Yes Yes No No
dBm
Yes
Yes
No
Bytes
Yes
No
No
Packets
Yes
No
No
Packets
Yes
No
No
Bytes
Yes
No
No
Packets
Yes
No
No
Packets
Yes
No
No
Infinera Corporation
ATN PM Parameters
Page B-39
Additional PM Parameters
The additional PM parameter such as PM on the FanTray is listed in Table B-10 on page B-39. Table B-10 Additional PM Parameters Supported on the ATN
PM Parameter Displayed in ATN GNM and CLI
Description
Inlet Temperature
Centigrade
Yes
Yes
No
Infinera Corporation
Release 2.0
Page B-40
Additional PM Parameters
Infinera Corporation
Appendix C
The OFM modules provide support for all the optical channels.
Infinera Corporation
Release 2.0
Page C-2
The DWDM optical channel plan (see Table C-1 on page C-3) supported by ATN consists of 40 DWDM channels grouped into the following:
Four 10-channel bands Ten 4-channel sub-bands Twenty 2-channel sub-bands
Infinera Corporation
Page C-3
Infinera Corporation
Release 2.0
Page C-4
2-channel Sub-Band Number Sub-Band 11 (Channels 3736) Sub-Band 12 (Channels 35 and 34)
Channel Number 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18
Center Wavelength (nm) 1547.72 1548.51 1549.32 1550.12 1550.92 1551.72 1552.52 1553.33 1554.13 1554.94 1555.75 1556.55 1557.36 1558.17 1558.98 1559.79 1560.61 1561.42 1562.23 1563.05
Center Frequency (THz) 193.7 193.6 193.5 193.4 193.3 193.2 193.1 193.0 192.9 192.8 192.7 192.6 192.5 192.4 192.3 192.2 192.1 192.0 191.9 191.8
Sub-Band 15 (Channels 29 and 28) Sub-Band 16 (Channels 27 and 26) Sub-Band 17 (Channels 25 and 24) Sub-Band 18 (Channels 23 and 22)
Infinera Corporation
Page C-5
Note: Only Channel 3, 4, 5 and 6 are available for 10GbE, OC-192 and STM-64 signal support in future releases.
Infinera Corporation
Release 2.0
Page C-6
Infinera Corporation
Appendix D
Acronyms
List of Acronyms
Acronym Definition
A
AAM ACLI ACO ACT AD ADLM ADM ADPCM AGC AID AINS AIS ALS AMM AMP ANSI APD ATN Amplifier Module application command line interface alarm cutoff active add/drop Amplified Digital Line Module add/drop multiplexer adaptive differential pulse code modulation Automated Gain Control access identifier automatic in-service alarm indication signal Automatic Laser Shutdown ATN Management Module amplifier American National Standards Institute avalanche photo diode
Infinera Corporation
Release 2.0
Page D-2
Acronym API APS ARC ARP ASAP ASCII ASE ASIC ASPS ATC-A ATC-P ATM AU AUX AVC AWG AXLM application programming interface automatic protection switching Alarm Reporting Control address resolution protocol
Definition
Alarm Severity Assignment Profile Settings (for ATN) American Standard Code for Information Interchange amplified spontaneous emission application-specific integrated circuit Alarm Severity Profile Settings ATN Transport Chassis - Active ATN Transport Chassis - Passive asynchronous transfer mode administrative unit auxiliary port attribute value change array waveguide gating; american wire gauge Amplified Switching Line Module
B
BDFB BDI BEI BER BERT BIP-8 BITS BLSR BMM BNC BOL BOM BOOTP BPF BPOST bps BPV battery distribution fuse bay backward defect indication backward error indication bit error rate; bit error ratio bit error rate testing bit interleaved parity building-integrated timing supply bi-directional line switched ring Band Multiplexing Module bayonet Neill-Concelman; British Naval Connector beginning of life bill of material bootstrap protocol Band Pass Filter Boot Power On Self Test bits per second bipolar violations
Infinera Corporation
Acronyms
Page D-3
Acronym
Definition
C
C CBN CCITT CCLI CDE CDR CDRH CET CFR CH/Ch/ch CID CIT CLEI CLI CLM CO CODEC COM CORBA CPC CPE CPLD CPU CRC CRM CSM CSPF CSV CTAG CTP CTS CV CV-L Celsius Common Bonding Network Consultative Committee on International Telegraph and Telephone (now known as the ITU-T) commissioning command line interface chromatic dispersion equalizer clock and data recovery Center for Devices and Radiological Health Channel Engineering Tool code for federal regulations channel circuit identifier craft interface terminal common language equipment identifier command line interface C-band and L-band Coupler central office coder and decoder communication Common Object Request Broker Architecture common processor complex customer premises equipment complex programmable logic device central processing unit cyclic redundancy check customer relationship management Customer Service Module constraint-based shortest path first algorithm comma separated value correlation tag connection termination point, channel trail termination point, client termination point clear to send coding violation coding violation-line
Infinera Corporation
Release 2.0
Page D-4
Definition
D
DA DB dB DCC DCE DCF DCM DCN DDR DEMUX DFB DFE DGE DHCP DLM DLV DMC DNA DR DSE DSF DSNCP DSP DT DTC DTC-B DTE DTF DTL DTP DTS digital amplifier database decibel data communications channel data communications equipment dispersion compensation fiber Dispersion Compensation Module data communication network double data rate de-multiplexing distributed feedback decision feedback equalizer dynamic gain equalization dynamic host configuration protocol Digital Line Module Digital Link View Dispersion Management Chassis Digital Network Administrator digital repeater Dynamic Spectrum Equalizer dispersion shifted fiber Digital Subnetwork Connection Protection digital signal processor digital terminal Digital Transport Chassis Digital Transport Chassis-B data terminal equipment Digital Transport Frame digital transport line; designated transit list digital transport path digital transport section
Infinera Corporation
Acronyms
Page D-5
Definition
E
ECC EDFA EEPROM EFEC EMC EMI EML EMS EOL EOS ESCON ES-L ES-P ES-S ESCON ESD ETS ETSI error-correcting code; error correction code erbium doped fiber amplifier electrically-erasable programmable read-only memory enhanced forward error correction electromagnetic compatibility electromagnetic interference element management layer element management system end of life end of shipping Enterprise Systems Connection line-errored seconds path-errored seconds section-errored seconds Enterprise Systems Connection electrostatic discharge; electrostatic-sensitive device IEEE European Test Symposium European Telecommunications Standards Institute
F
F FA FAS FBG FC FCAPS FCC FDA FDI FDR Fahrenheit frame alignment frame alignment signal fiber Bragg grating Fibre Channel; fiber channel; failure count fault management, configuration management, accounting, performance monitoring, and security administration Federal Communications Commission (USA) Food and Drug Administration forward defect indication flight data recorder
Infinera Corporation
Release 2.0
Page D-6
Acronym FEC FICON FIFO FIS FIT FLT FPGA FRU FTP forward error correction Fibre Connectivity first-in-first-out Fault Integration Server failure in time fault field programmable gate array field replaceable unit
Definition
G
GAM GbE Gbps GCC GFEC GFP GHz GMPLS GNE GNM GRE GTP GUI Gain Adapter Module gigabit Ethernet gigabits per second general communication channel general forward error correction generic framing protocol gigahertz generalized multi protocol label switching gateway network element Graphical Node Manager generic routing encapsulation group termination point graphical user interface
H/I
HD HDLC HTML HTTP I/O I2C IAP ICG ID IDF high definition high-level data link control hypertext markup language hypertext transfer protocol input/output inter-integrated circuit input, output, and alarm panel invalid code group identification invalid data flag
Infinera Corporation
Acronyms
Page D-7
Acronym IEC IMS IOP IP IQ IQ NOS IQA NOS ATN IR IS ITU-T International Electrical Commission Infinera Management Suite input/output panel Internet protocol see IQ NOS
Definition
Infinera IQ Network Operating System Infinera IQA Network Operating System ATN intermediate reach in-service International Telecommunications Union - Telecommunications
J/K/L
JDK JRE JS LAN LBC LC LCK LED LOC LOF LOL LOP LOS LP LR LSB LTE Java Development Kit Java Runtime Environment jabber seconds local area network laser bias current fiber optic cable connector type locked light-emitting diode loss of communication loss of frame loss of light loss of pointer loss of signal; loss of synch launch power long reach least significant bit line-terminating equipment
M
MA MAC MAP MB Mbps monitoring access media access control management application proxy megabyte megabits per second
Infinera Corporation
Release 2.0
Page D-8
Acronym MCM MEMS EDFA MFAS MIB MMF MS MSA MSB MSO MSOH MTBF MTU MUX Management Control Module micro electro mechanical systems micro-erbium doped fiber amplifier multi frame alignment signal management information base multimode fiber multiplex section multi source agreement most significant bit multi-service operator multiplex section overhead mean time between failure maximum transmission unit multiplex; multiplexer; multiplexing
Definition
N
NA NAND NC NCT NDSF NE NEBS NEC NECG NEL NEPA NFPA nm NML NMS NNI NO NOC NPS NSA network administrator flash type normally closed; node controller; nodal control nodal control and timing non zero dispersion shifted fiber network engineer network equipment building standards National Electrical Code net electrical coding gain network element layer National Environmental Policy Act National Fire Protection Association nanometer network management layer network management system network-to-network interface normally open network operations center Network Planning System non-service affecting
Infinera Corporation
Acronyms
Page D-9
Acronym NTP NVRAM network time protocol nonvolatile random access memory
Definition
O
OA OAM OAM&P OC-12 OC-192 OC-3 OC-48 OC-768 OCG Och OCI ODF ODU OE OEO OER OFC OFM OH OIF OLOS OMM OMS OOS OOS-MT OPN OPR OPSW OPT OPU ORL ORM Optical Amplifier Optical Amplification Module operation, administration, maintenance and provisioning optical carrier signal at 622.08Mbps optical carrier signal at 9.95328Gbps optical carrier signal at 155.52Mbps optical carrier signal at 2.48832Gbps optical carrier signal at 39.81312Gbps optical carrier group optical channel open connection indication optical distribution frame optical data unit Optical Engine optical-electrical-optical optical engineering route open fiber control Optical Filter Module overhead Optical Internetworking Forum optical loss of signal Optical Management Module optical multiplex section out-of-service out-of-service maintenance Optical Private Network optical power received Optical Power Switch optical power transmitted optical payload unit optical return loss Optical Raman Module
Infinera Corporation
Release 2.0
Page D-10
Acronym OS OSA OSC OSNR OSPF OSS OTC OTDR OTN OTS OTU OW OWM operating system optical spectrum analyzer Optical Supervisory Channel optical signal-to-noise ratio open shortest path first operations support system Optical Transport Chassis optical time domain reflectometer Optical Transport Network optical transport section optical transport unit orderwire Orderwire Module
Definition
P/Q
PC PCM PCPM PCS PD PDU PEM PG PHY PIC PID PIN PJO PL PLC PLD PLL PLO PM PMD POH personal computer Power Conversion Module per channel power monitoring physical coding sublayer photo diode protocol data unit; power distribution unit Power Entry Module protection group physical Photonic Integrated Circuit protocol identifier positive-intrinsic negative positive justification opportunity point loss Planar Lightwave Circuit programmable logic device phase locked loop point loss offset performance monitoring polarization mode dispersion path overhead
Infinera Corporation
Acronyms
Page D-11
Acronym PON POP POST PPM PPP PR PRBS PROV ps PSC PSD PSE PSTN PTP PU PWR QOS product ordering name point-of-presence Power On Self Test part per million point-to-point protocol provisioning pseudo random binary sequence provisioning
Definition
pico second (unit of measure for dispersion) protection switch completion; protection switch count protection switch duration Passive Spectrum Equalizer public switched telephone network physical termination point; point-to-point protection unit power quality of service
R
RADIUS RAM RBM RDI REI-L REI-P REM RFI RMA ROADM ROM RS RSOH RSTP RTC RTN RTS Remote Authentication Dial-In User Service Raman Amplifier Module; random access memory Red/Blue Band Mux/Demux remote defect indication remote error indication-line remote error indication-path Raman Extender Module remote failure indication return material authorization reconfigurable optical add/drop multiplexer read-only memory regenerator section; Reed-Solomon regenerator section overhead rapid spanning tree protocol real time clock return lead ready to send
Infinera Corporation
Release 2.0
Page D-12
Definition
S
SA SAPI SC SCM SD SDH SDI SDRAM SEF SEFS SELV SERDES SES SF SFP SFTP SID SIM SLM SLTE SMF SML SMPTE SNC SNCP SNE SNMP SNR SOH SOL SONET service affecting; security administrator source access point identifier square shaped fiber optic cable connector Submarine Control Module signal degrade; standard definition synchronous digital hierarchy serial digital interface synchronized dynamic random access memory severely errored frame severely errored frame second safety extra low voltage serializer and deserializer severely errored seconds signal fail small form factor pluggable secure file transfer protocol source identifier; system identifier Service Interface Module Submarine Line Module submarine line terminal equipment single-mode fiber service management layer Society of Motion Picture and Television Engineers subnetwork connection subnetwork connection protection subtending network element simple network management protocol signal-to-noise ratio section overhead start of life synchronous optical network
Infinera Corporation
Acronyms
Page D-13
Acronym SPE SQ SR SSHv2 SSL STE STM STM-1 STM-16 STM-256 STM-4 STM-64 STM-n STP STS STS-n SW synchronous payload envelope signal quality short reach Secure Shell version 2 secure sockets layer section terminating equipment synchronous transfer mode SDH signal at 155.52Mbps SDH signal at 2.48832Gbps SDH signal at 39.81312Gbps SDH signal at 622.08Mbps SDH signal at 9.95328Gbps
Definition
synchronous transfer module of level n (for example, STM-64, STM-16) spanning tree protocol synchronous transport signal synchronous transport signal of level n (for example, STS-12, STS-48) software
T/U/V
TAC TAM TAP TCA TCC TCM TCP TE TEC TEM TERM TFTP TID TIM TL1 TLA TLS technical assistance center Tributary Adapter Module Timing and Alarm Panel threshold crossing alert threshold crossing condition tandem connection monitoring transmission control protocol traffic engineering thermo-electric cooler TAM Extender Module terminal trivial file transfer protocol target identifier trace identifier mismatch transaction language 1 terminal line amplifier tunable laser source
Infinera Corporation
Release 2.0
Page D-14
Acronym TMF TMN TOM TP TR TT TTI TWC Tx UA UART UAS UAS-L UAS-P UDP ULH UNI UPC UPSR URL USB UTC V VCG VGA VLAN VOA VPN VSR TeleManagement Forum
Definition
telecommunications management network Tributary Optical Module termination point transceiver test and turn-up trail trace identifier true-wave-classic transmitter; transmit unavailable seconds universal asynchronous receiver transmitter unavailable seconds unavailable seconds, near-end line unavailable seconds, near-end STS path user datagram protocol ultra long haul user-network interface ultra physical contact unidirectional path switched ring universal resource locator Universal Serial Bus Coordinated Universal Time volt virtual concatenation group variable gain amplifier virtual local area network variable optical attenuator virtual private network very short reach
W/X/Y/Z
WAN WDM WPCS WPLM WTR wide area network wavelength division multiplexing Wet Plant Control and Surveillance System Wet Plant Link Manager wait to restore
Infinera Corporation
Acronyms
Page D-15
Acronym XC XFP XLM XML cross-connect 10Gbps small form factor pluggable Switching Line Module extensible markup language
Definition
MISC
1R 2R 3R 4R re-amplification re-amplification, re-shape re-amplification, re-shape, re-time re-amplification, re-shape, re-time, re-code
Infinera Corporation
Release 2.0
Page D-16
Infinera Corporation