Technical Handbook Alcatel Photonic Serv

Alcatel-Lucent
INSTALLATION ENGINEERING HANDBOOK | IEH 611

1830 PSS 64/36 GMPLS Implementation via 1350 OMS
Release 5.1
Delivery Readiness Document
Alcatel-Lucent – Internal
Proprietary – Use pursuant to Company instruction
LEGAL NOTICE
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are
the property of their respective owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for
inaccuracies contained herein.
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
This document contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be
made available to, or copied or used by anyone outside Alcatel-Lucent without its written authorization.
GCD Networks
Global Delivery Readiness
IEH 611, Section TOC

December 10, 2012
Alcatel-Lucent
INSTALLATION ENGINEERING HANDBOOK 611
1830 PSS-64/36 GMPLS IMPLEMENTATION VIA 1350 OMS
Table of Contents
Release Date Section Title

Introduction
December 10, 2012 001 Introduction
Background, Principles and Preparation
December 10, 2012 100 GMPLS Network Commissioning: Principles and Preparation
December 10, 2012 162 Fiber Optic Cleaning, Inspection, and Testing
December 10, 2012 170 GMRE Features for OCS application
December 10, 2012 200 GMPLS Network Planning and Requirements
Network Element Configuration and Testing
December 10, 2012 300 Network Element GMPLS Configuration Procedure
GMPLS Network Provisioning
December 10, 2012 400 GMPLS Network Provisioning with 1350 OMS
December 10, 2012 420 GMPLS Network Report
December 10, 2012 500 Troubleshooting
GCD Networks
IEH 611, Section 001

December 10, 2012
Alcatel-Lucent
IEH611 1830 PSS-64/36 GMPLS IMPLEMENTATION VIA 1350 OMS
1830 Photonic Service Switch PSS-64/36
Introduction
Table of Contents
General ............................................................................................................ 3
Description .................................................................................................... 3
Intended Audience ........................................................................................... 3
Feedback ...................................................................................................... 3
Related Versions ............................................................................................. 3
Global Product Expertise Center Resources (GPEC) ....................................................... 4
Web site ....................................................................................................... 4
GPEC Optics Subscription ................................................................................... 4
Usage Guidance .................................................................................................. 5
How to Use .................................................................................................... 5
High Level Flow Chart ....................................................................................... 5
Symbols ........................................................................................................ 6
Safety Operation Guide ........................................................................................ 8
Overview ....................................................................................................... 8
Potential Source of Danger ................................................................................. 8
General Safety Requirements .............................................................................. 8
Operations with Power On .................................................................................. 9
Fiber Optic Precautions ...................................................................................... 10
Fiber Optic Systems ........................................................................................ 10
Enclosed Systems ........................................................................................... 10
Unenclosed Systems ....................................................................................... 10
Fiber Inspection and Connection ........................................................................ 11
Electrostatic Discharge ....................................................................................... 12
Overview ..................................................................................................... 12
Circuit Pack Handling Precautions ...................................................................... 12
Static Control Wrist Strap ................................................................................ 13
Instruments and Tool ......................................................................................... 14
Instruments and Tools ..................................................................................... 14
IEH 611, Section 001 Introduction
List of Tables
Table 1: Product Releases ............................................................................................... 3
2 Alcatel-Lucent – Internal December 10, 2012

Introduction IEH 611, Section 001
General
Description This section provides the field engineers of 1830 PSS systems with an overview of the
information and procedures concerning GMPLS implementation in 1830 PSS-64/36. This
guide contains sections that explain the following:
Reasons for using GMPLS based optical networks over traditional ones
Communication and restoration protocols
Network Planning and Commissioning requirements
Procedure to turn up GMPLS in Network Elements
Service Types – Switching and Restoration Mechanisms
Service provisioning using OMS
Troubleshooting the GMPLS network
Intended The audience should have a basic knowledge of optical switching technology, 1830 PSS
Audience product portfolio, and completed at least Level 2 Certification program conducted by the
Alcatel-Lucent University. As such, this document is intended for:
Alcatel-Lucent (ALU) Field Engineers
ALU-Accredited 3rd Party Installers
ALU Technical Project Managers (TPM)
ALU Customer-Facing Project Managers (CFPM)
Feedback Address any feedback to: gpec.optics@alcatel-lucent.com
Related This document was developed in support of the official product manuals, which are listed in
Versions the table below and should remain as the official reference sources:
Table 1: Product Releases
Product Name Release

1830 PSS-64 5.1
1830 PSS-36 5.1
1390 NPT 5.1
1350 OMS 10.2
December 10, 2012 Alcatel-Lucent – Internal 3

Global Product Expertise Center Resources (GPEC)
Web site For more information visit the following page for product related documents in Optics portfolio:
https://all1.na.alcatel-lucent.com/Teams/GCDNetworks/OPTICSGPEC/default.aspx
Visit the following page for GPEC’s Optics Engage page:

https://engage.alcatel-lucent.com/groups/optics-gpec
GPEC Optics Subscribe to GPEC Optics bulletins and news flashes:

Subscription http://list.web.alcatel-lucent.com/cgi-bin/wa?SUBED1=gpec-optics-news&A=1

Usage Guidance
How to Use This document is composed of multiple sections. Each section contains several topical
subsections. Each subsection may contain several procedural steps. The sections are
numbered and sequentially arranged in the order they are advised to be executed. The key
areas are focused on comprehensive and actionable steps/phases to support the objective of
providing the precise and field-validated technical guidance.
High Level Flow The flowchart below outlines the top-level procedural flow of operations:
Chart
Continued on next page

Usage Guidance, Continued
Symbols The Table below lists symbols used throughout the document:
Symbol Description
NOTE Emphasizes important points or provides supplemental
guidance in addition to the main text
No personal risk. Indicates potential property damage or
service impacting situation.
CAUTION
Medium Personal Risk. Indicates potential hazardous
situation which could cause personal injury.
WARNING
High Personal Risk. Indicates potential hazardous situation
which could cause serious injury or death.
DANGER
Risk of laser radiation exposure. Viewing directly into a laser
beam increases the risk of eye damage. Never look into the
end of an exposed fiber or an open connector while the
source is switched on.
LASER
Methods & Procedures are designed to instruct readers on
what to do. However at times it is important to inform the read
of what not to do.
DO NOT
Highlights an important point.
IMPORTANT
Indicates a step/procedure where the 1350 OMS is used as
the primary interface. Applies to the OCS application of a
node.
Indicates a step/procedure where 1830 PSS ZIC (Zero

Installation Craft Terminal) is used as the primary interface.
Applies to the OCS application of a node.
Indicates a step/procedure where 1830 PSS EZ Setup is used

as the primary interface. Applies to the OCS application of a
node.

Usage Guidance, Continued
Symbols
(continued) Symbol Description
Indicates a step/procedure where 1830 PSS Command Line

Interface (CLI) is used as the primary interface.
Indicates a step/procedure where Microsoft Windows

command line is used as the primary interface.
Indicates a step/procedure where 1830 PSS TL1 is used as

the primary interface.
Indicates an attention point wherein an installer must check

before deciding to proceed
Indicates a time-saving tip or multitasking
Indicates the time-lapses to be considered within or between

steps/procedures

Safety Operation Guide
Overview All responsible technical personnel must read this section before servicing the system.
Always keep the most recent issue of this document close to the equipment.
In addition to the general safety instructions in this section, users must also observe the
specific safety instructions in the individual sections. The equipment complies with the current
national and international safety requirements. It is provided with a high degree of operational
safety resulting from many years of development experience and continuous stringent quality
checks.
Potential The equipment is safe in normal operation. However, some potential sources of danger
Source of cannot be completely eliminated. In particular, these may arise during the following
Danger operations:
Opening of housings or equipment covers
Manipulation of any kind within the equipment, even if it has been disconnected from the
power supply
Disconnection of optical or electrical connections
Through possible contact with live pairs, laser light, hot surfaces, sharp edges, or
components sensitive to electrostatic discharge
General Safety In order to keep the technically unavoidable residual risk to a minimum, it is imperative to
Requirements observe the following rules.
Transport, storage, and operation of the unit/system must be under the permissible
conditions only. See accompanying documentation and information on the unit/system.
Installation, configuration, and disassembly must be performed only by expert personnel
referring to the respective documentation. Due to the complexity of the unit/system, the
personnel performing installation, configuration, and disassembly require special training.
Expert and authorized users are required to operate the unit/system. Operate the
unit/system only after having read and understood the section on safety and the parts of the
documentation relevant to operation. For complex systems, additional training is
recommended. Any obligatory training for operating and service personnel must be carried
out and documented.
Do not operate the unit/system unless it is in perfect working order. Immediately report any
faults or errors that might affect safety.
Operate the unit/system with the proper connections and under the environmental
conditions as described in the documentation. Only qualified Alcatel-Lucent personnel or
expert personnel authorized by Alcatel-Lucent are permitted to perform conversions or
changes to the system or parts of the system (including the software). All changes
performed by other persons lead to a complete exemption from liability. Do not use
components or spare parts that are not recommended by the manufacturer and those not
listed in the procurement documents.
Only specially qualified personnel are permitted to remove or disable safety facilities, clear
faults and errors, and maintain the equipment. Strictly observe the respective parts of the
documentation, and consult the documentation during the selection of measuring and test
equipment.
Document and archive all work related to calibrations, special tests after repairs, and regular
safety checks.
Use non-system software at your own risk. The use/installation of non-system software can
adversely affect the normal functioning of the unit/system.

Safety Operation Guide, Continued
Operations with This section highlights the precautions during the procedures performed on the powered NE.
Power On
DANGER: Strictly follow these instructions:

Do not re-install or disassemble equipment when the power is on.
Do not install or remove power cables when the power is on.

Fiber Optic Precautions
Fiber Optic In its normal operating mode, an optical fiber telecommunication system is totally enclosed
Systems and presents no risk of eye injury. It is a Class I/1 system under the FDA/CDRH and IEC
classifications.
The fiber optic cables that interconnect various components of a telecommunication system
can disconnect or break and may expose people to lightwave emission. In addition, certain
maintenance procedures may expose technicians to lightwave emissions.
Unlike solid-state and gas lasers, the emission pattern of a semiconductor laser results in a
highly divergent beam. In a divergent beam, the irradiance (power density) decreases rapidly
with distance. The greater the distance, the less energy will enter the eye and the less
potential risk for eye injury. If you inadvertently view an unterminated fiber or damaged fiber
with the unaided eye at distances greater than 5 to 6 inches, normally, it will not cause eye
injury provided that the power in the fiber is less than a few milliwatts at the near IR
wavelengths and a few tens of milliwatts at the far IR wavelengths. However, damage may
occur if you use an optical instrument such as a microscope, magnifying glass, or eye loupe to
stare at the energized fiber end.
Enclosed Observe the following laser safety precautions for enclosed systems:
Systems
Because of the potential for eye damage, do not stare into optical connectors or broken
fibers.
Do not perform laser/fiber optic operations before satisfactorily completing laser safety
training.
Always observe laser safety labels. Appropriate labels must appear in plain view, in close
proximity to the optical port on the protective housing/access panel of the terminal equipment.
Unenclosed During service, maintenance, or restoration, an optical fiber telecommunication system is

Systems considered unenclosed. Observe the following laser safety precautions for unenclosed
systems:
Only authorized, trained personnel shall be permitted to perform service, maintenance, and
restoration. Avoid exposing the eye to emissions from unterminated, energized optical
connectors at close distances. Laser modules associated with the optical ports of laser
circuit packs are typically recessed, which limits the exposure distance. Optical port
shutters, automatic power reduction (APR), and automatic power shutdown (APSD) are
engineering controls that are also used to limit the emissions. However, do not stare or look
directly into the optical port with optical instruments or magnifying lenses when removing or
replacing laser circuit packs. (Normal eye wear or indirect viewing instruments, such as a
Find-R-Scopes, are not considered magnifying lenses or optical instruments.)
Only authorized, trained personnel shall use the optical test equipment during installation or
servicing. (Some examples of optical test equipment are Optical Time Domain
Reflectometers [OTDRs] and Hand-Held Loss Test Sets.)
Do not scan a fiber with an optical test set without verifying that all laser sources on the fiber
are turned off.
Only authorized personnel are permitted in the immediate area of the optical fiber
telecommunication systems during installation and service.
For guidance on the safe use of optical fiber optic communication systems in the workplace,
consult ANSI Z136.2, American National Standard for Safe Use of Optical Fiber
Communication Systems Utilizing Laser Diodes and LED Sources in the United States or
outside the United States, IEC-60825, Part 2.

Fiber Optic Precautions, Continued
Fiber The following text is the excerpt from the best practices for fiber inspection, testing, cleaning,
Inspection and and connection. For in-depth methods and procedures see Section 162 of this document.
Connection Always follow the “ICIC Process” to ensure fiber ferrules and optical ports/bulkheads are clean
prior to mating connectors:
Inspect optical jumpers and ports with optical probe
Clean optical jumpers and ports
Inspect optical jumpers and ports with optical probe
Connect to optical port/bulkhead
The Figure below illustrates the procedural sequence:
Figure 1: Fiber Inspection Flow Chart
NOTES:
Immediately connect fibers that have been cleaned and inspected;
Re-inspect a fiber jumper that has been exposed to impurities of air for a long time;
Re-inspect a fiber jumper that has been connected/re-connected multiple times and in
multiple ports;
Brand new factory-capped fibers must also be re-inspected.

Electrostatic Discharge
Overview Electrostatic discharge (ESD) (for example, caused by touching with the hand) can destroy
semiconductor components. The correct operation of the complete system is then no longer
assured.
All semiconductor components are basically sensitive to ESD. The ESD can also affect the
components indirectly.
Circuit Pack Industry experience has shown that all integrated circuit packs can be damaged by static
Handling electricity that builds up on work surfaces and personnel. The static charges are produced by
Precautions various charging effects of movement and contact with other objects. Dry air allows greater
static charges to accumulate. Higher potentials are measured in areas with low relative
humidity, but potentials high enough to cause damage can occur anywhere.
Observe the following precautions when handling circuit packs/units to prevent ESD damage.
Assume all circuit packs contain solid-state electronic components that can be damaged by
ESD.
When handling circuit packs or working on the backplane, always wear a grounded wrist
strap or heel strap and stand on a grounded, static-dissipating floor mat.
Wear working garment made of 100% cotton to avoid ESD.
Handle all circuit packs by the faceplate or latch and by the top and bottom outermost
edges. Never touch the components, conductors, or connector pins.
Store and ship circuit packs and components in their shipping packing. Circuit packs and
components must be packed and unpacked only at workplaces suitably protected against
build-up of charge.
Observe all warning labels on bags and cartons. Whenever possible, do not remove circuit
packs from antistatic packaging until ready to insert them into slots.
If possible, open all circuit packs at a static-safe work position, using properly grounded
wrist straps and static-dissipating table mats.
Always store and transport circuit packs in static-safe packaging. Shielding is not required
unless specified.
Keep all static-generating materials such as food wrappers, plastics, and Styrofoam®
containers away from all circuit packs. When removing circuit packs from a shelf,
immediately place the circuit packs in static-safe packages.
Whenever possible, maintain relative humidity above 20 percent.

Electrostatic Discharge, Continued
Circuit Pack
Handling
Precautions
IMPORTANT: Ensure that any connectors on the shelf interconnection panel that
(continued)
are not cabled are fitted with a plastic dust cap to provide ESD protection.
Static Control To reduce the possibility of ESD damage, the Alcatel-Lucent 1830 PSS shelf is equipped with
Wrist Strap an ESD grounding jack to enable personnel to ground themselves using wrist straps while
handling circuit packs or working on the shelf. Check the wrist straps periodically with a wrist
strap tester to ensure that they are working properly.
IMPORTANT: The grounding jack is located on the front of the shelf, on the
lower-right corner. Another grounding jack is also located on the rear panel.
Figure 2 Ground Strap

Instruments and Tool
Instruments The table below displays a non-exhaustive list of tools and test-sets to have on site(s):
and Tools
Instruments/Tools Usage
Optical Power Meter Measures Rx optical power, receiver sensitivity, and overload.
Mainly used to measure the optical power on the Client side,
Line side of OTs, and cumulative optical power of the
multiplexed signals.
PC Computer ZIC, 1350 OMS, CLI, Debug tool will be operated on the PC
computer.
Debug Tool A cable with mini usb connector on one end and serial port on
the other, it is used for accessing the base application running
on the FLC circuit pack. Any serial port communication
application such as HyperTerm, Putty etc are used on the PC.
3Com FTP/TFTP Server Software installed on a laptop and used to transfer and load
NE’s software.
ZIC Zero Installation Craft. Used for provisioning system and port
parameters on the 1830 PSS-64/36. ZIC is part of the PSS-
64/36 system and is accessed via any internet browser such as
Internet Explorer.
Putty It is a telnet and SSH terminal application for PC which is used
to access the CLI or serial debug port.
Fixed Line Build-Out Used to attenuate Rx optical power.
(LBO) pads
OTN Analyzer Used in the network commissioning and index tests of OTN
services.
SONET/SDH Analyzer Used in the network commissioning and index tests of SDH
services.
OC192/10 GbE Tester Used for the 10 Gbps /10 GbE services’ and protocol test.
EZ Setup A part of the ZIC but only used during the initial turn-up of the
system.

GCD Networks

December 10, 2012
Alcatel-Lucent
1830 PHOTONIC SERVICE SWITCH PSS-64/36
GMPLS Network Commissioning: Principles and Preparation
Table of Contents
General ............................................................................................................ 3
Description .................................................................................................... 3
Feedback ...................................................................................................... 3
Architecture ...................................................................................................... 4
Introduction ................................................................................................... 4
Advantages of GMRE ......................................................................................... 5
Comparison to Traditional Optical Networks ............................................................ 5
Components of GMPLS Control Plane Network ............................................................. 6
GMPLS Control Planes ....................................................................................... 6
Management Plane ........................................................................................... 6
Control Plane ................................................................................................. 6
Transport Plane .............................................................................................. 7
Protocols ....................................................................................................... 7
Routing using OSPF-TE ...................................................................................... 7
Signaling – RSVP-TE .......................................................................................... 7
Link Management Protocol ................................................................................. 7
Protocol Communication Channels ........................................................................... 8
Introduction ................................................................................................... 8
External IP Network ......................................................................................... 8
In-band Communication ..................................................................................... 9
Alcatel-Lucent GMPLS Control Plane ....................................................................... 10
Introduction to GMRE ...................................................................................... 10
GMRE Architecture ......................................................................................... 10
Network Management ..................................................................................... 11
GMRE Port Types and Signal Rates ......................................................................... 13
Transmission Ports ......................................................................................... 13
Drop Port .................................................................................................... 13
I-NNI Port .................................................................................................... 13
Drop Port Mappings ........................................................................................ 14
IEH 611, Section 100 GMPLS Network Commissioning: Principles and Preparation
List of Tables

GMPLS Network Commissioning: Principles and Preparation IEH 611, Section 100
General
Description This section provides the field engineers of 1830 PSS systems with the knowledge base
aimed for understanding of network planning/engineering with a focus on GMPLS based
optical switching.
Intended The audience should have a basic knowledge of OTN G.709 technology, 1830 PSS product
Audience portfolio, and completed at least Level 2 Certification program conducted by the Alcatel-Lucent
University. As such, this document is intended for:

1830 PSS-36 5.1
1830 PSS-64 5.1
1390 NPT 5.1
1350 OMS 10.2

Architecture
Introduction The Generalized Multi-Protocol Label Switching (GMPLS) control plane is an intelligent and
automated form of Optical Networking which is developed for the Alcatel-Lucent 1830 product
family. The purpose of GMPLS Routing Engine (GMRE) based network is to allow Optical
Network Operators to rapidly deploy services and manage them as a simplified solution which
is able to automatically restore traffic during link/node failures in the optical network.
The topology of GMRE based network is closely matches a mesh and hence it is sometimes
referred to as mesh networking.
GMPLS Topology
Core Optical Switch

Optical
Switch Router
Optical
Router Add/Drop
The Figure above shows a group of core optical switches connected to each other in a mesh
topology. Edge devices such as routers or optical switches connect as client devices to the
mesh network. The primary goal of this technology is to have the flexibility and simplicity of the
network such that it accelerates network planning, commissioning and provisioning.
Network Planning: GMPLS control plane network allows network planners to easily design
point to point multi-rate links between nodes without having to worry about complex inter-
ring and fixed line rate constraints. Growth planning is vastly simpler as new links only need
to be added where bandwidth is required. Such flexibility is not present when designing non-
GMPLS control plane networks as designer have to build closed rings across the network to
meet the growth of a smaller segment of the network
Node and Network Commissioning: With features like Automatic Node and Network
discovery, the commissioning process is much faster in GMPLS control plane networks.
Once the fibers are connected each port detects its neighbor port and informs the control
plane which in turn builds a database. Commissioning engineers can instantly check fiber
connections and begin link qualification tests using end to end service provisioning.
Network Provisioning and Maintenance: Network Operations Center (NOC) engineers
will have the ability to rapidly provision services by allowing the GMPLS control plane to
allocate and reserve bandwidth. Furthermore, troubleshooting and rerouting traffic during
multi-link failure is much faster in GMPLS control plane as the user commands the system
to take action rather than manually delete cross connections and enter them in new network
elements.

