700-0040-17-08 - (Z-Series R10.0 Troubleshooting and Maintenance Guide) - Issue - 1.1

Ciena Z-Series
Packet-Optical Transport Networking Platform
Z-Series Troubleshooting and

Maintenance Guide
CyOS Release 10.0
Planet Operate Release 17.08
700-0040-17-08 Issue 1.1
June 2018
Copyright© 2018 Ciena® Corporation. All Rights Reserved.

Z-Series Troubleshooting and Maintenance Guide Release 10.0/17.08
Legal Notices, Copyright, and Trademark

LEGAL NOTICES
THIS DOCUMENT CONTAINS CONFIDENTIAL AND TRADE SECRET INFORMATION OF CIENA
CORPORATION AND ITS RECEIPT OR POSSESSION DOES NOT CONVEY ANY RIGHTS TO REPRODUCE
OR DISCLOSE ITS CONTENTS, OR TO MANUFACTURE, USE, OR SELL ANYTHING THAT IT MAY
DESCRIBE. REPRODUCTION, DISCLOSURE, OR USE IN WHOLE OR IN PART WITHOUT THE SPECIFIC
WRITTEN AUTHORIZATION OF CIENA CORPORATION IS STRICTLY FORBIDDEN.
EVERY EFFORT HAS BEEN MADE TO ENSURE THAT THE INFORMATION IN THIS DOCUMENT IS
COMPLETE AND ACCURATE AT THE TIME OF PUBLISHING; HOWEVER, THE INFORMATION
CONTAINED IN THIS DOCUMENT IS SUBJECT TO CHANGE.
While the information in this document is believed to be accurate and reliable, except as otherwise
expressly agreed to in writing CIENA PROVIDES THIS DOCUMENT “AS IS” WITHOUT WARRANTY OR
CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described
in this document are subject to change without notice. For the most up-to-date technical
publications, visit www.ciena.com http://www.ciena.com.
Copyright© 2018 Ciena® Corporation – All Rights Reserved

The material contained in this document is also protected by copyright laws of the United States of
America and other countries. It may not be reproduced or distributed in any form by any means,
altered in any fashion, or stored in a data base or retrieval system, without express written
permission of the Ciena Corporation.
Ciena®, the Ciena logo, Z22™, Z33®, Z77®, Blue Planet® and other trademarks and service marks of
Ciena appearing in this publication are the property of Ciena. Trade names, trademarks, and service
marks of other companies appearing in this publication are the property of the respective holders.
Security
Ciena cannot be responsible for unauthorized use of equipment and will not make allowance or
credit for unauthorized use or access.
© 2018 Ciena® Corporation – All Rights Reserved.
700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. Page 2
Contacting Ciena
Corporate headquarters 410-694-5700 or 800-921-1144 www.ciena.com
http://www.ciena.com
Customer technical support/warranty
In North America 1-800-CIENA24 (243-6224)

410-865-4961
In Europe, Middle East, and Africa 800-CIENA-24-7 (800-243-6224-7)

+44-207-012-5508
00 0800 77 454 (Slovenia)
In Asia-Pacific 800-CIENA-24-7 (800-243-6224-7)

+81-3-6367-3989
+91-124-4340-600
120 11104 (Vietnam)
000 8004401369 (India)
In Caribbean and Latin America 800-CIENA-24-7 (800-243-6224-7)
1230-020-0845 (Chile)
009 800-2436-2247 (Colombia)
0800-77-454 (Mexico and Peru)
00 008000442510 (Panama)
Sales and General Information North America: 1-800-207-3714 E-mail: sales@ciena.com

International: +44 20 7012 5555
In North America 410-694-5700 or 800-207-3714 E-mail: sales@ciena.com
In Europe +44-207-012-5500 (UK) E-mail: sales@ciena.com
In Asia +81-3-3248-4680 (Japan) E-mail: sales@ciena.com
In India +91-22-42419600 E-mail: sales@ciena.com
In Latin America 011-5255-1719-0220 (Mexico City) E-mail: sales@ciena.com
Training E-mail: learning@ciena.com
For additional office locations and phone numbers, visit the Ciena website at www.ciena.com
http://www.ciena.com.
Naming Conventions
The following graphical icons identify specific features or functions to stress importance:
Important! — Information that must be seriously considered.
Note: Special suggestions, advice, or information that should be

seriously considered.
Safety Symbols and Labels

Read and understand all warning labels before working with equipment.
Warning
This warning symbol means danger. You are in a situation that could cause bodily
injury.
Caution
Environment requires a moderate level of awareness. There is a moderate level of
danger to yourself or others.
Laser Equipment Present
Electrostatic Discharge (ESD) Sensitive Equipment
Safety and Compliance Information

SAVE THESE INSTRUCTIONS
Warning IMPORTANT SAFETY INSTRUCTIONS

Before you work on any equipment, be aware of the hazards involved with electrical
circuitry and familiar with standard practices for preventing accidents.
Warning Before working on the equipment, remove conductive clothing and jewelry (for
example: rings, necklaces, bracelets, key chains, metal wristwatches, and apparel with
metal buttons). Conductive items can cause serious burns or weld the metal object to
the terminals.
Warning Only trained and qualified personnel (as defined in IEC 60950-1 and AS/NZS 3260) should
be allowed to install, replace, or service this equipment.
Warning Installation of the equipment must comply with local and national electrical codes.
Warning This unit is intended for installation in restricted access areas. A restricted access area
can be accessed only through the use of a special tool, lock and key, or other means of
security.
Warning Read the installation directions before connecting the system to the power source or
installing the modules and the accessories which are intended to be used only with
Optical/Packet system.
Warning Do not perform cabling on an electrically live system. Before performing any of the
following procedures, ensure that power is removed from the DC circuit.
Warning A readily accessible two-poled disconnect device must be incorporated in the fixed
wiring.
Warning No user serviceable parts are contained inside. Contact the manufacturer regarding
service of this equipment.
Warning This device requires short-circuit protection to be provided as part of the facility. Install
only in accordance with national and local wiring regulations.
Warning The copper RJ-45 SFP modules are suitable for connection only to shielded Ethernet
intra-building cabling grounded at both ends.
Warning Do not work on the system, or connect or disconnect cables during periods of lightning
activity.
Warning Do not stack the chassis on any other equipment. If the chassis falls, it can cause severe
bodily injury and equipment damage.
Warning Stability hazard. The rack must be stabilized or bolted to the floor before you mount
this shelf assembly. Failure to ensure rack stability may cause the rack to tip over.
Warning To prevent bodily harm when mounting or servicing this device in a rack, you must
ensure that the shelf remains stable. The following guidelines are provided to ensure
your safety:
• This unit should be mounted at the bottom of the rack if it is the only unit in the
rack.
• When mounting this unit in a partially filled rack, load the rack from bottom to
the top with the heaviest component at the bottom of the rack.
• If the rack is provided with stabilizing devices, install the stabilizers before
mounting or servicing the unit in the rack.
Warning Never use the cable management guide to lift the chassis. This is NOT the intended
purpose of the cable guide. Personal injury and/or damage to the shelf assembly may
result.
Warning Ensure that all power wiring is sufficient for the load carried to the shelf assembly. All
wiring and installation must be in accordance with local building and electrical codes
acceptable to the authorities in the countries where the equipment is installed and
used.
Warning This equipment must be grounded. Never defeat the ground conductor or
operate the equipment in the absence of a suitably installed ground
conductor. Contact the appropriate electrical inspection authority or an
electrician if you are uncertain that suitable grounding is available.
Warning When installing or replacing the unit, the ground connection must always be made first
and disconnected last.
Warning This unit might have more than one power supply connection. All connections must be
removed to de-energize the unit.
Warning For connections outside the building where the equipment is installed, the 10/100/1000
Ethernet ports must be connected through an approved network termination unit with
integral circuit protection.
Warning Operating this equipment in an area that exceeds ambient air temperature of 50° C /
120° F will result in machinery overheating.
Warning Operating I-Temp equipment in an area that exceeds ambient air temperature of 65° C
/ 149° F will result in overheating.
Warning Ultimate disposal of this product should be handled according to all national laws and
regulations.
Warning Connect the unit only to DC power source that complies with the safety extra-low
voltage (SELV) requirements in IEC 60950-based safety standards.
Warning This is a Class A product. In a domestic environment, this product may cause radio
interference, in which case the user may be required to take adequate measures.
Warning This is a Class A product based on the standard of the VCCI Council. If this equipment is
used in a domestic environment, radio interference may occur, in which case, the user
may be required to take corrective actions.
Warning This equipment is a class A product and should be used and installed properly
according to the Hungarian EMC Class A requirements (MSZEN55022). Class A
equipment is designed for typical commercial establishments for which special
conditions of installation and protection distance are used.
Warning This is a Class A Information Product. When used in residential environment, it may
cause radio frequency interference, under such circumstances, the user may be
requested to take appropriate countermeasures.
Warning This is a Class A Device and is registered for EMC requirements for industrial use. The
seller or buyer should be aware of this. If this type was sold or purchased by mistake, it
should be replaced with a residential-use type.
Warning Air Management Boards are required to meet EMI certification standards. Air
Management Boards must be installed to cover all unused slots.
Caution
Environment requires a moderate level of awareness. There is a moderate level of
danger to yourself or others.
Caution To avoid damage to the Z22 shelf, do not remove the fan module from an operating
system for longer than 60 seconds.
Caution Keep all ventilation openings clear and unobstructed.
Caution To prevent damage, do NOT install or remove XFP/SFP transceivers with

cables attached.
Caution The Air Management Boards are essential to proper cooling of the shelf assembly.
Air Management Boards must be installed over all unused slot openings to prevent
damage from overheating.
Caution Do not apply power to the unit until you complete all installation steps and check the
continuity of the battery and battery return. When terminating power, return, and
frame ground, do not use soldering lug connectors, push-in connectors, quick-connect
connectors, or other friction-fit connectors.
Caution Star washers must be used for anti-rotation on all power and ground fasteners.
Caution Use copper conductors only.
Caution This equipment is suitable for installation in Network Telecommunications Facilities,

Customer Premises, and OSPs. If this equipment is installed in a Customer Premise or
an OSP environment, the appropriate hardened modules must be used and DC power
interfaces must be connected to DC power via a proper fuse panel.
Caution The intra-building port(s) of the equipment or sub-assembly is suitable for connection
to intra building or unexposed wiring or cabling only. The intra-building port(s) of the
equipment or sub-assembly MUST NOT be metallically connected to interfaces that
connect to the Outside Plant (OSP) or its wiring. These interfaces are designed for use
as intra-building interfaces only (Type 2 or Type 4 ports as described in GR-1089-CORE,
Issue 4) and require isolation from the exposed OSP cabling. The addition of Primary
Protectors is not sufficient protection in order to connect these interfaces metallically
to OSP wiring.
Caution This equipment is intended to be grounded to a Common Bonding Network per

GR-CORE-1089. Ensure that the host is connected to earth ground during normal use.
Caution Hazard Level 1M Laser radiation. Do not view directly with non-attenuating optical
instruments.
Caution This product may employ Class 1M SFP or XFP. Check pluggable transceiver label for
laser classification.
Caution Some Z-Series shelf components are Electrostatic Discharge (ESD) sensitive devices.
Conform to the following rules:
• Observe standard precautions for handling ESD-sensitive devices.
• Assume that all solid-state electronic devices are ESD-sensitive.
• Ensure that you are grounded with a grounded wrist strap or equivalent while
working with ESD-sensitive devices.
• Transport, store, and handle ESD-sensitive devices in static-safe environments.
Note This equipment has been tested and found to comply with the limits for a Class A
digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide
reasonable protection against harmful interference when the equipment is operated in
a commercial environment. This equipment generates, uses, and can radiate radio
frequency energy and, if not installed and used in accordance with the instruction
manual, may cause harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful interference, in which case,
the user will be required to correct the interference at own expense.
Note The battery return connection is treated as DC-isolated (DC-I), as defined in Telcordia
GR-1089-CORE Issue 3.
Note This Class A digital apparatus complies with Canadian ICES-003.
Contents
Safety and Compliance Information ................................................................................................. 5
New in This Release / About This Guide ...........................................................................................14
General Troubleshooting ...................................................................................................................21
Loopback Tests for Transport .................................................................................................................... 21
MAC Swap Loopback ................................................................................................................................... 24
Configuring Accedian Loopbacks .............................................................................................................. 28
Trail Trace Identifier .................................................................................................................................... 31
Keepalive Messages and Comm Fail ......................................................................................................... 33
CFP and DTM-100G OTM Port Diagnostics .............................................................................................. 33
Alarm and Event Management .........................................................................................................35
Alarms Function ........................................................................................................................................... 36
Alarm Log ................................................................................................................................................. 36
Alarm Severity Assignment Profiles ...................................................................................................... 37
Set Alarm Scope to Active Node ............................................................................................................ 41
Clear Current Alarm Scope..................................................................................................................... 42
Configuring Northbound SNMP Alarm Forwarding ............................................................................ 42
External Alarm Notifications .................................................................................................................. 44
Email Transport Method......................................................................................................................... 48
Syslog Transport Method ....................................................................................................................... 48
TL1 Transport Method ............................................................................................................................ 49
Alarms Tool Tab ........................................................................................................................................... 50
Create an Annotation .............................................................................................................................. 50
View an Annotation ................................................................................................................................. 50
Edit an Annotation................................................................................................................................... 51
Delete an Annotation .............................................................................................................................. 51
Clear All Annotations .............................................................................................................................. 51
Acknowledge an Alarm ........................................................................................................................... 52

Alarm Source ............................................................................................................................................ 52
Alarm Troubleshooting ............................................................................................................................... 52
Performance Management ...............................................................................................................53
Performance Monitoring ............................................................................................................................ 54
Monitor Counters – PM Counters.............................................................................................................. 56
Threshold Crossing Alerts (TCA) ................................................................................................................ 61
Default TCA Profiles ................................................................................................................................ 62
Cloning a TCA Profile ............................................................................................................................... 63
Holding Time ................................................................................................................................................ 64
Plotting Data ................................................................................................................................................. 65
TCAs Sub-tab ................................................................................................................................................ 66
Collect Counters ........................................................................................................................................... 67
Enabling MAC Limiting ................................................................................................................................ 68
Routine Maintenance .........................................................................................................................70
Adjusting the Fan Filter Replacement Interval ......................................................................................... 70
Z22 Fan Maintenance .................................................................................................................................. 71
Z33 Fan Maintenance .................................................................................................................................. 73
Z77 Shelf v2 Fan Maintenance ................................................................................................................... 76
Z77 Shelf Fan Maintenance ........................................................................................................................ 78
Backup, Restore, and Software Upgrades .......................................................................................81
NE Backup Configuration ........................................................................................................................... 81
Scheduled NE Database Backup and Restore ..................................................................................... 83
Monitor Running Jobs and View Job Results ........................................................................................ 87
Manage Backup Files and Database Restore ...................................................................................... 90
Software Upgrades ...................................................................................................................................... 93
Service-Affected Line Cards ................................................................................................................... 95
Viewing NE Software Information ....................................................................................................... 102
Uploading a Software Upgrade Image ............................................................................................... 103
Defining an Upgrade Task .................................................................................................................... 105
Defining an Upgrade Task—Third-Party Nodes ................................................................................ 111
Enabling a Software Upgrade Task ..................................................................................................... 116
Monitoring a Software Upgrade .......................................................................................................... 117
700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 10

Aborting a Software Upgrade Task ..................................................................................................... 118

Additional Upgrade Options ................................................................................................................ 118
Upgrade Planet Operate – 17.08 ............................................................................................................. 123
Node Cut In and Cut Out..................................................................................................................124
Z-Series Node Cut In and Cut Out on a Network ERP Major Ring or Sub-Ring ................................. 125
Converting a Z-Series Express Node to an Add/Drop Node ................................................................ 131
Accedian Node Cut In and Cut Out on a G.8032v2 Client ERP Sub-Ring ............................................ 135
Inserting a Z-Series Node into an Operational Optical Link ................................................................ 143
Removing a Z-Series Node from an Operational Optical Link ............................................................. 154
Inserting and Removing a Ciena Packet Networking Device ............................................................... 160
Appendix A: Z-Series Quick Turn-Up...............................................................................................166
Appendix B: Turn-Up Checklists .....................................................................................................170
Appendix C: Replacing a DTM-8G Module with a DTM-8 Module ................................................179
Appendix D: Replacing RCMs with XC-2800 Switch Fabric Modules to Support PSW and TSW
Modules .............................................................................................................................................181
Appendix E: Replacing XC-2800 Switch Fabric Modules ...............................................................185
Appendix F: LAD-8 / LAD-8i Conversion .........................................................................................187
Appendix G: Z-Series Packet Line Card Migration .........................................................................191
Appendix H: Z77 LCD Operations Panel .........................................................................................192
Appendix I: Port Mirroring .............................................................................................................205
Appendix J: Alarm List ....................................................................................................................208
Appendix K: OLA-010 Raman Amplifier Safety Procedure ...........................................................214
Appendix L: Acronyms and Z-Series Terminology ........................................................................217

Table of Figures
Figure 1: Loopback Testing .............................................................................................................................. 23
Figure 2: MAC Swap Loopback Example ........................................................................................................ 25
Figure 3: Alarms Tool Tab ................................................................................................................................ 50
Figure 4: Resources with PM Enabled for a Selected Object ...................................................................... 58
Figure 5: PM Counters - Rx and Tx Utilization Percentages ........................................................................ 59
Figure 6: TCA Profiles for Bandwidth Utilization .......................................................................................... 61
Figure 7: Z22 Fan Modules (Front View) – Status Panel ............................................................................... 71
Figure 8: Extracted Z22 Fan Module Rear and Side Views .......................................................................... 72
Figure 9: Slide the Fan Air Filter from the Z22 Fan Module......................................................................... 72
Figure 10: Z33 Fan Module – Status Panel and Fan Filter ........................................................................... 73
Figure 11: Z33 Fan Module Front and Side Views ........................................................................................ 74
Figure 12: Z33 Fan Module .............................................................................................................................. 75
Figure 13: Z77 Fan Module .............................................................................................................................. 76
Figure 14: Z77 Fan Unit .................................................................................................................................... 78
Figure 15: Z77 Fan LEDs ................................................................................................................................... 78
Figure 16: Installing and Removing the Z77 Fan Filter ................................................................................. 79
Figure 17: All-Nodes Backup Job ..................................................................................................................... 82
Figure 18: Upgrade History Tab .................................................................................................................... 117
Figure 19: Event Log in Planet Operate ....................................................................................................... 118
Figure 20: Nodes Connecting a Fiber Ring .................................................................................................. 132
Figure 21: Ethernet Ring Protection ............................................................................................................. 134
Figure 22: In-Band Cut-In ............................................................................................................................... 146
Figure 23: Removing Node from Optical Link ............................................................................................. 156
Figure 24: Service Card DWDM Port to LAD ................................................................................................ 167
Figure 25: Span Turn-Up ................................................................................................................................ 168
Figure 26: DWDM Channel Turn-Up ............................................................................................................. 169

Figure 27: 2.5G-LME4 to LAD Functional Test Setup .................................................................................. 175

Figure 28: PME-412 to LAD Functional Test Setup ..................................................................................... 176
Figure 29: Z77 Rear Panel .............................................................................................................................. 182
Figure 30: EFM Slot Configuration ................................................................................................................ 184
Figure 31: Locked to Disable State ............................................................................................................... 185
Figure 32: LAD-8 Cross-Connects Example ................................................................................................. 188
Figure 33: Example of LAD-8i Cross-Connects After Line Card Conversion ........................................... 190
Figure 34: Z77 LCD Operations Panel .......................................................................................................... 192

New in This Release / About This Guide
New in Release 10.0/17.08

Release 10.0/17.08 introduces the following new packet line card:
• PSW-100G2W line card: The PSW-100G2W packet line card is a 2x100G module with the
same feature set as other line cards in the PSW platform but with two coherent 100G
interfaces using WaveLogic Nano (WL3n) technology. The module is a high-capacity switch
module for aggregating and grooming Ethernet services. The PSW-100G2W module is
optimized for end-to-end packet transport solutions. The module supports standards-based
Connection-Oriented Ethernet (COE) for increased network performance and scale. See
Service-Affected Line Cards starting on page 95.
For descriptions of new features provided in CyOS Release 10.0, refer to the "New Release 10
Features" section in the Z-Series CyOS Release Notes 10.0 available in the portal library.
New in Previous Release 9.0/16.12

Release 9.0/16.12 of the Z-Series Troubleshooting and Maintenance Guide includes the following new
features:
• Upgrade, Backup, and Restore of Ciena Packet Networking (PN) Devices—You can perform
software upgrade, database backup, and database restore for supported Ciena PN devices
with SAOS 16.16.0.0170 and higher through Planet Operate. Refer to Defining an Upgrade
Task—Third-Party Nodes starting on page 111.


Release 9.0 of the Z-Series Troubleshooting and Maintenance Guide includes the following new
features:
• FLX-216i Optical Protection: Planet Operate now provides unidirectional, non-revertive 1+1
optical protection groups FLX-216i for optical ports in conjunction with the passive Transport
Protection Module (TPM). Refer to Service-Affected Line Cards starting on page 95.
• PSW Loop Detection and Interruption Service: PSW line cards, PBB-TE protocol, and Planet
Operate support Ethernet ring loop detection and interruption on network NNI main and
sub-rings. When the loop detection and interruption feature is enabled, Planet Operate
creates a loop detection service and the RPL owner node sends out loop detect packets
periodically in both directions around the ring. If the loop detect packet does not encounter a
blocked port it returns to the RPL indicating a loop. The RPL owner node automatically
performs a forced switch (FS) on the RPL to stop the loop on the current ring; and the system
displays a major alarm to indicate a loop recovery FS. Refer to Service-Affected Line Cards
starting on page 95.
• Ciena Packet Networking (PN) Device: Planet Operate supports the cut in (insertion) and
cut out (removal) of a PN device to and from an existing operational link on a multi-hop
linear network topology. Refer to Inserting and Removing a Ciena Packet Networking
Device in a Multi-Hop Linear Topology starting on page 160.

modules and features:
• LME-10G10d: A new version of the LME-10G10 module, called the LME-10G10d (part number
800-138-02), supports configuration of the OSPF in-band management via the general
communications channel (GCC). All references to the LME-10G10 module in this guide also
refer to the LME10G10d; functionality is identical for these two modules, the only difference
is the LME-10G10d supports GCC. Refer to Service-Affected Line Cards starting on page 95.
• PSW-10G20: The Z-Series PSW-10G20 module is an Ethernet switching and transport module
for the Z-Series packet-optical transport platform (P-OTP). The module is a high-capacity
20-port 10GbE switch module for Ethernet aggregation and end-to-end packet transport
solutions. The PSW-10G20 module supports twenty 10GbE/OTU2/OTU2e/OTU1e ports.
Twelve ports are capable of OTU configuration, the remaining eight ports are capable of
running at 1/10 GbE. The PSW-10G20 module supports 200G fully non-blocking packet
switching for all frame sizes. Refer to Service-Affected Line Cards starting on page 95.
• PSW E-Tree—PSW modules support E-Tree, an MEF network feature. E-Tree service is similar
to E-LAN service; however, in an E-Tree network each customer UNI (port or VLAN) is
designated as either root or leaf. A root UNI can communicate with any leaf UNI. However, a
leaf UNI can only communicate (forward packets) to a root UNI, preventing any leaf-to-leaf
traffic flow. E-Tree service is mainly used for business Ethernet applications such as
multi-cast delivery services and backhaul services. Refer to Service-Affected Line Cards


• LAD-96E: The LAD-96E module is the latest addition to the family of Z-Series Lambda
Add/Drop (LAD) modules. The LAD-96E module, with pre-amp and booster amplifier,
combines with an associated AWG-96 Array Wave Guide module to support add/drop traffic.
Individual wavelengths are added and/or dropped using the passive AWG-96 2 RU module.
The AWG-96 provides the ability to multiplex and de-multiplex any of the 96 channels
supported by the LAD-96E module with 50GHz channel spacing. You can install the module in
Z33 and Z77 shelves. The LAD-96E module has a reach of 28 dB (112 Km nominal) with 10G
XFPs and 100G coherent optics (DTM-100G, DTM-100G2, and Coherent CFP). .
• DTM-100G2: The Z-Series DTM-100G2 is a dual-port 100 Gbps single-slot transponder
module providing DWDM interfaces for the Z22 (–48V), Z33, and Z77 100 Gbps transponder
solutions. The DTM-100G2 is fully compatible with existing Z-Series DWDM components
including LAD modules and WSS ROADM modules. This allows the mixing of 10G and 100G
waves over the same fiber. The DTM-100G2 module receives a C Form-Factor Pluggable
(CFP)-based 100 GbE and generates a 100 Gbps ITU grid wave. On the client side, the
DTM-100G2 module accepts either 100GE or OTU4 (GFEC). On the line side, the OTU4 is
encoded with either standard G.709 GFEC or a higher gain HG-FEC. CyOS 7.0 working in
conjunction with Planet Operate 15.02 provides non-revertive 1+1 optical protection groups
for DTM-100G2 optical ports. Optical protection groups, created in association with the
passive Transport Protection Module (TPM), provide reliable protection for facility and
hardware failures.
• OLA-010: The OLA-010 module utilizes Raman technology and functions as a uni-directional
amplifier to provide all-band wavelength coverage for up to 96 optical channels. The OLA-010
replaces existing external Raman chassis. You can install the module in Z22, Z33, and
Z77 shelves. Coupled with the Z-Series ROADM and DWDM modules the OLA-010 module
extends the reach of an optical span by 13.5dB and supports regional/long-haul network
applications.
• DTM-100G2 and LME-10G10 Optical Protection: Planet Operate now provides non-revertive
1+1 optical protection groups for DTM-100G2 and LME-10G10 optical ports in conjunction
with the passive Transport Protection Module (TPM).
• MAC Swap Loopback--This release supports diagnostic MAC swap loopback testing for
PSW-based UNI flow points. This feature enables you to perform benchmark tests (RFC-2544)
and service creation tests (Y.1564). When a UNI flow point is enabled with this option, the
test streams are looped back to the traffic source. The received traffic has the source MAC
address and the destination MAC address in a frame swapped. Hence, when the incoming
data is looped back, the ingressing MAC source address and MAC destination address are
reversed to become the egressing MAC destination address and MAC source address. The
system supports the MAC swap loopback feature in PBB-TE transport configurations. You can
execute a MAC swap loopback test on PSW-based UNI flow points, client ERP UNI flow points,
and LAG UNI flow points. Refer to MAC Swap Loopback starting on page 24.
• Accedian Loopback Configuration: You can use Planet Operate to configure and activate
loopback instances on supported Accedian devices. Refer to Configuring Accedian
Loopbacks.


• WSS-F8 and OFX-8: WSS-F8 module provides 96-channel, wavelength-selectable switching
and reconfigurable optical add/drop multiplexing (ROADM) capabilities with automated
provisioning, power balancing, and monitoring for the Z-Series packet-optical transport
platforms (P-OTPs). To simplify fiber connectivity, an OFX-8 optical mesh interconnects up to
eight WSS-F8 modules. The passive OFX-8 module has an LGX form factor. The WSS-F8
module also supports 8-degree configurations with 40 channels when paired with the
AWG-40 module.
• OLA-200: The Metro/short span OLA-200 module provides amplification for the WSS-F2,
WSS-F4, and WSS-F8 modules operating in either 40-channel or 96-channel mode.
• OLA-201: The long-haul OLA-201 module provides amplification for the WSS-F2, WSS-F4, and
WSS-F8 modules operating in either 40-channel or 96-channel mode. The module
additionally offers an integrated Optical Channel Monitor (OCM) for automatic spectral tilt
adjustment, removing the previous four-hop restriction due to tilt, and extending the
node-to-node span capacity by more than 60% before regeneration compared to the L-AMP
shelf.
• LAD-96: The non-amplified 96-channel terminal multiplexer works in conjunction with the
passive AWG-96 module for add/drop traffic. The LAD-96 module provides point-to-point
data center connectivity as a primary application.
• PM pre-soft FEC error reporting support for DTM-100G line cards and Acacia CFP modules.
The feature provides real time and historical bins. Refer to Performance Monitoring
• PSW and TSW hitless upgrades: CyOS Release 6.0 supports hitless upgrades for
PSW-10G10, PSW-618, and TSW-10G10 line cards. Support for non-service affecting upgrades
start with software updates from CyOS 6.0 and higher to a higher release. Refer to
Service-Affected Line Cards starting on page 95.
For descriptions of new features provided in CyOS Release 6.0, refer to the "New Release 6.0
Features" section in the Z-Series CyOS Release Notes 6.0 and the Z-Series Engineering and Planning Guide
available in the portal library.

This release of the Z-Series Troubleshooting and Maintenance Guide describes the following new
features.
• High CPU and Low Memory Thresholds—CyOS R5.4 provides a system equipment profile
and user-defined equipment profiles to apply High CPU and Low Memory thresholds for
each line card and shelf controller card(s) in the Z-Series node. The system automatically
applies the equipment system profile to each line card and shelf controller card installed in
the node. You can also create user-defined equipment profiles and apply a custom profile to
individual line cards or to a shelf controller card installed or preprovisioned in the Z-Series
node. Refer to the Planet Operate User Guide for details.

• Port Mirroring—CyOS R5.4 and Planet Operate R14.05 support port mirroring on PSW line
cards. Port mirroring replicates traffic from a source port and forwards the replicated traffic
to a destination port for monitoring and troubleshooting without impact to the original traffic
flow. Refer to Port Mirroring starting on page 205.
For descriptions of additional new features provided in CyOS Release 5.4, refer to the "New Release
5.4 Features" section in the Z-Series CyOS Release Notes 5.4 available in the portal library. Release 5.4
does not introduce new Z-Series equipment. Additionally, refer to "New Features in Planet Operate
R14.05" in the Planet Operate Release Notes 14.05 available in the portal library.

features.
• The LME-10G10 is a highly scalable, multiservice 100G OTN muxponding module optimized
for network transport applications. The LME-10G10 can be paired with the Z-Series DTM
100G coherent transponder module to deliver a complete end-to-end packet and OTN
transport solution. Supported across all Z-Series platforms, the LME-10G10 provides the
following interfaces.
 10 SFP+-based multi-service client ports (up to 11.1 Gbps)
 Single CFP-based network optical port (up to 112 Gbps optics)
• The WSS-F2 and WSS-F4 modules are a single-slot, 96-channel (50 GHz spacing) 2-degree and
4-degree respectively, reconfigurable optical add/drop multiplexing (ROADM) that
interoperate with the AWG-96. The modules provide wavelength-selectable switching and
ROADM capabilities with automated provisioning, power balancing, and monitoring for the
Z-Series packet-optical transport platforms. Note that the WSS-F2 and WSS-F4 modules work
with an existing 40-channel (100 GHz spacing) configuration within the same network and
same node as the WSS-402. It is compatible with the AWG-40, L-AMP, 40-channel DCMs, and
existing fixed and tunable XFP, SFP+, and SFP transceivers. Note that the L-AMP is not
compatible in a WSS 96-channel configuration.
• The PSW-100G module is an Ethernet switching and transport module optimized for
high-capacity Ethernet aggregation and end-to-end packet transport solutions. Supported
across all Z-Series platforms, the PSW-100G provides one 100G port. PSW-100G supports an
OTU4 rate of up to 112 Gbps.
• For PSW line cards configured for PBB-TE traffic, Planet Operate provides PM counters and
TCAs for PSW line cards for the number of MAC addresses learned on an Ethernet sub-flow
domain. A sub-flow domain, sometimes referred to as a "fragment," represents all flow
points associated with the flow domain on a single PSW line card and can consist of one or
multiple flow points. To collect MAC Limit PM counts and receive TCA notifications, you must
first enable MAC limiting at the node level. For instructions, see Enabling MAC Limiting

New in the Previous Release 5.0/13.08

