1830 Training

TRX-24000 Training
Release 2.1 / 4.02

Do not delete this graphic elements in here:
Module 1: DWDM Overview
1830 Photonic Service Switch 32 (PSS-32)

All Rights Reserved © Alcatel-Lucent 2009
Objectives
2
At the end of this lesson, the student will:

Understand how optical networks have evolved from single-wavelength
optical – electrical – optical (OEO) SONET networks to all-optical DWDM
networks
Understand DWDM terminology
Understand the issues that can affect DWDM transmission
Signal attenuation
S/N ratio
Dispersion
Non-linear effects

1830 PSS-32 Release 1.0
Evolution of Digital Communications
3
Simple phone conversation: DS0 = 64 kbits / sec
Time Division Multiplexing: Increases the capacity of a

signal electrical line to carry more data.
DS1 = 24 channels (1.544 Mbit/sec)
E1= 32 channels (2.048 Mbit/sec)
T3= 672 channels (44.736 Mbit/sec)
E3= 512 channels (34.368 Mbit/sec)
Rates above T3/E3 are usually in the optical domain. These are given in rates with notation
OC-X or STM-Y (SONET / SDH terminology)
OC3 = STM1 = 155.52 Mbit/s OC12 = STM4 = 622.08
Mbit/s
OC48 = STM16 = 2488.32 Mbit/s OC192 = STM64 = 9953.28 Mbit/s

Optical Frequencies
4
Frequency
Ultra
X-Rays Visible Infra-Red (IR)
Violet
…
850nm 1310nm 1550nm
Broad Mono- What we call light is actually

spectrum chromatic light just the visible part of the
light electromagnetic spectrum.
Light from the sun is a range
LASER of different frequencies.
Mono-chromatic devices like
lasers operate a single
frequency.
650nm

Signal Attenuation Over Distance
5

First Generation Optical Networks: SONET
6
1310 Optics
Optical Optical Optical Optical Optical

Mux Up to 60 km Regen Up to 60 km Regen Up to 60 km Regen Up to 60 km Mux
1310 nm (or more) 1310 nm (or more) 1310 nm (or more) 1310 nm (or more) 1310 nm
Tx/Rx Tx/Rx Tx/Rx Tx/Rx Tx/Rx
15XX Optics
Optical Optical Optical Optical Optical

Mux Up to 100 km Regen Up to 100 km Regen Up to 100 km Regen Up to 100 km Mux
1550 nm (or more) 1550 nm (or more) 1550 nm (or more) 1550 nm (or more) 1550 nm
Tx/Rx Tx/Rx Tx/Rx Tx/Rx Tx/Rx

Optical Networks Evolution : DWDM
7
Optical Xpndr Optical

Mux #1 Short WDM Xpndr Short
Mux #1
Ch #1 Ch #1 Reach
1310 nm Reach 15XX “Terminal” 15XX 1310 nm
Tx/Rx Sites Tx/Rx
Optical Xpndr
W EDFA
W Optical
Xpndr Short
Mux #2
1310 nm
Short
Reach
Ch #2
15XX
D Up to 100 km
(or more)
(Amp) Up to 100 km
(or more)
D Ch #2 Reach
15XX
Mux #2
1310 nm
Tx/Rx M No OEO M Tx/Rx
Optical Xpndr WDM “Amplifier” Sites Xpndr Short Optical

Short Ch #n Reach
Mux #n Reach
Ch #n
(typically up to 4 or 5 Mux #n
1310 nm 15XX 15XX 1310 nm
Tx/Rx between Terminal Sites) Tx/Rx
SONET/SDH on WDM (additional capacity requires only additional Transponders

[Xpndrs], no additional equipment required at “hut” sites)
Fault Isolation – Use SONET/SDH PMs and Optical Power readings

DWDM Terminology
8
Lambda (λ):
Greek symbol used to represent a wavelength
Wavelength (λ): eg. 1590.21nm
Length of an electromagnetic wave in a particular medium (ie. glass).
ITU Grid #: eg. 59
A numbering scheme for wavelength frequencies by the International Telecom Union standardizes wavelength
frequencies into a number
Decibels (dB): eg. -17.4dB
Relative unit of power measurement, logarithmic in nature (ie. 2x power is 3dB)
Decibel-milliwatt (dBm): eg. 1dBm
Absolute unit of power measurement, referenced to 1mW of power (0dBm = 1mW)
Attenuation: eg. 0.25dB/Km
Amount of power loss of signal as it passes through component or fiber optic cable.
Chromatic Dispersion(CD): eg. 100ps/nm*Km^2
Spreading of an optical signal as it travels through components or down fiber optic cable.
Optical Signal to Noise Ratio (OSNR): eg. 20dB
Relative measure of the difference between signal strength and noise floor.
Bit Error Rate (BER): eg. 10^-12
Measure of number of errors seen on a link.

WDM Issues
9
Signal Attenuation
Signal / Noise Ratio
Dispersion
Non-linear effects
Fault Isolation
Complicated Network Designs
80 km Amplifier
P P P P
Signal Attenuation Signal / Noise Ratio

Chromatic Dispersion
10
Higher bit-rates (i.e., shorter pulses) are more affected by chromatic dispersion
Limits ‘how fast’ and ‘how far’
Combat CD by using DSF and NZDSF or dispersion compensators

Link Budgets
11
40Km
3
0 Transmit Power
-3
-6 Budget = TX – RX
-9 = 3dBm - -18dBm
-12 = 21dB
-15 Receive Power
-18
-22
MIN RECEIVE THRESHOLD Min Receive Power
WDM Constant Loss Fiber WDM Max Budget = TX – RXmin

= 3dBm - -22dBm
Mux (0.25dB/Km) Demux = 24dB
5dB 10dB Total 3dB

Optical Budget
12
Optical budget = Output power – Input sensitivity

Optical budget is affected by:
Fiber attenuation
Splices
Patch panels / connectors
Optical components (filters, amplifiers, etc.)
Bends in the fiber
Contamination (dirt, oil, etc.)

Technical Design Elements: Power Penalties
13
• Penalty Ranking Original Signal

Fiber loss (attenuation)
Splices
High to Low
Connectors
Dispersion Penalties
Fiber Nonlinearities Penalties
Component / Fiber Aging Penalties
Signal After Power

Penalties

Not All Fiber is Created Equal
14
SMF (standard, 1310 nm optimized, G.652)

Most widely deployed so far, introduced

in 1986, cheapest
Corning SMF-28
DSF (Dispersion Shifted, G.653)
Intended for single channel operation at
1550 nm
Highly susceptible to non-linear
penalties.
NZDSF (Non-Zero Dispersion Shifted, G.655)
SMF/LS (limited slope) fiber from
Corning
Later fiber types are engineered for
WDM operation in the 1550 nm region

Optical Networks Evolution: OADM
15
WDM OADM WDM

Terminal Amp Amp Amp Site Amp Amp Amp Terminal
Site (no OEO) Site
Optical Add-Drop Multiplexers (Static or Remotely Configurable) provide all-

optical transport
Eliminate critical Fault Sectionalization point
End-to-end distances can become much greater.
Fault Isolation
Use SONET/SDH PMs at WDM Terminal Sites
Only Aggregate Optical Power readings elsewhere unless using OSA

Module 2 – Hardware

Objectives
17
At the end of this lesson, the student will:

Understand the hardware components that can be used in a
1830 PSS-32 NE:
Common equipment
Optical cards
Transponder cards
How the components fit into a rack

1830 PSS-32 Network Element
18
The Alcatel-Lucent 1830 PSS-32 system supports three types of shelves:

universal, DCM, and SFD.
Universal shelf
• The universal shelf is the basic building block for the Alcatel-Lucent 1830
PSS-32 network element (NE). It provides a framework for all active modules
in a system (such as controller, interface cards, etc.).
DCM and SFD shelves
• DCM and OMD shelves (SFD shelves) are passive module shelves that hold DCM
and SFD44 modules. These modules provide dispersion compensation and
optical mux/demux function associated with core optics modules (line drivers
and CWR8, respectively) that are present in the universal shelf. Each Alcatel-
Lucent 1830 PSS-32 Network Element (NE) includes up to 8 universal shelves
and up to 24 DCM/SFD shelves

1830 PSS-32 Shelf View
19

Power and Grounding
20
•Nominal voltage is –48V or -60V DC

•Operate fault-free in a voltage range of
-40V DC to -72V DC.
•Each shelf has its own power connections
•Fully redundant, with two circuits, A
and B, able to supply power to the
shelf. Redundant power feeds (A and B)
are connected to the power modules
•Power filters are available in 30A, 50A,
and 70A capacity
•Tolerance battery voltage decreases
below 45V ±1.5V, the Low Battery
Voltage alarm for feed is triggered
•Shelf power and ground connectors
are located as shown

Cooling
21
•Shelf is cooled by three variable-speed fans

•Fan tray located near top of shelf
•Provide full carrier class redundancy. In the
event of any single failure, fans continue to
operate, up to the maximum long-term
operational temperature limit defined in
NEBS
•Incoming air is filtered through a
replaceable air filter

Backplane
22
Provides the interface between the cards and the shelf, and the electrical
connectivity between the cards inserted in the shelf.
Used to supply power to the cards and transfer data and control information
across the shelf.
When you insert a card into the shelf, the female connectors on the card
mate with the high-density male electrical connectors located on the
backplane to make the connection.
No customer traffic flows across the shelf backplane (all traffic runs through
optical fibers connecting card faceplate connectors).

DCM and SFD Shelves
23
DCM Shelf
A DCM enclosure can hold a maximum of 16 DCM modules
The system models each DCM module as a separate shelf
SFD Shelf
The SFD44 (44-channel DWDM static filter) is modeled as an SFD shelf with a
SFD44 card
The inventory port of the SFD44 can be connected to an inventory port on a
CWR8 card

1830 PSS-32 Shelf Slot Allocation
24

Circuit Packs
25

Circuit Packs (continued)
26

Required Circuit Packs
27
The following circuit packs are required in the shelf:

Equipment Controller (EC)
Power Filter (PF)
Fan module (FAN)
User Interface Panel (USRPNL) main shelf only

28
•Provides main processing and communication

function in a universal shelf and provides system
storage resource when the EC is located in the
main shelf
•Each universal shelf contains at least one active
EC. A standby EC can be configured (and
equipped) to provide controller redundancy
•Non-revertive protection arrangement
•Master EC if installed in shelf with ID 1
•Subtending shelf EC’s provides protected
communication with the EC in the main shelf
(Master EC for a node)

Power Filter
29
Battery plant redundant feeds are brought

into the system through the power filter
(PF) modules and distributed to each slot
through the backplane pins.
External (typically, battery generated) DC
voltages are filtered by the two PFs and
distributed within the shelf by a copper
power plane.
Each PF provides the 3.6V service voltage
that is distributed by the backplane. PFs
also provide power to the USRPNL panel in
the main shelf
There are three types of PF modules (based
on the maximum current supported by
embedded circuit breaker): 30A, 50A and
70A

Fan Module
30
•The fan tray plugs directly into the backplane and

