R11.0 Infinera GNM Overview Guide

Infinera
GNM Overview Guide
Release 11.0
Version 001
V001
Document ID 1900-001369
Infinera Corporation
140 Caspian Court
Sunnyvale, CA 94089
www.infinera.com
+ 1-408-572-5200
- Please refer to the Infinera Customer Web Portal for the most recent version of this document -
Copyright
© Copyright 2015 Infinera Corporation. All rights reserved.
This Manual is the property of Infinera Corporation and is confidential. No part of this Manual may be reproduced for any purposes or
transmitted in any form to any third party without the express written consent of Infinera.
Infinera makes no warranties or representations, expressed or implied, of any kind relative to the information or any portion thereof
contained in this Manual or its adaptation or use, and assumes no responsibility or liability of any kind, including, but not limited to,
indirect, special, consequential or incidental damages, (1) for any errors or inaccuracies contained in the information or (2) arising
from the adaptation or use of the information or any portion thereof including any application of software referenced or utilized in the
Manual. The information in this Manual is subject to change without notice.
Trademarks
Infinera, Infinera Intelligent Transport Networks, I-PIC, IQ NOS, FlexILS, DTN-X, DTN, ATN, FastSMP and logos that contain Infinera
are trademarks or registered trademarks of Infinera Corporation in the United States and other countries.
All other trademarks in this Manual are the property of their respective owners.
Infinera DTN-X, DTN, ATN, 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 numérique respecte les limites de bruits radioélectriques applicables aux appareils numériques de Classe A prescrites
dans la norme sur le matériel brouilleur: "Appareils Numériques," NMB-003 édictée par le Ministère des Communications.
Class A ITE
This is a Class A product based on the standard of the VCCI Council. If this equipment is used in a domestic environment, radio
interference may occur, in which case, the user may be required to take corrective actions.
この装置は、クラス A 情報技術装置です。この装置を家庭環境で使用すると電波妨害を引き起こす場合があります。
この場合には使用者が適切な対策を講ずるよう要求されることがあります。 VCCI-A
Warning
This is a class A product. In a domestic environment this product may cause radio interference in which case the user may be
required to take adequate measures.
FDA
This product complies with the DHHS Rules 21CFR 1040.10 and 1040.11, except for deviations pursuant to Laser Notice No. 50,
dated June 24, 2007.
Page iii
Contents
About this Document

Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Documents for Release 11.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Technical Assistance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Chapter 1 - Introduction
Infinera GNM Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
New Features and Hardware for Release 11.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Configuration Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Service Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
DTN Service Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
DTN-X Service Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
FlexILS Service Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Security and Access Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Chapter 2 - Getting Started

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Infinera Corporation GNM Overview Guide Release 11.0 V001
Infinera Proprietary and Confidential

Page ii
Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Java Web Start Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Installing JRE when the Internet connectivity is not available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Port Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Chapter 3 - Establishing Connectivity

Connecting a GNM Terminal to a Target Network Element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Direct Ethernet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Connecting the GNM Terminal to a Target Network Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Configuring the GNM Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Testing the Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
LAN Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Connecting the GNM Terminal to the LAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Configuring the GNM Terminal for LAN access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Remote Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Connectivity over DCN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Configuring Custom Cache Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Launching Infinera GNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Clearing GNM Software Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Retrieving GNM logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Chapter 4 - Software Maintenance

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Downloading the Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Maintaining the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Maintaining the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Downloading the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Backing up the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Restoring the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Software and Database Maintenance Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
SW-DB Upload/Download Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Downloading the Software Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Downloading the Configuration Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Backing up the Configuration Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Uploading Debug Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
SW-DB Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Installing New Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Upgrading the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Activating Software and Database Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Restarting the Software with empty database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Restoring the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Backing up the Database Image Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
GNM Overview Guide Release 11.0 V001 Infinera Corporation

Page iii
Deleting an Unused Software or Database Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

Compressing the Software or Database Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Chapter 5 - Exploring the User Interface

Infinera GNM Interface Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Infinera GNM Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Keyboard Accelerators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Equipment Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Expanding the Equipment Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Workspace Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Rack View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Equipment View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Quick View Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Alarm Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Slide Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Configuring the GNM View Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Tree Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
GNM Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Save and Reset Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Viewing, Navigating and Printing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Inventories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Infinera GNM GUI Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Appendix A - Third Party Software License Terms
Appendix B - Acronyms
List of Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18

Page iv

Figures
Figure 1-1 Infinera Intelligent Transport Network and Infinera Management Solution . . . . . . . . . . . . . . . . . . 1-2
Figure 3-1 DTN-X Ethernet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Figure 3-2 FlexROADM -Ethernet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Figure 3-3 Local Area Connection Properties: Windows 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Figure 3-4 TCP/IP Properties: Windows 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Figure 3-5 Local Area Connection Properties: Windows XP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Figure 3-6 TCP/IP Properties: Windows XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Figure 3-7 Infinera GNM Login Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Figure 3-8 Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Figure 3-9 Opening LaunchGnmMgr window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Figure 3-10 Choose Helper Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Figure 3-11 Java Cache Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Figure 4-1 SW-DB Upload/Download Manager Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Figure 4-2 SW-DB Manager Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Figure 5-1 GNM Main View for DTN-X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Figure 5-2 GNM Main View for DTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Figure 5-3 GNM Main View for Optical Amplifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Figure 5-4 GNM Main View for FlexROADM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Figure 5-5 GNM Main View for Optical Line Amplifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Figure 5-6 Expanded Equipment Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Figure 5-7 GNM Equipment View for DTN-X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Figure 5-8 GNM Equipment View for DTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Figure 5-9 GNM Equipment View for Optical Amplifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Figure 5-10 GNM Equipment View for FlexROADM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Figure 5-11 GNM Equipment View for Optical Line Amplifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Figure 5-12 Quick View Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Page vi
Figure 5-13 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-17

Figure 5-14 Slide Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-18

Tables
Table 2-1 Infinera DTN GNM Client Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Table 2-2 Recommended Operating System Requirements for GNM Client . . . . . . . . . . . . . . . . . . . . . . . 2-3
Table 2-3 JRE Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Table 2-4 Infinera DTN GNM Client Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Table 2-5 Network Element Port Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Table 4-1 Software Images Panel Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Table 4-2 Database Images Panel Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Table 5-1 GNM Main Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Table 5-2 Alarm Severity Color on the Rack View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Table 5-3 Equipment State Color Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Table 5-4 Infinera GNM Icon Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

Page viii

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

To install JRE on a 64-bit Oracle Solaris machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
To install JRE on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
To connect the Ethernet cable from the craft computer to the target network element . . . . . . . . . . . . . . . . . . . . . . 3-4
To configure the GNM Terminal using Windows 7 platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
To configure the GNM Terminal using Windows XP platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
To ping the node IP address to test the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
To connect the Ethernet cable from the GNM Terminal to the target network element . . . . . . . . . . . . . . . . . . . . . . 3-8
To configure the GNM Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
To disable a proxy service using Internet Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
To configure the custom cache directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
To launch Infinera GNM using Internet Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
To change the password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
To launch Infinera GNM using Mozilla browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
To clear the cache if it is stored in the default directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
To clear the cache if a custom cache directory is configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
To enable GNM log capture for JRE 1.6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
To invoke the SW-DB Upload/Download Manager tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
To download the software image to the network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
To download the database file to the network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
To back up the database to an external server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
To enable automatic upload of network element debug information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
To upload network element debug information manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
To invoke SW-DB Manager tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
To install the new software image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
To upgrade the software image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Page x
To upgrade the firmware using Infinera GNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

To activate software and database images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
To restart the current software image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
To restore a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
To back up the active database image on the network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
To delete a software or database image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
To compress the software or database image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
To expand the tree structure to show more levels of equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
To select the Tree Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
To configure the GNM application window size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
To save user preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
To reset preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
To view Online help from the main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
To view online help from any window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
To navigate Online help pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
To print Online help pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

About this Document
This section is an overview of the Infinera GNM Overview Guide. It discusses these topics:
 “Objective” on page 11
 “Audience” on page 11
 “Document Organization” on page 12
 “Documents for Release 11.0” on page 12
 “Conventions” on page 14
 “Technical Assistance” on page 15
 “Documentation Feedback” on page 15
Objective
This guide describes the Infinera Graphical Node Manager user interface. It also describes the new
features, the hardware and software requirements required to launch the GNM. It also provides procedures
to install and upgrade the software and database on the Infinera network elements.
Audience
The primary audience for this guide includes network operation personnel and administrators responsible
for maintaining network elements and provisioning services using Infinera GNM. This guide assumes that
the reader is familiar with the following topics and products:
 Microsoft Windows XP and Microsoft Windows Vista
 Web browsers such as Internet Explorer, Mozilla and Netscape Navigator
 Internet and networking terminology and concepts
 Optical networking

Page 12 About this Document
Document Organization
The following table describes each chapter in this guide:
Chapter Number: Title Description
CHAPTER 1: Provides an introduction to Infinera GNM and a high-

“Introduction“ level description of the Fault Management, Equip-
ment and Termination Point Management, Perfor-
mance Monitoring and Security and Access
Management (FCPS) functions supported.
CHAPTER 2: Describes the hardware and software platform
“Getting Started“ requirements to run Infinera GNM.
CHAPTER 3: Provides procedures to connect the GNM Terminal to

“Establishing Connectivity“ the target network element.
CHAPTER 4: Describes how to maintain the network element

“Software Maintenance“ software and database using Infinera GNM
interface.
CHAPTER 5: Provides an overview of Infinera GNM interface
“Exploring the User Interface“ including the various GUI components and icons
used.
Appendix A Provides a list of third party software used by the
“Third Party Software License Terms“ Infinera IQ NOS, DNA and SNMP software and the
terms of agreement.
Appendix B: Provides a list of acronyms and their definitions used
“Acronyms“ in Infinera Technical Publications.
Documents for Release 11.0

The following documents are available for Infinera DTN and DTN-X:
Document Name Document ID Description
DTN and DTN-X Installation Guides Portfolio
Infinera DTN and DTN-X 1900-001363 Describes procedures for turning up, commissioning and testing
Turn-up and Test Guide the installed Infinera DTN-X, Infinera Line System (ILS), DTN,
and Optical Line Amplifier network elements. Includes the
description of circuit activation and end-end system testing pro-
cedures.

Documents for Release 11.0 Page 13
Infinera DTN and DTN-X Site 1900-001364 Describes the procedures for initial installation of the Infinera
Preparation and Hardware DTN-X, ILS, DTN, and Optical Line Amplifier network elements
Installation Guide at any given site. Includes procedures for site preparation and
site testing, system cabling, safety procedures and hand-over to
provisioning activities.
DTN and DTN-X Procedure Guides Portfolio
Infinera DTN and DTN-X 1900-001365 Provides the routine task oriented procedures (TOPs) used in
Task Oriented Procedures support of the Infinera DTN-X, ILS, DTN, and Optical Line
Guide Amplifier network elements.
DTN and DTN-X Reference Guides Portfolio
Infinera DTN and DTN-X 1900-001366 Provides the hardware description of the Infinera DTN-X, ILS,
Hardware Description Guide DTN, and Optical Line Amplifier network elements which
includes the description of chassis, common modules and circuit
packs. It provides hardware block diagrams, functional descrip-
tions, mechanical and electrical specifications for each module.
Infinera DTN and DTN-X 1900-001367 Describes the user interface for the Infinera DTN-X, ILS, DTN,
SNMP Agent Reference and Optical Line Amplifier Simple Network Management Proto-
Guide col (SNMP) Agent. It provides detailed instructions to configure
and operate the Infinera SNMP Agent from the Infinera network
element.
Infinera DTN and DTN-X 1900-001368 Provides an overview of the Intelligent Transport Network and its
System Description Guide principal elements, including the Infinera DTN-X, ILS, DTN, and
the Optical Line Amplifier. Includes a description of the Infinera
IQ Network Operating System and an overview of the manage-
ment interfaces for Infinera products.
DTN and DTN-X User Guides Portfolio
Infinera GNM Overview 1900-001369 Describes the Infinera Graphical Node Manager user interface.
Guide It also describes the new features, the hardware and software
requirements required to launch the GNM. It also provides pro-
cedures to install and upgrade the software and database on the
Infinera network elements.
Infinera GNM Fault 1900-001370 Describes the Fault Management inventories, Alarm Manager
Management and and Event Log. It also provides the procedures to perform diag-
Diagnostics Guide nostic tests on Infinera network elements. In addition, it
describes the alarms raised by the Infinera network elements
and the corrective procedures to perform to clear the alarms.
Infinera GNM Configuration 1900-001371 Describes the procedures to use the Infinera GNM to configure
Management Guide the Infinera network elements and the network topology. It also
provides a description on the Equipment Manager and Facility
Manager.

Infinera GNM Performance 1900-001372 Describes the procedures to use Infinera GNM to view perfor-
Management Guide mance monitoring (PM) data and modify PM thresholds for the
Infinera DTN-X, ILS, DTN, and Optical Line Amplifier network
elements. It also provides the PM parameters details reported
by the Infinera network elements.
Infinera GNM Security 1900-001373 Describes the procedures to perform security and access man-
Management Guide agement tasks such as creating, deleting and managing user
accounts on the Infinera network elements.
Infinera GNM Service 1900-001374 Describes the procedures to provision cross-connects, subnet-
Provisioning Guide work connections (SNCs) and protected services on Infinera
DTN-X, ILS, DTN, and Optical Line Amplifier network elements.
It includes a description of the various inventory managers dis-
played in the Infinera GNM.
Infinera DTN and DTN-X TL1 1900-001375 Describes the TL1 interface supported by the Infinera DTN-X,
User Guide ILS, DTN, and Optical Line Amplifier network elements. It
includes the description of the supported TL1 commands and
the procedures for the commonly performed OAM&P functions.
Conventions
The table below lists the conventions used in this guide.
Convention Item Example
bold default font Menu command paths Select Fault Management >
Alarm Manager
Button names Click Apply
User interface labels Click Summary panel
Window/dialog box titles In the Dial-Up Networking window
courier font User-entered text In the Label enter EastBMM
Command output Database restore from
local or remote machine?
Directory path /DNA/GNM
default font, italic Document titles Refer to the Infinera DTN and
DTN-X System Description

Technical Assistance Page 15
Convention Item Example
Default font Icon names Click Node icon

Window names not in the user In the GNM Main View
interface
Helpful suggestions
Note: Note: The window is
refreshed only
after making all
the changes
Technical Assistance
Customer Support for Infinera products is available, 24 hours a day, 7 days a week (24x7). For information
or assistance with Infinera products, please contact the Infinera Technical Assistance Center (TAC) using
any of the methods listed below:
 Email: techsupport@infinera.com
 Telephone:
 Direct within United States: 1-408-572-5288
 Outside North America: +1-408-572-5288
 Toll-free within United States: +1-877-INF-5288 (+1-877-463-5288)
 Toll-free within Germany/France/Benelux/United Kingdom: 00-800-4634-6372

 Toll-free within Japan: 010-800-4634-6372
 Infinera corporate website: http://www.infinera.com

 Infinera Customer Web Portal: https://customersupport.infinera.com
 Please see the Infinera Customer Web Portal to view technical support policies and procedures, to
download software updates and product documentation, to view training course information, or to
create/update incident reports and RMA requests.
Documentation Feedback
Infinera strives to constantly improve the quality of its products and documentation. Please submit
comments or suggestions regarding Infinera Technical Product Documentation using any of the following
methods:
 Submit a service request using the Infinera Customer Web Portal
 Send email to: techpubs@infinera.com
 Send mail to the following address:

Attention: Infinera Technical Documentation and Technical Training

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

CHAPTER 1
Introduction
This chapter provides a high-level introduction to the Infinera Graphical Node Manager and its capabilities
in the following sections:
 “Infinera GNM Overview” on page 1-2
 “New Features and Hardware for Release 11.0” on page 1-3
 “Fault Management” on page 1-14
 “Configuration Management” on page 1-15
 “Service Provisioning” on page 1-16
 “Performance Monitoring” on page 1-18

 “Security and Access Management” on page 1-19

Page 2
Infinera GNM Overview

Infinera GNM is a node-level management application that provides users with on-site access and control
of Infinera FlexROADMs, Infinera DTN-Xs, Infinera DTNs, Infinera Optical Amplifiers and Infinera Optical
Line Amplifiers. Figure 1-1 on page 1-2 depicts the Infinera Intelligent Transport Network solution and
Infinera Management Suite. Infinera GNM is provided to manage network elements within Infinera
Intelligent Transport Networks.
Figure 1-1 Infinera Intelligent Transport Network and Infinera Management Solution
The Infinera GNM is a browser-launched Java application. It provides fault management, configuration
management, service provisioning, performance management, and security management (FCPS)
functionality across local and remote network elements. Users launch the Infinera GNM from a computer
(referred to as the GNM Terminal) using an Internet browser (such as Microsoft Internet Explorer, Mozilla or
Netscape Navigator). Infinera GNM also features context-sensitive navigation and Java-based user
interfaces that provide a “native look-and-feel” on Windows and Solaris platforms.

Page 3
New Features and Hardware for Release

11.0
Table 1-1 lists the new and updated features for IQ NOS software and the FlexROADM, DTN-X, DTN, and/
or Optical Amplifier and Optical Line Amplifier nodes for Release 11.0:
Note: In previous releases, a node with an OTC as the Main Chassis (and an OMM as the node
controller module) was referred to in the documentation as an “Optical Line Amplifier”
node. Note that the management interfaces have always referred to this node type as an
“Optical Amplifier.” In Release 10, the customer documentation is updated to match the ter-
minology of the management interfaces, wherein a node with an OTC Main Chassis is
called an “Optical Amplifier.” Note that the term “Optical Line Amplifier” is re-introduced as
a node with an MTC-9 as the Main Chassis (with an IMM as the node controller module)
and configured with IAMs/IRMs. (Note that a FlexROADM node, a reconfigurable optical
add/drop multiplexer node, is also a node with an MTC-9 as the main chassis, but in this
case the node is configured with FRMs to support optical multiplexing.)
Note: Unless specifically noted otherwise, all references to “line module” will refer interchange-
ably to either the DLM, XLM, ADLM, AXLM, SLM, AXLM-80, ADLM-80 and/or SLM-80
(DTC/MTC only) and AOFM, AOFX, AOLM, AOLM2, AOLX, AOLX2, SOLM, SOLM2,
SOLX, and/or SOLX2 (XTC only). The term “LM-80” is used to specify the LM-80 sub-set
of line modules and refers interchangeably to the AXLM-80, ADLM-80 and/or SLM-80
(DTC/MTC only). Note that the term “line module” does not refer to TEMs, as they do not
have line-side capabilities and are used for tributary extension.
Table 1-1 New and Updated Features for DTN-X, DTN, Optical Amplifier, and FlexILS Nodes
Feature Description
Network Applications
Layer 0 Optical Private Release 11.0 introduces the Layer 0 Optical Private Network (L0 OPN) feature,
Network (OPN) wherein a subscriber’s line module OCG is connected to a provider’s BMM OCG for
cases in which the subscriber does not have access to fiber between required ser-
vice end points.
Open Wave Support In Release 11.0, the FlexILS line modules (AOFM/AOFX/SOFM/SOFX and their
Instant Bandwidth equivalents) support Open Wave configuration, in which two line
modules configured for Open Wave can be connected to each other without
requiring an intermediate amplifier (FRM, in the case of FlexILS line modules). The
two line modules can be connected directly, or with a third party line system between
them.

Page 4
Feature Description
Inter-node Control Plane In Release 11.0, support for Infinera General Communication Channel (IGCC) is
(IGCC) expanded: The maximum number of TE links using IGCC on a DTN-X node is
increased from 30 to 64.
In addition, Release 11.0 IGCC support is expanded to include inter-node connec-
tions between FlexILS line modules (AOFM/AOFX/SOFM/SOFX and their Instant
Bandwidth equivalents) configured for Open Wave.
Submarine Line Terminal Release 11.0 introduces support for split spectrum mode for SLTE manual optical
Equipment (SLTE) cross-connects on the SOFM/SOFX.
In addition, support for express connections between FRMs in SLTE mode is
expanded to include the following cross connect types:
• Optical channel blocking
• ASE idler optical cross connects

Page 5
Feature Description
Node Configurations
Multi-chassis Scalability In Release 11.0, the multi-chassis scalability for a DTN-X node has been updated:
• The total number of chassis supported on a DTN-X remains the same at 60. How-
ever, the maximum number of each chassis type is updated:
• The number of XTCs allowed has been increased from 10 XTCs to 14 XTCs.
• The number of DTCs/MTCs allowed has been decreased from 32 DTCs/MTCs
to 30 DTCs/MTCs.
• For OTCs and MTC-9s, Release 11.0 supports a combined total of 16 OTCs/
MTC-9s. (In Release 10.1 a DTN-X could have a maximum of 12 OTCs and a
separate maximum of 6 MTC-9s.)
• The total number of line modules and OTMs supported on a DTN-X has been
increased from 184 to 224:
• The number of OTMs allowed in a node has been increased from 40 to 64.
• The number of XTC line modules (AOLM, AOLX2, SOLM, etc.) allowed in a
node has been increased from 48 to 64.
• Also in Release 11.0, the supported number of fiber directions is increased for cer-
tain DTN-X configurations:
• For DTN-X using ILS links only (BMMs/OAMs/ORMs only), the number of sup-
ported fiber directions is increased from 12 to 16.
• For DTN-X with MTC-9s using both FlexILS and ILS links, the number of sup-
ported fiber directions is increased from 12 to 16:
• The number of ILS links (BMMs/OAMs/ORMs) supported is increased from
8 to 16.
• The number of FlexILS links (IAMs/IRMs) supported is increased from 4 to
9.
In addition, Release 11.0 updates the support for DTN-X node configuration with
XTC line modules only (no DTC/MTC line modules):
• Up to 42 total chassis (increased from 35 total chassis):
• The number of XTCs allowed has been increased from 18 XTCs to 22 XTCs.
• The number of DTCs allowed has been increased from 7 DTCs to 8 DTCs.
• The number of OTCs allowed has been increased from 10 OTCs to 12 OTCs.
• Up to 192 total line modules and OTMs (increased from 160 total chassis):
• The number of OTMs allowed in a node has been increased from 80 to 96.
• The number of XTC line modules (AOLM, AOLX2, SOLM, etc.) allowed in a
node has been increased from 80 to 96.
Network Timing Protocol To support NTP server redundancy, in Release 11.0 node can be configured with up
(NTP) Redundancy to three NTP servers.

Page 6
Feature Description
XTC Hardware and Hardware Modules
OTN Tributary Module Release 11.0 supports full pre-provisioning of the OTM2-500 PON. In previous
(OTM) releases, the OTM2-500 was pre-provisioned as a generic “OTM” and was reported
in the management interfaces for both “Installed Equipment” and “Provisioned
Equipment” as “OTM-500.” In Release 11.0, the OTM2-500 can be pre-provisioned
using the full PON “OTM2-500,” and the “Installed Equipment” and “Provisioned
Equipment” fields will reflect the full PON “OTM2-500. In addition, any OTM2-500
provisioned before Release 11.0 will also reflect the full PON in the “Installed
Equipment” and “Provisioned Equipment” fields.
Tributary Interface Module Release 11.0 introduces the following TIMs for the XTC:
(TIM) • TIM-16-2.5GM
• TIM-1-40GM
In Release 11.0, the management interfaces include support for installed equipment
type and provisioned equipment type for the following TIMs (before Release 11.0,
these TIMs were identified in the management interfaces in the PON field only):
• TIM-5B-10GM
• TIM-1B-100GE
In Release 11.0 the following TIMs support ODU multiplexing:
• TIM-1-100GX
• TIM-5-10GX
NOTE: A TIM-5-10GX shipped in Release 11.0 supports ODU multiplexing by
default. A TIM-5-10GX shipped before Release 11.0 supports ODUk switching by
default. When upgraded to Release 11.0 software, a pre-Release TIM-5-10GX will
continue to support ODUk switching with no effect to traffic. To provision a multiplex-
ing service on a TIM-5-10GX shipped before Release 11.0, the TIM-5-10GX must be
upgraded to the latest firmware. The upgrade requires a cold reboot, which will affect
any traffic on the TIM-5-10GX.

Page 7
Feature Description
Tributary Optical Module Release 11.0 introduces the following new TOM supported on the TIM-1-40GM of an
(TOM) XTC:
• TOM-40GMR-FR
Also in Release 11.0, the following existing DTC/MTC TOMs are now supported on
the XTC on the TIM-16-2.5GM:
• TOM-2.5G-LR2
• TOM-2.5G-IR2
• TOM-2.5GMR-IR1
• TOM-2.5GMR-SR1
• TOM-MR-Dn-LR2
• TOM-MR-Cn-LR2
• TOM-1G-LX
• TOM-1G-SX
• TOM-1G-ZX
MTC-9 Hardware and Hardware Modules
FlexROADM Module Release 11.0 supports the following new capabilities for express connections
(FRM) between FRMs in SLTE mode FRMs:
Fiber Panel Chassis (FPC) Hardware and Hardware Modules
Fiber Multiplexing Panel Release 11.0 adds a new FMP for Open Wave configurations with FlexILS line mod-
(FMP) ules :
• FMP-F250-19-2-LC-LC
OTC Hardware and Hardware Modules
Submarine Control Module Release 11.0 supports full pre-provisioning of the SCM-2 PON. In previous releases,
(SCM) the SCM-2 was pre-provisioned as a generic “SCM” and was reported in the man-
agement interfaces for both “Installed Equipment” and “Provisioned Equipment” as
“SCM-1.” In Release 11.0, the SCM-2 can be pre-provisioned using the full PON
“SCM-2,” and the “Installed Equipment” and “Provisioned Equipment” fields will
reflect the full PON “SCM-2.” In addition, any SCM-2 provisioned before Release
11.0 will also reflect the full PON in the “Installed Equipment” and “Provisioned
Equipment” fields.

Page 8
Feature Description
System Interfaces
Client/Tributary Interfaces Release 11.0 supports the following new client/tributary interfaces on the XTC:
• Supported by TIM-1-40GM:
• OC-768
• STM-256
• Supported by the TIM-16-2.5GM:
• 1GbE
Service Provisioning and Service Recovery
FlexILS Service In Release 11.0, FlexILS service provisioning is expanded to include the following
Provisioning new capabilities for FRMs in SLTE mode:
• Split spectrum mode for manual optical cross-connects in SLTE configuration
In addition, the following existing features are expanded to include express connec-
tions between FRMs in SLTE mode:
Dynamically Signaled Release 11.0 expands 1 Port D-SNCP support to include line-side termination points
Subnetwork Connection on the XTC.
(SNC) Provisioning
OTU4 Transparent In Release 11.0 the DTN-X supports virtual concatenation for transparent transport
Transport without FEC without FEC for OTU4 services on the following TIMs:
• TIM-1-100G
• TIM-1-100GM
• TIM-1-100GX, when configured for ODU4-ODL (ODU switching) operating mode
The OTU4 is routed through the network as ten ODU2i; all of the ODU2i must be
routed over the same OCG/SCG, and all ten ODU2i entities must traverse through
the same modulation type (QPSK or BPSK is supported).
ODU Multiplexing In Release 11.0, the DTN-X supports ODU multiplexing, in which the client OTUk
and ODUk overhead is terminated at the ingress, and the ODUj is switched across
the network. The ODUj overhead is switched at every network hop from one inter-
face to the next interface (meaning that the ODUj overhead is accessible at every
hop).
• The TIM-1-100GX supports the following ODU multiplexing options:
• Up to 4xODU2 to ODU4 to OTU4
• Up to 4xODU2e to ODU4 to OTU4
• The TIM-5-10GX supports the following ODU multiplexing options:

Page 9
Feature Description
Network Mappings Release 11.0 supports the following new network mapping options for services on
the XTC:
• OC-768 -> ODU3-AMP
• OC-768 -> ODU3-BMP
• STM-256 -> ODU3-AMP
• STM-256 -> ODU3-BMP
• 1GBE -> ODU0-TTT-GMP
• OTU4 -> ODU2i-10v
• GFP -> ODUflexi
Digital Subnetwork Release 11.0 expands 1 Port D-SNCP support to include the following:
Connection Protection • Line-side termination points on the XTC.
(D-SNCP)
• 1GbE services originating on the TIM-16-2.5GM on the XTC.
• ODU multiplexing services on the XTC:
• On the TIM-1-100GX:
• Up to 4xODU2e to ODU4 to OTU4
• On the TIM-5-10GX:
Fast Shared Mesh For services with endpoints on the XTC, the DTN-X supports Fast Shared Mesh
Protection (FastSMP™) Protection (FastSMP™), which allows protection groups to share protection
resources using protection paths that are not required concurrently by the two
protection groups. Infinera’s FastSMP supports protection switching in less than
50ms.
ODUk AIS for ODUk Release 11.0 introduces support for ODUk AIS TDA in DTN for ODUk encapsulated
Encapsulated Clients on clients on the DTC/MTC.
DTC/MTC
Tributary Disable Action Release 11.0 expands the support of the Tributary Disable Action feature: DTN-X
tributaries can be configured to trigger the egress tributary disable action based on
forwarded defects.
Encapsulated Client Release 11.0 includes the following updates for Encapsulated Client Disable Action:
Disable Action • For DTN-X, Encapsulated Client Disable Action is now supported for OC-768,
STM-256, and 1GbE services.
• For DTN, Encapsulated Client Disable Action is now supported for SONET, SDH,
and ODUk services. In addition, the 10GbE support is expanded to include ODU-
AIS and Laser Off options.