Architecture, Continued
Advantages of A GMRE enabled optical network has significant advantages over traditional optical networks.
GMRE A GMRE network has:
Automated Network Discovery
Faster Service Provisioning
Enhanced Scalability
Automatic Service Restoration (n-times)
Efficient Resource Balancing
Flexibility to have multiple rate links
Simpler Network Maintenance and Traffic Rerouting
Support of various client signals (SONET/SDH, IP/Ethernet, ATM, OTN etc)
Seamless Integration of Data and Transmission Networks
Support of Multi-Vendor networks
Interworking with Traditional Networks on Edge/Boundary Nodes
Distributed intelligence – each node is aware of other nodes and their resources in the
network.
Ability to offer different types of protection schema with different levels of Service Level
Agreement (SLA)
Network Planning tool able to design network and allocate protection bandwidth to allow for
multiple simultaneous failures within the transport network.
Comparison to After the deployment of optical networks based on Bidirectional Line Switched Ring (BLSR) or
Traditional Unidirectional Path Switched Ring (UPSR) topologies, network operators found the ring
Optical topologies to be limited in functionality and expensive to operate. Some of the areas identified
Networks for improvement were:
Maximum number of nodes in a ring limited to 16
Only 2 degrees of traffic protection
Lengthy Network Setup and Qualification time
Limited multi-vendor network support
Complicated network maintenance and troubleshooting
Slow and limited neighbor discovery
Fixed rate links
Expensive to operate due to reservation of protection bandwidth
Cumbersome and costly to modify topology
Complex circuit re-routing methods and procedures
Inability of Bidirectional Line Switched Ring BLSR to switch on path failure
Limited to In-band communication using Data Communications Channels (DCC)
Pre-defined Switching only – unable to perform intelligent switching
Limited awareness of neighbor nodes’ resources
Lack of flexibility for transport of new data rates defined in ITU-T G.709

Components of GMPLS Control Plane Network
GMPLS Control GMPLS optical networks are composed of logical planes with specific functions such as
Planes routing, signaling and transport. These planes operate using protocols over an internal or an
external communication band. The three planes in the GMPLS network are:
Management Plane
Control Plane
Transport Plane
Figure 1. Different Planes of GMPLS Control Plane Network
Management The function of the management plane is to provide centralized monitoring, provisioning and
Plane administration of the network. Operations such as end to end alarm surveillance, connection
setup/tear down, performance monitoring, link/node capacity computation are performed at
this plane.
The management plane communicates with the control plane for information and status of
links and nodes. This information is used to present to the NOC engineer for complete network
management.
Control Plane The primary function of the control plane is to perform routing and signaling functions. It is
distributed functionally across the network in each node such that it communicates directly
with the management plane and transport plane.
Operations such as connection, setup, tear down and reroute are handled by the control
plane. The control plane directs nodes in the transport plane to provision connections and
reports back to management plane the status and results of the operation.

Components of GMPLS Control Plane Network,

Continued
Control Plane It is also responsible for the restoration mechanism. It is crucial for the control plane to react
(continued) rapidly to link failures in the network and restore connections over alternate routes. The
algorithms running the control plane compute instructions for the transport plane for various
functions.
Transport Plane This plane is the actual physical network consisting of links and nodes that carry data across
the network. The transport network implements commands and instructions from the control
plane to provision or tear down cross connections. It is also responsible for reporting any fault
in the network to the control plane as alarms and conditions which are then used to trigger
connection restoration.
Protocols GMPLS Control Plane consists of three main protocols that form the basis of its operations
Open Shorted Path First with Traffic Engineering extensions (OSPF-TE) for Routing
Resource Reservation Protocol with Traffic Engineering extensions (RSVP-TE) for
Resource allocation and path setup
Link Management Protocol (LMP)
Routing using Open Shorted Path First (OSPF) is an adaptive routing protocol which uses path cost as its
OSPF-TE basic routing metric. Primarily designed for IP Networks, an extension of OSPF called OSPF-
TE (Traffic Engineering) was developed for non-IP networks. The function of OSPF-TE is to
exchange information among nodes to develop network topology. GMPLS control plane will
use this information to setup connections once it has the full network map.
A topology database is populated in each node using the OSPF-TE protocol consisting of
node and link information. Each node periodically advertises its node, link and neighbor
information to other nodes in the network. Such information is also advertised when a change
in the node or link is made such as adding a new link.
Signaling – The Resource Reservation Protocol (RSVP) is a transport layer protocol which is used to
RSVP-TE reserve resources across a network. An extension of RSVP called RSVP-TE (Traffic
Engineering) was developed for the telecommunications industry. In optical networks RSVP-
TE allows the establishment of Label Switched Paths (LSP) while considering network
constraints such as available bandwidth, risk and link/node diversity.
Link Link Management Protocol (LMP) operates between neighbor nodes using User Datagram
Management Protocol (UDP) and Transmission Control Protocol (TCP). The primary function of LMP is to
Protocol manage the Transmission Engineering (TE) links. Each TE link has a set of properties that it
shares between two neighbor nodes. These properties need to be supervised throughout the
network so that LSP creation and restoration is performed correctly.

Protocol Communication Channels
Introduction The GMPLS control plane uses a set of protocols (OSPF-TE, RSVP-TE etc) for its operation.
These protocols run on nodes where each node communicates with other nodes in the
network and exchange information for various functions. There are two mediums for the
protocols to communicate over:
External IP Network (Out of band communication)
Optical Transport Network, OTN (In band communication)
External IP In this mode of communication an external IP network is dedicated to the Control Plane for its
Network communication. This mode of exchange of traffic is called Out of band / out of fiber control
plane traffic. Some considerations for this mode are the network latency, congestion control
and available IP growth in the network. It is best to dedicate the control plane traffic to
separate IP network solely used by control plane to avoid the degradation of control plane
communication.
1675 LambdaUnite
TCP/IP Network
LAN LAN
System Controller System Controller
OCS Master Shelf OTN Interface OCS Master Shelf

PSS-64/36 PSS-64/36
OTN Port OTN Port
GMPLS Node GMPLS Node
Figure 2 External IP Network

The advantage of having an external IP network for control plane traffic is the ability of the
nodes to communicate with each other even when a fiber break has left a node isolated.
Secondly, a network comprising of multi-vendor equipment will also need an external IP
network in case there is incompatibility at the optical level.
From security point of view it is a good idea to diversify the control plane communication by
using an external IP network while it is cost effective to use in-band communication.

Protocol Communication Channels, Continued
In-band Traditionally in SONET/SDH networks, Line Data Communication Channels (Line-DCC) is

Communication used for In-band communication of control plane traffic. With OTN as a new communication
standard for Optical Switching, control plane has the option of using General Communication
Channels (GCCs) overhead bytes.
The control plane protocols are IP based hence IP-over-GCC stack is used to transport and
route traffic between GMPLS control plane nodes.
System Controller System Controller
OCS Master Shelf OTN Interface OCS Master Shelf

PSS-64/36 PSS-64/36
OTN Port OTN Port
GMPLS Node GMPLS Node
Figure 3 In-band communication

The advantage of using in-band communication is the cost saving of deploying and
maintaining a dedicated external IP network.

Alcatel-Lucent GMPLS Control Plane
Introduction to The Alcatel-Lucent GMPLS Routing Engine (GMRE) is a software package which contains the
GMRE GMPLS control plane application. This software resides on the First Level Controller (FLC)
and it is typically activated on each node in the network during the turn-up process using CLI
commands.
The GMRE application is responsible for end to end path setup, tear down, restoration and
network resource management. It uses OSPF-TE, RSVP-TE and LMP protocols for routing
and signaling.
In field applications, the GMRE enabled systems will be able to transport SONET/SDH,
Ethernet and OTN traffic across the network with various options of automatic protection and
restoration. The client links can be unprotected or 1+1 line protected. However, once the traffic
enters the GMRE domain, it has the ability to choose its path depending on the cost, risk or
latency from A node to Z node or by paths defined using constraints by the 1350 OMS.
GMPLS Control Plane Domain

OC
- 19
2 PSS-64 1830 PSS-64 PSS-36
1675 OTU3 OTU2 bE
10G 7750
OTU2
OTU2
OTU2
U2
OT
PSS-36 PSS-36
O
OTU3 OTU2
C-
19
1830 PSS-64
E
2
Gb
OT
U3
10
U3 OT
1678
7750
Figure 4 1830 GMPLS Control Plane Network

The GMRE application is present in both the Switching (OTN) and Photonic (WDM) layers.
This document will focus on the Layer 1 (L1) Switching specifically on 1830 PSS-64/36
Network Elements (NEs).
Refer to document IEH 601 1830 PSS-16/32 GMPLS Implementation via 1350 OMS.
GMRE The GMRE application is comprised of logical components which are responsible for various
Architecture functions. These components are:
Path Management: This component is responsible for end to end path setup, restoration
and tear down. The RSVP-TE protocol in each node provides resource information to the
Path Management component via the signaling handler. A path data base is maintained in
each node which has knowledge of every path in the network. It is important to note that for
any end to end path, the source node or A node is the owner of the path and is responsible
for actions such as path setup, restoration and path tear down.
Signaling Handler: This component is responsible for handling signaling messages and
protocol specific tasks. Information specific to the health of a path or link are communicated
by the signaling handler.

Alcatel-Lucent GMPLS Control Plane, Continued
GMRE Route Handler: Network Topology and link state information is maintained in a database
Architecture which is handled by the route handler using OSPF-TE protocol. With this information, the
(continued) route a path must take is computed which meets the requirements and constraints set by
the user. For example, if a user wishes to setup a path across a network and wants the path
to specifically avoid certain nodes or links.
Link Management: Manages the link resources from one node to other nodes in the
network.
Network A GMRE network can be managed by two interfaces:

Management Command Line Interface (CLI): The CLI is invoked using Secure Shell Protocol (SSH)
from a terminal which has IP access to a PSS-64/36 system. Once the basic system
software is installed on the FLC, the GMRE application is activated using CLI. The CLI
interface provides raw text output without any graphics. Although all functions of the GMRE
application can be provisioned and performed by the CLI, it is not practical to do as such
due to typing of long commands and reading raw text output. Hence, CLI is useful in initial
turn-up, troubleshooting and debugging of GMRE application, while the provisioning and
maintenance is performed by 1350 OMS Network Management System (NMS).
CLI 1350 OMS
SSH COBRA NMI
GMRE
GMRE Management Agent
Network Element
Contoller
Figure 5 Network Management

Alcatel-Lucent GMPLS Control Plane, Continued
Network 1350 OMS Network Management System: Once the GMRE application is activated by
Management CLI, and all standalone activities are completed, the node is then supervised by the 1350
(continued) OMS. The NOC OMS operator will require the PSS-64/36 login credentials, network
diagram with port numbers, types and their roles, GMRE and NE IP addresses. With this
information the 1350 OMS system performs network topology discovery and resource
availability for all NEs in the GMRE network. For this reason the 1350 OMS functions as a
centralized management system in a network of NEs having distributed intelligence.
It is important to note that once 1350 OMS begins to manage a GMRE network, all
provisioning must be performed by the 1350 OMS and CLI should only be used for
troubleshooting and debugging as otherwise it may result in network inconsistencies.

GMRE Port Types and Signal Rates
Transmission In a non-GMRE NE, all transmission ports are functionally similar such that cross connections
Ports can be provisioned from one port to another. Once GMRE application is activated in the NE
each port takes on one of the two roles.
Drop Port
Intra-Domain Port (I-NNI port)
Drop Port The Drop Port also known as Client Port is located on the inside boundary of GMRE network
domain. It connects directly via fiber to customer ports or edge devices such as routers,
Ethernet aggregators and add/drop multiplexers. The drop port is cross connected to the I-NNI
port or Line port when an end to end path or LSP is setup.
In a typical GMRE network following ports can act as drop ports
OC-48/STM-16
OC-192/STM-64
1GbE
10GbE
OTU2
OTU2E
OTU3
I-NNI Port The I-NNI port is located in the core domain of the GMRE network. These ports use the
GMRE routing and signaling protocols to discover neighbor ports and exchange topology
information. The I-NNI ports participate in restoration actions during a link failure and update
resource and status information to the GMRE application.

GMRE Port Types and Signal Rates, Continued
I-NNI Port In the PSS-64/36 system, only OTN ports can act as I-NNI ports. The following rates are
(continued) supported for I-NNI:
OTU2
OTU2E
OTU3
Drop Port The GMRE application has the ability to map client traffic connected to drop ports into I-NNI
Mappings ports without manually provisioning the multiplex structure of the I-NNI ports.
The table below illustrates the various mapping options available in PSS-64/36 GMRE
application.
Drop Port Rate OTU Layer ODU Path

OTM-0.2 LO OTU2 ODU1
ODU0
OTM-0.2 HO OTU2 ODU2
OTM-0.3 OTU3 ODU2E
ODU2
ODU1
ODU0
OTM-0.3E2 LO OTU3E2 ODU2E
ODU2
ODU1
ODU0
OC-192/STM-64 Transparently mapped to ODU ODU2
OC-48/STM-16 Transparently mapped to ODU ODU1
10GbE Transparently mapped to ODU ODU2
10GbE Transparently mapped to ODU ODU2E
1GbE Transparently mapped to ODU ODU0

GCD Net works
IEH 600, Sect ion 162