feature.
• Z-Series Node Insertion and Removal—You can cut in and cut out a Z-Series node to/from an
existing operational optical link while maintaining continuity for existing TESIs and ODU2
trails. Refer to Z-Series Node Insertion starting on page 143 and to Z-Series Node Removal
New in the Previous Release 5.0/13.06

The previous release of the Z-Series Troubleshooting and Maintenance Guide documented CyOS
Release 5.0 and Planet Operate Release 13.06.
This document describes the following features from the previous Release:
• Northbound SNMP Alarm Notification—You can configure Planet Operate to forward alarm
messages to up to 10 external, user-configurable destinations for consolidated alarm
monitoring and reporting. Refer to Configuring Northbound SNMP Alarm Forwarding
• Cut in/cut out—Planet Operate supports node cut in to and cut out from an existing,
operational G.8032v2 ring. Refer to Accedian Node Cut In/Cut Out on G.8032v2 ERP Group
• Upgrade, Backup, and Restore of Accedian Devices—You can perform software upgrade,
database backup, and database restore for supported Accedian devices through Planet
Operate. Refer to Backup, Restore, and Software Upgrades starting on page 81.
Supported Web Browsers

The following web browsers have been verified for viewing Z-Series, Planet Operate, and Blue Planet
HTML-based technical documentation downloaded from the portal library:
• Mozilla Firefox
• Microsoft Internet Explorer v8 and v9
Additional web browsers may be supported in the future.
Note: When viewing an HTML-based user guide extracted from a zip file downloaded from the portal
library, you must use either Mozilla Firefox or Internet Explorer (v8 or v9). Google Chrome cannot
open the index.htm file from a local hard drive.
Related Documentation
The documentation suite related to Blue Planet, Planet Operate, optical and packet transport, and
the Z22, Z33, Z77, L-AMP shelves, and managing third-party equipment consists of:
• Z-Series Engineering and Planning Guide
• Z77 Installation and Safety Guide

• L-AMP Installation and Safety Guide

• Planet Operate User Guides
 Getting Started
 Nodes, Modules, and Transport Resources
 Trails and Services
 Intra-Node Cross-Connects
 SONET/SDH and Optical Protection Groups
• Blue Planet Administration Guide
• Packet Switching User Guide
• Z-Series Troubleshooting and Maintenance Guide
• Z-Series Data Communications Network Planning and Configuration Reference Guide
• Optical Protection Switch User Guide
• Planet View Network Administrator Guide
• Planet View Guest Administrator Guide
• Planet View Network and Guest User Guide
• Planet Inventory User Guide
• TL-1 Reference Command Guide
• CLI Reference Command Guide

General Troubleshooting
This section describes general troubleshooting for Z-Series systems, including Trail Trace Identifier
(TTI) and loopback tests.
• TTI: Use the Trail Trace Identifier to monitor optical connections by attaching an identifying
string from a transmitting port.
• Loopback: Use the loopback feature to evaluate Z-Series connections. Loopbacks provide
circuit path tests through the network and help you to isolate a fault.
In This Chapter
Loopback Tests for Transport ................................................................. 21
MAC Swap Loopback ................................................................................ 24
Configuring Accedian Loopbacks ............................................................ 28
Trail Trace Identifier .................................................................................. 31
Keepalive Messages and Comm Fail ...................................................... 33
CFP and DTM-100G OTM Port Diagnostics ............................................ 33
Loopback Tests for Transport

Use a loopback test to evaluate Z-Series connections. The following Z-Series line cards support
loopback tests:
• DTM-8 • SFT-8 • MSE-1482 • PSW-10G20

• DTM-8G • PME-216i • LME-10G10 • PSW-618
• DTM-100G • PME-412 • PSW-100G • TSW-10G10
• DTM-100G2 • 2.5G-LME4 • PSW-100G2W
• SFT-10G16 • FLX-216i • PSW-10G10

You can configure most Z-Series equipment for three types of loopbacks:
• Terminal — A test signal is looped back towards the equipment.
• Non-Transparent Facility — A test signal is looped back towards the facility.
• Transparent Facility — A test signal is looped back towards the facility and allowed to pass
through to the near-end equipment.
For the PME, PSW, TSW, LME-10G10, DTM-100G, and DTM-100G2 line cards, configurable loopback
types depend on the configured Signal Type:
• Signal Type: OTU
 Transparent Facility
 Non-Transparent Facility
 Terminal
Note: For the PSW-100G2W, when a Terminal loopback is applied to the near-end node,
the system raises an alarm (Remote Resource Locked Indication) on the far-end node.
The alarm severity is Major.
• Signal Type: LAN/WAN
 Facility (non-transparent)
 Terminal
For the DTM-8/8G, SFT, and MSE line cards, there are two configurable loopback types:
• Facility (non-transparent)
• Terminal

The following diagrams show examples of the supported loopback types.
Example 1: Terminal Loopback

Test signal is looped back towards the equipment.
Z-Series Z-Series
Connection Client Line Line Client Connection
Line Line
to client Card Card to client
Z-Series shelf Z-Series shelf
Example 2: Non-Transparent Facility Loopback

Test signal is looped back towards the facilit y.
Line
Z-Series Z-Series
Connection Client Line Client Connection
Line Line
Example 3: Transparent Facility Loopback

Test signal is looped back towards the facility and allowed to pass through to the near-end equipment.
Line
Z-Series Z-Series
Connection Client Line Client Connection
Line Line
Figure 1: Loopback Testing
To create a loopback, the port must be in the Locked for Maint (maintenance) administrative state
and the Loopback Control parameter enabled.
Caution! — Facility or terminal loopback tests can be service affecting.
Note: Software loopbacks within the Z-Series platform are not flagged as
alarms. An operator must put the port into the Locked for Maint
administrative state to apply a loopback.
The Loopback control is the same for all applicable optical ports.
To provision a loopback test, follow this procedure.
Step Procedure
1 In the Network Tree or Network view tab, double-click the intended Z-Series node to open the Front
Panel tab.
2 From the main menu, select Node > Transport Resources to open the Transport Resources tab.
3 In the Physical Resources sub-tab, select an applicable fiber port. Click the General sub-tab.

Step Procedure
4 From the Admin. State list, select Locked for Maint. Click Apply.
5 From the Loopback Control list, select the loopback type. Click Apply.
MAC Swap Loopback

The system supports diagnostic MAC swap loopback testing for PSW-based UNI flow points. This
feature enables you to perform benchmark tests (RFC-2544) and service creation tests (Y.1564).
When a UNI flow point is enabled with this option, the test streams are looped back to the traffic
source. The received traffic has the source MAC address and the destination MAC address in a frame
swapped. Hence, when the incoming data is looped back, the ingressing MAC source address and
MAC destination address are reversed to become the egressing MAC destination address and MAC
source address.
The system supports the MAC swap loopback feature in PBB-TE transport configurations. You can
execute a MAC swap loopback test on PSW-based UNI flow points, client ERP UNI flow points, and
LAG UNI flow points.

You can configure PSW line cards for MAC swap loopback in Terminal mode. For a Terminal
loopback, a test signal is looped back towards the equipment upon egressing the target UNI flow
point.
The following diagram provides an example of a MAC swap terminal loopback.
Packet
Test Set
ETH Dst MAC Address

bb:bb:bb:bb:bb:bb
Rx
ETH Src MAC Address
aa:aa:aa:aa:aa:aa
Ciena
Network
ETH Dst MAC Address

aa:aa:aa:aa:aa:aa
Tx
ETH Src MAC Address
bb:bb:bb:bb:bb:bb
PSW UNI
Terminal
Loopback
Customer CPE
Figure 2: MAC Swap Loopback Example
MAC Swap Loopback Rules and Guidelines

• You can execute a MAC swap loopback test on PSW-based UNI flow points, client ERP flow
points, and LAG flow points.
• For a client ERP flow point, if the client ERP has more than one configured port, you must
block one of those ports in order to avoid traffic in that direction flowing to the looped back
port.
• When the UNI flow point being looped back is in an E-LAN/E-VLAN service, make sure the
looped back flow point is unblocked. For all other flow points within the flow domain, set the
Admin State for these flow points to Locked to Disable during the MAC swap loopback test.

Run the MAC Swap Loopback Test
Caution! — A Terminal loopback test can be service affecting.
To run a MAC swap loopback test for a PSW-based UNI flow point, follow this procedure.
Step Procedure
1 From the Network view tab, double-click the intended Z-Series node to open the node EMS panels.
2 From the main menu, select Node > Ethernet Packet Switching tab > Flow Domains sub-tab.
3 Click to select the intended UNI flow point.

Step Procedure
4 In the General sub-tab, do the following:
Important! — When the UNI flow point being looped back is in an E-LAN/E-VLAN service, make sure
the looped back flow point is unblocked. For all other flow points within the flow domain, set the
Admin State for these flow points to Locked to Disable during the MAC swap loopback test. At the
completion of the loopback test, set the Admin State of these flow points to Unlocked.
A. In the Admin. State list, select Locked for Maint.
B. Click Apply Changes.
C. In the MAC Swap Loopback list, select Terminal LB.
D. Click Apply Changes.
5 After the loopback test has completed, place the UNI flow point(s) back into service as follows:
A. In the Admin. State list, select Unlocked.
B. Click Apply Changes.

Configuring Accedian Loopbacks

Using Planet Operate, you can establish and activate traffic loopbacks on the following Accedian
device types:
• MetroNID GT
• MetroNID GT-S
• MetroNODE LT-S
You can establish local loopbacks (loopback applied by the Accedian device) toward the client
network or toward the provider network. You can designate the traffic to be looped based on the
following Layer 2 filters:
• VLAN: Outer VLAN ID, Untagged, Priority-tagged
• VLAN/Ethertype: Outer VLAN ID, Outer Ethertype
• PBIT: Outer VLAN Priority (0 through 7)
• DSCP: Setting (0 through 63)
• DHCP: Source and Destination Ports, IPv4 Protocol Type
• ARP: Outer VLAN Ethertype
• Broadcast (BC): Layer 2 MAC destination address/mask
• Multicast (MC): Layer 2 MAC destination address/mask
You can initiate loopback configuration either from the service or from the node. In either case,
Planet Operate discovers any loopbacks already configured on the Accedian device and displays
them in the Instance Name list. You can select an instance already configured or configure a new
instance.
From the Configure Loopbacks window, you can establish the loopback instance on the Accedian
device. You can then activate the loopback or simply save the configuration for activation at another
time.
Consider the following when planning and implementing Accedian loopbacks:
• Accedian nodes support one OAM instance per port.
• Accedian nodes support only one active loopback per device at one time.
• The loopback instance name must be unique on the node.
Important! — Activating loopbacks affects traffic.

To configure a loopback on a supported Accedian device, follow this procedure.
Step Procedure
1 Do one of the following:
• In the Nodes tab, right-click the intended Accedian node row and select Configure
Loopback....
—or—
• In the Network Services tab, right-click the intended service and select Configure Loopback....
—or—
• In the Network view tab, right-click the intended Accedian node or service and select Configure
Loopback....
2
In the Configure Loopback dialog box, identify the loopback instance by doing the following in the
Service Details area:
A. From the Service ID/Circuit ID list, select the service (if required; field pre-populated if you open
the dialog box from the service).
B. From the Node list, select the node (if required; field pre-populated if you open the dialog box
from the node).
C. From the Port list, select the port (if required; field pre-populated if you open the dialog box from
the service).
D. In the Instance Name field, select or enter the name of the loopback instance.
You can select from a list of configured loopback instances (if present), or you can enter a name
for a new instance. Each instance name must be unique on the node.

Step Procedure
3 In the Loopback Parameters area of the dialog box, identify the traffic to be looped by doing
the following:
A. From the Filter Profile list, select the intended filter type.
Depending on the filter you select, Planet Operate displays the appropriate associated fields; for
example: Outer VLAN ID, Outer VLAN Ethernet, Outer VLAN Priority, L2 MAC destination/mask,
and so forth.
B. Enter the appropriate values in the associated fields.
C. (Optional) Select the Swap MAC check box. When selected, Planet Operate swaps the incoming
source and destination MAC addresses on the looped packets.
D. (Optional) Select the Drop Opposite Traffic check box. When selected, the Accedian device drops
traffic from the originating port (client or network, depending on your configuration) when looping
back to the facing port.
Note: Enabling the Drop Opposite Traffic option interrupts the Ethernet service in one direction.
E. (Optional) In the Timeout field, accept the default loopback duration of 10 minutes or enter a
different duration in minutes. Valid values are from 1 through 60 minutes.
After loopback activation, the loopback remains in effect for the number of minutes you enter in this
field; then Planet Operate deactivates the loopback. Loopback configuration on the Accedian device
persists unless you remove it (refer to step 6).
• To configure the loopback instance on the Accedian node without actually activating the
loopback, click Apply.
—or—
• To configure the loopback instance on the device and activate the loopback, click Run.
While the loopback is in progress, click Refresh Status to display the time remaining until the
loopback times out (this button does not display until at least one loopback exists on the
selected port).
Important! — Depending on your configuration, activating a loopback may affect traffic.
5 To deactivate a loopback in progress, click Stop.

6 To delete a configured loopback instance from the Accedian device, identify the loopback using the
fields above and click Remove From Node (this button does not display until at least one loopback
exists on the selected port).
Note that loopback instances that you configure directly on the Accedian devices rather than through
Planet Operate do not display in Planet Operate until you rediscover the node.

Trail Trace Identifier

Use the Trail Trace Identifier (TTI) to monitor optical connections by attaching an identifying string
from a transmitting port. The trace identifier byte is a text string that identifies the OTU signal from
the source to the destination within the network. Trace messages are typically used to determine the
integrity of the connection between termination points during the connection setup process of
commissioning an OTN link. TTI messages help to determine if an active connection maintains
connectivity.
TTI Parameters
The TTI function allows you to provision transmitted and expected values and to retrieve an accepted
value. The receiving port string and sending string must match. If there is a mismatch, the system
notifies you of the error.
Note: The TTI is a single byte that is used to transport a 64-byte message and is part
of the OTU overhead. The message contains NE information with Source Access
Point Identifier (SAPI) and Destination Access Point Identifier (DAPI) trace strings to
identify the source and destination of an OTU signal.
• TTI Operation: Specify the TTI Operation as Insert or PassThru as appropriate. The default
is Insert. If set to Insert, the system will insert the access point identifier string towards the
physical interface. If set to PassThru, the system forwards the received system message
received untouched.
• TIM Control: Detection of trace identifier mismatch results in a TIM indication. In conjunction
with a TIM indication and TTI enabled, use the TIM Control parameter as follows:
 No Alarm: Do not raise an alarm upon TIM indication.
 Alarm Only: Raise an alarm upon TIM indication.
 Alarm Insert AIS or FDI: Raise an alarm and automatically insert an Alarm Indication
Signal (AIS) and Forward Detect Indication (FDI) upon TIM indication. An alarm indication
signal is sent downstream as an indication that an upstream defect has been detected. A
forward defect indication signal is sent downstream as an indication that an upstream
defect has been detected.
• TIM Evaluation: The TTI sub-tab allows you to set the Trail trace Identifier Mismatch (TIM)
trace mode to SAPI, or DAPI, or Both SAPI and DAPI modes. It also gives you the option to
disable automatic actions due to trace identifier mismatch. TIM is raised when the received
SAPI and/or DAPI values found in the TTI do not match the expected, pre-provisioned values.
For additional information on Trail Trace Identifier and access point identifiers, see ITU-T G.709,
Interfaces for the Optical Transport Network (OTN), Section 15.2.

Provisioning TTI
To view and provision connections at the OTU2 Section level using the TTI sub-tab, follow this
procedure.
Step Procedure
1 In the Network Tree, select the intended Z-Series or L-AMP shelf.
3 From the Physical Resources sub-tab, double-click the appropriate module to expand the view.
Continue to expand the view to the OTS, OTU-2, or ODU-2 layer as in the following example.
4 Click the TTI sub-tab.

5 In the TTI sub-tab, do the following:
A. From the TTI Operation list, select Insert or PassThru as appropriate.
When set to Insert, the system inserts the access point identifier string towards the physical
interface. When set to PassThru, the system message received is forwarded untouched. The
default for configurable layers is PassThru. Note the following:
• The TTI Operation parameter is configurable for 2.5G-LME4, DTM-8, DTM-8G, DTM-100G
(OTU-4 Section for both OTM and CFP ports, when configured with an OTU-4 signal type),
FLX-216i (OTU-2 Section), MSE-1482, and PSW-100G (OTU-4 Section) modules.
• The TTI Operation parameter is a read-only field set to "Insert" for the DTM-100G (ODU-4 for
both ports), DTM-100G2, LAC-8, LAD, FLX-216i (ODU-2), PSW-100G2W (OTU-4), PME, and WSS
modules.
• The TTI Operation parameter is a read-only field set to "PassThru" for the PSW-100G CFP port
ODU-4 layer and the PSW-100G2W (ODU-4 layer).
B. From the TIM Control list, select the Trace Identifier Mismatch control mode. The default is No
Alarm.
C. From the TIM Evaluation list, select the trace mode. The default is Both.
D. In the Inserted box, enter the access point identifier string to be transmitted.
E. In the Expected box, enter the expected access point identifier string to receive.
Note: The actual received string is displayed in the Accepted TTI box.
F. Click the Learn Expected button to perform the comparison of the received string with the
user-entered expected string. If there is a mismatch, TIM Control is enforced.
G. Click Apply.

Keepalive Messages and Comm Fail

Planet Operate uses a TCP keepalive signal to monitor the connections of Z-Series nodes. The server
sends one keepalive probe at the pre-defined interval of twenty seconds. If no replies are received
after five keepalive message probes, then the connection is considered down and the server raises a
communication failure alarm for that node. On occasion, there may be a minor reporting delay, but
Planet Operate typically reports communication failures at about the 100-seconds mark.
Additionally, Planet Operate uses keepalive probes for Accedian and RAD nodes to maintain CLI
sessions.
CFP and DTM-100G OTM Port Diagnostics

CFP Slot MSA Real-Time Diagnostics
Planet Operate provides the following CFP transceiver real-time statistics:
• Module state
• Module temperature (C)
• VCC voltage
• Tx bias current (A)
• Tunable XCVR Wavelength Setpoint (nano-meter) (LME-10G10 only)
• Tunable XCVR Wavelength Error (nano-meter) (LME-10G10 only)
To view the CFP transceiver MSA real-time statistics, follow this procedure.
Step Procedure
Panel tab.
3 In the Physical Resources sub-tab, right-click the intended module and select Expand Subtree to
expand the view. Click the CFP Transceiver.
4 Click the MSA Real-Time Diag. tab to view the diagnostics.

CFP and DTM-100G OTM Port Network Lane Real-Time Diagnostics

Planet Operate provides the following CFP transceiver and DTM-100G OTM port real-time statistics
for a network lane (fiber):
• Tx laser temperature (C)
• Tx bias current (A)
• Tx and Rx power (dBm)
• Tx and Rx frequency (THz)
• Chromatic dispersion (ps/nm)
• Differential group delay (ps)
• Second order polarization mode dispersion (ps/nm)
• State of polarization (radian/s)
• Polarization dependent loss (dB)
• Q (dB)
• Carrier frequency (MHz)
• Signal-to-noise ratio (dB)
Network Lane refers to the optical lanes resident inside the CFP module or DTM-100G OTM
port—similar to an optical channel wavelength. Each Network Lane relates to one internal Tx/Rx
wavelength. These internal wavelengths may or may not be muxed internally, depending on the CFP
type.
To view the CFP transceiver or DTM-100G OTM MSA real-time statistics, follow this procedure.
Step Procedure
Panel tab.
3 In the Physical Resources sub-tab, right-click the intended module and select Expand Subtree to
expand the view.
4 Under the CFP slot or DTM-100G OTM port, locate and click the Network Lane that you are viewing.
Click the MSA Real-Time Diag. tab to view the diagnostics.

Alarm and Event Management
This section describes Z-Series and L-AMP system alarm and event management.
Communication with all Z-Series and L-AMP shelves in the network is via the in-band Optical
Supervisory Channel (OSC) or out-of-band management networks. Z-Series shelves report all alarm
and event information to the Planet Operate where it is stored in a persistent database for reporting
and analysis.
Alarms propagate from the lowest port or protocol level upward to the top-level view, allowing
operators to view network status at a glance and drill down to isolate the fault. Z-Series shelves and
Planet Operate utilize an intelligent alarm suppression algorithm to present only the most relevant
alarms. For example, a fiber cut would cause potentially dozens of alarms, as the port, card, and
numerous services would be affected. Z-Series platforms correctly alarm the failed physical layer and
suppress other alarms, providing clear indication for technicians to remedy the problem. System
administrators have instant access to alarm tables, system logs, and configuration dialog boxes
without having to toggle between multiple widows or run multiple instances of the client.
Individual Z-Series line card alarm LEDs present a summary of all critical, major, and minor alarms
for the card. The active Z77 Broadband Operating System Supervisor (BOSS/BOSS2) card alarm LED
presents a summary of all critical, major, and minor alarms on a shelf and/or node. The Z22 and Z33
shelves provide a status panel on the Fan Module that includes LEDs for critical, major, and minor
alarms.
In This Chapter
Alarms Function ......................................................................................... 36
Alarms Tool Tab ......................................................................................... 50
Alarm Troubleshooting ............................................................................. 52

Alarms Function
The alarms function provides alarm logs, alarm filtering, setting assignments for alarm severities,
creating alarm profiles, external alarm notifications, and setting and clearing the alarm scope.
Note: The L-AMP shelf does not allow suppression of a battery input missing alarm.
For information about clearing a protection switch on an Ethernet Ring Protection (ERP) major ring or
sub-ring, refer to "Working with ERP Protection Switching" in the Packet Switching User Guide.
For information about clearing a protection switch on a protected DTM-100G/DTM-100G2 ODU4
circuit, refer to "Performing a DTM-100G/DTM-100G2 ODU4 Protection Switch" in the Planet Operate:
Trails and Services Guide.
Alarm Log
To filter alarms, follow this procedure.
Step Procedure
1 From the main menu, select Alarms > Alarm Log to open the Planet Operate Alarm Log Filter
dialog box.
Note: To filter the alarms, click the Filters button to open the Alarm to open the Alarm Filter dialog box.
In the Alarm Filter dialog box, do the following:
A. In the View Severity area, select or clear the alarm severity check boxes.
B. In the Time Interval area, click the Select buttons for the From and To time interval boxes. Choose
the date and time from the Select Date and Time dialog box for the From and To
intervals respectively.
C. In the View Acknowledged Alarms area, select the applicable acknowledgment type check box.
D. Click OK to open the Alarm Log dialog box.
2 The Alarm Log dialog box provides the following options:
• Click Filter to reapply the filter settings.
• Click Get Prev to retrieve and display the previous alarms based on the value entered in the box
to the right of the Get Prev button. The default is 100.
• Click Get Top to retrieve and display the most current alarms.
• Click Clear All to clear the alarm log history.
• Click Export to export the alarms to a XML, HTML, or CSV file.
• Click Update to update the alarm log history.
• Click Close to close the dialog box.

Alarm Severity Assignment Profiles

An Alarm Assignment Severity Profile (ASAP) details the severity assigned to alarm types associated
with a Z-Series node and/or its components. For a detailed list of Alarm Assignment Severity Profiles
that include probable cause, the probable cause qualifier, the service-affecting alarm level, and the
non-service affecting alarm level, see the ASAP list available for downloading in the portal library.
Although you have full control to edit ASAP settings, test any changes prior to deployment in your
production environment.
Configuring Severity Profiles
Note: If you modify a default Alarm Severity Assignment Profile, the profile
name displays in bold in the tree.
To set alarm severity assignment profiles, follow this procedure.
Step Procedure
1 In the Network view tab, double-click the primary Z-Series shelf to open the Front and Rear panel tabs
and the Equipment Tree panel.

Step Procedure
2 From the main menu, select Alarms > Alarm Severity Profiles to open the Alarm Severity
Assignments dialog box.
3 In the Alarm Severity Assignments dialog box, from the Select Object Type list, select the applicable
object type to display the default and any custom alarm severity profiles in the tree.

Step Procedure
4 The Alarm Severity Assignments dialog box provides the following options:
To create a new profile, do the following:
• Select a severity alarm profile from the tree.
• Click Create Profile to open the Create New Profile as Copy of Default Profile dialog box.
• In the text box, type the name of the new profile.
• Click OK to create the profile and return to the Alarm Severity Assignments dialog box.
Important! — Changing a default alarm severity profile for a selected entity will change the profile for
all identical entities in this shelf. A customized alarm severity profile for a selected entity will change
the profile only for that particular entity in this shelf.
To delete a profile, do the following:
• Select a severity alarm profile from the tree.
• Click Delete Profile.
• In the confirmation dialog box, click Yes to delete the profile and return to the Alarm Severity
To copy a profile, do the following:
• Select a custom severity alarm profile from the tree.
• Click Copy Profile.
• In the text box, type the name of the new profile.
• Click OK to copy the profile and return to the Alarm Severity Assignments dialog box.
Updating Severity Levels

Note: Only user-defined environmental alarms are provided to set environmental alarms.
The Alarm description can be applied in the Environmental Relay Configuration dialog box,
Relay Contacts tab (Node > Environmental Relays).
To update alarm severity profiles to their appropriate severity levels, follow this procedure.
Step Procedure
1 In the Network view tab, double-click the primary Z-Series shelf to open the Front and Rear panel tabs
and the Equipment Tree panel.

Step Procedure
2 From the main menu, select Alarms > Alarm Severity Profiles to open the Alarm Severity
3 Note: To set environmental alarms for a Z22, Z33, Z77, or L-AMP shelf, make the following initial
selections from the Select Object Type list:
• Z22 or Z33 shelf – Expand Shelf Types and select Z22 shelf or Z33 shelf
• Z77 shelf – Expand Equipment Types and select BOSS Termination Module
• L-AMP shelf – Expand Equipment Types and select L-AMP Environmental Ports
From the Select Object Type list, select the applicable object type to display the default and any custom
alarm severity profiles in the tree.

Step Procedure
In the Alarm Severity Assignments dialog box, do the following:

A. In the Default Alarm Severity panel, click the appropriate alarm severity profile.
B. From the Service Affecting list, select the appropriate alarm level.
C. From the Not Service Affecting list, select the appropriate alarm level.
D. From the Service Independent or Unknown list, select the appropriate level. This field helps the
system assign an alarm value if it cannot determine if the alarm is service-affecting or non-service
affecting.
E. Click Apply to save your changes.
Repeat this step for each affected alarm severity profile for this object type.
5 Repeat steps 3 and 4 for each applicable object type.
Set Alarm Scope to Active Node

To define the alarm scope for an active node, follow this procedure.
Step Procedure
1 From the Network Tree or the Network view tab, select the intended Z-Series node.
2 From the main menu, select Alarms > Set Alarm Scope to Active Entity. Active alarms for the
selected node display in the Alarms tab.

Clear Current Alarm Scope

To clear the current alarm scope from an entity, follow this procedure.
Step Procedure
1 From the Network Tree or the Network view tab, select the intended Z-Series node.
2 From the main menu, select Alarms > Clear Current Alarm Scope. Active alarms for the entire
network display in the Alarms tab.
Configuring Northbound SNMP Alarm Forwarding

You can configure Planet Operate to forward alarm messages to up to ten external,
user-configurable destinations for consolidated alarm monitoring and reporting.
An internal Planet Operate component, the Alarm Notification Server, receives each alarm from the
Planet Operate Alarm Server, then processes it and forwards it as an SNMP trap to the configured
external destinations. Each trap identifies the Planet Operate server, the network element in alarm,
the alarm state, severity, probable cause, description and so on.
Refer to the file CYAN-MS-MIB for OIDs and other details. You can download the MIB via the Planet
Operate client Help menu. To download the CYAN-MS-MIB file, select Help > About > Planet
Operate Client Software Download and Documentation Page > Docs > MIBs > Planet Operate
MIB.
Adding an Alarm Destination

To add an external alarm destination, follow this procedure.
Step Procedure
1 From the main menu, select Alarms > Alarm Forwarding Configuration to display the Alarms
Forwarding - Destination Configuration dialog box.

Step Procedure
2 In the Alarms Forwarding - Destination Configuration dialog box, click Add to display the Add
Destination dialog box.
3 In the Add Destination dialog box, do the following:

A. In the Address field, enter the IP address of the alarm destination device.
B. In the Port field, enter the port of the alarm destination device.
C. From the Protocol list, select the SNMP protocol version of the alarm destination device.
D. In the Trap Community field, enter the community name of the alarm destination device.
E. Click OK.
Note: Planet Operate validates that IP address and port conform to standard syntax, but does not
confirm that the IP address/port combination is reachable.
Modifying an Alarm Destination

To edit an existing external alarm destination, follow this procedure.
Step Procedure
2 In the Alarms Forwarding - Destination Configuration dialog box, select the destination row to modify;
click Edit to display the Edit Destination dialog box.
3 In the Edit Destination dialog box, modify the required settings and click OK.

Deleting an Alarm Destination

To delete an existing external alarm destination, follow this procedure.
Step Procedure
2 In the Alarms Forwarding - Destination Configuration dialog box, select the destination row to delete;
click Remove.
3 Click Yes to confirm deletion of the selected destination.
External Alarm Notifications

Use the external alarm notifications feature to send the system log files or alert messages to a
recipient’s email address. Planet Operate includes a built-in email notification function that notifies
network operators when alarms of any provisioned severity occur.
This section describes configuring external notifications using syslog, email, and TL1 transport
methods.
Preparing for Email Message SMTP Alarm Notification

If you are going to use an email message to send an SMTP notification, you need to:
• Add an SMTP server. For details on adding an SMTP server, see the Planet Operate: Nodes,
Modules, and Transport Resources Guide.
• Define the SMTP and email message addressing information.
• Specify the email message address for those to receive the notification when the alarm(s) are
raised.
Notification Profiles Tab

The Notifications Profiles tab allows you to create notification profiles and notification recipients.
Notification profile parameters are as follows:
• Emit Alarm Clears
Selecting (enabling) this option will send a notification when an alarm is cleared. The default
setting is disabled (cleared check box).
• Hold-Down Timer
The Hold-Down Timer indicates the number of milliseconds to wait for additional alarm
events before sending a notification. Use this option to bundle notifications.
• Max. Alarm Count
This indicates the maximum number of alarms to bundle before sending a notification. This
option overrides the Hold-Down Timer setting.

Note: The Hold-Down Timer and Max. Alarm Count parameters are only valid for
email transports.
To add, view, and modify alarm notification profiles and notification recipients, follow this procedure.
Step Procedure
1 From the main menu, select Alarms > External Alarm Notifications to open the External Alarms
Notifications dialog box. Click the Notification Profiles tab.

Step Procedure
2 Add a Notification Profile

In the Notification Profiles tab, click the Create Profile button.
In the Notification Profile tab, do the following:

A. Select (check) the Enabled check box.
B. In the Profile Name box, type a descriptive name for the notification profile.
C. In the Selected Severities area, select or clear the applicable severity level check boxes.
D. Select or clear the Emit Alarm Clears check box.
E. From the Hold-Down Timer list, select the timer value.
F. From the Maximum Alarm Count list, select the maximum number of alarms to bundle before
transporting the alert to recipient(s).
G. To include only selected nodes, clear the Include All NEs check box, click the Select button and
choose node(s) from the NEs to Include dialog box. Click OK to return to the Create Notification
Profile dialog box.
H. In the Instructions text box, enter any special instruction for the notification.
I. Click OK.

Step Procedure
3 View or Modify a Notification Profile