Page 10
Feature Description
Fault Management
Alarm Surveillance Release 11.0 introduces an administrative event to indicate an update to the
Expected Span Loss (ESL) values. In TL1 interface, the condition description for the
event (ESLCHG) includes the updated ESL high and low thresholds, as well as the
previous values for ESL high and low thresholds. In GNM/DNA, the new and previ-
ous values are displayed in the Additional Text field for the event.
In Release 11.0, in order to track equipment removals/replacements, any equipment
alarm/event (e.g., IMPROPRMVL, PLUGOUT, etc.) includes the serial number of the
module on which the condition is reported. In TL1 this is shown in the REPT ALM or
REPT EVT autonomous message. In GNM/DNA, the serial number is shown in the
Additional Text field for the alarm/event. The serial number is shown for both raising
and clearing of alarms/events. Note that the serial number isn’t reported for condi-
tions where the serial number is not yet known (e.g., upon circuit pack plug-in and
circuit pack initialization, etc).
In Release 11.0, GbE clients (1GbE, 10GbE, 40GbE, and 100GbE) on Infinera
nodes support a configurable setting to raise an OOS-AU alarm when the GbE cli-
ent’s operational state is disabled. The setting is configured on a per-client basis; the
default behavior (and the pre-Release 11.0 behavior) is that no alarm is raised when
the operation state is disabled. Without the OOS-AU alarm, the user can see the
operation state by viewing the properties of the GbE client.
Optical Ground Wire Release 11.0 supports the Optical Ground Wire (OPGW) feature, which helps
(OPGW) prevent traffic disruption in case of a lightning strike to an optical ground wire.
NOTE: Do not configure OPGW parameters (Aggressive Tracking and Rapid Recov-
ery) unless consulted to do so by an Infinera Technical Assistance Center (TAC)
resource.
Maintenance and Release 11.0 supports loopbacks on the new service types added on the XTC:
Troubleshooting • OC-768 (on the TIM-1-40GM)
• STM-256 (on the TIM-1-40GM)
Release 11.0 supports the following loopbacks for PXM services:
• Ethernet Interface (ETHIF)
• All other loopbacks supported by the TIM
Release 11.0 supports PRBS tests for the new service types added on the XTC:
• OC-768 (on the TIM-1-40GM)
• STM-256 (on the TIM-1-40GM)
Release 11.0 supports GbE client termination point test signals on 1GbE clients on
the TIM-16-2.5G on the XTC. .
In addition, Release 11.0 supports transparent J0 path trace messaging for OC-768
and STM-256 services on the TIM-1-40GM of an XTC.

Page 11
Feature Description
Debug File Transfer Before sending any compiled file (i.e., debug files, PM files, and database backups),
the node must first compile the file, a process which takes several minutes and can-
not be canceled once initiated. Because of this, starting in Release 11.0 when a
compiled file transfer is initiated by the user, the node will first verify the FTP server
configuration before compiling the file. Users can also enable a connectivity check
with the configured servers prior to initiating the debug file transfer.
Equipment Management
Line Module Modulation Release 11.0 introduces support for mixed modulation for ILS2 line modules with
SD-FEC. Starting in Release 11.0, an AOLM2, AOLX2, SOLM2, or SOLX2 can
support both BPSK and QPSK.
Performance Monitoring (PM)
Optical, Digital, and Client In addition to PM data support for the new modules listed above, Release 11.0 sup-
Performance Monitoring ports increased granularity for pre-FEC Q value PM for Carrier CTPs and Optical
Channel CTPs. In previous releases, pre-FEC Q value PM could be retrieved for 15
minute and 24 hour intervals. In Release 11.0, the AOLM2, AOLX2, SOLM2,
SOLX2, AOFX, AOFM, SOFX, and SOFM also support per carrier (wave) real-time
Pre-FEC Q value PM data for 10 second interval. The 10-second interval values are
stored on the node for 24 hours (note that the user can configure DNA to read and
archive this data every 24 hours so that the information is not lost). In addition, the
GNM/DNA interfaces are updated in Release 11.0 to support display of this informa-
tion in a chart format.
PM Data Uploads Release 11.0 introduces the following updates for PM data file uploads:
• Infinera nodes can be configured to transfer PM data files simultaneously to both
the primary and secondary FTP servers. (Simultaneous transfer requires that both
servers are configured correctly.)
• When a compiled file transfer is initiated, the node will first verify the FTP server
configuration before compiling the file. (Users can also enable a connectivity check
with the configured servers prior to initiating the file transfer.)
DTN-X Network Latency The DTN-X supports a PM measurement for network latency, a measure for network
Measurement latency incurred between ODUk connection termination points within a DTN-X net-
work. This includes measurements between any two peer ODUk termination points.

Page 12
Feature Description
Security and Access Management
User Passwords Release 11.0 includes the following updates for user passwords:
• Support for a configurable network element password digest type: In addition to
MD5, secure hash algorithm (SHA) values are now supported in Release 11.0.
The following password digest schemes are supported: MD5, SHA-256, SHA-384,
SHA-512. For new Release 11.0 installations, the default scheme is SHA-256. For
nodes upgrading from pre-Release 11.0, the default scheme is MD5 to maintain
backwards compatibility.
• Support for longer passwords: A user password can be up to 32 alphanumeric
characters long (the previous maximum password length was 10 characters).
• TL1 support for default user password configuration: An admin user can use the
TL1 interface to change the default user password for the node (the default pass-
word is “infinera1”). In previous releases, default user password could be changed
only via DNA/GNM.
Secure Sockets Layer In Release 11.0, Infinera nodes are upgraded to a later version of Secure Sockets
(SSL) Layer (SSL):
• From OpenSSL 1.0.0e to OpenSSL 1.0.1h
• From OpenSSH 5.9_p1 to OpenSSH 6.6_P1
Software and Database Management
Nodal Software Multi- Release 11.0 includes functionality that allows DTN and DTN-X digital node types
Release Interoperability which are running IQ NOS Release 11.0 software to inter-operate with ILS Optical
Amplifiers or FlexILS Optical Line Amplifiers that are running IQ NOS Release 10.1
software. Note that support is continued as in previous releases for the ILS Optical
Amplifiers or FlexILS Optical Line Amplifiers to be running the same software
release as the DTN and DTN-X digital nodes (e.g., Release 11.0).
Nodal Software Efficient Starting with upgrades from Release 11.0 software, the nodal software update pro-
Update cess will automatically bypass those hardware FRUs that do not have any software
changes and/or enhancements in the target upgrade release, hence reducing the
total nodal upgrade time and avoid unnecessary updates or issues. This feature will
take effect starting from the next IQ NOS software maintenance release of Release
11.0 (e.g., Release 11.0.1), and the next major release after Release 11.0 in the
future.
Nodal Software Pre- Release 11.0 includes functionality to support Nodal Software Pre-Upgrade
Upgrade Verification Verification for future software upgrades of the network element. At the time of a
nodal software upgrade (from Release 11.0 to a Release 11.0.x maintenance
release or from Release 11.0 to a future major release such as Release 15.3), the
user can initiate a Prepare for Upgrade command, which will cause the node to
distribute the new software to the shelf controllers and perform pre-upgrade checks
on the shelf controllers to verify that the upgrade will complete successfully. These
checks are performed without initiating the actual upgrade. In this way, the user can
prepare for a software upgrade without performing the upgrade, and without losing
management connectivity.

Page 13
Feature Description
FTP Connection Before sending any compiled file (i.e., debug files, PM files, and database backups),
Verification the node must first compile the file, a process which takes several minutes and can-
not be canceled once initiated. Because of this, starting in Release 11.0 when a
compiled file transfer is initiated by the user, the node will first verify the FTP/SFTP
server configuration before compiling the file.
Database Management Release 11.0 introduces the following updates for database backup file uploads:
• Infinera nodes can be configured to transfer database backup files simultaneously
to both the primary and secondary FTP servers. (Simultaneous transfer requires
that both servers are configured correctly.)
• When a compiled file transfer is initiated by the user, the node will first verify the
FTP server configuration before compiling the file. (Users can also enable a con-
nectivity check with the configured servers prior to initiating the file transfer.)
• The user interfaces (TL1, GNM, DNA) support the “%V” token for adding the soft-
ware version to the database backup file names.
Network Management User Interfaces
Transaction Language 1 Release 11.0 includes updates to the TL1 interface to support the Release 11.0 fea-
(TL1) Interface tures listed in this chapter. See the Infinera DTN and DTN-X TL1 User Guide for
detailed information on TL1 interface features and syntax updates.
Commissioning Command In Release 11.0, the CCLI presents an alert banner of hash marks during the reboot
Line Interface (CCLI) cycle to draw attention to the reconfiguration option that might otherwise be missed.
The hash tag alert banner is presented in the CLI prior to the reconfiguration option
before the prompt, “Press Enter to reconfigure, or wait for normal startup..."

Page 14
Fault Management
Infinera Intelligent Transport Networks feature 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.
Refer to the Infinera GNM Fault Management and Diagnostics Guide for more information on fault
management.
Infinera GNM provides two fault management tools:
 Alarm Manager—Displays outstanding alarm conditions. Alarm conditions display category, sever-
ity, source, time of occurrence, acknowledgment check, service-affecting or non-service affecting
and probable cause.
 Event Log—Displays historical event logs. Events display event type, severity, source, time of
occurrence, message, AID and Log Type.
Additionally, Infinera GNM allows you to:
 acknowledge outstanding alarms.
 allow/inhibit alarms per managed entity.
 configure reminders and useful messages for alarms using Customizable Alarm Settings feature.
 configure severity of individual fault conditions using Alarm Severity Profile Settings (ASPS) feature.
 control environmental alarms by configuring output closure contacts and input closure contacts.
 export all alarms and events.
 export current view of alarms and events.
 filter alarms and events.
 perform maintenance functions such as diagnostics and loopbacks.
 sort alarms and events based on all the fields, in both ascending and descending order.
 test and monitor the diagnostic capabilities like loopabacks, trace messaging, PRBS test and so on.
Refer to the Infinera GNM Fault Management and Diagnostics Guide for more information on fault
management and diagnostics.

Page 15
Configuration Management
Infinera Intelligent Transport Networks provide configuration management capabilities that allow the user
to configure and monitor the state of circuit packs and termination points. To ease deployment of network
elements and meet diverse customer needs, Infinera GNM supports two modes of configuration:
 Auto-configuration—In this mode, the network element automatically detects and configures the
equipment when it is present.
 Pre-configuration—In this mode, users can pre-configure equipment and termination point prior to
the equipment being present.
Refer to the Infinera DTN and DTN-X System Description for more information on equipment types and
configuration modes.
Infinera GNM enables users to:
 pre-configure managed equipment.
 modify attributes associated with managed equipment.
 delete managed equipment.
 modify the administrative state of managed entity, enabling it to be in-service or out-of-service.
 configure and modify switching mode options in DTC-B.
 clear or leave outstanding alarms, using the Alarm Reporting Control (ARC) feature.
 view equipment inventory using inventory tools like the Facility Manager and Equipment Manager.
 perform timer-based disabling of Automatic Laser Shutdown (ALS) feature.
 enable automatic in-service (AINS) on a Tributary port, for a specified time interval, to troubleshoot a
faulty termination point in an alarm-free state.
For faster configuration of managed equipment, Infinera GNM allows users to configure templates with
default values. The newly created managed object attributes are initialized to the default values defined in
the template.
Infinera GNM also supports Protection Group Manager tool to view, create, lockout, clear lockout, manual
switch or delete protection groups. The tool also supports revertive protection switching.
Refer to the Infinera GNM Configuration Management Guide for more information on equipment
management.

Page 16
Service Provisioning
 “DTN Service Provisioning” on page 1-16
 “DTN-X Service Provisioning” on page 1-16
 “FlexILS Service Provisioning” on page 1-17
DTN Service Provisioning

IQ NOS provides service provisioning capabilities that include establishing data path connectivity between
endpoints for delivery of end-to-end capacity. The services are originated and terminated in a DTN. IQ
NOS defines the following types of cross-connect endpoints:
 Tributary-side Endpoints
 Tributary DTF Path Endpoints
 Line DTF Path Endpoints
IQ NOS automatically creates the endpoints when connections are configured on the equipment. IQ NOS
supports the following service provisioning modes to meet diverse users needs:
 Manual Cross-connects (DTN)-End-to-end services are built by manually creating each of the cross-
connects that compose the circuit.
 GMPLS Signaled Subnetwork Connections (SNCs)-End-to-end services are created dynamically by
GMPLS; the user specifies only the endpoints.
DTN-X Service Provisioning

By way of DTC/MTC Expansion chassis, a DTN-X node supports all of the service provisioning capabilities
supported by the DTN. In addition to the DTC/MTC service provisioning features, the DTN-X supports the
following service provisioning capabilities on the XTC:
 Manual Cross-connects (DTN-X)
 GMPLS Signaled Subnetwork Connections (SNCs) on DTN-X
 DTN-X Virtual Concatenation (VCAT)
 DTN-X Network Mapping
 DTN-X Payload Treatment Options

Page 17
FlexILS Service Provisioning

FlexILS services are end-to-end optical light paths that are designed for a specific optical slice or super
channel across the Infinera FlexILS network. FlexILS supports the following service provisioning
capabilities:
 Manual Optical Cross-connects
 Traffic Engineering (TE) Links
 Optically Engineered Lightpath (OELs)
 Optical Subnetwork Connections (O-SNCs)
Refer to the Infinera DTN and DTN-X System Description and Infinera GNM Service Provisioning Guide
for more information on service provisioning.
Refer to the Infinera GNM Service Provisioning Guide for more information on provisioning management.

Page 18
Performance Monitoring
Infinera Intelligent Transport Networks provide 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.
The system provides an extensive collection of performance monitoring (PM) data, including:
 Infinera Digital Transport Frame (DTF) PM data (for section and path layers) at every DTN
 Optical PM data at every DTN and Optical Line Amplifiers
 Native SONET/SDH section layer PM data at tributary ports
 1GbE and 10GbE PM data
 Forward Error Connection (FEC) PM data at every DTN
For more information on the system performance monitoring, refer to the Infinera DTN and DTN-X System
Description.
Infinera GNM enables users to:
 access real-time PM data.
 view PM data collected for 15 minute and 24 hour intervals.
 reset PM counters.
 set PM threshold crossing alerts.
 enable or disable PM data reporting.
 monitor the performance of end-user circuits and log historical PM data for analysis.
 configure the PM data screen refresh rate.
Refer to the Infinera GNM Performance Management Guide for more information on performance
management.

Page 19
Security and Access Management

Infinera GNM provides control of the network element security features in compliance with the GR-815-
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 on security
administration functions supported by the network element, refer to the Infinera GNM Security
Management Guide.
Infinera GNM security administration capabilities enables users to:
 manage target network element user accounts, including the ability to add new users, modify user
attributes, and delete users
 end active user sessions
 export/import user profiles across network elements
 configure password reuse history count
The NE-Wide Security Settings option allows a network element user with security administrator privilege
to configure the security parameters. Infinera GNM also supports Remote Authentication Dial-In User
Service (RADIUS) server settings and Secure Shell (SSH).
Refer to the Infinera GNM Security Management Guide for more information on security management.

Page 20

CHAPTER 2
Getting Started
This chapter describes the browser, hardware and software platform requirements to run Infinera GNM on
your machine. It includes the following sections:
 “Hardware Requirements” on page 2-2
 “Software Requirements” on page 2-3
 “Browser Requirements” on page 2-7
 “Port Information” on page 2-8

Page 2
Hardware Requirements
Table 2-1 lists the minimum and recommended hardware requirements for Infinera GNM. Ensure that the
GNM Terminal configuration meets or exceeds the minimum requirements
Table 2-1 Infinera DTN GNM Client Hardware Requirements
Hard disk free

space
Processor speed Memory
Operating Recommende
System Minimum Recommended Minimum Recommended Minimum d
Oracle 1 GHz 1 GHz 2 GB 3 GBa 2 GB 2 GB

Solaris
Microsoft 1.5 GHz 2 GHz 2 GB 3 GBb 2 GB 2 GB
Windows PC
Linux 1 GHz 2 GHz 2 BG 3 GBa 2 GB 2 GB
Macintosh 2.4 GHz 2.4 GHz 2 GB 3 GB 2 GB 2 GB
a. Swap space equal to or greater than the physical RAM size
b. The recommended virtual memory is 1.5 times to 3 times the memory size

Page 3
Software Requirements
In order to launch Infinera GNM client, make sure any of the following operating system requirement is
met.
Table 2-2 Recommended Operating System Requirements for GNM Client
Requirements Versions
Oracle Solaris Oracle Solaris 11 (64 bit)

Microsoft Windows 7 Windows Service Pack 1
Microsoft Windows 8 Windows Service Pack
Redhat Enterprise Linux Version 6
Macintosh Version 10.8
Additionally,
 Ensure that all OS patches are installed as recommended by Sun Microsystems (now Oracle). For
the patch cluster, go to https://support.oracle.com.
 Ensure that the following two Oracle Solaris patches or the latest revision of the same are installed:
 118833-36 or later
 118777-13 or later
 119963-14 or later
 120753-06 or later
 139574-03 or later
 Ensure that the patch cluster required for Java is installed as recommended by Sun Microsystems
(now Oracle). For a list of patches go to https://support.oracle.com
In addition, the Verisign License Signature must be accepted. The DTN GNM client prompts you to accept
the license if it is not already accepted.
Java Web Start Requirements

This section lists the JRE requirements to run the Infinera GNM. When you first launch the GNM Client and
if no JRE is installed on your machine and Internet connectivity is available, the GNM client will
automatically download and install the JRE version (if available for automatic download). For information
on the list of JRE versions that are available for auto-download is available at http://www.oracle.com/
technetwork/systems/patches/overview/index.html

Page 4
If the JRE version is not available for auto-download, go to

http://www.oracle.com/technetwork/java/javase/downloads/index.html to download the JRE version
manually and install the required version.
Table 2-3 JRE Requirements
Oracle Solaris 11 and Microsoft Windows 7 and Red Hat Linux 6.6 and Macintosh 10.10
10 8 6.5 and 10.8
JRE1.7.72(64 bit) • JRE1.7.72 (32 and 64 • JRE1.7.72 (64 bit) on • JRE1.7.72 (32 and
bit) Red Hat Linux Version 64 bit)
• JRE1.8.40 (32 and 64 6.6 • JRE1.8.40 (64 bit)
bit) • JRE1.8.40 (64 bit) on on Macintosh 10.8
Red Hat Linux Version only
6.6
• JRE1.7.72 (32 bit) on
Red Hat Linux Version
6.5
• JRE1.8.40 (32 bit) on
Red Hat Linux Version
6.5
Note: GNM does not restrict the launch of GNM client using JRE versions higher than the listed
above. It is recommended to contact Infinera Technical Assistance Center before using a
JRE version not listed above. For contact information see “Obtaining Technical Assistance”
on page 77.
Installing JRE when the Internet connectivity is not available
To install JRE on a Microsoft Windows PC
Step 1 Navigate to the directory where the jre-6u20-windows-i586-p.exe file is present.

Step 2 Double-click on jre-6u20-windows-i586-p.exe to install the JRE.
To install JRE on a 64-bit Oracle Solaris machine
Note: Use common desktop environment to install the JRE on the Oracle Solaris machine.
Step 1 Copy the following files to the root directory:

 jre-6u20-solaris-sparc.sh
 jre-6u20-solaris-sparcv9.sh

Page 5
Step 2 Change permissions to the following files. Enter:

chmod 777 jre-6u20-solaris-sparc.sh
chmod 777 jre-6u20-solaris-sparcv9.sh
Step 3 Execute the two files. Enter:
./jre-6u20-solaris-sparc.sh
./jre-6u20-solaris-sparcv9.sh
Step 4 Remove the old/existing softlink to java. Enter,
rm /usr/java
Step 5 Create the java softlink for the new JRE
ln -s /jre1.6.0_20 /usr/java
Step 6 Remove the old/existing softlink to javaws. Enter,
rm /usr/bin/javaws
Step 7 Create the javaws softlink for the new JRE
ln -s /jre1.6.0_20/bin/javaws /usr/bin/javaws
Step 8 Remove the old/existing softlink to mozilla plug-in. Enter,
rm /usr/sfw/lib/mozilla/plugins/libjavaplugin_oji.so
Step 9 Create the mozilla plug-in softlink for the new JRE
ln -s /jre1.6.0_20/plugin/sparc/ns7/libjavaplugin_oji.so /usr/sfw/lib/
mozilla/plugins/libjavaplugin_oji.so
To install JRE on Linux
Note: Use common desktop environment to install the JRE on the Oracle Solaris platform.
Step 1 Copy the file jre-6u18-linux-i586.bin file to the /usr/java directory.

Step 2 Change directory to /usr/java. Enter:
cd /usr/java
Step 3 Change permissions to the file. Enter:
chmod 777 jre-6u18-linux-i586.bin
Step 4 Execute the file. Enter:
./jre-6u18-linux-i586.bin
Step 5 Remove the old/existing softlink to java. Enter,
rm /usr/bin/java
Step 6 Remove the old/existing softlink to javaws. Enter,

Page 6
rm /usr/bin/javaws
Step 7 Create the javaws softlink for the new JRE
ln -s /usr/java/jre1.6.0_18/bin/java /usr/bin/java
ln -s /usr/java/jre1.6.0_18/bin/javaws /usr/bin/javaws

Page 7
Browser Requirements
In order to run the Infinera GNM, the GNM Terminal must have one of the following browsers specified in
Table 2-4
Table 2-4 Infinera DTN GNM Client Browser Requirements
Oracle Sun Solaris Microsoft Windows Linux Macintosh
Mozilla 6.0.2 • Internet Explorer 11 Mozilla Firefox v 31.1.0 Safari 8.0.3

• Mozilla Firefox v 34.0.5
• Google Chrome v
41.0.2272

Page 8
Port Information
Table 2-5 provides the network element port information
Table 2-5 Network Element Port Information

Port Service Application Purpose Direction Communicatio Firewall configuration
No. n initiated by
Transport Protocol: TCP
5073 XML Agent XML Agent DNA server/GNM communicates with the network Bi-directional in terms of packet flow between Management To allow traffic to port 5073 on the
service element using this port DNA Server/GNM and Network Element. Applications (DNA network element from DNA Server
Server/GNM) and GNM client hosts
15073 XML Proxy XML proxy Agent Used by the DNA Server/GNM Client to Bi-directional in terms of packet flow between Management To allow traffic to port 15073 on
Agent Service communicate with XML Agent running on the proxy network element and the Management Applications (DNA the network element from DNA
SNE via GNE element (Proxy). Applications. Server /GNM) Server and GNM client hosts
10023a Telnet Proxy Telnet Proxy Server Used for telnet to SNEs via GNE through this Bi-directional in terms of packet flow between Client Host To allow traffic to port 10023 on
Server Port service for accessing NE operating system shell. network element and the Client Host. the network element from client
host used for telnet.
21b FTP FTP Used for manual FTP operations, like Transfer of Bi-directional in terms of packet flow between NE To allow traffic to port 21 on the
Slog info. network element and the Client Host. NE from client host
22 SSH Secured Channel for Used to establish secure communication for Bi-directional in terms of packet flow between Client host To allow traffic to port 22 on the
management management services between client host and network element and the Client Host. NE from DNA server, GNM and
applications (FTP, SSH, NE client host.
TL1 and XML)
23 Telnet Telnet Server Used to connect to NE's telnet shell. (Essentially Bi-directional in terms of packet flow between Client Host Can be blocked if access to telnet
for debugging) network element and the Client Host. is not required for debugging
purpose
8080 HTTP WebServer Used for downloading the JAR files of GNM from Bi-directional in terms of packet flow between GNM To allow traffic to port 80 on the
NE network element and the Client Host. NE from GNM.
10080 HTTP HTTP Proxy Server Used for downloading the GNM JAR files of SNEs Bi-directional in terms of packet flow between NE GNM To allow traffic to this port on the
via GNE through this service and GNM NE from GNM.
Transport Protocol: Telnet
9090 and TL1 TL1 Agent Used for launching TL1 session with NE. Port Bi-directional in terms of packet flow between NE Client Host To allow traffic to this port on the
9099c 9099 gives TL1 programmatic interface and Client Host NE from client host.
Transport Protocol UDP

123 NTPD Network Time Protocol NTPD server port- Required in case NE is used Uni-directional in terms of packet flow Network element(s) Allow traffic to UDP port on DNA
(No Server as NTP Server for the network elements. server from network elements.
longer
used in
R10.0)
123 NTP NTP Client on NE Used for synchronizing time with an external NTP Bi-directional in terms of packet flow between NE This port must be kept open.
server network element and the NTP server.

Page 9
Table 2-5 Network Element Port Information

Port Service Application Purpose Direction Communicatio Firewall configuration
No. n initiated by
161 SNMP SNMP Agent Used for interacting with SNMP agent running on Bi-directional in terms of packet flow between NE Client Host To allow traffic to this port on the
the NE and Client Host NE from client host.
162 SNMP SNMP Trap Proxy Used for receiving SNMP traps from SNE and Bi-directional in terms of packet flow between SNE Can be blocked as NE will use
proxy them to receiver GNE and SNE Ephemeral port to forward trap to
a trap receiver.
a. Can be blocked if Telnet is not going to be used for debugging Network Elements
b. If all the NEs are configured with secure FTP then this port may be blocked.
c. Can be blocked if secure TL1 is chosen as communication channel

Page 10

CHAPTER 3
Establishing Connectivity
This chapter describes how to establish connectivity between the GNM Terminal and a target network
element (a DTN/DTN-X/FlexROADM/Optical Amplifier/Optical Line Amplifier) in the following sections:
 “Connecting a GNM Terminal to a Target Network Element” on page 3-2
 “Launching Infinera GNM” on page 3-11
 “Retrieving GNM logs” on page 3-18

Page 2
Connecting a GNM Terminal to a Target

Network Element
The GNM Terminal can be connected to a target network element using one of the following methods:
 Direct Ethernet Connection. See “Direct Ethernet Connection” on page 3-2.
 LAN Connection. See “LAN Connection” on page 3-8.
 Remote Connection. See “Remote Access” on page 3-9.
Direct Ethernet Connection

This section describes how to set up a direct Ethernet connection from a GNM Terminal to the craft
Ethernet port on the Management and Control Module (MCM) / Optical Management Module (OMM) /
DTN-X Control Module (XCM)/ Infinera Management Module (IMM) of a target network element under the
following headings:
 “Connecting the GNM Terminal to a Target Network Element” on page 3-2
 “Configuring the GNM Terminal” on page 3-4
 “Testing the Connection” on page 3-7
Connecting the GNM Terminal to a Target Network Element

The GNM Terminal must be connected to the target network element and configured in order to access the
Infinera GNM interface.
The DTN-X network element provides a craft Ethernet port on the XCM, the FlexROADM network element
provides a craft Ethernet port on the IMM, the DTN network element provides a craft Ethernet port on the
MCM and the Optical Line Amplifier network element provides a craft Ethernet port on the OMM. The
following procedure describes how to connect to the XCM/MCM/OMM/IMM. The GNM Terminal must be
connected to the XCM/MCM/OMM/IMM.
Note: The type of Ethernet cable required will depend on the make and model of computer used
for the GNM Terminal.

Page 3
Figure 3-1 DTN-X Ethernet Connection
Figure 3-2 FlexROADM -Ethernet Connection
Each network element must have a unique IP address that you use to access the element.

Page 4
To connect the Ethernet cable from the craft computer to the target network element
Step 1 Connect the Ethernet cable to the Ethernet port on the craft computer.
Step 2 Connect the Ethernet cable to the connector labeled Craft on the active XCM/MCM/OMM/IMM.
Note: If there is a redundant XCM/MCM/OMM/IMM, it should not be installed in the slot at this
time.
Configuring the GNM Terminal