connects to the power, control, and monitoring leads
•Located directly above the function card slots
•Three FAN modules, each individually monitored
and speed-controlled by network element (NE)
software

User Interface Panel
31
Connected to the main shelf and provides the following interfaces:
Visual status indication (node LED indication)
Management and communication physical access points
External Input/Output access points
Miscellaneous interactive buttons
Management and communication access points consist of the following interfaces:
Four general-purpose switched auto-sensing LAN ports (10/100BaseTX), for connection
to EMS/NMS, VoIP, and externally managed devices. The OAMP port connect NE to the
External Management System (EMS). The VoIP port connect an IP phone to an IP
managed DCN within Alcatel-Lucent 1830 PSS-32 domain. The two external LAN ports
connect to externally managed devices. These ports are auto-sensing, so either a crossover
or straight-thru Ethernet cable can be used.
Two craft ports. One is designed as a female (DB9) and the other a USB-B port. Both
support local RS-232C serial interface (support setting: 9600 baud, 1 stop bit, no
parity) for connection to craft terminal via a serial link. When USB-B port and DB9
ports are simultaneously connected, preference is given to the USB-B port. The USB-B
port becomes active, and the DB9 port is rendered inactive.
External input/output access points are implemented as DB-9, DB-15, and DB-25
connectors

Optical Cards Overview
32
Optical cards are used to filter and transport optical

signals through the network. They perform the
following functions:
Optical add/drop
Channel filtering
Amplification
Dispersion compensation
Muxing of the OSC channel onto the network
fiber for control network communications
Encoding Wavelength Tracker data onto each
channel added at the NE and decoding the
Wavelength Tracker data for each channel
traversing the NE

Line Driver (LD)
33
Two types of Variable Gain Optical Amplifier modules

(VGOAMs)
High Power High Gain (AHPHG) and Low Power High Gain
(ALPHG), of 20dB
Various configurations, depending on target power and OSNR
values in the network
Provide several functions that comprise optical transport section of a DWDM
optical line:
Unidirectional optical amplification
Optical supervisory channel (OSC) generation/termination
Dispersion compensation access points
Optical line and individual optical channel monitoring points
Optical monitoring access point (OSA access point for non-intrusive
monitoring with external equipment)
Electrical access point for remote passive module inventory
monitoring (DCM and/or SFD44 modules)

CWR8 Module
34
Colorless 8-channel Wavelength Router (CWR8) packs support drop, through, and add
path.
Incoming channels go through the first coupler, and part of the signal goes to
broadband drop port that connects to the demux port of the SFD44/10/5 for colored
drop.
Signal can connect to a test port at the input to verify the connectivity during
commissioning.
Up to eight (8) colorless drops are routed to service ports 1-8 of the 1x9 WSS.
When mesh is supported, one or more of these ports become mesh output ports. No
limitation exists on which of colorless ports are being used as mesh from optical
architecture point of view.
Through channels are routed to through port 9 of the 1x9 WSS.
The WSS has adjustable per-channel attenuation for equalizing drop and thru
channels
Colorless add channel comes into the CWR8 from the OT via an 8x1 combiner and
are coupled with the colored add channel that comes from the SFD before the
add-amplifier.
The add-amplifier is a fixed gain C-band EDFA. The output of this amplifier goes
through a VOA and is then combined with the through channel on a single fiber to
feed into the LD.

CWR8 Module (continued)
35

Static Filters
36
Static Filter DWDM (SFD) modules perform the following functions

Optical multiplexer function: receives colored optical signal from the
transponder sub-system, multiplexes the signal (together with other bands)
into a WDM signal, and launches the WDM signal to the OTS line directly
(with or without an amplification) or to the colorless port of CWR8 module
Optical demultiplexer function: receives the WDM line signal, demultiplexes
this signal, and sends the individual optical channels to the transponder sub– system
1830 PSS-32 supports two types of Static Filter DWDM modules
Static Filter DWDM 5 channel (SFD5) module which can be inserted in one
half-height, single-width slot of the universal shelf
Static Filter DWDM 44 channel (SFD44) module that is implemented as a
passive module mounted in a rack outside the universal shelf. Inventory
monitoring for SFD44 is accomplished via CWR8 or LD electrical inventory access points

SFD 44 Module
37
SFD 44 mux/demuxes up to 44 channels onto a

single fiber.
SFD44 is a passive device mounted externally to
the Alcatel-Lucent 1830 PSS-32 shelf in its own
1RU (one rack unit height) shelf.
Remote inventory information (EEPROM data
such as module name, part number, serial
number) is monitored by CWR8 or LD module
that belongs to DWDM optical line to which
SFD44 is connected
Presence of SFD44 passive module is monitored
by electrical inventory connection to CWR8/LD
module

SFD 5 Module
38
The SFD5 card performs optical wavelength

multiplex/demultiplex operations for five consecutive ITU
channels to/from an optical band
In addition, the SFD5 performs a pass-through of all
other bands from the SFD ingress port to the SFD egress
port

Dispersion Compensation Module (DCM)
39
Provides unidirectional compensation for chromatic dispersion on

the network fiber
Chromatic dispersion is an optical effect that causes a light pulse to

"spread" as it travels down a fiber:
The amount of dispersion is directly related to the distance the
light travels. The longer the distance, the greater the dispersion.
At a certain distance the dispersion becomes so great that the
receiver can no longer successfully interpret the signal, and a
DCM must be deployed to reverse the effects of the dispersion.
DCMs for standard single-mode (ITU-T G.652) fiber routes are

available for compensating 10, 20, 30, 50, 50, 60, 70, and 80 km
DCMsare installed at the mid-stage of optical amplifiers and

compensate for the line

Optical Transponders
40
These transponders share many common features:
Line-side ITU-T G.709 OTU2 standards-compliant digital wrapper (10.709 Gb/s).

Tunable line wavelength. Each transponder is able to tune to any of the 44
wavelengths (in a future release, 88 wavelengths) that Alcatel-Lucent 1830 PSS-32
supports. This drastically improves operations and inventory.
On-board variable optical attenuator to control optical line transmit power and
allow automatic channel power balancing.
Wavelength Tracker encoder. Adds a unique WaveKey to the line transmit
wavelength for network-wide monitoring.
Optical 1+1 protection for services requiring high availability.
Pluggable client optics. All client ports use SFPs or XFPs for maximum flexibility
of service and reach, and for lowest cost.
Facility and terminal loopbacks, provisionable error handling, client side digital
performance monitoring.
Performance monitoring available on all optical ports.
LC connectors are used on all optical connections in the Alcatel-Lucent 1830
PSS-32, for low cost and high density.

11G Single Port Tunable AnyRate Transponder (11STAR1)
41
The 11STAR1 transponder accepts one of several

types of 10G client signals via XFP optics and
wraps them into the 11G DWDM line signal
The following client signals are supported.
OTU2 [ITU-T G.709]
STM-64, OC-192 [ITU-T SDH, Telcordia/ANSI
SONET]
10G Ethernet WAN PHY [IEEE]
10G Ethernet LAN PHY [IEEE].
Several mappings are supported.
– G.7041 compliant GFP-F mapping
– Semi-transparent GFP-F mapping that includes
Ethernet frame preamble
– Fully transparent mapping into over-clocked
OTU-2e (11.049 or 11.096 Gb/s)
10G Fibre Channel [ANSI]

11G Single Port Tunable Multirate Muxing Transponder (11STMM10)
42
The 11STMM10 transponder accepts up to ten sub-10G client

signals of several types via SFP optics and multiplexes them
into the 11G DWDM line signal.
The following client signals are supported.
STM-1/-4/-16, OC-3/-12/-48 [ITU-T SDH, Telcordia/ANSI
SONET].
Gigabit Ethernet (IEEE). Mapping via GFP-F or GFP-T
(provisionable).
Fibre Channel 1G (FC-100), 2G (FC-200), 4G (FC-400)
[ANSI]. Mapping via GFP-F or GFP-T (provisionable)
This card supports any service-any port, i.e., any

combination of the above client signals can be mixed on any
combination of client ports, as long as the aggregate
client bandwidth does not exceed the payload of the G.709
line signal.
As an example, when uniform clients are offered, the
maximum capacity of the 11STMM10 is as follows:
4 x OTU1/ STM-16/ OC-48
8 x STM-1/ OC-3/ STM-4/ OC-12
9 x Gigabit Ethernet
10 x FC-100
4 x FC-200
2 x FC-400

11G Single Port Tunable GbE Muxing Transponder (11STGE12)
43
The 11STGE12 transponder accepts up to ten