The left-side panel of the Notification Profiles tab shows a list of alarm notifications and associated
recipients. Select (click) a notification profile to display profile settings in the right-side panel.
Note: For details on notification profile settings, see step 2.
Update the settings as needed and then click Apply.
4 Add a Recipient Profile
In the Notifications Profile tab, click Add Recipient and do the following:
A. Select (enable) or clear (disable) the Enable External Alarm Notifications for this Recipient
check box.
B. In the Recipient Name text box, enter a descriptive name for the recipient.
C. Click Apply to save the recipient profile.
5 View or Modify a Recipient Profile
In the profiles and recipients tree, select (click) a notification recipient to view or modify recipient profile
settings.
Note: For details on recipient profile settings, see step 2.
In the Recipient Profile area, update the settings as needed and then click Apply.
6 Add a Transport Method
In the Add Transport list in the Notifications Profile tab, determine the appropriate transport method:
• Select Email to open the Add Transport Definition (Email Transport) dialog box. Go to Email
Transport Method starting on page 48.
• Select Syslog to open the Add Transport Definition (Syslog Transport) dialog box. Go to Syslog
• Select TL1 to open the Add Transport Definition (TL1 Transport) dialog box. Go to TL1

Email Transport Method

To configure an email transport method, follow this procedure.
Step Procedure
1 From the Add Transport list in the Notifications Profile tab, select Email to open the Add Transport
Definition (Email Transport) dialog box.
2 Note: You must define at least one SMTP server before you can add an email transport.
In the Add Transport Definition (Email Transport) dialog box, do the following:
A. Select or clear the Enable This Transport Method check box. The default is selected (enabled).
B. In the Subject Line box, enter the subject line to use.
C. Select the Node Name in Subject check box to have the node name included in the email subject.
D. In the Send to Email box, enter the address to which to send the email (separate multiple email
addresses with a comma).
E. In the From Email box, enter the email address from which the email comes.
F. From the Use Mail Server list, select the SMTP server.
G. Click OK to save the information and return to the Notifications tab.
3 In the Notifications tab, click Close.
Syslog Transport Method

To configure a syslog transport method, follow this procedure.
Step Procedure
1 From the Add Transport list in the Notifications Profile tab, select Syslog to open the Add Transport
2 In the Add Transport Definition dialog box, do the following:
A. Select or clear the Enable This Transport Method check box. The default is selected (enabled).
B. In the Syslog Address box, enter the IP address (in dotted decimal format) of the computer running
the syslog application.
C. In the Syslog Port box, accept the default UDP port 514 or specify a port as required by your
system.
D. Click OK to save the information return to the Notifications tab.

TL1 Transport Method

Planet Operate provides an optional TL1 transport northbound interface that sends TL1 alarm data
to a designated TL1 host. This feature is typically used to send alarm information from the Planet
Operate server to Operational Support System (OSS).
To configure a TL1 transport method, follow this procedure.
Step Procedure
1 From the Add Transport list in the Notifications Profile tab, select Syslog to open the Add Transport
2 In the Add Transport Definition dialog box, do the following:
A. Verify that the Enable This Transport Method check box is selected (default).
B. In the TL host address box, enter the IP address of the TL1 host (in dotted decimal format).
C. Click OK to save the information and return to the Notifications tab.
Global Settings Tab

To configure global settings for external alarm notifications, follow this procedure.
Step Procedure
1 From the main menu, select Alarms > External Alarm Notifications to open the External Alarms
Notifications dialog box. Click the Global Settings tab.
2 In the Global Settings tab, do the following:
A. Select or clear the Enable External Alarm Notifications check box.
B. In the Site Description text box, type a descriptive name for the site.
C. In the TL1 Listen Port, enter the port number. Accept the TL1 standard listening port 3081 (default)
or enter a different TL1 listening port.
D. Click Apply to save the configuration.
E. Click Close.

Alarms Tool Tab

The Alarms tool tab shows data pertaining to the entire network. Use the alarms tab to create, view,
modify, and delete alarm annotations.
From the main menu, select Tools > Alarms to display the Alarms tool tab.
Figure 3: Alarms Tool Tab
Create an Annotation
To create an annotation to an alarm, follow this procedure.
Step Procedure
1 Click the Alarms tool tab.
2 Click the alarm row to select the intended alarm. Right-click and select Create Annotation to open the
Create Annotation dialog box.
3 In the Create Annotation dialog box, enter an annotation message and click OK.
View an Annotation
To view an alarm annotation, follow this procedure.
Step Procedure
2 Click the alarm row to select the intended alarm. Right-click and select View Annotations from the
shortcut menu to open the Alarm Annotations dialog box.

Edit an Annotation
To edit an alarm annotation, follow this procedure.
Step Procedure
shortcut menu to open the Alarm Annotations dialog box.
In the Alarm Annotations dialog box, select the alarm annotation and click Modify to open the Create
Annotation dialog box.
3 In the Create Annotation dialog box, modify the message and click OK.
Delete an Annotation
To delete an individual alarm annotation, follow this procedure.
Step Procedure
shortcut menu to open the Alarm Annotation dialog box.
3 In the Alarm Annotations dialog box, select the intended alarm annotation and click Delete.
4 In the confirmation dialog box, click Yes.
Clear All Annotations

In addition to deleting individual alarm annotations, Planet Operate allows you to clear all
annotations from the system with a single command.
To delete ALL alarm annotations, follow this procedure.
Step Procedure
2
Click the Settings icon and then select Clear All Annotations to remove all alarm
annotations from the system.
Important! — This action clears all annotations for all alarm entries, which includes active
alarms and alarms in the alarm history file.

Acknowledge an Alarm
Planet Operate allows the operator to acknowledge an alarm and place it in an acknowledged state.
This state indicates that the operator is aware of the alarm, but it has not been resolved.
To acknowledge an alarm, follow this procedure.
Step Procedure
2 Right-click the alarm row of the intended alarm and select Acknowledge Alarm from the shortcut
menu.
Alarm Source
To display the source of an alarm, follow this procedure.
Step Procedure
2 Right-click the alarm row of the intended alarm and select Go to Alarm source to display the applicable
screen (for example, Transport Resources tab, Front or Rear Panel, or so forth) in the Planet Operate
main work area.
Alarm Troubleshooting
For a list of Z-Series alarm descriptions and severities, see the Alarm List starting on page 208 in
this guide.
Note: Beginning with Planet Operate release 15.02, the Blue Planet app, "Trap
Forwarding Application," is required for SNMP trap forwarding and alarm notification
management of Z-Series and third-party network elements. If you are using Planet
Operate release 15.02 (or higher) and alarms do not properly display in the Planet
Operate Alarms panel, verify that your system administrator has installed the Trap
Forwarding Application app on the Blue Planet server that hosts Planet Operate.
For more information, refer to the Planet Operate Release Notes.

Performance Management
Planet Operate integrates full performance management capabilities and provides performance
monitoring for each type of multiservice traffic supported. Binned statistics are logged into a
database stored in each Z-Series line card. In addition, you can configure polling and be configured
for a wide range of parameters, allowing customized reporting on service-level information.
The system provides Performance Monitoring (PM) at each layer, independent of the other layers.
The system can detect a defect at a particular layer either by receiving the appropriate incoming
signal, or by receiving it from a lower layer. Defects and failures that occur at a lower layer affect the
PM parameters at higher layers. The intent of the physical layer is to enable proactive monitoring of
the physical devices and facilities that act as the transmitter, optical path and receiver of the optical
signal, so that an early indication of a problem is possible before a failure actually occurs.
Each monitored performance parameter has a corresponding threshold for the current (15-min) and
daily (24-hour) time periods. If the value of a counter exceeds the threshold value for a particular
interval, the system raises a Threshold Crossing Alert (TCA). Thresholds are used to set error levels
for each PM. Planet Operate allows you to set Threshold Crossing Alerts using TCA profiles.
In This Chapter
Performance Monitoring .......................................................................... 54
Monitor Counters – PM Counters ............................................................ 56
Threshold Crossing Alerts (TCA) .............................................................. 61
Holding Time .............................................................................................. 64
Plotting Data ............................................................................................... 65
TCAs Sub-tab .............................................................................................. 66
Collect Counters ......................................................................................... 67
Enabling MAC Limiting .............................................................................. 68

Performance Monitoring
Use performance-monitoring parameters to gather, store, threshold, and report performance data
for early detection of problems.
Depending on the object selected, performance monitoring allows you to view:
• Forward Error Correction (FEC) • 1-min bins

• Code Violations (CV) or Background Block Error (BBE) • 15-min bins
• Error Seconds (ES) • 24-hour bins
• Severely Errored Seconds (SES) • Bandwidth utilization
• Unavailable Seconds (UAS) • Ethernet transmit and receive bit rates
• Severely Errored Frame Seconds (SEFS) • Plotted data
• Failure counts • Transmit and receive utilization
• Near-end data • Transmit and receive packets
• Forward Near-end data (A-end to Z-end) • Transmit and receive bytes
• Reverse Near-end data (Z-end to A-end) • Detected span loss
• Far-end data • Post-amp receive power
• Tidemark data – Tx and Rx optical power levels* • MAC address counts from MAC
(maximum, average, and minimum) learning tables for each Ethernet sub-flow
domain (see PM Notes below for an
• Protection switch count and traffic on protection duration
explanation of sub-flow domains)
(MSE-1482 Line layer, SONET/SDH protection groups)
* Tidemark data in the Planet Operate PM Counters tab are a sampling of the maximum, average,
and minimum transmit and receive power levels. The system collects sampling data every second for
all intended ports. Planet Operate collects and time stamps Tidemarks.
Soft-Decision FEC PM
The DTM-100G and DTM-100G2 line cards, as well as Acacia CFP modules, report counts of
Soft-Decision (SD) FEC corrected bits and uncorrectable codewords at the OTU4 MSA Section level of
the OTM 100G port (for a DTM-100G card) or Fiber Port (for a CFM module). Soft-Decision FEC
provides significant error-correction performance. SD FEC can extend optical performance and
increase distances.
To view SD FEC PM, navigate to the PM Counters tab (see Monitor Counters – PM Counters starting
on page 56 for instructions). In the PM Counters tab, do one of the following:
• Expand the DTM-100G module, click the Near-end data level under OTM 100G Port > OTU-4
MSA Section (MSAOTU4<slot>).
• Expand the DTM-100G, DTM-100G2, LME-10G10, PSW-100G module, click the Near-end data
level under OTU-4 100GE/OTU4 Fiber Port > OTU-4 MSA Section (MSAOTU4<slot>).

For more information on Soft-Decision FEC, see the Transport Resources section in the Planet
Operate: Nodes, Modules, and Transport Resources Guide.
PM Definitions
Statistic Definition
EIR bytes/packets Bytes/packets exceeding CIR but not exceeding EIR (yellow).
Discarded bytes/packets Bytes/packets exceeding EIR (red) and dropped.
Tx utilization (%) Per flow point:

Rx utilization (%) • When a bandwidth profile is not applied to the flow point,
utilization is reported as zero.
• When a bandwidth profile is applied to the flow point, Planet
Operate calculates utilization using the configured CIR as the
maximum bandwidth capacity.
• If the sum of CIR traffic and EIR traffic is greater than the
configured CIR, the utilization reported is greater than 100%.
Note: A bandwidth profile assigned to the port or flow point pool has no
effect on the flow point PM.
Per port:
• Whether or not a bandwidth profile is applied to the port, Planet
Operate calculates utilization using the port capacity as the
maximum bandwidth capacity.
Note: A bandwidth profile assigned to the flow point has no effect on the
port PM.
PM Notes
Note: The system stores Performance Monitoring data locally on each Z-Series line
card. If the line card is restarted, historical PM is lost.
• Note: For PSW line cards configured for PBB-TE traffic, Planet Operate
provides PM counters and TCAs for PSW line cards for the number of MAC
addresses learned on an Ethernet sub-flow domain. A sub-flow domain,
sometimes referred to as a "fragment," represents all flow points
associated with the flow domain on a single PSW line card and can consist
of one or multiple flow points. To collect MAC Limit PM counts and receive
TCA notifications, you must first enable MAC limiting at the node level. For
instructions, see Enabling MAC Limiting starting on page 68.
• Note: Occasionally while adding and deleting cross-connects to the
Z-Series 2.5G-LME4 and DTM-8G modules, an inaccurate remote
Performance Monitoring (PM) count may occur for OTUk and ODUk. You
can safely ignore this inaccurate PM count.

Monitor Counters – PM Counters

To display performance-monitoring counters, follow this procedure.
Step Procedure
1 In the Network view tab, select (click) the intended Z-Series node.
2 From the main menu, select Node > Performance Monitoring to open the Performance
Counters tab.
3 If not already displayed, click the PM Counters sub-tab.
4 In the PM Counters sub-tab, select the port, protocol level, Ethernet object, and so forth to view
performance data. The default view is the Tree View sub-tab.
Important! — The PM Enabled check box must be enabled in the Configuration sub-tab to view PM
data in the Tree View or Grid View sub-tabs. For instructions, see step 6.
5 Click the Grid View sub-tab. From the Interval Type list, select the time interval.

Step Procedure
6 In the Shelf Resources tree, click the port level. In the PM Counters sub-tab, set the basic
configuration for PM and/or TCA (select or clear the PM Enabled and/or TCA Enabled check boxes).
Click the Select button to choose a configuration profile.
Note: If you select the PM Enabled check box (enabled) in the PM Counters tab for an Ethernet
object, on-demand statistics will be automatically enabled for that Ethernet object. If you clear the PM
Enabled check box (disabled), on-demand statistics will return to its original enabled or disabled
configuration state. For additional Ethernet statistics information, see "Ethernet Statistics" section in
the Packet Switching User Guide.
Note: When clearing counters (Clear Counters button), the clearing function does not clear child
groups of a cleared parent group.

The next figure shows the shelf resources, including all the shelf modules. You can select an
individual object to display its resources that have PM enabled.
Figure 4: Resources with PM Enabled for a Selected Object
Packet Switching Bandwidth Utilization

CyOS calculates and Planet Operate displays Rx and Tx bandwidth utilization (percentage) per port
for PME and PSW line cards. You can display bandwidth utilization percentages for Ethernet ports
and flow points.
CyOS calculates the utilization on the running 15-min performance counter. For example, at 12:07
PM, CyOS retrieves a snapshot of good octets for a packet line card port. Next, the system calculates
the total bandwidth used by the intended port; good octets passed between 12:00 PM and 12:07 PM.
It then divides that amount by [7 minutes x line rate (in bits/sec)]. More precisely: every five seconds,
CyOS retrieves "passed octets" from the line card, per port, and calculates as follows:
• Rx Utilization percentage = [received octets since the beginning of the current 15-min interval
x 8] / [number of seconds elapsed since the beginning of the current 15-min interval x line
rate (in bits/sec)]. The calculated amount is then multiplied by 100 to convert the decimal
notation to an integer percentage.

• Tx Utilization percentage = [transmitted octets since beginning of the current 15-min interval
* 8]) / [number of seconds elapsed since the beginning of the current 15-min interval x line
rate (in bits/sec)]. The calculated amount is then multiplied by 100 to convert the decimal
notation to an integer percentage.
Important! — To calculate bandwidth utilization for flow points, you must apply an
ingress bandwidth profile for the Rx flow point and an egress bandwidth profile for the
Tx flow point. Applying bandwidth profiles provides the maximum bandwidth for the
utilization calculation. For details on applying bandwidth profiles, see Bandwidth
Profiles in the Packet Switching User Guide.
Planet Operate polls CyOS every two seconds (by default) when its PM Counters tab is in scope.
Note: CyOS does not calculate and Planet Operate does not display bandwidth utilization percentage
in the PM Counters tab for TESIs and LAG groups.
Displaying Bandwidth Utilization Data
Figure 5: PM Counters - Rx and Tx Utilization Percentages

To display the Rx and TX bandwidth utilization data, follow this procedure.
Step Procedure
2 From the main menu, select Node > Performance Monitoring to open the Performance
Counters tab.
3 If not already displayed, click the PM Counters sub-tab.
4 In the PM Counters sub-tab, right-click the intended packet port and select Expand Subtree to expand
the view. The default view is the Tree View sub-tab.
Important! — You must enable (select) the PM Enabled check box in the Configuration sub-tab to view
PM data in the Tree View or Grid View sub-tabs. For instructions, see step 6 in the procedure at the
beginning of this topic.
5 Click the Near-end Data level to view the Rx Utilization (%) and Tx Utilization (%) information as shown
in the figure above.
Note: Click the Grid View sub-tab to view multiple 15-minute counters.
Threshold Crossing Alerts (TCA) Profiles for Bandwidth Utilization

Planet Operate provides several TCA profiles for monitoring Rx and Tx bandwidth utilization
(percentage) per port for specific line cards and flow points.
TCA profile examples used for bandwidth utilization include:
• 1GE - IN LOAD, 15 min • Eth Flow Point - IN LOAD, 15 min

• 1GE - IN LOAD, 24 hour • Eth Flow Point - IN LOAD, 24 hour
• 1GE - OUT LOAD, 15 min • Eth Flow Point - OUT LOAD, 15 min
• 1GE - OUT LOAD, 24 hour • Eth Flow Point - OUT LOAD, 24 hour
• 10GE - IN LOAD, 15 min • ESP/TESI - IN LOAD, 15 min
• 10GE - IN LOAD, 24 hour • ESP/TESI - IN LOAD, 24 hour
• 10GE - OUT LOAD, 15 min • ESP/TESI - OUT LOAD, 15 min
• 10GE - OUT LOAD, 24 hour • ESP/TESI - OUT LOAD, 24 hour
• 100GE - IN LOAD, 15 min
• 100GE - IN LOAD, 24 hour
• 100GE - OUT LOAD, 15 min
• 100GE - OUT LOAD, 24 hour
If the value of a bandwidth utilization counter exceeds the assigned threshold value for a designated
interval, the system raises a threshold-crossing alert.

For details on provisioning TCA profiles, refer to "Threshold Crossing Alerts (TCA)" section in the
Z-Series Troubleshooting and Maintenance Guide.
Figure 6: TCA Profiles for Bandwidth Utilization
Threshold Crossing Alerts (TCA)

Each monitored performance parameter has a corresponding threshold for the current (15-min) and
daily (24-hour) time periods. If the value of a counter exceeds the threshold value for a particular
interval, a threshold crossing alert (TCA) will be raised. Thresholds are used to set error levels for
each PM. Planet Operate allows you to quickly set Threshold Crossing Alerts (TCA) using TCA profiles.
Note: If you modify a default TCA profile, the profile name displays in bold in the
TCA Profiles tree.

Default TCA Profiles

To set a default TCA profile, follow this procedure.
Step Procedure
2 From the main menu, select Node > Performance Monitoring to open the Performance Counters tab.
3 Click the TCA Profiles sub-tab.
4 In the TCA Profiles sub-tab, do the following:
A. In the Default Profiles tree, select an object.
B. In the Description box, enter a TCA profile configuration description to change the default
description.
C. Click Apply.
Note: A modified profile displays in bold after a change to its TCA parameter and the label "Custom
Value" displays under the TCA value in the TCA parameter panel.
Important! — Changing a default TCA profile for a selected object will change the TCA for all identical
objects in this shelf.
Flow Domain MAC Limit TCA Thresholds

For PSW line cards configured for PBB-TE traffic, Planet Operate provides PM counters and TCAs for
PSW line cards for the number of MAC addresses learned on an Ethernet sub-flow domain. A
sub-flow domain, sometimes referred to as a "fragment," represents all flow points associated with
the flow domain on a single PSW line card and can consist of one or multiple flow points. To collect
MAC Limit PM counts and receive TCA notifications, you must first enable MAC limiting at the node
level. For instructions, see Enabling MAC Limiting starting on page 68.

The default MAC Limit TCA Profile threshold value is set to 1843, which represents 90% of the Default
MAC Limit Profile setting (2048).
Cloning a TCA Profile

To clone a TCA profile, follow this procedure.
Step Procedure
2 Click the TCA Profiles sub-tab.
3 In the TCA Profiles sub-tab, do the following:

A. In the TCA Profiles tree, select an object.
B. Click the Clone TCA Profile icon to open the Create Custom TCA Profile dialog box.
C. In the Create Custom TCA Profile dialog box, do the following:

• In the Description text box, accept the default description or enter a new description.
• Click OK to return to the TCA Profiles sub-tab.
D. Click Apply.
Important! — A customized TCA profile for a selected object will change the TCA only for that
particular object in this shelf.

Holding Time
Use the holding time function to set the amount of time that the system will retain PM counters.
Node-Wide Holding Time Counters

The following list shows the valid ranges and defaults for the four Holding Time counters:
• 1-Minute Counters: The range is 1 to 24 hours. The default is 1 hour.
• 15-Minute Counters: The range is 1 to 24 hours. The default is 8 hours.
• 1-Hour Counters: The range is 1 to 96 hours. The default is 24 hours.
• 24-Hour Counters: The range is 1 to 96 hours. The default is 48 hours.
Provisioning Node-Wide Holding Time Counters

To set the holding time for PM counters, follow this procedure.
Step Procedure
2 Click the Holding Time sub-tab.
3 In the Holding Time sub-tab, do the following:

A. In the Holding Time for 1 Minute Counters box, type the number of hours to hold the 1-min bin
PM counters.
B. In the Holding Time for 15 Minute Counters box, type the number of hours to hold the 15-min bin
PM counters.
C. In the Holding Time for 1 Hour Counters box, type the number of hours to hold the 1-hour bin
PM counters.
D. In the Holding Time for 24 Hour Counters box, type the number of hours to hold the 24-hour bin
PM counters.
E. Click Apply.

Plotting Data
Planet Operate provides real-time enhanced Ethernet statistics and PM data with bandwidth
utilization data graphs to assist in troubleshooting and network monitoring.
To plot data, follow this procedure.
Step Procedure
2 Click the PM Counters sub-tab.
3
In the PM Counters sub-tab, do the following:

A. In the Shelf Resources tree, double-click the PME-412, PME-216i, PSW-10G10, PSW-618, TSW-10G10,
PSW-100G, LME-10G10, or MSE-1482 module and subsequent levels until the Ethernet
Termination interface is displayed in the tree (100G Ethernet Termination interface for the
PSW-100G). Double-click the 10G Ethernet Termination interface to display the Near-End Data
level. Click the Near-End Data level.
Note: For the PME and PSW modules, you can also display the Near-End Data for the Ethernet flow
points and TESI ESPs. For the TSW modules, you can also display the Near-End Data for the TESI
ESPs.
B. Click the Plot Data button to open the Select Plot Options dialog box.

Step Procedure
4 In the Select Options dialog box, do the following:
A. Select the Counter Type option.
B. Select the Traffic Direction option.
C. Select the PM Counter Type option.
D. Click OK to open the sub-tab that displays the requested graph.
Note: To change or plot options, repeat steps 3 and 4.
TCAs Sub-tab
Planet Operate allows the operator to acknowledge a TCA alert and place it in an acknowledged
state. This state indicates that the operator is aware of the TCA alert, but it has not been resolved.
To view TCA alerts, acknowledge TCA alerts, or to revert acknowledgment of a TCA alert, follow this
procedure.
Step Procedure
2 Click the TCAs sub-tab to view the TCA alerts for the selected node.
Note: To select multiple TCA alerts, hold down the Ctrl key as you click each row (or the Shift key to
select a range of rows).
3 To Acknowledge a TCA alert, select the row(s) and click the Acknowledge button.
4 To revert acknowledgment of a TCA alert, select the row(s) and the click the Un-Acknowledge button.
5 To delete a TCA alert, do the following:
A. Select the row(s) and click the Delete button.
B. In the confirmation needed dialog box, click Yes.
6 To delete all TCA events for a node, do the following:
A. Click the Delete All TCA Events button.
B. In the confirmation needed dialog box, click Yes.

Collect Counters
The collect counters function allows you to gather specific types of performance counters and export
the data to a user-defined file type (XML, HTML, or comma-separated values (CSV) format).
To collect performance counters, follow this procedure.
Step Procedure
2 From the main menu, select Node > Collect Performance Counters to open the Collect Performance
Counters tab.
3 If you want to use the automatic counter collection file name, go to step 4.
To change the file name, select the Override Automatic Filename check box.
In the Counter Collection File Name box, type the new file name.
4 If you want to use the default local backup directory, skip to step 5.
Click Select to open the Browse for Folder dialog box. Locate the folder where the counter collection
file will be saved and click OK.
5 In the Export Format area, select the export file type (XML, HTML, or CSV format).
6 Click Collect.
7 In the Information dialog box, click OK.

Enabling MAC Limiting

Enable MAC limiting profiles, MAC limit PM counters, and TCA notifications using the Node
Information dialog box.
To enable MAC limiting for PSW line cards on a Z-Series node, follow this procedure.
Step Procedure
1 In the Equipment Tree, select the node level.
2 Right-click the node and select View Information to open the Node Information dialog box.

Step Procedure
3 In the Node Information dialog box, do the following:
A. In the Node Information panel, click Maintenance.

B. In the right-side panel, select MAC Limit.
C. From the Enter New Value list, select Enabled.
D. Click Apply.

Routine Maintenance
This section provides routine maintenance task for node-specific equipment.

Note: If a line card or controller card report a communications failure, Z-Series
shelves automatically increase their fan speed to protect the equipment in case
the card reporting the failure is overheating and/or the active controller card
cannot assess the temperature warning. High fan speed is normal under these
circumstances.
In This Chapter
Adjusting the Fan Filter Replacement Interval ....................................... 70
Z22 Fan Maintenance ................................................................................ 71
Z33 Fan Maintenance ................................................................................ 73
Z77 Shelf v2 Fan Maintenance ................................................................. 76
Z77 Shelf Fan Maintenance ...................................................................... 78
Adjusting the Fan Filter Replacement Interval

Z-Series nodes require sufficient airflow to function within the specified temperature range. To
ensure airflow, the fan filter requires cleaning or replacement at regular intervals. Planet Operate
provides a user-configurable fan filter service reminder that is set to 90 days by default. When the
Fan filter-replacing interval expires, Planet Operate issues a Dirty Fan Filter alarm.
Follow the fan filter maintenance procedure for the specified shelf type. Refer to procedures in this
section.
To view or configure the filter service reminder interval and the view the number of days since the
filter was last serviced, follow this procedure.
Step Procedure
1 In Planet Operate, display the Front Panel tab for the Z-Series node.
2 Right-click the chassis and select View Information to display the Module information dialog box.
3 In the Module information tree, click Equipment status.

Step Procedure
4 Click the Fan Filter Replacing Interval (days) row. In the Enter a Value box, enter a value equal to the
previous entry plus the number of days from that date that fan filter maintenance will be performed.
For example, if the configured replacing interval is 90 days, but a site visit to clean the filter is not
available for another 15 days, set the Fan filter replacing interval field to 105 days.
Note: Adhere to your fan filter maintenance schedule. A dirty fan filter may lead to overheating of the
shelf or its components.
5 Click Apply.
6 Click Close.
Z22 Fan Maintenance

The fan filter meets GR-78-CORE specifications.
–48V Fan Module +24V Fan Module
Figure 7: Z22 Fan Modules (Front View) – Status Panel
The following table shows the status panel fan module LEDs.
Label Green Red Amber
Critical Critical Alarm
Major Major Alarm
Minor Minor Alarm
Fan Normal Operation Fan Fail Temporary Shutdown (flashing)
Filter Service Required
The Z22 shelf uses a fan air filter to keep the interior of the chassis clean. Clean or replace the fan air
filter every three to six months, depending on your local environment.

To clean the air filter, simply vacuum the filter. DO NOT USE any liquid to clean the filter as the fan
may subsequently blow it onto electrical parts.
Figure 8: Extracted Z22 Fan Module Rear and Side Views
Air Filter
Figure 9: Slide the Fan Air Filter from the Z22 Fan Module
Caution! — To avoid damage to the Z22 shelf, the fan module should not be removed for
longer than 60 seconds from an operating system.

To remove, clean, and replace the Z22 fan air filter, follow this procedure.
Step Procedure
1 To remove a fan module, press the release latch/handle located on the left side of the fan module; pull
the fan module out from its position in the chassis. The fan module stops operating when the module
is unseated from the shelf backplane.
Note: Removing the fan module resets the 90-day filter service reminder.
2 Slide the air filter from the fan module as shown in the figure above.
3 Vacuum the filter to clean it.
4 After the air filter is cleaned or removed, to reinstall do the following:
A. Slide the air filter back into place in the fan module.
B. Slide the fan module along the guide rails, located on the left side of the chassis, until it engages
with the shelf backplane.
Z33 Fan Maintenance

Fan Filter
Status Panel
Service Button
Figure 10: Z33 Fan Module – Status Panel and Fan Filter

The following table shows the status panel fan module LEDs.
Label Green Red Amber
Critical Critical Alarm
Major Major Alarm
Minor Minor Alarm
ACO ACO Active
Fan Normal Operation Fan Fail Temporary Shutdown (flashing)
Filter Service Required
The Z33 shelf uses a fan filter to keep the interior of the chassis clean. Clean or replace the fan filter
every three to six months, depending of your local environment.
To clean a filter, simply vacuum the filter. DO NOT USE any liquid to clean the filter as the fan may
subsequently blow it onto electrical parts.
Fan Module Front View Fan Module Side View
Fan Filter Handle Fan Filter
Figure 11: Z33 Fan Module Front and Side Views
To remove a fan module, press the release button located on the left side of the unit and pull the fan
module out from its position. The fan module stops operating when the module is unseated from
the shelf backplane.

You can remove the fan filter without removing the fan module.
Fan Filter
Z33 Chassis
Fan Module
Fan Filter Handle
Figure 12: Z33 Fan Module
Fan Filter Maintenance Procedure

To remove, clean, and replace a Z33 fan filter, follow this procedure.
Caution! — To avoid damage to the Z33 shelf, the fan module should not be removed for longer
than 60 seconds from an operating shelf.
Step Procedure
1 Press and hold the Service button on the Fan Module until the Fan LED flashes (amber).
Note: The fans will shut down for 30 seconds to allow you time to remove the fan filter without dust
blowning into the shelf.
Note: Pressing the Service button resets the 90-day filter service reminder. (Hold the button for at
least 3 seconds to reset the 90-day service reminder.)
2 Remove the fan filter by pulling the handle out from the Z33 shelf assembly.
Note: You can remove the fan filter without removing the fan module.
4 Important! — Make sure the correct side of the fan filter is facing the fan module before placing it into
the chassis. A label on the fan filter notes the proper orientation.
After the filter is cleaned or removed, to reinstall do the following:
A. Hold the fan filter so that the metal grill side is facing the line cards.
B. Push the fan filter into the guide rails next to the fan module until it is flush and securely locks.

Z77 Shelf v2 Fan Maintenance

The Z77 shelf v2 assembly uses two redundant fan modules to cool the chassis. The fan modules
push ambient air from the front of the shelf through the shelf to the top, rear exit. You can remove
either module independently without affecting the other. Normal operation requires both of the fan
modules, though one will fully support the cooling requirements of the chassis. Each fan module
contains four fans, adding further redundancy to the design.
Captive thumbscrew
Captive thumbscrew
Figure 13: Z77 Fan Module
Fan LED Details

During normal operation, alert issues may occur (for example, a fan stops working). If this occurs, the
RED LED indicates the fans are not working properly. The GREEN LED indicates the fans are working
properly. The BLUE LED indicates filter service.
Fan Maintenance
The Z77 shelf v2 uses a fan filter to protect and keep clean the interior of the chassis. Clean or
replace the fan filter every three to six months, depending of your local environment. To clean a
filter, simply vacuum the filter. DO NOT USE any liquid to clean it as the fan may subsequently blow
it onto electrical parts.
Disable the fans before removing the fan filter.
To remove, clean, and replace a fan filter, follow this procedure.

Step Procedure
1 Press and hold the Service button located on the right side of the Operations Panel until the Fan
LED flashes.
Service Button
The fans will shut down for 30 seconds to allow you time to remove the fan filter without dust blowing
into the shelf.
2 Remove the fan filter by pulling the handle out from the Z77 shelf v2 assembly.
4 After the filter is cleaned or removed, to reinstall, push the fan filter into the guide rails at each side of
the shelf until it is flush and securely locks.
Note: Disabling the fans resets the 90-day filter service reminder.
Important! — Make sure that the metal filter supports are FACE UP. The other side of the
filter unit does not contain the metal filter supports.

Z77 Shelf Fan Maintenance