Follow the procedures described below to establish a direct connection between the craft computer and
the target network element.
 “To configure the GNM Terminal using Windows 7 platform” on page 3-4
 “To configure the GNM Terminal using Windows XP platform” on page 3-6
If there are any values already entered prior to configuration, record the values and enter the new values
as suggested.
To configure the GNM Terminal using Windows 7 platform
Step 1 From your Windows desktop, choose Start > Control Panel > Network and Sharing Center >
Change adapter settings.
Step 2 Right-click Local Area Connection and select Properties. The Local Area Connection Properties
window is displayed.

Page 5
Figure 3-3 Local Area Connection Properties: Windows 7
Step 3 Select Internet Protocol(TCP/IP Protocol), and click Properties. The Internet Protocol(TCP/
IP) Properties window is displayed.
Figure 3-4 TCP/IP Properties: Windows 7
Step 4 Select Use the following IP address.

Step 5 In the IP Address field, enter an IP address. The IP address should be in the same subnet as
the craft port’s IP. The default Subnet mask is 255.255.255.0.
Step 6 The Default Gateway field should be left blank.

Page 6
Step 7 Click OK to save the changes.

Step 8 Click OK.
Step 9 Click Close.
To configure the GNM Terminal using Windows XP platform
Step 1 From your Windows desktop, choose Start > Control Panel. The Control Panel window is dis-
played.
Step 2 Double-click Network Connections. The Network Connections window is displayed.
Step 3 Right-click Local Area Connection icon and select Properties. The Local Area Connection
Properties window is displayed.
Figure 3-5 Local Area Connection Properties: Windows XP
Step 4 In the Local Area Connection Properties window, select Internet Protocol (TCP/IP) and click
Properties. The Internet Protocol (TCP/IP) Properties window is displayed.

Page 7
Figure 3-6 TCP/IP Properties: Windows XP
Step 5 Select Use the following IP address button.

Step 6 Enter the IP address and Subnet mask and click Ok.
Note: Specifying the Default gateway is optional.
Step 7 In the Local Area Connection Properties window, click Ok to save the changes.
Step 8 Click OK.
Step 9 Click Close.
Testing the Connection
To ping the node IP address to test the connection
Step 1 Go to Start > Run and enter cmd and click OK.
Step 2 At the cmd prompt, enter the following command:
ping [Craft IP]
A message similar to the following is displayed:
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<10ms TTL=128

Page 8

If you do not receive a response, a network issue exists. Contact the Network Administrator to
identify and correct the issue.
LAN Connection
To access the target network element from a LAN, the IP address of the GNM terminal must be in the same
sub-net of the DCN IP address of the network element. The procedure is described under the following
headings:
 “Connecting the GNM Terminal to the LAN” on page 3-8
 “Configuring the GNM Terminal for LAN access” on page 3-8
Connecting the GNM Terminal to the LAN

The target network element must be physically connected to the LAN using a straight-through cable to a
hub or switch.
To connect the Ethernet cable from the GNM Terminal to the target network element
Step 1 Connect the male RJ-45 connector on one end of a standard Category 5 Ethernet cable to the
Ethernet port on your GNM Terminal.
Step 2 Connect the male RJ-45 connector on the other end of the Ethernet cable to the female RJ-45
connector labeled “DCN” on the MCM/OMM/XCM/IMM.
Configuring the GNM Terminal for LAN access

If you changed the GNM terminal network settings for direct access to the target network element, change
the settings back to the LAN access settings.
To configure the GNM Terminal
Step 1 From your Windows desktop, choose Start > Settings > Network and Dial-up Connections >
Local Area Connection. The Local Area Connection Status dialog box is displayed.
Step 2 Click Properties. The Local Area Connection Properties dialog box is displayed. See
Figure 3-3 on page 3-5.
Step 3 Select TCP/IP Protocol and click Properties.
Step 4 Set the IP Address on the TCP/IP Properties dialog box back to Obtain an IP address from a
DHCP server. If your LAN requires that DNS or WINS be enabled, change the setting on the
DNS Configuration or WINS Configuration tab of the TCP/IP Properties dialog box.

Page 9
Step 5 If your computer is connected to a proxy server, disable the proxy service or add the target net-
work element nodes as exceptions. See “To disable a proxy service using Internet Explorer” on
page 3-9 and “Remote Access” on page 3-9.
To disable a proxy service using Internet Explorer
Step 1 From your Windows desktop, choose Start > Settings > Control Panel.
Step 2 In the Control Panel window, select Internet Options. The Internet Properties window is dis-
played.
Step 3 On the Connections tab click Connections > LAN Settings. The Local Area Network (LAN)
Settings window is displayed.
Step 4 Do one of the following:
 De-select Use a proxy server for your LAN to disable the service.
 Leave Use a proxy server selected and click Advanced. On the Proxy Setting dialog box,
under Exceptions, enter the IP addresses of the nodes that you will access. Separate each
address with a semicolon. To include all nodes on your network, insert an asterisk for the
host number. Click OK to close each open dialog box.
Remote Access
LAN modems can be used to access target network elements from remote sites. The modem port is
located on the I/O panel of the target network element. The LAN modem connected to the target network
element must be properly configured. When the modem is installed, dial-up access to the target network
element is available using a PC or Solaris workstation modem.
Connectivity over DCN

The DTN-X, FlexROADM, Optical Amplifier, DTN and Optical Line Amplifier network elements provide
remote access through the customer DCN. The GNM Terminal can be connected to the network element
through the customer DCN. The GNM Terminal must be properly configured to access the network
element. The network element can be connected to the customer DCN using Ethernet cable.
See Infinera DTN and DTN-X Turn-up and Test Guide for the procedure to configure a node as a GNE or a
SNE.
Configuring Custom Cache Directory

The Infinera GNM cache directory can be optionally configured by the user. Configuring the cache
directory enables storing cache in the specified location. In case the user chooses not to configure this
manually, the cache is stored in the default directory,
 If Infinera GNM is launched from a Windows machine, the default cache directory is:

Page 10
C:\Documents and Settings\<user_name>\Application Data\Sun\Java\Deployment\cache\Infin-

era\cache
 If Infinera GNM is launched from a Solaris machine, the default cache directory is:
$<user.home>/.java/deployment/cache/Infinera/cache
 If Infinera GNM is launched from a Linux machine, the default cache directory is:
~/.java/deployment/cache/Infinera/cache
 If Infinera GNM is launched from a Macintosh machine, the default cache directory is:
/Users/<username>/Library/Caches/Java/cache/Infinera/cache
To configure the custom cache directory
Step 1 Ensure that the appropriate version of Sun Java Runtime Environment (JRE) is installed. See
“Java Web Start Requirements” on page 2-3 for more details.
Step 2 Navigate to the appropriate directory as mentioned below:
 In case of a Windows client: C:\Documents and Settings\<user_name>\Application
Data\Sun\Java\Deployment
 In case of a Solaris client: $<user.home>/.java/deployment
 In case of a Linux client: ~/.java/deployment/cache/Infinera/cache
 In case of a Macintosh client: /Users/<username>/Library/Caches/Java/cache/Infinera/

cache
Step 3 Include an entry in the deployment.properties file located in the above directories to
include the custom path for storing cache. The syntax is as mentioned below:
deployment.user.cachedir=<path_to_the_cache_directory>
For example, if the entry added to the deployment.properties file reads,
deployment.user.cachedir=C\:\\Cache, then the software cache will be stored in the Cache direc-
tory on the C drive.
Step 4 Save and close the deployment.properties file.

Page 11
Launching Infinera GNM

Before a connection to the target network element is established, ensure that the following applications are
installed on your machine:
 Sun Java Runtime Environment (JRE) is installed as recommended in “Java Web Start Require-
ments” on page 2-3
Known issues:
 Contact Infinera Customer Service and Technical Support for any updates to the above. See
“Technical Assistance” on page 1-15 for contact information.
 Verisign License Signature. The user is prompted to accept the license if it is not already accepted.
If you want to collect GNM logs, see “Retrieving GNM logs” on page 3-18 for a detailed procedure.
If you want to configure a custom directory for Infinera GNM cache, see “Configuring Custom Cache
Directory” on page 3-9 for a detailed procedure.
To launch Infinera GNM using Internet Explorer
Note: GNM Client launch aborts when an intermittent or sustained loss of network connectivity is
detected during the GNM Client initialization or JAR file download process. An error mes-
sage will be displayed.
Note: GNM Client launch may abort due to cache issues. An error message, indicating a fatal
error with recommendation to clear the GNM software cache will be displayed. In such
cases, click Abort in the error message window to abort the client launch and follow the
instructions in the procedure, “Clearing GNM Software Cache” on page 3-15 to clear the
cache and re-launch the client.
Step 1 Start one of the recommended browsers.

Step 2 If the target network element is a GNE, do the following:
Step 2a In the browser, type the DCN IP address of the target network element you want to
access.
Step 2b Infinera GNM is launched in a new window and the Login window is displayed. See
Figure 3-7.
Step 2c If you want to close the Login window, click Cancel.
Step 2d To log in, enter the following:
User Name—A unique identifier to identify the user. If logging in for the first time, the
default user name is secadmin.

Page 12
Password—The password that allows you to login to Infinera GNM. If you are log-
ging in for the first time, enter Infinera1.
Note: If you do not have a User name or Password, contact your System Administrator.
Step 2e Click Login. A Security Message is displayed.

Step 2f Click OK in the Security Message dialog box to continue.
If you are connecting to the target network element for the first time, Infinera GNM
prompts you to change your password. This is mandatory for all users.
Step 3 If the target network element is a SNE node, do the following:
Step 3a In the browser, type the DCN IP address of the GNE.
Step 3b Infinera GNM is launched in a new window and the Login window is displayed.
Step 3c Enter the following:
User Name—A unique identifier to identify the user.
ging in for the first time and your user name is any of the above, enter Infinera1.
Note: If you do not have a User name or Password, contact your system administrator.
Step 3d Click Login. A Security Message is displayed.

Step 3e Click OK in the Security Message dialog box to continue.
If you are connecting to the target network element for the first time, Infinera GNM
prompts you to change your password. This is mandatory for all users.
Step 3f In the Equipment View of the GNE, click on the Network Neighborhood.
Step 3g From the expanded Network Neighborhood, right click the required SNE and choose
Launch Graphical Node Manager.
Step 3h Infinera GNM is launched in a new window and the Login window is displayed.
Step 3i Enter the following:
User Name—A unique identifier to identify the user.
ging in for the first time, enter Infinera1.
Step 3j Click Login. A Security Message is displayed.
Step 3k Click OK in the Security Message dialog box to continue.

Page 13
Figure 3-7 Infinera GNM Login Window
Figure 3-8 Change Password
Note: In the Solaris environment, Infinera GNM must be launched on a Solaris console only. If
launched from any other application connected to the Solaris machine, the menu items will
overlap and will not be usable.
To change the password
Step 1 Enter the current password and new password as prompted.

Step 2 Click Apply to close the window. A Success Message is displayed.
Step 3 Click OK to continue. The Infinera GNM user interface is displayed.
Note: More than 3 attempts to log in with an invalid password locks the account for 60 seconds.
Further attempts to login during this period will not be successful. Hence wait 60 seconds
before attempting to log in again. These values are configurable by the Security Adminis-
trator.

Page 14
To launch Infinera GNM using Mozilla browser
Step 1 Launch the Mozilla web browser.

Step 2 In the browser, type the DCN IP address of the target network element to be accessed.
If the application to launch the JNLP file is not chosen before, a pop-up window, Opening
launchGnmCacheMgr window is displayed.
Figure 3-9 Opening LaunchGnmMgr window
Step 3 Do the following to choose the application to launch the JNLP file:
Step 3a In the Opening launchGnmCacheMgr window, select the Open with radio button.
Step 3b Click the field next to the Open with radio button and then select Other to launch the
Choose Helper Application window.
Figure 3-10 Choose Helper Application
Step 3c In the Choose Helper Application window, browse to the Java Web Start Launcher
and click OK.

Page 15
Step 3d [Optional] Select the check-box, Do this automatically for files of this form from
now on.
This will save the application to be used to launch the JNLP file.
Step 3e Click OK to launch the JNLP file and hence the GNM client.
The GNM login window is displayed.
Clearing GNM Software Cache

GNM client launch may abort due to cache issues. An error message, indicating a fatal error, with a
recommendation to clear the GNM Software cache is displayed. In such cases, click Abort in the error
message window to abort the client launch and complete the instructions to clear the cache and re-launch
the client.
This section provides detailed procedures to clear GNM cache:
 To clear the cache if it is stored in the default directory
 To clear the cache if a custom cache directory is configured, see “Configuring Custom Cache Direc-
tory” on page 3-9 for details on configuring the Infinera cache directory.
To clear the cache if it is stored in the default directory
Step 1 Execute the following command from the command prompt to launch the Java Cache Viewer
from the Java Control Panel:
javaws -viewer
The Java Cache Viewer with a list of applications is displayed.

Page 16
Figure 3-11 Java Cache Viewer
Step 2 Select the applications to be deleted from the cache and click the Remove Selected Items but-
ton.
Note: Use the Ctrl key to select multiple applications to be removed from the cache.
The selected applications are cleared from the cache.

Step 3 Click Close to close the Java Cache Viewer.
The Java Control Panel is displayed.
Step 4 Click Ok to exit the Java Control Panel.
Step 5 Navigate to the default directory where Infinera GNM cache is stored. The default directory is:
 For a Windows client: C:\Documents and Settings\<User_Name> \Application
Data\Sun\Java\Deployment\cache\Infinera\cache
 For a Solaris client: $<user.home>/.java/deployment/cache/Infinera/cache
 For a Linux client: ~/.java/deployment/cache/Infinera/cache
 For a Macintosh client: /Users/<username>/Library/Caches/Java/cache/Infinera/cache

 To clear the cache associated with a particular software build, select the appropriate directory
that is named by the software build and delete it.
 To clear the complete software cache on the client, select all the directories and delete them.

Page 17
To clear the cache if a custom cache directory is configured
Step 1 Navigate to the custom cache directory.

Step 2 Delete all the contents of this directory to clear the cache on the client.

Page 18
Retrieving GNM logs

Availability of GNM logs considerably reduce the time taken to resolve issues. Before launching Infinera
GNM for the first time, perform the following procedure if you want to enable GNM log capture.
To enable GNM log capture for JRE 1.6.0
Step 1 From your Windows desktop, choose Start > Settings > Control Panel > Java.
The Java Control Panel window is displayed.
Step 2 Choose the Advanced.
Step 3 Choose Debugging.
Step 4 Select Enable tracing to enable GNM log capture.
Step 5 Click Apply.
Step 6 Click OK.
The log files are automatically stored at C:\Documents and Settings\<user name>\Application
Data\Sun\Java\Deployment\log\. The log files are named as javaws<number>.trace.

CHAPTER 4
Software Maintenance
This chapter describes how to maintain the network element software and database using Infinera GNM
interface. It consists of these topics:
 “Overview” on page 4-2
 “Software and Database Maintenance Procedures” on page 4-6

Page 2
Overview
Infinera network elements provide the following capabilities to manage software and database images:
 “Downloading the Software” on page 4-2
 “Maintaining the Software” on page 4-2
 “Maintaining the Database” on page 4-4
Downloading the Software

The system software-IQ Networking Operating System, operating DTN-X, DTN, FlexROADM, Optical
Amplifier and Optical Line Amplifier network elements, is packaged into separate software images. The
software image includes the software components required for all the circuit packs in the DTN-X, DTN,
FlexROADM, Optical Amplifier and Optical Line Amplifier network elements.
You can remotely download the software image from a customer specified FTP server to the MCM circuit
pack of the DTN, OMM circuit pack of the Optical Amplifier, XCM circuit pack of the DTN-X and IMM circuit
pack of the FlexROADM and Optical Line Amplifier network element. Once you download the software
image to the MCM/OMM/XCM/IMM circuit pack and initiate the software upgrade procedure, it is
automatically distributed to the remaining circuit packs within the chassis. See “Maintaining the Software”
on page 4-2.
The network element can store up to two versions of the software image including the current version, at
the same time.
Maintaining the Software

The network elements support in-service software upgrade. The software upgrade procedure lets you
activate a different software version from the one currently active. The following software upgrade
operations are supported:
 Install New Software—This operation lets you activate the new software image version with an
empty database. The software image may be older or newer than the active version.
 Upgrade Software—This operation lets you activate the new software image version with the previ-
ously active database. The previously active database version must be compatible or migrateable
with the new software image version.
 Activate Software and Database—This operation lets you activate a new software image version
and a new database version. The database version and the software version must be the same to

Page 3
activate the software and database. Before you upgrade the software, you must download the new
database image to the network element.
 Restart Software with empty database—This operation lets you activate the current software
image with an empty database.
 Uncompress Software—This operation lets you uncompress the software image to enable faster
software upgrade.
In general, upgrading the software does not affect existing service. However, upgrading of certain
firmware, for example, TAM FPGA that is not auto upgradable can be service affecting. Hence, proper
planning is recommended. If this occurs, you receive a warning message.
You must upgrade the 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.
When you initiate a software upgrade, the procedure:
1. validates the uncompressed software image. If the software image is invalid, the upgrade proce-
dure is not allowed.
2. uncompresses the software image. If there is not enough memory on the network element to store
the decompressed image, the upgrade procedure is aborted and software image reverts to the pre-
viously active software image version.
3. 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.
4. When the new software image is activated, the software upgrade procedure updates the format of
the Event Log and Alarm Manager, 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. Hence, before you upgrade the soft-
ware, 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.
In the FlexROADM, DTN-X, DTN, Optical Amplifier and Optical Line Amplifier network elements, the
software upgrade is also supported when there is only one management card (IMM circuit pack of the
ROADM and Optical Line Amplifier, MCM in the DTN, OMM in the Optical Amplifier and XCM in the DTN-
X) circuit pack in the Main Chassis. In the Infinera ATN, the AMM must be present for any software
operation. During the upgrade process, the communication with clients and with other network elements
within the network is lost.

Page 4
Maintaining the Database

To ensure that the correct database is activated on a network element, the database image includes this
information:
 The database version. This is used to check its compatibility with the software image version.
 The backplane ID of the network element on which the database was created. This is used to ensure
that the database is only activated on the network element on which it was originally created.
The following database operations are supported:
 “Downloading the Database” on page 4-4
 “Backing up the Database” on page 4-4
 “Restoring the Database” on page 4-5
Downloading the Database

You can download the previously backed up database file to the network element from a specified FTP
server. The downloaded database file does not change the current active database. It is simply stored in
the persistent memory of the network element. Infinera network elements can store up to three database
versions (including current) at a time.
Backing up the Database

There are two database backup modes:
 Manual Database Backup—You can manually backup the current database image to the specified
FTP server at any time.
 Scheduled Database Backup—You can schedule the database to be backed up automatically, at
either daily or weekly intervals. You 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.
Note: It is not recommended to perform any provisioning-related activities on a network element

when a database backup operation is in progress. New provisioning requests may be
rejected by the network element until the database backup operation is complete.
In both cases, the current active database is backed up, not any previously saved database files. In the
case of a multi-chassis system, a database backup operation is restricted to the active MCM/XCM on the
Main Chassis. For a system with redundant controllers, a database backup operation is restricted to the
active MCM/XCM.

Page 5
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
Restoring the Database

You can perform the restore operation to activate a new database image file with the current active
software image version. The new database image file and the software image version must be of the same
version. The restore operation restarts the network element and activates the new database image. You
can restore the database at system reboot time or at any time during normal operation.
If the restore operation fails, the software rolls back to the previously active database image and an alarm
is raised indicating the failure of the restore operation. When the database is successfully restored, the
alarm is cleared. You can manually restore the database.
Depending on the differences between the two databases, the database restore operation could affect
service. The database restoration procedure restores the configuration data as per the restored database.
The configuration data in the restored database may differ from the current hardware configuration. In
such scenarios, in general, the configuration data takes precedence over the hardware.

Page 6
Software and Database Maintenance

Procedures
Infinera GNM provides these tools to maintain the DTN, DTN-X, FlexROADM, Optical Amplifier and Optical
Line Amplifier network elements:
 SW-DB Upload/Download Manager (see “SW-DB Upload/Download Manager” on page 4-6)
 SW-DB Manager (see “SW-DB Manager” on page 4-15)
SW-DB Upload/Download Manager

The SW-DB Upload/Download Manager tool allows a user with network administrator privilege to perform
these procedures:
 “Downloading the Software Image” on page 4-7
 “Downloading the Configuration Database” on page 4-8
 “Backing up the Configuration Database” on page 4-9
 “Uploading Debug Information” on page 4-11
To invoke the SW-DB Upload/Download Manager tool
Step 1 Log into the network element with network administrator privilege.
Step 2 Select Tools > SW-DB Upload/Download Manager.The SW-DB Upload/Download Manager
window is displayed.

Page 7
Figure 4-1 SW-DB Upload/Download Manager Window
Downloading the Software Image

Use this procedure to download the software image from a specified FTP server to the MCM circuit pack of
the DTN/IMM circuit pack of the FlexROADM and Optical Line Amplifier/OMM circuit pack of the Optical
Amplifier/AMM circuit pack on the ATN network element or the XCM of the DTN-X network element. The
software image download does not change the active software version.
To download the software image to the network element
Note: You can store up to two software image versions (including current) in the network element.
Make sure there is sufficient space in the network element before downloading.
Note: For this procedure, there must be DCN connectivity to the FTP server.

Page 8
Step 1 Invoke the SW-DB Upload/Download Manager tool as described in “To invoke the SW-DB
Upload/Download Manager tool” on page 4-6. The SW-DB Upload/Download Manager window
is displayed.
Step 2 From the table, select Download SW Image operation.
Step 3 In the FTP Setup panel, specify the primary FTP or/and secondary FTP server information,
including:
 IP address of the primary and secondary FTP servers.
 User Name—Enter the user name.
 Password—Click Set. The Set Password window is displayed.

Enter and Confirm the password. Click Apply.
 Change the SFTP Port in the SFTP Port field, if required.
The SFTP Port is set to 22 by default and can range from 1-65535.
Step 4 In the FTP Transfers panel select Enabled.
Step 5 In the File Specification panel, specify:
 Path—Directory on the server where the software image file is located
 File Name—Name of the software image file to be downloaded.

Step 6 Click Apply.
Step 7 In the Download Settings panel, click Transfer Now to start the transfer. A success message is
displayed. Click Ok.
Depending on the link speed, it may take several minutes to complete the transfer. The Current
Transfer information in the Current/Last Attempt Details panel provides the transfer status. When
the transfer is complete, the Status(Primary) and Status(Secondary) fields indicate if the soft-
ware image was successfully downloaded from the primary and secondary FTP servers, respec-
tively.
Step 8 When you are done, click Close to exit SW-DB Upload/Download Manager.
Downloading the Configuration Database

You can download the previously backed up configuration database file (see “Backing up the Configuration
Database” on page 4-9) to the network element from a specified FTP server. Up to three database files can
be stored in the network element at a time. The downloaded database does not change the current active
database. It is simply stored in the persistent memory of the network element.
To download the database file to the network element
is displayed.
Step 2 From the table, select Download Config DB operation.

Page 9
including:
 FTP server address where the database file is located
 User ID and password to log into the FTP server

Click Set. The Set Password window is displayed.
Step 4 In the FTP Transfers panel, select Enabled.
 Path—Directory on the server where the database file is located
 File Name—Name of the database file to be downloaded.

Step 6 Click Apply.
Step 7 In the Download Settings panel, click Transfer Now to start the transfer. A success message is
The Current Transfer information in the Current/Last Attempt Details panel provides the transfer
status. Once the transfer is completed, Status(Primary) and Status(Secondary) fields indicates
if the database file was successfully downloaded from the primary and secondary FTP servers,
respectively.
Backing up the Configuration Database

There are two database backup modes:
 Manual Database Backup—You can manually backup the current database image at any time. The
current database image can be transferred to a specified FTP server (see “To back up the database
to an external server” on page 4-10) or can be stored locally on the network element (see “To back
up the active database image on the network element” on page 4-25).
 Scheduled Database Backup—You can schedule the database to be backed up automatically, at
either daily or weekly intervals. You can also specify a primary and secondary FTP server to receive
the backup. 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.The daily backup is automatically
triggered at 00hrs every day; the weekly backup is triggered at 00hrs every Sunday.
In order to prevent all network elements from transferring the database backup file at the same time,
Infinera GNM starts the transfer at xfrScheduleOffset seconds after the 00hrs. The xfrScheduleOff-
set value ranges from 0 to 60 seconds and is derived randomly in each network element.

Page 10
To back up the database to an external server
Note: Make sure the user ID has write permission in the directory where the database file is
uploaded and there is sufficient space on the server.
is displayed.
Step 2 From the table, select Backup Config DB operation.
including:
 FTP server address where the database file will uploaded
 User ID and password to log into the FTP server

Step 4 In the FTP Transfers panel do the following:
Step 4a Select Enabled.
Step 4b Select Simultaneously Upload Enabled to simultaneously upload Config DB to two
FTP destinations.
 Path—Directory into which the database file is backed up. The path can have a maximum of
256 characters.
Note: Both relative and absolute paths can be mentioned in combination with supported tokens. If
no path is specified, by default, the database file is backed-up to the home directory of the
user.
 Name Format—The format of the backed up database file. To specify the file name, the
tokens %M (network element name) and %D (date and time) are supported. A default file
name DB_%D is assigned, where %D is the token for the date and time at which the database
is backed up. You can replace the file name prefix DB with any name of your choice. The file
name can have a maximum of 48 characters when the tokens are expanded including the
extension .tar.gz. The network element validates for special characters such as
:@,$&"#* ()/\?;. These special characters are not supported in file names.
Note: There is a possibility that the backups from multiple network elements stored in the same
directory on the server may overwrite each other. Make sure that each network element is

Page 11
assigned a different directory on the server. Alternatively, append the network element’s
node name to the backed up database file name.
 Overwrite file—Check Overwrite file to overwrite the existing file.

Step 6 Click Apply.
Step 7 In the Upload Schedule panel, do one of the following:
 To backup the database manually anytime, select Unscheduled from the drop down menu
and click Transfer Now. A success message is displayed. Click Ok.
 To schedule the backup of database, choose Daily if you want automatic daily backup or
choose Weekly if you want weekly backup. Click [...] to set the date and time of upload.
Click Apply.
The Current Transfer information in the Current/Last Attempt Details panel provides the sched-
ule status. If the backup has been scheduled successfully, the Status field indicates Scheduled.
Note: In order to prevent all network elements from transferring the database backup file at the
same time, Infinera GNM starts the transfer at xfrScheduleOffset seconds after the config-
ured date and time. The xfrScheduleOffset value ranges from 0 to 60 seconds and its value
is derived randomly in each network element.
Uploading Debug Information

If there is a software crash, the network element stores core dump files as well as pertinent debug
information which is preserved over restart. This information is used by Infinera Technical Support for
failure analysis. You must specify the primary and secondary FTP server to which the debug information
must be uploaded. By default, the debug information is uploaded to the primary FTP server; however, if
that server is not available, the debug information is uploaded to the secondary FTP server. This
information is uploaded in a tar.gz file format.
There are two methods to upload the debug information:
 Automatic Upload—The basic debug information (FDR details) is uploaded automatically to the
specified FTP server. This upload is triggered within one hour after a successful reboot of the active
MCM/XCM or a successful switchover.
 Manual Upload—The debug information can be manually uploaded to the specified FTP server at
any time. This method can be used when any line cards or cards on the Expansion Chassis crash.
The AID of the equipment for which the detailed debug information is to be uploaded can be speci-
fied. Refer to the Infinera GNM Configuration Management Guide for a list of equipment with valid
AID formats that are supported by this application.

Page 12
To enable automatic upload of network element debug information
Note: Make sure the user ID has write permission in the directory where the debug file is
is displayed.
Step 2 From the table, select Upload Debug Info operation.
The AID option in the Debug Commands panel is enabled.
including:
 FTP server address where the database file will be uploaded to.
 User ID and password to log into the FTP server.

Step 4 In the Debug Commands panel, do the following:
 Enter values for AID.
The AID list specifies the managed objects for which the debug information is collected and
uploaded. Use the wildcard character ‘&’ to upload debug information for more than one man-
aged object. A maximum of three AIDs can be specified. If no AID is specified in the AID List
field, the basic debug information is collected for all cards that are reachable. See Table 4-1
on page 4-16 for the list of valid equipment AIDs.
 Select the Filter, the valid values are:
 Default—For XTC line modules, only the most recent 1000 records are retrieved from the
DSP Flight Data Recorder (FDR); for a node controller (XCM/IMM/MCM/OMM), only lim-
ited GMPLS data is retrieved. This default mode minimizes the amount of time required
for debug file transfer from the node.
 Complete LM DSP FDR—For retrieving debug information from the XTC line modules,