Gigabit Ethernet client signals via SFP optics and
performs non-blocking multiplexing into the 11G
DWDM line signal (there are 12 physical client SFP
cages, but in R1.0 only ten are usable.

Loopbacks
44
The two basic types of loopbacks are:

Line (Facility) loopbacks - The received optical external transmission signal
on the target facility is capable of being looped from the port function input
back toward the port function output. It is permissible to loopback the
electrical signal of the optical interfaces as opposed to the optical signal.
Each interface of a multiple interface port function is capable of being
looped back independently
Terminal loopbacks - The electrical transmission signal on an optical
interface port function is capable of being looped from the port function
output back toward the port function input. Port functions include optical
interfaces at various rates. The placement of the terminal loopback on any
particular port function is a compromise between having the loopback be as
close as possible to the physical interface and having the terminal loopback
support transparent data flow

Loopbacks (continued)
45

TRX-24000 Training
Release 2.1 / 4.02
Module 4 – Management Interfaces

Objectives
47
At the end of this lesson, the student will be able to:

Describe the different methods and options for connecting 1830 NEs to
the control network
Describe the various management interfaces
Command line interface
Web interface
1354RM-PhM
Connect to an NE using the various management interfaces

User Interface Panel (USRPNL)
48
User Interface Panel (USRPNL)

User Interfaces
49
Web User Interface (WebUI)

Provides web-based access to the network element (NE)
WebUI interface is accessed using Internet Explorer running on a computer that is
connected via Ethernet to the NE, either directly or over a LAN
WebUI supports provisioning, administration, performance monitoring, and display of
alarms and conditions from the NE
Provides a tool to assist in the initial installation and troubleshooting of NEs
Command Language Interface (CLI)
A line-oriented user interface that runs on the NE (like Hyper Terminal)
User can access the CLI using a terminal device connected to the NE
CLI provides commands that allow the user to configure, manage, and monitor the NE,
the NE interfaces, and the services running on the NE

User Interfaces (continued)
50
Simple Network Management Protocol (SNMP)

SNMP communications occur over the 1830 PSS control network
SNMP has two types of entities
• Management network elements (managers)
• Managed network elements (agents)
• SNMPv2c
User Panel (USRPNL)
User Panel (USRPNL) located on the main shelf, which supports the
majority of communication connections for the NE
This user panel includes the following ports:
• Craft serial connection via DB9
• Craft serial connection via USB-B
• Craft LAN connection via RJ45
• OAMP LAN connection via RJ45
• VoIP LAN connection via RJ45

51
Two LAN Ports (USRPNL)

OAMP port
OAMP port is used to connect to the External Management System (EMS) and
is the main control interface to the NE. The signaling format is 10/100BaseT
Default, the OAMP LAN inherits the Router ID IP address when the OAMP LAN
port is enabled for service
IP address of the OAMP LAN port can be user provisioned
VoIP port
VoIP port is used to connect to an IP phone
VoIP port supports a fixed IP address
IP address and status of the port can be user provisioned
The OAMP and VoIP ports on the USRPNL are disabled by default
The ports designated as the OAMP and Craft ports on the USRPNL, support
access to the CLI and TL1 commands.

52
Craft Interface
Two craft ports including a female (DB9) and a USB-B port
Both ports support local RS-232C serial interface for connection to a CIT via
serial link
Either the DB9 port or the USB-B port can be used to connect serially to the
NE
Only one port can be active at any given time. The NE automatically detects
the presence of a laptop (or any equivalent active device) when it is connected
to the USB-B port on the USRPNL
When both USB-B port and DB9 ports are simultaneously connected,
preference is given to the USB-B

53

1830 PSS shelf contains one or two ECs (depending on whether redundancy is
desired)
EC provides four auto-sensing RJ45 LAN ports
• First port (labeled CIT) located at the topmost of the EC, is dedicated for CIT
connection
• Active by default for ECs residing on the master shelf, and disabled by default
for ECs residing on sub-shelves
• Can be provisioned enabled or disabled
• ES1 and ES2 ports used to connect to 1830-PSS extension shelves (sub-shelves)

Communications Network
54
The basic communications network architecture for the 1830-PS includes all
LAN interfaces, OSC interfaces, and GCC interfaces
LAN interfaces include the OAMP, VoIP, CIT, and Extension Shelf (ES)
connections
Optical Supervisory Channel (OSC)
OSC carries node-to-node communication
The OSC is a separate optical channel, operating at the STM-1/OC-3 rate of 155 Mb/s,
that transfers management and control information between the ECs of two adjacent
nodes, regardless of whether any of the DWDM payload channels are terminated
between those two nodes
General communications channel (GCC)
No OSC available in CWDM transmission, so the GCC0 bytes in the G.709 overhead are
used for inter-node communication
For management connection extension to Alcatel-Lucent 1830 PSS-1 Edge Device
Gateway network element (GNE)
The network management system can manage an 1830 PSS-32 network while only
connecting to a single 1830 PSS-32 NE. That NE is called a GNE and provides the
management connectivity to all other 1830 PSS-32 NEs in the network

NE Interface Connection Summary
55

NE Interface Connection Summary (continued)
56

Management connectivity methods
57
Two methods by which NEs can

communicate with each other:
Using the OSC channel
Uses the optical fibers used to
OSPF Routing
connect the NEs in the network
N e tw o rk
NE routing table maintained
using OSPF In te r-N E
SNM P C o m m u n ic a tio n
By connecting to an external o v e r IP
network through the DCN port
Uses Ethernet cables S tatic R ou te via
DCN
A default route is configured
between the NE and a router NM S
An NE with DCN enabled is also
called a Gateway NE (GNE)

Management connectivity details
58
Optical Supervisory Channel (OSC) Connectivity

Uses 1510 nm optical channel, multiplexed onto C-Band traffic channels and is
terminated on the amplifiers via pluggable SFP.
Provides 100 Mbps Fast-Ethernet connection between NEs
Ports will automatically discover each other if connected
Gateway Network Element (GNE) Connectivity

Uses DCN Ethernet port to connect NEs to customer data network
Requires default route

Management connectivity options
59
1. Direct connection through the DCN Ethernet port

Each NE connected to the management network
through the DCN Ethernet port
The DCN Ethernet port supports 10/100 and auto-
negotiates accordingly.
Configure the following attributes on each NE:
DCN IP address
DCN IP address mask
Default router IP address
Benefits
ease of use
simple to configure
Limitations
requires Ethernet connectivity from NE to management
network at each site

60
2. Single GNE with static route

One NE selected as the gateway (GNE) NMS Client
1354RM-PhM, web and CLI access via the GNE
NMS Client NMS Server
OSCs for inter-NE communications
Gateway NE configuration
DCN IP address and mask
Static Route (which is redistributed)
Router
DCN routestate = redistribute
NE loopback IP address and mask
Configuration of other NEs Management Network

Router configuration
auto-negotiation enabled, or 10Mbps half-duplex
Router
static route for the NE loopback IP address subnet
Benefits
simple to configure and use
in-band management of network via a single connection to the Node1 Node3
management network
Limitations
single point of access for 1354RM-PhM
requires network router(s) have a static route to 1830 gateway NE
Node2

61
Dual GNEs with IP routing

The gateway network elements (GNE) run OSPF on their
DCN Ethernet ports, which peers to co-located routers
G1 and G2
Routers G1 and G2 run an exterior gateway routing
protocol (EGRP) and peer with Router 1 and Router 2.
The supported EGRP configuration is the Border
Gateway Protocol (BGP)
Configuration of other NEs
Router configuration
auto-negotiation enabled, or 10Mbps half-duplex
Benefits
In the case of a physical port failure, or network
element failure, the IP network routes around the
failure, thereby providing a redundant path.
in-band management of network via a single
connection to the management network
Limitations
A failure within the operating company's IP network
does not cause the NEs to switch to an alternate GNE,
resulting in possible loss of management connectivity.

Connecting to the NE
62
CLI Client
Connect through the active CC serial port with null modem cable.
Serial
port settings: 9600 bits/s, 1 stop bit, no parity.
Connect through the EC CIT local Ethernet port with a straight thru or crossover cable.
>telnet to “default gateway” IP address assigned by DHCP server running on NE (use ipconfig
on client PC to determine address)
Connect remotely using a telnet client to telnet to the NE IP address.
>telnet 172.21.152.126
Web Interface connection
The web interface provides user access to the NE using the Internet Explorer browser (version
6.0 or higher, with Java plug-in version 1.5.0.03 or higher). It is included with the NE software.
>http://172.21.152.126

NE Connectivity
63
GNE can be configured to redistribute traffic from the NE rings.

Network Elements can be accessed directly from the Equipment Controller (EC)
Ethernet ports or UserPanel serial port or over the network.
Node Loopback Addresses Local Craft Access

10.27.1.2 10.27.1.3 169.254.3.1
DHCP-assigned
(typically 169.254.3.2)
EMS Server GNE Router
Local Craft
10.15.25.5 10.156.25.1
Node #2 Node #3 PC:
Web / CLI
DCN Router(s)
CLI or WebUI
Network Access Node #1 Node #4
OSC Connectivity
EMS Router Node #5

10.15.25.1 DCN Port
10.156.25.4 10.27.1.4
10.27.1.1 10.27.1.5

Connectivity Example
64
EMS Server EMS Router Node Loopback Addresses Local Craft Access
10.15.25.5 10.15.25.1 10.27.1.2 10.27.1.3 169.254.3.1 DHCP-assigned
(typically
GNE Router 169.254.3.2)
10.156.25.1
EMS
Server Local Craft
Node #2 Node #3 PC:
Web / CLI
EMS
Client /
Web UI
DCN Router(s)
EMS Client Node #1 Node #4

and/or Web UI OSC
10.15.25.2 Connectivity
Node #5
Management DCN Port
Network 10.156.25.4 10.27.1.4
NTP Server 10.27.1.1

10.16.3.3 10.27.1.5
NTP
Server Node Loopback Addresses

1354RM-PhM Overview
65
Specifications:
manages only 1830 NE’s
can manage up to 250 NEs
maximum alarm processing throughput
is 1000/sec for 10 second burst
1354RM-PhM Engineering Guidelines:
no more than 100 simultaneous users
communications between the client
and server is at least 10 Mb/s
communication link between the server
and network is at least 10 Mb/s

Command Line Interface (CLI)
66
Commands
CLI commands are not case sensitive. That
is, command, CoMmAnD, and COMMAND are
all interpreted as the same command.
Strings
Any strings you enter as command variables
are case sensitive. That is, "This is a
string", is not the same as "This is a
STRING".
Question mark (?) help
Lists the currently available options. For
example config? lists all of the
subcommands in the config hierarchy.
TAB Key for command completion
Completes the command or options
Star (*)
Displays a list of possible cards/ports.
Help command
help from the main menu displays the
available help topics. help <keyword> lists
all commands that contain the keyword.

CLI Command Structure
67
Most of the CLI commands are grouped by function into the

following major hierarchical categories:
config
Commands in the config hierarchy allow you to configure the network element
and network services.
show
Commands in the show hierarchy allow you to view the current network element
configuration.
Within each category, the commands are grouped hierarchically by
subcategory. For example, all of the commands used to configure
interfaces are grouped under the “config interface” hierarchy.

Web Interface
68
Web Interface can be accessed

using Internet Explorer.
Active Alarms
Each NE is an http server – connect
by entering NE IP address as URL in
Internet Explorer.
Graphical interface with similar
functionality to CLI.
Navigation Pane

TRX-24000 Training
Release 2.1 / 4.02
Module 5 – Commissioning

Objectives
70

Describe the attributes that must be configured to commission a NE
Describe how to make a direct connection to a NE for web or CLI access
Use the NE configuration wizard to commission the NE

NE Commissioning Overview
71
Performed after hardware installation and before network commissioning

Configures the NE IP addresses, name, mode, time and date, etc.
Requires the CLI or web interface (some functions are CLI only)
Basic tasks performed using the NE Configuration Wizard
Required tasks Optional tasks
1. Connect to the NE Set the NE descriptive information

2. Clear Database Enable or disable NE features
3. Upgrade software
4. Clear the database and IP address
5. Run the NE configuration wizard
6. Run manual audit on software and commit shelf
7. Set the NE date and time or configure NTP server
8. Configure the SNMP server on the NE
9. Verify the settings
10. Fiber the NE

Clearing the preset database and IP address
72
All Equipment Controller modules are shipped with a populated database

Before the EC module can be used in a new deployment, the preconfigured
database and IP address must be cleared
Use CLI command config database clear ipclear
Not supported in the web interface
After the database and IP configuration are cleared, the EC reboots and the
NE configuration wizard is automatically launched upon CLI or WebUI login.

Running the NE configuration wizard
73
CLI or web interface

Runs automatically upon login to an uncommissioned NE
Prompts for the following:
Ring configuration (ring or no ring)
Ring Id (if part of ring)
NE Id
NE Name
Loopback IP address
DCN Port Configuration (optional)
Default Gateway IP address (optional)
All of the above parameters can be changed after the NE is

commissioned
NE restarts when complete
In case of failure, log out and log back in to restart wizard

NE Configuration Wizard (Web Interface)
74
If checked
“Configure As Gateway NE”

NE Configuration Wizard (CLI)
75
**
** NOTICE: This is a private computer system. Unauthorized
** access or use may lead to prosecution.
**
NE Initial Configuration...
Please answer the following questions to complete the initial configuration
of the Network Element (NE). When a default value is available, it is
shown inside angle brackets <>. To accept the default value, just press
the enter key.
An IP address and network prefix must be specified in the CIDR address
format of "IP address/prefix", where prefix is the number of bits for
the network part of the address.
Is this NE part of an optical ring (yes/no)? y
Enter the Ring Id (1 to 62): 1
Enter the NE Id (1 to 30): 2
NE Name<NE_1_2>:
Loopback Configuration:
Enter the IP address and network prefix<10.7.1.2/27>:
DCN Port Configuration: (to skip this step, accept the default value of 0)
Enter the IP address and network prefix<0>: 10.1.200.80/16
Default Gateway Configuration: (to skip, accept the default value of 0)
Enter the IP address<0>: 10.1.2.1
Configuration Summary:
----------------------
Ring ID: 1
NE ID : 2
NE Name: NE_1_2
Loopback IP Address: 10.7.1.2/27
DCN port IP address: 10.1.200.80/16
Default Gateway : 10.1.2.1
Save configuration (yes/no)? y
Please wait for the NE to restart...

Setting the NE date and time
76
Two methods: using the NE’s internal clock, or synchronizing to an NTP server.
NTP is highly recommended
Provides a reliable, consistent, and accurate timing mechanism for the NE using Coordinated Universal
Time (UTC)
Using the NE clock may cause events to appear out of order.
Using NTP
Each NE can use up to four NTP servers, indexed by number.
If the 1354RM-PhM is an NTP server, it can set this automatically when the NE is discovered
Adding an NTP server to the NE causes it to automatically get its time from the NTP server.
The NE automatically selects the highest stratum NTP server with which it can reliably communicate.
If the NE loses communications with an NTP server, it automatically selects the next best available
server.

Configuring the SNMP server on the NE
77
NEs communicate their status to the

1354RM-PhM using SNMP messaging
Specify the following SNMP attributes on
the NE:
The network management workstation, or
workstations, to which to send the SNMP traps.
The SNMP community strings used to provide
authentication between the network element
and network management workstations.
1354RM-PhM will set the SNMP attributes
automatically once the NE is discovered by
the 1354RM-PhM
Use CLI, or Web, or 1354RM-PhM UI to
provision 3rd party SNMP trap destination

TRX-24000 Training
Release 2.1 / 4.02
Module 6 – Power Commissioning

Objectives
79

Describe the automated power management features of the 1830 PSS-32
Describe how to use the 1354 RM-PhM (NMS) Commissioning Wizard to
commission the NEs in a TOADM ring or a FOADM network and perform
power commissioning on the network

Network Types & Power Commissioning
80
There are three types of networks:
1. Auto-power managed (TOADM network)
Requires complete TOADM ring network topology
All nodes are connected by OSC SFP’s
Ingress amplifiers are required in all nodes
Network designed and validated by Engineering Planning Tool (EPT)
Automated NE and power commissioning performed by 1354RM-PhM wizard (using
input from EPT network commissioning file)
2. Manually-power managed (FOADM network)

Wide variety of network and node configurations
Automated NE commissioning performed by 1354RM-PhM wizard
Manual power commissioning performed by user (using input from EPT files)
3. Hybrid mixed TOADM/FOADM (part auto-power and part manually-power

managed)
Wide variety of network and node configurations

Network Commissioning Overview
81
Network commissioning is the final step before the network is ready to

carry live services. Once a through path has been commissioned,
additional services can be added to the path without requiring thru
path changes.
Auto Power-managed Manually Power-managed
Network Commissioning Wizard Network Commissioning Wizard
Fully Automated Power Commissioning Partially Automated Power Commissioning
Only through-path cards required (no Requires test service(s) or actual service(s)
transponders or channel filter cards be installed (need channel filters and
needed during power commissioning) transponders)
Ensures any-to-any connectivity once Ensures point-to-point connectivity once

complete (guarantees all possible paths) complete (tests only the path of the
service(s) created)

Network Commissioning – Prerequisites
82
Prerequisites
nodal commissioning has been completed
cards are inserted into the correct slots
no unexpected alarms on the nodes being commissioned
Engineering Planning Tool was used to create the FOADM ring or point-to-point link
Engineering Planning Tool network commissioning file is available

Network Commissioning – Provision System
83
From the top menu select Provision ->

Provision System (using plan)... The Provision
System wizard will open as shown below
An overview of the network commissioning

process and prerequisites is given before
the user is prompted to select the network
commissioning file.

Network Commissioning – Provision System
84
The user is prompted to select the

appropriate network commissioning file.
The commissioning wizard verifies card

topology, creates fiber topology, provisions
power attributes and sets card
administrative status.

Network Commissioning – FOADM Network
85
To complete the network commissioning process, a service is created by the user to

ensure that the optical path is provisioned correctly to carry traffic from one point in
the network to another. Unlike an automatic power managed network, the power
commissioning process in a manual power managed network is a manual procedure.

Network Commissioning – FOADM Network
86
Create a wavelength service. Refer to “Creating or editing a wavelength service” in the 1354RM-PhM
Reference Guide.
On a FOADM system, the channel launch power defaults to –19.9 dBm at the OT on service creation.
The user must adjust this value (using value from EPT file) so that the received power at the far end
transponder port is within specification.
Launch a path trace for the service for the A to Z direction. This will allow you to view the service at
each Wavelength Tracker detect point.
Increase the launch power at the OT in increments of 3 dB (1 dB when inside 3 dB)
View the path trace for the service. Compare values at the Wavelength Tracker detect points with
the values predicted in the light path power trace file. If the losses exceed the minimum and maximum
losses, troubleshooting (fiber cleaning) will be required.
If troubleshooting does not isolate the issue, the user should re-run the EPT with actual losses found
in the network.
If power levels are satisfactory, accept the power levels.
Repeat for the Z to A direction.

FOADM Network Power Mgmt - Summary
87
Channels are individually adjusted at OT input port (launch point)

Expected powers are NOT automatically set during provisioning (will
automatically adjust to launch at manually provisioned expected power)

TOADM Ring Power Commissioning
88
Ensure the power levels for

wavelengths traversing the
network are balanced.
Automatic power
management system is used
to maintain and adapt to
new network conditions.

Automated power commissioning process
89
Automated power commissioning is a two-stage process, and

involves:
Use the Engineering Planning Tool (EPT) to design and plan the network.
The EPT data provides minimum and maximum values for span losses,
port-to-port losses between wavelength tracker detect points, and
amplifier gains. The EPT data is then exported to the 1354RM-PhM
Network Commissioning Application.
Use the 1354RM-PhM to measure the actual losses in the network and
adjust the amplifier gains to compensate for the span and card losses.
The actual values are then compared to the planned values and a loss
report is generated that flags any discrepancies.

Automatic power management
90
The purpose of automatic power management is to ensure that the channel

powers throughout the network are at acceptable levels, while at the same time
optimizing OSNR.
The approach taken is to optimize the power of all wavelengths leaving an NE,
such that all of the wavelengths leave the NE at an acceptable power level.

TOADM Network Commissioning Overview
91
Prerequisites
Nodal commissioning completed
Cards inserted into the correct slots
No unexpected alarms on the nodes being commissioned;
Control network connectivity established to all network elements
Network designed using the Engineering Planning Tool and commissioning file
generated.
The networkCommissioning.xml file created by the Engineering Planning Tool
has been copied to the machine on which the 1354RM-PhM client is running.
Automated Steps performed by the 1354RM-PhM

Verify that planned and present topology match
Provision planned power attributes to network
Verify that actual losses match planned losses
Set commissioning flag to complete

Commission Greenfield System Wizard
92
To start the Power commissioning process

select any node in the ring, select
“Commissioning” from the menu toolbar
and select “Commission Network”.
An overview of the power

commissioning process and
prerequisites is displayed before the
user is prompted to select the network
commissioning file.

Network Commissioning LPT File
93
The user is prompted to select the appropriate

network commissioning file.
The wizard checks for the following:
that the commissioning file has not been
modified since it was created by the EPT. If
the file has been modified, you are notified
and you can then locate and select a different
file.
that the number of physical NEs discovered
matches the number of NEs specified in the
commissioning file, and that the names of the
NEs match those specified in the
commissioning file. If there is a quantity or
naming mismatch, you can correct the
problems in the 1354RM-PhM.
that the inter-NE links and attributes match
those specified in the commissioning file. If
any links do not match, you are prompted to
change the link attributes to match those in
the commissioning file.
Commissioning stages
94
1. Verify card topology

2. Create Fiber Topology
3. Provision Power Atributes
4. Set Card Admin State
5. Set NEs ‘in process'
6. Adjust/Accept Power
7. Set NEs ‘completed'
8. Create loss report

Understanding the Loss Report
95
After the successful commissioning of the network, a loss report is

available detailing the measured losses and amplifier gain settings. The
1354RM-PhM highlights measured losses that are outside the range
determined by the LPT. Any highlighted areas should be investigated.

Troubleshooting network commissioning
96
Commissioning wizard stops if

network commissioning is not
successful
The progress dialog is updated and
indicates the reason for the failure
The commissioning wizard may fail
to commission the network for any
of the following reasons:
The actual network topology does not
match the planned topology.
The actual network losses do not
match the planned network losses.
The amplifier gain values required to
commission the network are outside
of the planned amplifier ranges as
specified in the EPT commissioning
file.

Network commissioning troubleshooting tools
97
The wizard provides the following functions to help you to determine

the cause of the problem:
View Loss report
Displays the loss report for the commissioning run. The loss report details nodal
and span losses and highlights areas in which the actual network losses do not
match the planned losses calculated by the LPT.
Network export
Exports the network topology to a file that can be read into the LPT.
Debug
Displays the debug window, which allows you to select a particular network
span (segment) and perform various debugging functions on the segment.

Network commissioning debug window
98
Create report
Generate a new loss report. Use to
generate a new report after power
adjusting the selected segment.
View report
View the most recent loss report.
Adjust
Perform a power adjust and accept for
the ingress and egress paths on the
selected segment.
Light segment
Light the selected segment and view, in
real time, a power loss chart that shows
the gains and losses at each detection
point along the segment,
Egress path
Display a diagram illustrating the logical
topology for the egress path.
Ingress path
Display a diagram illustrating the logical
topology for the ingress path.

Testing the through path
99
Create a temporary service

to run the BER test signal
across the network.
Configure a diagnostic
loopback on the far end
transponder.
Run traffic for 24 hours
without any errors reported
by the test.

Network Power Balancing
100
The 1354RM-PhM Power Balance feature is used to rebalance the optical powers on an
in-service network. There are 2 methods for power balancing.
Import data from the Link Planning Tool and use it to set targets and adjust powers
levels around the network
Use the current power targets and re-adjust power levels that may have drifted off
target
Prerequisites:
The network must be a ring
All of the nodes have been fully installed and commissioned, and are connected to the
DCN
All of the network elements must have been discovered in the 1354RM-PhM
There must be services in the network
There must be through-path cross-connects on all network elements. If a network
element does not have a through-path cross-connect provisioned on it, it is not
included in the power balancing
Back-up the databases of all network elements in the ring

Network Power Balancing – In-service
101
The 1354RM-PhM walks through all NEs consecutively, and

finishes by rebalancing the initial NE again.
Any NE can be selected as a starting NE for network power
rebalancing.
If several NEs require rebalancing, it is suggested (but not
essential) to pick an NE that has its ingress amplifier gain
and output power close to the target ranges.
The application begins to balance the optical power

levels across the network.
The buttons on the power commissioning window become
active as the application progresses through the
commissioning stages

Network Power Balancing – EPT Data
102
The user is prompted to locate and

select the commissioning file.
The commissioning file is used by the
1354RM-PhM to set power levels
around the network.
The application checks the following:
the commissioning file has not been
modified since it was created by the Link
Planning Tool.
the number of network elements
discovered and the names specified in
the commissioning file match.
the inter-NE links and attributes match
those specified in the commissioning file.

Network Power Balancing – EPT Data
103
The application begins to

balance the optical power
levels across the network.
The buttons on the power
commissioning window become
active as the application
progresses through the
commissioning stages.

Automatically responding to network changes
104
Power is adjusted continually or an adjustment can be manually triggered

Continuous
Automatically adjust the attenuation of channels on OT’s transponders that are connected
to a SFD44 or SFD5 so that the channel power at NE egress is equal to the planned egress
target power.
Through channels are adjusted by the CWR8 card.
Triggered
Used in a live network to compensate for changes in the loss characteristics of the
network that may occur due to fault conditions or network/fiber maintenance or upgrade.
Triggers include clearing a loss of signal condition on the network fiber or component
replacement on the through path.
Examples: Upstream fiber cut, or LD, CWR8, or DCM replacement.

Automatically Triggered Ingress Adjust
105
The aim of the ingress adjust function is to adjust the gain of the ingress amplifier until the average
per-channel output power reaches the target output power.
The ingress adjust function can be triggered manually, or automatically by the NE.
Automatically adjusts the gain of the ingress amplifier gain to achieve an average channel power at
the amplifier output.
Reset the expected power levels for all channels and change their pre-provisioned values to reflect
the actual values that are present in the network as a result of the ingress power adjustment.

Continuous Egress Adjust
106
The primary purpose of the egress adjust is to obtain the desired egress power
level for all wavelengths leaving the NE.
If an egress amplifier is not present, the NE adjusts the OT and CWR8 per channel
attenuation values as required to obtain the egress power level.
The CWR8 egress adjust only occurs when the network element detects that a
through path wavelength is present.

In-Service Power Adjustment
107
• Control loops on both TOADM and FOADM Networks

• OT’s continually adjust to meet target power
• CWR8 will continually adjust to balance channels within
reasonable range
• CWR8 will try to achieve the output power requested

TRX-24000 Training
Release 2.1 / 4.02
Module 7 – Equipment Configuration

Objectives
109

Describe the difference between pre- and post-provisioning
Identify the tools that can be used to provision an NE
Describe the provisionable attributes on the shelf equipment
Common equipment
Slots
Cards
Ports
Describe how to provision the NE physical topology
Describe how to provision protection switching

Pre- and post-provisioning
110
Two basic methods for provisioning the network element:

Post-provisioning
Hardware components are inserted into the shelf and then provisioned.
Any card attributes that are not pre-provisioned assume default values when the card is
inserted in the shelf
Only those attributes requiring non-default values need be provisioned.
Pre-provisioning
Requires that the network element be equipped with a control card only.
Can provision slots/cards/interfaces that are not physically present.
Can use all of the provisioning commands to pre-provision a network element, including those
used for service provisioning.
Cards inserted into a pre-provisioned shelf must match the provisioned topology. If they do
not, a mismatch alarm is raised.

Post-provisioning – things to know
111
Things to know:
Upon insertion, card state is automatically set to state up
All ports on through path cards are:
Assigned;
Set to state up; and
This includes LD modules, CWR8
This does not include OT’s transponder cards
For transponders:
Ports must be individually assigned; and
Port states must be set appropriately
If the 1354 RM-PhM physical topology UI is used to create the physical topology connections, the
1354 RM-PhM will automate the network port assignment and state change
If the 1354 RM-PhM service creation UI is used to create services, the 1354 RM-PhM will
automate the client port assignment and state change

Pre-provisioning and AINS
112
When pre-provisioning, you can specify that cards and ports use
automatic in service (AINS).
If AINS is enabled, all alarms are suppressed for the entity while it is
not physically present in the shelf.
When the card is inserted in the shelf, the card and the ports on the
card that are configured AINS are automatically set admin up.
For cards, AINS is automatically removed when the pre-configured card type is
inserted in the shelf.
For ports, AINS remains in effect while there are alarms on the port, and for a
configurable period of time (AINS timer) after the port is alarm free. Once the
port has been alarm-free for the duration of the AINS timer, the state will
automatically transition to a state of “In Service” and all future alarms will be
reported.

1354RM-PhM: Inventory View
113
Access by double-clicking on an NE in the

Topology View or by choosing Provision >
Inventory.
Provides the following capabilities:
view shelf and card lists and graphics
view and edit card and port attributes
view power levels at wavekey detect points
Card Lists Shelf Graphics Port Attributes

Interface Configuration (1354RM-PhM Inventory View)
114
Select an interface in the Inventory View to

list the interface attributes and their current
values. Attributes in bold can be modified.
Indicates shelf/slot/port selected
Name of card selected turns

violet
Any attributes in bold can be

modified
Holding the pointer over an

attribute will display a help tip
Actual port LED colors are

shown and automatically
updated
To apply a change, click the

apply button

1354RM-PhM: Facility/Connection View
115
Access by navigating to a
port in the Topology View
and double-clicking.
Provides the following
capabilities:
List the facilities on a given
network element
View and change the
attributes of each facility
View cross-connections on
facilities

Configuring interfaces using the 1354RM-PhM
116
1354RM-PhM Facility/Connection View

Select an interface in the Facility/Connection View to list the interface attributes and their current
values. Attributes in bold can be modified.
Indicates shelf/slot/port selected
Any attributes in bold can be

modified
To apply a change, click the

apply button

Slot Provisioning
117
Each slot on the shelf is configured for the card type that is, or will be, inserted into the slot.
Inserting a card into a slot automatically provisions the slot for the card.
If the slot has been pre-provisioned to accept a different card type, a card mismatch alarm is raised
when the card is inserted.
If a card is permanently removed from a slot, the user should set the slot out of service and
provision the slot type to “empty” to avoid future mismatch alarms.
Configurations
Empty The default. Inserting a card into an empty slot automatically provisions the slot for the
inserted card type.
Provisioned Used for pre-provisioning to specify that a specific card type is expected to be inserted
into the slot.
Present Used to identify the card type that is actually inserted in the slot.
States
Administrative state Specifies whether the card in the slot is programmed up (in service) or down (out of
service).
Operational state Specifies if the card in the slot is physically able to provide service. The operational state
is up if the card is inserted in the slot and is fault-free. Otherwise, the status is down.

Card Configuration: Common attributes
118
All cards share the following common attributes:

Card name.
Default: Card-<shelf>-<slot>
Card description.
Default: Blank
High temperature threshold. Specifies the
temperature above which the high
temperature alarm is triggered.
Default: 90°C
Low temperature threshold. Specifies the
temperature below which the low
temperature alarm is triggered.
Default: -5°C
Temperature threshold tolerance. Defines
the change in temperature that must be
exceeded before the alarm is cleared.
Default: 3°C

Transponder Port Configuration
119
Transponder interfaces provide OEO

conversion of the client signals. Configure
the interfaces for (not all attributes apply
to all transponder interfaces):
Programmed channel (BxCy or ITU
channel #)
Administrative state
Up/Down/Maintenance (note that states
are automatically set during service
creation)
Configure Line or Client loopbacks
Forward Error Correction (FEC) mode

How client port responds to upstream
event
Auto Laser Off
Auto Laser On (Inject AIS) or (idle frames)

Configuring the Channel Wavelength of the Interface
120
You need to configure the band and channel of the wavelength being
carried over the network port.
Tunable transponders
Physical topology provisioning by 1354RM-PhM will automatically tune laser to match the
SFD44 or SFD5 channel.
Note: When using the physical topology UI in the 1354RM-PhM, if the network
port has not been assigned, the 1354RM-PhM will prompt the user to assign the
port. In MOST 10G applications, the port will be assigned OTU2. This allows the
user to select a FEC mode appropriate for the application. On the 10GE LAN card,
the user can assign the network port to be 10GE LAN. If this is done, the user will
NOT be able to provision a FEC mode. This should only be used in special
applications where the Alcatel 10GE LAN network port is connected directly to
another 10GE LAN card that does not support FEC.

Port State Hierarchy
121
Some attribute changes require the user to put the port into maintenance state
Some attribute changes are service affecting (i.e. auto-negotiation, port
directionality, FEC mode)
This is to prevent the user from accidentally causes a service affecting event
Changing the port state from UP to Maintenance will not cause an outage
Rules
The network port of a transponder card can never have a lower port state than a
client port
Once a port is State UP, it cannot be put directly into UP AINS.
It must first transition through Maintenance
Example
To change the FEC mode on a 11STAR1 from EFEC to GFEC
Put all client ports into Maintenance state
Put network port into Maintenance State
Change FEC mode (service affecting event)
Put network port State UP or State UP AINS
Put all client ports State UP or State UP AINS

Transponder AINS
122
Termination point AINS

A typical use of termination point AINS is to enforce suppression of network
transponder port facility alarms until all facility problems have cleared for the
Och trail terminating on that port. This eliminates nuisance alarms when the Och
trail is initially created.
Client port AINS
Client port AINS is useful in preventing facility alarms until the facility problems
have cleared (and stayed clear) for the AINS timer duration. Client port AINS is bi-
directional. USALS, US_FLT, RFI, and FLT conditions must be cleared in addition
to all facility receive conditions.

Configuring the LOS propagation interface attribute
123
The loss of signal propagation (LOSPROP) capability determines how

a client transponder reacts to an upstream client or network failure
condition.
LOSPROP is configured per client port. A card with multiple client
ports can have LOSPROP configured differently from client port to
client port.
Turn Laser On - Inject AIS-L - Insert AIS-L on the signal and propagate
(SONET/SDH ports only).
Turn Laser On - Inject Idle Frames - Inject idle frames into the signal and
propagate (Ethernet ports only).
Turn Laser Off - Shutoff the client laser.

LOSPROP scenarios
124
Client-facing Rx failure with LOSPROP configured to LaserOff

1. LOS detected at far-end (FE) client port. LOS alarm raised.
2. LOS code sent from the FE network port using DW overhead
3. LOS code detected at near-end network port.
4. Near-end client laser turned off. Upstream auto laser shutoff
(UPSM-ALS) condition raised on client port.
Client-facing Rx failure with LOSPROP configured to InsertAISL

1. LOS detected at client port. LOS alarm raised.
2. LOS code sent from the network port using DW overhead bytes.
3. LOS code detected at the network port.
4. AIS-L inserted towards the client. UPSM-AISL condition raised on
client port.
Network Rx failure
1. Unidirectional network LOS, LOF, or LOC failure occurs.
2. LOS, LOF, or LOC failure detected at downstream network port
(depending on the ASE level). LOS, LOF, or LOC alarm raised.
3. Client ports configured as Laseroff: UPSM-ALS condition raised and
port lasers shut off. Client ports configured as InsertAISL: UPSM-
AISL condition raised and AIS-L inserted towards the clients.
Note For a bi-directional failure, items 2 and 3 also occur at the A-end.

Physical Topology
125
Defineshow the card interfaces are

connected using optical fibers.
connected to another interface (shelf,
slot, and port) on the network element
connected to an external interface,
either within or outside the 1830
network
unconnected
Topology connections are required to
be provisioned before a service can be
created. Once the topology is defined,
a service can be provisioned by:
specifying only the service endpoints on
each NE through which the service
passes (NE interfaces)
specifying only the network service
endpoints (1354RM-PhM)

Physical Topology Creation
126
Created automatically during Network

Commissioning using data from the EPT for
the through path
Can be created manually using the 1354RM-
PhM, WebUI, TL1, or CLI
Network ports automatically tuned to the
SFD44 or SFD5 channel port to which they are
connected.
NE automatically configures external
connections to another NE in the network on
system turn up (requires OSC connectivity)

Topology Channel Trail Trace
127
The 1354RM-PhM can display the path of a selected

channel through the network. This also provides the user
the ability to view the NE fiber management remotely.
To perform a topology channel trace:
In the Physical Topology view, select an interface
port on a card
Click the Lightpath Trace icon
To clear the light path trace, click the “Clear the
lightpath trace” icon

TRX-24000 Training
Release 2.1 / 4.02
Module 8 – Services

Objectives
129

Describe the services that can be provided by an 1830 network
Transponderless services (alien wavelength)
Protection options (Dual client, optical splitter, OPS, none)
Bi-directional
Manual or auto power managed
Describe the features offered by Wavelength Tracker
Describe how to provision services
Describe how to monitor power and locate faults for the services

Wavelength Service - Description
130
Allocation of bandwidth across a network from one interface to another.

For services using 1830 OT’s transponders, the end points are the client ports on the
1830 OT’s.
For transponderless services, the end points are the channel ports on SVAC module.
Implemented in two basic scenarios:
Pre-wired - all of the cards are installed, the fibers connected, and
transponders/transmitters are operating, and then the service is configured.
Pre-provisioned - the network element is pre-provisioned and the service configured
before the cards are inserted, the fibers connected, and the
transponders/transmitters are turned on.
Protection options:
Unprotected - The service will fail if any resource in its route fails.
Partially protected - Service protection exists but has at least one shared resource.
Fully protected - The service will not fail if any single managed resource along its
route fails.

Transponder-based services
131
All transponders provide transparent transmission

All transponders provide a digitally wrapped signal with Forward Error Correction
(FEC)
Protected or unprotected
11 STAR 1 supports OC-192, STM64 or 10 GE LAN PHY signals
11STMM10 supports STM-1/-4/-16, OC-3/-12/-48. Gigabit Ethernet. Fibre Channel
1G (FC-100), 2G (FC-200), 4G (FC-400)
11STGE12 supports Gigabit Ethernet

Transponderless Service
132
Provides transport of “alien wavelengths” through the

network (wavelengths that originate on third-party
transponders)
Alien wavelengths connect directly to SVAC cards
Must be tuned to one of the 44 supported
wavelengths (on the ITU 100 GHz grid)
Both ends of the service must be tuned to use the
same wavelength
Provides full Wavelength Tracker capability (path and
power trace)
All optical – no OEO conversion
Unaltered transport
No digital wrapper

Service protection options
133
Optical sub-block network connection protection (O-SCNP)

Transponders perform “switch”
No EC required, < 50 ms switch time
Switching decision made by transponder.
Splitter protection is supported on a port-by-port basis on
multi-port transponders. Each client port can belong to
different protection groups (or be unprotected).
Passive optical splitters required.
Per-channel optical line protection (with OPS)

Single ADM/router or 1830-PSS transponder at each end of the
service.
Signal split at near-end OPS card onto working and protect paths.
Far-end OPS card selects (switches) between two received signals and
sends one signal to far-end transponder Rx.
Protection of alien wavelengths

The OPS card operates in the same manner with the same features as
in optical line protection, but since it is on the client side of
redundant SVAC cards

Initiating, Clearing, or Locking out a Protection Switch
134
Automatic Protection Switch (APS) groups are created for partially protected services
(Optical Splitter or OPS card protection).
Users can initiate protection switches or configure each APS group in several ways.
User can initiate a manual or forced protection switch.
A manual switch is overridden by signal failures, signal degradations, or any other
higher-priority request.
A forced switch request overrides all other requests (e.g., signal failures, signal
degradations) unless an APS lockout is in place.
After initiating a manual or forced APS switch, you must clear the switch before
reversion can occur.
Clear APS switching to enable automatic switching and allow reversion of the
switch to occur.
Lock-out disables protection switching.
Lockout prevents switching between the working and protect paths and overrides
all switching requests. It locks out automatic, manual, and forced switches.

Wavelength Tracker Overview
135
All-optical circuits are difficult to troubleshoot, since SONET/SDH/Digital Wrapper

data (B1, B2 errors, corrected errors, etc) can only be read at Optical-Electrical-
Optical (OEO) conversion points.
Wavelength Tracker provides ITU channel #, specific ID, and power data for each OCH
trail (DWDM wavelength) in the network without the need for OEO conversion
Channel ID feature is crucial in WDM and OADM networks where multiple instances of the same
wavelength may occur.
Works with both native (1830 OT’s transponders) and alien (transponderless)
wavelengths
Wave keys encoded at input to 1830 network (SVAC or SFD44, SFD5 channel inputs)
Detected at numerous points on the system
detection points are programmed to expect particular channels
raise an alarm if the channels are not detected or if unexpected channel is present.
detection points also measure the optical power of individual wavelength services.
alarm raised if the optical power is too high or too low.
optical power range (alarm threshold) is provisionable.
Allows remote Och power level monitoring without disrupting service
invaluable during installation, commissioning, and on-going network management.

Wavelength Tracker Encode/Decode Points
136

Service provisioning overview
137
A service is defined as a wavelength that

traverses the network between two
endpoints
A service typically traverses one or more
NEs
The path the service takes through an NE
is called a cross-connect (XC)
A cross-connect is defined by the ingress
and egress points for the service on the NE
The NE physical topology defines the
internal path the service takes through the
NE
Each service is assigned a trail identifier
Fiber topology
(service name) and a pair of Wavelength
Tracker wave keys.
The trail identifier and wave key pair are
unique in the network

Services
138
Services consist of a series of NE cross-connects that define the network path used to
connect the service endpoints (transponders or transponderless).
Signals are encoded with Wavelength Tracker wavekeys when added to the network.
Services are identified in the network by an ITU channel, a unique Och trail name, and a
unique pair of Wavelength Tracker wavekeys.
1354RM-PhM recognizes adjoining XCs and manages linked XCs as a service.
Network Elements only see individual XCs and transponder ports.
1354RM-PhM
Add/Drop XC Thru XC Thru XC Thru XC Add/Drop XC
Transponder/Transponderless Transponder/Transponderless

Wavelength Service - Provisioning
139
Prerequisites
Band/channel must be configured for tunable transponders
Physical topology must be complete for entire XC path
All cards on XC path must be “admin up”
Wavelength Tracker wave key options

NE Autokeying (used to support customers who use TL1 to create services in Ring only
configurations) DO NOT USE
1354RM-PhM Autokeying (use for FOADM links or rings where there is a mix of auto and
manual power managed services)
NOTE: Wave Keys must be unique in order to properly ID all misfibered connections
Multi-client transponder cards (11STMM10, 11STGE12)
Firstservice provisioned creates NE XCs and turns up a DWDM channel.
Subsequent services created on other client ports on the same cards use the existing cross-
connect and ITU channel.
NE XCs will not be deleted on a multi-client transponder card until the last service is deleted
from that card.
Use 1354RM-PhM to create all services on multi-client transponder cards. Otherwise, unless
you discover services in the 1354RM-PhM, the user may think that bandwidth is available
when in fact it isn’t.

Wavelength Service – Using the 1354RM-PhM
140
The 1354RM-PhM provisions a service by specifying the A-end and Z-end interfaces
The 1354RM-PhM provides the following tools for creating and managing services:
Service creation (one command creates all NE XCs and sets WKs)
Service export (service definition can be stored in an off-line file)
Service import (service can be created/restored based on previously exported file)
Service upload (service created as individual NE XCs can be discovered and
managed as a service by 1354RM-PhM) – used during thru path reconfigurations
Unmanage services (service can be cleared from 1354RM-PhM without deleting XCs
on NEs – this will maintain traffic) – used during thru path reconfigurations

Adding a Wavelength Service (using 1354RM-PhM)
141
1. In the 1354RM-PhM Topological View, select the

network elements on which the service endpoints
reside.
2. Click the Add a Wavelength Service icon.
3. Enter service name and customer id.
4. Select layer rate, directionality, and protection
scheme.
5. Select Next.
6. Enter ITU (or band, channel, or port type) and

select search. The 1354RM-PhM will search for
possible endpoints on the nodes specified that
match that criteria.
7. Ensure endpoints are correct in drop down menus.
8. Select Next.

Adding a Wavelength Service (using 1354RM-PhM)
142
10. If the service endpoints are valid, the

following window will appear showing the
working and protect path (if present) for
this service.
11. Select Finish to create this service.
12. Select service options.

13. Select apply.

Wavelength Services – Adding (using 1354RM-PhM)
143
14. Examine the path power trace for

the service. When the power levels
are within acceptable ranges set by
the EPT, the service is fully
provisioned. Optical power levels
may be manipulated automatically
or manually depending on the
service path.
15. Select Close when finished. Service
successfully created

Adding Auto Power Managed Service (using 1354RM-PhM)
144
Powers are adjusted automatically by the system for auto power managed services

Adding Manual Power Managed Service (using 1354RM-PhM)
145
User is required to set OT’s and LD gains manually (approximate values are provided
by the EPT)

Adding Manual Power Managed Service (using 1354RM-PhM)
146
Expected powers
not yet set
User is required to set expected power to present power for manually power managed
detect points (once power has been manually adjusted to achieve EPT planned values)
Expected powers
are set

Wavelength Services – Deleting (using 1354RM-PhM)
147
1. Select “List wavelength services for selected NEs”.

2. Select service to delete.
3. Select delete button.
4. Select apply.

Wavelength Services – Import/Export (using 1354RM-PhM)
148
The 1354RM-PhM provides the capability to export and import service definitions. This is
useful during software and database upgrades, as well as network reconfiguration, so that
you do not need to re-create your services. Service definitions are saved as XML files.
Select service or multiple services to To import service or multiple services,

export and select the export button. select the import button and select the
XML file(s) to import.

Automatic In-Service (AINS)
149
AINS state masks alarms on an object.

Primary purpose of AINS is to mask alarms on cards, ports, and cross-
connects during network commissioning or upgrades until the equipment is
fully operational (i.e., still being turned up or tested)
AINS condition remains while the object has faults associated with it.
When all of the faults have cleared, the object will wait a period of time
designated by the AINS timer.
A global NE-wide timer value specifies the default for the NE
The default AINS timer value can be changed for specific ports
Objects cannot re-enter AINS from an in-service state. They must be

placed into maintenance before transitioning to AINS.

Module 9 – Wavelength Tracker

Objectives
151

Describe how to access and use Wavelength Tracker to monitor services
in the network

Using Wavelength Tracker to monitor services
152
Wavelength Tracker information is available from the following

interfaces
1354RM-PhM
Network-wide monitoring and graphical power reporting
Web interface
Graphical for local NE only
Text for entire network
CLI
Text based
Local NE only

Wavelength Tracker – Accessing from the 1354RM-PhM
153
Wavelength Tracker view can

be accessed through the View
menu in the main 1354RM-
PhM window.

Wavelength Tracker View (1354RM-PhM)
154
Open topology based

light path power trace
Right-click on power bar and then select

“Node Power” to show OSA-like view

Wavelength Tracker View (1354RM-PhM)
155
Query results Details for 11STAR1 Port
Query for
specific
Wave
Keys
Wave Keys
programmed
at Encoding
point

Wavelength Tracker – Fault Isolation (1354RM-PhM)
156
Alarm raised. Fault

location identified
on 1354RM-PhM.
NE traces power
along path of
Channel Powers - OADM Fiber View
Network Alarm View service to isolate
single λ spectral
equalization
problem
Path Power Trace View – Single Wavelength Channel Powers - OADM Fiber View

Troubleshooting
157
Channel reaches OT but WaveKeys

missing at downstream detect points
OSA-like view shows 2 channels

Missing and Unexpected Wave Keys Detected missing but others are present
Conclusion:
(1) Physical Topology on NE does not
match actual fibering OR
(2) Light entering OT is not the correct
ITU channel

Listing the NE Cross Connects (Web Interface)
158

Viewing the power for a cross connect (Web Interface)
159
Graphical
power trace
(local NE only)
Tabular power trace

(network-wide:
shows all nodes for
this circuit)

Viewing the WT WaveKeys (Web Interface)
160
Can view Wavelength Tracker data on a per

interface or network element basis.
Select the interface and filter by direction,
and band / channel if desired.
The channels are listed with the expected
power and the observed power.

Optical Interface WaveKey Info (Web Interface)
161
Optical interfaces which decode WaveKey information may be queried for this data.
Select the optical interface and view the WaveKey information
Select “Power
Summary”

WaveKey Power Chart (Web Interface)
162
A textual listing of all wavekeys decoded is available (Wave Keys:In, Wave Keys:Out) as well as a graphical
view of the WaveKey power levels (Power:In, Power:Out)

Wavelength Tracker Data (CLI)
163
Example of Wavelength Tracker parameter data (from CLI):

show wavekey wtmonitor <sh/sl/port> <in/out> freq

Module 10 – Maintenance and Troubleshooting

Objectives
165

Describe how the 1696 ROADM NE reports faults
Describe how to use the 1354RM-PhM, web interface, and CLI interfaces
to monitor faults in the network
Describe how 1354RM-PhM alarm correlation simplifies troubleshooting
Describe how to view logs
Describe how to configure and view performance management data

Fault detection
166
The NE provides the following fault detection functionality:

Fault monitoring
Each card continuously monitors its operation and can assess faults detected on the
card. The appropriate actions are taken, such as protection switching, alarms, and fault
indicator activation.
Diagnostics
The network element uses various diagnostic programs to verify its operation.
Diagnostics issues will cause an alarm to be raised.
Performance monitoring
Monitoring the performance of traffic signals and system resources. These features
collect statistics and metrics over time for certain parameters. When the value for a
given parameter crosses its threshold, an event is raised to serve as a threshold-crossing
alert.
Event logs
Alarms are specific categories of event logs. In addition to critical, major, and minor
alarms, there are three categories of non-alarm event logs.
Traps
Each time the network element creates an alarm, and certain event logs, it generates a
corresponding SNMP trap and sends it to the 1354RM-PhM. The trap is also sent to any
other external systems configured to receive them from the network element.

Alarms: Monitoring using the 1354RM-PhM
167
Events, such as alarms, are trapped and sent from the NE to the 1354RM-
PhM.
The 1354RM-PhM Topological View provides an alarm banner and a count
of current alarms
The alarms presented in the Topological View window represent only the
alarms currently stored in the 1354RM-PhM database that have not been
cleared, either manually or automatically.
Alarms that have been cleared can be viewed in the report manager
window.
If a NE has been out of contact, or a trap has been missed, the 1354RM-
PhM attempts to retrieve any missed alarms that are present in the
network element's SNMP trap buffer.
The 1354RM-PhM associates incoming alarms with its persistent view of
the network topology.
Alarm counts and severities are graphically represented in the 1354RM-
PhM user interface.

Alarms: 1354RM-PhM Topology View
168
alarms
1 critical alarm + 1 minor acknowledged
Alarm conditions displayed

in Topology View
Alarm pane showing alarms

and the filter that is currently
applied.

Alarm Correlation: 1354RM-PhM
169
1354RM-PhM alarms are marked as New until they have been processed by the
alarm correlation function.
The 1354RM-PhM examines each alarm it receives to determine the root cause.
1354RM-PhM alarm correlation works by analysing each alarm and finding the corresponding
light path. For each alarmed light path it analyzes its alarms to determine which are root
causes and which are sympathetic (masked) alarms, and sets the status accordingly.
After an alarm is processed, its status is set to either Root Cause or Masked.
If a common root cause for multiple alarms can be determined, and if the alarm
correlation capability is enabled, the 1354RM-PhM can group the related alarms and
display only the root alarm(s).
Related alarms can also be viewed by specifying the view options in the Alarm
window.
Alarm Correlation can be enabled or disabled (enabled by default)
In the 1354RM-PhM, choose Admin > Preferences

Alarms and Conditions: CLI
170
CR SA 07/10/18 13:30:40 OTS LOS 1/8A/1 In

Loss of signal
Condition Type
Layer Rate Location
Card Type
Date and Time
Critical
Major Service Affecting
Minor Non Service Affecting

Alarms and Conditions: CLI
171
Alarms can be viewed

using the alm (alarm)
and the show cond
commands.
The network element
alarm correlation will
change sympathetic
alarms to a not
reported condition.

Alarms: Web Interface
172

Logs
173
A log entry is a time-stamped record of

an event. These events include:
changes of state
provisioning or configuration changes made Query log records
by users
raising and clearing of alarms
the detection of software faults
Logs do not include user queries.

1354RM-PhM maintains a larger database
of event logs
Can view with the log viewer.
Note the 5 log tabs in the log view
Can configure the maximum size of the log
database, the maximum number of entries,
and oldest entry to retain.

Logs – Viewing Logs
174
1. To view logs in the 1354RM-PhM, choose

Maintenance > Log View or select the Log View
icon on the toolbar. This will display a Log
View window.
2. Select the appropriate log tab.
3. Press the “Query log records” button in the
toolbar
4. Enter appropriate search criteria
5. Specify how to sort and display data

Logs – Viewing Logs
175
When search criteria has

been entered, the top
pane will be populated
with the search criteria.
Searches can be saved as
favorites for quick access
to logs at a later time.
Separate queries are
required for each log
tab.

Performance monitoring
176
Performance monitoring (PM) statistics provide counts or measurements of

significant information that can be used to gauge the performance of the network
element and the services running on it.
The statistics gathered are used primarily for the following:
to provide instant notification, via events, that acceptable thresholds for data
such as CPU utilization or dropped packets have been crossed.
to provide a historical view of the performance of the network element over a
given period of time.
Performance monitoring statistics are gathered on
all service cards
all interface ports that perform OEO conversions or protection switching.
Gathered statistics are grouped by functional category
Each category has several monitored parameters for which you can configure
threshold crossing alerts (TCAs).
You can configure how much data is gathered, how it is stored, and how and when
you are notified if certain threshold levels are crossed.

PM Bins and Intervals
177
Data is continually gathered and stored on

each NE for the PM groups that apply to an
interface or card.
the data is placed into 15 minute and 24
hour (midnight to midnight UTC) bins
PM data is also placed into a raw bin. The
statistics in the raw bin accumulate until
cleared.
At the end of each interval period, the
PM data is moved to the subsequent bin.
The contents of the last bin are
discarded.
Can configure each data collection point to
use up to 50 bins.
allows you to maintain a historical view
of the performance of the card or
interface for up to 50 days.

PM Thresholds
178
Attribute counters in the active bin (bin 0) get incremented or updated each time an event,
such as a SONET/SDH errored second, occurs.
Can configure and assign a profile to an interval to monitor the value of each attribute in the
active bin and raise a log event when a certain threshold level is reached.
Each PM group can have up to eight profiles, all having different threshold levels.
Threshold levels you define in the profiles depend on two factors:
the interval length. For example, if you were gathering statistics for an interface over 15
minute and 24 hour intervals you would need to define two profiles, one that defines the
threshold values for the 15 minute interval and one that defines thresholds for the 24 hour
interval.
the service level of the traffic using the interface. For example, you could create a profile
with low thresholds for a premium service, and one with high thresholds for a best-effort
service.
Threshold levels tested as follows:
Every five minutes for optical power groups
Every 10 seconds for all other PM groups

TRX-24000 Training
Release 2.1 / 4.02
Module 11 – NE and 1354RM-PhM Administration

Objectives
180

Describe how to perform the following NE administration tasks:
Configure NE user accounts
Configure system logging
Customize alarm severity
Setup a TFTP server to use for software loading and database backup
Describe how to backup and restore the NE database
Describe how to perform a software upgrade

NE Accounts and Privileges
181
There are three privilege levels that can be assigned to user

accounts:
Admin
The admin privilege level provides the highest level of access to the NE.
Provisioner
The provisioner privilege level provides access to the NE functions required to
provision services on the network element.
Observer
Use a user account with observer privileges for monitoring the network, or for
training purposes.

Using 1354RM-PhM to Administer NE User Accounts
182

Setting up a TFTP Server
183
NE software includes a TFTP client.

NE communicates with TFTP server in the network to:
download NE software loads.
backup or restore the NE database.
send performance monitoring (PM) data from the NEs to the 1354RM-PhM.
TFTP server is installed on a Solaris, Windows or Linux computer
must be accessible by all NEs in the network.
TFTP server is included with the 1354RM-PhM server. If using the 1354RM-PhM, it is
recommended that the 1354RM-PhM and TFTP servers reside on the same machine.
Example configuration
Item Example location Description
TFTP Host 44.1.6.59 The IP address of the workstation running the TFTP server.
TFTP server C:\tftp The location on the host where the TFTP server is installed. This is the root directory for
TFTP. TFTP can only see the contents of this directory.
Software root C:\tftp\software\releases The software root directory, relative to the TFTP server. In this example, the value is
software\releases.
Software loads C:\tftp\software\releases\AA The directories that store the specific software loads, relative to the software root directory.
C:\tftp\software\releases\AB In this case, the values are AA or AB.

NE Database Backup (1354RM-PhM)
184
1354RM-PhM utility for NE database backup and restore.

Database backups can be performed on demand or can be scheduled to run on a regular basis.
Can provision the IP address and the path of the database backup.
Window will display the result and time of the last backup for each NE.

Scheduled NE Database Backup
185
The 1354RM-PhM can schedule periodic network element database backups.

From the backup and restore properties, select the clock icon to present the database
backup schedule. Enter the parameters appropriate for the network and select “OK”.
The following capture shows the “Schedule Backup” for the selected network element.

Scheduled NE Database Purge
186
The 1354RM-PhM maintains a

set number of network
element database backups.
The system automatically
purges older backups as new
backups are produced.
The configuration of the
purge schedule is accessed
via the Backup and Restore
window.

NE Database recovery procedures
187
If the network element is stating that an invalid database is present, the following
procedures will restore a valid database to the network element.
Requirement for the procedure is a valid backed up database from the network element.
Provides the ability to restore an older database. The restored database must be the current
software release, or one release older.
If the network element is visible from the 1354RM-PhM, follow the documented
procedure for remote network element database recovery.
If the network element is not visible from the 1354RM-PhM due to the invalid
database, a local recovery is necessary.
Local Recovery Procedure:
Requirements:
Laptop PC with an Ethernet cable
Copy of the most recent valid network element database backup
Configured TFTP server on the Laptop PC
Steps:
Connect to the active EC CIT ethernet port.
Establish an administrative session to the network element.
Confirm the alarm status of the network element
Configure the network element to restore the backup database from the local PC
· # config database server A.B.C.D
· # config database path /NE_backup.bak
· # config database restore

NE Software Upgrades
188
The 1354RM-PhM provides a utility to perform NE software upgrades.

Software upgrades can be performed on single or multiple NEs
Software upgrades can be performed manually or they can be automated
Software upgrades can be scheduled
The user selects software server address and target release directory.
Status message
window provides
user with log of
the upgrade steps
and results.

NE Software Management
189
Each card on an NE runs card-specific software

Allcards in an NE must run the same software release (except in software
upgrades).
Software is stored in non-volatile memory on the card.
Each card has two memory banks, one active and one inactive.
Active bank is used for the working software load.
Inactive bank is used for loading new software onto the card.
Control Card on master shelf
Manage NE software configuration (stored in the NE database)
Store card-specific software files for all cards supported in a particular software
load
Cards added to working system are auto upgraded to current committed release
Two loads are stored (to allow for software upgrades and backouts)
A software upgrade upgrades the software on all cards on the NE
Software is downloaded to the NE from a TFTP server
Software loaded automatically on card insertion
Ifload on the inserted card does not match the NE committed load, the correct
software is downloaded to the card from the control card
Do not add cards if NE software is not committed, as no auto upgrade will occur

Software Upgrade Steps
190
A software upgrade consists of a series of distinct steps that you can

perform automatically or manually. The major steps are as follows:
Software audit
Check of upgrade path
Is it a valid upgrade from current to desired software loads (hitless)?
Are all installed cards supported in the desired software load?
Upgrade script created
Database Backup – will be used for backout if necessary
Software download
Software is transferred to the master shelf control cards and then distributed to the
individual cards on the shelf.
This step can be done in advance of activation (e.g., day before maintenance
activity)
Software activation
Software activation (reboot cards to run new load).
Control card activated first then other cards concurrently (per upgrade script).
Software commit
Committing the software provides automatic software auditing, ensuring software
sanity on the network element.
Unable to back-out after software commit.
Enables auto-upgrade of software on all future cards added to NE.

Software Upgrade: Automatic
191
Performs all four upgrade steps

using a single command or
function
Not recommended for field
systems
Optional tasks:
Upgrade path check
NE database backup
Pro:
Simple
Con:
May require a long
maintenance window (mainly
dependent on time to
download software to all NEs)

Software Upgrade: Manual
192
Audit Load Activate Commit

Each step performed individually,
in order
Optional tasks:
Upgrade path check
NE database backup
Pro:
Can spread out the upgrade process
over a longer period of time, for
example:
to pre-load the software onto
the network element during
the day
to activate software during a
maintenance window.
Con:
Requires more user interaction

Clearing Software Upgrade Failure
193
Audit Commit
If a card is seated in the shelf

and there is an issue
upgrading the software, you
will get a software upgrade
failure alarm.
This could happen due to a
hardware or communication
problem.
To clear the alarm:
1. Select the NE that has alarm
2. Open Software Upgrade Wizard
3. Select the appropriate
software from the NMS server
4. Complete Audit
5. Commit Software

1354RM-PhM User Account Management
194
1354RM-PhM User / Password Management

User accounts
Unlocking accounts
Resets user information
Restore default factory information

Locked User on the 1354RM-PhM
195
If a user attempts but fails to log into a particular account for more
than 6 times, the user account will be locked. The next time they
attempt to login, they will get the following message:

1354RM-PhM Client Upgrade
196
The 1354RM-PhM client software will automatically update to the server

software version. The following window will be seen if the client and
server are running different version of the software.
Select the OK button and follow the instructions.

Installing the 1354RM-PhM client on a new PC can be done by entering the
following link into an Explorer window and following the instructions:
http://172.21.222.194:5960/global

1354RM-PhM Service Attribute Provisioning
197
Each client is unique and each user can set their own Service Attribute
Provisioning options. The recommended settings are Set service AINS and
Auto Keying (EMS).
This can be accessed from the Management Control Panel – Topology view
under Admin>Settings

1354RM-PhM Data Locations
198
The 1354RM-PhM stores data from the managed network in the following manner.
• /PhM directory configured to accept tftp and ftp requests for network element database backups
and software distribution
• /opt/<install directory>/stats/data directory which contains the performance monitoring data

from the managed network elements
• /opt/<install directory>/backups directory which contains the backup of the 1354RM-PhM

database
• /opt/<install directory>/archive/logs directory which contains the archived log files which have
been purged from the active system
• /opt/<install directory>/log directory which contains the server debug log files

1354RM-PhM Database Recovery Procedures
199
Use the following procedure to restore a 1354RM-PhM database.

Note: Before performing a database restore, shut down the EMS, but leave the
database running.
To restore the database
Stop the EMS on the server you wish to restore.
From the install_dir/bin directory, run dbrestore.sh backup_path_and_filename where
backup_path_and_filename is the path to and name of the file from which to restore.
cd /opt/<install dir>/bin
./dbrestore.sh /opt/<install dir>/backup/1354RM-PhM_DBfile.sql
Restart the EMS on the server.

Ensure that the 1354RM-PhM has discovered all of the NEs. For NEs that are not automatically
re-discovered, manually rediscover them.

Performance Monitoring Data
200
The 1354RM-PhM stores performance monitoring data for presentation of historical data to the user.
The directory and storage structure is as follows:
• /opt/<install directory>/stats/data/<date> All PM data for a given date
• /opt/<install directory>/stats/data/<date>/<hr-min> All PM data for a given 15 minute bin
• /opt/<install directory>/stats/data/<date>/<hr-min>/<file.stats> All PM data for a given 15 minute

bin for a given network element being monitored
• The performance monitoring data is kept for the current plus the last 14 days.
Today Today-1 Today-13 Today-14

15 min bin: 00:00 15 min bin: 00:00 15 min bin: 00:00 15 min bin: 00:00

1354RM-PhM Log Data
201
The 1354RM-PhM
can be configured
to archive network
log data to the
server disk drive.
To do so, select
the “Log view”
from the Fault
menu.
Open the options
screen and enter
the appropriate
data

Network Element / 1354RM-PhM Synchronization
202
In the event of a communication

failure between the network element
and the 1354RM-PhM, the 1354RM-
PhM will attempt to periodically re-
establish communication with the
network element. While the network
element is out of communication
with the 1354RM-PhM, the network
element will appear as a blue shaded
network element.

Advanced Data Gathering - 1354RM-PhM Issue
203
1354RM-PhM Debug Information

This is a collection of data from the 1354RM-PhM system to assist in the investigation of an
issue.
Server files to be collected:
All files from the “/opt/<install dir>/log” directory.
A copy of the 1354RM-PhM database.
1354RM-PhM client files

The “mcp_trace.log” files from the Window’s user client directory. Ie) “C:\Documents
and Settings\<user>\”. Where “<user>” was the user who was logged into the client
when the issue occurred.
1354RM-PhM log files
Select the timeframe and search criteria for all the log types required.
Export the log file by selecting the Export to .CVS File button.
Specify the location and filename for the exported file.
Click OK.


1830 Training

Uploaded by

Copyright:

Available Formats

1830 Training

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

1830 Training

Uploaded by

Copyright:

Available Formats

TRX-24000 Training

Release 2.1 / 4.02

Module 1: DWDM Overview

1830 Photonic Service Switch 32 (PSS-32)

At the end of this lesson, the student will:

All Rights Reserved © Alcatel-Lucent 2009

Simple phone conversation: DS0 = 64 kbits / sec

Time Division Multiplexing: Increases the capacity of a

All Rights Reserved © Alcatel-Lucent 2009

Broad Mono- What we call light is actually

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

Optical Optical Optical Optical Optical

Optical Optical Optical Optical Optical

All Rights Reserved © Alcatel-Lucent 2009

Optical Xpndr Optical

Optical Xpndr WDM “Amplifier” Sites Xpndr Short Optical

SONET/SDH on WDM (additional capacity requires only additional Transponders

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

Signal Attenuation Signal / Noise Ratio

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

WDM Constant Loss Fiber WDM Max Budget = TX – RXmin

All Rights Reserved © Alcatel-Lucent 2009

Optical budget = Output power – Input sensitivity

All Rights Reserved © Alcatel-Lucent 2009

• Penalty Ranking Original Signal

Signal After Power

All Rights Reserved © Alcatel-Lucent 2009

SMF (standard, 1310 nm optimized, G.652)

All Rights Reserved © Alcatel-Lucent 2009

WDM OADM WDM

Optical Add-Drop Multiplexers (Static or Remotely Configurable) provide all-

All Rights Reserved © Alcatel-Lucent 2009

1830 Photonic Service Switch 32 (PSS-32)

At the end of this lesson, the student will:

All Rights Reserved © Alcatel-Lucent 2009

The Alcatel-Lucent 1830 PSS-32 system supports three types of shelves:

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

•Nominal voltage is –48V or -60V DC

All Rights Reserved © Alcatel-Lucent 2009

•Shelf is cooled by three variable-speed fans

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

The following circuit packs are required in the shelf:

All Rights Reserved © Alcatel-Lucent 2009

•Provides main processing and communication

All Rights Reserved © Alcatel-Lucent 2009

Battery plant redundant feeds are brought

All Rights Reserved © Alcatel-Lucent 2009

•The fan tray plugs directly into the backplane and

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009