The early model Z77 shelf assembly uses three redundant fan modules to cool the chassis. The fan
modules push ambient air from the front of the shelf through the shelf to the top, rear exit. You can
remove each of the fan modules independently without affecting the others. Normal operation
requires all three of the fan modules, though two will fully support the cooling requirements of the
chassis. Each of the fan modules contains two fans, adding further redundancy to the design.
The Z77 shelf assembly has six fans, two fans per fan module. These modules are easily removed.
Thumbscrew
Figure 14: Z77 Fan Unit
Fan LED Details

In the lower right hand corner of the fan module, the fan unit has three LEDs.
Figure 15: Z77 Fan LEDs

During normal operation, alert issues may occur (for example, a fan stops working). Should this
occur, the RED (#3) LED indicates the fans not working properly. The GREEN LED indicates the fans
are working properly.
Handle Fan filter
Fan
Figure 16: Installing and Removing the Z77 Fan Filter
Fan Maintenance
The Z77 shelf uses a fan filter to protect and keep clean the interior of the chassis. Clean or replace
the fan filter every three to six months, depending of your local environment. To clean a filter, simply
vacuum the filter. DO NOT USE any liquid to clean it as the fan may subsequently blow it onto
electrical parts.
Disable the fans before removing the fan filter.
To remove, clean, and replace a fan filter, follow this procedure.
Step Procedure
1 For shelves with the LCD Operations Panel: On the Operations Panel, select the menu tab. Scroll down
to the Disable Fans screen and tap Initiate.

Step Procedure
2 For shelves with the LED Operations Panel: Press and hold the Service button located on the right side
of the Operations Panel until the Fan LED flashes.
Service Button
The fans will shut down for 30 seconds to allow you time to remove the fan filter without dust being
blown into the shelf.
3 Remove the fan filter by pulling the handle out from the Z77 shelf assembly.
5 After the filter is cleaned or removed, to reinstall, push the fan filter into the guide rails at each side of
the shelf until it is flush and securely locks.
Important! — Make sure that the metal filter supports are FACE UP. The other side of the
filter unit does not contain the metal filter supports.

Backup, Restore, and Software Upgrades
This section describes the procedures for database backup and restore and the procedures for
software upgrades.
In This Chapter
NE Backup Configuration.......................................................................... 81
Software Upgrades .................................................................................... 93
Upgrade Planet Operate – 17.08 ...........................................................123
NE Backup Configuration
The backup feature allows you to back up the entire network, individual nodes, nodes within a
Region, and nodes within a Multi Node Group.
Note: If you add one or more nodes to a Region or a Multi Node Group after you
have defined the backup job, you will need to add the node(s) to the backup job
in order to ensure a complete back up (unless the "Include All Nodes" check box
is selected).
Default All-Nodes Backup Job

Planet Operate provides one default backup job, called All-nodes backup job, to periodically back
up the databases of all Planet Operate-managed nodes in the network.
For a new server installation, the default interval for the All-nodes backup job is seven days; this
period is user-configurable. During an upgrade, the currently configured interval remains
unchanged.

You can configure and monitor this default backup job and manage the backup files as you would
any other configured backup job, as described in the following sections.
Figure 17: All-Nodes Backup Job

Scheduled NE Database Backup and Restore

This section provides step-by-step instructions on scheduled NE database backup and restore jobs.
To schedule backups and restores, follow this procedure.
Step Procedure
1 A. From the main menu, select Task > Node Backup Jobs. The Node Backup Configuration dialog
box opens. Note that the Job configuration fields are grayed out.
B. Click the Define backup jobs tab.

Step Procedure
2 Create a New Job
A. Click Create Job in the Job configuration pane. The Job configuration fields are no longer grayed
out.
B. Enter the new job name in the Job name field.

C. Enter the description of the new job in the Description field.
D. Select the Enabled checkbox to permit the job to run as scheduled. Deselect the Enabled checkbox
to prevent the job from running.
Note: A backup job will not run until you select the Enabled check box.
E. Click the Scheduled button to create a recurring backup job. Click the Manual button to create a
one-time backup job.
F. Click Select time. The Select Date and Time dialog box opens.
G. Select a date and time and then click OK.
Note: The date and time is based on the server’s date and time.
Tip: You can run a backup immediately by entering a start time earlier than the current
time, selecting the Enabled check box, and clicking Apply.
H. Enter the backup interval value in the Period field and then select Days, Hours, or Minutes from the
dropdown list.
I. Click Apply. The new job is created and appears in the Defined backup jobs list.
J. Continue with step 4 to add all nodes to the new backup job or with step 5 to add specified nodes,
regions, or multi-node groups.

Step Procedure
3 Add All Nodes to the Backup Job
A. Expand the Defined backup jobs list and select the newly created job.
B. Select the Include all nodes checkbox to include all Planet-Operate-managed nodes from the
entire network.
Important! — This option automatically adds new nodes added to the network in the future.
C. Select Incremental backups to create a backup of the Accedian nodes for which there has been a
configuration change. This option is designed for customers who have thousands of Accedian
nodes and do not want to use server resources to execute and save backups of Accedian nodes to
which changes have not been made.
• Only one incremental job may be created within the network.
• Nodes with the same config count are skipped and not recorded in the SQL DB.
• Include all nodes and Incremental backups may be combined.
• SQL DB migration is needed and adds a new column "incrementalbackups" with default value
disabled.
• Node info shows the "Backup config change count" to facilitate troubleshooting.
D. Click Apply. The changes are applied to the backup job.
E. Click Close.

Step Procedure
4 Add Specified Nodes, Regions, and Multi-Node Groups
A. Expand the Defined backup jobs list and select the newly created job.
B. Click Add Nodes. The Select Nodes for Backup dialog box opens.
C. Locate the node(s) to add to the task.

• Use the vertical scroll bar to view the list.
• In the search box, type all or part of the node information (node name, region, DCN IP address,
alarm status, software version, or communication state).
• Sort the list by a displayed criterion (such as node name, region, or software version) by clicking
a column title once. To reverse the sort order, click the column title a second time.
OR
• View only the selected nodes: Click the Settings icon , and select Show Selected.
• Change the column display: Drag and drop a column title into a new position, or, at the top right
of the dialog box, click the Settings icon and select Manage Columns. In the Select
Columns dialog box, you can hide a column by clearing the check box to the right of the column
name, or reorder a column by dragging the title and dropping it in a new position. Click OK to
return to the Select Nodes dialog box.
• Refresh the node list: Click the Settings icon, and select Refresh.
D. Select the nodes to include in the task by selecting (checking) the check box for each node. To
select all nodes that display in the list, select (check) the check box located to the left of the search
box.
E. Click OK. The selected node(s) appear below the Defined backup job name when expanded.

Step Procedure
5 Remove a Node
Do one of the following to remove a node from an existing backup job.
A. Select the backup job in the Defined backup jobs list.
B. Click Add nodes. The Select Nodes for Backup dialog box opens.
C. Uncheck the nodes to be removed from the backup job and then click OK to save the changes.
OR
A. Select the backup job in the Defined backup jobs list.
B. Expand the backup job and select an individual node from the tree. Click Remove Node in the Job
configuration pane.
C. Click Yes to confirm.
6 Delete a Job
A. Select the job to be deleted in the Defined backup jobs list.
B. Click Delete Job in the Job configuration pane.
C. Click Yes to delete the backup job and all associated backup files. Click No to delete the backup job
and retain the associated backup files.
Monitor Running Jobs and View Job Results

To activate a job and view job results, follow this procedure.
Step Procedure
1 From the main menu, select Task > Node Backup Jobs to open the Node Backup Configuration
dialog box.

Step Procedure
2 Click the Monitor Running Jobs tab.
3 In the Monitor Running Jobs tab, do the following:

A. Select the job.
B. Click Start Job.

Step Procedure
4 When the job has completed click the View Job Results tab.
In the tree panel, select the job to view.
Note: To remove a result from the display area, select the job result and click Delete Result.

Manage Backup Files and Database Restore

Use the backup file management feature to delete, restore, purge, and save backed-up databases.
Note: The Purge Backup Files option deletes the backed-up databases and associated job runs and
job results for all available nodes based on the Backup Files to be Kept for N Days server setting.
The default is 90 days. (To view your server setting, from the Planet Operate main menu, select
Options > Server Settings > General tab.)
To manage backup files, follow this procedure.
Step Procedure
dialog box.
2 Click the Manage Backup Files tab.
The panel on the left shows the nodes with backup files. When you select an entity, by default the
status, size, date, and related information for all available backup files display in the panel on the right.
To filter the list of backup files, do the following:
A. In the panel on the left, select an entity.
B. From the Filter Backup Files list, select an option to view backup files dated in the last 24 hours, the
last week, or the last month. Alternatively, enter a numeric value in the Filter Backup Files box to
enable the hours/days/weeks/months list, then select a frequency. (For example, to display all
backup files dated within the past two weeks, enter 2, then select weeks.)
C. (Optional) To clear the Backup File list, click Refresh.

Step Procedure
3 To delete a backup file, do the following:
B. In the panel on the right, select one or more backup files.
To select multiple files, hold down the Ctrl key and select the intended rows, or select a row, then
hold down the Shift key and select a range of rows.
C. Click Delete.
D. In the confirmation dialog box, click Yes.
4 To restore from a backup file, do the following:
B. In the panel on the right, select a backup file.
C. Click Restore.
Note: Although restoring the database may be service affecting, provisioning information is retained in
the management plane during the restore process. Traffic flow should not be affected during this
period.
Note: Accedian nodes automatically reboot after a database restore operation.
5 To save a backup file to your local machine, do the following:
B. In the panel on the right, select a backup file.
C. Click Save Locally.
6 To purge all backup files older than the number of days specified in the Backup Files to be Kept for N
Day server setting, do the following:
A. Click Purge Backup Files.
B. In the confirmation dialog box, click Yes.

Step Procedure
7 To automatically delete old backup files, do the following.
Purge backup files to keep only recent backups on the server and to remove unneeded files.
A. From the main menu, select Options > Server Settings. The Server Settings dialog box opens.
B. Select Auto purge backup files.

C. Enter the number of days between purges in the Purge backup files every N days field. The
default is 14 days.
D. Enter the number of days to keep old backup files before purging in the Backup files to be kept
for N days field. The default is 90 days.
E. Click Apply.

Software Upgrades
The software upgrade process includes defining and managing the software upgrades tasks. Planet
Operate allows you to view software version information. You can create, copy, view, modify, and
schedule software tasks.
For a matrix of Z-Series software compatibility, including version dependencies between Blue Planet,
Planet Operate, third-party element adapters, and CyOS, refer to the relevant Planet Operate Release
Notes and/or the Z-Series CyOS Release Notes, accessible online in the Ciena portal library.
Note: When a Network Element software upgrade is in progress, access to the
Network Element via Planet Operate or other management interfaces is less
responsive compared to non-upgrade access.
Note: In rare cases, an upgrade of a Z-Series shelf may show completed, but
the shelf CEM controller card has not completed the upgrade process. In these
cases, a non-traffic impacting hard reset can be issued to the CEM controller
card to complete the upgrade process.
Note: If a downgrade to an older Z-Series release is performed on the Z-Series

shelf, then a full power-cycle reset of the downgraded Network Element must
be performed. Note that this is different than reverting to a previous software
image.
Note: When the standby system controller is in slot 1 of the shelf (Z22, Z33 or
Z77) and not operational (because of a CyOS stop or an Auto-Upgrade in
progress), the Active/Standby indication shown on the Planet Operate Front
Panel may not display correctly.
Note: If a system controller switchover occurs while a Z-Series line card is in the
auto-upgrade process, the line card remains in an auto-upgrade state until
Planet Operate performs a reset on the line card.
Workaround: Use the "Software Restart" function to restart the line card. In
Planet Operate, select the node in the Network view tab. Double-click the node
to open the Front Panel tab. In the Node menu, select Reset Modules to open
the Reset Node Linecard Modules dialog box. In the dialog box Equipment tree,
click the standby system controller card. Then, select the Software Restart
option button. Click the Reset button. In the Confirmation dialog box, click Yes.
Note: For Link Aggregation Groups on PME line cards, to insure a "hitless"
upgrade during the activation phase of a software upgrade, the LACP Switching
Type must be set to On (On = static LAG configuration) for each member port.

Note: Configure one of the Z-Series ports on each VLAN in the Spanning Tree
Protocol (STP) or Multiple Spanning Tree Protocol (MSTP) group as the block
point to ensure a hitless upgrade and prevent a loop.
If Z-Series ports are not designated as the blocking point, special configuration
is required to prevent a loop during an upgrade, as follows:
• STP: set all but one of the transceivers in the STP group to
Locked to Disable. There should be only one unlocked port in the STP
group.
• MSTP: set all redundant flow points to Locked to Disable to ensure that
there is only one path per MSTP group and avoid loops.
Important! — Clear all alarm conditions related to equipment failures, for example, COMM
Fail, XCVR COMM Fail, and so forth, prior to activating an upgrade.

Service-Affected Line Cards

An Operating System software upgrade is service affecting for Z-Series line cards listed in the
following matrix.
Important! — This section provides specific PSW line card upgrade information. Review these
guidelines and considerations prior to upgrading PSW line cards. The PSW upgrade information
in this section follows the service-affecting line card matrix shown below.
Service-Affecting Line Card Matrix
From TO CyOS Release …

CyOS
Release 10.0 9.0 8.0 7.0 6.0 5.2 5.0
DTM-8/8G 1
10.0 and DTM-100G 1
higher PME-216i 2
PME-412 2
DTM-8/8G 1 DTM-8/8G 1
9.0 and DTM-100G 1 DTM-100G 1
higher 5 PME-216i 2 PME-216i 2
PME-412 2 PME-412 2
DTM-8/8G 1 DTM-8/8G 1 DTM-8/8G 1

8.0 and DTM-100G 1
DTM-100G 1
DTM-100G 1
higher 4 PME-216i 2 PME-216i 2 PME-216i 2
PME-412 2 PME-412 2 PME-412 2
DTM-8/8G 1 DTM-8/8G 1 DTM-8/8G 1

7.0 and DTM-100G 1 DTM-100G 1 DTM-100G 1
higher 3 PME-216i 2 PME-216i 2 PME-216i 2
PME-412 2 PME-412 2 PME-412 2
DTM-8/8G 1 DTM-8/8G 1 DTM-8/8G 1 DTM-8/8G 1

6.0.06 and DTM-100G 1 DTM-100G 1 DTM-100G 1 DTM-100G 1
higher PME-216i 2 PME-216i 2 PME-216i 2 PME-216i 2
PME-412 2 PME-412 2 PME-412 2 PME-412 2
DTM-8/8G 1 DTM-8/8G 1 DTM-8/8G 1 DTM-8/8G 1 DTM-8/8G 1

DTM-100G 1 DTM-100G 1 DTM-100G 1 DTM-100G 1 DTM-100G 1
PME-216i 2 PME-216i 2 PME-216i 2 PME-216i 2 PME-216i 2
6.0.01 to
PME-412 2 PME-412 2 PME-412 2 PME-412 2 PME-412 2
6.0.05
PSW-10G10 PSW-10G10 PSW-10G10 PSW-10G10 PSW-10G10
PSW-618 PSW-618 PSW-618 PSW-618 PSW-618
PSW-100G PSW-100G PSW-100G PSW-100G PSW-100G

From TO CyOS Release …

CyOS
Release 10.0 9.0 8.0 7.0 6.0 5.2 5.0
DTM-8/8G 1 DTM-8/8G 1 DTM-8/8G 1 DTM-8/8G 1 DTM-8/8G 1

DTM-100G 1 DTM-100G 1 DTM-100G 1 DTM-100G 1 DTM-100G 1
PME-216i 2 PME-216i 2 PME-216i 2 PME-216i 2 PME-216i 2
PME-412 2 PME-412 2 PME-412 2 PME-412 2 PME-412 2
5.2 PSW-10G10 PSW-10G10 PSW-10G10 PSW-10G10 PSW-10G10
PSW-618 PSW-618 PSW-618 PSW-618 PSW-618
PSW-100G PSW-100G PSW-100G PSW-100G PSW-100G
TSW-10G10 TSW-10G10 TSW-10G10 TSW-10G10 TSW-10G10
XC-2800 XC-2800 XC-2800 XC-2800 XC-2800
DTM-8/8G 1 DTM-8/8G 1 DTM-8/8G 1 DTM-8/8G 1 DTM-8/8G 1 FLX-216i

DTM-100G 1 DTM-100G 1 DTM-100G 1 DTM-100G 1 DTM-100G 1 PME-216i 2
FLX-216i FLX-216i FLX-216i FLX-216i FLX-216i PME-412 2
PME-216i 2 PME-216i 2 PME-216i 2 PME-216i 2 PME-216i 2 PSW-10G10
5.0 PME-412 2 PME-412 2 PME-412 2 PME-412 2 PME-412 2 PSW-618
PSW-10G10 PSW-10G10 PSW-10G10 PSW-10G10 PSW-10G10 TSW-10G10
PSW-618 PSW-618 PSW-618 PSW-618 PSW-618 XC-2800
TSW-10G10 TSW-10G10 TSW-10G10 TSW-10G10 TSW-10G10
XC-2800 XC-2800 XC-2800 XC-2800 XC-2800
1Software upgrades of DTM-8/8G and DTM-100G line cards to CyOS Release 6.0 or 7.0 are service affecting
when the cards participate in a TPM protection configuration.
2 Software upgrades of PME line cards are service affecting when supporting LAG with active or passive LACP.
3 PSW line cards participating in an NNI ring and upgraded to CyOS Release 7.0.09 or higher require a manual
service-affecting hardware reboot to enable the FPGA firmware and the PSW ERP loop detection and
interruption feature.
4A new version of the LME-10G10 line card (LME-10G10d) is available in CyOS Release 8.0 and higher. If a new
version LME-10G10d line card (with part number 800-0138-02 or later) is upgraded to CyOS Release 8.0 or
higher, then a manual service-affecting hardware reboot is required to configure the OSPF in-band
management via the general communications channel (GCC) feature.
5For a FLX-216i line card upgraded to CyOS release 9.0 or higher, a manual service-affecting hardware reboot is
required before including it in a TPM protection group.
PSW Upgrade Guidelines and Considerations

The Broadcom SDK reorders switch chip internal table entries on PSW line cards when:
• Provisioning on the PSW line card occurs requiring an entry in the internal table;
and
• There is insufficient free space in the internal table to add the entry, so the SDK moves
entries to create additional space (scale related).
Re-ordering sets the stage for a traffic impact, but does not actually impact traffic.

Re-ordering can impact traffic if:

• There are ERPs terminating on the PSW line card where re-ordering has occurred;
and
• A ring switch occurs requiring the FPGA on the PSW line card to write to the switch chip to
block/unblock;
and
• The entry being written by the FPGA has been moved elsewhere.
In summary, for CyOS Releases 6.0 and higher, the problem is limited to a PSW line card when:
• There is significant existing provisioning (scale);
• Additional provisioning is received causing a reorder;
and
• There are one or more ERPs terminating on the PSW line card, and there is an event causing
a ring switch to occur.
or
• An ERP V2 RPL blocking port remains blocked during a signal failure (SF) event. Release 9.0.06
corrects the problem if only ERP V2 is on the affected line card. However, if V1 and V2 are
both provisioned on the same line card and the card is the RPL owner for both a V1 and a V2
ring, the problem could occur. Release 10.0 corrects this issue completely.
A cold boot of PSW line cards is required to pick up the FPGA change that accompanies fixes in the
software. Following an upgrade to CyOS 8.0.08 or 9.0.03 and higher, users will receive an alarm
notifying them that a cold boot of PSW line cards is required. For additional information, see Field
Service Bulletin 101-2016-023.
Releases 8.0.08 and 9.0.03 and higher, PSW line cards will raise an alarm with a warning severity
whenever the FPGA image on disk differs from that loaded into the FPGA program memory. Because
an FPGA firmware update with ERP fixes/improvements is included with 8.0.08 and 9.0.03 and
higher, this alarm is raised for every PSW line card following an upgrade activation. The alarm will
clear after a cold boot of the line card.
To avoid requiring a Planet Operate upgrade to recognize this additional alarm, the text of an
existing alarm category is reused. The alarm Additional Information field displays, "Equipment
degraded - Requiring a cold restart to support new features."
Users may dismiss these alarms at their own discretion. To do so, select one or more alarms and
mark them as “acknowledged,” then filter the Planet Operate alarm list to display “unacknowledged”
alarms only.
Manual Hardware Reboot of PSW Modules in CyOS 8.0 or Higher

PSW line cards upgraded to CyOS Release 8.0 or higher require a manual service-affecting
hardware reboot (cold boot) in order:
• For Link Fault Propagation to function properly for EPL services
• To provision E-Tree services on a PSW line card

With the Z-Series node selected in the Network view tab, from the main menu select Node > Reset
Modules. From the slot list, select the intended line card to reset. Select the Hardware Reboot radio
button and click Reset.
Note 1: Performing a hardware reboot of the line card serves to enable the FPGA firmware and the
PSW Link Fault Propagation for EPL and E-Tree features.
Note 2: If a hardware reboot of installed PSW line cards is not performed after upgrading to
CyOS Release 8.0 or higher, the FPGA firmware for E-Tree services is not enabled and the
system generates the following message:
Firmware does not support this feature.
Perform a hard reboot to enable the FPGA firmware upgrade.
Manual Hardware Reboot of PSW Modules in CyOS 7.0.09 or Higher

Loop Detection and Interruption Feature
For PSW line cards participating in a NNI ring and upgraded to CyOS Release 7.0.09 or higher, a
manual service-affecting hardware reboot is required to enable the FPGA firmware and the PSW ERP
loop detection and interruption feature.
Performing a hardware reboot of the line card serves to enable the FPGA firmware and PSW ERP
loop detection and interruption feature.
Note 1: If a hardware reboot of installed PSW line cards is not performed after upgrading to
CyOS Release 7.0.09 or higher, the FPGA firmware is not enabled, and the loop detection and
interruption feature will fail and the system generates the following message:

Note 2: If the loop detection and interruption feature is pre-provisioned "without a PSW line
card in the slot," and a PSW line card is installed later with an older CyOS version, the PSW line
card will automatically upgrade to CyOS Release 7.0.09. However, you must still perform a
hardware reboot of the installed PSW line card to enable the FPGA firmware. If the hardware
reboot is not performed on the installed PSW line card, the loop detection and interruption
feature will fail, and the system generates the following alarm:
Source Type: PSW-xxx module
Probable Cause: Equipment Fail
Qualifier: ERP Loop Detection Not Supported

Resolution of Protection and Configuration Issues

For PSW line cards upgraded to CyOS Release 7.0.09 or higher, a manual, service-affecting
hardware reboot is required to resolve the following protection and configuration issues:
• In some cases, PSW line cards used in an ERP configuration were not providing blocking for
both shaped and non-shaped services on the same ring that could result in loops and traffic
disruption.
• In a PSW NNI network ring configuration, when the PSW port on one leg of the main ring was
in a Locked to Disable admin state, on a reboot of the line card, both ports of the main ring
were blocked.
• PSW line cards did not recognize a link fail status in a G.8032 protection configuration. This
issue caused disruption of traffic.
• When sending a Continuity Check Messages (CCM) immediately after sending Ring Automatic
Protection Switching (R-APS), the CCM was corrupted. The corruption occurred when the
R-APS, sent every 5 seconds, and CCMs, sent every 3.3 ms, infrequently lined up.
• For PSW line cards operating in the PBB-TE protocol, the ring initialized with all ports
unblocked in the Pending protection state after ring creation. This condition persisted until
the Wait-to-Restore (WTR) timer expired and then the protection state moved from Pending
to Idle. At that point, the ring corrected itself and automatically blocked the RPLO.
• For PSW line cards in a network ERP and cross-card configuration, when the RPLO was locked
and unlocked, both ports in the cross-card configuration in a non-RPLO node were blocked
and not allowing traffic to flow. The port in the lower slot number of the cross-card
configuration should have unblocked while in the Pending protection state.
CyOS Upgrades of PSW and TSW-10G10 Line Cards and XC-2800 Switch Fabric Modules
Note the following:
• Upgrading PSW-10G10, PSW-618, PSW-100G, and TSW-10G10 line cards and XC-2800 switch
fabric modules from CyOS Release 6.0.06 (or a higher 6.0 release) to Release 7.0 is a
non-service affecting ("hitless") operation. Support for non-service affecting upgrades starts
with software updates from CyOS release 6.0.06 and higher to a higher release.
• Upgrading from CyOS Release 6.0.01 through 6.01.05 to the latest available GA version of
release 6.0 is service affecting for all PSW line cards, but is non-service affecting for
TSW-10G10 line cards and XC-2800 modules.
• CyOS Release 6.0.06 and higher supports non-service affecting upgrades for PSW line cards
participating in a Link Aggregation Group. However, when a PSW line card participates in a
LAG or other protection scheme configuration, the system does not perform a protection
switch or warm reset during a software upgrade.
Manual Hardware Reboot of the FLX-216i Modules in CyOS 9.0 or Higher

For a FLX-216i line card upgraded to CyOS release 9.0 or higher, a manual service-affecting hardware
reboot is required before including it in a TPM protection group.
button option and click Reset.

Performing a hardware reboot of the line card is required to upgrade the firmware and enabling the
sub-50 ms optical protection switchover feature.
If a hardware reboot of the line card has not been performed after upgrading to CyOS release
9.0, creating a new protection group will fail with the following message:
ResErrProtectNotSupported:
createPg, Protection not supported:
FAC <card AID> Card must be present with CLPD version 16 or higher.
Insert card or perform a hard reboot to upgrade.
Manual Hardware Reboot of LME-10G10d Modules in CyOS 8.0 or Higher

A new version of the LME-10G10 line card (LME-10G10d) is available in CyOS Release 8.0 or higher. If
the new version LME-10G10d line card (with part number 800-0138-02 or later) is upgraded to CyOS
Release 8.0, then a manual service-affecting hardware reboot is required in order to configure the
OSPF in-band management via the general communications channel (GCC) feature. (With the
Z-Series node selected in Network view tab, from the main menu select Node > Reset Modules. In
the slot list, select the card to reset. Select the Hardware Reboot option button and click Reset.)
Performing a hard reboot of the LME-10G10d line card serves to activate the OSPF in-band
management via the GCC channel feature.
Manual Hardware Reboot of LME-10G10 Modules in CyOS 7.0 or Higher

For an LME-10G10 line card upgraded to CyOS Release 7.0 or higher, a manual, service-affecting
hardware reboot is required before including the line card in a TPM protection group.
Performing a hardware reboot of the line card serves to activate the sub-50 ms switchover timing
feature in this release.
Note: If a hardware reboot of the line card has not been performed after upgrading to CyOS Release
7.0 or higher, creating a new protection group will fail with the following message:
Manual Hardware Reboot of DTM-100G Modules in CyOS 6.0 or Higher

For a DTM-100G line card upgraded to CyOS Release 6.0 or higher, a manual, service-affecting
hardware reboot is required before including it in a TPM protection group.
button option and click Reset.
Performing a hardware reboot of the line card serves to activate the improved, sub-50 ms switchover
timing feature in this release.
If a hardware reboot of the line card has not been performed after upgrading to CyOS Release
6.0 or higher, creating a new protection group will fail with the following message:
Manual Hardware Reboot of DTM-8 Modules in CyOS 6.0 or Higher

For a DTM-8 line card upgraded to CyOS Release 6.0 or higher from a release lower than Release 6.0,
a manual, service-affecting hardware reboot is required before including it in a TPM protection
group.
option and click Reset.
Performing a hard reboot of the line card serves to activate the improved, sub-50 ms switchover
timing feature in this release.
If the line card has not been rebooted after upgrading to CyOS Release 6.0 or higher, creating a
new protection group will fail with the following message:
Viewing NE Software Information

To view network element software information, follow this procedure.
Step Procedure
1 From the main menu, select Task > Node Software Update to open the Software Management &
Packaging dialog box.
2 Click the NE Software Information tab.
In the panel on the left, select (click) the network element to display the software version information in
the panel on the right.
3 Click Close.
Uploading a Software Upgrade Image

Use the software repository function to view, upload, or remove software upgrade images.
To upload a software upgrade image, follow this procedure.
Step Procedure
1 Download the required Z-Series CyOS software package from the Ciena website portal.
3 Click the Software Repository tab to view the software image repository.
Step Procedure
Upload a software image
4 To upload a software image, do the following:
A. Click Upload Image to open the Choose an Image File to Upload to Server dialog box.
B. Select the file you downloaded in step 1 and click Open to display the Upload Image Details dialog
box.
C. From the Product Family list, select the node type for this image.
D. In the Description field, enter a useful description.
E. Click OK.
The uploaded image displays in the Software Repository tab.
Note: Click Refresh to update the display.
Defining an Upgrade Task

Completing the upgrade for Z-Series nodes requires these steps:
• Download
• Prepare
• Activate
You must perform the download and prepare, and activate steps in sequence. Whether processing
the steps individually or in combination, you must perform the download step first, followed by
prepare, and then activate.
Ciena recommends completing the upgrade process in two stages:
• Download and Prepare
• Activate
The following table shows the Operations parameters used in defining a software upgrade task.
Parameter Description
Download and Downloads the software upgrade image to the file system of the active Z77 BOSS, Z22/Z33
Prepare management card (slot 1 or 2), or L-AMP shelf.
The prepare step installs the already downloaded software package to the standby partition
of the shelf.
Activate Activates the standby partition as the active partition with the new software release.
(After activation, the previous software image will be intact on the standby partition until the
next Prepare operation.)
Operation Mode Parameter

Operation Mode of the software upgrade task has two options:
• Process NE(s) in Sequence: In this mode, one Z-Series node upgrades at a time. A node
does not upgrade until the previous node in the sequence has successfully upgraded. This
mode allows you to stop the upgrade more easily, if necessary.
• Process NE(s) in Parallel: In this mode, all Z-Series nodes targeted for upgrade, upgrade at
the same time.
Note that if any step in the upgrade process fails, the management process for the upgrade will
terminate for all nodes.
Important! — Resetting a network element using the Software Reboot or Hardware

Reboot option may be service affecting.
Important! — The Activation step requires all cards in the shelf to be prepared with the
same software release. If a card is not prepared or prepared with a different software
release, Activation will be rejected and marked as failed.
Max. Concurrent Downloads

Use this parameter to specify the maximum number of nodes to download the software image to
concurrently. The default is five nodes.
State Field
The following table describes each read-only task State field.
Inactive Task is not yet activated. Operational options: delete, modify, or activate
Pending Task is enabled, but not yet executing. Operational option: de-activate
Executing Task is executing. Operational option: abort
Aborted Task has been aborted based on user request. Operational option: delete
Completed Task is done. Operational option: delete
Failed One or more sub-tasks have failed. Operational option: delete
Additional Operations Parameter and Sequence

The download, prepare, and activate steps must always be done in sequence. Whether processing
the steps individually or in combination, download must always be done first, followed by prepare,
and then activate. For example, you could execute download in a maintenance window, execute
prepare in a later maintenance window and then execute activate in another maintenance window;
or you could execute download and then in a subsequent maintenance window execute prepare
and activate; or you could execute download, prepare and activate in the same maintenance
window.
The following table describes the Operations parameter used in defining a software upgrade task.
Download Downloads the software upgrade image to the file system of the active Z77 BOSS, Z22/Z33
management card (slot 1 or 2), or L-AMP shelf.
Download and Downloads the software upgrade image to the file system of the active Z77 BOSS, Z22/Z33
Prepare management card (slot 1 or 2), or L-AMP shelf.
The prepare step distributes the software upgrade image to the standby partition of all line
cards, or L-AMP shelf.
Download, Downloads the software upgrade image to the file system of the active Z77 BOSS, Z22/Z33
Prepare and management card (slot 1 or 2), or L-AMP shelf.
Activate The prepare step distributes the software upgrade image to the standby partition of all line
cards, or the L-AMP shelf.
The activate step resets the software image from the standby partition on each line card or
L-AMP shelf. The operating system stops and restarts pointed at the new software image.
(The standby partition with the new software image is now the active partition. The previously
active partition becomes the standby partition with the previous software image retained.)
Prepare Distributes the software upgrade image to the standby partition of all line cards or
L-AMP shelves.
Prepare and Distributes the software upgrade image to the standby partition of all line cards or L-AMP
Activate shelves.
The activate step resets the software image from the standby partition on each line card, or
L-AMP shelf. The operating system stops and restarts pointed at the new software image.
(After activation, the standby partition with the new software image becomes the active
partition. The previously active partition becomes the standby partition with the previous
software image retained.)
Activate Activates the software image from the standby partition on each line card or L-AMP shelf.
The operating system stops and restarts pointed at the new software image.
(After activation, the standby partition with the new software image becomes the active
partition. The previously active partition becomes the standby partition with the previous
software image retained.)
Revert Reverts to the previous software image.
Defining a Software Update Task

To define a software update task, follow this procedure.
Step Procedure
1 From the main menu, select Configuration > Node Software Update to open the Software
Management & Packaging dialog box.
2 In the Define Upgrade tab, click Create Upgrade to add a "New Task" to the Defined Upgrades tree and
to activate the Task Configuration area.
Step Procedure
3 In the Task Configuration area, do the following:
A. From the Task Name box, type a name for the task.
B. From the Description box, type a task description.
C. From the Product Family list, select the Z-Series Nodes.
D. Click Select to open the Select Image dialog box.
E. From the Select Image dialog box, select the applicable software upgrade image and click Select.
Note: Use the software repository function to upload software upgrade images. For detailed
information, see Uploading a Software Upgrade Image starting on page 103 (Software Repository
tab).
F. (Optional) Configure a Start Time for this task other than the current time by clicking Select Time
and specifying a date and time. If you do not configure a future time, the task executes as soon as
you click Enable (see step 5).
Note: The system bases the date and time selected on the server date and time.
G. From the Operations list, select the type of upgrade operation.
Note: For Z-Series nodes, you can select all six upgrade options plus Revert.
H. From the Operation Mode list, select the mode, Process NE(s) in Sequence or Process NE(s) in
Parallel.
I. From the Max. Concurrent Downloads list, select the maximum number of nodes allowed for
concurrent downloads of the software image.
J. To download the software image to the standby partition, select (check) the Use Standby Partition
check box.
Note: This option forces the software upgrade process to force prepare the software release on
the Z-Series standby partition, even if the current load is already running. Without this option
checked, if you attempt to prepare a node with the release that is already running, the activity will
be rejected.
K. Click Targets to open the Select Node for Upgrade dialog box and continue with step 4.
Step Procedure
4 In the Select Nodes for Upgrade dialog box, do the following:
A. Locate the node(s) to add to the task using the following methods:
Optionally customize the node list, as follows:
• Change the column display: Drag and drop a column title into a new position, or, at the top,
right of the dialog box, click the Settings icon , and select Manage Columns. In the Select
B. Select the nodes to include in the task by selecting (checking) the check box for each node.
To select all nodes that display in the list, select (check) the check box located to the left of the
search box.
C. Click OK.
The upgrade task with the target network entities display in the Defined Upgrades tree panel.
5 Click Apply to save the task and schedule the task to start according to the start time.
Note: To remove a node from the list of target nodes before the upgrade task
begins, do one of the following:
• In the Software Management & Packaging dialog box tree panel, select the
upgrade task, and click Targets to open the Node Selection dialog box. Clear
the check box for each node you are removing, and then click OK to save the
change.
—or—
• Expand the upgrade task and select the node in the tree panel. Click Remove
Target, and then click Yes to confirm the action.
Equipment Audit
It is essential to complete an Equipment Audit prior to enabling the Download & Prepare and
Activate steps.
Planet Operate reports the results of the audit in the Equipment Audit Report dialog box, which
displays a node/slot/module-indexed message describing each issue identified. Click (select) any
node marked with a red X icon to review the audit report for that node.
• A Warning message indicates that the operation may be service affecting. In some cases, you
can mitigate by changing the configuration before proceeding; for example, an LACP-enabled
LAG.
• An Error message indicates an issue that requires immediate attention and must be resolved
prior to any software upgrade, for example, damage or corruption of the flash storage
media.
The next table shows the audit activity based on the operation defined for the Z-Series equipment
upgrade task.
Download and The download audit checks for sufficient disk space for successful download of the software
Prepare package.
The prepare audit identifies any known issues that may affect services or the software
upgrade process (for example; high CPU, low memory, database migration issues).
Activate The activate audit checks for any firmware changes that may require a hard reset of a line
card (for example; FPGA or CPLD changes).
To execute an Equipment Audit task, follow this procedure.
Step Procedure
2 In the Define Upgrade tab, select the software upgrade task to apply the equipment audit.
3 To start the equipment audit process, click the Audit button.

The Audit feature allows you to perform an equipment audit without committing to the software
upgrade. The on-screen audit displays the equipment status of each target node. Planet Operate will
show any issues with a red X icon.
4 Click (select) any node marked with a red X icon to review the audit report for that node.
If you cannot resolve the issue, contact Ciena Customer Service for assistance.
(Click Cancel at any time to stop the audit.)
Defining an Upgrade Task—Third-Party Nodes

Completing an upgrade for third-party node Accedian (firmware 7.1 and higher), and Ciena Packet
Networking (SAOS 6.16 and higher) devices requires these steps:
• Download
• Activate
Note: You must perform the download and activate steps in sequence. Whether
processing the steps individually or in combination, you must perform the
download step first, followed by activate.
For example, you could execute download in a maintenance window, and then
execute activate in another subsequent maintenance window; or you could
execute download and activate in the same maintenance window. Ciena
recommends completing the upgrade process in two separate stages.
The following table shows the Operations parameters used in defining a software upgrade task.
Download Downloads (installs) the new software image to the device. This is the first step of a two-step
upgrade process.
Activate Activates the installed new software image. This is the second step of a two-step upgrade
process.
Note: Accedian devices with 6.4 and lower firmware do not support the Activate parameter.
Download and Downloads and activates the new software image. This is a one-step upgrade process.
Activate Note: Accedian devices with 6.4 and lower firmware do not support the Download and
Activate parameter.
Revert Reverts to the previous software image, if any.
Operation Mode Parameters

Operation Mode of the software upgrade task has two options:
• Process NE(s) in Sequence: In this mode, one node upgrades at a time. A node does not
upgrade until the previous node in the sequence has successfully upgraded. This mode
allows you to stop the upgrade more easily, if necessary.
• Process NE(s) in Parallel: In this mode, all nodes targeted for upgrade, upgrade at the same
time. The number of nodes processed in parallel is limited by Max. Concurrent Downloads
setting.
Note: If any step in the node upgrade process fails, the upgrade management process
terminates for the failed node.
Max. Concurrent Downloads

Use this parameter to specify the maximum number of nodes allowed for concurrent downloads of
the software image. The default setting is five nodes.
State Field
The following table describes each read-only task State field.
Defining a Software Update Task

To define a software update task, follow this procedure.
Step Procedure
1 From the main menu, select Configuration > Node Software Update to open the Software
Management & Packaging dialog box.
2 In the Define Upgrade tab, click Create Upgrade to add a "New Task" to the Defined Upgrades tree and
to activate the Task Configuration area.
Step Procedure
3 In the Task Configuration area, do the following:
A. From the Task Name box, type a name for the task.
B. From the Description box, type a task description.
C. From the Product Family list, select the third-party node family (Accedian Nodes/Ciena Nodes).
D. Click Select to open the Select Image dialog box.
E. From the Select Image dialog box, select the applicable software upgrade image and click Select.
Note: An Accedian software upgrade image has an .afl file extension, the Ciena Packet Networking
(PN) software image has a .zip file extention.
Note: Use the software repository function to upload software upgrade images. For detailed
information, see Uploading a Software Upgrade Image starting on page 103 (Software Repository
tab).
F. (Optional) Configure a Start Time for this task other than the current time by clicking Select Time
and specifying a date and time. If you do not configure a future time, the task executes as soon as
you click Enable (see step 5).
Note: The system bases the date and time selected on the server date and time.
G. From the Operations list, select the type of upgrade operation.
Accedian Nodes: Accedian devices with 6.4 and lower firmware only support the Download
upgrade option, plus Revert. Accedian nodes with 7.1 firmware and higher support three upgrade
options (Download, Activate, Download and Activate) plus Revert.
Ciena PN Devices: For Ciena PN devices, you can select three upgrade options (Download,
Activate, Download and Activate) plus Revert.
H. From the Operation Mode list, select the mode, Process NE(s) in Sequence or Process NE(s) in
Parallel.
I. From the Max. Concurrent Downloads list, select the maximum number of nodes allowed for
concurrent downloads of the software image. The default setting is 5.
J. Note: The Use Standby Partition option is not applicable for Accedian and Ciena PN devices.
K. Click Targets to open the Select Node for Upgrade dialog box and continue with step 4.
Step Procedure
4 In the Select Nodes for Upgrade dialog box, do the following:
A. Locate the node(s) to add to the task using the following methods:
Optionally customize the node list, as follows:
• Change the column display: Drag and drop a column title into a new position, or, at the top,
right of the dialog box, click the Settings icon , and select Manage Columns. In the Select
B. Select the nodes to include in the task by selecting (checking) the check box for each node.
To select all nodes that display in the list, select (check) the check box located to the left of the
search box.
C. Click OK.
The upgrade task with the target network entities display in the Defined Upgrades tree panel.
5 Click Apply to save the task and schedule the task to start according to the start time.
Note: To remove a node from the list of target nodes before the upgrade task
begins, do one of the following:
• In the Software Management & Packaging dialog box tree panel, select the
upgrade task, and click Targets to open the Node Selection dialog box. Clear
the check box for each node you are removing, and then click OK to save the
change.
—or—
• Expand the upgrade task and select the node in the tree panel. Click Remove
Target, and then click Yes to confirm the action.
Enabling a Software Upgrade Task

If you did not configure a start time for the Upgrade task in the Defining a Software Upgrade Task
procedure, you can execute the defined task immediately using this procedure.
Step Procedure
2 In the Define Upgrade tab, select the software upgrade task to execute.
3 Click the Enable button.
The next table describes each read-only task State field.
Monitoring a Software Upgrade

Planet Operate allows you to monitor the progress of each stage of an equipment upgrade.
To monitor the progress of each phase of the equipment upgrade, in the Software Management &
Packaging dialog box, click the Upgrade History tab.
Figure 18: Upgrade History Tab
During each stage, Planet Operate displays progress and current status with start and completion
times for each. During the Prepare stage, Planet Operate provides slot-specific progress indication.
Note: If any stage fails for a node or a slot, you can enable the upgrade task again and
the system will repeat the operation only at nodes/slots where it previously failed.
Planet Operate Event Log

You can also monitor upgrade activity using the Planet Operate Event Log. To display the Event Log,
from the main menu select Administration > View Event Log.
Figure 19: Event Log in Planet Operate
Aborting a Software Upgrade Task

In the Software Management & Packaging dialog box, click the Define Upgrade tab. To abort an
upgrade task during the Prepare phase, click the Abort button.
The Abort operation may stop the upgrade task during the Activation phase if the activation has not
been engaged. Because the Activation phase is short, the Abort operation may miss the window to
stop the process.
Additional Upgrade Options

This section provides information and instructions for copying, deleting, and disabling a software
upgrade task. Additional topics include instructions for reverting to a previous version of software,
accessing upgrade and image history, and instructions to view, upload, or remove a software
upgrade image. Lastly, this section describes the Restore Log for viewing restore log results and
removing unwanted entries.
Copying a Software Update Task

Use the copy function to create a copy of a software upgrade task.
Note: A failed software upgrade task cannot be re-run. However, you can make a copy
of a software upgrade task and schedule the copy for operation.
To copy a software update task, follow this procedure.
Step Procedure
2 In the Define Upgrade tab, select the software upgrade task to copy.
3 Click Copy.
4 Update the parameters in the Task Configuration area as needed and click Enable.
Note: Click Apply to update the parameters in the Task Configuration area.
Deleting a Software Upgrade Task

Use the delete upgrade function to delete a software upgrade task.
To delete a software update task, follow this procedure.
Step Procedure
2 In the Define Upgrade tab, select (click) the software upgrade task to delete.
3 Click Delete Upgrade.
4 In the confirmation needed dialog box, click Yes.
Disabling a Software Upgrade Task

Use the disable function to de-activate an enabled software upgrade task.
To disable a software update task, follow this procedure.
Step Procedure
2 In the Define Upgrade tab, select (click) the software upgrade task to disable.
3 Click Disable.
Reverting to a Previous Software Version

The NE Software Information tab displays the NE current, revert, and upgrade releases. This tab
provides the ability to revert to a previous version of the software.
To activate a previous version of the software, follow this procedure.
Step Procedure
Click the NE Software Information tab.
In the panel on the left, select (click) the network element to display the software version information in
the panel on the right. Verify that a revert package is available.
2 Important! — Selecting revert causes the network element to activate a previous software version on
all line cards. Connectivity with the network element will be interrupted for a short time period.
To revert to the previous version of the software, click Revert.
In the confirmation dialog box, click Yes to start the revert operation.
Upgrade History
Use the upgrade history function to view a history of the software upgrade tasks.
To view the upgrade history, follow this procedure.
Step Procedure
2 Click the Upgrade History tab.
3 In the left-most panel, select the software upgrade task to view.
Image History
Use the image history function to view the history of the software upgrade images.
To view the software image history, follow this procedure.
Step Procedure
2 Click the Image History tab.
3 In the left-side panel, select a software image file.

The image history displays in the right-side panel.
Note: Click Refresh to update the display.
Restore Log
Use the Restore Log tab to view restore log results and remove unwanted entries.
To display the Restore Log tab, remove the node and result entries from the log, follow this
procedure.
Step Procedure
dialog box.
2 Click the Restore Log tab.
To remove NE entries, select the Restored NE in the Restored NEs panel and click the Delete NE
Entry button.
To remove a results entry, select the intended row in the results panel and click the Remove
Entries button.
Note: You can select more than one result entry from the list by using the Ctrl key. Hold down the Ctrl
while selecting each individual result. You can select a range of consecutive result entries by using the
Shift key. Click the first result that you want to include. Hold down the Shift key and click the last result
in the range of result entries to include.
3 Click Close.
Upgrade Planet Operate – 17.08

For details on upgrading Planet Operate from a major release to release 17.08, see the 17.08 Planet
Operate Release Notes available online in the Ciena technical documentation portal.
Node Cut In and Cut Out
This section describes the following node insertion and removal processes supported by Planet
Operate:
• Convert an express node to an add/drop node in a network ERP major ring or sub-ring. See
Converting a Z-Series Express Node to an Add/Drop Node starting on page 131.
• Cut in (node insertion) to and cut out (node removal) from an existing, operational optical
link on a G.8032v2 client ERP sub-ring for various models of Accedian nodes. See Accedian
Node Cut In and Cut Out on a G.8032v2 Client ERP Sub-Ring starting on page 135.
• Cut in (node insertion) and cut out (node removal) of a Z-Series node (Z77, Z33, Z22) from an
existing, operational optical link while maintaining continuity for existing TESIs and ODU2
trails. See Inserting a Z-Series Node into an Operational Optical Link starting on page
143.
• Cut in (insertion) and cut out (removal) of a Ciena Packet Networking device to and from an
existing operational link on a multi-hop linear network topology. See Inserting and
Removing a Ciena Packet Networking Device in a Multi-Hop Linear Topology starting on
page 160.
After initiating the Planet Operate node insertion process, the interface guides you through the
workflow process. The process also runs as a background job accessible to any properly credentialed
user logged in to Planet Operate.
In This Chapter
Z-Series Node Cut In and Cut Out on a Network ERP Major Ring or
Sub-Ring ....................................................................................................125
Converting a Z-Series Express Node to an Add/Drop Node ..............131
Accedian Node Cut In and Cut Out on a G.8032v2 Client ERP Sub-Ring
....................................................................................................................135
Inserting a Z-Series Node into an Operational Optical Link ..............143
Removing a Z-Series Node from an Operational Optical Link ...........154
Inserting and Removing a Ciena Packet Networking Device .............160
Z-Series Node Cut In and Cut Out on a Network

ERP Major Ring or Sub-Ring
Planet Operate supports the cut in (node insertion) to and cut out (node removal) from an existing,
operational optical link on a G.8032v2 network (NNI) major ring or sub-ring for Z-Series nodes.
Once you initiate the Planet Operate node cut-in/cut-out process, it runs as a background job
accessible to any properly credentialed user logged in to Planet Operate. To open the background
job, right-click the appropriate row of the Background Jobs tab and select Open Job.
Before Disconnecting Fibers on the Ring
Important! — Start the Planet Operate cut-in/cut-out process as described in this

section before physically disconnecting fibers on the ERP group.
The first phase of the node cut-in/cut-out process verifies the ring state. If the ring state is not Idle,
do not disconnect fibers until the ring state is returned to Idle (Idle = not in protection mode; the RPL
is blocked as in normal operation) and resolve the issue(s) that caused the protection switch on the
ring before proceeding. If a protection switch has already occurred on the ring, disconnecting fibers
to insert a node may bring down traffic on the ring.
Note: Disconnecting fibers on a G.8032 ring in the Idle state results in a
< 50 ms switchover to the protection path. Disconnecting fibers on a G.8032
ring in a non-Idle state may affect traffic.
Node Cut-In
You can cut in a node that is already under Planet Operate-management, or you can add a node to
the network and cut it in to an existing optical link in the same operation.
For node cut-in, verify the following on the node to be cut in to the ring:
• Planet Operate only supports node cut-in operations when the shelf-level PSW Node
Personality is set to PBB-TE. Do not use this procedure if the PSW Node Personality is set to
MPLS-TP.
• The CyOS version running on the new node must match the CyOS version running on the
nodes in the ring (for example, all must be running CyOS 6.0.01).
• For an NNI major ring, the node must be running CyOS 5.0 or higher.
• For an NNI sub-ring, this feature requires Planet Operate 15.02 or higher.
• To cut in a node that is already under Planet Operate management, the node must be
configured as a standalone shelf with no existing optical links.
• The node has been configured for ring operation. For details, refer to the "Ethernet Ring
Protection (ERP)" section of the Packet Switching User Guide.
• The ERP Frame type is set for compatibility with the other nodes on the existing ring.
To add a node to an existing link on a G.8032v2 ring, follow this procedure.
Step Procedure
1 In the Network view tab with the fiber layer selected, click the optical link to receive the new node;
right-click the trail and select Node Cut-In... to display the Cut-In tab.
— or —
From the Link Connections tool tab, right-click the intended link row and select Node Cut-In... to display
the Cut-In tab.
2 If Planet Operate detects any Discovered services on the selected link, the Cut-In tab displays the
requirement to promote the services to User Provisioned before continuing.
To continue, click Promote.
Step Procedure
• To add a new node to Planet Operate management and cut in to this link simultaneously, go to
step 4.
— or —
• If the node to cut in is already under Planet Operate management, go to step 5.
4 To cut in a node already under Planet Operate management, do the following:
A. In the Select Node window, click the Select radio button.
B. Select the node from the Select Existing list.
Note: Only nodes configured as standalone shelves display in the list.
C. Click Set Node.
D. Go to step 6.
5 To cut in and create a new node simultaneously, do the following:
A. In the Cut-In tab, click the Create radio button.

B. Enter a user label and optional description.
C. From the Product Name list, select the node type.
D. In the DCN IP Address text box, enter the hostname or IP address for the node.
Note: The default DCN Port, 8888, displays. Do not change from the default 8888 port number
unless the Z-Series node is behind a NAT router. For more information, refer to the topic, "Create a
New Node Behind a NAT Router," in the Planet Operate: Nodes, Modules, and Transport Resources
Guide.
E. Click Set Node.
Once node discovery and network synchronization are complete and the node is reachable, Planet
Operate auto-discovers the links and the screen automatically advances to the next step.
6 Click Test Connection to verify that the node can be reached.
If the test fails, click the Change Node Configuration check box to review and update the node
settings.
Step Procedure
7 At the software validation window, click Confirm.
Planet Operate verifies that the CyOS version running on the cut-in node matches the version running
on the ring.
8 The Cut-In process pauses to enable invoking an optional traffic switch. Do one of the following:
• If the link is the ring protection link (RPL), a traffic switch is not required; click Continue.
— or —
• If the link is not the RPL, you can optionally click Switch > to perform a Forced traffic switch on
the ring, and wait for the traffic switch to complete. Performing a forced switch ensures that
adding the node does not affect traffic.
9 Perform the physical cut-in. Disconnect the existing fibers and reconnect the fiber in the new
configuration. Do not proceed with the cut-in operation until the new fibers are in place and the node is
communicating with Planet Operate.
10 In the Cut-In tab confirmation screen, click Update Services.
Planet Operate updates (auto-discovers) the trails in the 3D Network view tab and in the Trails and Link
Connections tabs. If the ring is fault-free, the ring state returns to Idle when the Wait-to-Restore (WTR)
timer expires. Optionally, click Clear to clear the WTR timer.
Click Close to close the Cut-In tab.
Step Procedure
11 Click the Network view tab to verify that the ERP group now includes the new node.
If required, synchronize the server and refresh the Network view tab.
12 Click Close to close the Cut-In tab.
Node Cut-Out
This section describes the procedure to remove a node from an existing, operational G.8032v2
network ERP major ring or sub-ring without affecting live traffic on the ring.
Note the following restrictions:
• For an NNI major ring, this procedure requires a minimum of three nodes in the ring.
• For an NNI sub-ring, this procedure requires a minimum of two non-interconnection nodes.
You cannot use this tool to cut out an interconnection node.
• This procedure assumes that only one optical link connects the intended cut-out node to
each of its adjacent nodes. If more than one optical link exists on either end of the intended
cut-out, the procedure will fail.
• Before using this procedure, you must tear down (remove) any network services that:
 terminate on the intended cut-out node
 use the intended cut-out node for service aggregation to the core network
Note: Planet Operate recognizes an "Unplanned Cutout" when a port or node

fails. For an unplanned cutout, the manual switch is not required since the ring
protection will have already switched traffic, and Planet Operate allows the
cut-out to proceed even if the ring is not Idle. For an unplanned cutout, the
node must be unreachable; if only signal or port failure is present, remove the
node from Planet Operate management to continue.
To remove a node from an existing optical link on a G.8032 network major ring or sub-ring, follow
this procedure.
Step Procedure
1 In the Network view tab with the fiber layer selected, right-click the node that you intend to remove and
select Cutout Node... to display the Cut-Out tab.
— or —
From the Nodes tool tab, right-click the node row and select Cutout Node... to display the Cut-Out tab.
2 If Planet Operate detects any Discovered services terminating on the selected node, the Cut-Out tab
displays the requirement to promote the services to User Provisioned before continuing.
To continue, click Promote.
3 The Cut-Out process pauses to enable invoking an optional traffic switch. Do one of the following:
• For an unplanned cut out, a traffic switch is not required since the ring protection will have
already switched traffic; click Continue.
— or —
• For a planned cut out of a node that is adjacent to the ring protection link (RPL), a traffic switch
is not required; click Continue.
— or —
• If neither of the above two conditions applies, you can optionally click Switch > to perform a
Forced traffic switch on the ring. Performing a switch ensures that removing the node does not
affect traffic.
4 Disconnect the existing fibers to the node and reconnect the fiber in the new configuration.
Note: The node must be unreachable to proceed. If the node is not in-band managed, disconnect the
management connection to proceed.
5 When Planet Operate confirms the fiber connections, click Update Services > to advance to the next
state.
Step Procedure
6 Planet Operate updates the trails in the 3D Network view tab and in the Trails and Link Connections
tab.
The ring remains in the Pending state until the WTR timer times out. Optionally click Clear to expire the
WTR timer.
If the ring is fault-free, it returns to the Idle state.
7 In the Network view tab, verify that the node you cut out is no longer part of the ring.
If required, synchronize the server and refresh the Network view tab.
8 Click Close to close the Cut-Out tab.
Converting a Z-Series Express Node to an

Add/Drop Node
To convert an express node (a node hosting only TESI express connections) into an add/drop node in
a G.8032 network ERP major ring or sub-ring, use the procedure in this section.
Support for this operation includes both PME-based and PSW-based rings.
During this operation, Planet Operate does the following tasks automatically:
• Updates TESI legs on the new node:
 Creates TESI objects as required on the new node
 Creates new TESI legs for the ERP, using the same B-VID as the existing TESI legs
 Removes the previous TESI leg that is now obsolete
 Updates ERP routes to include the new node
• Updates each packet service on the ERP:
 Adds new node data
 Expresses services through the new node
 Creates flow domains and flow points on the new node as required for existing services
on the ERP
At the completion of the node conversion operation, all existing network services on the ERP transit
the new node. You can add this node to an existing service (EPL, EVPL, or multipoint E-LAN in the
network services interface, or E-LAN or E-VLAN in the EMS panels) by modifying the service to include
this node as a site.
If you add the node on the ring protection link (RPL), Planet Operate maintains the original RPL
owner; the new TESI connected to the RPL owner becomes the RPL.
Requirements
Note the following requirements for this feature:
• Supported on both network (NNI) major rings and sub-rings.
• All nodes in the ERP ring must be running CyOS 5.0 or higher.
• All nodes in the ERP ring must be running the same G.8032 version (v1 or v2).
• The node to add must be a part of this ERP ring only. Do not use this procedure if the node
participates in other rings as express or add/drop.
• The ERP and all participating TESIs and affected packet services must be:
 In the Provisioned state
 User-Provisioned (not Discovered)
 Free of all discrepancies
• Once you begin the operation, Ciena strongly recommends that you complete it; there is no
revert option.
Initial State
The next drawing shows the initial state of the network. Four nodes are connected in a fiber ring. A
network ERP service connects Nodes A, B, and C, which are all add/drop nodes in the ERP service.
Node D is an express node with no add/drop of the ERP service. Use the procedure in this section to
convert Node D to an add/drop node in the ERP.
Figure 20: Nodes Connecting a Fiber Ring
The Trails tab shows the three TESI legs of the ERP. The yellow highlight indicates the leg into which
this procedure adds the node.
Procedure
To convert an express node to a node able to host add/drop services, follow this procedure.
Step Procedure
1 Right-click the ERP trail into which you want to add this node for add/drop services and select Add node
to ERP….
The Add Node workflow panel opens.

2 From the Select node list, select the node to add, and then click Set Node.
Step Procedure
3 When the operation completes, click Close.
Final State
The resulting Network view shows that Node D is part of the NNI ERP.
Figure 21: Ethernet Ring Protection
The Trails tab shows that Planet Operate removed leg 2 that connected Nodes A and C of the ERP
and replaced it with leg 2-1 connecting Nodes C and D, and with leg 2-2 connecting Nodes A and D.
Accedian Node Cut In and Cut Out on a

G.8032v2 Client ERP Sub-Ring
Planet Operate supports the cut in (node insertion) to and cut out (node removal) from an existing,
operational optical link on a G.8032v2 ring for the following nodes types:
• Accedian MetroNID GT
• Accedian MetroNID GT-S
• Accedian MetroNODE LT-S
• Accedian MetroNID GX
• Accedian MetroNID GX-S
• All Ciena Packet Networking (PN) devices
Note: To insert or remove vendor nodes other than those listed above (including Z-Series nodes),
you must tear down and rebuild the ERP.
Before Disconnecting Fibers on the Ring
Important! — Start the Planet Operate cut-in/cut-out process as described in this section
before physically disconnecting fibers on the ERP group.
The first phase of the node cut-in/cut-out process verifies the ring state. If the ring state is not Idle,
do not disconnect fibers until the ring state is returned to Idle (Idle = not in protection mode; the RPL
is blocked as in normal operation). You must resolve the issue(s) that caused the protection switch
on the ring before proceeding. If a protection switch has already occurred on the ring, disconnecting
fibers to insert a node may bring down traffic on the ring.
Note: Disconnecting fibers on a G.8032 ring in the Idle state results in a
< 50 ms switchover to the protection path. Disconnecting fibers on a G.8032
ring in a non-Idle state may affect traffic. PME-412 and PME-216i Ethernet
protection switching times can depend on the number of rings and MACs.
Protection switching can exceed 50 ms with multiple rings and large number
of MACs.
Node Cut-In
For node cut-in, verify the following on the node to be cut in to the ring:
• The node is running the correct software version.
• The node is configured for ring operation (refer to the Accedian documentation).
• The node APS Channel VLAN ID and the ERP Frame type are both set to be compatible with
the other nodes on the existing ring.
• Make sure Ciena PN devices/nodes were created in Planet Operate using the correct naming
convention before inserting in a client ERP group.
 LR-1, for the first logical ring of a client ERP
 VR-1, for the first virtual ring of a client ERP
Note: This is a requirement for successful client ERP protection switch performance.
Important! — If loop detection was previously enabled on the NNI sub-ring via A-to-Z
provisioning, then you must disable the loop detection feature prior to starting the node
cut-in procedure. The cut-in process will fail if loop detection is enabled.
See Packet Switching User Guide "Modifying Network ERP Description and Service
Specifics Settings" to disable the loop detection feature.
The following procedure refers to cut-in of the node GTS832 to the span of the ERP labeled
GTS831_ERP-15-Thurston.
To add a node to an existing optical link on a G.8032v2 ring, follow this procedure.
Step Procedure
1 In the Network view fiber layer, select the optical link to receive the new node; right-click the trail and
select Node Cut-In... to display the Cut-In panel.
— or —
From the Link Connections tab, right-click the link row and select Node Cut-In... to display the
Cut-In panel.
2 Planet Operate verifies that the ring is in the Idle state (not in protection mode). The node cut-in
process will not advance unless the ring is in the Idle state.
Click Switch to switch traffic on the ring so that adding the node does not affect traffic.
Note: If the link is the ring protection link, the traffic switch is not required; click Continue.
Step Procedure
3 When the traffic switch is complete, perform the physical cut-in. Disconnect the existing fibers and
reconnect the fiber in the new configuration. You cannot proceed with the cut-in operation until the
new fibers are in place and the node is communicating with Planet Operate.
4 When the new node is connected in the ring, resume the cut-in process as follows:
• To add a new node to Planet Operate management and cut in to this optical link
simultaneously, go to step 6.
A. Select the node from the Select Existing list.
B. Click Set Node.
C. Go to step 7.
Step Procedure
A. Select the Create New Node check box.
B. Select the Product name from the list.
C. Enter the hostname or IP address for the node.
D. Click Set Node.
Once node discovery and network synchronization are complete and the node is reachable, the GUI
automatically advances to the next step.
Step Procedure
7 Select the ports and designate the new trail names to connect to the cut-in node.
Important! — Ensure that the ports you select in this step correspond to the actual physical fiber
configuration in the network. Planet Operate cannot verify that the ports you select are correct.
Click Update Services.

At the confirmation dialog box, click Yes to proceed.
Step Procedure
8 Planet Operate updates the trails in the 3D network view and in the Trails and Link Connections tabs. If
there are no other faults on the ring, the ring state returns to Idle when the Wait-to-Restore timer
expires.
If desired, click Clear to clear the WTR timer.
Click Refresh to refresh the panel containing the timer information, or click Close to close the Cut-In
panel.
9 Click the Network tab to verify that the ERP group now includes the new node.
If required, resync the server and refresh the Network view.
10 Click Close to close the Cut-in panel.
Node Cut-Out
This section describes the procedure to remove a node from an existing, operational G.8032v2 ring
without affecting live traffic on the ring.
Note: Planet Operate recognizes an "Unplanned Cutout" when a port or node
fails. For an unplanned cutout, the manual switch is not required since the ring
protection will have already switched traffic, and Planet Operate allows the
cut-out to proceed even if the ring is not Idle. For an unplanned cutout, the
node must be unreachable; if only signal or port failure is present, remove the
node from Planet Operate management to continue.
Important! — If loop detection was previously enabled on the NNI main ring or sub-ring
via A-to-Z provisioning, then you must disable the loop detection feature prior to
starting the node cut-out procedure. When a node is cut out from an NNI main ring or
sub-ring with the loop detection option enabled, the system does not delete the
loop-detect flow domains from the cut-out node.
See Packet Switching User Guide Modifying Network ERP Description and Service Specifics
Settings to disable the loop detection feature.
The following procedure refers to removal of the node labeled GTS832_ERP-15 from the ring.
To remove a node from an existing optical link on a G.8032 ring, follow this procedure.
Step Procedure
1 In the Network view tab, select the node to remove; right-click the node and select Cutout Node... to
display the Cut-Out panel.
2 Planet Operate verifies that the ring is in the Idle state (not in protection mode). The node cut-out
process will not advance unless the ring is in the Idle state (except in the case of an unplanned cut out;
refer to the note above before procedure).
Once the Idle state is verified for the ring, click Switch > to switch traffic on the ring so that removing the
node does not affect traffic.
Note: if the node is adjacent to the ring protection link, the traffic switch is not required; click Continue.
3 When the traffic switch is complete, disconnect the existing fibers to the node and reconnect the fiber in
the new configuration.
Step Procedure
4 When the new fiber connections are in place, specify a new trail name, and click Apply > to advance to
the next state.
5 Planet Operate updates the trails in the 3D network view and in the Trails and Link Connections tabs.
The ring remains in the Pending state until the WTR timer times out. If desired, click Clear to expire the
WTR timer.
6 If there are no faults on the ring, it returns to the Idle state.

Click the Network tab to verify that the node you cut out is no longer part of the ring.
7 Click Close to close the Cut-Out panel.
Note: If you are going to reuse the cut-out node, then you must
re-commission the node prior to reuse, to remove all provisioning.
Inserting a Z-Series Node into an Operational

Optical Link
Planet Operate supports the cut in (node insertion) of a Z-Series node (Z77, Z33, Z22) to an existing,
operational optical link. Node insertion provides continuity for existing TESIs, ODU2, and ODU4 trails.
Node insertion supports TESI express connections only: you cannot add or drop services to/from the
new node during the node insertion process (you can provision add/drop services to/from the new
node in a separate, subsequent operation).
You can perform Z-Series node insertion on the following optical link types:
• LAD <—> LAD
• WSS <—> WSS
• PME/PSW <—> PME/PSW
• PSW-100G <—> PSW-100G
Once you initiate the Planet Operate node insertion process, a tab opens that guides you through
the workflow. The process also runs as a background job accessible to any properly credentialed
user logged in to Planet Operate. To open the background job, right-click the appropriate row of the
Background Jobs tab and select Open Job.
Important! — Node cut-in affects traffic on all services on the optical link receiving the
new node. To see which services exist on this link, right-click the link and select Show
Affected Services. Right-click a row in the Affected Services table to display options to
navigate to the service.
Important! — After creation of an ODU2/ODU4 trail as part of the node insertion process,
promoting the trail to User Provisioned results in discrepancies on the trail related to the
User Label and Owner fields.
Workaround: Clear the discrepancies on the ODU2/ODU4 trail using the bulk repair process
or by using the NMS Workflows tool to change the Owner and User Label.
Requirements
Note the following requirements for successful Z-Series node insertion:
• The new node to cut in and the A-End and Z-End nodes must all be running the correct
software version. Software on all three nodes must match to the minor release level (first two
decimal places; for example, 5.0); it is not necessary to have the same extended release level
(third decimal place; for example, 5.0.01).
• All services on the span to receive the node insertion should be in a stable state with no
discrepancies. Fix any existing discrepancies before proceeding.
• All services on the span to receive the node insertion must not be in the Routed state. Delete
or de-allocate all services on the span in a Routed state.
• All services on the link must be User-Provisioned rather than Discovered.
To identify services with discrepancies or in the Routed state, right-click the span in the Network view
and select Show Affected Services. The service list that displays indicates discrepancies and service
state. Right-click the intended row in the Affected Services table to display options to navigate to the
service.
Limitations
Note the following limitations for this feature:
• Planet Operate only supports node cut-in operations when the shelf-level PSW Node
Personality is set to PBB-TE.
• You can insert a node only into an ODU2 span directly connecting two PME/PSW modules. Do
not use this procedure if the ODU2 span includes LME, DTM, or TSW modules.
Note: This limitation is not applicable to the PSW-100G line card. The PSW-100G line card
does not support an ODU2 span.
• Only TESI expresses, WSS expresses, and ODU2 terminations will be built on the node to
insert.
• You can insert a node only into an ODU4 span directly connecting two PSW-100G modules.
Do not use this procedure if the ODU4 span includes LAD and WSS modules.
Prepare for Node Insertion

You can insert a node that is managed either in-band or out-of-band.
You can insert a node that is already under Planet Operate management, or you can create a new
node in the Planet Operate network and cut it in to an existing optical link or trail in the same
operation.
Before you begin node insertion, follow this procedure.
Step Procedure
1 Analyze your network to identify the following:
• Span type (LAD-LAD, PME/PSW-PME/PSW, PSW-100G/PSW-100G or WSS-WSS).
• Software version on all three nodes (A-End and Z-End nodes of the current optical link, and new
node to cut in).
• Ports to be used on all three nodes.
• Physical and logical fiber cross-connects required on the new node to be cut in; for example,
LAD-PME/PSW or AWG-WSS-PME/PSW fiber patches and logical cross-connections.
Step Procedure
2 Ensure the following:
• For a PME/PSW-PME/PSW link, you must enable topology discovery on the PME/PSW ports of the
new node being cut in. Refer to PME-412 and PME-216, PSW-10G10, PSW-10G20, PSW-618, and
PSW-100G in the Transport Resources section of the Planet Operate: Nodes, Modules, and
Transport Resources user guide for procedures to enable topology discovery.
• No user-initiated changes (for example, creating/deleting services) are permitted in the affected
network during the node cut-in operation.
• No maintenance activities (for example, card replacement) are permitted on the A-End and Z-End
nodes of the optical link receiving the new node.
• The new node to cut in and the A-End and Z-End nodes must all be running the correct software
version. Software on all three nodes must match to the minor release level (first two decimal
places; for example, 5.0); it is not necessary to have the same extended release level (third
decimal place; for example, 5.0.01).
• The new node cannot have inter-node links; it must be a standalone node.
3 Verify that all applicable services on the intended optical link show Trail Type = User-Provisioned
(for example, ODU2, ODU4, TESI, ERP; note that not all services can be User-Provisioned).
A. Right-click the intended optical span and select Show Affected Services.
B. In the table that displays, right-click the services to promote and select Workflows > Bulk Promote
to User-Managed.
C. Follow the prompts in the Task Panel to complete the promotion. As a result, the service displays the
Trail Type of User-Provisioned.
D. Repeat for other applicable services on the span.
Step Procedure
4 At the new node, connect the required physical fiber patches, if any, for your application (for example,
LAD-PME/PSW or AWG-WSS-PME/PSW fiber patches). During the Planet Operate node cut-in procedure,
you will configure these same connections in the EMS. Refer to step 8 in the "Node Cut-In" procedure.
Before Disconnecting Fibers
Important! — Start the Planet Operate cut-in process as described in this section before
physically disconnecting fibers on the optical link.
Important! — Once you begin the node cut-in procedure, you must complete it; there is no
option to abort, cancel, or revert.
Verify that all services on the span to receive the new node are in a stable, non-alarmed state with no
trail discrepancies. During the cut-in process, do not perform any other configuration or
maintenance activities in the network.
Node Cut-In
The following procedure, as an example, refers to cut-in of the in-band managed node ksimC to the
optical link between ksimA and ksimB.
Figure 22: In-Band Cut-In
To cut in a node to an existing optical link or trail, follow this procedure.
Step Procedure
1 Before beginning the Planet Operate node cut-in procedure, install the physical fiber cross-connects
required (if any) on the new node. For example, you may need fiber patches between LAD and PME/PSW
modules, or between AWG-WSS-PME/PSW modules.
Once these physical fibers are in place, begin the Planet Operate node cut-in procedure.
2 In the Network view fiber layer, select the intended optical link or trail to receive the new node; right-click
the link or trail and select Node Cut-In... to display the Cut-In tab.
— or —
From the Link Connections tab or Trails tab, right-click the intended optical link/trail row and select Node
Cut-In... to display the Cut-In tab.
3 Planet Operate finds and displays services on the link that are in the Discovered state.
Note: This screen does not display all services on the link, but only those in the Discovered state.
Since the node insertion process supports only user-provisioned services, you must promote Discovered
services to proceed.
Click Promote to move these services to the User-Provisioned state.
Note: If all services on this link are already in the User-Provisioned state, Planet Operate does not
display “Found the following discovered services” screen. In this case, go to step 4.
4 To proceed:
• To add a new node to Planet Operate management and cut in to this optical link or trail
Step Procedure
A. Click the Select radio button.
B. Select the intended node from the Existing node list.
Note: Planet Operate displays only reachable nodes that have no inter-node links.
C. Click Set Node.
D. Skip to step 7.

A. Select the Create radio button.
B. In the User Label field, enter a label to identify this node.
C. From the Product Name list, select the node type.
D. In the DCN IP address field, enter the IP address for the node.
E. In the DCN port field, enter the port to use for communications between the node and Planet
Operate.
F. Click Set Node.
Once node discovery and network synchronization are complete and the node is reachable, the Planet
Operate interface automatically advances to the next step.
Step Procedure
7 Warning! — This step affects all services on the link. If you have a configured protection path, traffic will
switch to the protect path in less than 50 ms. If there is no protection path, traffic will not flow until the
cut-in procedure is complete. PME-412 and PME-216i Ethernet protection switching times can depend on
the number of rings and MACs. Protection switching can exceed 50 ms with multiple rings and large
number of MACs.
An in-band managed node is not reachable until you make the new fiber connections.
At the new physical node to cut in, connect the physical fibers from the original A-End and Z-End nodes
to the proper ports on the new node. Then click Test Connection.
Once the node is reachable, Planet Operate performs other checks to ensure that the node is in sync
and running the proper software version.
8 Envision the final state of the new physical and logical cross-connections on the new node required for
your application. Refer to step 3 in the 'Prepare for Node Cut In' procedure.
Go to the EMS cross-connect tab for the modules on the new node (including AWG modules, if required)
involved in the new spans and configure the optical cross-connects via the EMS to match the physical
and logical cross-connects required.
Step Procedure
9 Return to the Cut-In tab.
Planet Operate displays the configured cross-connect and transceiver wavelengths.
Note: If your application uses adjacent PME/PSW line cards on the new node for a direct
PME/PSW-to-PME/PSW connection with no front fiber patch, the Planet Operate cross-connect fields and
transceiver wavelength fields do not display. Instead, Planet Operate displays the message "No
cross-connection information."
Important! — Ensure that the cross-connects and wavelength displayed in this step correspond to the
actual physical and logical cross-connections and transceiver wavelength on the new node.
If you need to change fibers at the node or change the cross-connect provisioning, do so now and then
click Rediscover.
When the information displayed matches the expected configuration, click Confirm.
For sample screens showing WSS-PME/PSW and WSS express configurations, refer to Sample
Configurations below.
Step Procedure
10 Important! — Ensure that the ports displayed in this step correspond to the actual physical fiber
configuration in the network. If they do not, change the physical fibers as required.
Once you have confirmed the node configuration, Planet Operate discovers the new optical links that
include the new node. Planet Operate displays the ports on the new node that face the A-End and Z-End
of the original link.
Click Update Services.
Planet Operate updates the trails in the 3D network view and in the Trails and Link Connections tabs.
This includes configuring the new node information on all the ODU2, ODU4, TESI, and ERP legs on the
link; it expresses these services through the new node that is cut in, creates TESI express connections on
the new node, deletes old optical and ODU2/ODU4 trails as needed, and creates new optical
ODU2/ODU4 trails as needed.
Step Procedure
11 Click the Network view tab to verify that the optical span now includes the new node.
Verify that traffic is flowing as expected. If desired, check the Trail Analyzer for updated TESI-based
services running through the cut-in node.
12 Click Close to close the Cut-In tab.
Converting an Express Node to an Add/Drop Node

Once you have added the node to the optical link, you can then convert the node from an
express-only node to an add/drop node that is part of an ERP service. Refer to Adding a Z-Series
Node to an NNI ERP starting on page 131.
Sample Configurations
The next graphic shows the screen in step 9 above with a sample WSS-PME/PSW line card
configuration.
The next graphic shows the screen in step 9 above with a sample WSS express card configuration.
Removing a Z-Series Node from an Operational

Optical Link
Planet Operate supports the cut out (node removal) of a Z-Series node (Z77, Z33, Z22) from an
existing, operational optical link. Node removal provides continuity for existing TESIs and ODU2
trails.
You can perform Z-Series node removal on the following optical link types:
• LAD <—> LAD
• WSS <—> WSS
• PME <—> PME
• PSW <—> PSW
Once you initiate the Planet Operate node removal process, a tab opens that guides you through the
workflow. The process also runs as a background job accessible to any properly credentialed user
logged in to Planet Operate. To open the background job, right-click the appropriate row of the
Background Jobs tab and select Open Job.
Important! — Node cut out affects traffic on all services on the optical links of the node to
remove. To see existing services exist on these links, right-click each link and select Show
Affected Services. Right-click the intended row in the Affected Services table to display
options to navigate to the service.
Requirements
Note the following requirements for successful Z-Series node removal:
• All services on the node to remove must be in a stable state with no discrepancies. Fix any
existing discrepancies before proceeding.
• Services on the node to remove must NOT be in the Routed state. Delete or de-allocate all
services on the span in a Routed state.
• Services on the node to remove must be User-Provisioned rather than Discovered (Trail Type
attribute).
To identify services with discrepancies or in the Routed state, right-click the intended span in the
Network view tab and select Show Affected Services. The service list that displays indicates
discrepancies and service state. Right-click a row in the Affected Services table to display options to
navigate to the service.
Limitations
Note the following limitations for this feature:
• Planet Operate only supports node cut-out operations when the shelf-level PSW Node
Personality is set to PBB-TE.
• The node to remove cannot add or drop network services.
• The node to remove cannot express network services (the node cannot be an ERP add/drop
node).
• The node to remove cannot terminate TESIs or ERP legs.
• You must re-use the same ports on the remaining nodes that formerly faced the node to be
removed. This implies that wavelengths on both links of the span must match.
• The node to remove can have only two optical links: one to each adjacent node.
• PME-based services only are supported. Do not use this procedure if the span includes LME,
DTM, PSW, or TSW-based services.
• The number of ODU2 trails on the spans on both sides of the node to remove must be
identical.
• The wavelength of the ODU2 trails on both side of the node to remove must be identical.
Prepare for Node Removal

Before you begin the node removal process, verify that all applicable services on the node show Trail
Type = User-Provisioned (for example, Layer Rate = ODU2, TESI, ERP; note that not all service types
can be User-Provisioned.
To ensure that all services on the node are User-Provisioned, follow this procedure for each optical
span on the node.
Step Procedure
1 Right-click the intended optical span and select Show Affected Services.
2 In the table that displays, right-click the services to promote and select
Workflows > Bulk Promote to User-Managed.
Step Procedure
3 Follow the prompts in the Task Panel to complete the promotion. As a result, the service displays the
Trail Type of User-Provisioned.
4 Repeat for other applicable services on the span.
Before Disconnecting Fibers
Important! — Start the Planet Operate cut-out process as described in this section before
physically disconnecting fibers on the optical link.
Important! — Once you begin the node cut-out procedure, you must complete it; there is no
option to abort, cancel, or revert.
Verify that all services on the affected nodes are in a stable, non-alarmed state with no trail
discrepancies. During the cut-out process, do not perform any other configuration or maintenance
activities in the network.
Node Cut-Out
The following procedure, as an example, refers to cut-out of the node ksimC from the optical link
between ksimA and ksimB.
Figure 23: Removing Node from Optical Link
To remove a node from an existing optical link or trail, follow this procedure.
Step Procedure
1 In the Network view fiber layer, select the node to remove; right-click the node and select Cutout
Node... to display the Cut-Out tab.
2 Planet Operate finds and displays services on this node that are in the Discovered state.
Note: This screen does not display all services on the link, but only those in the Discovered state.
Since the node cut-out process supports only user-provisioned services, you must promote Discovered
services to proceed.
Click Promote to move these services to the User-Provisioned state.
Note: If all services on this node are already in the User-Provisioned state, Planet Operate does not
display this screen. In this case, go to step 4.
Step Procedure
3 Planet Operate analyzes the current fiber connections. Connect the physical fibers as described in the
Expected Connections field.
Click Rediscover.
4 When physical fiber connections are correct, click Update Services.
5 When Planet Operate completes the services update, click Close to close the Cut-Out tab.
Step Procedure
6 Click the Network tab to verify that the optical span now does not include the new node.
Verify that traffic is flowing as expected. If desired, check the Trail Analyzer for updated TESI-based
services running through the new span.
Note: Planet Operate does not delete TESIs or other configuration on the cut-out node.
Use the EMS panels to remove remaining or obsolete configuration on the node.
Inserting and Removing a Ciena Packet

Networking Device
Planet Operate supports the cut in (insertion) and cut out (removal) of Ciena Packet Networking (PN)
devices to and from an existing operational link on a multi-hop linear network topology.
Before Disconnecting Fibers on the Multi-Hop Linear Topology
Important! — Start the Planet Operate cut-in/cut-out process as described in this section before
physically disconnecting fibers on the multi-hop linear topology.
Before Proceeding with Node Cut-In
Important! — You must complete all prerequisites for Ciena Packet Networking devices before
proceeding with node cut-in. Refer to the Ciena|Blue Planet Packet Networking Node Discovery and
Management documentation.
Node Cut In
For node cut in, verify the following on the node to be cut in:
• The node is running the correct software version.
• The node is configured for multi-hop linear topology operation (refer to the Ciena Packet
Networking documentation).
• The node management channel VLAN ID must be a member of both ports used on the
devices.
To insert a Ciena Packet Networking device (node) to an existing optical link on a multi-hop linear
topology, follow this procedure.
Step Procedure
1 In the Network view fiber layer, select the optical link to receive the new node; right-click the trail and
select Show extended menu, select Node Cut-In... to display the Cut-In panel.
2 When the new node is connected in the linear chain, resume the cut-in process as follows:
• To add a new node to Planet Operate management and cut in to this optical link
A. Click the Select option button.
B. Select the node from the Existing node list.
C. Click Set Node.
D. Go to step 5.
Step Procedure
4 To cut in and create a new node to Planet Operate management simultaneously, do the following:
A. Select the Create option button.
B. Enter a user label for the node.
C. Select the Ciena Packet Networking device name from the list.
D. Enter the DCN IP address for the node.
E. Enter the DCN port for the node.
F. Click Set Node>.
G. Click Continue.
Once node discovery and network synchronization are complete and the node is reachable, Planet
Operate automatically advances to the next step.
Step Procedure
5 A. Select the ports (A and Z end) and designate the new trail names (towards A port and Z port) to
connect to the cut-in node.
Important! — Ensure that the ports you select in this step correspond to the actual physical fiber
configuration in the network. Planet Operate cannot verify the ports you select are correct.
B. Click Update Services.

C. At the confirmation dialog box, click Yes to proceed.
Click Refresh to refresh the panel containing the timer information, or click Close to close the Cut-In
panel.
7 Click the Network tab to verify the new node in the linear chain.
8 Click Close to close the Cut-in panel.
Node Cut Out

This section describes the procedure to remove a node from an existing optical link on a multi-hop
linear topology without affecting live traffic.
To remove a Ciena Packet Networking device (node) from an existing optical link on a multi-hop
linear topology, follow this procedure.
Step Procedure
1 In the Network view tab, select the node to remove; right-click the node and select Cutout Node... to
display the Cut-Out panel.
2 Disconnect the existing fibers to the node and reconnect the fiber in the new configuration.
3 When the new fiber connections are in place, specify a new trail name, and click Apply > to advance to
the next state.
Step Procedure
5 Click the Network tab to verify that the node you cut out is no longer part of the multi-hop linear
topology.
6 Click Close to close the Cut-Out panel.

7 The node is now cut out from the linear topology. However, it still remains in the Planet Operate
database and displays in Network view. To delete the node from the database and from Network view:
A. Right-click the cut-out node.
B. Select Delete Node.
C. Click Yes to delete the cut-out node from the database.
Important! — You must recommission the cut-out node (to remove all provisioning
information) before reusing and cutting in to another network.
Appendix A: Z-Series Quick
Turn-Up
Note: When a Network Element is initializing, the node operational state of the
NE will reflect the real-time status of the NE. This may change during the boot-up
stage during the arrival and configuration of line modules that have not
completely transitioned into service.
Follow the procedures in this section to turn up a Z-Series node, span, and DWDM channel with LAD
modules. For detailed information regarding the procedures in this quick turn up, see the Z33
Installation and Safety Guide, Z77 Installation and Safety Guide, the Planet Operate user guides, and the
Z-Series Data Communications Network Planning and Configuration Reference Guide.
Step Procedure
1 Slot the line cards.
2 Connect the Dispersion Compensating Module (DCM) as needed (supported by the LAD-8E, LAD-40E,
and LAD-8X modules).
3 Slot the pluggable optics.
4 Commission the Z-Series node.
5 Verify DCN connectivity to the node. If you connect the LAN to the Z-Series node MGMT1 port, the
Planet Operate server should be able to communicate node.
• Provision all WDM XFP ports Admin State to Unlocked (to raise alarms during turn up).
• Set the LAD module OSC Transmit Control parameter to On.
• Leave the LAD-4A, LAD-8A , LAD-8X, and LAD-8E amplifier parameter values at their default
settings.
Important! — To avoid damage to the LAD-4A, LAD-8A, LAD-8X, or LAD-8E and the associated XFP
transceivers, leave the LAD amplifier parameter values at their default settings during turn-up.
6 Connect a 10 dB attenuator between the TX and RX on the LAD Line port.

Important! — Do NOT connect the LAD Line port TX and RX without a 10 dBm attenuator (15 dB
attenuator for the LAD-8X) or damage will result.
7 Verify the correct OSC optical levels.

With a 10 dB attenuator RX optical level should be less the TX optical level +/– 3 dBm. If not, then
resolve this before continuing to the next step.
8 Add a fiber patch jumper from the OTU2/WDM XFP port to the appropriate LAD add/drop (AD) port.
9 Provision the XFP to LAD fiber patch cross-connects.
Step Procedure
10 Verify the TX and RX optical levels on OTU2/WDM XFP port of each service card.
• For LAD-4, LAD-8, or LAD-8i modules, the XFP RX optical level should be within –15.2 dBm to
–9.2 dBm.
• For LAD-8A, LAD-8X, or LAD-8E modules, the XFP RX optical level should be within –15.8 dBm to
–10.8 dBm.
11 Remove the fiber patch jumper from the service card OTU2/ WDM XFP port to LAD add/drop port.
• This will leave one end of the fiber terminated to the LAD add/drop port.
• This is a safety measure to assure when the far-end shelf is connected we can verify optical
levels before completing the fiber patch jumper connection.
12 Remove the attenuator from the LAD Line port.
13 Connect the LAD Line port to the fiber patch panel.
DWDM Port to LAD – Functional Test Setup
Service Card LAD-x

TX
DWDM/ TX Line
RX
OTU2 Port P1 10 dB
RX
TX
Midstage*
RX
If no DCM,
loop the Add 10 dB
TX
midstage port attenuator
Express
Verify the optical RX RX on LAD
level using Planet LINE port
Operate/CyCT for TX (Add 15 dB
AD1 attenuator
each DWDM/OTU2
RX 1533.31 on the
port
LAD-8X
TX AD2 LINE port)
1552.52
RX
TX AD3
RX 1551.72
* Midstage port
on supported TX AD8
cards only 1546.92
RX
Figure 24: Service Card DWDM Port to LAD
L-AMP Node Turn-up
Step Procedure
1 Connect the DCMs as needed.

2 Commission the L-AMP shelf.
3 Provision the OTM ports Admin State to Unlocked (to raise alarms during turn up).
4 Set the OTM ports OSC Transmit Control parameter to On.
Span Turn-up
Step Procedure
1 Verify that the LAD modules are NOT connected via fiber patch jumpers to the service cards
OTU2/WDM XFPs.
This is to prevent potential damage to the DWDM XFPs due to high RX power.
2 Via the fiber patch panels, connect the LAD Line port to the adjacent Z-Series shelf LAD Line port.
• Verify the OSCs are up. Note the detected span loss.
• Record the OSC TX and RX optical levels.
3 Verify that the OSC alarms clear.
4 Verify DCN connectivity to the Z-Series node. The Planet Operate server should be able to communicate
with the node.
Verify that proxy ARP, OSPF, or routes have been provisioned.
Span Turn-Up (LAD Modules)
Near-End Far-End
Service Card LAD LAD Service Card
TX TX
Line Line TX
TX RX RX
P1 P1
RX RX
TX TX
Midstage* Midstage* DWDM/OTU2
DWDM/OTU2 RX RX
Port Port
TX TX
Express Use a Power Meter Express
RX to measure the Rx RX
AD1 optical level on the AD1

TX LAD before TX
1533.31 1533.31
patching the LINE
RX RX
port
TX AD2 TX AD2
1552.52 1552.52
RX RX
TX AD3 TX AD3
1551.72 1551.72
RX RX
TX AD8 TX AD8
1546.92 * Midstage port on 1546.92
RX RX
supported cards only
Figure 25: Span Turn-Up
DWDM Channel Turn-up
Step Procedure
1 Set the Transmit Control parameter to On for the DWDM XFPs on the near-end and far-end Z-Series
nodes.
2 Connect fiber patch jumpers from the service card DWDM XFP to the LAD add/drop port on the far-end
node.
3 Connect the power meter to the fiber patch from the LAD add/drop port TX on the near-end node.
Verify that the RX optical level is between –23 dBm and –10 dBm.
4 Adjust the LAD-8A, LAD-8X, or LAD-8E modules as necessary; verify that the RX power level on the
near-end node is correct.
Contact Customer Service for the recommended LAD-8A, LAD-8X, and LAD-8E amplification settings.
5 Disconnect the DWDM XFP to LAD add/drop port fiber patch jumper on the far-end node.
6 Connect the DWDM XFP to LAD add/drop port fiber patch jumper on near-end node.
7 Connect the power meter to the fiber patch from the LAD add/drop port TX on the far-end node.
Verify that the RX optical level is between –23 dBm and –10 dBm.
8 Adjust the LAD-8A, LAD-8X, or LAD-8E modules as necessary; verify that the RX power level on the
far-end node is correct.
9 Repeat steps 1 through 8 for each DWDM channel to be turned up.
DWDM Optical Test Configuration (LAD Modules)
Near-End Far-End
LAD LAD Service Card
TX TX
Line Line TX
RX RX
P1
RX
TX TX
Midstage* Midstage* DWDM/OTU2
RX RX
Port
TX TX
Express Express
RX RX
AD1 AD1
Fiber Patch Jumper TX TX
1533.31 1533.31
RX RX
Fiber
TX AD2 TX AD2 Patch
Use a Power Meter
to measure the 1552.52 1552.52 Jumpers
RX RX
optical level on
each channel TX TX
AD3 AD3
before patching to
1551.72 1551.72
the XFP RX RX
TX AD8 TX AD8
1546.92 * Midstage port on 1546.92
RX RX
supported cards only
Figure 26: DWDM Channel Turn-Up
Appendix B: Turn-Up Checklists
Power Checklist
For power installation and verification, follow this procedure.
Power Checklist
Part 1: Power checklist for new power installation from the Battery Distribution Fuse Board (BDFB) to the
equipment rack fuse panel
Check (X) or
Record Tasks to Perform
Step Perform steps 1 through 11 on new power installations only
1 Visually check all cables "A" and "B" for correct routing and labeling.
2 Record the rack number that contains the main power panel (BDFB).
3 Record the fuse or breaker size at the main power panel (BDFB).
4 Record the fuse/breaker panel type in the rack being powered.
5 Verify that the A and B breakers at the BDFB are in the OFF position.
Perform steps 6 through 8 on the input leads to the Power Distribution and
Alarm Panel (PDAP)
6 Verify with a multimeter that the A feed is not shorted to the A or B return feed.
7 Verify with a multimeter that the B feed is not shorted to the A or B return feed.
8 Verify with a multimeter that the A feed is not shorted to the B feed.
9 Verify that the fuses are NOT installed on the PDAP.
10 At the BDFB, turn on breaker "A."
At the PDAP verify polarity across the "A" feed and the return feed. Record the "A"
11
feed voltage.
12 At the BDFB, turn on breaker "B."
At the PDAP verify polarity across the "B" feed and the return feed. Record the "B"
13
feed voltage.
Power Checklist
Part 2: Power checklist for new power installation from the fuse panel to the Z-Series shelf
Begin PDAP
14 Verify there are NO circuit packs installed in the terminal shelf(s).
Power Up
Perform steps 15 through 17 on the output leads from the PDAP and where the
leads physically enter the terminal shelf.
15 Verify with a multimeter that the A feed is not shorted to the A or B return feed.
16 Verify with a multimeter that the B feed is not shorted to the A or B return feed.
17 Verify with a multimeter that the A feed is not shorted to the B feed.
18 Record the size of the fuses (AMPS) being installed.
19 At the PDAP, insert the "A" side fuse – the shelf fans should power up.
20 Measure and record the "A" feed voltage.
21 Remove the "A" side fuse – the shelf will power down.
22 At the PDAP, insert the "B" side fuse – the shelf fans should power up.
23 Measure and record the "B" feed voltage.
24 Insert the "A" side fuse.
Using the multimeter continuity tester, check for continuity between the shelf and
the rack.
25
Select "Ohms" on your multimeter, check for Ohms between the chassis and the
rack. It must be less than 1 Ohm. Record the value (Ohms).
End of Procedure
Transmit and Receive Power Testing

Note: Ports 3 and 4 on the PME-216i line card are SFP interfaces.
Use the following tables to enter transmit and receive power data.
LAD – TX / RX Optical Power

(RX value should be < –12dB)
TX RX RX
XFP XFP Pad Pad Final
Slot # Line Line Required Value Rec Value
Slot
Slot
2.5G-LME4 – TX / RX Optical Power

(XFP RX value should be < –12dB)
TX RX TX TX TX TX RX RX RX RX
XFP XFP SFP SFP SFP SFP SFP SFP SFP SFP
Slot # P1 P1 P2 P3 P4 P5 P2 P3 P4 P5
Slot
Slot
DTM-8 / DTM-8G – TX Optical Power

(RX value should be < –12dB)
TX TX TX TX TX TX TX TX
XFP XFP XFP XFP XFP XFP XFP XFP
Slot # P1 P2 P3 P4 P5 P6 P7 P8
Slot
DTM-8 / DTM-8G – RX Optical Power

(RX Value should be < –12dB)
RX RX RX RX RX RX RX RX
Slot
PME
(XFP RX value should be < –12dB)
TX TX TX TX RX RX RX RX
Slot
TX TX TX TX TX TX
SFP SFP SFP SFP SFP SFP
Slot # P5 P6 P7 P8 P9 P10
Slot
TX TX TX TX TX TX
Slot # P11 P12 P13 P14 P15 P16
Slot
RX RX RX RX RX RX
Slot # P5 P6 P7 P8 P9 P10
Slot
RX RX RX RX RX RX
Slot # P11 P12 P13 P14 P15 P16
Slot
Important! — Only a trained and certified individual that has experience with this process should
perform transmit and receive power testing procedures.
• After cleaning the connectors and using a fiber scope to verify the cleanliness, use an optical
power meter to measure the transmit power of each transmitter at the fiber distribution
panel.
• All power measurements must be within the minimum and maximum values as indicated on
the chart below.
• If the power does not meet the minimum output value:
 Clean the fiber patch jumper and test again
 Change fiber patch jumper
 Replace the SFP or XFP transceiver
• Record all results.
• Test all spare optical line card.
Note: The recommended maximum RX optical power level must not be greater
than –12 dB.
2.5G-LME4 to LAD Functional Test Setup

Perform this test during the shelf testing activities.
Important! — Always check the optical specifications page for the correct power specifications.
RR ______ Shelf ____
2.5G-LME4 Function Test Results
P or F P or F P or F P or F P or F
XFP SFP SFP SFP SFP
Slot # Card Type P1 P2 P3 P4 P5
2.5G-LME4
2.5G-LME4
Perform the following functional test for a period of 15 minutes. The test set should show 0 errors.
2.5G-LME4 to LAD-4 or LAD-8 – Functional Test Setup
2.5G-LME4 LAD
TX
TX Line
RX 10dB
P1 If no DCM
RX Loop
TX Midstage
(LAD-8E
and
TX RX LAD-8X
P2 Only)
OC-48, STM-16, OTU1
RX TX
Express
RX
TX
P3
Test Set
RX TX
1533.31
RX
TX
P4 TX
RX 1552.52
RX
TX
P5 TX
RX 1551.72
RX
TX
1550.92
RX
TX
P9
RX
Figure 27: 2.5G-LME4 to LAD Functional Test Setup
PME to LAD Functional Test

Note: Ports 3 and 4 on the PME-216i are SFP interfaces.
Perform this test during the shelf testing activities.
RR ______ Shelf ____
PME-412 Function Test Results
P or F P or F P or F P or F
XFP XFP XFP XFP
Slot # Card Type P1 P2 P3 P4
PME
PME
P or F P or F P or F P or F P or F P or F
Slot # Card Type P5 P6 P7 P8 P9 P10
PME
PME
RR ______ Shelf ____

P or F P or F P or F P or F P or F P or F
Slot # Card Type P11 P12 P13 P14 P15 P16
PME
PME
Perform the following functional test for a period of 15 minutes. The test set should show 0 errors.
PME-412 to LAD-4 or LAD-8 – Functional Test Setup
PME-412 LAD-x
TX
TX TX Line
P5 RX 10dB
P1 If no DCM
OC-48, STM-16, OTU1
RX RX Loop Midstage
TX (LAD-8E
and
TX RX LAD-8X
P6
Test Set
Only)
RX TX
TX
Express
P2 RX
TX RX
P7
RX TX
1533.31
RX
TX
P8
RX TX TX
P3 1552.52
RX RX
TX
1551.72
RX
TX
P13 TX
TX
RX P4 1550.92
RX
RX
TX
P14
RX
TX
P15
RX
TX
P16
RX
Figure 28: PME-412 to LAD Functional Test Setup
System Level Records – End-to-End Testing

Use the following table to record end-to-end testing and system levels.
Note: Record (P = Passed, N/A, or leave blank).
From To Test Results
BER
Card Card Duration Test
Site Name Type Slot# Port# Site Name Type Slot# Port# Time Results
End-to-End and BER Testing

For multi-node systems, end-to-end testing must be performed. It is not expected that every port on
every line card be tested end-to-end. Only a sampling of the circuits is required.
Configure the cross-connect between port P2 and P1 on the LAD modules.
2.5G-LME4 to LAD-x End-to-End Test Setup

Remote Pass-through Sites
LAD 2.5G-LME4 2.5G-LME4 LAD

TX TX
Line TX TX Line
RX RX
DCM P1 P1 DCM
Midstage or RX RX or Midstage
(LAD-8E TX TX (LAD-8E
and and
LAD-8X RX RX LAD-8X
Only) Only)
TX TX TX TX
Express P2 P2 Express
RX RX
RX RX
TX TX
1533.31 TX TX 1533.31
RX P3 P3 RX
RX RX
TX TX
1552.52 Install 1552.52
RX TX TX RX
P4 Jumpers P4
RX RX
TX or TX
1551.72
TX
Provision TX
1551.72
RX RX
P5 Pass-thru P5
RX Connection RX
TX TX
1550.92 1550.92
RX RX
2.5G-LME4 to LAD-x End-to-End Test Setup

Head End Sites
LAD 2.5G-LME4 2.5G-LME4 LAD

TX TX
Line TX TX Line
RX RX
DCM P1 P1 DCM
Midstage or RX RX or Midstage
(LAD-8E TX TX (LAD-8E
and and
LAD-8X RX RX LAD-8X
Only) Only)
TX TX TX TX
Express P2 P2 Express
RX RX
RX RX
TX TX
1533.31 TX TX 1533.31
RX P3 P3 RX
RX RX
TX TX
1552.52 1552.52
RX TX TX RX
P4 P4
RX RX
TX TX
1551.72 1551.72
RX TX TX RX
P5 P5
RX RX
TX TX
1550.92 1550.92
RX RX
OC-48
Test Set
Appendix C: Replacing a DTM-8G
Module with a DTM-8 Module
Ciena has discontinued the Z-Series DTM-8G module (No.: 800-0031-01). The Z-Series DTM-8 module
(No.: 800-0035-01) replaces the DTM-8G and is available immediately. End of Life for the DTM-8G
module is set for 5 years. Ciena will offer maintenance and support for the DTM-8G module until the
product reaches its End of Life date, January 31, 2016.
To replace the DTM-8G module with a DTM-8 module, follow this procedure. Use Planet Operate or
CyCT for all steps, except steps 4 and 5.
Step Procedure
1 Record the Transport Resources and cross-connect information associated with the DTM-8G you are
about to replace.
Note: If the DTM-8G was configured with A-to-Z provisioning, record the trails information for each
DTM-8G port.
2 Delete all provisioned cross-connects from the DTM-8G module.
3 Delete the DTM-8G module.
4 Physically remove the DTM-8G module from the Z-Series shelf.
5 Install the new DTM-8 module in to the open slot.
Note: Install the XFP transceiver and attach the jumper cable to the DTM-8 module.
Note: The DTM-8 module will be inserted in to the Planet Operate or CyCT display automatically.
6 Use the Transport Resources information that you recorded in step 1 to assist you in provisioning the
Transport Resources as needed.
7 Click the Refresh Node View icon to refresh the Cross-Connections sub-tabs.
8 If the DTM-8G cross-connects were created with A-to-Z provisioning, go to step 9.
If cross-connects for the DTM-8G were originally created manually, do the following:
A. Use the cross-connect information that you recorded in step 1 to re-create the cross-connects for
the DTM-8 module.
B. Change the Admin State of the equipped DTM-8 ports to Unlocked.
C. Go to step 10.
Step Procedure
9 This step will re-create the cross-connects and clear the transceiver mismatch alarm.
If the DTM-8G cross-connects were created with A-to-Z provisioning, use Planet Operate or CyCT to do
the following:
A. Click the Trails tab to find the trail associated with the DTM-8 module for all ports. The trail may
have a "Discrepancies Found" label in the Last Sync Status column or an Out-of-Service label in the
Service State column.
B. If the trail has a "Discrepancies Found" label, right-click the trail and select NMS Workflows > Bulk
Trail Repair and Reprovisioning. Follow the A-to-Z provisioning prompts to repair the trail.
C. Change the Admin State of the equipped DTM-8 port to Unlocked.
Repeat step 9 for all of the pertinent trails associated with equipped DTM-8 ports.
10 You have completed this procedure. If the cross-connects are not re-created or mismatch alarms have
not cleared, contact Customer Service for assistance.
Appendix D: Replacing RCMs with
XC-2800 Switch Fabric Modules to
Support PSW and TSW Modules
Before adding TSW-10G10, PSW-10G10, or PSW-618 modules to empty slots in the Z77 shelf, you
must upgrade system software to Release 5.x or higher and insert XC-2800 switch fabric modules to
the slots in the rear of the shelf.
Before adding PSW-10G20 modules to empty slots in the Z77 shelf, you must upgrade system
software to Release 8.x or higher and insert XC-2800 switch fabric modules to the slots in the rear of
the shelf.
If the Z77 shelf contains Ring Closure Modules (RCMs) in the rear slots, you must remove the RCMs
and replace them with XC-2800 modules. This section contains a procedure for this replacement
task.
To use TSW-10G10, PSW-10G10, PSW-10G20, or PSW-618 modules to replace PME line cards
(PME-216i, PME-412) carrying active services, contact the TAC for assistance.
Note: Starting in Release 4.2, you can install MSE-1482 line cards in a Z77
shelf supported by the XC-2800 switch fabric. The XC-2800 switch fabric
module supports the MSE-1482 in a standalone muxponder configuration.
However, the XC-2800 switch fabric module does not support MSE-1482
card-to-card backplane cross-connections or protection.
If you require MSE-1482 card-pair applications to support MSE cross-card
connections, MSE SONET/SDH protection groups, or pass-through traffic
between a pair of MSE-1482 modules, remove the MSE line cards from the
shelf prior to installing XC-2800 modules and place the MSE line cards into a
Z77 shelf equipped with RCMs.
EFM Slots with

RCMs installed
Figure 29: Z77 Rear Panel
Warning! – This procedure affects traffic.
To replace RCMs with XC-2800 modules, follow these steps.
Step 1: Remove MSE-1482 Modules

If you require MSE-1482 card-pair applications to support MSE cross-card connections, MSE
SONET/SDH protection groups, or pass-through traffic between a pair of MSE-1482 modules, follow
step 1 to remove the MSE line cards from the shelf prior to installing XC-2800 modules and place the
MSE line cards into a Z77 shelf equipped with RCMs. If the MSE-1482 modules are strictly in a
standalone muxponder configuration, you can leave them in the Z77 shelf, skip step 1 and go to step
2.
Before removing the MSE-1482 line cards from the Z77 shelf, it is important to obtain a provisioning
"snapshot" of each line card by collecting provisioned services, VCAT groups, cross-connect
information and so forth so that you can re-apply this information after you install the MSE line cards
into a Z77 shelf with RCMs.
A. Record the MSE configuration on the node.
B. Delete MSE configurations, including services, cross-connects, VCAT groups, and so forth.
C. Remove the MSE line cards from the Z77 shelf.
D. Using Planet Operate, right-click the module and select Remove Module.
Step 2: Upgrade the Node to CyOS Release 5.x or Higher

Upgrade CyOS software to Release 5.x or higher. Refer to "Software Upgrade starting on page 93" in
the Z-Series Troubleshooting and Maintenance Guide.
Step 3: Upgrade the RCM in slots 1, 2, and 4 to XC-2800

Replace the RCMs in slots 1, 2, and 4. Do NOT replace the RCM in slot 3 until step 5.
A. Remove the RCM from slot 1 in the shelf rear.
B. Install the XC-2800 module into the empty slot.
C. Repeat steps 1 and 2 for RCMs in slots 2 and 4.
D. Wait for any auto-upgrade process on the new XC-2800 modules to complete.
Note: An auto-upgrade is indicated by double-blue flashing LEDs on the front panel; the module
then reboots. Wait until the active LED turns solid green before continuing.
Step 4: Switch the LME/PME traffic to EFM slot 4
Warning! – Switching traffic from EFM slot 3 to EFM slot 4 can affect traffic for up to
500 ms.
Note: All PME/LME traffic currently runs on the RCM in EFM slot 3. Be sure to
return traffic to EFM slot 3 in step 6.
Note: Before beginning this procedure, ensure that any auto-upgrade process
of the XC-2800 modules is complete and that all XC-2800 modules are free of
alarms.
Using Planet Operate, do the following:

A. From the Shelf view, click the Rear Panel tab.
B. Right-click the side border of the shelf in the rear panel (or click the shelf in the Equipment
Tree) and select View Information.
C. In the Module information tree, select Equipment configuration.
D. Click to select the row for Attribute Fabric Slot Select.
E. In the Enter New Value field, select EFM Slot 4.
Figure 30: EFM Slot Configuration
F. Click Apply.
G. Click Close.
Step 5: Replace the RCM in Slot 3

Repeat the procedure in step 3 for the RCM in slot 3.
Step 6: Switch the LME/PME traffic to EFM slot 3
Warning! – Switching traffic from EFM slot 4 to EFM slot 3 affects traffic for up to 500 ms.
Note: Before beginning this procedure, ensure that any auto-upgrade process of the
XC-2800 modules is complete and that all XC-2800 modules are free of alarms.
Repeat the procedure in step 4, selecting EFM Slot 3 in sub-step E to switch traffic from EFM slot 4 to
EFM slot 3.
The upgrade of RCMs to XC-2800 modules procedure is complete.
Appendix E: Replacing XC-2800
Switch Fabric Modules
If the Z77 shelf contains Ring Closure Modules (RCMs) in the rear slots, you must remove the RCMs
and replace them with XC-2800 modules. For details, see Replacing RCMs with XC-2800 Switch
Fabric Modules to Support PSW and TSW Modules starting on page 181.
Warning! — This procedure affects traffic.
To replace XC-2800 modules, follow these steps.
Step 1: Change the Administrative State to Locked to Disable

A. In Planet Operate Network view tab, select the Z-Series shelf.
B. In the menu bar, click Node > Transport Resources (or from the icon bar, click the Transport
Resources icon).
C. In the Physical Resources panel, select the XC-2800 slot for the module you are replacing.
D. In the General sub-tab, from the Admin. State list, select Locked to Disable. In the
Confirmation box, click Yes to confirm.
E. Click Apply.
Figure 31: Locked to Disable State
Warning! — Replacing an XC-2800 module without setting the Admin State to Locked to
Disable results in a traffic disruption of up to 115 ms for affected services. Completing
steps 1 and 3 in this procedure will reduce, but not eliminate, the length of the
disruption.
Step 2: Replace the XC-2800 Module

A. Remove the XC-2800 module from the slot in the shelf rear.
B. Install the replacement XC-2800 module into the empty slot.
C. Wait for any auto-upgrade process on the new XC-2800 modules to complete.
Note: An auto-upgrade is indicated by double-blue flashing LEDs on the front panel; the module
then reboots. Wait until the active LED turns solid green before continuing.
Important! — This note applies when replacing RCMs with XC-2800 Switch Fabric
Modules in an ERP configuration (G.8032v1).
Removal of an RCM causes a link failure across the Z77 shelf backplane and prevents
cross-card communication. Even though the link failure is subsequently cleared, ERP ring
frames will be duplicated until you clear the Wait To Restore (WTR) value and the ERP
returns to an “Idle” Configuration State.
Services in G.8032v1 ring configurations may be impacted until the WTR timer expires or
until the timer is manually cleared.
Step 3: Change the Administrative State to Unlocked

A. From the Transport Resources EMS panel, in the Physical Resources panel, select the
XC-2800 slot for the module you replaced.
B. In the General sub-tab, from the Admin. State list, select Unlocked.
C. Click Apply.
Repeat steps 1 to 3 for any additional modules you are replacing.
The replacement of XC-2800 modules procedure is complete.
Appendix F: LAD-8 / LAD-8i
Conversion
Planet Operate provides a conversion utility that allows you to convert LAD-8 modules to LAD-8i
modules and conversely, LAD-8i modules to LAD-8 modules.
Important! — The LAD-8 / LAD-8i conversion utility is a service-affecting operation.

Convert LAD module(s) during a scheduled maintenance window.
During the conversion process, the system deletes all fiber patch cross-connects, deletes the old line
card, then re-creates the new (converted) line card and applies the original fiber patch
cross-connects to the converted line card.
The conversion example in this section is a LAD-8 to LAD-8i conversion. Note that a LAD-8i to LAD-8
conversion is the same process.
Note: The LAD-8 module does not provide a 1310 nm add/drop port.
When converting a LAD-8i module to a LAD-8 module, the LAD-8i 1310 nm
add/drop port must not be in use.
Record existing cross-connects prior to running the conversion utility

Record (write down) the LAD-8 module(s) provisioning and fiber patch cross-connects prior to
starting the conversion utility. The next figure shows an example of the cross-connects on a LAD-8
module that will be re-built after the module is converted to LAD-8i module.
This LAD-8 module

will be converted to
a LAD-8i module.
Figure 32: LAD-8 Cross-Connects Example
LAD-8/LAD-8i Conversion Utility

You can physically replace the old line card with the new line card prior to running the conversion
utility. The system will raise an equipment alarm, but the alarm clears automatically when the
conversion utility completes. Node connectivity is restored after inserting the LAD-8i module.
If your configuration has a pair of LAD-8 or LAD-8i line cards, you must replace the first card in the
card pair and run the conversion utility for the first card. Then replace the second card in the card
pair and then run the conversion utility for the second card.
To convert a LAD-8 module to a LAD-8i module, follow this procedure.
Important! — The LAD-8 / LAD-8i conversion utility is a service-affecting procedure. Traffic for all
circuits traversing this line card will be affected.
Step Description
1
From the Network view tab, double-click the intended node to display it in the Front Panel tab.
2 From the Front Panel tab, select the intended LAD-8 module to convert to a LAD-8i module. Right-click
the module to display the shortcut menu. From the shortcut menu, select Convert Module to LAD-8i
Module to open the Convert Linecard dialog box.
3 In the Convert Linecard dialog box, do the following:

A. Verify the Old Linecard is the correct type and slot. In this example, a LAD-8 module (1-3).
B. Verify the New Linecard Type is the correct type. In this example, a LAD-8i module.
C. Click the Convert button to start the conversion.
You will be notified that the conversion has completed in the Overall State field.
Verify cross-connects after completion of the conversion utility

From the Planet Operate main menu, select Node > Cross-Connections to open the
Cross-Connections tab and Port Resource View sub-tab. In the Port Resource View sub-tab verify that
the cross-connects have been properly rebuilt on the LAD-8i module.
This is the LAD-8i module

that was converted from
a LAD-8 module.
Figure 33: Example of LAD-8i Cross-Connects After Line Card Conversion
Appendix G: Z-Series Packet Line
Card Migration
Planet Operate and the Z-Series CyOS do not support service migration between packet line card
types. Migrating services from a PME line card to a PSW line card, or conversely a PSW line card to a
PME line card, is not supported. To migrate packet line cards, you must delete all provisioning on the
line card and then recreate the provisioning on the target line card. Using Planet Operate to
deprovision services from one line card type, leaving the services in a routed state, and then
reprovisioning the services on the new line card type is not supported.
If needed, you can engage Ciena Professional Services to migrate the line card provisioning for you
to ensure operational success. Contact your Ciena account representative for information.
Appendix H: Z77 LCD Operations
Panel
This section describes the LCD Operations Panel that was provided on early models of the Z77 shelf
and node recommissioning using the LCD Operations Panel.
The LCD Operations Panel attaches to the front of the Z77 chassis and provides a color touch-screen
interface, and an alarm cut-off button for facility alarms. Use The panel to view standing alarms and
display system information. It also provides a configuration interface to recommission a Z77 shelf.
Touchscreen Home ACO

Back
Figure 34: Z77 LCD Operations Panel
Note: Each tab has a scrolling side bar that allows you to scroll the screen. You
can also scroll by dragging your finger vertically across the LCD.
The LCD Operations Panel provides an Alarms tab and a Menu tab. Each tab has a scrolling side bar
that allows you to scroll the screen. You can also scroll by dragging your finger vertically across the
LCD.
Press the Home button to return to the beginning screen.
Press the Back button to return to the previous screen.
The ACO (Alarm Cut-off) button is used to terminate an audible alarm (alarm condition remains).
The ACO LED only illuminates when you push the ACO button. It is a visual indicator to the operator
that audible indication of an alarm has been suppressed. After you have pushed the ACO button, if a
new alarm occurs within the system, the ACO LED clears (no illumination) returning to the beginning
of the ACO state machine and the audio alarm sounds again (indicating there is a newer alarm since
the ACO had been pressed). That is, for a new alarm, you still want the audible and then an operator
can push the ACO button again to suppress the audible.
Note that pressing the ACO does not remove the alarm conditions. An alarm condition does not
illuminate the ACO LED, but it does activate an audio alarm.
The ACO LED remains illuminated until all current/previous alarms are removed. The LED is not
illuminated when:
• There are no alarms.
• A new alarm occurs AFTER the ACO button has been pushed to suppress a previous audio
alarm.
Alarm Conditions
The following LCD background colors indicate a specific alarm condition the unit is in:
White: Free choice, non-alarmed, indeterminate
Yellow: Minor alarms
Orange: Major alarms
Red: Critical alarms
Blue: Warning
LCD Operations Panel Menu

The LCD Operations Panel menu tab provides four options:
• Status
• Craft DHCP
• Temp. Disable Fans (fan maintenance)
• Screen saver
Status
The status screen provides you with basic system information.
Craft DHCP
The Craft DHCP screen allows you to enable or disable the DHCP server function. Enabling this
option allows the system to provide an IP address for a craft technician’s PC laptop via DHCP.
Tap Change to enable DHCP on the active BOSS card front craft port.
Note: To have the system provide an IP address via DHCP, you can also enable
the DHCP on console port setting via the Node Information dialog box in the
Planet Operate.
Temp. Disable Fans

Use this option to temporarily disable fans for maintenance. The fans will shut down for 30 seconds
to allow you time to remove the fan filter without dust blowing into the shelf.
For additional information on fan maintenance, see the Z77 Installation and Safety Guide and the
Quick Reference Guide – Z77 Fan Filter Maintenance.
Tap Initiate to disable the fans.
Screensaver
This option allows you to enable or disable the screensaver function. Tap Change to toggle the
screensaver enable/disable option.
Note: If the screensaver is enabled, the screen returns to the opening screen
after 30 seconds of no screen activity.
LCD Operations Panel Alarms

Tap the Alarms menu to display shelf alarms in the LCD Operations Panel. For each alarm the panel
displays the date and time, the alarm severity, location, and a brief alarm description.
Recommissioning the Z77 Node using the LCD Operations Panel

The LCD Operations Panel allows you to recommission a Z77 node without using a PC laptop.
To recommission a Z77 shelf, you need the following:
• System IP address
• Mask address
• Gateway IP address
• (Optional) Domain Name System (DNS)
Note: Each Z-Series node in the network must have a unique IP address provisioned.
When commissioning Z-Series equipment the following IP addresses are not supported:
• 192.168.0.1 – 192.168.0.255 Subnet 255.255.255.0
• 192.168.1.0 – 192.168.1.255 Subnet 255.255.255.0
• 192.168.2.0 – 192.168.2.255 Subnet 255.255.255.0
• 192.168.3.0 – 192.168.3.255 Subnet 255.255.255.0
• 172.16.0.1 – 172.16.0.255 Subnet 255.255.255.0
• 169.254.0.1 – 169.254.254.254 Subnet 255.255.255.0
Step 1
Tap the Operations Panel to display the Alarms screen.
Step 2
Tap the Menu tab to display the menu.
Step 3
In the Menu tab, tap Recommissioning.
Tap Continue.
Tap Continue.
Step 4
The Start screen continues the recommissioning process. Tap Start to open the System IP Address
screen.
Step 5
The System IP Address screen displays. Enter your system IP Address.
Step 6
In the System IP Mask screen, enter your System IP Mask address. Tap Next to open the Gateway IP
Address screen.
Step 7
In the Gateway IP Address screen, enter the Gateway IP Address. Tap Next to open the Gateway IP
Address screen.
Step 8
In the Pri DNS IP Address screen, enter the primary DNS IP address (if available). This step is optional
if no such IP address exists. Tap Next to open the Sec DNS IP Address screen.
Step 9
In the Sec DNS IP Address screen, enter the secondary DNS IP address (if available). This step is
optional if no such IP address exists. Tap Next to open the Review screen.
Step 10
In the Pri NTP IP Address screen, enter the primary NTP server IP address. Tap Next to open the Sec
Pri NTP IP Address screen.
Step 11
In the Sec NTP IP Address screen, enter the secondary NTP server IP address. Tap Next to open the
Review screen.
Step 12
Use the Review screen to verify that the information entered is correct. If incorrect, tap Prev to go
back to any previous screen to correct the information. When the information is corrected, tap
Finish.
Step 13
In this screen, verify the system information and commit the commissioning. If any items need to be
changed, click Go Back to return to the beginning of the commissioning process. Tap Commit to
accept the information and finish the commissioning process.
Step 14
A Commissioning Complete message displays and the BOSS card will reboot. During this stage, all
blue LEDs will light and flash on the BOSS card indicating the commissioning process is in progress.
Within a short amount of time, the blue LEDs turn to green LEDs. These will remain steady as the
reboot ends.
Step 15
The opening screen displays in the Operations Panel. The commissioning process is complete.
Note: If an alarm condition exists, the screen color reflects its severity.
• White: No Alarm
• Yellow: Minor Alarm
• Orange: Major Alarm
• Red: Critical
• Blue: Warning
For additional information on recommissioning a Z77 node, see the Z77 Installation and Safety Guide.
Appendix I: Port Mirroring
Planet Operate supports mirroring of traffic on ports of the PSW family of line cards. Whether for
troubleshooting or monitoring purposes, you can configure the mirroring function to duplicate
ingress traffic, egress traffic, or both, without impact to the original traffic flow.
Traffic mirroring replicates the data from a source port and sends the replicated traffic to a target or
destination port for observation and analysis. Traffic mirroring does not affect the source data flow.
Replicated traffic consumes system resources, and network planning must account for this.
Port mirroring is a node-level function: you can mirror traffic from any UNI or NNI PSW port to any
other UNI (only) PSW port in the same node. You can use the port mirroring feature with the PSW
Node Personality setting of "PBB-TE".
Note: For a Z33 shelf, traffic on a port in slots 1 through 4 can be mirrored only
to another port in slots 1 through 4; likewise for ports in slots 5 and 6. For
additional Z33 slot grouping information, refer to "Z33 Card Installation
Guidelines" in the Z-Series Engineering and Planning Guide. This restriction does
not apply to Z77 shelves equipped with XC-2800 fabric cards or to Z22 shelves.
Port Mirroring Terminology

The Planet Operate traffic mirroring function uses the following terms:
• Source Port: The UNI or NNI port on the PSW line card hosting the source traffic, or the
traffic to be mirrored. You can mirror egress, ingress, or both egress and ingress traffic from
this port. The source port can be a member of only one mirroring instance.
• Destination Port: The UNI port on a PSW line card that receives the duplicated traffic from
the source port. The destination port must be unused: it cannot be part of a LAG, LSP, ESP, or
Ethernet service. The destination port can be a member of more than one mirroring
instance, supporting traffic replicated from multiple source ports. The destination port
capacity (for example, 1G, 10G, 100G) does not have to match the capacity of an associated
source port, although the total capacity of the associated source traffic stream(s) should not
exceed the destination port capacity. The destination port must be a UNI port.
• Port Mirror: The Port Mirror instance is a logical entity that associates the source and
destination ports. Each Port Mirror operates independently of the others, and each contains
a single source port and a single destination port.
Note: Planet Operate retains the transport header on packets mirrored from
an NNI source port to a UNI destination port.
Capacity
This release supports the following per node:
• Up to 64 port mirror instances
• Up to 10 destination ports
Configuring Port Mirroring

To configure port mirroring, follow this procedure.
Step Procedure
1 From the Network view tab, select the intended Z-Series shelf. Double-click the shelf to display the
Front Panel tab.
2 From the main menu, select Node > Packet Switching to open the Ethernet Packet Switching tab.
3 Click the Port Mirrors sub-tab.
4 In the Port Mirrors panel, click the green plus icon to open the Create Port Mirror dialog box.
Step Procedure
5
In the Create Port Mirror dialog box, do the following:

A. In the Choices for Source Port panel, select the port containing the traffic to mirror.
B. In the Choices for Destination Port panel, select the port to receive the mirrored traffic.
C. (Optional) In the User Label field, enter a label for this Port Mirror instance.
D. (Optional) In the Owner field, enter the owner for the Port Mirror instance.
E. Select the appropriate administrative state.
F. From the Traffic Direction list, select the direction of traffic to mirror: Receive (default), Transmit,
or Bidirectional.
G. Click OK.
Deleting a Port Mirror

To delete a port mirror, follow this procedure.
Step Procedure
1 From the Network view tab, select the intended Z-Series shelf. Double-click the shelf to display the
Front Panel tab.
2 From the main menu, select Node > Packet Switching to open the Ethernet Packet Switching tab.
3 Click the Port Mirrors sub-tab.
4 In the Port Mirrors sub-tab, do the following:
A. Right-click a port mirror row to select it.
B. Click Delete Port Mirror.
C. Confirm deletion by clicking Yes.
Appendix J: Alarm List
The following tables show the alarms pertaining to Z-Series systems.

Alarm list 1 of 6:
Alarm list 2 of 6:
Alarm list 3 of 6:
Alarm list 4 of 6:
Alarm list 5 of 6:
Alarm list 6 of 6:
Appendix K: OLA-010 Raman
Amplifier Safety Procedure
Complete the following procedure using CyCT (craft terminal) or Plant Operate to pre-test OLA-010
network port fiber; verify back reflection level and DWDM/OSC signal levels, and the Raman amplifier
operational state.
Step Procedure
1 In the Planet Operate Network Tree or Network view tab, double-click the intended Z-Series node to
open the Front Panel tab.
Note: CyCT does not provide a Network Tree or Network view tab; you can only view one Z-Series
shelf/node at a time.
3 In the Physical Resources sub-tab, right-click the intended OLA-010 module and select Expand Subtree
to expand the view.
Click the OLA Network Port.
4 Click the Port sub-tab.
5 Set the Operational Mode to Disabled.
6 At the Z-Series shelf, clean the incoming line fiber connector and connect the fiber to the OLA module
Network RX port.
Step Procedure
7 Click Pre-test Line. Wait a few seconds for test results to register.
8 Verify pre-test line results.

If the pre-test line result is Pass (indicating a back reflection (dBm) below -21.0), then skip step 9 and
proceed to step 10.
If the pre-test line result is Fail, then go to step 9 to correct the fiber back reflection results.
9 A pre-test line result of Fail (a back reflection (dBm) above -21.0), indicates the fiber is impaired and
requires correction.
Test the line fiber with an Optical Time-Domain Reflectometer (OTDR). Review the OTDR reading.
Examine and repair all reflection located within the first 2 km of the line fiber.
Repeat steps 7 through 9, until you have cleared all reflective events and receive a pre-test line result of
Pass.
10 Click the Advanced sub-tab to verify DWDM (dBm) and OSC (dBm) signal levels.
Readings must show DWDM and OSC levels above the programmed DWDM and OSC level thresholds.
The result of the threshold check is shown in the Current field. Both DWDM and OSC threshold
readings must indicate Pass, or the Raman pumps will not activate. If both readings indicate Pass, then
skip step 11 and proceed to step 12.
If either reading indicates Fail, then go to step 11 to correct the failed threshold check.
Step Procedure
11 To rectify a failed threshold check, the far-end equipment must transmit valid DWDM and OSC levels,
and received signal levels must be above the programmed thresholds. The Raman amplifier will not
become operational until received DWDM and OSC levels are valid.
Once the received signals are above the thresholds, and the DWDM and OSC threshold checks indicate
Pass, then proceed to step 12.
12 Click the Port sub-tab.
13 Set the Operational Mode to Auto Gain.
14 Set the Requested Gain to the required level.
Note: Gain equals Detected Rx Span Loss minus 10 dB (Gain = Detected Rx Span Loss - 10 dB).
Set the Requested Gain to 13.5 dB, or to the Detected Rx Span Loss minus 10 dB; whichever is less.
For example, if the Detected Rx Span Loss is 28 dB minus 10 (18 dB), then set the Requested Gain to
13.5.
If Detected Rx Span Loss is 20 dB minus 10 (10 dB), then set the Requested Gain to 10.
15 Click Apply.
16 Verify the Raman State.
A. If the Raman State is On (indicating the amplifier is operational and gain is achieved), then skip
step 17, and proceed with turn-up procedures.
B. If the Raman State is Eye Safety Shutdown, then click the Advanced sub-tab and go to step 17.
17 Review all Advanced threshold check readings of Fail to determine the reason for the eye safety
shutdown.
Note: One or more readings (Pump Reflection Ratio, ASE Offset Threshold, DWDM level, OSC level,
Raman Gain, and Temperature) may cause an eye safety shutdown.
A. Repeat steps 7 through 11 until all fail conditions are corrected; and the Port tab pre-test line result
is Pass, and all Advanced tab threshold check readings are Pass.
B. Repeat steps 12 through 16 until the Raman State is On (indicating the amplifier is operational and
gain is achieved).
You have completed this procedure.
Appendix L: Acronyms and
Z-Series Terminology
ACO Alarm Cut-Off
ADM Add/Drop Multiplexer
AID Access Identifier
AIS Alarm Indication Signal
ALS Automatic Laser Shutdown — The ALS protocol is used to turn off the optical output
power of remote transmitters if an optical link is broken.
AMB Air Management Board — Z-Series Air Management Boards are essential to proper
cooling of the shelf assembly. Air Management Boards must be installed over all unused
slot openings to prevent damage from overheating.
ARP Address Resolution Protocol
Attenuation A loss in signal strength along an electrical or optical cable. In optical fibers, attenuation is
the reduction in signal strength. The higher the signal loss, the higher the attenuation.
Dispersion, absorption and light scattering cause attenuation. Attenuation is typically
referenced in decibels per length of medium in kilometers (dB/km).
AUI Attachment Unit Interface
AWG Arrayed Wavelength Grating

– or –
Array Wave Guide
– or –
American Wire Gauge
B-MAC Backbone MAC address — B-MAC is an individual MAC address associated with a Provider
Instance Port and used in creating the MAC header of I-tagged frames transmitted across
a Provider Backbone Bridged Network.
B-VID Backbone VLAN Identifier — B-VIDs are used in PBB-TE as part of the 3-tuple that
identifies a TESI path. The valid B-VID range is 1 through 4089.
BE Bit Error
BER Bit Error Ratio
Blue Planet Blue Planet is a software-defined network (SDN) system built specifically for service
provider networks. Blue Planet lets service providers of all types virtualize their networks,
flatten legacy cost structures, make more efficient use of network assets, and accelerate
service delivery.
Blue Planet is composed of three distinct elements: an open SDN platform, SDN apps,
and element adapter apps facilitating control over a wide range of third-party network
devices.
BNG Broadband Network Gateway
BOSS Broadband Operating System Supervisor — The BOSS card provides common shelf
control functionality to Z77 nodes.
BTM BOSS Termination Module — The BTM houses the Z77 physical connectors for
management and timing interfaces.
BPDU Bridge Protocol Data Unit
CAC Connection Admission Control — CAC is used for Traffic Engineering configuration and
helps to control congestion in a connection-oriented network such as Carrier Ethernet.
CAC is used during the setup of a connection to determine if the Quality of Service (QoS)
is valid for the connection request and to verify that there are sufficient resources
available to allow a new connection. The QoS of the new connection cannot affect the
QoS of existing connections.
CBS Committed Burst Size — The Committed Burst Size is a bandwidth profile parameter. CBS
limits the maximum number of bytes available for a burst of service frames sent at the
UNI speed to remain CIR conformant.
CCM Continuity Check Messages — CFM Continuity Check Messages are multicast heartbeat
messages exchanged periodically among MEPs. CCMs allow MEPs to discover other MEPs
in a domain and allow MIPs to discover MEPs.
CDF Client Data Frame
CE • Customer Equipment
• Carrier Ethernet
• Customer Edge
• Circuit Emulation
CEM Common Equipment Module
CFI Canonical Format Indicator
CFM Connectivity Fault Management — Connectivity Fault Management is an IEEE 802.1ag

end-to-end per-service-instance Ethernet OAM protocol. CFM provides connectivity
monitoring, fault verification, and isolation for carrier networks. CFM uses standard
Ethernet frames.
CIR Committed Information Rate — The Committed Information Rate is a bandwidth profile
parameter. CIR defines the average bits per second of service frames up to which the
network delivers service frames and meets the performance objectives defined by the
Class of Service (CoS) service attribute.
CIST Common and Internal Spanning Tree identifies the regions in a network and administers
the CIST root bridge for the network, the root bridge for each region, and the root bridge
for each spanning-tree instance in each region.
CoS Class of Service

Service frames delivery and performance levels agreed to by the service provider.
CPE Customer Premises Equipment
CSF Client Signal Fail
CSV Comma-Separated Values
C-VID Customer VLAN Identifier
C-VLAN Customer VLAN
CWDM Coarse Wave Division Multiplexing

CWDM uses the center wavelengths from 1271 nm to 1611 nm with a channel spacing of
20 nm.
DAPI Destination Access Point Identifier
DCI Data Center Interconnect
DCM Dispersion Compensating Module
DCN Data Communication Network
Decibel Decibel (dB) is a logarithmic scale used as a measurement of relative power.
DEI Drop Eligible Indicator

A Drop Eligible Indicator indicates the drop eligibility of a frame.
DHCP Dynamic Host Configuration Protocol — DHCP allows a computer to connect to an
IP-based network without having a pre-configured IP address.
DM Delay Measurement
DNS Domain Name System — DNS is used to convert human-friendly host names and domain
names into numerical IP addresses.
DSCP Differentiated Services Code Point
DSR Digital Signal Rate
DTE Data Terminating Entity
DTM Digital Transmission Module — The Z-Series 8-port DTM-8 and DTM-8G provide
multiservice 10G transponder and regenerator functions. The DTM-8 and DTM-8G
encode Ethernet and SONET/SDH client-side signals into a standard G.709 OTN optical
channel (OTU2 DWDM) for DWDM drop and insert services in the Z-Series multi-layer
transport platforms.
The Z-Series DTM-100G is a 100 Gbps dual-slot transponder module with configurable
OTU4 mapping and forms the DWDM interfaces for the Z22 (–48V), Z33, and Z77 100
Gbps transponder solutions.
The DTM-100G module receives a C Form-Factor Pluggable (CFP) based 100 GbE or OTU4
signal and generates a 100 Gbps ITU grid wave with OTU4 embedded wrapping.
DVM Delay Variation Measurement
DWDM Dense Wavelength Division Multiplexing — DWDM is the transmission of multiple signals
over closely spaced wavelengths in the 1550 nm region on a single fiber of fiber pair.
EA Element Access
EBS Excess Burst Size — The Excess Burst Size is a bandwidth profile parameter. EBS limits
the maximum number of bytes available for a burst of service frames sent at the UNI
speed to remain EIR conformant.
EDFA Erbium Doped Fiber Amplifier — EDFA is a device used to amplify optical signals. Unlike
regenerators, EDFAs directly amplify an optical signal. EDFAs do not convert it to electrical
before increasing the signal. With EDFA, optical fibers are doped with erbium, which can
amplify light in the 1550 nm region when it is pumped by an external laser.
EFM Ethernet in the First Mile
EFP Ethernet Flow Point
Egress Frame A service frame sent from the service provider to the CE.
EIR Excess Information Rate — The EIR is a bandwidth profile parameter. EIR defines the
average rate in bits per second of service frames up to which the network can deliver
service frames, but without any performance objectives.
E-LMI Ethernet Link Management Interface
EMS Element Management System
E-LAN An Ethernet service type that is based on a multipoint-to-multipoint EVC.
E-Line An Ethernet service type based on a point-to-point Ethernet Virtual Connection. EPL and
EVPL are E-Line services. E-Line supports Class of Service (CoS) and VLAN tagging.
E-NNI External Network-to-Network Interface
EoS Ethernet over SONET/SDH
EPL Ethernet Private Line — EPL provides a point-to-point Ethernet connection between a pair
of dedicated User-Network Interfaces (UNIs). EPL service is specified using an E-Line
service type. EPL is implemented as a point-to-point EVC.
EP-Tree Ethernet Private Tree
ERP Ethernet Ring Protection EP-Tree (Ethernet Private Tree)— As specified in ITU-T G.8032,
ERP provides E-LAN and E-VLAN service protection for ring configurations through the
protocol protection switching mechanisms for Ethernet rings.
EVP-Tree Ethernet Virtual Private Tree
ESMC Ethernet Synchronization Messaging Channel — The ESMC, provided by a

SyncE-provisioned Z-Series PME-412 or PME-216i 10G port, supplies the clock quality level
value from node to node. It sends and receives Synchronization Status Messages (SSM) to
maintain the timing synchronization chain and allow external equipment to retrieve Line
timing from the PME 10G port.
ESP Ethernet Switched Path — ESP is a provisioned traffic-engineered unidirectional
connectivity path between two or more subscriber backbone ports that extends over a
Provider Backbone Bridge Network.
EtherType A field in the Ethernet frame that indicates which protocol is encapsulated in the payload.
ETYn ITU-T Ethernet Physical Section Layer of order n:

• n=1 (10Base)
• n=2 (100Base)
• n=3 (1000Base)
• n=4 (10GBase)
• n=5 (100GBase)
EVPL Ethernet Virtual Private Line — EVPL is another E-Line service that provides a
point-to-point Ethernet connection between two Ethernet UNIs. EVPL allows a single
physical connection (UNI) to customer premises equipment for multiple virtual
connections.
EVC Ethernet Virtual Connection — An association of two or more UNIs that limits the
exchange of frames to UNIs in the Ethernet Virtual Connection.
FCAPS Fault, Configuration, Administration, Performance, and Security
FCAPS is the ISO Telecommunications Management Network model for network
management.
FCS Frame Check Sequence
FD Flow Domain — Represents a connectionless sub-network and is defined by a set of flow

points that are available for the purpose of transferring information. An Ethernet flow
domain represents a logical Ethernet Bridge with flow points representing logical ports
on the bridge.
FDI Forward Defect Indication
FEC Forward Error Correction
FIB Forwarding Information Base — Also referred to as Forwarding Table, it provides

optimized information of destination addresses in network bridging and routing.
FLX The Z-Series FLX-216i is a flexible multi-rate OTN muxponder I-Temp module. The
FLX-216i module is a highly scalable OTN switching and muxponder optimized for
deployments in network transport applications. The environmentally hardened FLX-216i
module provides end-to-end packet and TDM/OTN transport.
FP Flow Point — An Ethernet flow point is a reference point that represents a location of
transfer of connectionless traffic units between topological components. A flow point can
represent a location of a physical port or individual sub-flow within a physical port such
as a VLAN.
FPP Flow Point Pool — The termination of a link is called a flow point pool. The FPP describes
configuration information associated with an interface, such as a UNI or NNI.
Frame Short for Ethernet frame
FRU Field Replaceable Unit
FWM Four-Wave Mixing — FWM can occur in WDM systems when multiple wavelengths
combine to form new wavelengths. FWM can decrease channel spacing of wavelengths
and have high signal power levels.
GARP Generic Attribute Registration Protocol
GbE Gigabit Ethernet
Gbps Gigabits per second
GE Gigabit Ethernet
GFEC Generic Forward Error Correction
GFP Generic Framing Protocol
GMRP GARP Multicast Registration Protocol
GUI Graphical User Interface
GVRP GARP VLAN Registration Protocol
HALT Highly Accelerated Life Testing
IGMP Internet Group Management Protocol (IGMP) snooping provides greater bandwidth
efficiency for intensive multicast applications such as IPTV. IGMP snooping reduces
bandwidth consumption to avoid flooding the network with mutlicast packets that nodes
do not need to receive. Starting in Release 10.0, Ciena PSW line cards support IGMP
snooping.
ILA In-Line Amplifier
I-SID Service Instance Identifier — The I-SID is assigned for a service. The service ID is part of
the payload in provider backbone bridges per IEEE 802.1ah. I-SIDs provide additional
network security. I-SID is a unique identifier used to ensure that users only receive traffic
and services for their respective subscription agreements.
IP Internet Protocol — Data packets are forwarded from node to node based on the
four-byte destination IP address.
IPMI Intelligent Platform Management Interface
Ingress Frame A service frame sent from the CE to the service provider network.
IS In Service
ITU-T International Telecommunication Union-Telecommunication standards sector
Kbps Kilobits per second
LAC Lambda Aggregator CWDM — The Z-Series Lambda Aggregator CWDM terminal
multiplexer module provides up to eight CWDM wavelengths for use in the Z-Series
multi-layer transport platforms. Each LAC provides optical multiplexing and
demultiplexing capability in the 1470 nm to 1610 nm band with 20 nm spacing.
LACP Link Aggregation Control Protocol (LACP) is a method of bundling several physical ports
together to form a single logical channel.
LACPDU Link Aggregation Control Protocol Data Unit — Two devices exchange LACPDUs in the
process of forming a LAG.
LAD Lambda Add/Drop — The Z-Series LAD lambda add/drop DWDM terminal multiplexer
modules are available in four or eight 10G wavelength models for use in the Z-Series
multi-layer transport platforms. Each LAD provides optical add/drop multiplexing
capability in the 1550 nm band across predefined ITU channel designations with 50 or
100 GHz spacings.
LAG Link Aggregation Group — Link Aggregation Group allows for the grouping of Ethernet
interfaces to form a single link layer interface. LAGs provide a logical aggregation of
bandwidth and link redundancy (fault tolerance).
Lambda A wavelength used to carry one or more data channels in a WDM or DWDM system.
L-AMP Lambda Amplifier — The Z-Series L-AMP is a self-contained 1 RU module that functions as
a bi-directional mid-span optical amplifier / repeater. Each 4-port L-AMP supports
bi-directional physical layer amplification of multiple DWDM wavelengths where
node-to-node spans are greater than 80 kilometers.
LAN Local Area Network
LBM Loopback Message – A Loopback Message is used to verify bidirectional connectivity

between the two maintenance entities. A MEP may send one or more LBMs to a specific
Maintenance Point (MEP or MIP).
LBR Loopback Response — When an LBM is received by a remote MEP/MIP that matches its
address, an LBR is generated. The LBR returns the information, if any, that was
transmitted in the LBM.
LER Label Edge Router
LGX Light-Guide Cross-connects
Link Links represent a connection between two nodes.
LM Loss Measurement
LME Lambda Multiplexer Element — The Z-Series 2.5G-LME4 is a 4-port muxponder

(multiplex-transponder) module with integrated OTN encoding for efficient 10G
wavelength transport in the Z-Series multi-layer transport platforms. Each module
accepts any combination of up to four 2.5G OC-48, STM-16 and OTU-1 signals which are
encoded/translated into discrete ODU-1 layers and then multiplexed into a 10G OTU2
wavelength for managed DWDM transport.
The Z-Series LME-10G10 multiservice 100G OTN muxponding module is optimized for
network transport applications. The LME-10G10 can be paired with the Z-Series DTM
100G coherent transponder module to deliver a complete end-to-end packet and OTN
transport solution. The module is supported across all Z-Series platforms.
LOS Loss of Signal
LSA Link State Announcements
LSP Label Switched Path
LSR Label Switch Router
LTM Link Trace Message — LTMs are multicast frames that a MEP transmits to follow the path
(hop-by-hop) to the target MEP.
LTR Link Trace Reply
MA Maintenance Association
MAC The Media Access Control address is a unique hardware number that is assigned to each
Ethernet device by the manufacturer.
MAU 802.3 Medium Attachment Unit
Mbps Megabits per second
MD Maintenance Domain
ME Metro Ethernet
MEF Metro Ethernet Forum
MEN Metro Ethernet Network
MEP Maintenance End Point

MEPs are edge nodes where flows originate and terminate.
MIB Management Information Base
The MIB contains managed objects that the user can access through a network
communication protocol such as SNMP.
MIP Maintenance Intermediate Points
MPO Multi-Fiber Push On connector
MS Multiplex Section
MSE Multiservice SONET/SDH Element — The Z-Series Multiservice SONET/SDH Element

(MSE-1482) is an advanced SONET/SDH aggregation and transport module, with
integrated OTN transport supporting both the Z-Series multi-layer transport platforms.
The MSE-1482 module provides a full 10G transport of SONET, SDH and Ethernet services
with non-blocking STS cross-connect for aggregation and grooming (including hair-pin
capability) across a wide range of SFP/XFP pluggable interfaces.
MSO Multiple Service Operator
MSPP Multi-Service Provisioning Platform
MST Multiple Spanning Tree
MSTI Multiple Spanning Tree Instance
MSTP Multiple Spanning Tree Protocol — As defined in IEEE 802.1Q, provides simple and full
connectivity for frames assigned to any given VLAN throughout a bridged LAN comprising
arbitrarily interconnected bridges, each operating MSTP, STP, or RSTP. MSTP allows
frames assigned to different VLANs to follow separate paths, each based on an
independent Multiple Spanning Tree Instance (MSTI), within Multiple Spanning Tree (MST)
Regions composed of LANs and or MST Bridges. These Regions and the other Bridges and
LANs are connected into a single Common Spanning Tree (CST).
MTNM Multi-Technology Network Management
MTP MTP is a high performance multi-fiber push on connector used in the Z-Series OFX-4 and
OFX-8 modules. MTP connectors comply with all MPO standards including EIA/TIA-604-5
FOCIS 5 and the IEC-61754-7.
MTU Maximum Transmission Unit
Multiplex Combining multiple signals for simultaneous transmission across a single physical
channel.
Muxponder Multiplexed transponder
NE Network Element
NEBS Network Equipment Building Systems
NMS Network Management Station

– or –
Network Management System
NNI Network-to-Network Interface — An interface used to interconnect network elements.
NTP Network Time Protocol
OADM Optical Add/Drop Multiplexer
OAM Operation, Administration and Maintenance
OAMPDU OAM Protocol Data Units are link-layer OAM messages transmitted in untagged slow
protocol frames. Per IEEE 802.3ah, OAMPDUs are normal Ethernet frames that use a
specific multicast destination address and EtherType. OAMPDUs contain control and
status information needed to monitor and troubleshoot OAM-enabled links.
OCh Optical Channel
OCM Optical Channel Monitor – The OCM provides optical performance monitoring by
measuring channel power, wavelength, and optical signal-to-noise ratio (OSNR) for each
DWDM channel.
OCP Open Compute Project
ODU Optical Data Unit
ODTU Optical channel Data Tributary Unit — An ODTU is an ODU with justification overhead
that includes the framing bytes.
OEO Optical-Electrical-Optical
OLA Optical Line Amplifier — The Z-Series OLA-200 and OLA-201 modules feature an
integrated Erbium Doped Fiber Amplifier (EDFA) for both East and West directions. The
OLA-200 and OLA-201 modules provide amplification for the LAD-40E, LAD-96E, and all
WSS modules operating in either 40-channel or 96-channel mode; and OLA-200, and
OLA-201 modules.
The OLA-010 module utilizes Raman technology and functions as an amplifier to provide
all-band wavelength coverage for up to 96 optical channels. The OLA-010 module
provides amplification for the LAD-8E, LAD-8X, LAD-40E, LAD-96E, all WSS modules, and
OLA-200, and OLA-201 modules.
OMS Optical Multiplex Section
ONIE Open Network Install Environment
OOO Optical-Optical-Optical
OOS Out of Service
OPS Optical Protection Switch — The Z-Series Optical Protection Switch (OPS) uses low-loss
switching technology to provide protection against fiber cuts and failures. It provides
redundant path protection for telecommunication transmission systems. The OPS
operates independent of rate, format, and wavelength.
The OPS provides 1+1 protection. It continuously monitors optical power on both its
primary and secondary links. If received optical power on the active link drops below a
configured threshold, the OPS switches the optical signal to the standby link within 25
ms.
OPU Optical channel Payload Unit — Per ITU-T G.709, The OPUk is the information structure
used to adapt client information for transport over an optical channel. It comprises client
information together with any overhead needed to perform rate adaptation between the
client signal rate and the OPUk payload rate and other OPUk overhead supporting the
client signal transport. This overhead is adaptation specific. OPUk capacities for k=1, k=2,
k=3 are defined.
The client signal is mapped into the OPUk. The OPUk is mapped into an ODUk and the
ODUk is mapped into an OTUk. The OTUk is mapped into an OCh.
OSC Optical Supervisory Channel — In order to supervise all network elements in the network,
without relying on an external DCN, Z-Series systems provide an Optical Supervisory
Channel (OSC). Each Z-Series shelf connects to its neighbors via a 100 Mbps Ethernet
channel carried in-band over the optical network.
The system provides an embedded OSC that is resident in each Z-Series network
element. These select Z-Series optical interfaces insert a 100 Mbps OSC on 1510 nm and
provide transparent links between each Z-Series NE in the network. The OSC is a separate
channel that carries overhead information for network management purposes that is
added and dropped at each network element. It does not affect traffic.
OSNR Optical Signal to Noise Ratio
OSP Outside Plant
OSPF Open Shortest Path First
OSS Operations Support System
OTM Optical Transport Module
OTN Optical Transport Network
OTS Optical Transport Section
OTU Optical Transport Unit
OUI Organizational Unique Identifier
OXC Optical cross-connect
Packet A formatted unit of data carried on a network.
PBB Provider Backbone Bridging
PBBPG Provider Backbone Bridged Protection Group
PBBN Provider Backbone Bridged Network
PBB-TE Provider Backbone Bridging with Traffic Engineering

PBB-TE provides carrier-class Ethernet switching and transport, allowing a separation of
the service layer from the transport layer.
PBT Provider Backbone Transport
PCP Priority Code Point is a 3-bit field storing the priority level for an Ethernet frame.
PDFAP Power Distribution, Fuse and Alarm Panel
PDU Protocol Data Units
PE Provider Edge
PEB Provider Edge Bridge
PEM Power Entry Module
PHY Ethernet Physical Layer entity
PIR Peak Information Rate — Per the MEF, the PIR is the rate up to which the network will
attempt to deliver Ethernet service frames before they are discarded. The PIR equals the
CIR plus the EIR set in the bandwidth profile and applied to the flow point. PIR represents
the maximum bandwidth for the flow point.
PLL Phase-Locked Loop
PM Performance Monitoring
PME Packet Multiplexer Element — The Z-Series PME-412 and PME-216i modules are
high-capacity Ethernet switches providing MEF-compliant services with optional carrier
Ethernet transport. PME-412 and PME-216i modules are supported in the Z-Series
multi-layer transport platforms for 10G transport using OTN over DWDM or 10GbE.
Point-to-Point EVC An EVC with exactly two UNIs.
Priority Tagging Allows the user to set a field within the Ethernet packet so that it can have a higher (or
lower) priority than other packets in the same network.
PSW Packet Switch module — Z-Series PSW modules are optimized for high-capacity Ethernet
aggregation and end-to-end packet transport solutions.
PW Pseudowire
Q-in-Q A provider bridge extension in 802.1Q VLAN tag. Also referred to a "stackable VLANs."
QoS Quality of Service
R-APS Ethernet Ring Automatic Protection Switching — The R-APS protocol manages the
protection of all nodes on the ring. R-APS coordinates protection switching on and off of
the RPL link.
RCM Ring Closure Module
RDI Remote Defect Indication
RFC Request For Comment (IETF standards tracking documents)
RHEL Red Hat Enterprise Linux
ROADM Reconfigurable Optical Add Drop Multiplexer
RPG Ethernet Ring Protection Group
RPL Ring Protection Link
RPM Red Hat Package Manager

– or –
RPM Package Manager
RPR Resilient Packet Ring
RS Regeneration Section
The Regeneration Section provides supervision of segments between optical
regenerators.
– or –
Reed-Solomon
Reed-Solomon codes are linear block codes that can detect and correct burst errors.
G.975 uses an RS code to produce redundant information that gets concatenated with
the signal to be transmitted. This additional information is used on the receive interface
to help identify and correct transmission errors. The RS encoding provides significant
correction capability and low error burst sensitivity.
RSTP Rapid Spanning Tree Protocol — As defined in IEEE 802.1D-2004, configures full, simple
and symmetric connectivity throughout a bridged LAN that comprises individual LANs
interconnected by bridges. RSTP supersedes Spanning Tree Protocol (STP). RSTP
interoperates with STP to facilitate migration. RSTP provides faster spanning tree
recovery (convergence time) after a topology change.
RU Rack Unit
One rack unit is 1.75 inches in height. Racked equipment is specified to be mounted in
increments of RUs in height.
RX Receive
SAN Storage Area Network
SAP Service Access Point
SAPI Source Access Point Identifier
SDH Synchronous Digital Hierarchy
SEP Subnetwork Edge Point
Service Frame An Ethernet frame transmitted across the UNI toward the service provider or an Ethernet
frame transmitted across the UNI toward the subscriber.
Service A UNI attribute in which the UNI can be in more than one EVC instance.
Multiplexing
Service Provider The organization providing voice, data, video, and Ethernet service(s).
SFP Small form-factor pluggable
SFT SFP Transponder — The Z-Series 8-port SFP Transponder (SFT-8) is a multi-rate module
capable of supporting drop or insert or express traffic in the Z-Series multi-layer
transport network platform. The module provides transponding for Gigabit Ethernet and
OC-3/12/48 SONET STM-1/4/16 SDH services. The module also offers 3R regeneration
(re-timing, re-shaping, re-transmitting) of up to 2.5G transmit signals.
The SFT-10G16 is a high-density, multi-rate transponder module for the Z-Series
packet-optical transport platforms (P-OTPs) that addresses a broad range of service
requirements. The SFT-10G16 performs 3R signal regeneration (re-time, re-transmit,
re-shape) and wavelength conversion in CWDM and DWDM applications.
The multi-protocol architecture of the SFT-10G16 extends the reach of client signals such
as Fiber Channel, Ethernet, SONET/SDH and Optical Transport Network (OTN) at data
rates ranging from 1.0 to 11.3 Gbps. The SFT-10G16 provides 16 SFP/SFP+ client or
line-side ports.
SLA Service Level Agreement
The agreement between the subscriber and service provider that specifies the service
level.
SMTP Simple Mail Transfer Protocol
SNMP Simple Network Management Protocol

SNMP is the standard management protocol for TCP/IP networks.
SONET Synchronous Optical Network
SSL Secured Socket Layer
SSM Synchronization Status Messaging
STP Spanning Tree Protocol — As defined in IEEE 802.1D-1998, is a link management protocol
that provides path redundancy and ensures a loop-free topology for any bridged LAN.
STP defines a tree structure by allowing bridges to communicate with each other to
discover physical loops in the network.
STS Synchronous Transport Signal
Subscriber The organization or customer purchasing or using voice, data, video, and Ethernet
services.
Alternate term: Customer
S-VID Service VLAN Identifier
S-VLAN Service VLAN
TAC Technical Assistance Center
TC Traffic Class
TCA Threshold Crossing Alert
TDM Time Division Multiplexing
TESI Traffic Engineered Service Instance

A TESI refers to a PBB-TE service instance.
TIM Trail trace Identifier Mismatch
TL1 Transaction Language One
TLS Transparent LAN Services
TLV Type, Length, and Value
TPID Tagged Protocol Identifier

By default, the VLAN tag uses the TPID field to identify the protocol type of the tag.
TPM Transport Protection Module
Transponder Optional device in a DWDM system that provides the conversion of one optical
wavelength to a precision narrow band wavelength.
TSW The TSW-10G10 transport switching module, designed for Z77 deployments, provides
grooming and aggregation of TESIs across 10G rings and add/drop capabilities. The
TSW-10G10 serves to eliminate existing fiber patches between PME (PME-412 or
PME-216i) line cards used for aggregation; freeing up multiple PME ports for Ethernet
services.
The TSW-10G10 provides four XFP ports and SFP+ ports. OTU2 and OTU2e with FEC are
supported on every TSW-10G10 port, as well as 10GbE LAN.
TTI Trail Trace Identifier
TTP Trail Termination Point
TX Transmit
T-VLAN Tunneling VLAN — Refers to IEEE 802.1Q Ethertype 0x9100, the Q-in-Q tunneling
Ethertype.
UAC User Access Control
UDP User Datagram Protocol — UDP is Internet standard network layer, transport layer, and
session layer protocols that provide basic datagram services.
UNI User-to-Network Interface — Per the MEF, the User Network Interface is the interface
used to interconnect a subscriber to its service provider. The UNI also provides a
reference point for demarcation between the network operator equipment that enables
access to the network services and the subscriber access equipment. The UNI represents
the demarcation point that indicates the location where the responsibility of the service
provider ends; and the responsibility of subscriber begins.
VCAT Virtual Concatenation
VCG Virtual Concatenation Group
VCP Virtual Container Path
VLAN Virtual LAN
VLAN ID VLAN Identifier
VNTM Virtual Network Topology Manager
VOA Variable Optical Attenuator
VPN Virtual Private Network
WDM Wave Division Multiplexing
WSS Wavelength-Selective Switching — The Z-Series WSS modules provide

wavelength-selectable switching and re-configurable optical add/drop multiplexing
(ROADM) capabilities with automated provisioning, power balancing, and monitoring.
WTR Wait to Restore
XAUI 10 Gigabit Attachment Unit Interface
XC-2800 The XC-2800 is a unified packet and Optical Transport Network (OTN) switch fabric for the
Z77 shelf (Z77 and Z77 shelf v2). The XC-2800 provides service versatility and increased
switching capacity for the Z77. The fully non-blocking design of XC-2800 switch-fabric
provides 2.8 Tbps of capacity across the Z77 backplane. Working in unison with currently
available Z-Series high-performance service interface modules, the XC-2800 can scale in
excess of two billion packets-per-second (pps) of line-rate traffic throughput.
XFP 10-Gbps Small Form-Factor optical transceiver

700-0040-17-08 - (Z-Series R10.0 Troubleshooting and Maintenance Guide) - Issue - 1.1

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

700-0040-17-08 - (Z-Series R10.0 Troubleshooting and Maintenance Guide) - Issue - 1.1

Uploaded by

Copyright:

Available Formats

Ciena Z-Series

Packet-Optical Transport Networking Platform

Z-Series Troubleshooting and

700-0040-17-08 Issue 1.1

Copyright© 2018 Ciena® Corporation. All Rights Reserved.

Legal Notices, Copyright, and Trademark

Copyright© 2018 Ciena® Corporation – All Rights Reserved

In North America 1-800-CIENA24 (243-6224)

In Europe, Middle East, and Africa 800-CIENA-24-7 (800-243-6224-7)

In Asia-Pacific 800-CIENA-24-7 (800-243-6224-7)

Sales and General Information North America: 1-800-207-3714 E-mail: sales@ciena.com

In Europe +44-207-012-5500 (UK) E-mail: sales@ciena.com

In Asia +81-3-3248-4680 (Japan) E-mail: sales@ciena.com

In India +91-22-42419600 E-mail: sales@ciena.com

In Latin America 011-5255-1719-0220 (Mexico City) E-mail: sales@ciena.com

Training E-mail: learning@ciena.com

Important! — Information that must be seriously considered.

Note: Special suggestions, advice, or information that should be

Safety Symbols and Labels

Laser Equipment Present

Electrostatic Discharge (ESD) Sensitive Equipment

Safety and Compliance Information

Warning IMPORTANT SAFETY INSTRUCTIONS

Caution Keep all ventilation openings clear and unobstructed.

Caution To prevent damage, do NOT install or remove XFP/SFP transceivers with

Caution Use copper conductors only.

Caution This equipment is suitable for installation in Network Telecommunications Facilities,

Caution This equipment is intended to be grounded to a Common Bonding Network per

Note This Class A digital apparatus complies with Canadian ICES-003.

Acknowledge an Alarm ........................................................................................................................... 52

700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 10

Aborting a Software Upgrade Task ..................................................................................................... 118

700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 11

700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 12

Figure 27: 2.5G-LME4 to LAD Functional Test Setup .................................................................................. 175

700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 13

New in Release 10.0/17.08

New in Previous Release 9.0/16.12

700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 14

New in Previous Release 9.0/16.03

New in Previous Release 8.0/15.08

700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 15

New in Previous Release 7.0/15.02

700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 16

New in Previous Release 6.0/14.07

New in Previous Release 5.4/14.05

700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 17

New in Previous Release 5.2/14.02

700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 18

New in the Previous Release 5.0/13.08

New in the Previous Release 5.0/13.06

Supported Web Browsers

700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 19

• L-AMP Installation and Safety Guide

700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 20

Loopback Tests for Transport

• DTM-8 • SFT-8 • MSE-1482 • PSW-10G20

700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 21

700-0040-17-08 Issue 1.1 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 22

The following diagrams show examples of the supported loopback types.

Example 1: Terminal Loopback

Z-Series shelf Z-Series shelf

Example 2: Non-Transparent Facility Loopback