the user can specify that all DSP FDR records are to be retrieved (not just the latest 1000
records). (For GMPLS data, the default/limited data is retrieved as with default setting.)
 Complete GMPLS Data —For retrieving debug information from the XCM/IMM/MCM/
OMM node controller, the user can specify that all GMPLS data is to be retrieved (i.e.,
topology nodes, TE links, control links, backplane connectivity, and tributary/ line payload
capacity). (For XTC line module data, the default 1000 DSP FDR records are retrieved as
with default setting.)

Page 13

 Path—Directory into which debug file is uploaded. The path can have a maximum of 256
characters.
no path is specified, by default, the database file is uploaded to the home directory of the
user.
 Name Format—The format of the uploaded debug file. A default file name debuginfo_%D
is assigned, where %D is the token for the date and time at which the debug information is
uploaded. You can replace the file name prefix debuginfo with any name of your choice.
The file name can have a maximum of 48 characters when the tokens are expanded includ-
ing the extension .tar.gz. The network element validates for special characters such as
assigned a different directory on the server.
Step 7 Click Apply.

To monitor the transfer status, click the Current/Last Attempt Details panel.
status. When the transfer is complete, the Status(Primary) and Status(Secondary) fields indi-
cates if the database file was successfully uploaded to the primary and secondary FTP servers,
respectively.
Click the Last Successful Upload/Download panel to view details of the last successful
upload/download operation.
To upload network element debug information manually
Note: Make sure the user ID has write permission in the directory where the debug file is
Upload/Download Manager tool” on page 4-6. The SW-DB Upload/Download Manager win-
dow is displayed.
Step 2 From the table, select Upload Debug Info operation.
The AID option in the Debug Commands panel is enabled.
including:

Page 14
 FTP server address where the database file will be uploaded to.
 User ID and password to log into the FTP server.

Step 4 In the Debug Commands panel, enter values for AID. The AID list specifies the managed
objects for which the debug information is collected and uploaded. Use the wildcard character ‘&’
to upload debug information for more than one managed object. A maximum of three AIDs can
be specified. If no AID is specified in the AID List field, the basic debug information is collected
for all cards that are reachable.
 Path—Directory into which debug file is uploaded. The path can have a maximum of 256
characters.
no path is specified, by default, the database file is uploaded to the home directory of the
user.
 Name Format—The format of the uploaded debug file. A default file name debuginfo_%D is
assigned, where %D is the token for the date and time at which the debug information is
uploaded. You can replace the file name prefix debuginfo with any name of your choice.
The file name can have a maximum of 48 characters when the tokens are expanded includ-
ing the extension .tar.gz. The network element validates for special characters such as
assigned a different directory on the server.
Step 7 Click Current/Last Attempt Details panel to monitor the transfer status.
Step 8 In the Upload Schedule panel, click Transfer Now to start the transfer. A success message is
status. When the transfer is complete, the Status(Primary) and Status(Secondary) fields indi-
cates if the database file was successfully uploaded to the primary and secondary FTP servers,
respectively.
Click the Last Successful Upload/Download panel to view details of the last successful upload/
download operation.

Page 15
SW-DB Manager
The SW-DB Manager tool lets a user with network administrator privilege perform these procedures:
 “Installing New Software” on page 4-18
 “Upgrading the Software” on page 4-19
 “Activating Software and Database Images” on page 4-23
 “Restarting the Software with empty database” on page 4-24
 “Restoring the Database” on page 4-24
 “Backing up the Database Image Locally” on page 4-25
 “Deleting an Unused Software or Database Image” on page 4-26
 “Compressing the Software or Database Image” on page 4-26
Note: Before you perform any software and database maintenance operations, make sure that
there are no more than three database images (including current) stored in the network
element.
To invoke SW-DB Manager tool
Step 1 Log into the network element with network administrator privilege.
Step 2 Select Tools > SW-DB Manager. The SW-DB Manager window is displayed.

Page 16
Figure 4-2 SW-DB Manager Window
The SW-DB Manager window displays the software images and database files stored in the network
element. Table 4-1 on page 4-16 describes the software image information. Table 4-2 on page 4-17
describes the database file information.
Table 4-1 Software Images Panel Attributes
Item Description
SW Version Software release number.

Usage Status The software database status. Valid values can be one of the following:
• Current—This software image is currently active.
• Backup—This software image version is older than the active software
image version.
• Upgrade—This software image is available for upgrade
Validity The validity of the software image. Valid values can be one of the follow-
ing:
• Good—Software image is valid.
• CRCFailed—The CRC check failed on the software image.
• FilesMissing—The software image has some missing files.
• Unknown—The software image is invalid for unknown reasons.
Type The type of the software image. This field takes the value Digital.

Page 17
Table 4-1 Software Images Panel Attributes
Item Description
Format The format in which the software is stored. Valid values can be one of the
following:
• Compressed—Software image is compressed.
• Normal—Software image is uncompressed.
SpaceUsed(Kb) The amount of space in kilobytes, used by this software version.
Created The date and time the software image was created. This is generated by
the system.
Table 4-2 Database Images Panel Attributes
Item Description
DB Name Database file name.

Usage Status Software image status. Valid values can be one of the following:
• Current—Indicates this database image is currently active.
• Backup—Previously backed database image.
Version Release version number.
Compatible with Indicates whether this database version is compatible with the software
selected SW? image version selected in the SW Images panel.
Format The format in which the database file is stored. Valid values can be one
of the following:
• Compressed—Database file is compressed.
• Normal—Database file is uncompressed.
Validity The validity of the database file. Valid values can be one of the follow-
ing:
• Good—Database file is valid.
• CRCFailed—The CRC check failed on the database file.
• FilesMissing—Files in the database image are missing.
• Unknown—The database image is invalid for unknown reasons.
Branded NodeId Unique network element identifier from where the database file was
originally created.
Space Used (Kb) The amount of space (in kilobytes), used by this database version.
Created The date and time the database version was created. This is generated
by the system.
Last Backed Up The date and time the database was backed up.

Page 18
Installing New Software

Use this procedure to activate a new software image version with an empty database. You must download
the new software image to the network element using the procedure described in “Downloading the
Software Image” on page 4-7.
Note: Installing a new software with empty database is traffic affecting. Do not attempt to reboot
the system while it is coming up with an empty database. This may corrupt the database
and cause the MCM/OMM/XCM/IMM to reboot repeatedly.
Note: The new software image version may be older than or newer than the active software ver-
sion.
To install the new software image
Step 1 If the chassis is equipped with MCMs/OMMs/XCMs/IMMs in the redundant configuration, right-
click the stand-by (stby) MCM/OMMs/XCMs/IMMs and select Admin State > Lock.
Step 1 Invoke the SW-DB Manager tool as described in “To invoke SW-DB Manager tool” on page 4-15.
The SW-DB Manager window is displayed.
Step 2 [Optional]In the SW Images panel, right-click the software image that you want to install and
choose Uncompress. Uncompressing the software images saves time when the new software
image is to be installed.
Step 3 In the SW-DB Manager window, do one of the following:
 In the SW Images panel, right-click the software image that you want to install and choose
Fresh Install. A warning message Fresh Install will activate the selected SW
Image and start with empty DB. Do you want to continue? is displayed.
 In the SW Images panel, select the software image that you want to install and click Fresh
Install button. A warning message Fresh Install will activate the selected SW
Image and start with empty DB. Do you want to continue? is displayed.
Step 4 Click Fresh Install. A success message is displayed.

Page 19
Step 5 Click Ok. The network element is rebooted. It takes a few minutes for the network element to
reboot. Infinera GNM loses connectivity to the network element.
Note: Because the software is new and the database is empty, you need to reconfigure the net-
work element. Use the default user ID and password to log into the network element.
Note: Performing the Fresh Install operation on a SNE, results in the GMPLS information being
lost. This results in loss of connectivity to management interfaces GNM, DNA and TL1.
Refer to the Infinera DTN and DTN-X Turn-up and Test Guide to re-configure the SNE.
Note: If the database image with the same name as that of the software image exists on the net-
work element, the Fresh Install operation will be rejected by displaying an appropriate error
message.
Note: Any software image that was previously uncompressed, will be stored in a compressed for-
mat after a successful install.
Upgrading the Software

Use this procedure to activate a new software image version with the current active database. The active
database version must be compatible with the new software image version. You must download the new
software image to the network element using the procedure described in “Downloading the Software
Image” on page 4-7.
To upgrade the software image
Note: When upgrading to Release 9.0 for network elements that are provisioned with restorable
SNCs with OTU2 Clear Channel service type, do one of the following:
Upgrade both the head-end and tail-end network elements for the OTU2 Clear Channel
service at the same time.
or
Before upgrading to Release 9.0, change all OTU2 Clear Channel restorable SNCs to
non-restorable SNCs. After the upgrade, the SNCs can be changed back to restorable
SNCs.
In case of mixed scenario for manual cross-connect:
There is no impact on the OTU2-Clear Channel services created manually in Release
8.x.
New OTU2-Clear Channel services will not come up if head-end and tail-end have a mix
of Release 8.x and Release 9.x.

Page 20
In case of mixed Release scenario:

There is no impact to OTU2-Clear Channel services created using GMPLS in Release 8.x
unless there is a failure.
The service does not come up if there is a restoration due to failure.
New OTU2-Clear Channel services will not come up if head-end and tail-end have a mix
of Release 8.x and Release 9.x.
Note: During IQ NOS software upgrade in Optical Line Amplifier nodes, OMM flash requirement
reaches its peak (requires two software images to be in an uncompressed format plus an
additional Database being created for the Software Upgrade). This will result in a transient
alarm “available non-volatile memory low or very low alarm” being reported. The transient
alarm will clear automatically and it is not service affecting.
Note: Do not physically unseat a TAM-1-40GE or TAM-1-40GR when a firmware upgrade is in

progress.
Step 1 Ensure all expansion chassis on the network element being upgraded to Release 9.0 are reach-
able. If any of the expansion chassis is not reachable, the upgrade procedure will fail and the
Software Upgrade Failure alarm will be reported.
Note: If a chassis is physically installed and reachable (at least one MCM/XCM controller is
active), upgrade can be performed with pre-provisioned services and equipments.
Step 3 Verify the number of software images on the network element. From the Infinera DTN GNM main
view, select Tools > SW-DB Manager. The SW-DB Manager window is displayed.
Note: Up to two software images (including the current) can be stored on the network element.
Step 4 If two software images exist, select the image that is not in use (backup), right click and select
Delete. In the SW Images panel, ensure that the Usage Status attribute lists Backup. A warning
message is displayed.
Step 5 Click Delete.
Note: Verify any associated alarms before initiating the software download process.
Step 6 Download the appropriate software image using the SW-DB Upload/Download Manager. See
“To download the software image to the network element” on page 4-7 for detailed procedure.

Page 21
Step 8 From the SW-DB Manager window, verify the following two attributes (Validity and Compatible
with selected SW?) before proceeding to the next step:
 In the SW Images panel, Validity—Good
 In the DB Images panel, Compatible with selected SW?—Migrateable or Compatible

If either of the above attributes display different values, download the appropriate software
image using the SW-DB Upload/Download Manager. See “To download the software image to
the network element” on page 4-7 for detailed procedure.
Step 9 [Optional]In the SW Images panel, right-click the software image that you want to upgrade to
and choose Uncompress. Uncompressing the software images saves time when the software
image is to be upgraded.
Step 10 In the SW Images panel, select the software image that you would like to upgrade. The Usage
Status value must be Upgrade.
Step 11 Click Upgrade. The following message is displayed:
Upgrade operation started successfully. Node will reboot shortly for
changes to take effect.
Step 12 Click Ok. It will take some time for the network element to get fully upgraded to the new version.
Note: Once the network element upgrades to the new version, the software upgrade is complete.
This upgrade is not traffic affecting. Any software image that was previously uncom-
pressed, will be stored in a compressed format after a successful upgrade.
Note: For detailed traffic, FPGA upgrade, and operational effects associated with upgrading to a
specific software image version, refer to the applicable Software Release Notes.
To upgrade the firmware using Infinera GNM
Use this procedure to upgrade the FPGA firmware on a circuit pack using Infinera GNM.
Note: Infinera recommends that the current configuration database be backed up prior to per-
forming this procedure. Refer to the respective Infinera DTN Product Release Notes for
procedures to backup the network element database.
Note: Do not physically unseat a circuit pack when a firmware upgrade is in progress.
Step 1 Launch Infinera GNM, refer to “To launch Infinera GNM using Mozilla browser” on page 3-14.
Step 2 From the Infinera GNM main view, select Configuration > Equipment Manager. The Equip-
ment Manager window is displayed.

Page 22
Step 3 In the Filter drop down menu, select FW Upgrade Available. A list of hardware is displayed in
the table. Scroll to the right to see the hidden frames.
Step 4 In the Firmware field (under SA Upgrade), if Available is listed, this indicates that an FPGA
firmware version upgrade is available.
Note: Non-Service Affecting (NSA) firmware upgrades are automatically performed for all the cir-
cuit packs in DTN/DTN-X/FlexROADM.
Note: For DTN-X, sidekick upgrades take effect only when the circuit pack is cold rebooted or
reset and not performed automatically. However, FCP upgrade is automatically performed
when the software is upgraded.
Step 5 Verify that there are no new related alarms on any equipment requiring an FPGA firmware ver-
sion upgrade.
Step 6 Right click on a circuit pack requiring an FPGA firmware version upgrade. From the menu dis-
played, select Admin State. Click Maintenance.
Step 7 Right click on the circuit pack. From the menu displayed, select Reset. Click Cold.
Note: Except for MCM/OMM/XCM/IMM cards, a cold reset of any circuit pack is service affecting.
Step 8 Upon initiating a Cold Reset, the following message is displayed:

New Firmware version will be automatically downloaded upon cold
reset. This operation will affect the data traffic. Do you wish to
continue?
Click Continue. The circuit pack will now reboot; depending on the circuit pack configuration, it
will take several minutes for the reboot to complete.
Step 9 Right click on the circuit pack that has just rebooted. From the menu displayed, select Admin
State. Click Unlock.
Note: From the Infinera GNM main view, the circuit pack that has just rebooted will remain in a
Major (SA) alarm state (displayed in Orange) until the reboot is complete.
Step 10 Once the circuit pack has finished booting, it will be necessary to verify that the FPGA firmware
version upgrade completed successfully. From the Infinera GNM main view, select Configura-
tion > Equipment Manager. The Equipment Manager window is displayed.
Step 11 In the Filter drop down menu, select FW Upgrade Available. A list of hardware is displayed in
the table.
Step 12 The circuit pack that was just upgraded will no longer be listed in the FW Upgrade Available filter.
This indicates that the FPGA firmware version upgrade was successful.

Page 23
Note: If the upgrade was not successful, contact Infinera Technical Support.
Step 13 Repeat Step 2 through Step 12 for all circuit packs requiring an FPGA firmware version upgrade.
Activating Software and Database Images

Use this procedure to activate a software image version as well as a compatible database image. The
software image and the database image version must be the same. You must download the required
software and database images to the network element using the procedures described “Downloading the
Software Image” on page 4-7 and “Downloading the Configuration Database” on page 4-8.
To activate software and database images
Step 3 In the SW Images panel, select the software image you want to activate.
Step 4 [Optional]Right-click and choose Uncompress. Uncompressing the software images saves
time when the software image is to be activated.
Step 5 In the DB Images panel, select the database image you want to activate. The Compatible with
selected SW? value must be Compatible or Migratable.
Step 6 Click Activate SW & DB. A warning message This action will restart the Node
with the selected SW Image and force it to use the selected DB Image
instead of the currently running DB. Do you want to continue? is displayed.
Note: To see the Activate SW & DB option, you must select the correct software and database
images.
Step 7 Click Activate SW & DB. A success message is displayed.

Step 8 Click Ok. The node is rebooted. It takes a few minutes for the network element to reboot. Infin-
era GNM loses connectivity to the network element.
Note: Any software image that was previously uncompressed, will be stored in a compressed for-
mat after the software image and database image have been successfully activated.

Page 24
Restarting the Software with empty database

Use this procedure to restart the current software image with an empty database.
Note: Restarting the current software image with an empty database is traffic affecting.
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 MCM/OMM/XCM/IMM to re-boot repeatedly.
To restart the current software image
Step 3 In the SW Images panel, select the current active software image. The Usage Status value
must be Current.
Step 4 Click Restart with empty DB.... A warning message This action will delete the cur-
rent running database and restart the NE. This will bring down the traf-
fic running through this node. This will also bring down the
communication to and away from this node. Do you want to proceed with
this operation? is displayed.
Step 5 Click Restart with Empty DB. A success message is displayed.
Step 6 Click Ok. The node is rebooted. It takes a few minutes for the network element to reboot. Infinera
GNM loses connectivity to the network element.
Note: Because the software is restarted with an empty database, you need to reconfigure the net-
work element. Use the default user ID and password to log into the network element.
Restoring the Database

Use this procedure to restore a previously backed up database image. The database image must be
downloaded to the network element (“Downloading the Configuration Database” on page 4-8).
To restore a database

Page 25
Step 2 In the SW Images panel, select the current active software image. The Usage Status value
must be Current.
Step 3 In the DB Images panel, select the database image you want to activate. The Compatible with
selected SW? value must be Compatible/Migratable.
Step 4 Click Restore DB. A warning message Restore DB operation will restore config-
uration and reboot the node. Do you want to continue? is displayed.
Step 5 Click Restore. A success message is displayed.
Step 6 Click Ok. The node is rebooted. It takes a few minutes for the network element to reboot. Infin-
era GNM loses connectivity to the network element.
Note: When an SNC is restored along an alternate path, note that the network elements associ-
ated with the SNC (including the local, remote, and intermediate network elements used
for the alternate path as well as those used for the original path) will have updated their
Cross-connect databases. However, until a backup operation is performed, the backup
databases on these network elements will not contain information for the restored alternate
path of the SNC. This must be taken into consideration before performing a database res-
toration on any of these network elements. Traffic will be affected if an older database is
restored after an SNC auto restoration has occurred.
Backing up the Database Image Locally

Use this procedure to save a backup copy of the active database locally on the network element.
Note: You can have a maximum of two software images including the current image and three
database images including the current image, on the network element. If there are more
than the permissible number of software and database images, you cannot perform any of
the software and database upgrade operations.
To back up the active database image on the network element
Step 2 In the DB Images panel, select the current active database image. Make sure the Usage Status
is Current.
Step 3 Click Take Local Backup. A warning message is displayed.
Step 4 Click Backup. A success message is displayed.
Step 5 Click Ok. The database backup file is created and displayed in the DB Images panel.
Step 6 When you are done, click Close to exit SW-DB Manager.

Page 26
Deleting an Unused Software or Database Image

Use this procedure to delete an unused software or database image on the network element. You cannot
delete an active software or database image.
To delete a software or database image
 To delete a software image, in the SW Images panel, select the software image you want to
delete.
 To delete a database image, in the DB Images panel select the database image you want to
delete.
Step 3 Right-click and select Delete. A warning message is displayed.
Step 4 Click Delete. A success message is displayed.
Step 5 Click Ok.
Compressing the Software or Database Image

Use this procedure to compress a software or database image stored in the network element.
To compress the software or database image
 To compress the software image, in the SW Images panel, right-click the software image you
want to compress and choose Compress.
 To compress the database image, in the DB Images panel, right-click the database image
you want to compress and choose Compress.

CHAPTER 5
Exploring the User Interface
Infinera GNM provides a graphical user interface to access and manage Infinera DTN-Xs, DTNs,
FlexROADMs, Optical Amplifiers and Optical Line Amplifiers.This chapter provides an overview of the
Infinera GNM user interface and provides information on how to use it, in the following sections:
 “Infinera GNM Interface Components” on page 5-2
 “Infinera GNM GUI Conventions” on page 5-23
Note: Unless specifically noted otherwise, all references to "line module" will refer interchange-
ably to either the DLM, XLM, ADLM, AXLM, SLM, AXLM-80, ADLM-80 and/or SLM-80
(DTC/MTC only) and AOLM, AOLM2, AOLX, AOLX2, SOLM, SOLM2, SOLX, SOLX2,
AOFM, and/or AOFX (XTC only). The term "LM-80" is used to specify the LM-80 sub-set of
line modules and refers interchangeably to the AXLM-80, ADLM-80 and/or SLM-80 (DTC/
MTC only). Note that the term "line module" does not refer to TEMs, as they do not have
line-side capabilities and are used for tributary extension.
Note: In previous software releases, a node with an OTC as the Main Chassis (i.e. OMM as the
node controller module) was referred to in the documentation as an "Optical Line Amplifier"
node. Note that the management interfaces have always referred to this node type as an
"Optical Amplifier". Starting in Release 10.0, the customer documentation is updated to
match the terminology of the management interfaces, wherein a node with an OTC Main
Chassis is called an "Optical Amplifier" and a node with an MTC-9 Main Chassis (i.e. IMM
as the node controller module) configured with IAMs/IRMs is now called an "Optical Line
Amplifier". Note that an MTC-9 Main Chassis configured with FRMs is called a Flex-
ROADM node, to support optical multiplexing.

Page 2
Infinera GNM Interface Components

On a successful login to the network element, the GNM Main View is displayed. The GNM Main View for a:
 DTN-X is shown in Figure 5-1 on page 5-2
 DTN is shown in Figure 5-2 on page 5-3 and
 Optical Amplifier is shown in Figure 5-3 on page 5-4.
 FlexROADM is shown in Figure 5-3 on page 5-4

 Optical Line Amplifier is shown in Figure 5-5 on page 5-6
The GNM Main View displays a graphical representation of the network element being managed and the
access to equipment, facilities and tools used to control and monitor the network element.
Figure 5-1 GNM Main View for DTN-X

Page 3
Figure 5-2 GNM Main View for DTN

Page 4
Figure 5-3 GNM Main View for Optical Amplifier

Page 5
Figure 5-4 GNM Main View for FlexROADM

Page 6
Figure 5-5 GNM Main View for Optical Line Amplifier
The GNM Main View consists of the following components:

 Infinera GNM Main Menu—“Infinera GNM Main Menu” on page 5-7
 Equipment Tree—“Equipment Tree” on page 5-8
 Workspace Area—“Workspace Area” on page 5-9
 Rack View—“Rack View” on page 5-9
 Equipment View—“Equipment View” on page 5-10
 Quick View Browser—“Quick View Browser” on page 5-16
 Alarm Manager—“Alarm Manager” on page 5-16
 Status Bar—“Status Bar” on page 5-17
 Slide Bar— “Slide Bar” on page 5-17

Page 7
Infinera GNM Main Menu

The Infinera GNM Main Menu contains commands that are grouped together and displayed in the main
menu bar. Table 5-1 lists the menu options in the Infinera GNM Main Menu.
Table 5-1 GNM Main Menu Options
File Fault Management Configuration Provisioning
• Exit • Alarm Manager • Network Element... • Cross-Connect Manager

• Event Log • Create Chassis • Circuit Manager
• Export All Alarms To • Create Protection Group... • Lightpath Manager
File • Create UNI Neighbor • UNI TE Link Manager
• Export All Events To • Create UNI TE Link • Create Digital Cross-Connect
File
• Equipment Manager • Create Digital Circuit
• Export Current View of
Alarms To File • Facility Manager • Create Optical Cross-Connect
• Export Current View of • Protection Group Manager • Create Optical Circuit
Events To File • Link Manager
• Alarm Severity Profile • Back Plane Link Manager
Settings
• Static Route Manager
• Customize Alarm Set-
• UNI Neighbor Manager
tings
• Default Templates
Security Tools Window Help
• Change Password • SW-DB Manager • Cascade • Contents

• NE Security Administration • SW-DB Upload/Download • <NE Name> • Technical Support
• Active User Sessions Manager • About
• IP Security Manager • PM Upload Scheduler
• NE-Wide Security Settings • Connectivity Verification Tools
• Regenerate SSH Keys • SNMP Configuration

• TL1 Session
• Save Preferences
• Reset Preferences
• View
• Alarm Troubleshoot

Page 8
Keyboard Accelerators
Frequently used commands have keyboard shortcuts. To access commands using these keyboard
shortcuts, press Alt+<underlined letter in the menu option>. For example, to access the Provisioning
menu, hold the Alt key and press P.
Equipment Tree
The Equipment Tree is located at the top left side of the GNM Main View. It provides a hierarchical view of
all the equipment contained within the target network element, and a list of all other nodes in the same
signaling domain. When an object in the Equipment Tree is selected the corresponding object is outlined in
the Equipment View. Right-click options on objects in the Equipment Tree is supported wherein, a context-
based menu is displayed to perform various operations depending on the access privileges of the user;
some operations may be disabled, and appear in grey text.
The Equipment Tree displays a tree structure of the following:
 Current Network Element View
The Current Network Element View displays the target network element and its sub-equipment. It
lists the network element’s chassis and other contained equipment in hierarchical format. See
Figure 5-6 on page 5-9. The equipment tree can be expanded and collapsed as desired.
 Network Neighborhood View
The Network Neighborhood View lists the network elements within the same signaling domain of the
target network element. Users can launch separate instances of Infinera GNM to manage neighbor-
ing network elements by right-clicking on the network element icons. Every new instance of Infinera
GNM requires the user to log in and is launched in a separate Web browser window. Unreachable
network elements are not displayed in the Network Neighborhood View.
Expanding the Equipment Tree

This section describes how to expand and collapse icons to selectively view equipment within the network
element.
To expand the tree structure to show more levels of equipment
 Select the network element name, and click the expand button to expand the tree. Figure 5-6 on
page 5-9 shows the expanded view of the tree.

Page 9
Figure 5-6 Expanded Equipment Tree
Workspace Area
The Workspace Area is located at the top right side of the GNM Main View. The Workspace Area displays
the Equipment View and the other inventory tools such as Facility Manager, Equipment Manager, Cross-
Connect Manager, Protection group Manager, and Circuit Manager. The following sections describes each
of the applications that can be displayed within the Workspace Area.
Rack View
The Rack View is displayed in the Workspace area when a user successfully logs into a network element.
The Rack View displays the rack view of all chassis comprising the network element. It displays the
location of the chassis within a node.
The Rack View displays the following information:
 The name of the rack. Chassis are grouped according to the rack name. A maximum of two chassis
can be in a rack. If no rack name is entered, no rack name is displayed. If multiple chassis have
the same rack name, the chassis are displayed in two racks.
 The chassis label. If no label is entered for a chassis, nothing is displayed.
 The chassis number at the top right corner. Chassis are sorted and placed using the RU Location
in Rack attribute of chassis configured from the Chassis Properties dialog. Chassis are first
grouped using the rack name and inside the same group stacked from bottom to top using the RU
Location in Rack attribute. If this attribute is not provided or equal then the chassis number is
used
 The Node Controller chassis is indicated by a * next to the chassis number. The rack with the Node
Controller chassis is displayed first followed by the other racks.
 The maximum severity color of the chassis or any equipment and (or) facilities is displayed on the
chassis panel.

Page 10
 The maximum severity color of the chassis object is displayed on the chassis icon
The Rack View displays the maximum alarm severity as per the color scheme described in Table 5-2 on
page 5-10.
Table 5-2 Alarm Severity Color on the Rack View
Color/Imagea Description
Light Grey No alarms are reported on the chassis or equipment and/or facilities in the chassis
Red The chassis has at least one critical alarm
Orange The chassis has at least one major alarm.
Yellow The chassis has at least one minor alarm.
Light Blue The chassis has at least one warning.
a. If the chassis icon is colored, it indicates the chassis has an alarm. If the chassis panel is colored, it indicated the alarm is
raised on the chassis or any of the equipment or facilities on the chassis.
The Rack View provides right-click options for the most commonly performed tasks. To view the Rack
View, click the network element label in the Equipment Tree. Double-click the chassis view to view the
Equipment View.
Equipment View
The Equipment View is displayed when the user clicks on the chassis icon in the Equipment Tree. It
displays the target network element’s chassis along with its contained equipment and associated ports.The
GNM equipment View for a:
 DTN-X is shown in Figure 5-7 on page 5-11
 DTN is shown in Figure 5-8 on page 5-12 and
 Optical Amplifier is shown in Figure 5-9 on page 5-13.
 FlexROADM is shown in Figure 5-10 on page 5-14
 Optical Line Amplifier is shown in Figure 5-11 on page 5-15

Page 11
Figure 5-7 GNM Equipment View for DTN-X

Page 12
Figure 5-8 GNM Equipment View for DTN

Page 13
Figure 5-9 GNM Equipment View for Optical Amplifier

Page 14
Figure 5-10 GNM Equipment View for FlexROADM