April 27, 2012
Alcat el-Lucent
INSTALLATION ENGINEERING HANDBOOK 600
Fiber Opt ic Cleaning, Inspect ion and Test ing using TK-0665B
Table of Cont ent s
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Sect ion Descript ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Previous Release Dat e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Release Not es. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Bat t ery Lif e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Calibrat ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Precaut ions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Equipment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Online Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Inspect Bef ore You Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Follow ICIC Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Fiber Opt ic Inspect ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Fiber Opt ic Inspect ion Met hod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
FiberChekPRO Set up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Fiber or Bulkhead Inspect ion Set up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Transceiver Inspect ion Set up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Inspect and Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Fiber Opt ic Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Cleaning Met hods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Cleaning Best Pract ices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Cleaning Mat erials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Recommended Met hods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Cleaning a Fiber Opt ic Connect or . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Using Casset t e St yle Cleaner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Using In Bulkhead Cleaner (IBC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Wet Cleaning a Fiber Opt ic Connect or . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Cleaning a Fiber Opt ic Transceiver or Bulkhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Using In Bulkhead Cleaner (IBC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Using St icks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Using Compressed Air . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Det ermine Insert ion Loss of Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Fiber Opt ic Insert ion Loss Met hod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Insert ion Loss Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Alcat el-Lucent – Int ernal

Propriet ary – Use pursuant t o Company inst ruct ion
IEH 600, Sect ion 162 Fiber Opt ic Cleaning, Inspect ion and Test ing using TK-0665B
Component Est imat ed Loss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Test Set up Using 1 Ref erence Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Test Set up Using 2 Ref erence Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Insert ion Loss Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Insert ion Loss Test ing Ref erences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Troubleshoot ing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Visual Fault Locat or . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Tracing Long Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Cont aminat ion Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Appendix B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Inspect ion Probe Requirement s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
IEC/ IPC St andards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Inspect ion Crit eria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
List of Figures
Figure 1: ITE-7511 JDSU P5000i Video Inspect ion Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Figure 2: Inst allat ion Not ebook Comput er wit h FiberChekPRO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 3: Inspect , Clean, Inspect , Connect Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Figure 4: Inspect ion Zones (SM endf ace) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 5: SM and MM Visual Inspect ion Crit eria (IEC-61300-3-35) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2 Alcat el-Lucent – Int ernal April 27, 2012

Fiber Opt ic Cleaning, Inspect ion and Test ing using TK-0665B IEH 600, Sect ion 162
General
Section This section contains procedures for performing Fiber Optic Cleaning, Inspection and Testing.
Description This section is based on the equipment specified in TK-0665B.
Previous New Section

Release Date
Release Notes New Section
Battery Life Most all of the equipment described in this section uses batteries for power. To ensure valid
test results make sure the batteries are fresh or recharged.
Calibration Verify that all test equipment is within the calibration cycle before performing any testing.
Precautions
• DO NOT perform any fiber testing with the laser energized.

• DO NOT look directly into the end of a fiber optic cable or fiber optic transceiver without
being absolutely certain that the system is deactivated and the laser power source is off.
• DO NOT allow the end of the fiber optic cable to make contact with any surface including
fingers.
• Ensure fiber optic cables are connected to proper test equipment before energizing the
laser.
• Use proper handling procedures when working with fiber optics cables. Sharp bends and
kinks will result in damaged or degraded fiber optics performance.
• Handle the fiber optic connectors with care to avoid direct contact with any contamination.
Dirt, oil, grease, wax and many liquids are damaging to the fiber optic.
• Use only the recommended fiber optic grade cleaning solvents and cleaning tools.
April 27, 2012 Alcat el-Lucent – Int ernal 3

General, Cont inued
Equipment Refer to the National Tool Room (NTR) for all supported ITE tools.
Overview The following equipment found in TK-0665B is recommended for fiber optic inspection,
cleaning, and insertion loss measurement:
• TK-0654 L2 Single-mode 9/125 um (yellow) Optical Test Jumper Kit
• TK-0654 L3 Multimode 62.5/125 (orange) Optical Test Jumper Kit
• TK-0654L5 Optical Fiber Cleaning Kit (port and connector end face cleaning)
• ITE-7117B JDSU OLS-36 Optical Light Source
• ITE-7116 JDSU FI-60 Optical Power Meter
• ITE-7511 JDSU P5000i Digital Video Inspection Probe with FiberChekPRO software
Figure 1: ITE-7511 JDSU P5000i Video Inspection Probe
An Installation Notebook Computer with FiberChekPRO software installed is also required for
use with ITE-7511 (video inspection probe).
Figure 2: Installation Notebook Computer with FiberChekPRO
NOTE:
• If the above probe is not available then an equivalent must be used. See Appendix B.
• FiberChek2, the previous version, may also be used but the detailed procedure for setup
and use will be different. Refer to the JDSU FiberChek2 user manual for details.

General, Cont inued
Online
Resources
Item Description and Location
TK-0665 LTE Optical Cleaning, Inspection, & Testing Kit/ Connector Grading
http://toolroomdb.web.lucent.com/ntltoolroom/Catalog/ShortSpec2.asp?t
ype=TK-0665
ITE-7511 Westover Video fiber scope probe, 400x
http://toolroomdb.web.lucent.com/ntltoolroom/Catalog/ShortSpec2.asp?t
ype=ITE-7511
JDSU P5000i Digital Analysis Microscope
FiberChekPRO
http://www.jdsu.com/en-us/Test-and-Measurement/Products/a-z-
product-list/Pages/P5000i-Digital-Analysis-Microscope.aspx

Inspect Bef ore You Connect
Follow ICIC Always follow the “ICIC Process” to ensure fiber end-faces and optical ports/bulkheads are
Process clean prior to mating connectors:
• Inspect optical jumpers and ports with optical probe
• Clean optical jumpers and ports
• Inspect optical jumpers and ports with optical probe
• Connect to optical port/bulkhead
Figure 3: Inspect, Clean, Inspect, Connect Process
NOTE:
• Immediately connect fibers that have been cleaned and inspected.
• Re-inspect a fiber that has been left open to the air and has not been immediately
connected.
• Capped fibers must also be re-inspected before being connected. This includes capped and
sealed fiber from the factory.

Fiber Opt ic Inspect ion
Fiber Optic The following procedures explain how to inspect a fiber optic connector and fiber optic
Inspection transceiver. These procedures should be followed each and every time fiber optics is
Method handled. Perform these steps before making a fiber optic connection.
FiberChekPRO Use the following steps to prepare the FiberChekPRO application for use:
Setup NOTE: FiberChek2, the previous version, may also be used but the detailed procedure for
setup and use will be different. Refer to the JDSU FiberChek2 user manual for details.
Step Action
1 Verify that the FiberChekPRO software is
installed on the Installation Notebook
Computer.
If not, install it following the manufacturer
instructions. Refer to Online Resources
above.
2 Plug the inspection probe into a USB port of

the Installation Notebook Computer.
3 Open the FiberChekPRO application on the

Installation Notebook Computer.
FiberChekPRO
4 Verify the Archiving Options settings of the
FiberChekPRO application as follows:
• Go to Setup | Archiving Options
• Set Report Layout to Consolidated (this
will same all test results in a single
Grouped Report)
• Set File Format to PDF
5 If performing work for AT&T, install the special profiles supplied in ITE-7511.

Fiber Opt ic Inspect ion, Cont inued
FiberChekPRO
Setup
Step Action
(cont inued)
6 Continue to the appropriate probe setup steps based on the item under test.
If . . . Then . . .
Inspecting a fiber optic cable or Continue to Fiber or Bulkhead
bulkhead Inspection Setup on page 8.
Inspecting a SFP or XFP Continue to Transceiver Inspection
Transceiver Setup on page 11.
Fiber or Use the following steps to prepare the probe and FiberChekPRO application for inspection of
Bulkhead a fiber optic cable or bulkhead:
Inspection NOTE:
• The inspection probe, tips, and adapters must be kept clean so that contaminants are not
Setup
transferred to the components being inspected. Compressed air can be used for this
purpose. Refer to the Fiber Optic Cleaning section on page 17 and Using Compressed Air
on page 26.
• To help keep the inspection probe, tips, and adapters clean in between inspections, rest
them in a clean dry place such as their storage case.
Step Action
1 Select an inspection tip based on the connector type and side being inspected.
Standard Patch Cord Tips
FBPT-U25M FBPT-U12M
(2.5mm – FC, SC, ST) (1.25mm – LC, MU)
Standard Bulkhead Tips
FBPT-SC FBPT-SC-APC FBPT-FC

Fiber or
Bulkhead
Step Action
Inspection
Setup 2 Attach the selected inspection tip to the probe. The Barrel Assembly (FBPP-
(cont inued) BAP1) must be used for standard bulkhead and patch cord tips.
3 Select the “Standard Tips (with BAP1)” TIP in the FiberChekPRO application.
4 Select the corresponding PROFILE in the FiberChekPRO application based on

the connector being inspected.
NOTE: The pre-configured profiles match the PASS/FAIL criteria specified in the
IEC-61300-3-35 visual inspection standard.
NOTE: There are special profiles for AT&T work. See ITE-7511.

Fiber or
Bulkhead
Step Action
Inspection
Setup 5 Inspect the connector or fiber.
(cont inued)
If . . . Then . . .
Inspecting a bulkhead Insert the probe into the connector
Inspecting fiber optic cable Insert the ferrule into the probe tip
6 Continue to Inspect and Test on page 14.

Transceiver Use the following steps to prepare the probe and FiberChekPRO application for inspection of
Inspection an XFP of SFP transceiver:
Setup When inspecting a SFP transceiver, the video probe must be used to determine the type of
the receive port, and the profile must be set accordingly.
Step Action
1 Select the long reach inspection
tip, FBPT-LC-L.
FBPT-LC-L
2 Attach the selected inspection tip to the probe:
NOTE: The long reach tip does NOT require the Barrel Assembly
3 Select the “Simplex Long Reach (-L) Tips” TIP in the FiberChekPRO application:

Transceiver
Inspection
Step Action
Setup
(cont inued) 4 Select Low Magnification in the FiberChekPRO application:
5 Insert the probe into the

transceiver port.
6 Focus and center the image

displayed in the FiberChekPRO
application.
NOTE: To focus, use the Focus

Control on the probe.

Transceiver
Inspection
Step Action
Setup
(cont inued) 7 Use the following table to determine which type of port you are viewing and
select the corresponding PROFILE in the FiberChekPRO application.
Example Image Type Profile to Select

SFP Fiber Stub
FIBER STUB
SFP Ball Lenses
FERRULE STOP
SFP Special/Flat
Lenses
FLAT LENS
8 Continue to Inspect and Test on page 14.

Inspect and Use the following steps to inspect a fiber optic connector after the setup steps are complete.
Test
Step Action
1 Focus and center the fiber end face
image displayed in the
FiberChekPRO application.
NOTE: To focus, use the Focus

Control on the probe.
The Focus Quality Meter displayed

by the FiberChekPRO application
can be used to achieve optimal
focus as follows:
• As the image comes into focus,

the length of the blue bar
increases.
• A red line will show the highest
level that the bar reaches.
• Optimal focus level is reached
when the blue bar is closest to the
red line at the highest point
achievable.
2 Run the automated analysis test by

either…
• Pressing the QuickCapture button

on the probe, or
• Clicking the TEST button on the
FiberChekPRO application

Inspect and
Test (cont inued)
Step Action
3 Examine the results when the test is complete. The results include:
• Overlay of the zones, defects, and scratches.
• Overall test result, and zone specific results (PASS or FAIL)
If the test. . . Then . . .

PASSED Continue inspection with next connector.
FAILED Perform the cleaning steps found in Fiber
Optic Cleaning on page 17.
Re-inspect after cleaning.
NOTE: Also refer to Appendix A on page 38 for examples of contamination

Inspect and
Test (cont inued)
Step Action
4 Enter port/fiber identifying
information in the comment area.
NOTE: If Job Map data is

available then copy and paste
the port/fiber assignment name
from the Job Map into the
comment area.
5 Repeat until all ports/fibers have been inspected.
If . . . Then . . .
There are more ports/fibers to Click Next Fiber and repeat this
inspect procedure.
NOTE: This will save the results to the

Group Report.
Inspections are complete Click Group Report to save all of the
test results.

Fiber Opt ic Cleaning
Cleaning The following procedures explain how to clean a fiber optic connector and fiber optic
Methods transceiver or bulkhead. These procedures should be followed each and every time fiber
optics is handled. Perform these steps before making a fiber optic connection.
Cleaning Best This section describes the best practices to be followed when cleaning fiber optic equipment.
• ICIC Rule:
Practices
− Always follow the ICIC rule (Inspect, Clean, Inspect, Connect) for all fiber end faces,
optical ports, and bulkheads.
• Dry Clean First:
− Dry clean first, up to three attempts.
− If still not clean, try up to two wet cleans as a last resort.
• Immediately Connect Fibers:
− Immediately connect fibers that have been cleaned and inspected.
− Re-inspect if not immediately connected.
• Use Dust Caps:
− Utilize dust caps or plugs when connectors are not in use.
− Make sure caps/plugs are clean.
− Re-inspect fibers even if covered with a dust cap.
• Wet Cleaning:
− Wet cleaning should be avoided. It may have long term effects on fiber connector end
faces.
− However, wet cleaning may be necessary to clean off certain contaminants such as the
wax that comes from the wax cord used to wrap and secure cables.
− Wet cleaning must be finished off with a dry cleaning wipe or stick to ensure that
evaporation rings and other contaminants are removed.
• Cleaning Materials:
− Use the recommended cleaning materials listed in Cleaning Materials on page 18.
• Cleaning Methods:
− Use the recommended cleaning methods. Refer Recommended Methods on page 20.

Fiber Opt ic Cleaning, Cont inued
Cleaning The tables below summarize the recommended cleaning tools and supplies. The tools and
Materials materials used may vary based on the number of items to be cleaned, application environment
(indoor, outdoor, or tower-top), and the availability of materials.
Refer to TK-0659 and ITE-0654 of the National Tool Room.
Kit Description
ITE-7136 Individually wrapped 99% pure isopropyl
alcohol wipes. Used as a source of alcohol
for wetting fiber end faces and other tools
(e.g. IBC, stick), or for cleaning jumper
connectors.
R-6197 Sticklers individually wrapped wipe for dry

jumper end face cleaning.
R-6126 Chemtronics QbE Fiber optic end face

cleaning sheets.
R-6127 Chemtronics ElectrO-Wash PX cleaner.

Used to wet R-6126 sheets and other tools
when wet clean is needed.

Cleaning
Materials
Kit Description
(cont inued)
ITE-7134A Pack of 5 individual Stickler port cleaning
sticks.
• ITE-7134: 1.25 mm (LC) sticks (green)
ITE-7135A
• ITE-7135: 2.5 mm (SC, FC, ST) sticks

(blue)
R-6143 Ultra pure duster can.
R-6166A Neoclean multi use fiber port or In Bulkhead

Cleaner (IBC).
• R-6166A: 1.25 mm (LC)
R-6167A
• R-6167A: 2.5 mm (SC, FC, ST)

ITE-7137B Optipop multi use fiber end face cassette
style cleaner. (Preferred over ITE-7137
Cletops.)
ITE-7137 Cletop multi use fiber end face cassette

style cleaner. (ITE-7137B Optipop is
preferred.)

Recommended The tables below contain the recommended cleaning methods, in order of preference, based
Methods on industry documentation and deployment experience. Use the methods in the preferred
order defined in the tables.
Item Connector Cleaning Note

1 Cassette Style Cleaners Useful for larger sized jobs (> 36 ports)
2 In Bulkhead (IBC) Cleaners With connector adapter tip.
3 Lint-free Sheet
4 Wet (alcohol followed by dry) Avoid wet cleaning if possible.
See Cleaning a Fiber Optic Connector on page 21 for detailed procedures.
Item Port Cleaning Note

1 In Bulkhead (IBC) Cleaners
2 Stick Cleaners
3 Compressed Air (no touch) Can also be used for connectors.
See Cleaning a Fiber Optic Transceiver or Bulkhead on page 25 for detailed procedures.
NOTE: The cleaning method used may vary based on the number of items to be cleaned,
application environment (indoor, outdoor, or tower-top), and the availability of materials.

Cleaning a Based on the method being used, proceed to the appropriate procedure:
• Using Cassette Style Cleaner on page 21
Fiber Optic
• Using In Bulkhead Cleaner (IBC) on page 22

Connector
If it is determined that wet cleaning is needed then go to :

• Wet Cleaning a Fiber Optic Connector on page 23
Using Cassette Use these steps to clean a fiber optic connector with a cassette style cleaner.
Style Cleaner One of the following tools is needed (or equivalent):
• ITE-7137B Optipop fiber end face cleaner (preferred)
• ITE-7137 Cletop fiber end face cleaner
NOTE:
• Never re-use the same space on the cleaning tape.
• Hold the connector as perpendicular to the cleaning tape as possible.
• Drag slowly and without too much pressure in the direction indicated on the tool.
Step Action
1 Open the shutter on the
cleaner by
squeezing/depressing the
lever.
NOTE: This also advances

the cleaning tape.
2 Drag the fiber end face across

the cleaning tape in the
direction indicated by the
arrow.
3 Rotate the connector 90 degrees and repeat Step 2, using a fresh section of
cleaning tape.
4 Inspect before connecting. Refer to Fiber Optic Inspection on page 7.

Using In Use these steps to clean a fiber optic connector with an In Bulkhead Cleaner (IBC).
Bulkhead
Cleaner (IBC)
One of the following tools is needed (or equivalent):
• R-6166A Neoclean IBC, 1.25 mm (LC)
• 61667A Neoclean IBC, 2.5 mm (SC, FC, ST)
Step Action
1 With the cap on, open the tip
on end of the cap.
2 Insert the connector into the

IBC tip.
3 Engage the IBC tool.

• For the R-6166A/61667A Neoclean IBC, push the tool toward the connector.
This both twists and advances the cleaning string.
• For other IBCs, squeeze/depress the trigger per manufacturer instructions.

Wet Cleaning a Use these steps to wet clean a fiber optic connector end face.
Fiber Optic Materials used:
• For wetting, one of the following:
Connector
− ITE-7136 99% alcohol wipe

− R-6126 QbE sheet with R-6127 cleaner
• For dry cleaning, one of the following:
− R-6126 QbE sheet (dry or dry section of sheet used for wetting)
− R-6197 Sticklers dry wipes
NOTE:
• Wet cleaning should be avoided if possible. It may have long term effects on fiber connector
end faces.
• Wet cleaning may be necessary to clean off certain contaminants such as the wax that
comes from the wax cord used to wrap and secure cables.
• Once a connector is wetted, the cleaning process should be completed with one of the
various dry cleaning sticks or wipes. If only the alcohol wipe is used to clean a connector,
wet alcohol now filled with contaminants will be left on the end of the connector. The wet
alcohol will evaporate and rings of dirt and contaminant will be left on the end of the fiber
end face.
• Never re-use the same space on a wipe/sheet.
• Hold the connector as perpendicular to the sheet as possible.
• Drag slowly and without too much pressure.
Step Action
1 If cleaning the entire connector (not just the end face) then continue to Step 2.
If cleaning just the end face then skip to Step 3.
2 Wipe the connector clean with a
wet wipe, then dry with a dry wipe.
3 If using the QbE sheets, first spray

a dime-size amount of the R-6127
cleaner on the top corner of a
sheet.
NOTE: The supplied pad can be

used to protect the box from the
cleaner.

Wet Cleaning a
Fiber Optic
Step Action
Connector
(cont inued) 4 Drag the connector face across the wet wipe/sheet several times. Each time,
rotate the connector 90 degrees.
OR
5 Drag the connector over the dry area several times. Rotate the connector 90
degrees each time.
NOTE: Each QbE sheet can be used for two connectors, Use the left half for
one, and the right half for the second.

Cleaning a Most types of ports can be cleaned using any of the procedures below. However, the Ferrule
Fiber Optic Stop (Ball Lens) type of port, which may be present on the receive side of an SFP
Transceiver or transceivers, can only be cleaned with compressed air. This type of port contains a lens for
Bulkhead focusing a wide input, which is more easily scratched than cleaned.
Refer to the Transceiver Inspection Setup procedure on page 11 to determine the type of port
that is being cleaned.
If the port is. . . Then . . .

SFP Ferrule Stop (Ball Lens) Continue to Using Compressed Air on page 26.
Do NOT use an IBC or stick.
anything else (bulkhead, XFP, SFP Continue to one the following procedures, as
Fiber Stub, or SFP Flat Lens) desired:
• Using In Bulkhead Cleaner (IBC) on page 25
• Using Sticks on page 26
Using In Use these steps to clean fiber optic transceivers or bulkheads with an In Bulkhead Cleaner
Bulkhead (IBC) tool.
Cleaner (IBC) NOTE: Do not use an IBC on SFP transceiver Ferrule Stop (ball lens) receive ports.
Materials used:
• Use the appropriately sized IBC for the connector being cleaned:
− R-6166A Neoclean for 1.25 mm LC connectors
− R-6167A Neoclean for 2.5 mm SC, and FC connectors
Step Action
1 Remove the entire cap from the IBC.
2 Insert the IBC into the bulkhead
or transceiver.

Using In
Bulkhead
Step Action
Cleaner (IBC)
(cont inued) 3 Engage the IBC tool.
• For the R-6166A/61667A Neoclean IBC, push the tool toward the connector.
This both twists and advances the cleaning string.
• For other IBCs, squeeze/depress the trigger per manufacturer instructions.
Using Sticks Use these steps to clean fiber optic transceivers or bulkheads with sticks.
NOTE: Do not use sticks on SFP transceiver Ferrule Stop (ball lens) receiver ports.
Materials used:
• Use the appropriately sized stick for the connector being cleaned:
− ITE-7134A Stickler port cleaning sticks for 1.25 mm LC connectors
− ITE-7135A Stickler port cleaning sticks for 2.5 mm SC, and FC connectors
Step Action
1 Insert the stick into the port while rotating the stick at the same time.
2 When the stick makes contact with the connector, apply slight pressure and
rotate the stick three full turns.
3 Remove the stick while rotating the stick at the same time.
Using Compressed air must be used to clean Ferrule Stop (ball lens) type receiver ports, which may
Compressed Air appear in SFP transceivers. (This type of port contains a lens for focusing a wide input, which
is more easily scratched than cleaned.)
These steps can also be used on all other port types and fiber optic connectors.
Material used:
• R-6143 Ultra pure duster can
Step Action
1 Position the tip of the nozzle extension as close as possible to the sleeve inside
the port without making contact.
2 Make three consecutive short blows into the port.

Det ermine Insert ion Loss of Cable
Fiber Optic To determine the insertion loss of a fiber optic cable, a known light source (SM or MM) and
Insertion Loss optical power meter must be used. The power meter must first be referenced (zeroed) to
Method eliminate any loss in test fiber optic cables and connectors. Then the fiber optic cable to be
tested is inserted between the light source and power meter.
There are three approved methods to reference the meter, using 1, 2, or 3 reference cables.
Use the 1 reference cable method when possible, since it introduces the least error. The 2
cable (or even 3 cable) method may be necessary to match up the test equipment connectors
to the cable under test. These procedures will cover the 1 and 2 cable methods, as they are
the most common.
1 Reference Cable 2 Reference Cables
NOTE:
• Follow ICIC rules for all connections. Refer to Fiber Optic Inspection on page 7.
• Do not turn off the power source or meter after referencing.
• Do not disconnect the reference jumper from the light source after referencing. The power
may be different each time the connection is made.

Det ermine Insert ion Loss of Cable, Cont inued
Insertion Loss The following equipment is used to measure the insertion loss of a fiber optic cable:
Test Equipment NOTE:
• Multimode testing is performed at 850 nm
• Single-mode testing is performed at 1310 nm
The table below contains the recommended optical light sources, and whether or not the kit
can be used for Multimode (MM) or Single-mode (SM) testing.
Kit Description MM SM
850 1310
9 9
nm nm
ITE-7117B JDSU OLS-36 Optical Light

Source
9 9
ITE-7117A Noyes OLS4 Quad Source
8 9
ITE-7117 Noyes OLS-2 Dual Single-
mode Optical Light Source
9 8
ITE-6550 Optical Light Source
Pictured with the required 850
nm Optical Source Module
(OSM) installed.
NOTE: The ITE-6550 should

NOT be used to measure
power; use it as an 850 nm
light source only.

Insertion Loss
Test Equipment The table below contains the recommended optical power meters, and whether or not the kit
(cont inued) can be used for Multimode (MM) or Single-mode (SM) testing.
850 1310
9 9
nm nm
ITE-7116 JDSU FI-60 Optical Power

Meter
9 9
ITE-7116B Noyes OMP-4, OMP4-4B,
ITE-7116A OMP4-4C, and OMP4-4D
Optical Power Meter
ITE-7116
NOTE:
• Some versions of OMP4
did not test down to 850 nm
• Refer to ITE-7116 of the
National Tool Room.

Insertion Loss
Test Equipment The following table contains the recommended jumper kits, and whether or not the kit can be
(cont inued) used for Multimode (MM) or Single-mode (SM) testing.
850 1310
9 8
nm nm
TK-0654 Multimode 62.5/125 mm

L3 (usually orange) Optical
Jumper Kit
8 9
TK-0654 Single-mode 9/125 mm
L2 (usually yellow) Optical
Jumper Kit
Component The following table shows the estimated loss (attenuation) for various components.
Estimated Loss
Component Wavelengt hs Nominal Loss

Single-mode Fiber 1310 nm 0.35 dB/km
1550 nm 0.2 dB/km
1625 nm 0.2 dB/km
Multimode Fiber 850 nm 3 dB/km
1300 nm 1 dB/km
Fusion Splice Single-mode (any λ) 0.02 – 0.1 dB
Mechanical Splice Single-mode (any λ) 0.3 dB
Connector Single-mode (any λ) 0.25 – 0.5 dB
Splitters 1:32 (any λ) – typical PON 17 dB
1:2 3.5 dB

Test Setup Use the following steps to setup the light source and power meter for insertion loss
Using 1 measurement using 1 reference cable.
Reference
Cable
Step Action
1 Select the appropriate optical light source, power meter, and jumper kit for the
cable under test (e.g. MM vs. SM). Refer to Insertion Loss Test Equipment on
page 28.
2 Make sure the power is off on the optical light source.
3 Inspect the connector on the optical light source and clean if needed.
4 Inspect the connector on the optical power meter and clean if needed.
5 Select one optical jumper and required connectors and/or adapters. Inspect
each end of each connector and clean if needed.
NOTE: Make sure the jumper is the correct type for the cable under test (e.g.
MM vs. SM).
6 Insert the jumper between the
optical light source and the
optical power meter.
7 Turn on the optical power source.

8 Select the appropriate test wavelength based on the cable under test:
• 850 nm for Multimode
• 1310 nm for Single-mode
9 Select dB for relative measurements (not dBm for absolute) on the optical
power meter.

Test Setup
Using 1
Step Action
Reference
Cable 10 Press the “Ref” button on the optical power meter to zero the setup, UNLESS
(cont inued) the customer requires otherwise. See note below.
NOTE: AT&T does not allow zeroing. The report must state the initial dB and
final dB reading. In this case, record the initial reading.
11 Continue to Insertion Loss Measurement on page 34.
Test Setup Use the following steps to setup the light source and power meter for insertion loss
Using 2 measurement using 2 reference cables.
Reference
Cables
Step Action
1 Select the appropriate optical light source, power meter, and jumper kit for the
cable under test (e.g. MM vs. SM). Refer to Insertion Loss Test Equipment on
page 28.
2 Make sure the power is off on the optical light source.
3 Inspect the connector on the optical light source and clean if needed.
4 Inspect the connector on the optical power meter and clean if needed.
5 Select two optical jumpers and required connectors and/or adapters. Inspect
each end of each connector and clean if needed.
NOTE: Make sure the jumper is the correct type for the cable under test (e.g.
MM vs. SM).

Test Setup
Using 2
Step Action
Reference
Cables 6 Insert the two jumpers
(cont inued) between the optical light
source and the optical
power meter.
7 Turn on the optical power source.

8 Select the appropriate test wavelength based on the cable under test:
• 850 nm for Multimode
• 1310 nm for Single-mode
9 Select dB for relative measurements (not dBm for absolute) on the optical
power meter.
10 Press the “Ref” button on the optical power meter to zero the setup, UNLESS
the customer requires otherwise. See note below.
NOTE: AT&T does not allow zeroing. The report must state the initial dB and
final dB reading. In this case, record the initial reading.
11 Continue to Insertion Loss Measurement on page 34.

Insertion Use the following steps to measure the insertion loss of a fiber optic cable.
Loss Example for 1 reference cable:
Measurement
Example for 2 reference cables:
Step Action
1 Verify the test setup as described in Test Setup Using 1 Reference Cable or
Test Setup Using 2 Reference Cables above.
2 Inspect and clean both ends of the cable under test.
3 Select any additional connectors or adapters needed to splice in the cable
under test. Inspect and clean if needed.
4 Insert the cable under test as shown in the examples above:
• For 1 reference cable, insert the cable under test between the jumper cable
and the power meter.
• For 2 reference cables, insert the cable under test between the two jumper
cables.
NOTE:
• Use caution not to look directly into the end of the fiber optic cables.
• Do not turn off either the light source or the meter.
• Do not disconnect the reference jumper from the light source. The power
may be different each time the connection is made.
5 Read the insertion loss measurement on the optical power meter and record
as required.

Insertion Loss See the following reference for additional information on fiber optic cable loss measurement:
• The Fiber Optic Association, Inc. “5 Standard Ways to Test Fiber Optic Cables”
Testing
References < http://www.thefoa.org/tech/ref/testing/5ways/fiveways.html>
• Loss Testing Specifications:
− ANSI/TIA/EIA-526-7, OFSTP-7 Measurement of Optical Power Loss of Installed Single-
Mode Fiber Cable Plant
− ANSI/TIA/EIA-526-14A, OFSTP-4 Optical Power Loss Measurement of Installed
Multimode Fiber Cable Plant
− IEC 61280-4-1 Multimode fibre-optic cable plant attenuation measurement
− IEC 61280-4-2 Single-mode fibre-optic cable plant attenuation
− ISO/IEC-TR-14763-3 Testing of optical fibre cabling

Troubleshoot ing
General This section explains some basic techniques for troubleshooting fiber optics.
Visual Fault The Visual Fault Locator (VFL) is a troubleshooting tool that can be used to locate damage or
Locator broken fiber. It also can be used to trace fiber from one end to another. Use the following
steps to locate a damage or broken fiber or trace a fiber.
Step Action
1 Ensure the cable under test is clean and free of any contamination.
2 Insert the ferrule of the fiber
under test into the VFL.
NOTE: An adapter may be

needed.
3 Power on the VFL.
4 Select “continous” or “pulse” light

Troubleshoot ing, Cont inued
Visual Fault
Locator
(cont inued) Step Action
5 If a fiber is bent too sharply, damaged
or broken the light from the laser will
shine through the fiber jacket.
NOTE: Light may shine through the

fiber jacket within the first 12 inches
from the connector. This is not an
indication of a faulty fiber optic cable.
Macro Bend loss can occur when the

fiber is bent beyond the recommended
bend radius.
Macro Bend
Micro Bend loss can be caused by

pinching or squeezing of the fiber, or by
imperfections or cracks in the fiber.
Micro Bend
6 Verify that the red light is passing

through the entire fiber optic cable.
NOTE: Use a white fiber dust cap or

point the connector at a white piece of
paper to see the red light. This test
can also be used for tracing fiber optic
cables.
Tracing Long To trace a very long fiber optic cable, use the Power Meter and Light Source setup to measure
Cables Insertion Loss. This test works well for bright outdoor applications where you can not see the
red light from a VFL.
NOTE: Refer to Determine Insertion Loss of Cable on page 27.

Appendix A
Contamination These images describe various contamination conditions.

Examples
Illustration Description
A Clean Connector Illustration shows a clean single-mode
ceramic endface at 200x magnification.
NOTE: Sometimes the core is not

illuminated.
Clean Multifiber Connector with Acceptable Illustration shows a clean multimode MT

Shadowing connector. Notice that there is a small
amount of acceptable shadowing along
the edge of the cladding.
NOTE: There is more than one fiber

visible at 200x magnification and
sometimes the core is not illuminated.
Connector with Dust Illustration shows a connector with dust

particles spread across the surface of the
endface that needs cleaning.

Appendix A, Cont inued
Contamination
Examples
(cont inued) Illustration Description
Connector with Liquid Contamination Illustration shows a connector with liquid
contamination that needs cleaning.
Connector with Liquid Contamination Illustration shows a connector with liquid

contamination that needs cleaning.
Connector with Alcohol Residue Illustration shows a connector with alcohol

Contamination residue that needs cleaning.

Contamination
Examples
Connector with Liquid Contamination Illustration shows a connector with small
droplets of liquid contamination that needs
cleaning.
Connector with Dry Residue Illustration shows a connector with a dry

residue that needs cleaning.
Connector with Oil Residue Illustration shows a connector with an oil

residue that needs cleaning.

Contamination
Examples
Connector with Scratches Illustration shows a connector with
scratches. These scratches are not
detrimental to the endface and does not
clean off.
But, deep scratches that appear to cross
the fiber-optic core can cause signal loss.
Connector with Chipped Cladding and Illustration shows a connector with

Excessive Epoxy damage to the cladding. Cleaning cannot
remove damaged cladding.
A small amount of epoxy around the
cladding is allowable, but this shows
excessive epoxy around the cladding that
does not clean off.
This connector must be replaced.
Damaged Connector Illustration shows a 1.25 mm ferrule that

has been over chamfered.
The connector must be replaced.

Appendix B
Inspection If the inspection probe described in the Fiber Optic Inspection section is not available then a
Probe probe with equivalent or better specifications must be used.
Requirements The inspection probe used must:
• Allow adherence to the IEC-61300-3-35/IPC-8497-1 standards for defect detection:
− Low resolution microscopes must have a minimum field of view of at least 250 μm and
capable of detecting low-contrast defects of 2 μm in size.
− High resolution microscopes must have a minimum field of view of at least 120 μm and
capable of detecting low contrast scratches of 0.2 μm in width and 0.003 μm in depth.
− See IEC/IPC Standards and Inspection Criteria below.
• Support the use of adapter tips for compatibility with 1.25mm and 2.5mm connectors and
ports.
• Use video microscopy (as opposed to direct view) with the ability to measure observed
defects.
It is recommended that the inspection probe also support:

• Automated testing and contamination detection to eliminate human subjectivity, with:
− Built-in PASS/FAIL criteria based on IEC-61300-3-35 standards.
− Configurable PASS/FAIL settings to meet specific customer requirements.
• Test report generation and archiving to provide results to the customer.
IEC/ IPC IEC-61300-3-35 Fibre optic connector endface visual and automated inspection
Standards The IEC-61300-3-35 standard describes methods and criteria for inspecting fiber optic
connectors. It defines zones within the fiber endface and specifies allowable defect size and
placement within these zones to be able to quantitatively determine if the component should
pass or fail inspection. These methods and criteria apply to both visual and automated
inspection.
IPC-8497-1 Cleaning Methods and Contamination Assessment for Optical Assembly
Like IEC-61300-3-35, the IPC-8497-1 standard describes methods and criteria for inspecting
fiber optic connectors. IPC-8497-1 also describes processes used by the industry to clean
optical connections, as well as ways to evaluate these methods to determine which is best for
a particular application.

Appendix B, Cont inued
Inspection The SM fiber inspection criteria are the same for the IEC and IPC standards. The MM fiber
Criteria criteria are slightly different. The figures below show the zones and acceptance criteria
presented in the IEC-61300-3-35 standard.
Figure 4: Inspection Zones (SM endface)
Figure 5: SM and MM Visual Inspection Criteria (IEC-61300-3-35)

This page intentionally left blank.

GCD Networks

December 10, 2012
Alcatel-Lucent
GMRE Features for OCS application
Table of Contents
General ............................................................................................................ 2
Description .................................................................................................... 2
Feedback ...................................................................................................... 2
GMRE Service Types ............................................................................................. 3
Soft permanent Connection ................................................................................ 3
Source based restoration ................................................................................... 4
Guaranteed restoration ..................................................................................... 4
SNCP protected service ..................................................................................... 4
Protection and Restoration Combined ................................................................... 5
Shared Risk Groups .............................................................................................. 6
Introduction ................................................................................................... 6
SRG Diversity .................................................................................................. 7
Link Latency ...................................................................................................... 8
Introduction ................................................................................................... 8
GMRE Alarms ..................................................................................................... 9
Alarm Types ................................................................................................... 9
List of Tables

Table 2: Node alarms ..................................................................................................... 9
Table 3: Sub network connection (SNC) alarms .................................................................... 10
Table 4 Control plane communication alarms ...................................................................... 12
IEH 611, Section 170 GMRE Features for OCS application
General
aimed for understanding of features and functions of the GMRE application. The intention is
for the user to be able to differentiate between various types of services and restoration
mechanisms.

1830 PSS-36 5.1
1830 PSS-64 5.1
1390 NPT 5.1
1350 OMS 10.2

GMRE Features for OCS application IEH 611, Section 170
GMRE Service Types
Soft permanent A soft permanent connection (SPC) is an end to end service between a source node and
Connection destination node which may or may not go through intermediate nodes. An SPC is setup by
the 1350 OMS management platform and can be defined as two basic services types.
Unprotected
Protected
Unprotected: This is an end to end path which may contain risk, cost and node constraints
but upon a link failure that traffic will not be restored. A typical application for such service is
low priority traffic containing data which is classified as best effort or zero priority. Once the
link failure is cleared the path is in-service again.
Protected: This is an end to end path consisting of risk, cost and node constraints but will
establish alternate paths in the network if link failure occurs. There are various types of service
options for a protected path. The table below shows the two basic service types:
Service Types GMRE Service Type

Basic Unprotected
Source Based Restoration (SBR)
Guaranteed Restoration (GR)
Network SNCP (Sub network connection protection)
Protection and Restoration Combined (PRC)
It is important to note that the terminology of Service types is different in 1350 OMS. The
correlation is listed in the table below.
GMRE Service Naming in 1350 OMS

Unprotected No Restoration
Source Based Restoration (SBR) Upon Failure
Guaranteed Pre-calculated
SNCP Protected with No Restoration
Protection and Restoration Combined (PRC) Protected with Restoration

GMRE Service Types, Continued
Source based Source Based Restoration (SBR) is a path restoration mechanism in which a failed path is
restoration restored once the path is in failed condition. This method is also known as “post-calculated
restoration” where a backup path is calculated and established once the active path is
disrupted. The time to calculate the backup path adds to the restoration time of the circuit
hence SBR based services are slower in restoration compare to other service types. It is
important to note:
The active path, as defined by the 1350 OMS is referred to as the „nominal’ path; this route
cannot be changed by the control plane and after restoration of the network failure, the
traffic will be moved back to this route.
In case of failure, the source node calculates a backup path.
The backup path is Shared Risk Group (SRG) diverse. If that is not possible then it is at
least TE link diverse to the point of failure.
A backup path may re-use existing sections of the original or active path to recover allowing
for efficient use of network resources.
Once the link failure that led to restoration is repaired, a nominal path is defined and this
nominal path is –re-activated.
Guaranteed Guaranteed Restoration (GR) is a path restoration mechanism in which the backup path is
restoration pre-calculated and registered at the time of the active path setup. When a failure occurs, the
source node switches the failed path on to the back-up path. The switching time for this type
of restoration is faster than SBR service. It is important to note:
Source node monitors the health of both the active and backup path at all times.
Once failure is repaired, a nominal path is defined and service is reverted to the nominal
path.
If an inactive backup path fails, the source node calculates and registers a new backup
path.
If a new backup path is not possible an indication is sent to the management system that
guaranteed restoration is not possible. At this time SBR restoration is used as fall back upon
failure.
Backup path is fully SRG diverse to provide high reliability
SNCP protected Sub Network Connection Protection (SNCP) is a restoration mechanism which consists of 1+1
service protection at the path level. It is similar in operation of a UPSR/SNCP where two redundant
active paths are setup between source and destination nodes. The protection switching is
performed by the NE hardware in case one of the path fails. If both paths fail no further
restoration is performed. It is important to note:
Both paths of an SNCP service are SRG diverse.
Both paths of an SNCP operate as unprotected service.
Switching time for SNCP is fastest compared to other services
Protection switching is unidirectional

GMRE Service Types, Continued
Protection and Protection and Restoration Combined (PRC) restoration mechanism is similar to SNCP but
Restoration with extended restoration capabilities to offer the highest level of protection to any services
Combined defined within the GMRE domain.
A PRC service is a combination of SNCP and SBR services. Initially the service is setup like
an SNCP and once one leg fails, SNCP switches over to the protecting path and the failed
path is restored by the control plane as an SBR service. If a subsequent failure occurs, the
path will be switched onto the SBR protection path and a new SBR will be established.

Shared Risk Groups
Introduction The purpose of Shared Risk Groups (SRGs) is to provide diversity to a Label Switch Path
(LSP) such that the protecting path may not have similar risk as the working or active path. For
example, if a node has two links to the neighbor node and both links are on ports located on
the same I/O board then both links share the same risk. The reason is that if the I/O board fails
and needs to be replaced with a spare one then both links will suffer an outage while the
board is being replaced.
A risk can be other factors too. Such as:
A common fiber cable
A common fiber duct
Any common physical entity that may disrupt service such as a river bed, a repeater
location, common WDM link etc.
Thus, the SRG concept is designed to ensure failure diversity between paths in a transport
network. The SRG values are assigned to links as positive integers. The value of the integer
does not specify whether a risk is higher or lower, for example a link with risk value of 3 does
not indicate that it has greater risk than that of a link with value of 1 or 5. It only indicates that it
has a risk associated to some property.
An important thing to note is that each fiber goes through various points in a network which
can be identified for risk allocation; hence a link may have more than one risk associated with
it. As a result this concept is known as Shared Risk Group.
Below is an example of how SRG attributes are associated with a TE link.
Figure 1 Example of SRG attributes

Shared Risk Groups, Continued
Introduction The SRG values for the link from NE A to NE B (Green Cable only) is {1,3,5,8}. The green
(continued) cable may contain various fibers but they all share the risk if any of the three conduits were
crushed or broken. It is important to note that not all three conduits maybe present in the
same location hence it is vital to identify every point in the link which may have risk associated
with it that may impact more than one link.
SRG Diversity Two paths are defined to be fully SRG when the intersection of the set of SRG values is
computed and the result is empty. This formula ensures that both paths do not have any SRG
values in common.
Figure 2 Example of fully SRG Nominal and Backup path

From the example above:
SRG of nominal path is: {1,2,3}
SRG of backup path is: {4,5,6,7,8}
Intersection of both sets: {1,2,3} n {4,5,6,7,8} = empty
It is important to note that when assigning SRG values to ports/links they must be consistent
with both ends of the link. Network and traffic planners should design the set of SRG values
for their network depending on most likely failures or incidents that may happen. This will
reduce the number of values in the SRG group hence increasing the flexibility in resource
allocation for services.
The shared risk groups defined during the network planning stage must be defined on the
1350 OMS during TE link definition to ensure the network topology is deployed in accordance
with the design parameters to ensure there is sufficient protection bandwidth available as
defined by the NPT planning tool.

Link Latency
Introduction Latency is an attribute that may be assigned to a link. This value is only assigned manually
and is not measured automatically. The purpose of latency is only to be used as a constraint
parameter when LSP are being setup.
Latency is provisioned in microseconds. An end to end latency of 0 means that latency is
not used for constraint based routing.
GR Service: In case of GR services, latency is used as a constraint for establishing both the
active and back up path independently.
TE link latency: Latency defined for a TE link in microseconds
Access link latency: This is latency for the drop ports and defined as the time in
microseconds caused by the drop ports at the source and destination nodes.
Calculated latency: This is the total sum of the TE link latency and Access link latency. The
source node uses this value when constraint decision is made for latency.
A violation of the latency constraint does not lead to restoration or revision action for the
service and it stays on its active route. During setup of a path, the control plane will select the
least cost route if the latency threshold is met. If the latency threshold is violated, then the path
will not be setup.

GMRE Alarms
Alarm Types GMRE control plane communicates with the 1350 OMS to report alarms and conditions
spontaneously. The alarming is classified in three basic types
Node alarms
Sub network connection (SNC) alarms
Control Plane communications alarms
Table 2: Node alarms

Alarm Description Likely cause of alarms
NE not reachable Indicates that the Typically this alarm is
communication between the caused if the NE has a
GMRE and the managed problem, for example due to
NE is disturbed. a process restart.
Note that the GMRE will
recalculate inactive backups
of GR services that are
crossing this node.
GMRE Degraded Indicates that GMRE fully A GMRE process is down or
operational communication between
GMRE processes is
disturbed.
GMRE in active traffic GMRE is currently in GMRE is in migration state
migration state migration preparation and deactivated
when migration is cancelled
or successfully finished.
GMRE in automatic GMRE is set to manual This is done usually during
restoration disabled mode restoration by operator maintenance activities or
recovery scenarios to stop
GMRE from doing
restoration.
Logical node not reachable Indicates that the OCS shelf This alarm is raised during a
is not reachable. process restart.

GMRE Alarms, Continued
Alarm Types
(continued)
Table 3: Sub network connection (SNC) alarms
Alarm Description Likely cause of alarm

Active failed – APE failed Indicates that APE has point This alarm is raised when
of failure restoration is triggered for
the current route.
Active failed – Cross The active route has failed This alarm is raised when
connection problem due to a cross connection restoration is triggered for
problem. A backup path will the current route. Point of
be established failure is also included.
Active failed - preemption Active route of a service has A restoration event has
been preempted. been triggered causing a
backup path to be setup for
active path.
Active Failed – Transmission problem has A restoration event has
Transmission problem caused the active path to been triggered and backup
fail. path is setup for active path.
Active failed – Unprotected An unprotected LSP has An unprotected LSP is failed
failed or Failed but connected.
Active unavailable Current route of the LSP is For unprotected, SBR or GR
failed services, current route is
failed.
For SNCP or PRC services,
both active and backup
have failed.
Latency Violation Indicates that the nominal The LSP is setup even if it
route of the LSP violates the violates the latency
specified latency constraint. threshold, but alarm is
raised to warn the operator.
Link diversity violation Current route of the LSP, no Alarm will be cleared once
fully link-diverse backup the next re-route where full
could be found link diversity is achieved.
Nominal unavailable – Nominal route failed due to This condition is cleared
Transmission problem a data plane problem when failure on the nominal
route is repaired.
Ready to revert Nominal resources are In case of manual reversion,
available again and a this is the trigger for the
reversion can be done operator
Reroute not possible For SNC, no backup route Only occurs when
can be found or activated restoration is enabled for
SNC. Add link to the
network to clear this
situation.

Alarm Types
(continued)
Alarm Description Likely cause of alarm
SNCP degraded The LSP is currently no 1+1 This alarm is only for SNCP
path protected and PRC services. Indicates
that main, spare or both legs
of the SNCP are failed.
SRG violation Indicates that both legs of LSP configured with LSP
the LSP are not SRG diversity constraint. Nominal
diverse. May also be raised route overrules the SRG
after a link fail incident and constraint. Link failure leads
new backup is not SRG to less resources such that
diverse. two legs of the SNCP use
same SRG.
Test mode enabled The LSP is in test mode and Implies the enabling of PM
frozen to its current route data collection along the
current route.

Alarm Types
(continued)
Table 4 Control plane communication alarms
Alarm Description Likely cause

RSVP degraded Indicates that the The RSVP control plane
communication to the interface is set to down by
neighbor node for RSVP the GMRE if the RSVP
traffic is not working Hellos time out.
Check: IP communication
between nodes or
incompatible configuration
of RSVP timers between
adjacent nodes.
RSVP down RSVP communication to The administrative state of
neighbor node is down the RSVP is set to down
DPR OSPF routing protocol is Occurs during OSPF startup
down. when OSPF hellos are
exchanged and working
properly but no OSPF
database has been
exchanged.
DPR down Communication to the IP communication
adjacent node for OSPF problem between
data plane is not working neighbor nodes
Incompatible DPR timer
configured for adjacent
nodes
Administrative state of
DPR interface is down
DPR NetworkVersion GMRE active network May happen during software
Mismatch version of adjacent nodes upgrade. All NEs in the
does not match the active network should be on the
network version of local same active network version
node of GMRE.
InBandComm degraded Problem with ECC channel ECC problem likely due to
of the ECC protection group problems on corresponding
OTH link.
InBandComm down IP communication via ECC All ECCs of the protection

protection group is not group are not working.
working

GCD Networks

December 10, 2012
Alcatel-Lucent
GMPLS Network Planning and Requirements
Table of Contents
General ............................................................................................................ 2
Description .................................................................................................... 2
Feedback ...................................................................................................... 2
GMRE Interface Architecture .................................................................................. 3
OCS Shelf addressing and assignment .................................................................... 3
Interface Index ............................................................................................... 3
Network Planning Guidelines .................................................................................. 5
Network Size .................................................................................................. 5
Control Plane IP addressing ................................................................................ 5
Excluded addresses and address ranges .................................................................. 5
Recommendations............................................................................................ 5
Example of addressing scheme ............................................................................ 6
TE Link, SRG and Metrics Planning ........................................................................... 7
TE links ......................................................................................................... 7
SRG ............................................................................................................. 7
Latency ........................................................................................................ 7
Cost Metric .................................................................................................... 7
Network Drawing and Tables .................................................................................. 8
Organizing Information ...................................................................................... 8
Network Diagram ............................................................................................. 8
System Information .......................................................................................... 8
TE Link Assignment .......................................................................................... 9
Service Assignment .......................................................................................... 9
List of Tables

Table 2 Example of a node numbering scheme for up to 260 nodes ............................................. 6
IEH 611, Section 200 GMPLS Network Planning and Requirements
General
aimed for understanding of limitations of parameters used in the planning of GMRE based
network.

1830 PSS-36 5.1
1830 PSS-64 5.1
1390 NPT 5.1
1350 OMS 10.2

GMPLS Network Planning and Requirements IEH 611, Section 200
GMRE Interface Architecture
OCS Shelf In R5.1, the Alcatel-Lucent 1830 PS-S64/36 supports single or multi shelf configuration in a
addressing and single node. In both cases the GMRE software running on the FLC of the main shelf manages
assignment all the shelves in the node. While each node will have a single node ID, the following rules
must be understood and followed.
Each GMRE node must have one node IP address and one node ID. The node ID must be
unique integer in IPv4 format and must not be repeated anywhere in the GMRE network.
This node ID is called Control Plane node ID (CPNodeId).
The node IP address and CPNodeId can be identical, however, two or more nodes in the
network cannot have same CPNodeId. Only the node IP address of the node can be
modified but CPNodeId is permanent hence should be planned very carefully.
CPNodeId is provisioned by GMRE operator using CLI command before the GMRE node
administrative state is up. The parameter cannot be provisioned by 1350 OMS.
A node may consist of more than one shelf
Each shelf is considered a unique logical node with its own data plane node ID (DPNodeId).
DPNodeId is provisioned by GMRE operator using CLI for each shelf in the node and
cannot be provisioned using 1350 OMS. DPNodeId maynot be left blank and cannot be
auto-created.
The DPNodeId can be freely assigned but must not be repeated in any other shelf in the
GMRE network.
Databearer ports are identified with the DPNodeId plus slot and port location by OSPF-TE
protocol.
The ODU switching capability is limited to a single shelf from I/O boards located in the shelf
only.
Optical links between two neighbor shelves may be bundled and defined as a Traffic
engineered (TE) link.
Interface Index The following table shows the GMRE Index scheme for protocol and link interfaces.
Type of Interface Index Range

CPNeighbor 2000 - 2999
RSVP-TE NNI 3000 - 3999
RSVP-TE UNI 4000 - 4999
DPR interfaces 5000 - 5999
LMP interfaces 7000 - 7999
IFIPCC interfaces 9000 - 9999

GMRE Interface Architecture, Continued
Interface Index
(continued)
Type of Interface Index Range
OOFTunnels 11000 -11999
Subnode ≥101000000
Using the following numbering scheme: rss000000
r = rack
ss = subrack
Databearer Possible values
≥ 101010101, for example 101020101
using the following numbering scheme:
r = rack
ss = subrack
bb = board/slot
pp = port
tt = termination point: tt=01
n = number (from pool)
Examples:
OTUn: rssbbpp01
ODUn rssbbpp01 (transp. STM-N, GbE)
ODU2 virtual interface: rss92nnnn (nnnn=0001-0384)
ODU3 virtual interface: rss93nnnn (nnnn=0001-0064)
ODU3E2 virtual interface: rss95nnnn (nnnn=0001-0064)

Network Planning Guidelines
Network Size The recommended size of the GMRE network is up to 260 nodes where each node can have
up to 32 neighbor nodes.
Control Plane IP All GMRE protocols are IP based hence a set of IP addresses are defined for each GMRE
addressing node. Following is a set of IP addresses that have to be provisioned in each GMRE node:
GMRE node IP address: This IP address is used for the communication of the GMRE node
when OSPF-TE, RSVP-TE and LPM protocols communicate with other nodes in the
network.
Control Plane node ID: This ID is used for identification of the GMRE node.
Data plane node ID: This ID is used to identify resources: TE links and Data links.
GMRE notify address: The IP address is used to signal failures on downstream nodes to
source node.
GMRE Management address: This address is used for COBRA communication between
1350 OMS and GMRE.
NE IP address Usage for GMRE

Control plane IP address (CPIP) GMRE node IP address
IP address of the active FLC GMRE notify address
GMRE Management address
Excluded The following IPv4 addresses or address ranges cannot be used:

addresses and
0.0.0.0 – Not an IP address
address ranges
100.0.0.0 - 100.255.255.255 – Reserved for NE-internal communication.
101.0.0.0 - 101.255.255.255 – Discouraged to be used for external purposes; there might
be legacy NEs, which use this range for internal purposes.
127.0.0.0 - 127.255.255.255 – Reserved by the Internet Assigned Numbers Authority
(IANA) as loopback addresses.
224.0.0.0 - 255.255.255.255 – These are multicast/broadcast addresses, or reserved by the
IANA “for special use”; see also RFC3330, Special-Use IPv4 Addresses.
169.254.0.0 - 169.254.255.255 – Reserved for the communication with the Zero Installation
Craft (ZIC).
Recommendatio
ns
Ensure that GMRE node and notify addresses are correctly planned as they cannot be
modified once GMRE is activated on the node. The only way to modify it is to rebuild the
node from initial software installation which is traffic effecting.
Never attempt to modify the GMRE node and notify addresses after the activation of the
GMRE node as it will result in failure of the GMRE application.
The Control plane IP address must be unique and diverse to all subnets.

Network Planning Guidelines, Continued
Recommendatio The GMRE node IP address must be unique within the GMRE network.
ns (continued)
The IP address of the active FLC must be in a common subnet with other FLC cards in the
GMRE network.
The loopback IP address must also be configured in the NE so that it can be used by the
GMRE application.
Example of For each node, a subnet needs to be defined containing the following IP addresses:
addressing
The IP address of the FLC card in the protected slot (FLC A; slot 73 in the PSS-64 subrack,
scheme slot 23 in the PSS-36 subrack).
The IP address of the FLC card in the protecting slot (FLC B; slot 75 in the PSS-64 subrack,
slot 40 in the PSS-36 subrack).
The IP address of the currently active FLC. This address is independent of the slot position,
it follows the active FLC on each FLC equipment protection switch.
Note: These addresses need to be configured for the FLC cards of the main shelf only. As this
subnet only contains IP addresses related to the FLC cards, it is also called “FLC subnet”. The
FLC subnet can, for example, be of the form 10.n1.n2.0/24 where the combination of n1 and
n2 represents the node number as illustrated in the following table. The CIDR notation “/24”
indicates a subnet mask with a length of 24 bits, that is 255.255.255.0 in dotted decimal
notation.
Table 2 Example of a node numbering scheme for up to 260 nodes
The host part in the FLC subnet could be used as follows:

0: Network; 1: FLCA; 2: FLCB; 3: Active FLC; 4: Local CT
254: Gateway router; 255: Broadcast

TE Link, SRG and Metrics Planning
TE links The TE links between two neighbor nodes are a group of databearers that link the two nodes.
Hence a low number of TE links keeps the routing subsystem optimized as all databearers
within the TE link are seen as equivalents from a GMPLS routing perspective.
All databearers using the same physical routing attributes (i.e. cable ducts, multicore optical
fiber) must be assigned to the same TE link along with associated SRG attributes to ensure
correct databearer recovery during a network failure.
Note: TE links are defined by the 1350 OMS as part of the GMPLS NPA creation process.
SRG The SRG value of a link or TE-link identifies each of the cable ducts with a unique number.
Minimum number of SRG per link= 0
Maximum number of SRG per link= 32600
Minimum value of SRG = 1
Maximum value of SRG = 2147483647
Note: SRGs are defined during the TE link configuration on the 1350 OMS as part of the
GMPLS NPA creation process.
Latency Minimum value of latency = 0

Maximum value of latency = 1000000 micro seconds
Note: Latency attributes are defined by the 1350 OMS as part of ODU trail/path creation
process.
Cost Metric During setup of a LSP, the GMRE application will compute the route based on the least cost of
end to end path.
Minimum value of cost per link = 1
Maximum value of cost per link = 255
Note: TE link cost attributes are defined by the OMS as part of the NPA creation process.

Network Drawing and Tables
Organizing As seen in the previous pages, the data and parameters for GMRE network are significant in
Information number and hence information must be carefully organized and maintained. Accurate
drawings and traffic tables not only help network planners but also are very useful in
provisioning traffic and troubleshooting. Hence the following items should be prepared as first
step in planning for GMRE network.
Network Diagram
System Information per node
TE Link assignments
Service assignment
Network It is good practice to develop a complete network diagram for the GMRE network. It must
Diagram include the following:
Node name or Target ID (TID)
GMRE IP address
Active FLC IP address
I-NNI Port Access ID (AID) and its interface rate for each link e. g 44-1; OTU2
Client Port AID with interface type and rate.
Switch capacity of node.
TE links.
SRG per link and per TE link.
Cost for each link.
Latency for each link.
Login information of the systems should not be written on the diagram.
System Each system has its properties that should be carefully planned prior to implementing the turn-
Information up of the network. Some basic parameters to plan are:
Node TID
Active FLC IP address
FLCA IP address
FLC IP address
GMRE IP address
Data plane node ID
Loop back IP address
Gateway IP address
1350 OMS IP address
Matrix capacity
Normal/Secure mode operation
Defined user logins
Port group information

Network Drawing and Tables, Continued
TE Link TE link information should be maintained in table form. It must contain the following:
Assignment TE link ID defined by 1350 OMS
A and Z node port AID for each link
Cost
SRG
Service This information is the mostly used after the GMRE network has been turned up. The traffic
Assignment mapping table should include:
LSP Description
LSP Index
Source port AID and TID
Destination port AID and TID
Connection type (SBR, GR etc)
Cost constraint
SRG constraint
Latency constraint
Node diversity


GCD Networks

December 10, 2012
Alcatel-Lucent
Network Element GMPLS Configuration Procedure
Table of Contents
General ............................................................................................................ 2
Description .................................................................................................... 2
Feedback ...................................................................................................... 2
Preparation ....................................................................................................... 3
System Overview ............................................................................................. 3
Required Tools and Applications .......................................................................... 3
Flow Chart ........................................................................................................ 4
GMRE Enable Process ........................................................................................ 4
Loop Back IP and GMRE IP Addressing ....................................................................... 5
Provision Loop Back IP Address ............................................................................ 5
Provision Control Plane IP Address ........................................................................ 7
Activate GMRE ................................................................................................... 9
CLI Session ..................................................................................................... 9
Activate GMRE .............................................................................................. 12
Neighbor Discovery ............................................................................................ 14
Overview ..................................................................................................... 14
Neighbor Node Verification .............................................................................. 14
1350 OMS ........................................................................................................ 15
Handover Process .......................................................................................... 15
List of Tables
IEH 611, Section 300 Network Element GMPLS Configuration Procedure
General
Description This section provides the field engineers of 1830 PSS systems with the knowledge base and
the step by step process of enabling GMRE application and verifying its correct operation.

1830 PSS-36 5.1
1830 PSS-64 5.1
1390 NPT 5.1
1350 OMS 10.2

Network Element GMPLS Configuration Procedure IEH 611, Section 300
Preparation
System In order to start GMRE application in the 1830 PSS-64/36 systems, it is important to complete
Overview the system commissioning as defined in the IEH 610 and ensure NE is alarm free.
Ensure that the following items have been correctly provisioned in the NE.
Item System Information Yes/No

1 Site Identifier
2 Shelf / Matrix Size
3 Management IP address
4 Gateway IP address
5 I/O Board assignments
6 Client and I-NNI port assignments
Do not proceed if any of items in the list above are not provisioned or available.
Required Tools The following tools and applications will be used during the GMRE configuration.
and ZIC: Zero Installation Craft. Included within the NE.
Applications
Debug Tool: Mini USB to Serial connection. For debugging and troubleshooting
SSH terminal: For CLI session. Any SSH application such as Putty.

Flow Chart
GMRE Enable The process to activating GMRE is comprised of two parts. First is to verify and provision
Process parameters using ZIC and then issue CLI commands using an SSH terminal. Once the GMRE
is activated neighbor node and port information is verified before the network is handed over
to 1350 OMS for provisioning of links and traffic.
The flow chart below shows the overview of the GMRE activation process.
Figure 1. GMRE Activation Process
Activate GMRE
Verify
Verify
ZIC
Control
Loopback
Plane IP
address
address
Verify GMRE NE
Access
Activate GMRE parameters
CLI
CLI
Handover to 1350 I-NNI port Neighbor node

OMS discovery discovery

Loop Back IP and GMRE IP Addressing
Provision Loop The following steps will be used to provision the Loop Back IP address in the 1830 PSS64/36
Back IP Address system.
Step Action
1 Login to the PSS-64/36 system using ZIC.
2 From the Menu Tree, right click on Networking | IP Addresses | IP
Addresses as shown in the screen below:
3 Slide the scroll bar to right and verify if correct Loopback IP is provisioned
If the Loopback IP is provisioned and correct then proceed to Step 7.

Loop Back IP and GMRE IP Addressing, Continued
Provision Loop
Back IP Address
Step Action
(continued)
4 Click on Edit Loopback IP Address on the bottom right of the window.
5 Enter the Loopback IP Address in the field.
6 Click Apply for the provisioning to take effect and verify the correct value
appears in the Loopback IP field of the IP address window.
7 Click Close to exit out of the window.

Provision The Control Plane IP address is specific to each system in the network and used by the
Control Plane IP GMRE application.
Address
IMPORTANT
It is important to note that the Control Plane IP address cannot be changed once entered,
hence it should be provisioned correctly.
The following steps show how to provision the Control Plane IP address.
Step Action
1 From the ZIC Menu Tree, right click on Networking | IP Addresses | IP
Addresses as shown in the screen below:

Provision
Control Plane IP
Step Action
Address
(continued) 2 Verify that the Control Plane IP is correctly provisioned.
3 If the Control Plane IP is 0-0-0-0 then Click on Edit Control Plane IP

Address at the bottom of the window.
4 Enter the correct address in the field as shown below.
5 Click Apply for the provisioning to take effect and verify that the Control
Plane IP is correctly provisioned in the IP Address window.
6 Click Close to exit out of the window.

Activate GMRE
CLI Session In order to activate GMRE application on the PSS-64/36 a CLI session needs to be
established between the user’s PC computer and NE.
Follow the steps below to setup a CLI session with the NE.
Step Action
1 From the command prompt of the PC computer, Ping the management IP
address of the NE and ensure that both can communicate.
2 Launch an SSH application such Putty and enter the management IP address
and port 22 to open the SSH session.
3 Once the session is open, the user will be prompted to enter the login and
password for the session.
Login Password
appl Geheim

Activate GMRE, Continued
CLI Session
(continued)
Step Action
4 After a successful login, the following text output is displayed:
MontaVista(R) Linux(R) Carrier Grade Edition 4.0.1

Running on host PSS36-NE-01-FLCA
appl@PSS36-NE-01-FLCA(appl)$
5 At the command prompt type cli as shown below:
appl@PSS36-NE-01-FLCA(appl)$ cli
6 A CLI session has now been established. Verify the following text output is
displayed on the screen.
Welcome to GMRE Rel 5.4.0 (Build GTT25-01W)
(c) 2005 - 2012 by Alcatel-Lucent
System loading...successful.
Your terminal type is: XTERM
username[8chars]:
7 Type the username and password for the GMRE application.
User Name Password

install Only4Inst

CLI Session
(continued)
Step Action
8 After a successful login the following text output is displayed:
username[8chars]:install
password:*********
Available keys:
<backspace>|<delete> Erase the character left to the cursor
<ctrl-d> Erase the character right to the cursor
<ctrl-u> Erase the entire command from the
command line
<ctrl-p>|<up> Display the previous command from
history
<ctrl-n>|<down> Display the next command from history
<ctrl-a> Cursor moves to the beginning of the
command line
<ctrl-e> Cursor moves to the end of the command
line
<ctrl-b>|<left> Move the cursor one character left
<ctrl-f>|<right> Move the cursor one character right
<ctrl-r> Reverse search in the command history
Please type ? for help.
unknown(2)[1](Deg)#

Activate GMRE The PSS-64/36 system is now ready to have its GMRE application activated. For the
activation command the following information is required:
GMRE Version
Control Plane Node ID or CPNodeID
Node ID
Use the following steps to activate and verify GMRE application.
Step Action
1 Enter the following command with proper changes relative to the specific NE
to activate the GMRE application:
config node activeNetworkVersion 5.4.0 adminState up

dcnOspfAreaId 0.0.0.0 cpNodeId 11.11.11.220 gmREName
PSS36-02
Wait one (1) minute for the activation process to complete.

Activate GMRE
(continued)
Step Action
3 Verify that the GMRE application has started by entering the following
command at the CLI prompt:
show node
Result:
PSS36-02(2)[2]# show node
NodeAddress: 11.11.11.219
NotifyAddress: 135.117.245.219
MgmtAddress: 135.117.245.219
CPNodeId: 11.11.11.220
DcnGatewayAddress: 135.117.245.4
DcnGatewayAddress: 135.117.245.4
DcnOspfAreaId: 0.0.0.0
NeType: 1830_PSS
NeVersion: E05.10.00
NeOpState: Up
NeXcProcessingState: Normal
GmreName: PSS36-02
Automode: Managed
RestorationMode: Automatic
AdminState: Up
OperationalState: Up ( )
ActiveNetworkVersion: 5.4.0
InstalledNetworkVersion: 5.4.0
NMSConfiguration: OMS
ALSCheck: True
OSPFAuthAlgo: none
OSPFAuthKeyId: -
FeasibilityParameterVersionInUse: -
FeasibilityParameterLatestVersion: -
Neighbors: -,11.11.11.235
Uptime: 12:42:58 up 3 days, 1:52, 2 users, load average:
0.00, 0.01, 0.00
Note: The output from the „show node’ command shows which immediate
neighbors have been discovered by displaying the cpnodeID.
Neighbors: -,11.11.11.235
4 Verify the IP addresses are correct and the NEopstate and AdminState are
UP.

Neighbor Discovery
Overview Once the GMRE application has been activated each node advertises its properties and
exchanges information with other nodes.
Neighbor Node In order for the I-NNI ports to discover each other, follow the steps below:
Verification
Step Action
1 Connect I-NNI ports between NE’s with fiber.
2 Ensure that the I-NNI ports are provisioned for OTUk rate and not for
SONET/SDH or Ethernet.
NOTE: As discussed previously, only OTN ports are allowed to be I-NNI ports
3 Verify proper power levels on the transmit and receive of I-NNI ports using an
optical power meter.
4 Issue the following command to see which ports have discovered neighbors:
show tti
Result:
PSS36-02(2)[2]# show tti
Databearer: 101190101
Transport Mechanism: G709_ODUk_TCM_Level6
TTI: msg16Byte (hex) ContextId DCNAddress TCPId
sent: 2b4a484a41734c4339734743416e56 18212 11.11.11.219

101190101
recv: 2b4a484a41734c4337634743416e56 18212 11.11.11.183
101190101
5 Use the output from the show tti to verify that I-NNI ports are connected
correctly as per the network map.
From the output in step 4, one can conclude that port 19-1 on node
11.11.11.219 is connected to port 19-1 on node 11.11.11.183.
6 Verify all I-NNI ports on each NE in the network.
7 Correct any links that are not fibered correctly.

1350 OMS
Handover At this point the GMRE network is ready to be handed over to the 1350 OMS. As discussed in
Process Section 200 of this guide, it is important to provide the 1350 OMS with a complete and correct
network map so that NPAs, SRGs and actual traffic can be provisioned.
As the 1350 OMS system builds the network in its system, the user can verify parameters
using CLI.
From this point onwards all provisioning must be performed by 1350 OMS only. Any
provisioning performed by CLI will cause inconsistencies in the network.


GCD Networks

December 10, 2012
Alcatel-Lucent
GMPLS Network Provisioning with 1350 OMS
Table of Contents
General ............................................................................................................ 3
Description .................................................................................................... 3
Feedback ...................................................................................................... 3
1350 OMS Configuration ........................................................................................ 4
1350 OMS Specific Configuration .......................................................................... 4
Network Element and Physical Connection Provisioning ................................................. 5
Introduction ................................................................................................... 5
Define OMS Map Views ...................................................................................... 6
Create Network Elements .................................................................................. 8
Add Network Elements to Map View .................................................................... 15
Physical Connection Creation ............................................................................ 20
Shared Risk Group management using 1350 OMS ........................................................ 24
Shared Risk Group Introduction ......................................................................... 24
Shared Risk Group creation .............................................................................. 24
Shared Risk Group Verification .......................................................................... 27
Correlate Shared Risk Groups to Physical Connections .............................................. 28
Correlate Shared Risk Groups to Physical Connections .............................................. 29
GMPLS NPA Creation .......................................................................................... 30
Create GMPLS NPA ......................................................................................... 30
Unlock Physical Connections ............................................................................. 33
ENE – Drop Port Physical connection ....................................................................... 34
ENE Introduction ........................................................................................... 34
Create ENE .................................................................................................. 34
ENE management using 1350 OMS .......................................................................... 37
ENE Physical Connection Introduction .................................................................. 37
Create ENE Physical Connection ......................................................................... 37
SPC Path Creation / Management using 1350 OMS ...................................................... 41
ODU / SPC Introduction ................................................................................... 41
ODU Trail Creation- Unprotected ....................................................................... 41
ODU Trail Creation- Source Based Restoration (Upon Failure) ..................................... 45
IEH 611, Section 400 GMPLS Network Provisioning with 1350 OMS
ODU Trail Creation- Source Based Restoration (Pre-calculated) .................................. 49

ODU Trail Creation- SNCP ................................................................................. 53
ODU Trail Creation- Protection and Restoration Combined (PRC) ................................ 57
ODU Trail Creation- Using Constraints ................................................................. 61
ODU Trail Deletion ......................................................................................... 68
GMPLS NPA Verification ...................................................................................... 70
GMPLS NPA verification ................................................................................... 70
NPA- Nodes .................................................................................................. 71
NPA- Control Plane......................................................................................... 72
NPA- Physical Connections ............................................................................... 72
NPA- TE Links ............................................................................................... 73
NPA- Paths ................................................................................................... 73
NPA- SNCs ................................................................................................... 73
TE Link management using 1350 OMS ...................................................................... 74
TE Link Introduction ....................................................................................... 74
Display TE Links ............................................................................................ 74
TE Link Modification- Add Physical Connection ....................................................... 76
TE Link Modification- Update TE Link .................................................................. 80
Control Plane Restoration.................................................................................... 85
Control Plane Restoration ................................................................................ 85
Source Based Restoration (Upon Failure and Pre-calculated) ...................................... 85
SNCP .......................................................................................................... 89
PRC-Protection Restoration Combined ................................................................. 92
Equipment views using 1350 OMS ........................................................................... 96
NE Shelf View ............................................................................................... 96
Generate NE Shelf View ................................................................................... 96
1350 OMS Alarm Handling .................................................................................... 98
Introduction ................................................................................................. 98
Alarm View .................................................................................................. 98
Alarm View From OMS Generated Lists................................................................. 99
GMRE Administration ........................................................................................ 100
Link Maintenance ......................................................................................... 100
Appendix A: 1350 OMS Optical Management System ................................................... 106
1350 OMS Optical Management System ............................................................... 106
Hardware Requirements ................................................................................. 106
1350 OMS GUI connectivity .............................................................................. 107
List of Tables

GMPLS Network Provisioning with 1350 OMS IEH 611, Section 400
General
Description This section provides the field and NOC engineers of 1830 PSS systems with detailed
procedures for network configuration of a Layer 1 (L1) GMPLS Network Protection
Architecture (NPA) using the 1350 Optical Management System (OMS) and the step by step
process for accessing the 1350 OMS management platform.
Intended The audience should have a basic knowledge of DWDM technology, 1830 PSS product
Audience portfolio, Optical Switching, G709 OTN knowledge, 1350 OMS Operation experience and
completed at least 1830 PSS-64/36 Level 2 Certification program conducted by the Alcatel-
Lucent University. As such, this document is intended for:
Alcatel-Lucent (ALU) NOC Engineers
Related This document was developed in support of the official product releases, which are listed in

1830 PSS-36 5.1
1830 PSS-64 5.1
1390 NPT (Network Planning Tool) 5.1
1350 OMS (Optical management system) 10.2

1350 OMS Configuration
1350 OMS Prior to commencement of the activities listed in this document, please check with the 1350
Specific OMS System administrator that the following specific configuration has been completed on the
Configuration management platform
Requirement Action on OMS

System configuration of EML application must include Required to allow for correct
the option for RMI_Proxy display of equipment views when
requested from OMS
System configuration of SDH- the RM_IMLIB option Required to allow the correct
should be modified to set the attributes to be set to WDM
WDM_END_TO_END_MANAGEMENT option to physical connections as required
“wdmApplWithSdhIW” for the GMRE ASON build

Network Element and Physical Connection

Provisioning
Introduction PC requirements and instructions for accessing the 1350 OMS are defined in Appendix A of
this document.
The flowchart below illustrates the high level GMPLS NPA creation using the 1350 OMS.
YES
Define OMS map

Log onto OMS and start NO
Is Map view layout in accordance
network management
defined with customer NMS
application
specifications
YES
YES
Rectify Supervision issues

Ensure correct details entered during NE
EML: Network elements NO create nodes and start NO creation
created and supervised supervision verify IP connectivity
ensure user account not suspended
recreate NE in another EMLIM
YES
YES
Rectify Synchronisation issues

Ensure NE is reachable and aligned
Ensure EMLIM is reachable and aligned
Add Elements to YES Port YES Synchronise Ports NO
Synchronise EMLIM
Map synchronisation all ports aligned in OMS
verify if all nodes in EMLIM failed to sync
Liaise with system Admin to resolve OMS
synchronisation issues
YES
YES
Rectify Physical connection issues
Ensure required ports are available in port
Create OPS Physical Create OPS NO list
connections Physical connections
Manually build OPS physical connections
Liaise with system Admin to resolve OMS
physical connection creation issues
YES
Create Shared Risk Groups YES Correlate SRG to

(SRG) Physical Connections
YES
YES add Physical

Create ASON NPA connections to NPA
YES YES
Rectify ASON Implementation issues

check state of EMLIM and FEP’s
NO check log out for indication of failure reason
YES ASON NPA
Implement ASON NPA Set nodes to download disable and
implemented
implement ASON NPA, then perform global
download
YES Liaise with system Admin to resolve OMS
ASON implementation issues
Unlock Physical
Connections
Verify ASON NPA Build:

SDH- search- ASON created NPA
Highlight created ASON NPA and select search- NPA view
Verify all resources within the ASON NPA have been

correctly assigned and are aligned with EPT planning tool
output for 1830 OCS GMRE network
1- Nodes
2- Control Plane network elements
3- Physical connection
4- TE links


Provisioning, Continued
Define OMS Map Follow these steps to configure OMS map views as defined by the customer for their Network
Views Management System recommendations.
Step Action
1 Highlight the root map in map view, ensure root map is highlighted and
click with right hand mouse button-
Select
Actions
Create Sub-Network


Define OMS Map

Views
Step Action
(continued)
2 When the Create Sub-Network wizard is displayed
Define the following information
Name: Define Sub Map Name
Apply
Result: When the banner at the top of the screen goes green, the sub map has
been successfully created.


Create Network Follow these steps to configure 1830 network elements on the 1350 OMS and start
Elements supervision
Step Action
1 From 1350 OMS network management view select
Actions
EML
Create NE


Create Network
Elements
Step Action
(continued)
2 Using the Create NE wizard- define the following parameters
Family- OTN
Type- 1830PSS
Release- software release of 1830
User label- 1830 SID
Location Name- customer provided location of network element
Select OCS for PSS36/64 (SID will be appended with #OCS).
(PHN option will be selected when creating a PSS32 network element)
Click Apply.
Result: When the banner at the top of screen turns green, the 1830 NE has
successfully been created.
NOTE: repeat for all network elements to be managed by the OMS


Create Network
Elements
Step Action
(continued)
3 From 1350 OMS network management view select
Search
EML
Network Elements
The following screen will be displayed:


Create Network
Elements
Step Action
(continued)
4 Highlight required network element and right mouse click,
Actions
Composite NE Set Address


Create Network
Elements
Step Action
(continued)
5 Using the Composite NE Set Address screen- define the following
parameters:
Primary address - IP address of OCS NE
Partner IP address - set to 0.0.0.0 to cancel logical relationship between
Photonic (PHN) and Optical cross connect (OCS) compounds
Primary User ID - as defined during NE commissioning process
NOTE: For OMS supervision, it is advisable to use either EML001 or EML002
Primary Password - as defined during NE commissioning process
TID- append listed TID to remove the #OCS which is added during NE
creation
Secure Comms (TL1)- Select SSH
Select Apply.
Result: When the banner at top of screen turns green, the Network element
details have been successfully entered.


Create Network
Elements
Step Action
(continued)
6 Verify IP connectivity.
Highlight required network element and right mouse click,
Actions
Ping NE’s
7 Selected NE will appear in Ping NEs list:
Click on Apply.
Result: If there is IP connectivity to the 1830 NE, the banner will go green and
the Address Reachability will be defined as Reachable.


Create Network
Elements
Step Action
(continued)
8 Start Supervision.
Highlight required network element and right hand mouse click,
Actions
Supervision
Start Supervision
9 When the node is successfully supervised, the following states will be defined:
Supervision state- Supervised
NE Reach ability- Reachable
Alignment state- Aligned
See example screen below:
10 Repeat Steps 1 – 9 for all network elements.


Add Network Follow these steps to define the 1830 Network elements into the correct Map Sub-network.
Elements to
Map View Step Action
1 Highlight Sub-Network map in map view and click with right mouse button.
Select
Actions
Modify Sub-Network.
2
On the Modify Sub-Network wizard - Click on the icon.


Add Network
Elements to
Step Action
Map View
(continued) 3 On the Contained Nodes and Sub-Network screen, select nodes to be
added to current map view and select ok
4 Node will now be displayed in the Modify Sub-Network wizard screen
Click on Apply and when the banner goes green at top of wizard, command is
successful. Close the window


Add Network
Elements to
Step Action
Map View
(continued) 5 Double click on sub-network to generate map view


Add Network
Elements to
Step Action
Map View
(continued) 6 Double click on the Not placed icon and the nodes will be displayed on the
right hand side of the map view
Click on node and while holding down left key on mouse, drag icon into the
map view


Add Network
Elements to
Step Action
Map View
(continued) 7
Click on „save’ icon to save the map view
Select Yes on window notification
8 Repeat for all nodes to be entered into current sub-network


Physical Follow these steps to create the physical ports on the OCS nodes deployed within the network
Connection topology
Creation
Step Action
1 From Network management view, select required network element
Actions
Physical
Create Physical Connection
2 When the Create Physical Connection screen is generated, define the

following parameters:
User label
Connection type- WDM
Leave allocation cost as default- 20
Select next


Physical
Connection
Step Action
Creation
(continued) 3 Next Page- Create Physical Connection, set the following parameters
WDM connection type- OPS
Client Signal type- leave as default
OCS-Photonic Interworking type- leave as default
Select A node
A Port- click in box and select Ports for Physical Connection creation
4 Repeat for Z node and Z port
5 From generated port list, select required port- OK


Physical
Connection
Step Action
Creation
(continued) 6
Verify ports selected and click Apply.

Result: When banner goes green, the Physical connection has been
successfully completed
7 Verify from graphical view that the OPS Physical Connection has been
successfully created.


Physical
Connection
Step Action
Creation
(continued) 8 Repeat for all Physical connections to be defined in GMPLS topology.

Shared Risk Group management using 1350 OMS
Shared Risk According to the ITU-T Recommendations, a Shared Risk Group (SRG) is a group of elements
Group (Nodes or links) that share a common risk, and whose failure can cause the failure of all the
Introduction elements in the group.
The purpose of SRGs is to provide the GMPLS topology with the appropriate information to
correctly calculate redundant routes through the network for an existing route avoiding that the
same problem, for example a link failure which could affect the nominal and planned
protection routes.
Thus, the SRG concept is a useful mechanism to support “failure diversity” between paths in a
GMPLS transport network.
Shared Risk Follow these steps to create SRG

Group creation
Step Action
1 To create a SRG, select
Actions
SDH
Shared Risk Groups
Manage Shared Risk Groups
2 When Create/Remove SRGs window is displayed, select

Create
Click Next

Shared Risk Group management using 1350 OMS,

Continued
Shared Risk
Group creation
Step Action
(continued)
3
Select the Icon to define the SRG type
Select:
SRG Type
OK


Continued
Shared Risk
Group creation
Step Action
(continued)
4 Define the following fields
User label: define the SRG name
Comments: add any applicable comments
A site- define A site of SRG to be created
Z site- define Z site of SRG to be created
Click Apply.
Result: When banner at top of screen goes green, SRG has been successfully
created


Continued
Shared Risk Follow these steps to Verify SRG Creation

Group
Verification Step Action
1 To verify the creation of a SRG, select
Search
SDH
Shared Risk Groups
2 The Shared Risk Group assignment screen will be generated, this will; be
used to verify that the SRG has been correctly created for the required
physical connections


Continued
Correlate Follow these steps to unlock the logical links

Shared Risk
Groups to Step Action
Physical 1 To correlate the assignment of a SRG, select
Connections
Actions
SDH
Correlate SRGs
2 When the Correlate, Uncorrelate, Upload SRGs wizard is displayed,

Select:
The icon and choose the required Physical connection from the list
generated
Click Next


Continued
Correlate
Shared Risk
Step Action
Groups to
Physical 3 When the next screen is displayed
Connections Select:
(continued)
The icon and choose the required SRG from the list generated
Select SRG
Click OK
4 Verify information is correct

Click Apply
Result: When the banner at top of screen goes green, the SRG has correctly
been correlated to the physical connection

GMPLS NPA Creation
Create GMPLS A NPA is a set of NE’s and physical connections working together to create a dedicated
NPA protection mechanism for a network based topology.
Follow these steps to configure GMPLS NPA:
Step Action
1 From Network management view, select
Actions
SDH
Create NPA
2 When the NPA Creation wizard is displayed, specify the following information:
User label- as defined by customer
NPA type- ASON
Leave all other paramaters as default
Click Next

GMPLS NPA Creation, Continued
Create GMPLS
NPA (continued)
Step Action
3 When the NPA wizard screen is displayed, specify the following information:
Click on the icon for the internal physical connections

Select the required internal links which are being provisioned for the I-NNI
links for ASON NPA interworking
Click OK
4 The ASON NPA now needs to be implemented.

Select
Search
SDH
NPAs

Create GMPLS
NPA (continued)
Step Action
5 When the NPA list is generated, highlight required NPA
Select
Actions
Configuration
Implement
6 When NPA has been successfully implemented, the configuration state will
change to Implemented and will go green.

Unlock Physical Follow these steps to verify correct GMPLS NPA for the OMS and 1830 Network elements
Connections
Step Action
1 From Network Management View,
Select
Search
Physical
Physical Connections
From generated Physical connection list,

Select
Actions
SDH
Maintenance
Set Administrative State to Unlocked

ENE – Drop Port Physical connection
ENE External Network Elements are used to allow for non-terminated paths to be managed using
Introduction ENE virtual node. A non-terminated path describes a path between a Trail Termination Point
(TTP) associated to a OTN port and a Connection Termination Point (CTP).defined on an ENE
Create ENE Follow these steps create an ENE
Step Action
Actions
SDH
Create External Network
2 When the Create External Network wizard is displayed,

User label
Location name

ENE – Drop Port Physical connection, Continued
Create ENE
(continued)
Step Action
3 Click Apply
When the banner at top of screen goes green, the ENE has successfully
created
4 The ENE virtual nodes now need to be added to the MAP view.
Highlight Sub-Network map in map view and click with right mouse button.
Select
Actions
Modify Sub-Network.
On the Modify Sub-Network wizard - Click on the icon.
Select required ENE nodes to be added to map and click Apply

ENE – Drop Port Physical connection, Continued
Create ENE
(continued)
Step Action
5 Move ENE to maps as defined in section 6 on page 15 of this procedure.
Once all ENE’s have been moved to map view:

click on Save icon
select OK

ENE management using 1350 OMS
ENE Physical Physical connections must be built between the OCS network elements and the ENE virtual
Connection nodes, to allow for termination of client paths which are automatically created by the OMS
Introduction after successful creation of the ODUk trail during ODUk trail provisioning.
Create ENE Follow these steps to create Physical connections between drop ports and ENE
Physical
Connection Step Action
1 From Map view, or from Node list,
Select:
OCS node
ENE node (using Ctrl button)
Actions
Physical
Create Physical Connection
Define::
User label: as required by customer Connection naming convention
Connection type: WDM
Allocation cost: 20

ENE management using 1350 OMS, Continued
Create ENE
Physical
Step Action
Connection
(continued) 2 When next screen of Physical Connection wizard is displayed,
WDM connection type –OPS
Client Signal Type- as required for client port being connected
Click on Icon and then select from the Nodes for Physical Connection
creation to generate available node list for port granularity select above list
Select required Nodes
Click on Icon and then select from the Ports for Physical Connection
creation to generate available port list
Select required ports

Create ENE
Physical
Step Action
Connection
(continued) 3 Click Apply
Result: When banner at top of screen goes green, Physical connection has
been successfully created
4 Routing Display of Physical connection will be displayed

Create ENE
Physical
Step Action
Connection
(continued) 5 Select:
Search
Physical
Physical Connections to generate a list of all Physical connection created on
the OMS

SPC Path Creation / Management using 1350 OMS
ODU / SPC A soft permanent connection (SPC) is an end to end service between a source node and
Introduction destination node which may or may not go through intermediate nodes. An SPC is setup by
the 1350 OMS management platform and can be defined as two basic services types.
Unprotected
Protected
Unprotected: This is an end to end path which may contain risk, cost and node constraints
but upon a link failure that traffic will not be restored. A typical application for such service is
low priority traffic containing data which is classified as best effort or zero priority. Once the
link failure is cleared the path is in-service again.
Protected: This is an end to end path consisting of risk, cost and node constraints but will
establish alternate paths in the network if link failure occurs. There are various types of service
options for a protected path.
It is important to note that the terminology of Service types is different in 1350 OMS. The
correlation is listed in the table below.
GMRE Service Naming in 1350 OMS

Unprotected No Restoration
Source Based Restoration (SBR) Upon Failure
Guaranteed Pre-calculated
SNCP Protected with No Restoration
Protection and Restoration Combined (PRC) Protected with Restoration
ODU Trail Follow these steps to create an unprotected Optical data Unit (ODU) trail
Creation- Prior to configuring the service, please ensure:
Unprotected
Physical connection with correct service rate is created between OCS node and ENE
Step Action
Actions
SDH
Create ODU trail

SPC Path Creation / Management using 1350 OMS,

Continued
ODU Trail
Creation-
Step Action
Unprotected
(continued) 2 When the Create ODU trail wizard is displayed
Populate the following fields

User label: trail name
WDM Trail layer rate: ODUk container size for required transport connection
Allocation rule: set to automatic
Implementation rule: set to automatic
Source A node: click on to generate list options and then select required
node
Source CAP: click on to generate list options and then select required
connection access point
Source B node: click on to generate list options and then select required
node
Sink CAP: click on to generate list options and then select required


Continued
ODU Trail
Creation-
Step Action
Unprotected
(continued) 3 Select Protection Tab
*Protection : None
4 Select PM tab and enable PM if required
5 Select CP restoration tab

*Preferred Restoration Mode: No Restoration
Click Apply:
Result: When banner at top of create ODU wizard goes green, the trail has


Continued
ODU Trail
Creation-
Step Action
Unprotected
(continued) 6 A routing display of the created trail is generated
7
Click on ODUk icon and select:
Search
Paths
To generate a supported path list for created ODUk trail
Click on path and select:

Search
Routing display
A routing display of the path will be generated


Continued
Creation- Prior to configuring the service, please ensure:
Source Based
Restoration Physical connection with correct service rate is created between OCS node and ENE
(Upon Failure)
Step Action
Actions
SDH
Create ODU trail


Continued
ODU Trail
Creation-
Step Action
Source Based
Restoration 2 When the Create ODU trail wizard is displayed
(Upon Failure)
(continued)

node
node


Continued
ODU Trail
Creation-
Step Action
Source Based
Restoration 3 Select Protection Tab
(Upon Failure) *Protection : None
(continued)

*Preferred Restoration Mode: Upon Failure
*Reversion Mode: Automatic / Manual as required by customer
Click Apply:


Continued
ODU Trail
Creation-
Step Action
Source Based
Restoration 6 A routing display of the created trail is generated
(Upon Failure)
(continued)
7
Search
Paths

Search
Routing display


Continued
ODU Trail Follow these steps to create a Source Based Restoration (Pre-calculated) Optical data Unit
Creation- (ODU) trail
Source Based Prior to configuring the service, please ensure:
Restoration
(Pre-calculated) Physical connection with correct service rate is created between OCS node and ENE
Step Action
Actions
SDH
Create ODU trail


Continued
ODU Trail
Creation-
Step Action
Source Based
(Pre-calculated)
(continued)

node
node


Continued
ODU Trail
Creation-
Step Action
Source Based
(Pre-calculated) *Protection : None
(continued)

*Preferred Restoration Mode: Pre-calculated
Click Apply:


Continued
ODU Trail
Creation-
Step Action
Source Based
(Pre-calculated)
(continued)
7
Search
Paths

Search
Routing display


Continued
ODU Trail Follow these steps to create a SNCP Protected Optical data Unit (ODU) trail
Creation- SNCP Prior to configuring the service, please ensure:
Step Action
Actions
SDH
Create ODU trail


Continued
ODU Trail
Creation- SNCP
Step Action
(continued)
2 When the Create ODU trail wizard is displayed

node
node


Continued
ODU Trail
Creation- SNCP
Step Action
(continued)
3 Select Protection Tab
*Protection : SNCP

*Preferred Restoration Mode: None
Click Apply:


Continued
ODU Trail
Creation- SNCP
Step Action
(continued)
6 A routing display of the created trail is generated
7
Search
Paths

Search
Routing display
NOTE: The end to end path is displayed, to see the server trail which is where the SNCP configuration is
displayed, you must click on the icon and select server routing display to show the SNCP ODUk trail as
displayed in step 6.


Continued
ODU Trail Follow these steps to create a Protection and Restoration Combined Protected Optical data
Creation- Unit (ODU) trail
Protection and Prior to configuring the service, please ensure:
Restoration
Combined (PRC) Physical connection with correct service rate is created between OCS node and ENE
Step Action
Actions
SDH
Create ODU trail


Continued
ODU Trail
Creation-
Step Action
Protection and
Combined (PRC)
(continued)

node
node


Continued
ODU Trail
Creation-
Step Action
Protection and
Combined (PRC) *Protection : SNCP
(continued)

*Preferred Restoration Mode: Upon Failure
Click Apply:


Continued
ODU Trail
Creation-
Step Action
Protection and
Combined (PRC)
(continued)
7
Search
Paths

Search
Routing display
NOTE: The end to end path is displayed, to see the server trail which is where the SNCP configuration is
displayed, you must click on the icon and select server routing display to show the SNCP ODUk trail as
displayed in step 6.


Continued
Creation- Using Prior to configuring the service, please ensure:
Constraints
Step Action
Actions
SDH
Create ODU trail


Continued
ODU Trail
Creation- Using
Step Action
Constraints
(continued) 2 When the Create ODU trail wizard is displayed

Allocation rule: set to user
Implementation rule: set to user
node
node


Continued
ODU Trail
Creation- Using
Step Action
Constraints
(continued) 3 Select Protection Tab
*Protection : Dependant on service type being provisioned


Continued
ODU Trail
Creation- Using
Step Action
Constraints
(continued) 4 Select PM tab and enable PM if required

*Preferred Restoration Mode: Dependant on service type being
provisioned
Click Apply:


Continued
ODU Trail
Creation- Using
Step Action
Constraints
(continued) 6 A routing display of the created trail is generated
The ODUk trail has only been moved to the Defined stage, the routing
constraints need to be added now

Actions
Constraints
Edit Constraints


Continued
ODU Trail
Creation- Using
Step Action
Constraints
(continued) 7 The constraints window will be generated,
Select required routing constrains to be added (as detailed below to use
specific physical topology), select
Send to
Constraints Management
Routing Constraints
This information will then be added to the constraints wizard

Ensure required constraint information is correctly specified and click apply
Result: When banner at top of wizard goes green, the constraint has
successfully been added to the path routing


Continued
ODU Trail
Creation- Using
Step Action
Constraints
(continued) 8 Return to the routing display of the ODUk trail

Actions
Allocate

Actions
Implement
The ODUk trail will now be implemented and a routing display will be
generated, verify that the routing constraint has been correctly applied to the
created ODUk trail


Continued
ODU Trail Follow these steps to delete an Optical data Unit (ODU) trail.
Deletion
Step Action
Search
SDH
ODUk trails
2 When the Create ODU trail list
Select required trail to be deleted and then select

Search
Paths
3 Highlight required path and select:
Actions
Remove
Selected path will now be deleted


Continued
ODU Trail
Deletion
Step Action
(continued)
4 Return to list generated in step 2
Select required ODUk to be deleted and select
Actions
Remove
Trail will be removed

GMPLS NPA Verification
GMPLS NPA Follow these steps to verify correct GMPLS NPA construction for the OMS and 1830 Network
verification elements.
Step Action
1 To generate an NPA view,
Select
Search
SDH
NPAs
2 From generated NPA list

Highlight required NPA
Click on Icon to generate NPA view

GMPLS NPA Verification, Continued
GMPLS NPA
verification
Step Action
(continued)
3 NPA view will be displayed
NPA- Nodes In the NPA view generated, click on the Nodes folder:
The list generated will provide an overview of the nodes deployed in the ASON NPA and their
status for communication with the OMS management platform

NPA- Control In the NPA view generated, click on the Control Plane folder:
Plane
The list generated will provide a list of all nodes connected using control plane and defined in
the ASON NPA, including :
Node name
NA reach ability- status of communication with OCS control plane
Alarm status- will provide a visual indicator of control plane alarms
Consistency status- which will indicate if there is a mismatch between the OMS NE
database and the Network element
Native name- GMRE Control plane IP address
CLI IP address- Node OAMP address
Assignment state - assigned
NPA- Physical In the NPA view generated, click on the Physical Connections folder:
Connections
The list generated will provide a list of all Physical connections, including:
User label
Link type- i-NNI links
TELink Name- will define to which TE link the physical connection has been assigned
ASON administrative state- will display the administrative state of the physical connection

NPA- TE Links In the NPA view generated, click on the TE links folder:
The list generated will provide a list of all TE links:

User label
Link Metric- default value of 20
NPA- Paths In the NPA view generated, click on the Paths folder:
The list generated will provide all paths managed by the ASON NPA, including:
User label
Link Metric- default value of 20
NPA- SNCs In the NPA view generated, click on the Sub Network connections, SNCs folder:
The list generated will provide a list of all of the SNC (ODUk trails) :
User label
WDM layer rate- ODUk
Restoration Mode- as defined during ODUk trail creation

TE Link management using 1350 OMS
TE Link For path routing purposes, multiple data links can be combined to form a single TE (Transport
Introduction Engineered) link. This summarization mechanism reduces the amount of routing information
that needs to be disseminated through the network
Display TE Links Follow these steps to display the TE Links
Step Action
Search
SDH
NPAs
2 When the NPA list is displayed
Select
Required NPA group
Click on icon to generate NPA view

TE Link management using 1350 OMS, Continued
Display TE Links
(continued)
Step Action
3 When NPA view is displayed
Select
TE links
4 When TE links list is displayed
Select required i-NNI link between two nodes and select

Search
Physical connections
To display physical connections managed by the GME control plane under the
TE link

TE Link Follow these steps to modify the parameters of the TE link

Modification- 1- Create New Physical connection
Add Physical 2- Modify required TE link
Connection
Step Action
1 Create Physical connection as detailed in Create Physical connection section
starting on page 18 of this MOP
Search
SDH
NPAs

TE Link
Modification-
Step Action
Add Physical
Connection 3 From generated NPA list
(continued)
Select
Actions
Modify
Add Physical Connection
Select
The Icon alongside additional Physical connections- Internal

TE Link
Modification-
Step Action
Add Physical
Connection 4 When the available physical connections screen is displayed, select physical
(continued) connection to be added and click ok
Verify information for selected physical connection has been added to the list
and click apply
Result: When the banner at top of screen goes green, NPA has been
successfully modified

TE Link
Modification-
Step Action
Add Physical
Connection 5 From Network management view, navigate to NPA view.
(continued) Select
When Physical connection screen is displayed
Highlight required physical connection
Actions
SDH
Maintenance
Set administrative state to unlocked
ASON Administrative state will now show locked

TE Link Follow these steps to modify the parameters of the TE link

Modification- 1- Create New Physical connection
Update TE Link 2- Modify required TE link
Step Action
1 Generate TE link list as detailed in Display TE links section of this mop.
Highlight the new physical connection, which has been created as a TE link
and select
Actions
Modifcation
Move Physical Connection

TE Link
Modification-
Step Action
Update TE Link
(continued) 2 When Update TE link screen is displayed
Change *Operation to Move to an existing TE link

TE Link
Modification-
Step Action
Update TE Link
(continued) 3 Select
Destination TE link using the Icon

Choose destination TE link
Verify information for TE link update and click apply

Result: When banner at top of screen goes green, the TE link has been
successfully updated

TE Link
Modification-
Step Action
Update TE Link
(continued) 4 To verify the TE link update, return to the TE link list
Select
Updated TE link from list
Search
Verify from physical connection list generated that the TE links has been
successfully updated:

TE Link
Modification-
Step Action
Update TE Link
(continued) 5 From the Physical Connections (ASON) list, Highlight required Physical
connection, Select
Actions
SDH
Maintenance
Set ASON Administrative state to unlocked
ASON administrative state will be changed to unlocked:

Control Plane Restoration
Control Plane The 1350 OMS can define two different reports for the trails created within the ASON GMRE
Restoration domain,
Nominal route
Current route
The Nominal route is the route created when the trail is first established, this is the default
route and cannot be changed by the control plane, this is the route which traffic will be
reverted to after any network outage, which has instigated a protection switching event, has
been resolved. The routing display within OMS will always show the nominal route.
The current route is the route which the traffic has been switched to by the GMRE control
plane after a network outage had been detected and a protection switching event has
occurred.
Source Based After a network outage has been detected, the network services configured with Source based
Restoration restoration (upon failure and pre-calculated) will be rerouted by the GMRE control plane.
(Upon Failure
and Pre-
calculated) Step Action
1 To verify the routing of a SBR protected path,
Select
Search
SDH
ODUk trails

Control Plane Restoration, Continued
Source Based
Restoration
Step Action
(Upon Failure
and Pre- 2 From the generated ODUk trail list.
calculated)
(continued)
Select
Highlight required ODUk trail
Select the current alarm Icon to see the active trail alarms

Source Based
Restoration
Step Action
(Upon Failure
and Pre- 3 From the ODUk trail window
calculated) Select
(continued) Highlight required trail
Select SNC icon to generate SNC list for required trail

Source Based
Restoration
Step Action
(Upon Failure
and Pre- 4 From generated SNC list,
calculated) Select
(continued) Highlight SNC
Search
Nominal route
NOTE:
This is the nominal route which cannot be changed by the GMRE control
plane; this will be the route which the traffic will be restored to after the
network outage has been repaired.
If a routing display is generated, the system will only show the nominal route
5 Top display the current route,

Select
Highlight the required SNC
Search
Current route

SNCP After a network outage has been detected, the network services configured with SNCP
restoration will be switched by the network elements at the ingress and egress point (uni-
directional SNCP) of the configured ODUk trail.
Step Action
1 To verify the routing of a SNCP protected path,
Select
Search
SDH
ODUk trails
2 From the generated ODUk trail list
Select

SNCP
(continued)
Step Action
3 For the required SNCP protected ODUk trail,
Select
Highlight required SNCP
Search
Routing display
4
When the routing display is generated click on the SNC icon . To
display the nominal route
Select
Search
Nominal route

SNCP
(continued)
Step Action
5 From the ODUk routing display
Click on the switch icon,

Select
Actions
SNCP Management
Synchronize- to synchronize the switch position and to establish current
route

PRC-Protection After a network outage has been detected, the network services configured with SNCP
Restoration restoration will be switched by the network elements at the ingress and egress point (uni-
Combined directional SNCP) of the configured ODUk trail.
The control plane will then configure an additional protection leg for the SNCP.
Step Action
1 To verify the routing of a SNCP protected path,
Select
Search
SDH
ODUk trails

PRC-Protection
Restoration
Step Action
Combined
(continued) 2 From the generated ODUk trail list
Select
3 For the required PRC protected ODUk trail,

Select
Highlight required SNCP
Search
Routing display

PRC-Protection
Restoration
Step Action
Combined
(continued) 4
When the routing display is generated click on the SNC icon . To
display the nominal route
Select
Search
Nominal route

PRC-Protection
Restoration
Step Action
Combined
(continued) 5 From the ODUk routing display
Click on the switch icon,

Select
Actions
SNCP Management
Synchronize- to synchronize the switch position and to establish current
route

Equipment views using 1350 OMS
NE Shelf View The OMS can display a ZIC view from the OMS management platform, similar to the ZIC
generated when directly connected to the network element.
Generate NE Follow these steps to generate a shelf view of the Network element
Shelf View
Step Action
1 There are multiple different ways to generate equipment views, please see
below for different options
2 From OMS management view
Search
EML
Network element
From generated Network element list, select

Required network element
Search
Equipment view

Equipment views using 1350 OMS, Continued
Generate NE
Shelf View
Step Action
(continued)
From OMS management view
Search
Physical
Nodes
From generated Network element list, select

Required network element
Search
Physical
Equipment view
From OMS management view of a path routing display
Select Required network element from graphical display
Search
Physical
Equipment view
NOTE:
The Equipment view can be generated from many different management
windows within the OMS, the options detailed above are just to display
different ways of accessing the network element shelf view.

1350 OMS Alarm Handling
Introduction Alarm messages on elementary objects (Network Access Points (NAP),Connection Access
Points (Cap), Connection Termination Points (CTP), Ports) are received from the EML layer,
Processed and propagated to the affected objects.
These alarms are propagated to the following objects:

1- Transport entities (link connection, trail, path)
2- Topological object (node, Subnetwork, network)
Alarms are generated on paths, Physical Connections, Trails (both HO and MS). Elementary
Alarms are received from EML layer and processed by SDH and WDM in order to determine
the SDH/WDM object to be marked as faulty.
SDH/WDM provides for the impacted object the Alarm Severity, the Operational State and the
Probable Cause.
Alarms are forwarded from the respective manager, EML, WDM and SDH to the global alarm
view which provides alarm correlation for all alarms generated on the systems managed by
the 1350 OMS.
Alarm View To generate an alarm browser, from the OMS web portal
Step Action
1 Select
Alarms
2 Double click on the global alarms Icon
To start the global alarms view

1350 OMS Alarm Handling, Continued
Alarm View From any OMS generated list, the alarms of the attributes being displayed can be displayed
From OMS on the OMS
Generated Lists
Step Action
1 Generate the required list, from network management view
Select (for example)
Search
Physical
2
Highlight required object and select the alarm icon
All alarms for the required object will be displayed

GMRE Administration
Link For scheduled maintenance activities, a physical connection which is configured to carry
Maintenance traffic, can be migrate the traffic onto a separate physical connection using the administrative
state shutting down capability:
After a physical connection has been moved to the administrative state “shutting down”, the
physical connection is locked for new traffic, but will keep the existing traffic until it is moved to
another physical connection.
When all traffic is running via the physical connection has been moved to a different physical
connection, the administrative state is automatically set to lock.
NOTE:
If the administrative state would be set directly to locked, traffic without protection/restoration
would be lost.
Step Action
1 From Network Management view,
Select
Search
Physical
To generate a Physical connection list
From list, select required Physical Connection to be locked

GMRE Administration, Continued
Link
Maintenance
Step Action
(continued)
2 Select
Actions
SDH
Maintenance
When the ASON maintenance wizard is displayed,

Select the command to perform- choose set Ason Administrative state to
shutting down
Result: When the banner at top of screen goes green, the Physical connection
Administrative state has been correctly set

Link
Maintenance
Step Action
(continued)
3 Any traffic configured on the physical connection needs to be moved off this
connection to allow for no network traffic outage during maintenance activities.
Highlight traffic to me moved to a different physical connection and in the
*Select the command to perform- choose Move Traffic and apply
Use the refresh icon to update the screen to see the traffic being migrated

Link
Maintenance
Step Action
(continued)
4 To check the Administrative state of the Physical connection,
*Select the command to perform- choose Check Ason Administrative State
and apply
When all applicable traffic has been moved off the Physical Connection, the
ASON Administrative state will be automatically moved to the ASON
Administrative state of locked, the physical connection now has now trails or
paths configured and can be released for the required maintenance activities.
NOTE:
The move traffic will only work for unprotected or Source based restoration
control plane service types, SNCP and PRC will be protected by protection
switching when the administrative state of the physical connection is set to
locked.
5 From the SNC list displayed from the ASON NPA view, the SNC for the trail
that was moved in step 3 now has a warning alarm
Highlight the SNC and select the icon, the alarms for the SNC will be
displayed

Link
Maintenance
Step Action
(continued)
6 After the maintenance activities have been concluded, the port must be
returned to service with ASON Administrative state set to locked
From the Physical connection list generated in step 1,
Highlight required Physical connection and select
Actions
SDH
Maintenance
Set ASON Administrative state to unlocked
ASON Administrative set will now be set to unlocked

Link
Maintenance
Step Action
(continued)
7 The traffic moved from this link prior to the ASON administrative change and
planned activity needs to be moved back onto the physical connection.
From the ASON SNCs window
Highlight required SNC to be moved and select
Actions
Switch
Switch to Nominal
SNC will be moved to its Nominal (original) route and the warning alarm will be
cleared
NOTE:
The move traffic will only work for unprotected or Source based restoration
control plane service types, SNCP and PRC will be protected by protection
switching when the administrative state of the physical connection is set to
locked.

Appendix A: 1350 OMS Optical Management System
1350 OMS
Optical 1350 OMS (Optical management system) is the Server/Client Management platform designed
Management for 1830 PSS configuration, maintenance, and monitoring operations. The 1350 OMS all
System supports all other Optical and TDM transmission network elements within the Alcatel-Lucent
portfolio
1350 OMS uses Alcatel-Lucent’s patented Wavelength Tracker™ technology at various points
along the service path to provide wavelength identification, path tracing, and power-level
monitoring that guarantee the integrity, performance, and reliability of wavelength services.
The Commissioning and Power Balancing (CPB) application is a function of the 1350 OMS
and is an embedded tool that performs:
Provisioning of a Greenfield NE
Provisioning of Greenfield networks of NEs
Power-balancing of in-service individual NEs
Power-balancing of in-service networks of NEs
Creates the Loss Report for Greenfield or existing NEs and networks
Hardware The laptop or PC must meet the following requirements in order to properly run the OMS:
Requirements OS versions: Windows 2003, Windows 2008, Windows XP SP2
2 GB or more or RAM
.

Appendix A: 1350 OMS Optical Management System,

Continued
1350 OMS GUI Follow the below procedure to access the 1350 Graphical User Interface (GUI)
connectivity
Step Action
1 Obtain the host name / IP address of the OMS server and user login
information
2 Edit Host file on user PC
Using windows explorer, navigate to the following location on pc
Open the hosts file using either notepad or WordPad and enter the IP
address and host name obtained in step 1
(for example ip address: 135.221.39.222 host name: MH057)
After editing the hosts file, save the updated file and close the window


Continued
1350 OMS GUI

connectivity
Step Action
(continued)
3 Start Internet Explorer and enter the IP address of the OMS server
obtained in step 1
Click on enter
NOTE:
For first time log in to the OMS, the server will download some applications
to the local laptop/PC, this process may take up to 10 minutes for all of the
software to be downloaded


Continued
1350 OMS GUI

connectivity
Step Action
(continued)
4 When all of the required Pc based applications have been downloaded
from the OMS server, a login splash will be displayed
Enter user/password details obtained in step 1 and click on login
NOTE:
to the local laptop/PC, this process may take up to 10 minutes for all of the
software to be downloaded


Continued
1350 OMS GUI

connectivity
Step Action
(continued)
5 When the Alcatel web portal window is displayed,
Select Operation – Management and then double click on the Network
Management Icon
NOTE:
to the local laptop/PC; this process may take up to 10 minutes for all of the
software to be downloaded.
6 The network management portal:

GCD Networks

December 10, 2012
Alcatel-Lucent
GMPLS Network Report
Table of Contents
General ............................................................................................................ 2
Description .................................................................................................... 2
Feedback ...................................................................................................... 2
GMRE Network Report .......................................................................................... 3
GMRE Network Report ....................................................................................... 3
Network Element List ....................................................................................... 3
Remote Inventory ............................................................................................ 5
GMPLS NPA View ............................................................................................. 7
NPA- Nodes- Export Data ................................................................................... 8
NPA- Control Plane- Export Data .......................................................................... 9
NPA- Physical Connections- Export Data ................................................................. 9
NPA- TE Links- Export Data ................................................................................. 9
NPA- Paths- Export Data .................................................................................... 9
NPA- SNCs- Export Data ................................................................................... 10
Report Format .............................................................................................. 10
Database back-up ............................................................................................. 11
Database Back-up Overview .............................................................................. 11
NE Database Back-up for Un-protected FLC ........................................................... 11
NE Database Back-up for Protected FLC Option 1 .................................................... 16
NE Database Back-up for Protected FLC Option 2 .................................................... 19
List of Tables
IEH 611, Section 420 GMPLS Network Report
General
Description This section provides the Network Operators of 1830 PSS systems with the knowledge base
aimed for creating a network report of the GMRE network, remote inventory collection and
database back-ups of the PSS36/64 nodes deployed and managed using the 1350 OMS.

1830 PSS-36 5.1
1830 PSS-64 5.1
1390 NPT 5.1
1350 OMS 10.2

GMPLS Network Report IEH 611, Section 420
GMRE Network Report
GMRE Network A network report will be generated for handover to the customer of the GMRE network
Report topology, this report will include the following information
Network Elements, including TID and IP addressing information
Remote inventory
Node information
GMRE Control plane information
TE Links
Physical Connection
ASON supported SNC’s
ASON supported paths
Network To generate a network element list, use the following procedure.

Element List
Step Action
1 From network management view,
Select
Search
EML
Network Element

GMRE Network Report, Continued
Network
Element List
Step Action
(continued)
2 When EML list is generated
Select the icon to export the list to your computer
3 When the export file wizard is displayed, select the required destination folder
Click export
The EML list will be exported to the local computer

Remote To upload the remote inventory for the network elements managed by the OMS in the GMRE
Inventory network, use the following procedure
Step Action
1 From network element list,
Select
Highlight all required network element
Action
Global remote inventory

Remote
Inventory
Step Action
(continued)
2 When Global remote inventory wizard is displayed
Verify all required network element are show in list and select apply
Result: When banner at top of screen goes green, operation has been
successfully completed
Select cancel
3 The global remote inventory list will automatically be displayed
Export the list using the icon to the required destination folder


GMPLS NPA Follow these steps to generate GMPLS NPA view required for list generation
View
Step Action
1 To generate an NPA view,
Select
Search
SDH
NPAs
2 From generated NPA list

Click on Icon to generate NPA view

GMPLS NPA
View
Step Action
(continued)
3 NPA view will be displayed
NPA- Nodes- In the NPA view generated, click on the Nodes folder:
Export Data
The list generated will provide an overview of the nodes deployed in the ASON NPA and their
status for communication with the OMS management platform

NPA- Control In the NPA view generated, click on the Control Plane folder:
Plane- Export
Data
NPA- Physical In the NPA view generated, click on the Physical Connections folder:
Connections-
Export Data
NPA- TE Links- In the NPA view generated, click on the TE links folder:
Export Data
NPA- Paths- In the NPA view generated, click on the Paths folder:
Export Data

NPA- SNCs- In the NPA view generated, click on the Sub Network connections, SNCs folder:
Export Data
Report Format Please refer to the example report on the GPEC web site:
https://all1.na.alcatel-lucent.com/Teams/GCDNetworks/default.aspx
Select Optics GPEC under Team Sites.

Select 1830 PSS 36/64 OCS.
Scroll to bottom of page to select the “ASON network report example” under “Additional
1830 PSS Documents and Information”.

Database back-up
Database Back- The 1350 OMS can be used to facilitate database backups of network elements.
up Overview The database back up can be completed by using the File Transfer Scheduler or by using the
show equipment view from the network element
For PS36/64 networks, the backup must be approached with two different options, depending
on whether the FLC’s are deployed either in a protected or un-protected configuration.
NE Database To generate a database back up of the network element which is deployed with only one FLC,
Back-up for Un- use the following procedure
protected FLC
Step Action
1 From the OMS Network Management View, generate a Network element
list equipment) view of the required network element
Select
Seach
EML Network elements
2 When the Network Elements list is displayed

Select
Highlight required network Element
Search
Show equipment

Database back-up, Continued
NE Database Step Action

Back-up for Un-
protected FLC 3 When the ZIC view is generated
(continued) Select
Highlight node top level
Database operations
Start DB backup

NE Database
Back-up for Un-
Step Action
protected FLC
(continued) 4 The Start Database Backup screen will be displayed
Select
Send
NOTE:
Node will now restart communications, close the ZIC view and wait until the
node is shown as reachable on the Network Element list.
The Start Database Backup may generate an error message stating that the
server is busy, this is due to the one FLC configuration, to verify that the back
is complete:
SSH to the FLC using OAMP IP address and after login, enter:
cd /var/NE/BackupRestore/backup/data
ll
and verify backup.tgz file aligns with time that back up was initiated.
-rw-rw-rw- 1 appl appl 42163 2012-12-03 03:43:19 backup.tgz

NE Database
Back-up for Un-
Step Action
protected FLC
(continued) 5 From OMS generate ZIC view
Select
Highlight node top level
File transfer
Start Copy

NE Database Step Action

Back-up for Un-
protected FLC 6 When the File Transfer- Start wizard is displayed, define the following
(continued) parameters:
From: STBYDB- Standby database
To: RFSDB- remote file server database
Protocol- sftp
LOCATION: user ID: swdl1
LOCATION: password- swdl1692
LOCATION: FTP Host: Ip address of server
LOCATION: Port: no value
LOCATION: URL-Path: /backup name
Command mode: no value
Send
When action is finished, Command Successful will be displayed
NOTE: To verify correct upload of DB copy, log onto the OMS server:
cd /usr/Systems/EML_1/swdl/swdlserv/data/
ll
drwxr-xr-x 2 swdl1 ftpscoss 96 Dec 5 16:51 backup-03-date
Verify backup file has been uploaded to server.

NE Database To generate a database back up of the network element which is deployed with a protected
Back-up for FLC configuration, use the following procedure.
Protected FLC
Option 1
Step Action
1 From the OMS Network Management View,
Select
EML
Network Elements

NE Database
Back-up for
Step Action
Protected FLC
Option 1 2 Select
(continued) Highlight required network element
Actions
Single Click MIB Backup
The following information screen will be displayed
Click OK to close window

NE Database
Back-up for
Step Action
Protected FLC
Option 1 3 From the OMS Network Management View,
(continued) Select
Search
File Transfer Schedule
Jobs
4 From the generated Jobs list,

To view the status of the backup job,
Select
Highlight required FTS job
Search
Job Status
The following screen will be displayed
Use the Update icon to refresh the view until the job status is progress is
100% and then close this view

NE Database To generate a database back up of the network element which is deployed with a protected
Back-up for FLC configuration, use the following procedure
Protected FLC
Option 2
Step Action
1 From the OMS Network Management View,
Select
Actions
Create Job

NE Database
Back-up for
Step Action
Protected FLC
Option 2 2 When the Job Creation wizard is displayed
(continued)
Define the following parameters

*Job name- as required, job name must be unique
*Type- MIB Backup
*Activation- Immediate
Apply
Result: When banner at top of screen goes green, the FTS job has been
successfully created

NE Database
Back-up for
Step Action
Protected FLC
Option 2 3 From the OMS Network Management View,
(continued) Select
Search
Jobs

NE Database
Back-up for
Step Action
Protected FLC
Option 2 4 From the generated Jobs list,
(continued) Select
Actions
Create Backup Session
The Backup Session creation screen will be displayed

NE Database
Back-up for
Step Action
Protected FLC
Option 2 5
(continued) Click on the NE icon to generate an available NE list and select required
network element (s).

NE Database
Back-up for
Step Action
Protected FLC
Option 2 6 Click Apply.
(continued)
Result: When banner at top of screen goes green, the FTS job has been
successfully updated.

NE Database
Back-up for
Step Action
Protected FLC
Option 2 7 From the generated Jobs list,
(continued) Select
Actions
Activate Job
FTS job will be activated

NE Database
Back-up for
Step Action
Protected FLC
Option 2 8 To view the status of the backup job,
(continued) Select
Search
Job Status
The following screen will be displayed
Use the Update icon to refresh the view until the job status is progress is
100% and then close this view
Note: All FTS jobs can be scheduled to run at a predetermined date and time,
the configuration for this type of FTS configuration, is detailed in the 1350
OMS EML Guide 8DG42302BAAA

GCD Networks

December 10, 2012
Alcatel-Lucent
Troubleshooting
Table of Contents
General ............................................................................................................ 2
Description .................................................................................................... 2
Feedback ...................................................................................................... 2
Node Level Troubleshooting ................................................................................... 3
Introduction ................................................................................................... 3
Unable to start CLI session ................................................................................. 3
GMRE Activation Fails ....................................................................................... 5
GMRE Admin State Down .................................................................................... 6
Network Level Troubleshooting ............................................................................... 8
Introduction ................................................................................................... 8
Unable to detect Neighbor node .......................................................................... 8
Active GMRE alarms.......................................................................................... 8
Command History ............................................................................................ 9
Interface Status ............................................................................................ 10
Neighbor Port Information ................................................................................ 10
Label Switched Path ....................................................................................... 11
TElink......................................................................................................... 14
List of Tables
IEH 611, Section 500 Troubleshooting
General
aimed for troubleshooting GMRE application at the node level and at the network level.
Intended The audience should have a basic knowledge of GMRE application, 1830 PSS product

1830 PSS-64 5.1
1830 PSS-36 5.1
1350 OMS 10.2
1390 NPT 5.1

Troubleshooting IEH 611, Section 500
Node Level Troubleshooting
Introduction The GMRE application operates on the FLC on each node. There can be various reasons why
it may not start up correctly hence below are some verification steps which will help in
troubleshooting.
Unable to start The CLI session is invoked using an SSH terminal. The following two parameters must be
CLI session provisioned correctly for the CLI to work.
Control Plane IP address
Loopback IP address
The following steps show how to verify if the Control Plane and Loopback IP addresses are
correctly provisioned.
Step Action
1 Login to the 1830 PSS-64/36 system using ZIC
2 From the menu tree on left, expand System |Networking|. Right click on
networking and select IP Addresses | IP Addresses.

Node Level Troubleshooting, Continued
Unable to start
CLI session
Step Action
(continued)
3 Verify that the control Plane IP address is correctly provisioned.
4 As mentioned in Section 300 of this guide, Control Plane IP address can only
be provisioned once.
Hence, if the value is 0-0-0-0 only then click on Edit Control Plane IP
Address and enter the address.
If any other incorrect address is displayed in the field then contact your next
level of support.
Proceed to next step if the Control Plane IP address is correct.

5 Slide the horizontal bar to right and verify that the Loopback IP address is
correctly provisioned.
If the value displayed is 0-0-0-0 or incorrect then click on Edit Loopback IP
Address and enter the correct value.
6 Once the Control Plane and Loopback IP is verified, open an SSH session to
the active FLC and start CLI.
7 If CLI is still unable to start then contact your next level of support.

GMRE The GMRE activation command may fail to execute if parameters have incorrect value. The
Activation Fails following steps will show how to verify the parameters.
Step Action
1 Login to the GMRE application via CLI.
2 Verify that the following text output is displayed.
Welcome to GMRE Rel 5.4.0 (Build GTT25-01W)
3 If any other Rel number or build number is displayed, then stop and install the
correct software on the FLC. Refer to IEH 610 Section 300.
4 Ensure that the Config Node command to activate GMRE contains the correct
activeNetworkVersion as shown in smaple command below.
PSS64-01
5 Next ensure that cpNodeID is entered correct and does not match the Control
Plane IP address.
6 If the GMRE activation command still fails then contact your next level of
support.

GMRE Admin Once the GMRE application is activated the FLC works in conjunction with the matrix pack to
State Down provide information to the GMRE engine. The following steps will show how to troubleshoot an
Admin State Down on the GMRE application.
Step Action
1 Ensure that the correct command is entered in the CLI for GMRE activation. It
must contain adminState up parameter.
2 At the CLI prompt enter the following:
show node
3 Verify the admin state below shows the following:
AdminState: Up
4 If the Adminstate is still down then proceed to the next step.
5 Login to the system using ZIC and reboot the active FLC by righting clicking
on the active FLC and Select Initialize Board | COLD | Forced.
6 The FLC will reboot and ZIC connection is terminated for few minutes.
7 Once reboot is complete login to the CLI and verify if GMRE AdminState is UP
by entering the following command.
show node
Proceed to next step if AdminState is still down.

GMRE Admin
State Down
Step Action
(continued)
8 Login to the system using ZIC and reboot the active Matrix pack by righting
clicking on the active Matrix pack and Select Initialize Board | COLD |
Forced.
Warning: This action may be service affecting, hence take proper permissions
from Network Operations Center if there is traffic present on the system.
9 When the Matrix pack completes the reboot, login to the CLI and verify
AdminStates by entering the following command.
show node
10 Contact your next level of support if the AdminState is still down.

Network Level Troubleshooting
Introduction Once GMRE application is enabled on PSS64/36 systems in the network, each node
advertises itself to other nodes and exchanges topology information. This section will provide
CLI commands that will be helpful in troubleshooting network level problems.
Unable to The steps below will guide the user to troubleshoot neighbor discovery issues.
detect Neighbor
node
Step Action
1 Open CLI session on the two systems which are direct neighbors to each
other.
2 Enter show node and verify that AdminState on both nodes is UP.
3 If AdminState is down then refer to previous section for troubleshooting the
issue.
4 If the AdminState is UP on both systems then proceed to the next step
5 Verify that both nodes have LAN connectivity from the OAMP port on the FLC
circuit pack.
6 Next, verify that fiber link between both systems is correctly in place with
correct power levels.
7 Login to both systems using ZIC and verify there are no alarms on the optical
ports connecting the two nodes together.
8 Clear any alarm on the optical ports that are present.
9 If neighbor node is still not discovered then contact your next level of support.
Active GMRE The GMRE application reports alarms that are useful in troubleshooting network level issues.
alarms To view the current alarms on any node, follow the steps below.
Step Action
1 Open the CLI session on the system.
2 Enter the command
show alarmState
3 Any GMRE related alarm will be displayed

Network Level Troubleshooting, Continued
Command The CLI session records all commands entered so that one can review them later.
History The following steps will show to see command history.
Step Action
1 Login to the CLI session on the system
2 Enter the command
history
3 The output will display all the commands entered till this point.
PSS36-03(2)[0]# history
show node
PSS36-03
show node
show version
show node
show alarmState
show tti
history
PSS36-03(2)[0]#

Interface Status To view the interface status, the following command should be used.
show interface
The output of the show interface command is shown in the screen shot below.
Neighbor Port The neighbor port information is displayed by issuing the following command.
Information show tti
The output of the show tti command is shown in the screen shot below.

Label Switched As discussed previously, LSPs are always provisioned using 1350 OMS. One may use CLI
Path commands to view LSPs using the following command
show lsp
The screen shot below shows the provisioned LSPs.
As an example, if we want to view the details of a LSP, then we can view them using the LSP
index of the path. For example:
show lsp lspindex 6
Output:
PSS64-01(2)[0]# show lsp lspindex 6
LSP_Index: 6
LSPType: P2P
Source LSR/LSP_Id: 11.11.11.235/6
CallId: 11.11.11.235/6
DestLSR: 11.11.11.184
ProtType/Traffic/Prio: Guaranteed/ODU1/4
ConfiguredSetupPriority: 5
Connection Type: SPC
LSPDirectionType: Bidirectional
Role: Transit
AdminState/ProtState: Up/-
E2E_ProtRestType: -
LSPDesc:
Source_Based_Restoration_(Pre-calculated) 01
ReversionState: NotApplicable
Creation Time: 2012/11/26 05:18:14
SrcTNA: -
SrcTNA2: -

Label Switched DestTNA: -

Path DestTNA2: -
(continued)
DestLabels: 101050201#ODU1/1
DestLabelAvailability: -
SNCPState(upstream): -
SNCPState(downstream): -
Configured SNCPCommand(upstream): -
Configured SNCPCommand(downstream): -
RestorationMode: -
ReversionMode: -
LinkDiversity: -
LSPDiversity: -
IncludeColors: -
ExcludeColors: -
LatencyThreshold: 0
LatencyOffset: 0
MaxHops: 0
ConstraintsViolation: -
NominalUnavailableAlarms: -
AlarmDetails: -
IncomingERO: -
Backup Reroutings: 0
Backup Activations: 0

Label Switched Flow #1

Path -----------
(continued)
LegType: Main
FlowType: Nominal
FlowIndex: 2
FlowSegment: 0
FlowState: Up
APEState: -
SetupPriority: 5
NetworkVersion: 5.4.0
TotalLatency: 0
InLabels:
253#100001#101360101#ODU1/2/0/2-1-3
OutLabels:
253#100000#101360201#ODU1/2/0/1-1-2
ConfiguredRoute: -
ActualRoute: ODU1#234#101070301#ODU1/1
ODU1#234#100001#101190101#ODU1/2/0/2-1-3
ODU1#253#100001#101360101#ODU1/2/0/2-1-3
ODU1#253#100000#101360201#ODU1/2/0/1-1-2
ODU1#183#100000#101190201#ODU1/2/0/1-1-2
ODU1#183#101050201#ODU1/1
DomainExternalRRO: -

TElink In order to view the details of the TElink, the show interface command is entered with the
TElink interface id.
show interface telink 10000
Output:
PSS64-01(2)[0]# show interface teLINK 100000
IfIndex: 100000
IfName: PSS36-UPPER-03/PSS64-01-100000
IfType: TeLink
LocalDPNodeId: 253
RemoteNodeAddress: 11.11.11.183
RemoteCPNodeId: 11.11.11.184
RemoteDPNodeId: 183
RemoteIfIndex: 100000
AdminState: Up
OperState: Up
MaintState: Up
Alarms: -
TeType: P2P
LinkType: I_NNI
TEMetric: 20
MuxCapEncoding: TDM/G709_ODUk
HwType: TDM
Colors: -
Latency: 0
Srg: 1
TNAaddress: -
RemoteRcId: -
RemoteDcnOspfAreaId: 0.0.0.0
RemoteSigOOFTEPAddr: 135.117.245.183
IpTunnelEncapsulation: IPinIP
BundleType: True
MinimumServiceType: ODU0


Technical Handbook Alcatel Photonic Serv

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Technical Handbook Alcatel Photonic Serv

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent

INSTALLATION ENGINEERING HANDBOOK | IEH 611

Delivery Readiness Document

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

IEH 611, Section TOC

Release Date Section Title

IEH 611, Section 001

Table 1: Product Releases ............................................................................................... 3

2 Alcatel-Lucent – Internal December 10, 2012

Feedback Address any feedback to: gpec.optics@alcatel-lucent.com

Table 1: Product Releases

Product Name Release

December 10, 2012 Alcatel-Lucent – Internal 3

Global Product Expertise Center Resources (GPEC)

Visit the following page for GPEC’s Optics Engage page:

GPEC Optics Subscribe to GPEC Optics bulletins and news flashes:

4 Alcatel-Lucent – Internal December 10, 2012

Continued on next page

December 10, 2012 Alcatel-Lucent – Internal 5

Usage Guidance, Continued

Indicates a step/procedure where 1830 PSS ZIC (Zero

Indicates a step/procedure where 1830 PSS EZ Setup is used

Continued on next page

6 Alcatel-Lucent – Internal December 10, 2012

Usage Guidance, Continued

Indicates a step/procedure where 1830 PSS Command Line

Indicates a step/procedure where Microsoft Windows

Indicates a step/procedure where 1830 PSS TL1 is used as

Indicates an attention point wherein an installer must check

Indicates a time-saving tip or multitasking

Indicates the time-lapses to be considered within or between

December 10, 2012 Alcatel-Lucent – Internal 7

Safety Operation Guide

Continued on next page

8 Alcatel-Lucent – Internal December 10, 2012

Safety Operation Guide, Continued

DANGER: Strictly follow these instructions:

December 10, 2012 Alcatel-Lucent – Internal 9

Fiber Optic Precautions

Unenclosed During service, maintenance, or restoration, an optical fiber telecommunication system is

Continued on next page

10 Alcatel-Lucent – Internal December 10, 2012

Fiber Optic Precautions, Continued

The Figure below illustrates the procedural sequence:

Figure 1: Fiber Inspection Flow Chart

December 10, 2012 Alcatel-Lucent – Internal 11

Continued on next page

12 Alcatel-Lucent – Internal December 10, 2012

Electrostatic Discharge, Continued

Figure 2 Ground Strap

December 10, 2012 Alcatel-Lucent – Internal 13

Instruments and Tool

14 Alcatel-Lucent – Internal December 10, 2012

IEH 611, Section 100

GMPLS Network Commissioning: Principles and Preparation

Table 1: Product Releases ............................................................................................... 3

2 Alcatel-Lucent – Internal December 10, 2012

Feedback Address any feedback to: gpec.optics@alcatel-lucent.com

Table 1: Product Releases

December 10, 2012 Alcatel-Lucent – Internal 3

Core Optical Switch

Continued on next page

4 Alcatel-Lucent – Internal December 10, 2012