Page 15
Figure 5-11 GNM Equipment View for Optical Line Amplifier
In a multi-chassis configuration, to view the contents of another chassis, click the corresponding chassis in
the Equipment Tree. To select an item in Equipment View, click the label or name of the equipment in the
Equipment Tree. The selected item is highlighted by a black outline. Selecting an item within the
Equipment View refreshes the Equipment Tree (by highlighting the corresponding item in the tree
structure) and the Quick View Browser (by displaying summary information about the selected item).
Right-clicking an item in the Equipment View displays a context-sensitive pop-up menu. The most
frequently used actions are listed at the top of the menu, and the context sensitive actions appear after a
separator.
The Equipment View represents the state of each displayed item using the color scheme described in
Table 5-3 on page 5-15.
Table 5-3 Equipment State Color Schema
Color/Image Description
Dark Grey The slot is empty. The circuit pack has not been pre-provisioned or equipped.
Blue The circuit pack is only pre-provisioned. No alarms can be reported.

Page 16
Table 5-3 Equipment State Color Schema
Color/Image Description
Light Grey The circuit pack is provisioned and no alarms are reported from the circuit pack.
Red The circuit pack is provisioned and has at least one critical alarm reported.
Orange The circuit pack is provisioned and has at least one major alarm reported.
Yellow The circuit pack is provisioned and has at least one minor alarm reported.
Light Blue The circuit pack is provisioned and has at least one warning reported.
Quick View Browser

The Quick View Browser is located at the bottom left of the GNM Main View. It provides a summary of the
network element (node ID, the primary DCN IP address, the secondary DCN IP address, if defined and the
current gateway) when the network element label is selected in the Equipment Tree.
When the equipment label is selected, it displays a summary of the equipment last selected in the
Equipment Tree or the Equipment View. For more information see“Equipment Tree” on page 5-8 and
“Equipment View” on page 5-10.
Figure 5-12 Quick View Browser
The Quick View Browser displays the information in the Details tab. The Details tab of the Quick View
Browser displays a snapshot (summary information) of the equipment selected in the Equipment Tree or
the Equipment View. Information can be displayed for a port, a card, a chassis or the network element.
Alarm Manager
The Alarm Manager is located at the lower right side of the GNM Main View. It includes the Alarm Table
and the Filter panel. The Alarm Table displays all outstanding alarms in the target network element. Alarms

Page 17
displayed in the Alarm Manager can be customized using the Filter panel. For more information on Alarm
Manager, refer to Infinera GNM Fault Management and Diagnostics Guide.
Status Bar
The status bar is located at the bottom of the GNM Main View. It displays the connectivity status, user
information, status of the last operation performed using Infinera GNM and alarm summary.
Figure 5-13 Status Bar
The status bar displays the following details:

 Logged In
Displays the current user login ID.
 Activity Status
Displays the status of the last operation initiated using Infinera GNM.
 Alarm Summary
Displays the total count of the current outstanding alarms for each severity, regardless of filters
applied on the alarm manager. This information is updated dynamically. The alarms can be filtered
based on severity, by clicking the respective button in the alarm summary panel.
 Connectivity Status
Displays the status of the connection between the GNM Terminal and the target network element.
For information, see “Establishing Connectivity” on page 3-1.
Slide Bar
The slide bar is located at the extreme right of the GNM Equipment View. It is used to zoom/unzoom an
equipment view.

Page 18
Figure 5-14 Slide Bar
Configuring the GNM View Options

Infinera GNM User Interface provides the following View options that can be configured by the user from
the Tools menu:
 Tree Option—“Tree Option” on page 5-18
 GNM Size—“GNM Size” on page 5-19
Tree Option
The Equipment Tree displays the network element and equipment identifiers such as Label and/or Name
beside the icon by default. This display can be configured using the Tree Option menu. Users can
configure the Tree Option appropriately to either display the label or name or both associated with the
network element and equipment on the network element.
To select the Tree Option
Step 1 In the GNM Main Menu, select Tools > View > Tree Option.
The following options are displayed for selection:
 Show Label
 Show Name
 Show Name and Label

Step 2 Select the radio button associated with the desired option to enable the option.

Page 19
The Equipment Tree is updated to display the network element and equipment identifiers based
on the configuration.
GNM Size
The GNM user interface application window can be resized using the GNM size menu option.
To configure the GNM application window size
Step 1 In the GNM Main Menu, select Tools > View > GNM Size.
The following options are displayed for selection:
 800x600
 1024x768
 Full Screen
Step 2 Select the radio button associated with the desired option to enable the option.
The GNM user interface application window is resized based on the selected option.
Save and Reset Preferences

User modified viewing preferences are saved and persisted on per user account name basis, irrespective
of the node the GNM was launched for. This feature eliminates the need for re-applying preferences for
every session launched. The last saved preference(s) will take effect on subsequent launch/re-open of the
application(s). It does not require re-launch of the GNM. The preferences saved for a user account on any
network element is applicable to the user account with the same name on any other network element,
when the GNM is launched from the same GNM Terminal. The user-changed preferences for each window
get automatically saved, when each of the windows in the GNM are individually closed. The user-changed
preferences do not get saved when the GNM is closed, without closing any of the currently open windows
in the GNM. Use this option to save/reset preferences for all the currently open windows in the GNM.
User preferences such as window size, column width, column sort order and sort criteria are persisted for
all inventory managers.
User preferences such as window size, column width, column ordering, column sort order, sort criteria,
severity selection and filter selection are persisted for Alarm Manager and Event Log. The height and width
of the displayed Alarm Manager and Event Log window are also persisted.
For all other applications with tabular information, user preferences such as column width, column
ordering, column sort order, sort criteria, filter selection and search criteria are persisted, wherever
applicable.
Other persisted preferences are tree options, tab selection in the Quick View Browser and the size of the
GNM main view.

Page 20
To save user preferences
Step 1 Launch the Infinera GNM client.

Step 2 Modify/set the required viewing preferences.
Step 3 In the Infinera GNM Main Menu, click Tools > Save Preferences.
The user defined/modified viewing preferences are saved.
At any time, the user modified viewing preferences can be reset to the default settings.
To reset preferences
Step 1 Launch the Infinera GNM client.

Step 2 In the Infinera GNM Main Menu, click Tools > Reset Preferences.
The user defined/modified preferences are reset and default preferences take effect on subse-
quent launch/re-open of the applications.
Viewing, Navigating and Printing Online Help

Infinera GNM also provides an Online help system. Use the Online help system to obtain information on
using the Infinera GNM, navigating within the menu options and getting information about specific tasks.
The Online help provides a detailed description of every window, procedures and related information on
the Infinera GNM features and applications. It contains a Table of Contents and a Search option to search
for specific text or topics within the Online help system.
The Online help system can be accessed from the Infinera GNM in two ways:
 From the main menu (See “To view Online help from the main menu” on page 5-20)
 From any window with a context-sensitive Help button (See “To view online help from any window”
on page 5-20)
To view Online help from the main menu
 From the Infinera GNM main menu, click Help > Help Contents.
The main page of the Online help is displayed.
Starting from the main page, you can navigate anywhere within the Online help system to access
other information.
To view online help from any window
Step 1 Launch the required window from the Infinera GNM.

Step 2 In the window, click the Help button.
The Online help page with help contents for the specific window is displayed.
From the displayed page, you can navigate within the Online help system.

Page 21
To navigate Online help pages
 Use one of the following options:

 In the Online help window, click the required topic in the Table of Contents.
The Online help page for the selected topic is displayed.
 In the Online help window, click the Search icon, enter the required text in the Find panel and
click Enter.
An index of all topics matching the search text is displayed.
At any time, to display the previously viewed page, click Previous page option in the Online help win-
dow. To go to the next page, click Next Page option in the Online help window.
To print Online help pages
Step 1 Click Page Setup to enter/verify the print settings.

Step 2 Click Print.
Inventories
Infinera GNM supports the following inventories:
 Equipment Manager: The Equipment Manager displays an equipment inventory for the target net-
work element in a tabular format. Filter operations allow users to customize how the information is
displayed. For a description of the attributes in the Equipment Manager, refer to the Infinera GNM
Configuration Management Guide.
 Facility Manager: The Facility Manager displays an inventory of all termination points for the net-
work element in a tabular format. Filter operations allow users to customize how the information is
displayed. For a description of the attributes in the Facility Manager, refer to the Infinera GNM Con-
figuration Management Guide.
 Static Route Manager: The Static Route Manager is used to view, create, modify and delete static
routes. For a description of the attributes in the Static Route Manager, refer to the Infinera GNM
Configuration Management Guide.
 Cross-Connect Manager: The Cross-connect Manager is used to view, filter, create, modify, and
delete manual Cross-Connects. For information on how to create Cross-Connects, refer to the Infin-
era GNM Service Provisioning Guide.
 Circuit Manager: The Circuit Manager is used to view, create, modify and delete circuits. For infor-
mation on how to create circuits refer to the Infinera GNM Service Provisioning Guide.
 UNI Neighbor Manager: Use UNI Neighbor Manager tool to view, create, modify, filter and delete
UNI Neighbors and to associate/disassociate GRE Tunnels and UNI TE Links with UNI Neighbors.

Page 22
For a description of the attributes in the UNI TE Neighbor Manager, refer to the Infinera GNM Ser-
vice Provisioning Guide.
 UNI TE Link Manager: Use UNI TE Link Manager tool to view, create, modify, filter and delete UNI
TE Links and to associate/disassociate Tributary Ports with UNI TE Links. For a description of the
attributes in the UNI TE Link Manager, refer to the Infinera GNM Service Provisioning Guide.
 Link Manager: The Link Manager displays an inventory of all the OCG TE Links and the L1OPN
links available from the source node, in a tabular format. Filter operations allow users to customize
how the information is displayed. The Link Manager allows for the configuration of the GRE Tunnels,
GMPLS Control Channels, TE Interfaces, and TE Endpoints and support the setting up of the out of
band GMPLS channels through the GRE Tunnels. Link Manager also supports the export functional-
ity, wherein the link inventory information can be exported to a .csv format. For more information on
the various configurations and procedural details associated with the Link Manager, refer to the Infin-
era GNM Service Provisioning Guide.
 Back Plane Link Manager: The Back Plane Link Manager displays an inventory of unidirectional
Traffic Engineering (TE) links with the source and destination line module slots in a tabular format.
These are virtual links between line modules within a network element where back plane traces are
available to transfer data. Filter operations allow users to customize how the information is dis-
played. For a description of the attributes in the Back Plane Link Manager, refer to the Infinera GNM
Service Provisioning Guide.
 Protection Group Manager: The Protection Group Manager displays an inventory of Digital SNCPs
and is used to view, filter, create, lockout, clear lockout, manual switch or delete Digital SNCPs. For
information on how to create Digital SNCPs, refer to the Infinera GNM Service Provisioning Guide.
 Event Log: The Event Log displays a list of logged events in tabular form. The events displayed are
generated by the target network element. For information on events and event management, refer to
the Infinera GNM Fault Management and Diagnostics Guide.
 Alarm Manager: The Alarm Manager displays all outstanding conditions (alarms) in a tabular form.
All outstanding alarms are maintained in the Alarm Table and displayed until the condition is cleared.
For a description of attributes in the Alarm Manager, refer to the Infinera GNM Fault Management
and Diagnostics Guide.
 Lightpath Manager: Lightpath Manager allows the user to create, modify, delete, validate, clone,
view and export Optically Engineered Lightpaths (OELs). An OEL is an end-to-end optical path that
is optically reachable for a given rate, modulation, and frequency slot type. For more information on
Lightpath Manager, refer to the Infinera GNM Service Provisioning Guide.

Page 23
Infinera GNM GUI Conventions

The Infinera GNM uses specific icons and color-coding to represent different types of equipment and their
corresponding status, as described in Table 5-4.
Table 5-4 Infinera GNM Icon Scheme
Icon Icon Name Description
Critical Alarm Circuit Indicates a circuit pack with at least one outstanding alarm of critical
Pack severity level. The Equipment View displays the card in red.
Major Alarm Circuit Pack Indicates a circuit pack with at least one outstanding alarm of major
severity level. The Equipment View displays the card in orange.
Minor Alarm Circuit Pack Indicates a circuit pack with at least one outstanding alarm of minor
severity level. The Equipment View displays the card in yellow.
Warning Circuit Pack Indicates a circuit pack with at least one warning. The Equipment View
displays the card in cyan.
No Alarm Circuit Pack Indicates a circuit pack with no outstanding alarms. The icon is dis-
played in the Equipment View.
Critical Alarm Chassis Indicates a chassis with at least one critical outstanding alarm. The icon
is displayed next to the chassis ID in the Equipment Tree.
Major Alarm Chassis Indicates a chassis with at least one major outstanding alarm. The icon
Minor Alarm Chassis Indicates a chassis with at least one minor outstanding alarm. The icon
Warning Chassis Indicates a chassis with at least one warning. The icon is displayed next
to the chassis ID in the Equipment Tree.
No Alarm Chassis Indicates a chassis with no outstanding alarms. The icon is displayed
next to the chassis ID in the Equipment Tree.
Critical Alarm PEM Indicates a Power Entry Module with at least one critical outstanding
alarm. The icon is displayed in the top left corner of the Equipment
View.
Major Alarm PEM Indicates a Power Entry Module with at least one major outstanding
View.
Minor Alarm PEM Indicates a Power Entry Module with at least one minor outstanding
View.

Page 24
Warning PEM Indicates a Power Entry Module with at least one warning outstanding
View.
No Alarm PEM Indicates a Power Entry Module with no alarms. The icon is displayed in
the top left hand corner of the Equipment View.
Critical Alarm FAN Indicates a fan with at least one critical outstanding alarm. The icon is
displayed in the top left hand corner of the Equipment View beside the
Power Entry Module icons.
Major Alarm FAN Indicates a fan with at least one major outstanding alarm. The icon is
displayed in the top left hand corner of the Equipment View beside the
Power Entry Module icons.
No Alarm FAN Indicates a fan with no outstanding alarms. The icon is displayed in the
top left hand corner of the Equipment View beside the Power Entry
Module icons.
Equipment Under Main- Indicates that the equipment is under maintenance and will not provide
tenance any service. This icon is displayed in the Equipment View.
Equipment Unlocked Indicates that the equipment is in an unlocked state. All outstanding
alarms are re-evaluated and new alarms are raised appropriately. This
icon is displayed in the State panel in the equipment properties window.
Equipment Locked Indicates that the equipment is in a locked state. All outstanding alarms
on the equipment are cleared, and new alarm reporting is suppressed.
This icon is displayed in the State panel in the equipment properties
window.
Equipment Alarm Report- Indicates that alarm reporting for the equipment is enabled. This icon is
ing Enabled displayed in the State panel in the equipment properties window.
Parent Equipment Alarm Indicates that alarm reporting for the equipment is disabled because it is
Reporting Disabled disabled for the parent object. This icon is displayed in the State panel
in the equipment properties window.
Parent and This Equip- Indicates that alarm reporting for the equipment and the parent object is
ment Alarm Reporting disabled. This icon is displayed in the State panel in the equipment
Disabled properties window.
Equipment Alarm Report- Indicates that alarm reporting for the equipment is disabled. This icon is
ing Disabled displayed in the State panel in the equipment properties window.
Equipment In Service Indicates that the equipment is in-service. This icon is displayed in the
Equipment Tree beside the equipment and in the State panel in the
equipment properties window.
Equipment Out Of Ser- Indicates that the equipment is out-of-service. This icon is displayed in
vice the Equipment Tree beside the equipment and in the State panel in the
equipment properties window.

Page 25
No Alarm Termination Indicates absence of alarm on the termination point. This icon is dis-
point played in the Equipment Tree beside the equipment.
Alarm Termination point Indicates presence of alarm on the termination point. This icon is dis-
played in the Equipment Tree beside the equipment.
Equipment Out of Ser- Indicates that the equipment is out-of-service and in administrative
vice and Maintenance maintenance state. This icon is displayed in the Equipment Tree beside
the equipment.
Equipment Out of Ser- Indicates that the equipment is out-of-service and in administrative
vice and Locked locked state. This icon is displayed in the Equipment Tree beside the
equipment.
Empty Slot Indicates an empty slot in the chassis. The icon is displayed in the
Equipment Tree beside the equipment.
Digital Repeater Node Indicates that the node is a digital repeater. The icon appears in the
Equipment Tree, next to the node label.
Optical Line Amplifier Indicates that the node is an Optical Line Amplifier. This icon appears in
Node the Equipment Tree, next to the node label.
Terminal Node Indicates that the node is a terminal node. This icon appears in the
Equipment Tree, next to the node label.
Add-Drop Node Indicates that the node type is Add-Drop. This icon appears in the
Equipment Tree.
Digital Optical Node Indicates that the node type is Digital Optical Node. This icon appears in
the Equipment Tree.
Critical Alarm DTC-B Indicates at least one critical outstanding alarm on the DTC-B. The icon
is positioned next to the DTC-B chassis ID in the Equipment Tree.
Major Alarm DTC-B Indicates at least one major outstanding alarm on the DTC-B. The icon
Minor Alarm DTC-B Indicates at least one minor outstanding alarm on the DTC-B. The icon
Warning DTC-B Indicates at least one warning on the DTC-B. The icon is positioned
next to the DTC-B chassis ID in the Equipment Tree.
No Alarm DTC-B Indicates a chassis with no outstanding alarms on the DTC-B. The icon

Page 26
Critical Alarm MTC Indicates at least one critical outstanding alarm on the MTC. The icon is
positioned next to the MTC chassis ID in the Equipment Tree.
Major Alarm MTC Indicates at least one major outstanding alarm on the MTC. The icon is
Minor Alarm MTC Indicates at least one minor outstanding alarm on the MTC. The icon is
Warning MTC Indicates at least one warning on the MTC. The icon is positioned next
to the MTC chassis ID in the Equipment Tree.
No Alarm MTC Indicates a chassis with no outstanding alarms on the MTC. The icon is
Critical Alarm OTC Indicates at least one critical outstanding alarm on the OTC. The icon is
positioned next to the OTC chassis ID in the Equipment Tree.
Major Alarm OTC Indicates at least one major outstanding alarm on the OTC. The icon is
Minor Alarm OTC Indicates at least one minor outstanding alarm on the OTC. The icon is
Warning OTC Indicates at least one warning on the OTC. The icon is positioned next
to the OTC chassis ID in the Equipment Tree.
No Alarm OTC Indicates a chassis with no outstanding alarms on the OTC. The icon is
Active Management Card Indicates that the management card is active.
Standby Management Indicates that the management card is standby.

Card
Transitioning Manage- Indicates that the management card is transitioning from active to
ment Card standby.
Service Provisioning Related Icons
Circuit Icon in the graphical representation panel of the service summary

screen indicating a circuit provisioned.

Page 27
Diversity Enabled Icon in the graphical representation panel of the service summary
screen indicating if diversity is enabled on the circuit.
Routing Constraints Icon in the graphical representation panel of the service summary
Enabled screen indicating if routing constraints are enabled on the circuit.
Service Summary Navi- Icon in the Navigation Panel of the Circuit Properties window to navi-
gation Icon gate to the Service Summary screen.
Circuit Properties Navi- Icon in the Navigation Panel of the Circuit Properties window to navi-
gation Icon gate to the Circuit Properties screen in case of unprotected circuits.
Working Path Properties Icon in the Navigation Panel of the Circuit Properties window to navi-
Navigation Icon gate to the Working Path Properties screen in case of protected circuits.
Protection Path Proper- Icon in the Navigation Panel of the Circuit Properties window to navi-
ties Navigation Icon gate to the Protection Path Properties screen in case of protected cir-
cuits.
Edit Protection Parame- Icon in the Navigation Panel of the Circuit Properties window to navi-
ters Navigation Icon gate to the Edit Protection Parameters screen in case of protected cir-
cuits.
Cross-Connect Icon in the graphical representation panel of the service summary
screen indicating a cross-connect provisioned.
Service Summary Navi- Icon in the Navigation Panel of the Cross-Connect Properties window to
gation Icon navigate to the Service Summary screen.
Cross-Connect Proper- Icon in the Navigation Panel of the Cross-Connect Properties window to
ties Navigation Icon navigate to the Circuit Properties screen in case of unprotected circuits.
Working Path Properties Icon in the Navigation Panel of the Cross-Connect Properties window to
Navigation Icon navigate to the Working Cross-Connect Properties screen in case of
protected circuits.
Protection Path Proper- Icon in the Navigation Panel of the Cross-Connect Properties window to
ties Navigation Icon navigate to the Protection Cross-Connect Properties screen in case of
protected circuits.
Edit DSNCP Navigation Icon in the Navigation Panel of the Cross-Connect Properties window to
Icon navigate to the Edit Protection Parameters screen in case of protected
circuits.

Page 28

Appendix A
Third Party Software License Terms
Infinera IQ NOS software uses certain third party software. The license terms associated with this software
require that we give copyright and license information, and these Infinera IQ NOS Third Party Software
License Terms provide those details.
As can be seen in the chart below, several third party software packages are licensed under the Sun
Binary Code License Agreement, Apache License Version 2.0, GNU General Public License Version 2,
GNU Library General Public License Version 2, or the GNU Lesser General Public License Version 2.1.
The complete text of each of those licenses is set forth after the chart below.
Notice Description of Software or

Number Name of the Licensor Terms of Agreement
1 AdventNet Licensee shall state prominently in the human interface portion of

the Derivative Works and in the documentation accompanying the
Derivative Works the following copyright message: “This product
contains copyright material licensed from AdventNet, Inc. http://
www.adventnet.com. All rights to such copyright material rest with
AdventNet.”
2 Data Connections Limited Infinera shall ensure that copyright notices listed in Schedule A
shall be displayed during the standard installation procedure, or
shall be visibly displayed as part of the product user interface (such
as in an “About” dialog box). Infinera also needs to make such
attribution in the documentation.
“Copyright © 199x-200x Data Connection Limited.”
3 J2SSH Maverick "This product includes software licensed from 3SP Ltd (http://
3sp.com). Copyright (c) 2002-2005 3SP Ltd. All rights reserved"

Page 2

4 QNX Software Systems © 1982-2002, QNX Software Systems Ltd. All rights reserved.
This product incorporates software from QNX Software Systems.
QNX Software systems incorporates certain third party software in
its stack. For license terms associated with this third party soft-
ware, please refer to the following document:
http://www.qnx.com/legal/licensing/dev_license/eula/
TPLTG.1_05d.updated.Nov24_06.pdf
5 javax jnlp javax jnlp is licensed under the GNU Lesser General Public
License v 2.1.
6 NanoXML Copyright
NanoXML is distributed under the zlib/libpng license, which is OSS
(Open Source Software) compliant. It is not GPL or LGPL and it will
never be part of the GNU project.
Copyrighted ©2000-2002 Marc De Scheemaecker, All Rights
Reserved
This software is provided 'as-is', without any express or implied
warranty. In no event will the authors be held liable for any dam-
ages arising from the use of this software.
Permission is granted to anyone to use this software for any pur-
pose, including commercial applications, and to alter it and redis-
tribute it freely, subject to the following restrictions:
The origin of this software must not be misrepresented; you must
not claim that you wrote the original software. If you use this soft-
ware in a product, an acknowledgment in the product documenta-
tion would be appreciated but is not required.
Altered source versions must be plainly marked as such, and must
not be misrepresented as being the original software.
This notice may not be removed or altered from any source distri-
bution.
7 Glazed Lists Glazed Lists is licensed under the GNU Lesser General Public
License v 2.1.

Page 3

8 bpf Copyright (c) 1990, 1991, 1992, 1993, 1994, 1995, 1996
The Regents of the University of California. All rights reserved.
This code is derived from the Stanford/CMU enet packet filter, (net/
enet.c) distributed as part of 4.3BSD, and code contributed to
Berkeley by Steven McCanne and Van Jacobson both of Lawrence
Berkeley Laboratory.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copy-
right notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribu-
tion.
3. All advertising materials mentioning features or use of this soft-
ware must display the following acknowledgement:
This product includes software developed by the University of Cali-
fornia, Berkeley and its contributors.
4. Neither the name of the University nor the names of its contrib-
utors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CON-
TRIBUTORS `ÀS IS'' AND ANY EXPRESS OR IMPLIED WAR-
RANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIM-
ITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SER-
VICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
9 GNU Readline Licensed under the terms of the GNU General Public License, ver-
sion 2.

Page 4

10 tftpd Copyright (c) 1983 Regents of the University of California. All rights
reserved.
are met:
tion.
This product includes software developed by the University of Cali-
fornia, Berkeley and its contributors.
4. Neither the name of the University nor the names of its contribu-
tors may be used to endorse or promote products derived from this
software without specific prior written permission.
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
To obtain a copy of this source code, please contact Brad Good-
son, Director, Intellectual Property Counsel, at Infinera Corporation
at bgoodson@infinera.com.
11 netx jnlp Licensed under the GNU Lesser General Public License v 2.1.

Page 5

12 javahelp Javahelp is licensed under the Sun Binary Code License Agree-
ment with the addition of the following supplemental licensing
terms:
JAVAHELP(TM) VERSION 2.0 SUPPLEMENTAL LICENSE
TERMS
These supplemental license terms ("Supplemental Terms") add to
or modify the terms of the Binary Code License Agreement (collec-
tively, the "Agreement"). Capitalized terms not defined in these
Supplemental Terms shall have the same meanings ascribed to
them in the Agreement. These Supplemental Terms shall super-
sede any inconsistent or conflicting terms in the Agreement, or in
any license contained within the Software.
1. Software Internal Use and Development License Grant. Subject
to the terms and conditions of this Agreement, including, but not
limited to Section 4 (Java(TM) Technology Restrictions) of these
Supplemental Terms, Sun grants you a non-exclusive, non-trans-
ferable, limited license to reproduce internally and use internally
the binary form of the Software complete and unmodified for the
sole purpose of designing, developing and testing your Java
applets and applications intended to run on the Java platform
("Programs").
2. License to Distribute Software.á In addition to the license
granted in Section 1 (Software Internal Use and Development
License Grant) of these Supplemental Terms, subject to the terms
and conditions of this Agreement, including but not limited to Sec-
tion 4 (Java Technology Restrictions), Sun grants you a non-exclu-
sive, non-transferable, limited license to reproduce and distribute
the Software in binary form only, provided that you (i) distribute the
Software complete and unmodified and only bundled as part of
your Programs, (ii) do not distribute additional software intended to
replace any component(s) of the Software, (iii) do not remove or
alter any proprietary legends or notices contained in the Software,
(iv) only distribute the Software subject to a license agreement that
protects Sun's interests consistent with the terms contained in this
Agreement, and (v) agree to defend and indemnify Sun and its
licensors from and against any damages, costs, liabilities, settle-
ment amounts and/or expenses (including attorneys' fees) incurred
in connection with any claim, lawsuit or action by any third party
that arises or results from the use or distribution of any and all Pro-
grams and/or Software.
3. License to Distribute Redistributables. In addition to the license
granted in Section 1 (Software Internal Use and Development
License Grant) of these Supplemental Terms, subject to the terms
and conditions of this Agreement,

Page 6

including but not limited to Section 3 (Java Technology Restric-

tions) of these Supplemental Terms, Sun grants you a non-exclu-
sive, non-transferable, limited license to reproduce and distribute
those files specifically identified as redistributable in the Software
"README" file ("Redistributables") provided that: (i) you distribute
the Redistributables complete and unmodified (unless otherwise
specified in the applicable README file), and only bundled as part
of your Programs, (ii) you do not distribute additional software
intended to supersede any component(s) of the Redistributables,
(iii) you do not remove or alter any proprietary legends or notices
contained in or on the Redistributables, (iv) you only distribute the
Redistributables pursuant to a license agreement that protects
Sun's interests consistent with the terms contained in the Agree-
ment, and (v) you agree to defend and indemnify Sun and its licen-
sors from and against any damages, costs, liabilities, settlement
amounts and/or expenses (including attorneys' fees) incurred in
connection with any claim, lawsuit or action by any third party that
arises or results from the use or distribution of any and all Pro-
grams and/or Software.
4. Java Technology Restrictions. You may not modify the Java Plat-
form Interface ("JPI", identified as classes contained within the
"java" package or any subpackages of the "java" package), by cre-
ating additional classes within the JPI or otherwise causing the
addition to or modification of the classes in the JPI. In the event
that you create an additional class and associated API(s) which (i)
extends the functionality of the Java platform, and (ii) is exposed to
third party software developers for the purpose of developing addi-
tional software which invokes such additional API, you must
promptly publish broadly an accurate specification for such API for
free use by all developers. You may not create, or authorize your
licensees to create, additional classes, interfaces, or subpackages
that are in any way identified as "java", "javax", "sun" or similar con-
vention as specified by Sun in any naming convention designation.
5. Java Runtime Availability. Refer to the appropriate version of the
Java Runtime Environment binary code license (currently located
at http://www.java.sun.com/jdk/index.html) for the availability of
runtime code which may be distributed with Java applets and appli-
cations.
6. Trademarks and Logos. You acknowledge and agree as
between you and Sun that Sun owns the SUN, SOLARIS, JAVA,
JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS,
JAVA, JINI, FORTE, and iPLANET-related trade

Page 7

marks, service marks, logos and other brand designations ("Sun

Marks"), and you agree to comply with the Sun Trademark and
Logo Usage Requirements currently located at http://
www.sun.com/policies/trademarks. Any use you make of the Sun
Marks inures to Sun's benefit.
7. Source Code. Software may contain source code that is pro-
vided solely for reference purposes pursuant to the terms of this
Agreement. Source code may not be redistributed unless expressly
provided for in this Agreement. Some source code may contain
alternative license terms that apply only to that source code file.
8. Termination for Infringement. Either party may terminate this
Agreement immediately should any Software become, or in either
party's opinion be likely to become, the subject of a claim of
infringement of any intellectual property right.
13 RSTP library RSTP library - Rapid Spanning Tree (802.1t, 802.1w)
Copyright (C) 2001-2003 Optical Access
Author: Alex Rozin
This file is part of RSTP library.
RSTP library is free software; you can redistribute it and/or modify
it under the terms of the GNU Lesser General Public License as
published by the Free Software Foundation; version 2.1
RSTP library is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR-
POSE. See the GNU Lesser
• General Public License for more details.
You should have received a copy of the GNU Lesser General Pub-
lic License along with RSTP library; see the file COPYING. If not,
write to the Free Software Foundation, Inc., 59 Temple Place -
Suite 330, Boston, MA 02111-1307, USA.
Note:ychugh:its done

Page 8

14 socket++ sockstream.C -*- C++ -*- socket library

Copyright (C) 2002 Herbert Straub for my changes, see Chan-
geLog.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published
by the Free Software Foundation; either version 2 of the License,
or (at your option) any later version.
This program is distributed in the hope that it will be useful, but
POSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public
License along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
Copyright (C) 1992-1996 Gnanasekaran Swaminathan <gs4t@vir-
ginia.edu>
Permission is granted to use at your own risk and distribute this
software in source and binary forms provided the above copyright
notice and this paragraph are preserved on all copies. This soft-
ware is provided "as is" with no express or implied warranty.
ginia.edu>
Socket++-1.11ln---------------
This is a modified version 1.11 of the Socket++ library. I had to
change the source code a bit to make it compile with egcs-2.91.66
and gcc-2.96 (Linux). This modified code will not necessarily com-
pile under other platforms than Linux (i386). It has not been tested.
If this code happens to compile with your compiler, that's good. But
if it doesn't, I really can't help you. I actually even don't know very
well how the code works, I just changed the lines that wouldn't
compile.
This source code was modified by: Lauri Nurmi lanurmi@iki.fi
Portions Copyright (C) 2002 Herbert Straub for all my changes (see
ChangeLog) Copyright (C) 1992-1996 Gnanasekaran Swamina-
than <gs4t@virginia.edu>

Page 9


15 ftplib.c ftplib.c - callable ftp access routines
Copyright (C) 1996, 1997, 1998 Thomas Pfau, pfau@cnj.digex.net
73 Catherine Street, South Bound Brook, NJ, 08880
This library is free software; you can redistribute it and/or modify it
under the terms of the GNU Library General Public License as pub-
lished by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version.
This library is distributed in the hope that it will be useful, but WITH-
OUT ANY WARRANTY; without even the implied warranty of MER-
CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the GNU Library General Public License for more details.
You should have received a copy of the GNU Library General Pub-
lic License along with this program; if not, write to the Free Soft-
ware Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
02111-1307, USA.
16 ftpproxy/ftp.c File: ftpproxy/ftp.c
Copyright (C) 1999, 2000 Wolfgang Zekoll <wzk@quietsche-
entchen.de>
Copyright (C) 2000, 2003 Andreas Schoenberg <asg@ftp-
proxy.org>
This software is free software; you can redistribute it and/or modify
POSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public
License along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.

Page 10

17 sockstream.h sockstream.h -*- C++ -*- socket library

Copyright (C) 2002 Herbert Straub
This program is free software; you can redistribute it and/or modify
POSE. See the GNU General Public License for more details. You
should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software Founda-
tion, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
ginia.edu>
Version: 12Jan97 1.11
Version: 1.2 2002-07-25 Herbert Straub
Improved Error Handling - extending the sockerr class by operation

Page 11

18 FreeRADIUS Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005 The Fre-
eRADIUS Server Project
Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005 Alan
DeKok <aland@ox.org>
Copyright (C) 1996, 1997, 1999, 2000, 2002, 2003, 2004, 2005
Free Software Foundation, Inc.
Copyright (C) 2003, 2004, 2005 Kostas Kalevras <kka-
lev@noc.ntua.gr>
Copyright (C) 2004 Cladju Consulting, Inc.
Copyright (C) 2001, 2002, 2003, 2004, 2005 Google, Inc.
Copyright (C) 2003, 2004 Michael Richardson <mcr@sandel-
man.ottawa.on.ca>
Copyright (C) 2002, 2003, 2004 Novell, Inc.
Copyright (C) 2002 Miguel A.L. Paraz <mparaz@mparaz.com>
Copyright (C) 2002 Simon Ekstrand <simon@routemeister.net>
Copyright (C) 2001 Chad Miller <cmiller@surfsouth.com>
Copyright (C) 2001 hereUare Communications, Inc.
Copyright (C) 2000 Jochen Friedrich <jochen@scram.de>
Copyright (C) 2000, 2002 Miquel van Smoorenburg
Copyright (C) 2000 Jeff Carneal <jeff@apex.net>
Copyright (C) 2000 Alan Curry <pacman@world.std.com>
Copyright (C) 2000 David Kerry <davidk@snti.com>
Copyright (C) 2000 Dmitri Ageev <d_ageev@ortcc.ru>
Copyright (C) 2000 Nathan Neulinger <nneul@umr.edu>
Copyright (C) 2000 Mike Machado <mike@innercite.com>
Copyright (C) 2000, 2001 Chad Miller <cmiller@surfsouth.com>
Copyright (C) 1997, 1998, 1999 Cistron Internet Services B.V.
Copyright (C) 1999 Kunihiro Ishiguro <kunihiro@zebra.org>
Licensed under the GNU General Public License version 2.

Page 12

19 Network Time Protocol Ver- Copyright (c) David L. Mills 1992-2001

sion 4 Distribution Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appears in all copies and
that both the copyright notice and this permission notice appear in
supporting documentation, and that the name University of elaware
not be used in advertising or publicity pertaining to distribution of
the software without specific, written prior permission.The Univer-
sity of Delaware makes no representations about the suitability this
software for any purpose. It is provided "as is" without express or
implied warranty.
20 OpenSSH This file is part of the OpenSSH software. The licences which com-
ponents of this software fall under are as follows. First, we will sum-
marize and say that all components are under a BSD licence, or a
licence more free than that. OpenSSH contains no GPL code.
1. Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland.
All rights reserved
As far as I am concerned, the code I have written for this software
can be used freely for any purpose.Any derived versions of this
software must be clearly marked as such, and if the derived work is
incompatible with the protocol description in the RFC file, it must be
called by a name other than "ssh" or "Secure Shell". However, I am
not implying to give any licenses to any patents or copyrights held
by third parties, and the software includes parts that are not under
my direct control.As far as I know, all included source code is used
in accordance with the relevant license agreements and can be
used freely for any purpose (the GNU license being the most
restrictive); see below for details.[However, none of that term is rel-
evant at this point in time. All of these restrictively licensed software
components which he talks about have been removed from
OpenSSH, i.e.,
• RSA is no longer included, found in the OpenSSL library
• IDEA is no longer included, its use is deprecated
• DES is now external, in the OpenSSL library
• GMP is no longer used, and instead we call BN code from
OpenSSL
• Zlib is now external, in a library
• The make-ssh-known-hosts script is no longer included
• TSS has been removed
• MD5 is now external, in the OpenSSL library
• RC4 support has been replaced with ARC4 support from
OpenSSL
• Blowfish is now external, in the OpenSSL library

Page 13

[Continued...]
Note that any information and cryptographic algorithms used in this
software are publicly available on the Internet and at any major
bookstore, scientific library, and patent office worldwide. More infor-
mation can be found e.g. at "http://www.cs.hut.fi/crypto".
The legal status of this program is some combination of all these
permissions and restrictions.Use only at your own responsibility.
You will be responsible for any legal consequences yourself; I am
not making any claims whether possessing or using this is legal or
not in your country, and I am not taking any responsibility on your
behalf.
NO WARRANTY BECAUSE THE PROGRAM IS LICENSED FREE
OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM,
TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT
WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PRO-
GRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FIT-
NESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS
WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE,
YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION. IN NO EVENT UNLESS REQUIRED
BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY
MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMIT-
TED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING
ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL
DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES
SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF
THE PROGRAM TO OPERATE WITH ANY OTHER PRO-
GRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
2. The 32-bit CRC compensation attack detector in deattack.c was
contributed by CORE SDI S.A. under a BSD-style license. Cryp-
tographic attack detector for ssh - source code Copyright (c) 1998
CORE SDI S.A., Buenos Aires, Argentina. All rights reserved.
modification, are permitted provided that this copyright notice is
retained.
THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESS
OR IMPLIED WARRANTIES ARE DISCLAIMED. IN NO EVENT
SHALL CORE SDI S.A. BE LIABLE FOR ANY DIRECT, INDIRECT,

Page 14

[Continued...]
INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL
DAMAGES RESULTING FROM THE USE OR MISUSE OFTHIS
SOFTWARE.
Ariel Futoransky <futo@core-sdi.com> <http://www.core-sdi.com>
3. ssh-keyscan was contributed by David Mazieres under a BSD-
style license. Copyright 1995, 1996 by David Mazieres
<dm@lcs.mit.edu>. Modification and redistribution in source and
binary forms is permitted provided that due credit is given to the
author and the OpenBSD project by leaving this copyright notice
intact.
4. The Rijndael implementation by Vincent Rijmen, Antoon Bosse-
laers and Paulo Barreto is in the public domain and distributed with
the following license:
• @version 3.0 (December 2000) Optimised ANSI C code for the
Rijndael cipher (now AES)
• @author Vincent Rijmen <vincent.rijmen@esat.kuleuven.ac.be>
• @author Antoon Bosselaers <antoon.bosselaers@esat.kuleu-
ven.ac.be>
• @author Paulo Barreto <paulo.barreto@terra.com.br>
This code is hereby placed in the public domain.
THIS SOFTWARE IS PROVIDED BY THE AUTHORS ''AS IS''
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MER-
CHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED.IN NO EVENT SHALL THE AUTHORS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCURE-
MENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOW-
EVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
5. One component of the ssh source code is under a 3-clause BSD
license, held by the University of California, since we pulled these
parts from original Berkeley code.
Copyright (c) 1983, 1990, 1992, 1993, 1995
The Regents of the University of California.All rights reserved.
are met:

Page 15

[Continued...]
tion.
PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT
(INTERRUPTION). HOWEVER CAUSED AND ON ANY THEORY
6. Remaining components of the software are provided under a
standard 2-term BSD licence with the following names as copyright
holders:
• Markus Friedl
• Theo de Raadt
• Niels Provos
• Dug Song
• Aaron Campbell
• Damien Miller
• Kevin Steves
• Daniel Kouril
• Wesley Griffin
• Per Allansson
• Nils Nordman
• Simon Wilkinson
Portable OpenSSH additionally includes code from the following
copyright holders, also under the 2-term BSD license:

Page 16

[Continued...]
• Ben Lindstrom
• Tim Rice
• Andre Lucas
• Chris Adams
• Corinna Vinschen
• Cray Inc.
• Denis Parker
• Gert Doering
• Jakob Schlyter
• Jason Downs
• Juha Yrjölä
• Michael Stone
• Networks Associates Technology, Inc.
• Solar Designer
• Todd C. Miller
• Wayne Schroeder
• William Jones
• Darren Tucker
• Sun Microsystems
are met:
tion.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR `ÀS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANT-
ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEM-
PLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSI-
NESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

Page 17

[Continued...]
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHER-
WISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFT-
WARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
8. Portable OpenSSH contains the following additional licenses:
a) md5crypt.c, md5crypt.h
"THE BEER-WARE LICENSE" (Revision
42):<phk@login.dknet.dk> wrote this file.
As long as you retain this notice you can do whatever you want
with this stuff. If we meet some day, and you think this stuff is worth
it, you can buy me a beer in return. Poul-Henning Kamp
b) snprintf replacement
Copyright Patrick Powell 1995
This code is based on code written by Patrick Powell (papow-
ell@astart.com) It may be used for any purpose as long as this
notice remains intact on all source code distributions
c) Compatibility code (openbsd-compat)
Apart from the previously mentioned licenses, various pieces of
code in the openbsd-compat/ subdirectory are licensed as follows:
Some code is licensed under a 3-term BSD license, to the following
copyright holders:
• Todd C. Miller
• Theo de Raadt
• Damien Miller
• Eric P. Allman
• The Regents of the University of California
are met:
tion.
TRIBUTORS `ÀS IS'' AND ANY EXPRESS OR IMPLIED

Page 18

[Continued...]
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO
EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEM-
PLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSI-
NESS INTERRUPTION). HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIA-
BILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Some code is licensed under an ISC-style license, to the following
copyright holders:
• Internet Software Consortium.
• Todd C. Miller
Permission to use, copy, modify, and distribute this software for any
purpose with or without fee is hereby granted, provided that the
above copyright notice and this permission notice appear in all cop-
ies.
THE SOFTWARE IS PROVIDED "AS IS" AND TODD C. MILLER
DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFT-
WARE INCLUDING ALL IMPLIED WARRANTIES OF MER-
CHANTABILITY AND FITNESS. IN NO EVENT SHALL TODD C.
MILLER BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSO-
EVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNEC-
TION WITH THE USE OR PERFORMANCE OF THIS SOFT-
WARE.
Some code is licensed under a MIT-style license to the following
copyright holders:
Free Software Foundation, Inc.
Permission is hereby granted, free of charge, to any person obtain-
ing a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, distribute with modifications, sublicense, and/or sell cop-
ies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

Page 19

[Continued...]
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY
OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FIT-
NESS FOR A PARTICULAR PURPOSE AND NONINFRINGE-
MENT. IN NO EVENT SHALL THE ABOVE COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
Except as contained in this notice, the name(s) of the above copy-
right holders shall not be used in advertising or otherwise to pro-
mote the sale, use or other dealings in this Software without prior
written authorization.
$OpenBSD: LICENSE, v 1.19 2004/08/30 09:18:08 markus Exp $

Page 20

21 OpenSSL LICENSE ISSUES

The OpenSSL toolkit stays under a dual license, i.e. both the condi-
tions of the OpenSSL License and the original SSLeay license
apply to the toolkit. See below for the actual license texts. Actually
both licenses are BSD-style Open Source licenses. In case of any
license issues related to OpenSSL please contact openssl-
core@openssl.org.
OpenSSL License
Copyright (c) 1998-2004 The OpenSSL Project. All rights reserved.
are met:
tion.
ware must display the following acknowledgment:
"This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not
be used to endorse or promote products derived from this software
without prior written permission. For written permission, please
contact openssl-core@openssl.org.
5. Products derived from this software may not be called
"OpenSSL" nor may "OpenSSL" appear in their names without
prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following
acknowledgment:
"This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit (http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT
`ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRAN-
TIES OF MERCHANTABILITY AND FITNESS FOR A PARTICU-
LAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR

Page 21

[Continued...]
This product includes cryptographic software written by Eric Young
(eay@cryptsoft.com). This product includes software written by Tim
Hudson (tjh@cryptsoft.com).
Original SSLeay License
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
All rights reserved.
This package is an SSL implementation written by Eric Young
(eay@cryptsoft.com). The implementation was written so as to
conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long
as the following conditions are adhered to. The following conditions
apply to all code found in this distribution, be it the RC4, RSA,
lhash, DES, etc., code; not just the SSL code. The SSL documen-
tation included with this distribution is covered by the same copy-
right terms except that the holder is Tim Hudson
(tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices
in the code are not to be removed. If this package is used in a prod-
uct, Eric Young should be given attribution as the author of the
parts of the library used. This can be in the form of a textual mes-
sage at program startup or in documentation (online or textual) pro-
vided with the package.
are met:
1. Redistributions of source code must retain the copyright notice,
this list of conditions and the following disclaimer.
tion.
"This product includes cryptographic software written by Eric Young
(eay@cryptsoft.com)"
The word 'cryptographic' can be left out if the routines from the
library being used are not cryptographic related.

Page 22

[Continued...]
4. If you include any Windows specific code (or a derivative
thereof) from the apps directory (application code) you must
include an acknowledgement:
"This product includes software written by Tim Hudson (tjh@crypt-
soft.com)"
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG `ÀS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANT-
ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CON-
TRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCI-
DENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCURE-
MENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOW-
EVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
The licence and distribution terms for any publicly available version
or derivative of this code cannot be changed. i.e. this code cannot
simply be copied and put under another distribution licence [includ-
ing the GNU Public Licence.]
22 MD5.cpp MD5.cpp - RSA Data Security, Inc., MD5 message-digest algorithm
Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All
rights reserved.
License to copy and use this software is granted provided that it is
identified as the "RSA Data Security, Inc. MD5 Message-Digest
Algorithm" in all material mentioning or referencing this software or
this function.
License is also granted to make and use derivative works provided
that such works are identified as "derived from the RSA Data Secu-
rity, Inc. MD5 Message-Digest Algorithm" in all material mentioning
or referencing the derived work.
RSA Data Security, Inc. makes no representations concerning
either the merchantability of this software or the suitability of this
software for any particular purpose. It is provided "as is" without
express or implied warranty of any kind. These notices must be
retained in any copies of any part of this documentation and/or soft-
ware.*/
23 XercesX Licensed under the Apache Software License, Version 2.0.

Page 23

24 GoAhead WebServer 2.1 License Agreement

THIS LICENSE AGREEMENT IS BETWEEN YOU AND GOA-
HEAD (BOTH AS DEFINED BELOW). THIS AGREEMENT
GRANTS YOU ONLY A LIMITED LICENSE TO USE GOAHEAD
PROPRIETARY COMPUTER SOFTWARE. BY EXECUTING THIS
AGREEMENT OR USING THE SOFTWARE, YOU CERTIFY
THAT YOU WILL USE THE SOFTWARE ONLY IN THE MANNER
PERMITTED HEREIN.
1. Definitions.
1.1 "Documentation" means any documentation GoAhead provides
with the Original Code.
1.2 "GoAhead" means GoAhead Software, Inc.
1.3 "Agreement" means this document.
1.4 "Modifications" means any addition to or deletion from the sub-
stance or structure of either the Original Code or any previous
Modifications.
1.5 "Original Code" means the source code to GoAhead’s propri-
etary computer software entitled GoAhead WebServer that is pro-
vided to You by GoAhead.
1.6 "You" means an individual or a legal entity exercising rights
under, and complying with all of the terms of, this license or a future
version of this license. For legal entities, "You" includes any entity
that controls, is controlled by, or is under common control with You.
For purposes of this definition, "control" means (a) the power, direct
or indirect, to cause the direction or management of such entity,
whether by contract or otherwise, or (b) ownership of fifty percent
(50%) or more of the outstanding shares or beneficial ownership of
such entity.
1.7 "Response Header" means the first portion of the response
message output by the GoAhead WebServer, containing but not
limited to, header fields for date, content-type, server identification
and cache control.
1.8"Server Identification Field" means the field in the Response
Header which contains the text "Server: GoAhead-Webs".
2. License.
2.1 Limited Original Code Grant.
Subject to the terms of this Agreement, GoAhead hereby grants
You a worldwide, royalty-free, nonexclusive, nontransferable
license, without right of sublicense, subject to third party intellectual
property claims, (a) to use and reproduce the Original Code, (b) to
create Modifications from the Original Code, and (c) to distribute
source code copies of the Original Code from solely when embed-
ded in other software (in a manner that does not allow the Original

Page 24

[Continued...]
Code to be separated) that provides material functionality in addi-
tion to the functionality provided by the Original Code.
2.2 Binary Code.
license, without right of sublicense, to copy and distribute binary
code copies of the Original Code together with Your Modifications
in binary code.
2.3 Restrictions on Use.
You may sublicense third parties to use Your Modifications if You
enter into a license agreement with such third parties that bind
such third parties to all the obligations under this Agreement appli-
cable to You and that are otherwise substantially similar in scope
and application to this Agreement (without limiting the protections
afforded to GoAhead). You may not rent, lease, or loan the soft-
ware.
2.4 Documentation.
license, without right of sublicense, to copy and distribute the Doc-
umentation in connection with the authorized distribution of the
Original Code and Modifications.
2.5License Back to GoAhead.
You hereby grant in both source code and binary code to GoAhead
a world-wide, royalty-free, non-exclusive license to copy, modify,
display, use and sublicense any Modifications You make that are
distributed or planned for distribution. Within 30 days of either such
event, You agree to ship to GoAhead a file containing the Modifica-
tions (in a media to be determined by the parties), including any
programmers’ notes and other programmers’ materials. Addition-
ally, You will provide to GoAhead a complete description of the
product, the product code or model number, the date on which the
product is initially shipped, and a contact name, phone number and
e-mail address for future correspondence. GoAhead will keep con-
fidential all data specifically marked as such.
3. Trademarks and Brand.
3.1 License and Use.
GoAhead hereby grants to You a limited world-wide, royalty-free,
non-exclusive license to use the GoAhead trade names, trade-
marks, logos, service marks and product designations posted in
Exhibit A (collectively, the "GoAhead Marks") in connection with the
activities by You under this Agreement. Additionally, GoAhead
grants You a license under the terms above to such GoAhead

Page 25

[Continued...]
trademarks as shall be identified at a URL (the "URL") provided by
GoAhead. The use by You of GoAhead Marks shall be in accor-
dance with GoAhead’s trademark policies regarding trademark
usage as established at the Web site designated by the URL, or as
otherwise communicated to You by GoAhead at its sole discretion.
You understand and agree that any use of GoAhead Marks in con-
nection with this Agreement shall not create any right, title or inter-
est in or to such GoAhead Marks and that all such use and goodwill
associated with GoAhead Marks will inure to the benefit of GoA-
head.
3.2 Promotion by You of GoAhead WebServer Mark.
In consideration for the licenses granted by GoAhead to You
herein, You agree to notify GoAhead when You incorporate the
GoAhead WebServer in Your product and to inform GoAhead when
such product begins to ship. You agree to promote the Original
Code by prominently and visibly displaying a graphic of the GoA-
head WebServer mark on the initial Web page of Your product that
is displayed each time a user connects to it. You also agree that
GoAhead may identify your company as a user of the GoAhead
WebServer by placing your company logo on its Web site. You may
further promote the Original Code by displaying the GoAhead Web-
Server mark in marketing and promotional materials such as the
home page of your Web site or Web pages promoting the product.
3.3 Copyright Notice.
You agree to include copies of the following notice (the "Notice")
regarding proprietary rights in all copies of the Original Code and
Modifications that You distribute, as follows: (a) embedded in the
binary code; and (b) on the title pages of all documentation. Fur-
thermore, You agree to use commercially reasonable efforts to
cause any licensees of your products to embed the Notice in object
code and on the title pages or relevant documentation. The Notice
is as follows: Copyright (c) 20XX GoAhead Software, Inc. All Rights
Reserved. Unless GoAhead otherwise instructs, the year 20xx is to
be replaced with the year during which the release of the Original
Code containing the notice is issued by GoAhead. If this year is not
supplied with Documentation, GoAhead will supply it upon request.
3.4 No Modifications to Server Identification Field.
You agree not to remove or modify the Server identification Field
contained in the Response Header as defined in Section 1.7 and
1.8.
4. Term.
This Agreement and license are effective from the time You exe-
cute this Agreement until this Agreement is terminated. You may

Page 26

[Continued...]
terminate this Agreement at any time by uninstalling or destroying
all copies of the Original Code including all binary versions and
removing any Modifications to the Original Code existing in any
products. This Agreement will terminate immediately and without
further notice if You fail to comply with any provision of this Agree-
ment. All restrictions on use, and all other provisions that may rea-
sonably be interpreted to survive termination of this Agreement, will
survive termination of this Agreement for any reason. Upon termi-
nation, You agree to uninstall or destroy all copies of the Original
Code, Modifications, and Documentation.
5. Warranty Disclaimers.
THE ORIGINAL CODE, THE DOCUMENTATION, AND THE
MEDIA UPON WHICH THE ORIGINAL CODE IS RECORDED (IF
ANY) ARE PROVIDED "AS IS" AND WITHOUT WARRANTIES OF
ANY KIND, EXPRESS, STATUTORY OR IMPLIED, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MER-
CHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
TITLE, AND NON-INFRINGEMENT.
The entire risk as to the quality and performance of the Original
Code (including any Modifications You make) and the Documenta-
tion is with You. Should the Original Code or the Documentation
prove defective, You (and not GoAhead or its distributors, licensors
or dealers) assume the entire cost of all necessary servicing or
repair. GoAhead does not warrant that the functions contained in
the Original Code will meet your requirements or operate in the
combination that You may select for use, that the operation of the
Original Code will be uninterrupted or error free, or that defects in
the Original Code will be corrected. No oral or written statement by
GoAhead or by a representative of GoAhead shall create a war-
ranty or increase the scope of this warranty.
GOAHEAD DOES NOT WARRANT THE ORIGINAL CODE
AGAINST INFRINGEMENT OR THE LIKE WITH RESPECT TO
ANY COPYRIGHT, PATENT, TRADE SECRET, TRADEMARK OR
OTHER PROPRIETARY OR INTELLECTUAL PROPERTY RIGHT
OF ANY THIRD PARTY AND DOES NOT WARRANT THAT THE
ORIGINAL CODE DOES NOT INCLUDE ANY VIRUS, SOFT-
WARE ROUTINE OR OTHER SOFTWARE DESIGNED TO PER-
MIT UNAUTHORIZED ACCESS, TO DISABLE, ERASE OR
OTHERWISE HARM SOFTWARE, HARDWARE OR DATA, OR
TO PERFORM ANY OTHER SUCH ACTIONS.
Any warranties that by law survive the foregoing disclaimers shall
terminate 90 days from the date You received the Original Code.
6. Limitation of Liability.
YOUR SOLE REMEDIES AND GOAHEAD'S ENTIRE LIABILITY

Page 27

[Continued...]
ARE SET FORTH ABOVE. IN NO EVENT WILL GOAHEAD OR
ITS DISTRIBUTORS OR DEALERS BE LIABLE FOR DIRECT,
INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES
RESULTING FROM THE USE OF THE ORIGINAL CODE, THE
INABILITY TO USE THE ORIGINAL CODE, OR ANY DEFECT IN
THE ORIGINAL CODE, INCLUDING ANY LOST PROFITS, EVEN
IF THEY HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
You agree that GoAhead and its distributors and dealers will not be
LIABLE for defense or indemnity with respect to any claim against
You by any third party arising from your possession or use of the
Original Code or the Documentation.
In no event will GoAhead’s total liability to You for all damages,
losses, and causes of action (whether in contract, tort, including
negligence, or otherwise) exceed the amount You paid for this
product.
SOME STATES DO NOT ALLOW LIMITATIONS ON HOW LONG
AN IMPLIED WARRANTY LASTS, AND SOME STATES DO NOT
ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR
CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATIONS
OR EXCLUSIONS MAY NOT APPLY TO YOU. THIS WARRANTY
GIVES YOU SPECIFIC LEGAL RIGHTS AND YOU MAY HAVE
OTHER RIGHTS THAT VARY FROM STATE TO STATE.
7. Indemnification by You.
You agree to indemnify and hold GoAhead harmless against any
and all claims, losses, damages and costs (including legal
expenses and reasonable counsel fees) arising out of any claim of
a third party with respect to the contents of Your products, and any
intellectual property rights or other rights or interests related
thereto.
8. High-Risk Activities.
The Original Code is not fault-tolerant and is not designed, manu-
factured or intended for use or resale as online control equipment
in hazardous environments requiring fail-safe performance, such
as in the operation of nuclear facilities, aircraft navigation or com-
munication systems, air traffic control, direct life support machines
or weapons systems, in which the failure of the Original Code could
lead directly to death, personal injury, or severe physical or envi-
ronmental damage. GoAhead and its suppliers specifically disclaim
any express or implied warranty of fitness for any high-risk uses
listed above.
9. Government Restricted Rights.
For units of the Department of Defense, use, duplication, or disclo-
sure by the Government is subject to restrictions as set forth in

Page 28

[Continued...]
subparagraph (c)(1)(ii) of the Rights in Technical Data and Com-
puter Software clause at DFARS 252.227-7013. Contractor/manu-
facturer is GoAhead Software, Inc., 10900 N.E. 8th Street, Suite
1200, Bellevue, Washington 98004.
If the Commercial Computer Software Restricted rights clause at
FAR 52.227-19 or its successors apply, the Software and Docu-
mentation constitute restricted computer software as defined in that
clause and the Government shall not have the license for published
software set forth in subparagraph (c)(3) of that clause.
The Original Code (i) was developed at private expense, and no
part of it was developed with governmental funds; (ii) is a trade
secret of GoAhead (or its licensor(s)) for all purposes of the Free-
dom of Information Act; (iii) is "restricted computer software" sub-
ject to limited utilization as provided in the contract between the
vendor and the governmental entity; and (iv) in all respects is pro-
prietary data belonging solely to GoAhead (or its licensor(s)).
10. Governing Law and Interpretation.
This Agreement shall be interpreted under and governed by the
laws of the State of Washington, without regard to its rules govern-
ing the conflict of laws. You hereby consent to the exclusive juris-
diction of the state and federal courts located in King County,
Washington over any disputes arising out of related to this Agree-
ment. If any provision of this Agreement is held illegal or unenforce-
able by a court or tribunal of competent jurisdiction, the remaining
provisions of this Agreement shall remain in effect and the invalid
provision deemed modified to the least degree necessary to rem-
edy such invalidity.
11. Entire Agreement.
This Agreement is the complete agreement between GoAhead and
You and supersedes all prior agreements, oral or written, with
respect to the subject matter hereof.
If You have any questions concerning this Agreement, You may
write to GoAhead Software, Inc., 10900 N.E. 8th Street, Suite
1200, Bellevue, Washington 98004 or send e-mail to info@goa-
head.com.
25 NuDesign software Include the following in the documentation:
Copyright (c) 1998-2007 NuDesign Technologies, Inc. All Rights
Reserved.
Copyright (c) 1999-2007 The OpenSSL Project. All rights reserved.
26 SMC – The State Machine The Source Code version of SMC is available at http://source-
Compiler forge.net/projects/smc/ under the terms of the Mozilla Public
License, Version 1.1.

Page 29
Sun Binary Code License Agreement

Sun Microsystems, Inc.
Binary Code License Agreement
READ THE TERMS OF THIS AGREEMENT AND ANY PROVIDED SUPPLEMENTAL LICENSE TERMS
(COLLECTIVELY "AGREEMENT") CAREFULLY BEFORE OPENING THE SOFTWARE MEDIA
PACKAGE. BY OPENING THE SOFTWARE MEDIA PACKAGE, YOU AGREE TO THE TERMS OF THIS
AGREEMENT. IF YOU ARE ACCESSING THE SOFTWARE ELECTRONICALLY, INDICATE YOUR
ACCEPTANCE OF THESE TERMS BY SELECTING THE "ACCEPT" BUTTON AT THE END OF THIS
AGREEMENT. IF YOU DO NOT AGREE TO ALL THESE TERMS, PROMPTLY RETURN THE UNUSED
SOFTWARE TO YOUR PLACE OF PURCHASE FOR A REFUND OR, IF THE SOFTWARE IS
ACCESSED ELECTRONICALLY, SELECT THE "DECLINE" BUTTON AT THE END OF THIS
AGREEMENT.
1. LICENSE TO USE. Sun grants you a non-exclusive and non-transferable license for the internal
use only of the accompanying software and documentation and any error corrections provided by
Sun (collectively "Software"), by the number of users and the class of computer hardware for which
the corresponding fee has been paid.
2. RESTRICTIONS. Software is confidential and copyrighted. Title to Software and all associated
intellectual property rights is retained by Sun and/or its licensors. Except as specifically authorized
in any Supplemental License Terms, you may not make copies of Software, other than a single
copy of Software for archival purposes. Unless enforcement is prohibited by applicable law, you
may not modify, decompile, or reverse engineer Software. Licensee acknowledges that Licensed
Software is not designed or intended for use in the design, construction, operation or maintenance
of any nuclear facility. Sun Microsystems, Inc. disclaims any express or implied warranty of fitness
for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name of
Sun or its licensors is granted under this Agreement.
3. LIMITED WARRANTY. Sun warrants to you that for a period of ninety (90) days from the date of
purchase, as evidenced by a copy of the receipt, the media on which Software is furnished (if any)
will be free of defects in materials and workmanship under normal use. Except for the foregoing,
Software is provided "AS IS". Your exclusive remedy and Sun's entire liability under this limited
warranty will be at Sun's option to replace Software media or refund the fee paid for Software.
4. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR
IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-
INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS
ARE HELD TO BE LEGALLY INVALID.
5. LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL
SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR
SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER
CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO
THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. In no event will Sun's liability to you, whether in contract, tort
(including negligence), or otherwise, exceed the amount paid by you for Software under this Agree-

Page 30
ment. The foregoing limitations will apply even if the above stated warranty fails of its essential pur-
pose.
6. Termination. This Agreement is effective until terminated. You may terminate this Agreement at any
time by destroying all copies of Software. This Agreement will terminate immediately without notice
from Sun if you fail to comply with any provision of this Agreement. Upon Termination, you must
destroy all copies of Software.
7. Export Regulations. All Software and technical data delivered under this Agreement are subject to
US export control laws and may be subject to export or import regulations in other countries. You
agree to comply strictly with all such laws and regulations and acknowledge that you have the
responsibility to obtain such licenses to export, re-export, or import as may be required after deliv-
ery to you.
8. U.S. Government Restricted Rights. If Software is being acquired by or on behalf of the U.S. Gov-
ernment or by a U.S. Government prime contractor or subcontractor (at any tier), then the Govern-
ment's rights in Software and accompanying documentation will be only as set forth in this
Agreement; this is in accordance with 48 CFR 227.7201 through 227.7202-4 (for Department of
Defense (DOD) acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD acquisitions).
9. Governing Law. Any action related to this Agreement will be governed by California law and con-
trolling U.S. federal law. No choice of law rules of any jurisdiction will apply.
10. 10. Severability. If any provision of this Agreement is held to be unenforceable, this Agreement will
remain in effect with the provision omitted, unless omission would frustrate the intent of the parties,
in which case this Agreement will immediately terminate.
11. Integration. This Agreement is the entire agreement between you and Sun relating to its subject
matter. It supersedes all prior or contemporaneous oral or written communications, proposals, rep-
resentations and warranties and prevails over any conflicting or additional terms of any quote,
order, acknowledgment, or other communication between the parties relating to its subject matter
during the term of this Agreement. No modification of this Agreement will be binding, unless in writ-
ing and signed by an authorized representative of each party.
GNU GENERAL PUBLIC LICENSE

Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is
not allowed.
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By
contrast, the GNU General Public License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This General Public License applies to most of
the Free Software Foundation's software and to any other program whose authors commit to using it.

Page 31
(Some other Free Software Foundation software is covered by the GNU Lesser General Public License
instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are
designed to make sure that you have the freedom to distribute copies of free software (and charge for this
service if you wish), that you receive source code or can get it if you want it, that you can change the
software or use pieces of it in new free programs; and that you know you can do these things. To protect
your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to
surrender the rights.
These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if
you modify it.For example, if you distribute copies of such a program, whether gratis or for a fee, you must
give the recipients all the rights that you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their rights. We protect your rights with
two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to
copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make
certain that everyone understands that there is no warranty for this free software. If the software is
modified by someone else and passed on, we want its recipients to know that what they have is not the
original, so that any problems introduced by others will not reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that
redistributors of a free program will individually obtain patent licenses, in effect making the program
proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use
or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright
holder saying it may be distributed under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program" means either the Program or any
derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either
verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included
without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than
copying, distribution and modification are not covered by this License; they are outside its scope. The act
of running the Program is not restricted, and the output from the Program is covered only if its contents
constitute a work based on the Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any
medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright
notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of
any warranty; and give any other recipients of the Program a copy of this License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty
protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on
the Program, and copy and distribute such modifications or work under the terms of Section 1 above,
provided that you also meet all of these conditions:

Page 32
a) You must cause the modified files to carry prominent notices stating that you changed the files and the
date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived
from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the
terms of this License.
c) If the modified program normally reads commands interactively when run, you must cause it, when
started running for such interactive use in the most ordinary way, to print or display an announcement
including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you
provide a warranty) and that users may redistribute the program under these conditions, and telling the
user how to view a copy of this License. (Exception: if the Program itself is interactive but does not
normally print such an announcement, your work based on the Program is not required to print an
announcement.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not
derived from the Program, and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those sections when you distribute them as
separate works. But when you distribute the same sections as part of a whole which is a work based on the
Program, the distribution of the whole must be on the terms of this License, whose permissions for other
licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is
not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the
intent is to exercise the right to control the distribution of derivative or collective works based on the
Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work
based on the Program) on a volume of a storage or distribution medium does not bring the other work
under the scope of this License.
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or
executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be
distributed under the terms of Sections 1 and 2 above on a medium customarily used for software
interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no
more than your cost of physically performing source distribution, a complete machine-readable copy of the
corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source
code. (This alternative is allowed only for noncommercial distribution and only if you received the program
in object code or executable form with such an offer, in accord with Subsection b above.) The source code
for a work means the preferred form of the work for making modifications to it. For an executable work,
complete source code means all the source code for all modules it contains, plus any associated interface
definition files, plus the scripts used to control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include anything that is normally distributed (in
either source or binary form) with the major components (compiler, kernel, and so on) of the operating
system on which the executable runs, unless that component itself accompanies the executable. If
distribution of executable or object code is made by offering access to copy from a designated place, then

Page 33
offering equivalent access to copy the source code from the same place counts as distribution of the
source code, even though third parties are not compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this
License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will
automatically terminate your rights under this License. However, parties who have received copies, or
rights, from you under this License will not have their licenses terminated so long as such parties remain in
full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else grants
you permission to modify or distribute the Program or its derivative works. These actions are prohibited by
law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work
based on the Program), you indicate your acceptance of this License to do so, and all its terms and
conditions for copying, distributing or modifying the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically
receives a license from the original licensor to copy, distribute or modify the Program subject to these
terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights
granted herein. You are not responsible for enforcing compliance by third parties to this License.
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not
limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise)
that contradict the conditions of this License, they do not excuse you from the conditions of this License. If
you cannot distribute so as to satisfy simultaneously your obligations under this License and any other
pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a
patent license would not permit royalty-free redistribution of the Program by all those who receive copies
directly or indirectly through you, then the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program. If any portion of this section is held invalid or
unenforceable under any particular circumstance, the balance of the section is intended to apply and the
section as a whole is intended to apply in other circumstances. It is not the purpose of this section to
induce you to infringe any patents or other property right claims or to contest validity of any such claims;
this section has the sole purpose of protecting the integrity of the free software distribution system, which
is implemented by public license practices. Many people have made generous contributions to the wide
range of software distributed through that system in reliance on consistent application of that system; it is
up to the author/donor to decide if he or she is willing to distribute software through any other system and
a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this
License.
8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by
copyrighted interfaces, the original copyright holder who places the Program under this License may add
an explicit geographical distribution limitation excluding those countries, so that distribution is permitted
only in or among countries not thus excluded. In such case, this License incorporates the limitation as if
written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions of the General Public License
from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail
to address new problems or concerns. Each version is given a distinguishing version number. If the
Program specifies a version number of this License which applies to it and "any later version", you have
the option of following the terms and conditions either of that version or of any later version published by

Page 34
the Free Software Foundation. If the Program does not specify a version number of this License, you may
choose any version ever published by the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions
are different, write to the author to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status of all derivatives of our free software
and of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR
THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE
STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE
PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND
PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE,
YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE
PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA
BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH
HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way
to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source
file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright"
line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General
Public License as published by the Free Software Foundation; either version 2 of the License, or (at your
option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even
the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write
to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Page 35
Also add information on how to contact you by electronic and paper mail. If the program is interactive,
make it output a short notice like this when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author. Gnomovision comes with ABSOLUTELY NO
WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under
certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should
show the appropriate parts of the General Public License. Of course, the commands you use may be
called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--
whatever suits your program. You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the
names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes
at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into proprietary programs. If your
program is a subroutine library, you may consider it more useful to permit linking proprietary applications
with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this
License.
GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999
Copyright (C) 1991, 1999 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
not allowed. [This is the first released version of the Lesser GPL. It also counts as the successor of the
GNU Library Public License, version 2, hence the version number 2.1.]
Preamble
contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users. This license, the Lesser General Public
License, applies to some specially designated software packages--typically libraries--of the Free Software
Foundation and other authors who decide to use it. You can use it too, but we suggest you first think
carefully about whether this license or the ordinary General Public License is the better strategy to use in
any particular case, based on the explanations below. When we speak of free software, we are referring to
freedom of use, not price. Our General Public Licenses are designed to make sure that you have the
freedom to distribute copies of free software (and charge for this service if you wish); that you receive
source code or can get it if you want it; that you can change the software and use pieces of it in new free
programs; and that you are informed that you can do these things. To protect your rights, we need to make
restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These
restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify
it. For example, if you distribute copies of the library, whether gratis or for a fee, you must give the
recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source
code. If you link other code with the library, you must provide complete object files to the recipients, so that

Page 36
they can relink them with the library after making changes to the library and recompiling it. And you must
show them these terms so they know their rights. We protect your rights with a two-step method: (1) we
copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute
and/or modify the library.
To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also,
if the library is modified by someone else and passed on, the recipients should know that what they have is
not the original version, so that the original author's reputation will not be affected by problems that might
be introduced by others. Finally, software patents pose a constant threat to the existence of any free
program. We wish to make sure that a company cannot effectively restrict the users of a free program by
obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for
a version of the library must be consistent with the full freedom of use specified in this license. Most GNU
software, including some libraries, is covered by the ordinary GNU General Public License. This license,
the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from
the ordinary General Public License. We use this license for certain libraries in order to permit linking those
libraries into non-free programs. When a program is linked with a library, whether statically or using a
shared library, the combination of the two is legally speaking a combined work, a derivative of the original
library. The ordinary General Public License therefore permits such linking only if the entire combination fits
its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code
with the library. We call this license the "Lesser" General Public License because it does Less to protect
the user's freedom than the ordinary General Public License. It also provides other free software
developers Less of an advantage over competing non-free programs. These disadvantages are the reason
we use the ordinary General Public License for many libraries. However, the Lesser license provides
advantages in certain special circumstances. For example, on rare occasions, there may be a special need
to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To
achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free
library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the
free library to free software only, so we use the Lesser General Public License. In other cases, permission
to use a particular library in non-free programs enables a greater number of people to use a large body of
free software. For example, permission to use the GNU C Library in non-free programs enables many
more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating
system. Although the Lesser General Public License is Less protective of the users' freedom, it does
ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library. The precise terms and conditions for copying,
distribution and modification follow. Pay close attention to the difference between a "work based on the
library" and a "work that uses the library". The former contains code derived from the library, whereas the
latter must be combined with the library in order to run.
GNU LESSER GENERAL PUBLIC LICENSE

0. This License Agreement applies to any software library or other program which contains a notice placed
by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser
General Public License (also called "this License"). Each licensee is addressed as "you".
A "library" means a collection of software functions and/or data prepared so as to be conveniently linked
with application programs (which use some of those functions and data) to form executables. The "Library",

Page 37
below, refers to any such software library or work which has been distributed under these terms. A "work
based on the Library" means either the Library or any derivative work under copyright law: that is to say, a
work containing the Library or a portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is included without limitation in the term
"modification".)
"Source code" for a work means the preferred form of the work for making modifications to it. For a library,
complete source code means all the source code for all modules it contains, plus any associated interface
definition files, plus the scripts used to control compilation and installation of the library. Activities other
than copying, distribution and modification are not covered by this License; they are outside its scope. The
act of running a program using the Library is not restricted, and output from such a program is covered
only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does and what the program that uses the
Library does.
1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in
any medium, provided that you conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the
absence of any warranty; and distribute a copy of this License along with the Library. You may charge a
fee for the physical act of transferring a copy, and you may at your option offer warranty protection in
exchange for a fee.
2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the
Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided
that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices stating that you changed the files and
the date of any change.
c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms
of this License.
d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application
program that uses the facility, other than as an argument passed when the facility is invoked, then you
must make a good faith effort to ensure that, in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For
example, a function in a library to compute square roots has a purpose that is entirely well-defined
independent of the application. Therefore, Subsection 2d requires that any application-supplied function or
table used by this function must be optional: if the application does not supply it, the square root function
must still compute square roots.) These requirements apply to the modified work as a whole. If identifiable
sections of that work are not derived from the Library, and can be reasonably considered independent and
separate works in themselves, then this License, and its terms, do not apply to those sections when you
distribute them as separate works. But when you distribute the same sections as part of a whole which is a
work based on the Library, the distribution of the whole must be on the terms of this License, whose
permissions for other licensees extend to the entire whole, and thus to each and every part regardless of
who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written
entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective
works based on the Library. In addition, mere aggregation of another work not based on the Library with

Page 38
the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not
bring the other work under the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a
given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they
refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version
than version 2 of the ordinary GNU General Public License has appeared, then you can specify that
version instead if you wish.) Do not make any other change in these notices. Once this change is made in
a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy. This option is useful when you wish to copy
part of the code of the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or
executable form under the terms of Sections 1 and 2 above provided that you accompany it with the
complete corresponding machine-readable source code, which must be distributed under the terms of
Sections 1 and 2 above on a medium customarily used for software interchange. If distribution of object
code is made by offering access to copy from a designated place, then offering equivalent access to copy
the source code from the same place satisfies the requirement to distribute the source code, even though
third parties are not compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the Library, but is designed to work with the
Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation,
is not a derivative work of the Library, and therefore falls outside the scope of this License. However, linking
a "work that uses the Library" with the Library creates an executable that is a derivative of the Library
(because it contains portions of the Library), rather than a "work that uses the library". The executable is
therefore covered by this License. Section 6 states terms for distribution of such executables. When a
"work that uses the Library" uses material from a header file that is part of the Library, the object code for
the work may be a derivative work of the Library even though the source code is not. Whether this is true is
especially significant if the work can be linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law. If such an object file uses only numerical
parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or
less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under
the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they
are linked directly with the Library itself.
6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with
the Library to produce a work containing portions of the Library, and distribute that work under terms of
your choice, provided that the terms permit modification of the work for the customer's own use and
reverse engineering for debugging such modifications. You must give prominent notice with each copy of
the work that the Library is used in it and that the Library and its use are covered by this License. You must
supply a copy of this License. If the work during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference directing the user to the copy of this
License. Also, you must do one of these things:
a) Accompany the work with the complete corresponding machine-readable source code for the Library
including whatever changes were used in the work (which must be distributed under Sections 1 and 2
above); and, if the work is an executable linked with the Library, with the complete machine-readable "work
that uses the Library", as object code and/or source code, so that the user can modify the Library and then

Page 39
relink to produce a modified executable containing the modified Library. (It is understood that the user who
changes the contents of definitions files in the Library will not necessarily be able to recompile the
application to use the modified definitions.)
b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that
(1) uses at run time a copy of the library already present on the user's computer system, rather than
copying library functions into the executable, and (2) will operate properly with a modified version of the
library, if the user installs one, as long as the modified version is interface-compatible with the version that
the work was made with.
c) Accompany the work with a written offer, valid for at least three years, to give the same user the
materials specified in Subsection 6a, above, for a charge no more than the cost of performing this
distribution.
d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent
access to copy the above specified materials from the same place.
e) Verify that the user has already received a copy of these materials or that you have already sent this
user a copy. For an executable, the required form of the "work that uses the Library" must include any data
and utility programs needed for reproducing the executable from it. However, as a special exception, the
materials to be distributed need not include anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the operating system on which the
executable runs, unless that component itself accompanies the executable. It may happen that this
requirement contradicts the license restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot use both them and the Library
together in an executable that you distribute.
7. You may place library facilities that are a work based on the Library side-by-side in a single library
together with other library facilities not covered by this License, and distribute such a combined library,
provided that the separate distribution of the work based on the Library and of the other library facilities is
otherwise permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work based on the Library, uncombined with
any other library facilities. This must be distributed under the terms of the Sections above.
b) Give prominent notice with the combined library of the fact that part of it is a work based on the
Library, and explaining where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided
under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is
void, and will automatically terminate your rights under this License. However, parties who have received
copies, or rights, from you under this License will not have their licenses terminated so long as such
parties remain in full compliance.
you permission to modify or distribute the Library or its derivative works. These actions are prohibited by
law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based
on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for
copying, distributing or modifying the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically
receives a license from the original licensor to copy, distribute, link with or modify the Library subject to

Page 40
these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the
rights granted herein. You are not responsible for enforcing compliance by third parties with this License.
11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason
(not limited to patent issues), conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this
License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any
other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if
a patent license would not permit royalty-free redistribution of the Library by all those who receive copies
refrain entirely from distribution of the Library. If any portion of this section is held invalid or unenforceable
under any particular circumstance, the balance of the section is intended to apply, and the section as a
whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to
infringe any patents or other property right claims or to contest validity of any such claims; this section has
the sole purpose of protecting the integrity of the free software distribution system which is implemented by
public license practices. Many people have made generous contributions to the wide range of software
distributed through that system in reliance on consistent application of that system; it is up to the author/
donor to decide if he or she is willing to distribute software through any other system and a licensee cannot
impose that choice. This section is intended to make thoroughly clear what is believed to be a
consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by
copyrighted interfaces, the original copyright holder who places the Library under this License may add an
explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in
or among countries not thus excluded. In such case, this License incorporates the limitation as if written in
the body of this License.
13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public
License from time to time. Such new versions will be similar in spirit to the present version, but may differ in
detail to address new problems or concerns. Each version is given a distinguishing version number. If the
Library specifies a version number of this License which applies to it and "any later version", you have the
option of following the terms and conditions either of that version or of any later version published by the
Free Software Foundation. If the Library does not specify a license version number, you may choose any
version ever published by the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are
incompatible with these, write to the author to ask for permission. For software which is copyrighted by the
Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this.
Our decision will be guided by the two goals of preserving the free status of all derivatives of our free
software and of promoting the sharing and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE
LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU
ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

Page 41
LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL,
SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY
TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF
THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER
PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest possible use to the public, we
recommend making it free software that everyone can redistribute and change. You can do so by
permitting redistribution under these terms (or, alternatively, under the terms of the ordinary General Public
License). To apply these terms, attach the following notices to the library. It is safest to attach them to the
start of each source file to most effectively convey the exclusion of warranty; and each file should have at
least the "copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser
General Public License as published by the Free Software Foundation; either version 2.1 of the License, or
(at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have
received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free
Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
Also add information on how to contact you by electronic and paper mail. You should also get your
employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the
library, if necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library for tweaking knobs)
written by James Random Hacker.
Ty Coon, President of Vice
That's all there is to it!
GNU LIBRARY GENERAL PUBLIC LICENSE

Version 2, June 1991
Copyright (C) 1991 Free Software Foundation, Inc.
675 Mass Ave, Cambridge, MA 02139, USA

Page 42
not allowed.[This is the first released version of the library GPL. It is numbered 2 because it goes with
version 2 of the ordinary GPL.]
Preamble
contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users. This license, the Library General Public
License, applies to some specially designated Free Software Foundation software, and to any other
libraries whose authors decide to use it. You can use it for your libraries, too. When we speak of free
software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure
that you have the freedom to distribute copies of free software (and charge for this service if you wish), that
you receive source code or can get it if you want it, that you can change the software or use pieces of it in
new free programs; and that you know you can do these things. To protect your rights, we need to make
restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These
restrictions translate to certain responsibilities for you if you distribute copies of the library, or if you modify
it.
For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients
all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If
you link a program with the library, you must provide complete object files to the recipients so that they can
relink them with the library, after making changes to the library and recompiling it. And you must show them
these terms so they know their rights.
Our method of protecting your rights has two steps: (1) copyright the library, and (2) offer you this license
which gives you legal permission to copy, distribute and/or modify the library. Also, for each distributor's
protection, we want to make certain that everyone understands that there is no warranty for this free library.
If the library is modified by someone else and passed on, we want its recipients to know that what they
have is not the original version, so that any problems introduced by others will not reflect on the original
authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to
avoid the danger that companies distributing free software will individually obtain patent licenses, thus in
effect transforming the program into proprietary software. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all. Most GNU software, including some
libraries, is covered by the ordinary GNU General Public License, which was designed for utility programs.
This license, the GNU Library General Public License, applies to certain designated libraries. This license
is quite different from the ordinary one; be sure to read it in full, and don't assume that anything in it is the
same as in the ordinary license. The reason we have a separate public license for some libraries is that
they blur the distinction we usually make between modifying or adding to a program and simply using it.
Linking a program with a library, without changing the library, is in some sense simply using the library, and
is analogous to running a utility program or application program. However, in a textual and legal sense, the
linked executable is a combined work, a derivative of the original library, and the ordinary General Public
License treats it as such. Because of this blurred distinction, using the ordinary General Public License for
libraries did not effectively promote software sharing, because most developers did not use the libraries.
We concluded that weaker conditions might promote sharing better. However, unrestricted linking of non-
free programs would deprive the users of those programs of all benefit from the free status of the libraries
themselves. This Library General Public License is intended to permit developers of non-free programs to
use free libraries, while preserving your freedom as a user of such programs to change the free libraries
that are incorporated in them. (We have not seen how to achieve this as regards changes in header files,
but we have achieved it as regards changes in the actual functions of the Library.) The hope is that this will

Page 43
lead to faster development of free libraries. The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a "work based on the library" and a "work
that uses the library". The former contains code derived from the library, while the latter only works
together with the library. Note that it is possible for a library to be covered by the ordinary General Public
License rather than by this special one.
GNU LIBRARY GENERAL PUBLIC LICENSE
0. This License Agreement applies to any software library which contains a notice placed by the copyright
holder or other authorized party saying it may be distributed under the terms of this Library General Public
License (also called "this License"). Each licensee is addressed as "you".
A "library" means a collection of software functions and/or data prepared so as to be conveniently linked
with application programs (which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work which has been distributed under these
terms. A "work based on the Library" means either the Library or any derivative work under copyright law:
that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or
translated straightforwardly into another language. (Hereinafter, translation is included without limitation in
the term "modification".) "Source code" for a work means the preferred form of the work for making
modifications to it. For a library, complete source code means all the source code for all modules it
contains, plus any associated interface definition files, plus the scripts used to control compilation and
installation of the library. Activities other than copying, distribution and modification are not covered by this
License; they are outside its scope. The act of running a program using the Library is not restricted, and
output from such a program is covered only if its contents constitute a work based on the Library
(independent of the use of the Library in a tool for writing it). Whether that is true depends on what the
Library does and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in
any medium, provided that you conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the
absence of any warranty; and distribute a copy of this License along with the Library. You may charge a
fee for the physical act of transferring a copy, and you may at your option offer warranty protection in
exchange for a fee.
2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the
Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided
that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices stating that you changed the files and
the date of any change.
c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms
of this License.
d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application
program that uses the facility, other than as an argument passed when the facility is invoked, then you
must make a good faith effort to ensure that, in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For

Page 44
example, a function in a library to compute square roots has a purpose that is entirely well-defined
independent of the application. Therefore, Subsection 2d requires that any application-supplied function or
table used by this function must be optional: if the application does not supply it, the square root function
must still compute square roots.) These requirements apply to the modified work as a whole. If identifiable
sections of that work are not derived from the Library, and can be reasonably considered independent and
separate works in themselves, then this License, and its terms, do not apply to those sections when you
distribute them as separate works. But when you distribute the same sections as part of a whole which is a
work based on the Library, the distribution of the whole must be on the terms of this License, whose
permissions for other licensees extend to the entire whole, and thus to each and every part regardless of
who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written
entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective
works based on the Library. In addition, mere aggregation of another work not based on the Library with
the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not
bring the other work under the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a
given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they
refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version
than version 2 of the ordinary GNU General Public License has appeared, then you can specify that
version instead if you wish.) Do not make any other change in these notices. Once this change is made in
a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy. This option is useful when you wish to copy
part of the code of the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or
executable form under the terms of Sections 1 and 2 above provided that you accompany it with the
complete corresponding machine-readable source code, which must be distributed under the terms of
Sections 1 and 2 above on a medium customarily used for software interchange. If distribution of object
code is made by offering access to copy from a designated place, then offering equivalent access to copy
the source code from the same place satisfies the requirement to distribute the source code, even though
third parties are not compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the Library, but is designed to work with the
Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation,
is not a derivative work of the Library, and therefore falls outside the scope of this License. However, linking
a "work that uses the Library" with the Library creates an executable that is a derivative of the Library
(because it contains portions of the Library), rather than a "work that uses the library". The executable is
therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file that is part of the Library, the object
code for the work may be a derivative work of the Library even though the source code is not. Whether this
is true is especially significant if the work can be linked without the Library, or if the work is itself a library.
The threshold for this to be true is not precisely defined by law. If such an object file uses only numerical
parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or
less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under

Page 45
the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they
are linked directly with the Library itself.
6. As an exception to the Sections above, you may also compile or link a "work that uses the Library" with
the Library to produce a work containing portions of the Library, and distribute that work under terms of
your choice, provided that the terms permit modification of the work for the customer's own use and
reverse engineering for debugging such modifications. You must give prominent notice with each copy of
the work that the Library is used in it and that the Library and its use are covered by this License. You must
supply a copy of this License. If the work during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference directing the user to the copy of this
License. Also, you must do one of these things:
a) Accompany the work with the complete corresponding machine-readable source code for the Library
including whatever changes were used in the work (which must be distributed under Sections 1 and 2
above); and, if the work is an executable linked with the Library, with the complete machine-readable "work
that uses the Library", as object code and/or source code, so that the user can modify the Library and then
relink to produce a modified executable containing the modified Library. (It is understood that the user who
changes the contents of definitions files in the Library will not necessarily be able to recompile the
application to use the modified definitions.)
b) Accompany the work with a written offer, valid for at least three years, to give the same user the
materials specified in Subsection 6a, above, for a charge no more than the cost of performing this
distribution.
c) If distribution of the work is made by offering access to copy from a designated place, offer equivalent
access to copy the above specified materials from the same place.
d) Verify that the user has already received a copy of these materials or that you have already sent this
user a copy. For an executable, the required form of the "work that uses the Library" must include any data
and utility programs needed for reproducing the executable from it. However, as a special exception, the
source code distributed need not include anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the operating system on which the
executable runs, unless that component itself accompanies the executable. It may happen that this
requirement contradicts the license restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot use both them and the Library
together in an executable that you distribute.
7. You may place library facilities that are a work based on the Library side-by-side in a single library
together with other library facilities not covered by this License, and distribute such a combined library,
provided that the separate distribution of the work based on the Library and of the other library facilities is
otherwise permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work based on the Library, uncombined with
any other library facilities. This must be distributed under the terms of the Sections above.
b) Give prominent notice with the combined library of the fact that part of it is a work based on the
Library, and explaining where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided
under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is
void, and will automatically terminate your rights under this License. However, parties who have received

Page 46
copies, or rights, from you under this License will not have their licenses terminated so long as such parties
remain in full compliance.
you permission to modify or distribute the Library or its derivative works. These actions are prohibited by
law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based
on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for
copying, distributing or modifying the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically
receives a license from the original licensor to copy, distribute, link with or modify the Library subject to
these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the
rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason
(not limited to patent issues), conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this
License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any
other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if
a patent license would not permit royalty-free redistribution of the Library by all those who receive copies
refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance
of the section is intended to apply, and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to
contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free
software distribution system which is implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed through that system in reliance on
consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute
software through any other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this
License.
12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by
copyrighted interfaces, the original copyright holder who places the Library under this License may add an
explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in
or among countries not thus excluded. In such case, this License incorporates the limitation as if written in
the body of this License.
13. The Free Software Foundation may publish revised and/or new versions of the Library General Public
License from time to time. Such new versions will be similar in spirit to the present version, but may differ in
detail to address new problems or concerns. Each version is given a distinguishing version number. If the
Library specifies a version number of this License which applies to it and "any later version", you have the
option of following the terms and conditions either of that version or of any later version published by the
Free Software Foundation. If the Library does not specify a license version number, you may choose any
version ever published by the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are
incompatible with these, write to the author to ask for permission. For software which is copyrighted by the
Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this.

Page 47
Our decision will be guided by the two goals of preserving the free status of all derivatives of our free
software and of promoting the sharing and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE
LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU
ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL,
SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY
TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF
THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER
PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Appendix: How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest possible use to the public, we
recommend making it free software that everyone can redistribute and change. You can do so by
permitting redistribution under these terms (or, alternatively, under the terms of the ordinary General Public
License).
To apply these terms, attach the following notices to the library. It is safest to attach them to the start of
each source file to most effectively convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
This library is free software; you can redistribute it and/or modify it under the terms of the GNU Library
General Public License as published by the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even
the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Library General Public License for more details.
You should have received a copy of the GNU Library General Public License along with this library; if not,
write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
Also add information on how to contact you by electronic and paper mail.
You should also get your employer (if you work as a programmer) or your school, if any, to sign a
"copyright disclaimer" for the library, if necessary. Here is a sample; alter the names:

Page 48
Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library for tweaking knobs)
written by James Random Hacker.
Ty Coon, President of Vice That's all there is to it!
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by
Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the
License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by,
or are under common control with that entity. For the purposes of this definition, "control" means (i) the
power, direct or indirect, to cause the direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial
ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
“Source" form shall mean the preferred form for making modifications, including but not limited to software
source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source
form, including but not limited to compiled object code, generated documentation, and conversions to other
media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the
License, as indicated by a copyright notice that is included in or attached to the work (an example is
provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived
from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works
shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any
modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to
Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to
submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of
electronic, verbal, or written communication sent to the Licensor or its representatives, including but not
limited to communication on electronic mailing lists, source code control systems, and issue tracking

Page 49
systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving
the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by
the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has
been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby
grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license
to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby
grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated
in this section) patent license to make, have made, use, offer to sell import, and otherwise transfer the
Work, where such license applies only to those patent claims licensable by such Contributor that are
necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work
to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the
Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under
this License for that Work shall terminate as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any
medium, with or without modifications, and in Source or Object form, provided that You meet the following
conditions:
(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent,
trademark, and attribution notices from the Source form of the Work, excluding those notices that do not
pertain to any part of the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that
You distribute must include a readable copy of the attribution notices contained within such NOTICE file,
excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the
following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source
form or documentation, if provided along with the Derivative Works; or, within a display generated by the
Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE
file are for informational purposes only and do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from
the Work, provided that such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different
license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such
Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise
complies with the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally
submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this
License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall

Page 50
supersede or modify the terms of any separate license agreement you may have executed with Licensor
regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service
marks, or product names of the Licensor, except as required for reasonable and customary use in
describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the
Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES
OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or
conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR
PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the
Work and assume any risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence),
contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or
agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect,
special, incidental, or consequential damages of any character arising as a result of this License or out of
the use or inability to use the Work (including but not limited to damages for loss of goodwill, work
stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if
such Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You
may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability
obligations and/or rights consistent with this License. However, in accepting such obligations, You may act
only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if
You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims
asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed
by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should
be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class
name and description of purpose be included on the same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in
compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/
LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is
distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either
express or implied. See the License for the specific language governing permissions and limitations under
the License.

Appendix B
Acronyms
List of Acronyms
Acronym Definition
A
AAM ATN Amplifier Module
AC alternating current; air conditioner; attachment circuit
ACLI administrative command line interface
ACO alarm cutoff
ACT active
AD add/drop
ADLM Amplified Digital Line Module
ADM add/drop multiplexer
AGC Automated Gain Control
AID access identifier
AINS automatic in-service
AIS alarm indication signal
ALS Automatic Laser Shutdown
AMM ATN Management Module
AMP amplifier
ANSI American National Standards Institute
AOFM Advanced OTN FlexChannel Line Module

Page 2
Acronym Definition
AOFX Advanced OTN FlexChannel Switching Line Module

AOLM Advanced OTN Line Module
AOLX Advanced OTN Switching Line Module
APC angled physical contact
APD avalanche photo diode
API application programming interface
APS automatic protection switching
ARC Alarm Reporting Control
ARP address resolution protocol
ASAP Alarm Severity Assignment Profile Settings (for ATN; other Infinera network ele-
ments use ASPS)
ASCII American Standard Code for Information Interchange
ASE amplified spontaneous emission
ASIC application-specific integrated circuit
ASPS Alarm Severity Profile Settings
ATC-A ATN Transport Chassis - Active
ATC-P ATN Transport Chassis - Passive
ATIS Alliance for Telecommunications Industry Solutions
ATM asynchronous transfer mode
AU administrative unit
AUX auxiliary port
AVC attribute value change
AWG array waveguide grating; American wire gauge
AXLM Amplified Switching Line Module
B
BDFB battery distribution fuse bay
BDI backward defect indication
BEI backward error indication
BER bit error rate; bit error ratio
BERT bit error rate testing
BIF bend insensitive fiber
BIP-8 bit interleaved parity
BITS building-integrated timing supply
BLSR bi-directional line switched ring
BMM Band Multiplexing Module

Page 3
Acronym Definition
BNC bayonet Neill-Concelman; British Naval Connector

BOL beginning of life
BOM bill of material
BOOTP bootstrap protocol
BPF Band Pass Filter
BPOST Boot Power On Self Test
bps bits per second
BPV bipolar violations
BWP bandwidth profile
BWRP bandwidth resource profile
C
C Celsius
CBN Common Bonding Network
CBS committed burst size
CCITT Consultative Committee on International Telegraph and Telephone
(now known as the ITU-T)
CCLI commissioning command line interface
CDC colorless, directionless, and contentionless
CDE chromatic dispersion equalizer
CDR clock and data recovery
CDRH Center for Devices and Radiological Health
cDTF Clear Channel Digital Transport Frame
CET Channel Engineering Tool
CFP 100G* form factor pluggable *(C = 100 in Roman numerals; Centum)
CFR code for federal regulations
CH/Ch/ch channel
CID circuit identifier
CIR committed information rate
CIT craft interface terminal
CLEI common language equipment identifier
CLI command line interface
CLM C-band and L-band Coupler
CMM Channel Multiplexing Module
CMP congestion management profile
CNM Customer Network Manager

Page 4
Acronym Definition
CO central office
CODEC coder and decoder
COM communication
CORBA Common Object Request Broker Architecture
CoS class of service
COSP class of service profile
COSV class of service values
CPC common processor complex
CPE customer premises equipment
CPLD complex programmable logic device
CPU central processing unit
CRC cyclic redundancy check
CRM customer relationship management
CS contiguous spectrum
CSM Customer Service Module
CSPF constraint-based shortest path first algorithm
CSV comma separated value
CTAG correlation tag
CTP connection termination point, channel trail termination point, client termination point
CTS clear to send
CV coding violation
CV-L coding violation-line
CV-P coding violation-path
CV-S coding violation-section
CWDM coarse wavelength division multiplexing
D
DA digital amplifier
DB database
dB decibel
DC direct current; dual carrier
DCC data communications channel
DCE data communications equipment
DCF dispersion compensation fiber
DCM Dispersion Compensation Module
DCN data communication network

Page 5
Acronym Definition
DDR double data rate

DEMUX de-multiplexing
DFB distributed feedback
DFE decision feedback equalizer
DGE dynamic gain equalization; dynamic gain equalizer
DHCP dynamic host configuration protocol
DHDW dual height dual width
DICM DTN Interconnect Module
DLM Digital Line Module
DLV Digital Link Viewer
DMC Dispersion Management Chassis
DNA Digital Network Administrator
DPSK differential phase shift keying
DQPSK differential quadrature phase shift keying
DR digital repeater
DSE Dynamic Spectrum Equalizer
DSF dispersion shifted fiber
DSNCP Digital Subnetwork Connection Protection
DSP digital signal processor
DT digital terminal
DTC Digital Transport Chassis
DTC-B Digital Transport Chassis-B
DTE data terminal equipment
DTF Digital Transport Frame
DTL digital transport line; designated transit list
DTP digital transport path
DTS digital transport section
DV digital video
DVB digital video broadcasting
DWDM dense wavelength division multiplexing
E
EBS excess burst size
ECC error-correcting code; error correction code
EDFA erbium doped fiber amplifier
EEPROM electrically-erasable programmable read-only memory

Page 6
Acronym Definition
EFEC enhanced forward error correction

EIR excess information rate
EMC electromagnetic compatibility
EMI electromagnetic interference
EML element management layer
EMS element management system
EOL end of life
EOS end of sale
EPL Ethernet private line
ES-L line-errored seconds
ES-P path-errored seconds
ES-S section-errored seconds
ESCON Enterprise Systems Connection
ESD electrostatic discharge; electrostatic-sensitive device
ESL effective span loss
ESP Encapsulating Security Payload
ETHIF Ethernet interface
ETS IEEE European Test Symposium
ETSI European Telecommunications Standards Institute
EVC Ethernet virtual connection
F
F Fahrenheit
FA frame alignment
FAS frame alignment signal
FastSMP Fast Shared Mesh Protection
FBG fiber Bragg grating
FC Fibre Channel; fiber channel; failure count
FCAPS fault management, configuration management, accounting, performance monitor-
ing, and security administration
FCC Federal Communications Commission (USA)
FDA Food and Drug Administration
FDI forward defect indication
FDR field data recorder
FEC forward error correction
FICON Fibre Connection

Page 7
Acronym Definition
FIFO first-in-first-out
FIS Fault Integration Server
FIT failures in time
FLT fault
FOADM fixed optical add/drop multiplexer
FMP Fiber Multiplexing Panel
FMP-C Fiber Multiplexing Panel – Colorless
FPC Fiber Panel Chassis
FPGA field programmable gate array
FRM FlexROADM Module
FRU field replaceable unit
FSE FlexROADM Switching Expansion Module
FSM FlexROADM Switching Module
FSP Fiber Shuffle Panel
FTP file transfer protocol; floating termination point
G
GAM Gain Adapter Module
GbE gigabit Ethernet
Gbps gigabits per second
GCC general communication channel
GFEC general forward error correction
GFP generic framing protocol
GHz gigahertz
GMPLS generalized multi protocol label switching
GNE gateway network element
GNM Graphical Node Manager
GRE generic routing encapsulation
GTP group termination point
GUI graphical user interface
H/I
HD high definition
HD-FEC Hard Decision Forward Error Correction
HDLC high-level data link control
HTML hypertext markup language

Page 8
Acronym Definition
HTTP hypertext transfer protocol

I/O input/output
I2C inter-integrated circuit
IAM ILS Amplifier Module
IAP input, output, and alarm panel
ICG invalid code group
ID identification
IDF invalid data flag
IEC International Electrical Commission
IFF Intermittent Fault Flag
IGCC Infinera General Communication Channel
ILS Infinera Line System
IMM Infinera Management Module
IMS Infinera Management Suite
IOP input/output panel
IP Internet protocol
IQ see IQ NOS
IQ NOS Infinera IQ Network Operating System
IQA NOS Infinera IQA ATN Network Operating System
IR intermediate reach
IRM ILS Raman Amplifier Module
IS in-service
ITE information technology equipment
ITU-T International Telecommunications Union - Telecommunications
J/K/L
JDK Java Development Kit
JRE Java Runtime Environment
JS jabber seconds
L2CP Layer 2 Control Protocol
LAN local area network
LBC laser bias current
LC fiber optic cable connector type
LCK locked
LED light-emitting diode
LMM Line Multiplexing Module

Page 9
Acronym Definition
LOC loss of communication

LOF loss of frame
LOL loss of light
LOP loss of pointer
LOS loss of signal; loss of sync
LOSYNC loss of sync
LP launch power
LR long reach
LSA link state advertisement
LSB least significant bit
LTE line-terminating equipment
M
MA monitoring access
MAC media access control
MAP management application proxy
MB megabyte
Mbps megabits per second
MCM Management Control Module
MEMS micro electro mechanical systems
MFAS multi frame alignment signal
MIB management information base
MMF multimode fiber
MPO multiple-fiber push-on/pull-off
MS multiplex section
MSA multi source agreement
MSB most significant bit
MSI multiplex structure identifier
MSO multi-service operator
MSOH multiplex section overhead
MTBF mean time between failure
MTC-9 Modular Transport Chassis, 9 slot
MTU maximum transmission unit
MUX multiplex; multiplexer; multiplexing

Page 10
Acronym Definition
N
NA network administrator
NAND flash type
NC normally closed; node controller; nodal control
NCT nodal control and timing
NDSF non zero dispersion shifted fiber
NE network engineer
NEBS network equipment building standards
NEC National Electrical Code
NECG net electrical coding gain
NEL network element layer
NEPA National Environmental Policy Act
NFPA National Fire Protection Association
nm nanometer
NML network management layer
NMS network management system
NNI network-to-network interface
NO normally open
NOC network operations center
NPS Network Planning System
NRZ non-return to zero
NSA non-service affecting
NTP network time protocol
NVRAM nonvolatile random access memory
NWIF network interface
O
O-SNC optical subnetwork connection
O-TE link optical traffic engineering link
OA Optical Amplifier
OAM Optical Amplification Module
OAM&P operation, administration, maintenance and provisioning
OC-12 optical carrier signal at 622.08Mbps
OC-192 optical carrier signal at 9.95328Gbps
OC-3 optical carrier signal at 155.52Mbps

Page 11
Acronym Definition

OCG optical carrier group
Och optical channel
OCI open connection indication
ODF optical distribution frame
ODU optical data unit
OE Optical Engine
OEL optically engineered lightpath
OEO optical-electrical-optical
OER optical engineering route; Optical Express ring; Optical Express Route
OFC open fiber control
OFM Optical Filter Module
OH overhead
OIF Optical Internetworking Forum
OLOS optical loss of signal
OMA optical modulation amplitude
OMM Optical Management Module
OMS optical multiplex section
OOK on-off keying
OOS out-of-service
OOS-MT out-of-service maintenance
OPM optical power monitor
OPN Optical Private Network
OPR optical power received
OPSW Optical Protection Switch
OPT optical power transmitted
OPU optical payload unit
ORL optical return loss
ORM Optical Raman Module
OS operating system
OSA optical spectrum analyzer
OSC Optical Supervisory Channel
OSMINE Operations Systems Modifications for the Integration of Network Elements
OSNR optical signal-to-noise ratio
OSP outside plant

Page 12
Acronym Definition
OSPF open shortest path first

OSS operations support system
OTC Optical Transport Chassis
OTDR optical time domain reflectometer
OTM OTN Tributary Module
OTN Optical Transport Network
OTS optical transport section
OTU optical transport unit
OTU1 optical transport unit at the rate of 2.67Gbps.
OTU1e optical transport unit at the rate of 11.05Gbps.
OTU2 optical transport unit at the rate of 10.71Gbps.
OTU2e optical transport unit at the rate of 11.1Gbps.
OTU3 optical transport unit at the rate of 43.02Gbps
OTU3e1 optical transport unit at the rate of 44.57Gbps
OTU3e2 optical transport unit at the rate of 44.58Gbps
OTU4 optical transport unit at the rate of 111.81Gbps
OTUk optical transport unit of level k (for example, OTU1, OTU3e2, etc.)
OTUki The enhanced Infinera optical transport unit of level k (for example, OTU3i+,
OTU4i, etc.)
OW orderwire
OWM Orderwire Module
OXM OTN Switch Module
P/Q
PC personal computer
PCM Power Conversion Module
PCPM per channel power monitoring
PCS physical coding sublayer
PD photo diode
PDU protocol data unit; power distribution unit
PEM Power Entry Module
PG protection group
PHY physical
PIC Photonic Integrated Circuit
PID protocol identifier
PIN positive-intrinsic negative

Page 13
Acronym Definition
PJO positive justification opportunity

PL point loss
PLC Planar Lightwave Circuit
PLD programmable logic device
PLL phase locked loop
PLO point loss offset
PM performance monitoring; phase modulation; polarization multiplexed; preventive
maintenance
PM-BPSK polarization multiplexed-bi phase shift keying
PM-DQPSK polarization multiplexed-differential quadrature phase shift keying
PM-QPSK polarization multiplexed-quadrature phase shift keying
PMD polarization mode dispersion
PNTP provisioned neighbor termination point
POH path overhead
PON product ordering name
POP point-of-presence
POST Power On Self Test
PPM part per million
PPP point-to-point protocol
PR provisioning
PRBS pseudo random binary sequence
PROV provisioning
PRTP provisioned remote termination point
ps pico second (unit of measure for dispersion)
PSBT phase shaped binary transmission
PSC protection switch completion; protection switch count
PSD protection switch duration; power spectral density
PSE Passive Spectrum Equalizer
PSTN public switched telephone network
PTP physical termination point; point-to-point
PU protection unit
PW pseudowire
PWR power
PXM Packet Switching Module
QOS quality of service

Page 14
Acronym Definition
R
RADIUS Remote Authentication Dial-In User Service
RAM Raman Amplifier Module; random access memory
RBM Red/Blue Band Mux/Demux
RDI remote defect indication
REI-L remote error indication-line
REI-P remote error indication-path
REM Raman Extender Module
RFI remote failure indication
RLL Receive Light Level
RMA return material authorization
ROADM reconfigurable optical add/drop multiplexer
ROM read-only memory
RS regenerator section; Reed-Solomon
RSOH regenerator section overhead
RSTP rapid spanning tree protocol
RTC real time clock
RTN return lead
RTS ready to send
RU rack unit
Rx receiver; receive
Rx Q receiver quality
RZ return to zero
RZ-DQPSK return to zero-differential quadrature phase shift keying
S
SA service affecting; security administrator; security association
SAPI source access point identifier
SC shelf controller; single carrier; square shaped fiber optic cable connector
SCh super channel
SCG super channel group
SCM Submarine Control Module
SD signal degrade; standard definition
SD-FEC Soft Decision Forward Error Correction
SDH synchronous digital hierarchy

Page 15
Acronym Definition
SDI serial digital interface

SDRAM synchronized dynamic random access memory
SEF severely errored frame
SEFS severely errored frame second
SELV safety extra low voltage
SERDES serializer and deserializer
SES severely errored seconds
SF signal fail
SFP small form factor pluggable
SFTP secure file transfer protocol
SHA secure hash algorithm
SID source identifier; system identifier
SIM Service Interface Module
SL span loss
SLL Send Light Level
SLM Submarine Line Module
SLTE submarine line terminal equipment
SMF single-mode fiber
SML service management layer
SMPTE Society of Motion Picture and Television Engineers
SNC subnetwork connection
SNCP subnetwork connection protection
SNE subtending network element
SNMP simple network management protocol
SNR signal-to-noise ratio
SOFM Submarine OTN FlexChannel Line Module
SOFX Submarine OTN FlexChannel Switching Line Module
SOH section overhead
SOL start of life
SOLM Submarine OTN Line Module
SOLX Submarine OTN Switching Line Module
SONET synchronous optical network
SPE synchronous payload envelope
SQ signal quality
SR short reach
SS split spectrum

Page 16
Acronym Definition
SSHv2 Secure Shell version 2

SSL secure sockets layer
STE section terminating equipment
STM synchronous transfer mode
STM-1 SDH signal at 155.52Mbps
STM-16 SDH signal at 2.48832Gbps
STM-4 SDH signal at 622.08Mbps
STM-n synchronous transfer module of level n (for example, STM-64, STM-16)
STP spanning tree protocol
STS synchronous transport signal
STS-n synchronous transport signal of level n (for example, STS-12, STS-48)
SW software
T/U/V
TAC technical assistance center
TAM Tributary Adapter Module
TAP Timing and Alarm Panel
TCA threshold crossing alert
TCC threshold crossing condition
TCM tandem connection monitoring
TCP transmission control protocol
TE traffic engineering
TEC thermo-electric cooler
TEM TAM Extender Module
TERM terminal
TFTP trivial file transfer protocol
TID target identifier
TIM Tributary Interface Module; trace identifier mismatch
TL1 Transaction Language 1
TLA terminal line amplifier
TLS tunable laser source
TMA traffic management action list
TMF TeleManagement Forum
TMN telecommunications management network

Page 17
Acronym Definition
TMP traffic management profile

TOM Tributary Optical Module
TP termination point
TR transceiver
TSM Timing Synchronization Module
TT test and turn-up
TTI trail trace identifier
TWC true-wave-classic
Tx transmitter; transmit
UA unavailable seconds
UART universal asynchronous receiver transmitter
UAS unavailable seconds
UAS-L unavailable seconds, near-end line
UAS-P unavailable seconds, near-end path
UDP user datagram protocol
ULH ultra long haul
UNI user-network interface
UPC ultra physical contact
UPSR unidirectional path switched ring
URL universal resource locator
USB Universal Serial Bus
UTC Coordinated Universal Time
V volt
VCCI Voluntary Control Council for Interference by Information Technology Equipment
VCG virtual concatenation group
VGA variable gain amplifier
VLAN virtual local area network
VOA variable optical attenuator
VPN virtual private network
VSI virtual service instance
VSR very short reach
W/X/Y/Z
WAN wide area network
WDM wavelength division multiplexing
WPCS Wet Plant Control and Surveillance System

Page 18
Acronym Definition
WPLM Wet Plant Link Manager

WSS wavelength selective switch
WTR wait to restore, wait to revert
XC cross-connect
XCM DTN-X Control Module
XFP 10Gbps small form factor pluggable
XICM DTN-X Interconnect Module
XLM Switching Line Module
XML extensible markup language
XTC Switching Transport Chassis
MISC
1R re-amplification
2R re-amplification, re-shape
3R re-amplification, re-shape, re-time
4R re-amplification, re-shape, re-time, re-code
µEDFA micro-erbium doped fiber amplifier

R11.0 Infinera GNM Overview Guide

Uploaded by

Copyright:

Available Formats

R11.0 Infinera GNM Overview Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

R11.0 Infinera GNM Overview Guide

Uploaded by

Copyright:

Available Formats

Infinera

GNM Overview Guide

この場合には使用者が適切な対策を講 ずるよう要求されることがあります。 VCCI-A

About this Document

Chapter 2 - Getting Started

Infinera Corporation GNM Overview Guide Release 11.0 V001

Infinera Proprietary and Confidential

Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Chapter 3 - Establishing Connectivity

Chapter 4 - Software Maintenance

GNM Overview Guide Release 11.0 V001 Infinera Corporation

Infinera Proprietary and Confidential

Deleting an Unused Software or Database Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

Chapter 5 - Exploring the User Interface

Appendix A - Third Party Software License Terms

Infinera Corporation GNM Overview Guide Release 11.0 V001

Infinera Proprietary and Confidential

GNM Overview Guide Release 11.0 V001 Infinera Corporation

Infinera Proprietary and Confidential

Infinera Corporation GNM Overview Guide Release 11.0 V001

Infinera Proprietary and Confidential

Figure 5-13 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-17

GNM Overview Guide Release 11.0 V001 Infinera Corporation

Infinera Proprietary and Confidential

Table 2-1 Infinera DTN GNM Client Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Infinera Corporation GNM Overview Guide Release 11.0 V001

Infinera Proprietary and Confidential

GNM Overview Guide Release 11.0 V001 Infinera Corporation

Infinera Proprietary and Confidential

To install JRE on a Microsoft Windows PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Infinera Corporation GNM Overview Guide Release 11.0 V001

Infinera Proprietary and Confidential

To upgrade the firmware using Infinera GNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

GNM Overview Guide Release 11.0 V001 Infinera Corporation

Infinera Proprietary and Confidential

 “Document Organization” on page 12

 “Documents for Release 11.0” on page 12

 “Technical Assistance” on page 15

 “Documentation Feedback” on page 15

Infinera Corporation GNM Overview Guide Release 11.0 V001

Infinera Proprietary and Confidential

Chapter Number: Title Description

CHAPTER 1: Provides an introduction to Infinera GNM and a high-

CHAPTER 3: Provides procedures to connect the GNM Terminal to

CHAPTER 4: Describes how to maintain the network element

Documents for Release 11.0

Document Name Document ID Description

DTN and DTN-X Installation Guides Portfolio

GNM Overview Guide Release 11.0 V001 Infinera Corporation

Infinera Proprietary and Confidential

Document Name Document ID Description

DTN and DTN-X Procedure Guides Portfolio

DTN and DTN-X Reference Guides Portfolio

DTN and DTN-X User Guides Portfolio

Infinera Corporation GNM Overview Guide Release 11.0 V001

Infinera Proprietary and Confidential

Document Name Document ID Description

Convention Item Example

GNM Overview Guide Release 11.0 V001 Infinera Corporation

Infinera Proprietary and Confidential

この場合には使用者が適切な対策を講ずるよう要求されることがあります。 VCCI-A