009 2004 191 - CoreDirector

COREDIRECTOR
MULTI-SERVICE OPTICAL SWITCH
COREDIRECTOR CI
MULTI-SERVICE OPTICAL SWITCH
Release 4.0
MAINTENANCE AND UPGRADE MANUAL

CIENA Part Number: 009-2004-191
February 11, 2005 Revision A
Ciena Confidential and Proprietary
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 PRINTING; HOWEVER, THE INFORMATION CONTAINED IN THIS DOCUMENT IS SUBJECT TO CHANGE. Copyright 2005 Ciena Corporation Unpublished 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. Security Ciena cannot be responsible for unauthorized use of equipment and will not make allowance or credit for unauthorized use or access. Contacting Ciena
Corporate Headquarters 410-694-5700 www.ciena.com
Customer Technical Support/Warranty In North America In Europe, Middle East, and Africa In Asia-Pacific Sales and General Information In North America In Europe In Asia In Latin America Training and Documentation Training Documentation 877-Ciena-TD (243-6283) or 410-865-8990 877-Ciena-TD (243-6283) or 410-694-8125 E-mail: techtng@ciena.com E-mail: techpubs@ciena.com 1-800-Ciena24 (243-6224) 410-865-4961 800-Ciena-24-7 (800-243-6224-7) +44-207-012-5508 800-Ciena-24-7 (800-243-6224-7) +81-3-3248-4743 410-694-5700 410-694-5700 +44-207-012-5500 (UK) +81-3-3248-4680 (Japan) 561-620-1925 E-mail: Ciena24@ciena.com E-mail: Ciena24@ciena.com E-mail: Ciena24@ciena.com E-mail: sales@ciena.com E-mail: sales@ciena.com E-mail: sales@ciena.com E-mail: sales@ciena.com E-mail: sales@ciena.com
For additional office locations and phone numbers, please visit the Ciena web site at: www.ciena.com.
CoreDirector Switch
Preface
PREFACE
DISCLAIMER
Portions of this document are intended solely as an outline of methodologies to be followed while working with CoreDirector Multi-Service Optical Switches and CoreDirector CI Multi-Service Optical Switches. It is not intended as a step-by-step guide or a complete set of all procedures necessary and sufficient to do such work. While every effort has been made to ensure that this document is complete and accurate at the time of printing, the information that it contains is subject to change. Ciena is not responsible for any additions to or alterations of the original document. Networks vary widely in their configurations, topologies, and traffic conditions. This document is intended as a general guide only. It has not been tested for all possible applications, and it may not be complete or accurate for some situations. Procedures and information contained in this document for which this disclaimer applies are preceded by the Disclaimer Banner, shown below.
R E F E R T O D I S C L A I M E R I N P R E F A C E !
Users of this document are urged to heed warnings interspersed throughout the document, such as traffic disruption warnings.
COMPLIANCE INFORMATION
Food and Drug Administration (FDA) Laser Safety Warning
This product contains a laser diode. Ciena Corporation strongly recommends that users, maintenance, and service personnel comply with the following standards and regulations in the design, modification, operation, maintenance, and service of lasers and fiber-optic devices: Jurisdiction
Federal, US Federal, US United States International European Regulation Guidelines Standard Standard Standard
Type
OSHA
Title
FDA 21 CFR 1040.10/.11 ANSI Z136 series IEC 825 series EN 60825
It is further recommended that the owner of this equipment determine and ensure conformance with any specific and applicable local regulations.
LASER RADIATION EXPOSURE

Warning:
Use of controls or adjustments or performance of procedures other than those specified herein may result in hazardous radiation exposure.
Class 1 Laser Product Notice

The Ciena Corporation CoreDirector product is a Class 1 Laser product as identified by US FDA/CDRH 21CFR1040.10/.11; Class 1 Laser product as defined by IEC825/EN-60825; and OFCS SG1 as defined by ANSI Z136.1/.2/. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
Preface
CoreDirector Switch
Part 15 of the Federal Communications Commission (FCC): Interference

Every effort has been made to ensure that this equipment is designed to comply with the limits for a Class A digital device, as described in the FCC Rules. Equipment limitations are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment, if not installed and used properly, and in accordance with guidelines established by Ciena Corporation may cause interference with other communications equipment. Operations of this equipment in a residential environment may cause interference; it is the responsibility of the user to correct the interference at his own expense.
Environmental Impact Statement

Ciena equipment contains no hazardous materials as defined by the United States Environmental Protection Agency (USEPA). Ciena recommends that all failed product be returned to Ciena for failure analysis and proper disposal.
Toxic Emissions
Ciena equipment releases no toxic emissions.
Telcordia Document Standards

The format and structure of this document is derived from the Telcordia Generic Requirements for SupplierProvided Documentation, GR-454-CORE.
CISPR Declaration of Conformity

This product meets the CISPR 22 Class A standards in accordance with EMC Directive 89/336/EEC. It is specifically designed to operate in a public utility environment. The use of this product in a domestic or residential environment or connected to a low voltage power network that can be shared with domestic or residential equipment is prohibited. The manufacturer (Ciena Corporation) recommends that Ciena be contacted regarding restrictions on the resale, relocation, or change of intended use of this product.
TRADEMARK ACKNOWLEDGEMENTS
Ciena is a registered trademark of Ciena Corporation. CoreDirector Multi-Service Optical Switch and CoreDirector CI Multi-Service Optical Switch are trademarks of Ciena Corporation. Windows 95/98/2000, Windows NT, and Windows XP are registered trademarks of the Microsoft Corporation. Microsoft is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries. UNIX is a registered trademark licensed exclusively through X/Open Company, Ltd. Pentium is a registered trademark of Intel Corporation. Sun, Sun Microsystems, JAVA, Java Secure Socket Extension, and JAVAX are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. or other countries. This product includes code licensed from RSA Data Security.
ii
Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
CoreDirector Switch RELEASE NOTES AND DOCUMENT UPDATES
Preface
The hard copy and Compact Disc Read Only Memory (CD-ROM) versions of this document are revised only at major releases and, therefore, may not always contain the latest product information. As needed, Software Release Documents (SRDs), Hardware Release Documents (HRDs), Application Notes, Field Service Bulletins (FSBs), and/or Document Maintenance Bulletins (DMBs) will be provided between major releases to describe any new information or document changes. The latest online version of this document and all release notes can be accessed from the Ciena web site at http://www.ciena.com.
PRINTING HISTORY
The following information provides the printing history of this document. Issue/Revision
Revision A
Release Date
February 2005
Content Description
First formal release.
RELATED DOCUMENTATION
All Ciena documentation is available in both hard copy and on CD-ROM. The following list provides a brief description of the related documents. Additional supporting documentation is available through our web site at http://www.ciena.com. CoreDirector CI Multi-Service Optical Switch - Hardware Installation Manual CoreDirector CI Multi-Service Optical Switch - NA and ETSI Rack Package Hardware Installation Manual CoreDirector Multi-Service Optical Switch - Turn-Up and Test Manual CoreDirector Multi-Service Optical Switch - System Description Manual CoreDirector Multi-Service Optical Switch - Alarm and Trouble Clearing Manual CoreDirector Multi-Service Optical Switch - Maintenance and Upgrade Manual CoreDirector Multi-Service Optical Switch - TL1 Interface Manual CoreDirector Multi-Service Optical Switch - Node Manager User Guide CoreDirector Multi-Service Optical Switch - Software Release Documents (SRDs) CoreDirector Multi-Service Optical Switch - CoreDirector Designer Software Tool User Guide Ciena Installation Workmanship Standards Standard Cleaning & Equipment Safety Practices
DOCUMENT ORDERING INFORMATION

To order additional documentation, the user may contact the local sales representative or Ciena through the contact numbers and/or e-mail addresses listed on the back of the cover.
DOCUMENT COMMENTS
Ciena appreciates all comments that will help us improve our documentation quality. The user can submit comments through our web site (http://www.ciena.com) or with the Documentation Improvement Request form included with this document.

iii
Preface ADDITIONAL PRODUCT INFORMATION
CoreDirector Switch
Additional product information can be obtained by contacting the local sales representative or Ciena through the contact numbers and/or e-mail addresses listed on the back of the cover.
iv
TOC
CoreDirector Switch Table of Contents
TABLE OF CONTENTS
PREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i LIST OF FIGURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix LIST OF TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv CHAPTER 1 OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Required Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Software Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 hardware features Of The CoreDirector Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2 Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Equipment Shelves and Component Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12 CHAPTER 2 OPERATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Hardware Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 LEDs on Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2 CHAPTER 3 MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Preventive Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Fan Filter Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1 Corrective Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
System Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 TOPs for Maintenance Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 CHAPTER 4 TASK ORIENTED PRACTICES (TOPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 TOP 001D Measuring Optical Power Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4- 3 TOP 007D Using the ACO Switch to Turn Off an Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 7 TOP 015D Verifying -48 VDC Supply Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 9 Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
TOC
Table of Contents CoreDirector Switch
TOP 016D Verifying System Grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 11 TOP 032D Removing and Installing an Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 15 TOP 072D Ciena Return Material Authorization (RMA) Procedure . . . . . . . . . . . . . . . . . . . . . . 4- 17 TOP 168D Removing and Installing a Circuit Breaker Module . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 19 TOP 169D Removing and Installing a Cooling Fan Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 23 TOP 170D Removing and Installing a Control Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 27 TOP 171D Removing and Installing a Switch Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 35 TOP 172D Removing and Installing an Optical Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 41 TOP 173D Removing and Installing a Line Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 53 TOP 174D Removing and Installing a Timing Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 73 TOP 175D Removing and Installing a PDU Display Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 77 TOP 176D Removing and Installing a Fan Power Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 81 TOP 177D Removing and Installing a CoreDirector CI I/O Module . . . . . . . . . . . . . . . . . . . . . . 4- 85 TOP 178D CoreDirector Switch Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 89 TOP 183D Removing and Connecting the Alarms and Parallel Telemetry Cable . . . . . . . . . . .4- 91 TOP 185D Removing and Installing the PDU-B/P Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4- 97 TOP 187D Test LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 99 TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch . . 4- 101 TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface . . . . . . . .4- 107 TOP 207D Adding Channel Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 111 TOP 208D Configuration Database Backup and Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 115 TOP 209D Setting Up a CoreDirector Switch for Modem Access. . . . . . . . . . . . . . . . . . . . . . . . 4- 121 TOP 210D CoreDirector Switch Software Upgrade and Restore . . . . . . . . . . . . . . . . . . . . . . . . 4- 127 TOP 211D Software In-Service Reversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 143 TOP 217D CoreDirector Switch Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 151 TOP 218D Pack Up a CoreDirector Switch System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 155 TOP 220D Test Line Modules and Optical Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4- 161 TOP 221D Test Optical Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 177 TOP 223D Change CoreDirector Switch Name/IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 181
vi
TOC
CoreDirector Switch Table of Contents
TOP 261D Change NE CLI Login User ID and/or Password . . . . . . . . . . . . . . . . . . . . . . . . . . .4- 185 TOP 262D Recovery from Dual CM Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4- 187 TOP 270D Resetting the Primary Control Module (CM Switch) . . . . . . . . . . . . . . . . . . . . . . . . . 4- 195 TOP 271D Resetting the Secondary Control Module (CM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 199 TOP 274D IO Panel EEPROM Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 203 TOP 275D Change CoreDirector Initial Install Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 205 TOP 276D LM-8 to LM-16 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 209 TOP 278D Handling Circuit Packs Properly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4- 215 TOP 279D Prepare Site Terminal (or Laptop) for Software Transfer . . . . . . . . . . . . . . . . . . . . . 4- 223 TOP 280D Resetting the Primary Timing Module (TM Switch). . . . . . . . . . . . . . . . . . . . . . . . . . 4- 225 TOP 281D Resetting the Secondary Timing Module (TM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 229 TOP 282D Decommissioning a CoreDirector Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 233 TOP 283D FTP Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 243 APPENDIX A COREDIRECTOR TEST DATA SHEETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 Using Test Data Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 APPENDIX B COREDIRECTOR CI TEST DATA SHEETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 Using Test Data Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1 Abbreviations and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-5 INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-1

vii
TOC
Table of Contents CoreDirector Switch
THIS PAGE INTENTIONALLY LEFT BLANK
viii
LOF
CoreDirector Switch
FIGURE #
LIST OF FIGURES
List of Figures
PAGE #
FIGURE NAME
Figure 1-1. Figure 1-2. Figure 1-3. Figure 1-4. Figure 1-5. Figure 1-6. Figure 1-7. Figure 1-8. Figure 1-9. Figure 1-10. Figure 1-11. Figure 1-12. Figure 1-13. Figure 1-14. Figure 2-1. Figure 2-2. Figure 2-3. Figure 2-4. Figure 2-5. Figure 2-6. Figure 2-7. Figure 2-8. Figure 2-9. Figure 4-1. Figure 4-2. Figure 4-3. Figure 4-4. Figure 4-5. Figure 4-6. Figure 4-7. Figure 4-8. Figure 4-9. Figure 4-10.
CoreDirector Switch Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 CoreDirector CI Switch Display Panel Controls . . . . . . . . . . . . . . . . . . . . . . . . 1-3 CoreDirector CI Switch PDU Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 CoreDirector Switch PDU Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 CoreDirector CI Switch Display Panel Indicators . . . . . . . . . . . . . . . . . . . . . . . 1-4 CoreDirector Switch PDU (Rear View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 I/O Panel in the CoreDirector Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 I/O Module in the CoreDirector CI Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 I/O Panels for the CoreDirector Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 I/O Modules for the CoreDirector CI Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 CoreDirector Switch Shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13 Slot Numbering in the CoreDirector Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14 Slot Numbering in the CoreDirector CI Switch . . . . . . . . . . . . . . . . . . . . . . . . . 1-15 Naming Optical Modules and Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16 Timing Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Optical Module LEDsOC-48 and OC-3/12 . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Optical Module LEDsOC-192 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Switch Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Control Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 LM-2 Line Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 LM-8 Line Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 LEDs on the LM-20-E Line Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 LM-16 Line Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Optical Power Meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 CoreDirector Switch Power Distribution Unit -48 VDC Connections . . . . . . . . 4-10 CoreDirector CI Switch Power Distribution Unit -48 VDC Connections . . . . . . 4-10 CoreDirector Switch System Grounding Scheme (Typical) . . . . . . . . . . . . . . . 4-12 CoreDirector CI Switch System Grounding Scheme (Typical) . . . . . . . . . . . . . 4-13 Air Filter Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16 CoreDirector Switch CFU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24 CoreDirector CI Blower Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25 CM Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33 SM Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39

ix
LOF
List of Figures
FIGURE #
Figure 4-11. Figure 4-12. Figure 4-13. Figure 4-14. Figure 4-15. Figure 4-16. Figure 4-17. Figure 4-18. Figure 4-19. Figure 4-20. Figure 4-21. Figure 4-22. Figure 4-23. Figure 4-24. Figure 4-25. Figure 4-26. Figure 4-27. Figure 4-28. Figure 4-29. Figure 4-30. Figure 4-31. Figure 4-32. Figure 4-33. Figure 4-34. Figure 4-35. Figure 4-36. Figure 4-37. Figure 4-38. Figure 4-39. Figure 4-40. Figure 4-41. Figure 4-42. Figure 4-43.
CoreDirector Switch
PAGE #
FIGURE NAME
Fiber Moved Out of the Path of an OM to Be Removed . . . . . . . . . . . . . . . . . . 4-44 Connecting an SC OM to an LC Site Fiber . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47 Connecting an LC OM to an SC Site Fiber . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47 LM Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63 Module Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68 Alignment Plate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70 Bridge Module Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71 TM Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76 Power Distribution Unit for CoreDirector Switch . . . . . . . . . . . . . . . . . . . . . . . . 4-79 CoreDirector CI Alarm Cable Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92 CoreDirector CI Alarm Cable Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92 CoreDirector Alarms Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-95 CoreDirector Alarms Cable Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96 LED Test Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-100 Control Module (CM) Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103 CoreDirector Switch I/O Panel Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103 I/O Panel Top View (CoreDirector Switch) . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104 I/O Panel Connectors (CoreDirector CI Switch) . . . . . . . . . . . . . . . . . . . . . . . . 4-104 CM CLI Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-105 CoreDirector Switch I/O Panel Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108 I/O Panel Connectors on the CoreDirector Switch . . . . . . . . . . . . . . . . . . . . . . 4-109 I/O Panel Connectors on the CoreDirector CI Switch . . . . . . . . . . . . . . . . . . . . 4-109 Backup and Restore Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-117 CoreDirector Switch Rear I/O Panel Location . . . . . . . . . . . . . . . . . . . . . . . . . 4-125 CoreDirector Switch Rear I/O PanelTop View . . . . . . . . . . . . . . . . . . . . . . . 4-125 CM CLI Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-126 Software Reversion Warning Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-147 Empty Database Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-147 CoreDirector Switch Caster Assemblies (Installed) . . . . . . . . . . . . . . . . . . . . . 4-156 Latches on the Shipping Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-157 Ramp for Unloading the Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-157 Shockwatch Label Inside the Shipping Crate . . . . . . . . . . . . . . . . . . . . . . . . . . 4-158 Opening the Inner Brace Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-158
x
LOF
CoreDirector Switch
FIGURE #
Figure 4-44. Figure 4-45. Figure 4-46. Figure 4-47. Figure 4-48. Figure 4-49. Figure 4-50. Figure 4-51. Figure 4-52. Figure 4-53. Figure 4-54. Figure 4-55. Figure 4-56. Figure 4-57. Figure 4-58. Figure 4-59. Figure 4-60. Figure 4-61. Figure 4-62. Figure 4-63. Figure 4-64. Figure 4-65. Figure 4-66. Figure 4-67.
List of Figures
PAGE #
FIGURE NAME
OM Test with Cross Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-164 OM Test with Jumpers and Cross Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-164 Complete LM Test Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-166 Two LM Test Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-167 Test Set-up (Diagnostic Loopback) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-170 Test Set-up (Fiber Jumper and Cross Connect) . . . . . . . . . . . . . . . . . . . . . . . . 4-171 Test Set-up (Fiber Jumpers, Diagnostic Loopback, and Cross-Connect) . . . . 4-172 Test Setup for One 16-port (LM-16) Line Module . . . . . . . . . . . . . . . . . . . . . . . 4-174 Test Setup for Two Integrated Optics Line Modules (LM-16 Shown) . . . . . . . . 4-175 CoreDirector Switch CM CLI Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-186 Improper Circuit Pack Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-217 Inserting a Circuit Pack into an Antistatic Bag . . . . . . . . . . . . . . . . . . . . . . . . . 4-218 Removing an OM from Its Antistatic Bag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-218 Correct Connector Block Alignment Planar View (LM-8 shown) . . . . . . . . . . . 4-219 Correct Connector Block Alignment Planar Top View (LM-8 shown) . . . . . . . . 4-219 Module Insertion (CM and LM/TM Shown) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-220 Installing OMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-221 Back Panel Attached to Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-237 Ramp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-238 Ramp Blocks in Place . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-238 Rear Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-239 Front and Top Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-239 Side Braces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-240 Bolts on the Side Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-241

xi
LOF
List of Figures CoreDirector Switch
xii
LOT
CoreDirector Switch
TABLE #
LIST OF TABLES
List of Tables
PAGE #
TABLE NAME
Table 1. Table 2. Table 3. Table 4. Table 5. Table 7. Table 8. Table 9. Table 1-1. Table 1-2. Table 1-3. Table 1-4. Table 2-1. Table 2-2. Table 2-3. Table 2-4. Table 3-1. Table 4-1. Table 4-2. Table 4-3. Table 4-4. Table 4-5. Table 4-6. Table 4-7. Table 4-8. Table 4-9. Table 4-10. Table 4-11. Table 4-12. Table 4-13. Table 4-14. Table 4-15. Table 4-16.
Topics Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Maintenance and Upgrade Chapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv CoreDirector Switch R4.0 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi Revision Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii GUI Navigation Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Text Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix SONET and SDH Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Module Environmental Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv CoreDirector Switch Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Basic Module States Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Module Boot Sequence Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Redundant Module States Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Operations: Software- and Hardware-Related TOPs . . . . . . . . . . . . . . . . . . . . 2-1 Line Module LED States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 LM-20-E Line Module Optical Port LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 LM-20-E Line Module Optical Port LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Maintenance: Hardware and Software Related TOPs . . . . . . . . . . . . . . . . . . . 3-2 Task-Oriented Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Optical Output Power Ranges for OMs and Optical Ports . . . . . . . . . . . . . . . . 4-6 Mapping Primary SMs to Supported LM OMs/Ports on CoreDirector Switch . 4-36 Mapping Primary SMs to Supported LM OMs/Ports on CoreDirector CI Switch4-37 Pigtail Cables and Adapter for OM Installation. . . . . . . . . . . . . . . . . . . . . . . . . 4-46 10G Optical Module Input Power Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48 Optical Receiver Power Ranges for OMs and Optical Ports . . . . . . . . . . . . . . 4-49 LM-16 Optical Port LED States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66 CoreDirector CI Alarm Cable Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . 4-93 25-Pin Connector Pin Assignments for the RS-232 Serial Cable . . . . . . . . . . 4-102 RS-232 Craft Connector Pin Designation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-105 Mapping Primary SMs to Supported LM OMs/Ports on CoreDirector Switch . 4-112 Mapping Primary SMs to Supported LM OMs/Ports on CoreDirector CI Switch4-112 DIP Switch Settings for the Modem to PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-122 Software Command Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-123 Modem to CoreDirector Switch DIP Switch Settings . . . . . . . . . . . . . . . . . . . . 4-123

xiii
LOT
List of Tables
TABLE #
Table 4-17. Table 4-18. Table 4-19. Table 4-20. Table 4-21. Table 4-22. Table 4-23. Table 4-24. Table 4-25.
CoreDirector Switch
PAGE #
TABLE NAME
RS-232 Craft Connector Pin Designation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124 Invalid Special Characters/Characters to Avoid . . . . . . . . . . . . . . . . . . . . . . . . 4-134 Handling Spaces by Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134 Software Upgrade Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-135 Optical Output Power Ranges for OMs and Optical Ports . . . . . . . . . . . . . . . . 4-163 Optical Power Level Data Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-169 Optical Output Power Ranges for OMs and Optical Ports . . . . . . . . . . . . . . . . 4-178 CM Branding Mismatch Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-188 Circuit Pack Installation TOPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-219
Data Sheet A-1. CoreDirector Site Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 Data Sheet A-2. CoreDirector Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 Data Sheet A-3. CoreDirector Spare Hardware Inventory and Testing . . . . . . . . . . . . . . . . . . . A-17 Data Sheet A-4. Module LED Status and Redundancy Tests . . . . . . . . . . . . . . . . . . . . . . . . . . A-18 Data Sheet A-5. LM and OM LED Status and Functional Test. . . . . . . . . . . . . . . . . . . . . . . . . . A-19 Data Sheet A-6. CoreDirector CM Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . A-38 Data Sheet B-1. CoreDirector CI Site Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 Data Sheet B-2. CoreDirector CI Timing Cable Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4 Data Sheet B-3. CoreDirector CI Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5 Data Sheet B-4. CoreDirector CI Spare Hardware Inventory and Testing . . . . . . . . . . . . . . . . . B-7 Data Sheet B-5. Module LED Status and Redundancy Tests . . . . . . . . . . . . . . . . . . . . . . . . . . B-8 Data Sheet B-6. LM and OM LED Status and Functional Test. . . . . . . . . . . . . . . . . . . . . . . . . . B-8 Data Sheet B-7. CoreDirector CI CM Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . B-13
xiv
CoreDirector Switch
Introduction
INTRODUCTION
OVERVIEW
This section provides the document revision history, documentation conventions used in Ciena product technical publications, important safety information, and environmental impact information about the CoreDirector Multi-Service Optical Switch and CoreDirector CI Multi-Service Optical Switch. This manual includes the information listed in Table 1. Table 1. Topics Table Topic About This Manual Related Publications Prerequisites Revision History Documentation Conventions General Safety Precautions Page page xv page xvi page xvi page xvii page xvii page xx
ABOUT THIS MANUAL

This manual is organized in chapters which describe the CoreDirector Switch maintenance and upgrade procedures. The term CoreDirector Switch is used in this document to represent, unless otherwise stated, both the CoreDirector Switch and the CoreDirector CI Switch products. Table 2 describes the contents of each chapter. Table 2. Maintenance and Upgrade Chapters Chapter 1Overview 2Operations 3Maintenance 4TOPs Appendix A Appendix B Glossary Description Summarizes the CoreDirector Switch hardware and software features that are used in operation and maintenance procedures. Lists the Task-Oriented Practices (TOPs) specific to CoreDirector Switch operation. Lists the TOPs specific to maintaining and upgrading the CoreDirector Switch. Contains all CoreDirector Switch TOPs. CoreDirector Switch Test Data Sheets, provides forms for recording test data for the CoreDirector Switch. CoreDirector CI Switch Test Data Sheets, provides forms for recording test data for the CoreDirector CI Switch. Lists abbreviations, acronyms, and technical terms, and provides definitions.

xv
Introduction RELATED PUBLICATIONS

Table 3 lists related CoreDirector Switch technical publications.
CoreDirector Switch
Table 3. CoreDirector Switch R4.0 Documentation Part Number Title
CoreDirector Switch/CoreDirector CI Switch Common 009-2004-189 System Description Manual 009-2004-192 Alarm and Trouble Clearing Manual 009-2004-191 Maintenance and Upgrade Manual 009-2004-193 Node Manager User Manual 009-2004-194 TL1 Reference Manual 009-2004-190 Turn-up and Test Manual CoreDirector Switch Specific 009-2004-186 Hardware Installation Manual CoreDirector CI Switch Specific 009-2004-187 NA and ETSI Rack Package Hardware Installation Manual 009-2004-188 Hardware Installation Manual
PREREQUISITES
The following prerequisites must be met in order to successfully operate the CoreDirector Switch using procedures contained in this manual.
!
The CoreDirector Switch system must be installed in accordance with the appropriate CoreDirector Switch installation manual. The CoreDirector Switch system must be turned up and tested in accordance with the Turn-up and Test Manual. Node Manager must be installed and running on either a laptop or site terminal. The revision level of the Node Manager software must be compatible with the CoreDirector Switch. A File Transfer Protocol (FTP) application (for example, WFTPD software by Texas Imperial Software or another FTP package) must be made available to support software upgrades that may be required. The user must be Ciena-certified. The user must have the appropriate CoreDirector Switch Node Manager user privileges to perform certain tasks. The user must have a knowledge of: The operating system on which Node Manager resides (for example, Windows NT, Windows 2000, Windows XP, or UNIX operating systems). Digital optical test set usage. CoreDirector Switch Node Manager software.
! !
xvi
CoreDirector Switch REVISION HISTORY

Overview
Introduction
This section describes how Ciena product and documentation revision numbers are assigned and provides the revision history of this manual.
Revision Number Sequencing

Each Ciena hardware release is identified by a release level in the format of RX.Y. Examples are R2.1 and R3.0. Hardware documentation is updated and delivered to support each release. New software is delivered concurrently with a new hardware release. Ciena software releases use the format of RX.Y.Z (where Z indicates a maintenance release). Examples are R2.0.0, R2.1.0, and R2.1.5. Software documentation is updated and delivered to support each RX.Y release. Maintenance release data is captured in a Software Release Document (SRD) shipped with the software. Note: Ciena technical documentation is not revised to reflect .Z maintenance (or bug fix) releases, as all technical documentation is written to describe the features and functionality as they were designed.
The revision number sequencing format of Ciena technical publications is as follows:

! ! ! ! !
Rev 001 - First preliminary release Rev 002 - Second preliminary release (if required) Rev A - First formal release Rev B - Second formal release (and so forth)
Documents released as preliminary versions may be incomplete or may contain unverified information. They are subject to revision.
Revision History of This Manual

Table 4. Revision Log Revision 001 A Release October 2004 Preliminary release February 2005 General Availability release Impact
DOCUMENTATION CONVENTIONS
Overview
This section describes how Ciena technical documentation represents screen elements, user inputs, system prompts and responses, commands, and procedures related to Ciena applications that are based on a Graphical User Interface (GUI) (for example, Node Manager or Modeling and Planning Suite).

xvii
Introduction
GUI Navigation Elements
Table 5. GUI Navigation Elements Item Menu bar Description To use...
CoreDirector Switch
Example In the MPS Network Topology window: File > Load Map instructs the user to open the File menu, and then select Load Map. In Node Manager: Go > Administration > Security > Accounts instructs the user to click the Security tab, and then click the Accounts tab. In Node Manager: From the Go > Administration > Timing References > Timing Admin tab, select a timing reference in the List frame. The selected timing input populates the Details frame. In Node Manager: From the Go > Diagnostics > TAP Connection tab, select New in the List frame. The Details Frame provides fields for setting up a new TAP connection.
At the top of the main Pull-down menus: open the window, beneath the menu with a single mouse title bar. Can consist click, then click a submenu. of either pull-down menus or tabs (see Tabs below). Displayed horizontally across the top of the window, in the List frame and/or Details frame. Top portion of the right side of the window. Typically, a summary table. Items are read-only. May contain additional tabs. Click the tab to display groups of related information identified on the tabs label.
Tabs
List frame
Click an item in the List frame table. Table items can be created, deleted, filtered, and sorted.
Details frame Bottom portion of the right side of the window. May contain additional tabs.
Click an item in the List frame table. Details are displayed. White text fields can be modified; yellow text fields cannot be changed. To save or invoke changes, click Apply.
Equipment Tree
Directory tree (like Windows Explorer)
Click a handle to expanded In MPS: The Network Element selection tree in the MPS Network or collapsed a branch. Explorer window. Then click the desired element, details are displayed in the List and Details frames.
Inputs and Responses

Throughout this manual, user inputs and system messages are represented with different text styles. Table 6. Inputs and Responses
Item
User inputs System prompts System responses System messages with a variable in the string Bold Courier Courier
Font
Example
Type the IP Address. Enter selection: Enter selection: [ ] network is down. Main or auxiliary network is down. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
[ ] standing in for the variable; a description of the variables in Italic
xviii
CoreDirector Switch
Use of Bold Text
Introduction
In this manual, bold text is used to call special attention to items, such as labels and commands, displayed on the screen or, in the case of actions the user must execute, keyboard key strokes. Table 7. Text Elements Screen Element Tab Dialog box title Command buttons Keyboard key strokes Example In Node Manager, click the Monitoring tab. The Logon Successful dialog box opens. Click Accept to apply changes. Press Ctrl+V to paste the copied selection, and then press Enter.
Drop-down box selections Select Unlocked or Locked from the list.
Terminology
SONET AND SDH Throughout this manual are terms that are specific to SONET or SDH. When a sentence includes two or more of these terms, the word or separates the SONET term (always the first term or terms) and the SDH term (always the second term or terms); for example: Code Violations or Background Block Errors. In the tables that explain the attributes of the CoreDirector Switch Node Manager screens, a center column identifies whether the attribute applies specifically to SONET or SDH, or how the attribute applies differently in each case. Table 8. SONET and SDH Terms Attribute Size Of CTP Definition Displays the number of STS1s or STM-1s constituting this termination point. SONET SDH Values are 1, 3c, 12c, 48c, and 192c. Values are 1, 4, 16, and 64.
COREDIRECTOR SWITCH AND COREDIRECTOR CI SWITCH Unless explicitly noted, in this manual the term CoreDirector Switch refers to both the CoreDirector Switch and CoreDirector CI Switch. Differences in equipment handling or procedures between the two systems are noted; those relevant to the CoreDirector Switch are addressed first, then the CoreDirector CI Switch. The CoreDirector Switch has five equipment shelves, and the CoreDirector CI Switch has three equipment shelves. The screens displayed in this manual reflect these mechanical differences.

xix
Introduction GENERAL SAFETY PRECAUTIONS

Overview
CoreDirector Switch
To avoid injury to personnel and/or damage to the equipment, the following precautions must be adhered to, as well as the safety procedures established by the organization in which the system is installed. The general safety precautions discussed include:
! ! ! ! ! ! ! ! !
General Warnings and Cautions Voltage Precaution Laser Precautions Lift Precautions Static Electricity Precautions Optical Fiber Handling Precautions Fiber Break and Damaged Fiber Precautions Precautions for Handling and Storing Modules Traffic Disruption Precaution
General Warnings and Cautions

Throughout this manual, danger and caution notices are provided in procedures as appropriate. These notices emphasize the safety considerations that should be followed to minimize the potential for personal injury and/or equipment damage.
Voltage Precaution RISK OF PERSONAL INJURY

Warning: Negative 48 volts DC is present in the equipment. Contact can cause personal injury. Take appropriate safety precautions.
A voltage of -48 volts DC is present in the CoreDirector Switch as a power source for normal equipment operation. Depending on the facility, a voltage of either 120 or 230 volts AC is also present for test equipment, tools, and lighting. Personnel should exercise safety precautions when connecting, measuring, and disconnecting all voltage supply lines. Observe the following precautions to avoid voltage shock:
! ! ! !
Never use both hands when working on or near a voltage source. Use the buddy system when working around voltage sources. Ensure that rescue and first aid equipment is available and accessible. Remove watches, rings, necklaces, and other conductive devices that might come in contact with live voltages. Before activating circuits, ensure that other personnel are not in contact with voltage sources. Deactivate power whenever possible before performing maintenance on system components.
! !
xx
CoreDirector Switch
Laser Precautions LASER RADIATION AVOID EXPOSURE TO BEAM CLASS 1 LASER PRODUCT
Introduction
Warning:
Laser emissions may cause eye damage. Never look directly into fiber connectors. Always assume that laser radiation is present even when equipment is turned off. The CoreDirector Switch uses infrared light energy to interface the modules in the system with the external fiber plant and client equipment. The transmission of infrared light energy between the fiber plant and client equipment is performed by fiber cables. The infrared light energy used in Ciena products falls within the invisible portion of the electromagnetic spectrum, and this energy is of sufficient magnitude to cause eye injury with indirect exposure and/or skin injury with direct exposure. When working with Ciena equipment, the following general laser precautions must be observed.
!
Ensure that all operators and technicians have satisfactorily completed an approved training course before they work on the system. Never permit unauthorized or untrained personnel to perform service, maintenance, or restoration. Exclude all unauthorized personnel from the immediate area of lightwave transmission systems during installation and service. Never disconnect a lightwave cable or look into the optical connector. Be careful to avoid indirect eye exposure or direct skin exposure to unprotected optical connectors. Wear laser safety goggles whenever in close proximity to lasers. Install protective covers/caps on all optical connectors when they are not in use. Because laser energy is invisible, always assume that exposed optical connectors and cables are energized. Before cleaning a fiber or connector, always make an optical power measurement and/or visual inspection to ensure that the fiber is not energized. Never view an optical fiber with a direct magnification fiber scope without verifying that all lightwave sources on the fiber are turned off.
! !
! ! !
Lift Precautions LIFT WARNING

Warning: The equipment is heavy. Unassisted or improper lifting techniques can cause personal injury. Take appropriate safety precautions.
When lifting or handling materials manually, use only methods that ensure personal safety and protection of the material. Never attempt to lift objects that are too bulky or heavy to handle safely. Whenever possible, push loads instead of pulling them. Pushing uses the strong leg muscles, whereas pulling uses the back muscles, which can be easily strained.

xxi
Introduction
Observe the following precautions when lifting an object:
!
CoreDirector Switch
Before lifting the load, inspect the route over which the load will be carried for obstructions or spills that could cause slipping or tripping. Inspect the load for sharp edges before lifting. Identify good handholds on the load; these handholds must be able to support the full weight of the object. Avoid twisting or bending when lifting, and carry the load close to the body. When team-lifting, ensure that the load is raised at the same rate and that it rides level to ensure that each person carries equal weight.
! !
! !
Static Electricity Precautions Risk of Damage to Circuit Packs and Backplanes

Caution: This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures.
A damaging static electrical charge can be generated by the rubbing and sliding of materials against each other. Different materials have different potentials of generating and holding a static electric charge. Plastic materials similar to nylon and polyester are capable of generating and holding a potentially large damaging static electricity charge. Materials similar to cotton do not typically have the potential to generate and hold a charge. The buildup of static electricity can be of a sufficient potential to damage electronic circuitry. When working on Ciena equipment or any interconnecting electrical/optical cabling, always wear an approved personnel ground device. Industry experience has shown that all devices containing integrated circuits can be damaged by static electricity that builds up on work surfaces and personnel. The effect of ESD damage may be immediate failure or it may manifest itself as a latent failure affecting the reliability of the equipment. The static charges and discharges are produced by various charging effects of movement and contact with other objects. Dry air allows greater static charges to accumulate on a body. Observe the following precautions to avoid static charges and discharges:
!
Assume that all modules contain solid state electronic components that can be damaged by ESD. When handling modules (that is, storing, installing, removing, and so forth) or when working on the backplane, always wear a grounded wrist strap or wear a heel strap and stand on a grounded, static-dissipating floor mat. Handle all modules by the faceplate or latch and by the top and bottom outermost edges. Never touch the components, conductors, or connector pins. Observe all warning labels on bags and cartons. If possible, do not remove modules from antistatic packaging until they are ready for use. If possible, open all module packaging at a static-safe work station using properly grounded wrist straps and static-dissipating table mats. Always store and transport modules in static-safe packaging. Keep all static-generating material, such as food wrappers, plastics, and styrofoam containers, away from all modules. When removing modules from an enclosure, immediately place them in static-safe packages. Whenever possible, maintain relative humidity above 20 percent.
! ! !
! !
! !
xxii
CoreDirector Switch
Optical Fiber Handling Precautions
When handling or connecting optical fibers, observe the following precautions:
! !
Introduction
Always wear safety glasses when handling fibers. After handling optical fibers, wash hands to avoid possible eye injuries caused by invisible fiber fragments on the skin. Avoid indirect eye or direct skin exposure to the ends of optical connectors and fibers, because laser energy may be present. Install protective covers or caps on all fiber optical connectors when they are not in use.
Fiber Break and Damaged Fiber Precautions

If a fiber break occurs or a damaged fiber is seen, observe the following precautions:
! ! ! !
Power off all laser sources to the fiber or disconnect the fiber end from the laser source. Notify the facility manager or supervisor about the damaged or broken fiber. Identify where the fiber is damaged or broken. Be careful when handling damaged or broken optical fibers to avoid eye injuries caused by invisible fiber fragments.
Precautions for Handling and Storing Modules Risk of Damage to Modules and Backplanes
Caution: Remove all optical connector dust caps from modules and backplane before installing modules.
When handling, installing, or removing modules, observe the following precautions.

!
Wear wrist straps or other suitable ESD-grounding devices before touching and/or removing a module from the equipment shelf or ESD-protective packaging. Handle modules by the faceplate only and do not touch the components, printed circuit board, or connector contacts. Ensure the protective covers or caps are installed on all optical connectors when the connectors are not in use. Ensure the backplane protective covers or caps are removed from the modules before installing them in equipment shelves. Store all modules in suitable ESD-protective packaging when they are not installed in an equipment shelf. Do not stack modules directly on or against each other. Store all modules in the original protective packaging container. Do not stack modules without the use of the original protective packaging containers.
! !
Modules must be maintained at all times within the environmental parameters provided in the Telcordia Generic Requirements document references listed in Table 9.

xxiii
Introduction
CoreDirector Switch
Table 9. Module Environmental Parameters
Operating Temperature Refer to Telcordia Generic Requirements GR-63-CORE, Section 4.1.2.
Relative Humidity Refer to Telcordia Generic Requirements GR-63-CORE, Section 4.1.2.
Storage Temperature Refer to Telcordia Generic Requirements GR-63-CORE, Section 4.1.1.
Shock and Vibration Refer to Telcordia Generic Requirements GR-63-CORE, Section 4.3 and 4.4.
Traffic Disruption Precaution Traffic Disruption Risk

Caution: Performance of the following step may cause a traffic disruption. This instruction is intended as a general guide only, has not been tested for all possible applications or configurations, and may not be complete or accurate for some situations.
Traffic interruption is a major concern for users of fiber optics systems. Take precautions to ensure that traffic disruption does not occur. Observe the following precautions to avoid traffic interruptions:
! !
Ensure that anyone performing a procedure is properly trained in the use of all appropriate tools. Contact the appropriate authority before proceeding with any procedure that may cause a disruption of traffic. Do not perform any procedure if in doubt about the effect of the action on system traffic.
xxiv
1
CoreDirector Switch Overview
CHAPTER 1 OVERVIEW
OVERVIEW
This manual contains information and procedures for maintaining, operating, and upgrading CoreDirector Multi-Service Optical Switch or CoreDirector CI Multi-Service Optical Switch network elements. The term CoreDirector Switch is used in this document to represent, unless otherwise stated, both the CoreDirector Switch and the CoreDirector CI Switch products. The procedures in this manual are performed after the CoreDirector Switch or CoreDirector CI Switch is installed and operational. Procedures for installing and turning up CoreDirector Switch systems are described in the applicable Hardware Installation Manuals and Turn-up and Test Manuals. System administrators, operations personnel, and maintenance technicians perform operation, maintenance, and upgrade procedures after CoreDirector Switch installation and turn-up and test. This manual includes mechanical procedures, such as replacing hardware components, and procedures that are based on the CoreDirector Node Manager software and the CoreDirector Switch Command Line Interface (CLI). The specific maintenance, operation, and upgrade services are defined as follows:
!
Operations include procedures associated with day-to-day switch operations at the Network Element (NE) level. Most of these procedures are based on the CoreDirector Node Manager software. Maintenance consists of preventive maintenance, corrective maintenance, and system upgrade procedures. Upgrade procedures are a subset of maintenance procedures and involve adding capabilities to the system or installing newer versions of software or hardware.
The procedures in this manual are presented as Task-Oriented Practices (TOPs).
REQUIRED TOOLS
!
Personal computer (PC) running Windows NT, Windows 2000, or Windows XP and equipped with a Compact Disc Read-Only Memory (CD-ROM) drive and 256 megabytes of Random Access Memory (RAM) 10Base-T, RJ-45 Ethernet cable for use with a 10Base-T hub. If a hub is not used, an Ethernet crossover cable for direct connection to the Input/Output (I/O) panel must be used. 9-pin to 25-pin RS-232 Data Communications Equipment (DCE) serial cable (DB-9 to DB-25 straight cable) for P- to-Craft Interface connection on the Control Module 9-pin to 9-pin RS-232 DCE serial cable for PC-to-Craft interface connection on the rear I/O panel CoreDirector Node Manager software (approved version) Miscellaneous hand tools, including: For the CoreDirector Switch: Torque wrench or torque driver with a 7/16-inch socket for torquing power input and return hardware to 65 inch-pounds (7.35 meter-Newtons). For the CoreDirector CI Switch: Torque wrench or torque driver with a 3/8-inch (10 mm) socket for torquing chassis ground, power input, and return hardware to 16 inch-pounds (1.8 meter-newtons). Insulated screwdrivers Digital Multimeter (DMM) with test leads
! ! !

1-1
1
Overview
!
CoreDirector Switch
Digital optical test set (Agilent 10G OmniBER SONET/SDH Tester or similar) with necessary fiber jumpers, 6-foot (2-meter) recommended, FC-to-SC adapters, and FC attenuators For testing the LM-16e Line Module, an STM1-E test set. Fiber cleaning kit with scope Optical power meter SC-to-SC small fiber jumpers, 6-inch (15-centimeter) recommended; may require as many as 230 fiber jumpers for testing one fully populated CoreDirector Switch. Bit Error Rate (BER) testing cannot be performed without the fiber jumpers. SC-to-SC, LC-to-SC, and LC-to-LC couplers Two Electrostatic Discharge (ESD) heel straps and one ESD wrist strap for each technician who will access the equipment
! ! ! !
! !
SOFTWARE INTERFACES
The software interfaces provide local and remote access to the nodes and modules in a CoreDirector Switch system. Access to the local CoreDirector Switch equipment is designed specifically for the on-site administrator or Craftsperson responsible for ensuring optimum node operation. Remote access to the CoreDirector Switch equipment is typically used by the authorized system administrator and other authorized network operations personnel. Operational software interfaces include the following:
! ! ! !
Node Manager software Transaction Language 1 (TL1) Command Line Interface ON-Center Core Switching Manager (CSM) Software
Local access to the equipment using the software interfaces is available through a connection to the Control Module or I/O panel on the CoreDirector Switch. Remote access is available through a telnet connection or from a management station. Specific details on the operations of the Switching Network Manager, the Node Manager, and the TL1, may be found in their individual manuals listed in the Introduction, Table 3.
HARDWARE FEATURES OF THE COREDIRECTOR SWITCH

This section provides a summary of the controls, indicators, and connectors on the CoreDirector Switch and CoreDirector CI Switch. Many of the procedures in this manual refer to these physical features of the CoreDirector Switch. The CoreDirector Switch System Description Manual provides more detailed information about the hardware.
Controls
The CoreDirector Switch and CoreDirector CI Switch have the same sets of manual controls, although some of them have different locations on each switch. Manual controls for CoreDirector Switches are in the following two locations:
! !
On the CoreDirector Switch, they are on the Power Distribution Unit (PDU) (Figure 1-1). On the CoreDirector CI Switch, they are on the front display panel (Figure 1-2) and on the rearmounted PDU (Figure 1-3).
1-2
1
CoreDirector Switch
POWER CRITICAL MAJOR MINOR ACO LED POWER A POWER B FAN SHELF SHELF A SHELF B SHELF C
A BATTERY
Overview
POWER GOOD FAN 1 POWER MODULE
POWER GOOD FAN 2 POWER MODULE B BATTERY
Alarm Cutoff Switch LED Test Switch
A Battery Circuit Breakers
B Battery Circuit Breakers
Figure 1-1. CoreDirector Switch Controls

ACO Switch LED Switch
POWER CRITICAL MAJOR MINOR POWER A POWER B FAN SHELF MODULE SHELF
ACO LED
Figure 1-2. CoreDirector CI Switch Display Panel Controls

CIRCUIT BREAKER A CIRCUIT BREAKER B
A
OFF 0 ON 1 OFF 0 ON 1
TOGGLE SWITCH
Figure 1-3. CoreDirector CI Switch PDU Controls The CoreDirector Switch has the following controls:
!
Circuit breakers on the PDU Protect the source from overcurrent conditions within the switch and allow the operator to turn on power to the switch. The CoreDirector Switch has four circuit breakers, two per input. They are on the front panel of the PDU at the top of the switch. The CoreDirector CI Switch has two circuit breakers, one per input. They are on the rearmounted PDU at the bottom of the switch.
Alarm Cutoff (ACO) switch on the display panel When pressed, silences an audible alarm. ACO activation does not affect the visual alarms. A new alarm condition activates the proper audible alarm, regardless of the ACO state.
LED test switch on the display panel When pressed, lights all visible indicators (except the Fan Power LED on the CoreDirector CI Switch and the large POWER indicator on both switches). The LEDs remain lit until the switch is disengaged by pressing it again.

1-3
1
Overview
Indicators
The CoreDirector Switches include visual indicators for overall system condition and for individual module operating states. The indicators are activated by the Control Modules (CMs). Except for power failure or card removal, LED activation is controlled by software. SYSTEM-LEVEL INDICATORS Indicators for overall system condition are in the following locations:
!
CoreDirector Switch
The PDU of the CoreDirector Switch, including indicators on the display panel and on the fan power modules (Figure 1-4) The display panel on the front of the CoreDirector CI Switch (Figure 1-5) The fan units
! !
System Power Indicator System-Level Alarms

ACO
POWER CRITICAL MAJOR MINOR LED
POWER A POWER B FAN SHELF SHELF A SHELF B SHELF C

A BATTERY
POWER GOOD FAN 2 POWER MODULE B BATTERY
Power, Shelf, and Fan Alarms
Fan Power LEDs
Figure 1-4. CoreDirector Switch PDU Indicators
ACO LED
POWER CRITICAL MAJOR MINOR
POWER A POWER B FAN SHELF MODULE SHELF
System-Level Alarms
Power Arm and Shelf Alarms
Figure 1-5. CoreDirector CI Switch Display Panel Indicators Table 1-1 describes the indicators on the CoreDirector Switches.
1-4
1
CoreDirector Switch
Table 1-1. CoreDirector Switch Indicators Indicator Type or Label POWER Color Green Location CoreDirector Switch: PDU CoreDirector CI Switch: Display panel Description A large indicator that lights when power is available to the CoreDirector Switch or CoreDirector CI Switch. In the CoreDirector CI Switch, this indicator also indicates that the PDU circuit breaker is in the ON position.
Overview
NOTE: In earlier versions of the CoreDirector Switch PDU (prior to -120 Rev 3), a lit POWER indicator confirms that the POWER A or POWER B circuit breakers are turned on. In later versions of the PDU, a lit POWER indicator confirms that power is present at the power connections at the rear of the CoreDirector Switch. Bay Alarm State: CRITICAL MAJOR MINOR Power Arm Failure: POWER A POWER B Red Red Yellow CoreDirector Switch: PDU CoreDirector CI Switch: Display panel CoreDirector Switch: PDU CoreDirector CI Switch: Display panel PDU Red Display panel Red Red Blue CoreDirector Switch: PDU CoreDirector CI Switch: Display panel CoreDirector Switch: PDU CoreDirector CI Switch: Display panel PDU CoreDirector Switch or CoreDirector CI Switch Fan Units Three large indicators show the alarm status of the system. They indicate critical (red), major (red), and minor (yellow) alarm status and mirror the current equipment status reported for the rack. Two LEDs that indicate a failure of either arm of the power distribution circuitry. The LED lights if there is a failure of the indicated power arm.
Red
Shelf Failure Indicators (CoreDirector Switch) Shelf Failure: FAN SHELF MODULE SHELF (CoreDirector CI Switch) ACO (Lighted Pushbutton)
Four red LEDs indicate that a failure is present on any of the four equipment shelves of the rack (fan shelf, Shelf A, Shelf B, or Shelf C). Two LEDs that indicate a failure is present on the fan unit shelf or the module shelf.
The ACO switch lights blue when the alarm cutoff feature is active (see description in next section).
LED Test (Lighted Pushbutton)
Blue
If an LED test is currently active, all visible indicators in the bay light, and the LED switch lights blue.
Fan Power (CoreDirector Switch) Fan Unit LEDs: Red Green
Green
Indicates that power is being supplied to the associated fan unit. Red LED indicates a failure or degradation of operation in the fan, including possible excessive bearing wear; green LED indicates operation of the fan.
Red Green

1-5
1
Overview CoreDirector Switch
The CoreDirector Node Manager Graphical User Interface (GUI) displays the alarm LEDs of the node element (CoreDirector Switch or CoreDirector CI Switch) to which it is connected. The displayed LEDs for each switch are as follows:
!
For the CoreDirector Switch, the Node Manager screen displays five LEDs: P (Power) F (Fan) A, B, C (Shelves A, B, and C)
For the CoreDirector CI Switch, the Node Manager screen displays three LEDs: P (Power) F (Fan) A (Shelf A)
MODULE LED OPERATION All modules in the CoreDirector Switches have Light Emitting Diodes (LEDs) to indicate module status. There are basic rules for the meanings of each color (that is, red, yellow, and green), as well as for the sequence pattern of LED lighting during operation of the modules. The color rules are as follows:
!
Basic red ruleAn illuminated red LED indicates that the module is not in a legal operating state. A red LED is, therefore, illuminated during any boot, initial configuration, or initialization state; in addition, a red LED lights when there is a reset or module failure. If a yellow LED is present on the module, it may supply additional information about the module. Basic yellow ruleAn illuminated yellow LED indicates that the module is in a maintenance state, such as Admin Locked. The yellow LED may also supply additional state information about a module when a red or green LED is illuminated. Basic green ruleAn illuminated green LED indicates that the module is active. OnThe LED lights steadily. OffThe LED is dark. FlashingThe LED cycles on and off in equal time periods. WinkingThe LED cycles on and off with a significantly longer on period than off period.
The following terms are used in describing LED patterns.

! ! ! !
During operation, all system modules follow the basic module states pattern described in the next section. Modules that have local processors with downloadable code (Line Module, Control Module, and Timing Module) follow the module boot sequence pattern described in Table 1-3. Modules with redundant backup or an active secondary (Control Module, Timing Module, and Switch Module) follow the redundant module states pattern described in Table 1-4 on page 7. BASIC MODULE STATES PATTERN The Basic Module States Pattern (Table 1-2) applies to all modules. Table 1-2. Basic Module States Pattern Yellow Off Flashing On On Red Green Off Off State Module is held in Reset state, or there is a hardware failure, or software is not yet running from local flash memory. Run-time image diagnostics, configuration, or initialization is taking place.
1-6
1
CoreDirector Switch
Table 1-2. Basic Module States Pattern (Continued) Yellow On Off Off Off Off Off Red Green Off On Off State Module is in a maintenance state (for example, Admin Locked) and is safe for removal. Module is operational and active. Power is off.
Overview
MODULE BOOT SEQUENCE The Module Boot Sequence Pattern (Table 1-3) applies to all modules with local processors that must be downloaded and initialized before providing service. This pattern requires that the modules have a pair of dedicated LEDs, preferably red and yellow. Table 1-3. Module Boot Sequence Pattern Yellow Off On On On Red State Module is held in Reset state, there is a hardware failure, or software is not yet running from local flash memory. Software is running from local flash memory. (Includes first-pass diagnostics, BOOTP, loading of run-time image, and early initialization in run-time image.) Power is off.
Off
Off
REDUNDANT MODULE STATES Modules that are part of a redundant set or have an active secondary indicate their role by means of a single green LED. This LED lights steadily if the module is currently acting in the primary role and winks if the module is currently in the secondary or redundant role. Table 1-4 lists the LED indications for redundant module states. Table 1-4. Redundant Module States Pattern Green On Winking Off State Module is currently in the primary role. Module is currently in the secondary role. Power is off.
Connectors
Electrical connections to the CoreDirector Switch are made at two locations.
! !
Power connections are made at the rear of the PDU. I/O connections are made at the rear I/O panel (CoreDirector Switch) or at the front of the I/O Module (CoreDirector CI Switch).
POWER DISTRIBUTION The PDU receives -48 VDC power inputs (POWER A and B) from the facility Battery Distribution Fuse Bay (BDFB). The DC power wiring attaches to the terminal block on the rear of the PDU (Figure 1-6 or Figure 13 for CoreDirector CI Switch). Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
1-7
1
RACK
NOTE: Wiring is not shown for clarity.
Figure 1-6. CoreDirector Switch PDU (Rear View) In a CoreDirector Switch, the A1 and B2 pair and the B1 and A2 pair provide power to vertical halves of the backplane. The FPMs provide overcurrent protection for the FMs and redundancy so that either power source can power both fans. There is one FPM for each FM. I/O PANEL OR MODULE In the CoreDirector Switch, the I/O panel (Figure 1-7) is mounted on the backplane at the rear of the unit. The I/O panel is covered by a metal protective cover with the connectors exposed for access. It provides electrical connectors for all system I/O signals. Connections are made from the I/O panel to the backplane by board-stacking connectors. The I/O signals are distributed to the modules through backplane circuit traces.
I/O Panel
Backplane (Covered)
Figure 1-7. I/O Panel in the CoreDirector Switch I/O MODULE IN THE COREDIRECTOR CI SWITCH In the CoreDirector CI Switch, I/O connections are provided by an I/O module (Figure 1-8) that is installed in the upper middle part of the single module shelf. This I/O module provides external electrical connectors for all system I/O signals. Architecturally, the two rows of connectors on the I/O module each feed signals through the backplane to either the primary CM (A-CM1) and the primary TM (A-TM1) or the redundant CM (A-CM2) and redundant TM (A-TM2).
1-8
1
ACO LED
FAN A
FAN B
I/O Module
TIMING MODULE TIMING MODULE
CONTROL MODULE
CONTROL MODULE
........ .......
........ .......
SWITCH MODULE
SWITCH MODULE
SWITCH MODULE
SWITCH MODULE
Figure 1-8. I/O Module in the CoreDirector CI Switch Two types of I/O panels or modules are available for CoreDirector Switches:
!
SONET (T1) to support GR-1244-CORE input/output (I/O) requirements for SONET communications SDH (E1) to support I/O requirements for SDH communications
Functionally, the two types of I/O panels or modules are identical; physically, they differ only in the types of connectors used for the timing interface. In the CoreDirector Switch, the T1 I/O panel has two DB15 connectors for the timing interface to the Building Integrated Timing Supply (BITS), and the E1 I/O panel has replaced those connectors with four BNC timing interface connectors. Figure 1-9 shows the two types of I/O panels for the CoreDirector Switch.

1-9
1
Overview
10/100 Ethernet
CoreDirector Switch
144
Alarm
BITS 2 C-CM AUX A-CM AUX C-CM MAIN A-CM MAIN BITS 1
PDU A-CM RS-232 DTE C-CM RS-232 DTE
T1 I/O Panel (SONET)
Timing Interface (BITS 1 and BITS 2) 10/100 Ethernet
Alarm
A-CM MAIN C-CM MAIN A-CM AUX C-CM AUX
145
PDU C-CM RS-232 DTE A-CM RS-232 DTE
E1 I/O Panel (SDH) Figure 1-9. I/O Panels for the CoreDirector Switch In the CoreDirector CI Switch, the T1 I/O module has two RJ-45 timing interface connectors, and the E1 I/ O module has four BNC timing interface connectors. Figure 1-10 shows the two types of I/O modules for the CoreDirector CI Switch.
1 - 10
1
A-CM 1
A-CM 2
A-CM 1
A-CM 2
MAIN
MAIN
ETHERNET
10/100 Ethernet Interfaces
ETHERNET
AUX
AUX
RS-232 DTE
RS-232 Craft Interfaces
RS-232 DTE
BITS 1 BITS
BITS 2 TX TX
BITS Interfaces RJ-45 for SONET (T1) Version BNC for SDH (E1) Version
RX
RX
Figure 1-10. I/O Modules for the CoreDirector CI Switch The CoreDirector CI Switch I/O Module is hot-swappable. The following connectors are on the I/O panel or module:
!
RS 232 connectorsProvide a communications path for Craft Interface dial-up access to a CoreDirector Switch. BITS (Timing Interface) connectorsProvide input for an external timing source. The CoreDirector Switch SONET (T1) I/O panel uses two 15-pin DB-15 connectors. The CoreDirector CI Switch SONET (T1) I/O module uses two RJ-45 connectors. The SDH (E1) I/O panel or module for either switch uses four BNC coaxial connectors.
SONET I/O MODULE
SDH I/O MODULE
A L A R M
Alarm Interfaces
A L A R M
148
SONET (T1)
SDH (E1)
Ethernet connectorsProvide a communications path to the CoreDirector Node Manager software (via a router or switch). The Ethernet connector pinout is the standard used for RJ-45 terminals. Individual Ethernet connectors are associated with each of the two CMs in the switch. On a CoreDirector Switch, the Ethernet connectors are designated as A-CM MAIN, A-CM AUX, CCM MAIN, and C-CM AUX. On a CoreDirector CI Switch, Ethernet connectors are designated as A-CM1 Main, A-CM1 Aux, A-CM2 Main, and A-CM2 Aux.

1 - 11
1
Overview
!
CoreDirector Switch
Alarm connectorProvides an output to a potential LED display in a central office, audible alarms, ACO sense inputs, user-defined relay outputs, and power fail relay output. These pins are chosen without regard to a particular standard. The P and N signals are matched on opposing rows on the connector. On the CoreDirector CI Switch, the Alarm connector presents both Normally Open (NO) and Normally Closed (NC) - form C dry contact closures. The Alarm interface uses a DB-62 female connector. The CoreDirector CI Switch provides Critical, Major, Minor, and power fail contacts. In addition, the CoreDirector CI Switch also provides four NO general-purpose dry contact closures and eight general-purpose dry contact closure inputs. The general-purpose signals may be user-defined for environmental or other external alarm conditions.
PDU connector (CoreDirector Switch only)Provides an I/O conduit between the PDU and Fan Modules to the PDU display.
OPTICAL PORT CONNECTORS Optical interfaces on CoreDirector Switches use SC, LC, and MTP connectors. On LM-8 Line Modules, the connectors are recessed behind the faceplates of the OMs. An OM must be partially removed from the Line Module in order to access the optical connectors. On the LM-2 Line Modules, the connectors are on the front of the OM faceplate. The LM-16 optical interfaces are on the front of the module faceplate and use LC-type connectors on a 1.6mm or 2.0mm Simplex fiber assembly. The LC-type port connectors on the LM-16 are not physically compatible with SC-type connectors and require SC-to-LC adapter cables in cases where LC-type terminated site fiber is not available.
Equipment Shelves and Component Locations

Locations of the hardware components in the CoreDirector Switch rack or chassis are identified as a combination of shelf, slot, and subslot (or port) references (for example, A-1-8). The following sections describe how the hardware components are identified looking at the front of the system. SYSTEM SHELVES The CoreDirector Switch modules are installed in shelves that are lettered for identification by management software (Figure 1-11). In the CoreDirector Switch, the top shelf of Line Modules is Shelf A, and the bottom shelf of Line Modules is Shelf C. The middle shelf of Switch Modules and Timing Modules is Shelf B. In the CoreDirector CI Switch, the single shelf for all system modules is called Shelf A.
1 - 12
1
ACO LED
FAN A
FAN B
Shelf A
CONTROL MODULE
CONTROL MODULE CONTROL MODULE
........ .......
ALARM MAINT NORMAL
........ .......
........ .......
Shelf B CoreDirector CI Switch

CONTROL MODULE
........ .......
ALARM
MAINT
NORMAL
Shelf C
CoreDirector Switch Figure 1-11. CoreDirector Switch Shelves In the CoreDirector Switch, slots within each shelf are generally labeled from left to right, starting at slot 1. Special slot labels are used to identify the Control Modules and Timing Modules. Control Modules are labeled as A-CM and C-CM; Timing Modules are labeled as TM1 and TM2. The Control Module on Shelf A occupies physical slot 17, and the Control Module on Shelf C occupies physical slot 1. Line Modules on Shelf A are numbered, starting from the left in physical slot 1, and are identified as A-1 through A-16. Line Modules on Shelf C are numbered, starting from the left in physical slot 2, and are identified as C-1 through C-16. Figure 1-12 shows these numbering arrangements.

1 - 13
1
Slot A-CM Line Module Slots A-1 through A-16

CONTROL MODULE
........ .......
ALARM MAINT NO RMAL
Slot B-TM-1
Switch Modules B-1 through B-15

NO RMAL
Slot B-TM-2
CONTROL MODULE
........ .......
ALARM
MAINT
Slot C-CM
Line Module Slots C-1 through C-16
Figure 1-12. Slot Numbering in the CoreDirector Switch SYSTEM MODULE SLOTS In the CoreDirector CI Switch, module slots are labeled according to module type (Figure 1-13). The letter A preceding the module type identifies the single A shelf. The system module slots, and their corresponding modules, are listed below:
! ! ! !
Control Modules (CM) occupy slots A-CM1 (primary) and A-CM2 (secondary). Timing Modules (TM) occupy slots A-TM1 (primary) and A-TM2 (secondary). Switch Modules (SM) occupy slots A-SM1 through A-SM4. Line Modules (LM) occupy two groups of slots identified as A-1 through A-4 (left side of the system shelf) and A-5 through A-8 (right side of the system shelf). The location of the modular I/O panel is designated slot A-IO.
1 - 14
1
ACO LED
Slot A-IO: I/O Panel

FAN A FAN B
Slots A-1 through A-4: Line Modules Slot A-TM1: Timing Module 1
Slots A-5 through A-8: Line Modules Slot A-TM2: Timing Module 2
CONTROL MODULE
CONTROL MODULE
........ .......
........ .......
Slot A-CM1: Control Module 1
Slot A-CM2: Control Module 2
Slots A-SM1 through A-SM4: Switch Modules Figure 1-13. Slot Numbering in the CoreDirector CI Switch OPTICAL MODULES AND PORTS Optical modules and ports are identified by their position in a Line Module and by the slot in which the Line Module resides. The optical modules or ports are logically numbered from top to bottom in the module, as follows:
!
On an LM-2 Line Module the optical modules are numbered 1 through 2. Example - A-4-1 and A-4-2 On an LM-8 Line Module the optical modules are numbered 1 through 8. Example - A-3-1 through A-3-8 On an LM-16 Line Module the ports are numbered 1 through 16. Example - A-2-1 through A-2-16 On an LM-20 Line Module the optical port groups are numbered 1 and 2 and each port group has optical ports numbered 1 through 10. Example - A-1-1-1 through A1-1-10 and A-1-2-1 through A1-2-10
This numbering scheme applies to both Shelf A and Shelf C in the CoreDirector Switch. For example, the optical modules on an LM-8 module in slot A-3 are identified as A-3-1 through A-3-8. On an LM-8 module in slot C-3, the optical modules are still numbered top to bottom, this time as C-3-1 through C-3-8.Figure 114 illustrates the numbering scheme in each type of Line Module. Note: Optical Modules are not physically labeled on the front panel of the Line Module. Slot numbers are for reference only.

1 - 15
1
OP-1 OP-2 OP-3 OP-4 OP-5 OP-6 OP-7 OP-8 OP-9 OP-10
Port Group 1
OP-1 OM 1 OP-2 OP-3 OM 2 OP-4 OP-5 OM 3 OP-6 OP-7 OM 4 OP-8 OP-9 OM 5 OP-10 OP-11 OM 6 OP-12 OP-13 OM 7 OP-14 OP-15 OP-16 A-2 LM-16 A-3 LM-8 A-4 LM-2 OM 8 OM 2 OM 1
EP-1 EP-2 EP-3 EP-4 EP-5 EP-6 EP-7 EP-8 EP-9 EP-10 EP-11 EP-12 EP-13 EP-14 EP-15 EP-16
EP-1 EP-2 EP-3 EP-4 EP-5 EP-6 EP-7 EP-8 EP-9 EP-10 EP-11 EP-12 EP-13 EP-14 EP-15 EP-16
OP-1 OP-2 OP-3 OP-4 OP-5 OP-6 OP-7 OP-8 OP-9 OP-10
Port Group 2
A-1 LM-20-GE
A-5 LM-16STM-1EA-U
A-8
A-6 A-7 LM-16-STM-1E-A
A-9
...
Figure 1-14. Naming Optical Modules and Ports
1 - 16
2
CoreDirector Switch Operations
CHAPTER 2 OPERATIONS
OVERVIEW
The CoreDirector Switch or CoreDirector CI Switch system operations tasks ensure continued operations of all system components in the network. Authorized users normally perform the software-based system operations tasks using the Switching Network Manager software, Transaction Language One (TL1) interface, or the Node Manager software. System operations tasks may also be performed by a craftsperson at the location of the CoreDirector Switch. For software-related tasks, the craftsperson can access the CoreDirector Switch locally using the CoreDirector Node Manager software. The instructions in the Task-Oriented Practices (TOPs) serve as job aids to assist the user in performing the operations tasks. Table 2-1 lists the Operations TOPs (provided in Chapter 4 of this manual). Table 2-1. Operations: Software- and Hardware-Related TOPs Title TOP 007D Using the ACO Switch to Turn Off an Alarm TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface TOP 208D Configuration Database Backup and Restore TOP 217D CoreDirector Switch Shutdown TOP 270D Resetting the Primary Control Module (CM Switch) TOP 271D Resetting the Secondary Control Module (CM) TOP 274D IO Panel EEPROM Check TOP 275D Change CoreDirector Initial Install Settings TOP 283D FTP Server Setup Page page 4-7 page 4-101 page 4-107 page 4-115 page 4-151 page 4-195 page 4-199 page 4-203 page 4-205 page 4-243
HARDWARE OPERATIONS
Daily operation of a CoreDirector Switch requires little or no equipment handling. Most system operations tasks are performed using one or more of the software interfaces. The visual indicators described in Chapter 1 (see page 1-4) provide high-level information about the general operating health of the system. (These indicators are represented in the Node Manager GUI; see page 1-6.) This chapter shows the locations of the LEDs on CoreDirector Switch modules; these LEDs can provide information about the operating state of the module or individual ports. Chapter 1, Overview, provides information about hardware controls, indicators, and connectors. The CoreDirector Switch System Description Manual provides additional system details.

2-1
2
Operations
LEDs on Modules
This section provides illustrations of the locations of the LEDs on CoreDirector modules. TIMING MODULE The Timing Module (Figure 2-1) has three LEDs: red, yellow, and green. Table 1-2 on page 6 of this manual provides details about module LED states. The CoreDirector Switch System Description Manual provides more detailed information about the Timing Module hardware.
CoreDirector Switch
FAIL MAINT ACTIVE
STATUS LEDs Fail Maintenance Active
Color Red Yellow Green
200388
Figure 2-1. Timing Module LEDs OPTICAL MODULES Optical Modules for the LM-8 Line module (Figure 2-2) have four LEDs: one red, one green, and two yellow LEDs. For details of module LED states, see Table 1-2 on page 6 of this manual. For more detailed information about the Optical Module hardware, refer to the CoreDirector Switch System Description Manual.
OM155/622
FAIL MAINT ACTIVE LINE
OUT
Status LEDs Red Fail

Maintenance Active Line
STATUS LEDs Color Yellow Green Yellow
IN
200391
Figure 2-2. Optical Module LEDsOC-48 and OC-3/12 The OC-192 Optical Module (Figure 2-3) for the LM-2 Line Module has four LEDs: one red, one green, and two yellow. Table 1-2 on page 6 of this manual provides details about module LED states. The CoreDirector Switch System Description Manual provides more detailed information about the Optical Module hardware.
2-2
2
Status LEDs
STATUS LEDs COLOR Fail RED Maintenance YELLOW Active GREEN Line YELLOW
210077
Figure 2-3. Optical Module LEDsOC-192 SWITCH MODULE The Switch Module (Figure 2-4) has three LEDs: red, yellow, and green. Table 1-2 on page 6 of this manual provides details about module LED states. The CoreDirector Switch System Description Manual provides more detailed information about the Switch Module hardware.
FAIL MAINT ACTIVE
200389
Figure 2-4. Switch Module LEDs CONTROL MODULE The Control Module (Figure 2-5), has three LEDs: red, yellow, and green. Table 1-2 on page 6 of this manual provides details about module LED states. The CoreDirector Switch System Description Manual provides more detailed information about the Control Module hardware.

2-3
2
Operations CoreDirector Switch
STATUS LEDs Fail Maintenance Active Color Red Yellow Green
FAIL MAINT ACTIVE
200390
Figure 2-5. Control Module LEDs LINE MODULES Four types of Line Modules are currently available for the CoreDirector Switch as follows:
! !
LM-2 Line Module (Figure 2-6) for use with up to two 10G Optical Modules LM-8 Line Module (Figure 2-7) for use with up to eight 2.5G Optical Modules or 155/622M Optical Modules LM-16 Line Module (Figure 2-9) with 16 integrated OC-3/12 STM-1/4 (155/622M) optical ports LM-16-E Line Module (Figure 2-8) that provides 16 STM-1e ports LM-20-E Line Module (Figure 2-8) that provides 20 Gigabit Ethernet ports
! ! !
Table 2-2 describes the operation of the line module LEDs. Table 2-2. Line Module LED States M (Maintenance) or LM MAINT Yellow Off On S (Status) or LM STAT Red (Fail) Green (Active) Off Module is held in Reset state, or there is a hardware failure, or software is not yet running from local Flash memory. Software is running from local Flash memory. This state includes first-pass diagnostics, BOOTP, loading of runtime image, and early initialization in run-time image. Run-time image diagnostics, configuration, and initialization are taking place. Module is in a state that is safe for removal (for example, Admin Locked). Module is operational. Power is off.
State
On
On
Off
Flashing On Off Off
On Off Off Off
Off Off On Off
LM-2 Line Module. The LM-2 module (Figure 2-6) has one yellow LED and one red/green bicolor LED. Table 2-2 and Table 1-3, Module Boot Sequence Pattern, on page 7 describe the operation of these LEDs. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
2-4
2
LED LABEL STATUS LED M Maintenance
COLOR Yellow
LED LABEL STATUS LED COLOR S Fail Red Active Green
210076
Figure 2-6. LM-2 Line Module LEDs
LM-8 Line Module. The LM-8 module (Figure 2-7) has one yellow LED and one red/green bicolor LED. Table 2-2 and Table 1-3, Module Boot Sequence Pattern, on page 7 describe the operation of these LEDs.

2-5
2
Operations
.
CoreDirector Switch
LED LABEL M
STATUS LED Maintenance
Color Yellow
OPTICAL MODULE FRONT VIEW
STATUS LEDs Fail Maintenance Active Line
Color Red Yellow Green Yellow
LED LABEL STATUS LED BICOLOR S Fail Active Red Green
Figure 2-7. LM-8 Line Module LEDs LM-20-E Line Module. The LM-20-E Line Module (Figure 2-8) has one yellow LED and one red/green bicolor LED to indicate port status. Table 2-3 and Table 1-3, Module Boot Sequence Pattern, on page 7 describe the operation of these LEDs.
200387
2-6
2
LM MAINT (Yellow)
Optical Port LEDs: MAINT (Yellow) LINE (Yellow) ACT/FAIL (Red/Green)
LM STAT (Red/
Figure 2-8. LEDs on the LM-20-E Line Module The LM-20-E Line Module also has three LEDs associated with each optical port to show status information about the optical port itself (Figure 2-8). These are a single red/green bicolor LED and two yellow LEDs. During and following a module reset, the red FAIL LED is illuminated by hardware until it is turned off by means of a microWire command from the Line Module. Table 2-3 describes operation of these LEDs. Table 2-3. LM-20-E Line Module Optical Port LEDs MAINT Yellow Off LINE Yellow Off On ACT/FAIL Red (Fail) Green (Active) Off State Optical port is held in a Reset state, or there is a hardware failure, or software is not yet running from local Flash memory. Run-time image diagnostics, configuration, and initialization are taking place. Optical port is in a locked, laser-off state (for example, Admin Locked). Alarms are not generated. Optical port is in an unlocked, laser-on state (for example, Admin Unlocked), but the port has no fiber connected or is not receiving proper framing. Loss of Signal (LOS) and Loss of Frame (LOF) alarms are generated. Optical port is in an unlocked, laser-on state (for example, Admin Unlocked), and the port has fiber connected and is receiving proper framing. Power is off.
Flashing On Off
On On On
On Off Off
Off Off On
Off
Off
Off
On
Off
Off
Off
Off
NOTE: The LINE LED refers only to the presence or absence of a signal at the port and does not apply to the operation of the module otherwise.

2-7
2
LM-16 Line Module. To indicate module status, the LM-16 Line Module (Figure 2-9) has a single yellow LED and a single bicolor red/green LED. Table 2-2 and Table 1-3, Module Boot Sequence Pattern, on page 7 describe the operation of these LEDs.
OPTICAL PORT LEDS
MAINT LINE ACT/FAIL LM MAINT
M L AF
M L AF
ACT/FAIL AF
LM MAINT
MAINT M
LINE L
RECEIVE
AF M L
EJECTOR
TRANSMIT
AF M L
LM MAINT LED
AF AF AF AF AF AF AF AF
M M M M M M M M
L L L L L L L L
OPTICAL PORT LEDS
EJECTOR
LM16-155/622-ML
AF M L
LASER WARNING LABEL
AF AF
M M
L L
M L AF
M L AF
M L AF
M L AF
MAINT LINE ACT/FAIL LM STAT

AF M L
LM16-155/622-ML
LINE
MAINT
ACT/FAIL
RECEIVE TRANSMIT LM STAT LED
LM STAT
Figure 2-9. LM-16 Line Module LEDs The LM-16 Line Module also has three LEDs associated with each optical port to show status information about the optical port itself. These are a single green/red bicolor LED and two yellow LEDs. During and following a module reset, the red FAIL LED is lit by hardware until it is turned off by means of a microWire command from the Line Module. Table 2-4 describes operation of these LEDs.
2-8
2
CoreDirector Switch
Table 2-4. LM-20-E Line Module Optical Port LEDs MAINT Yellow Off LINE Yellow Off On ACT/FAIL Red (Fail) Green (Active) Off State Optical port is held in a Reset state, there is a hardware failure, or software is not yet running from local Flash memory. Run-time image diagnostics, configuration, and initialization are taking place. Optical port is in a locked, laser-off state (for example, Admin Locked). Alarms are not generated. Optical port is in an unlocked, laser-on state (for example, Admin Unlocked), but the port has no fiber connected or is not receiving proper framing. Loss of Signal (LOS) and Loss of Frame (LOF) alarms are generated. Optical port is in an unlocked, laser-on state (for example, Admin Unlocked), and the port has fiber connected and is receiving proper framing. Power is off.
Operations
Flashing On Off
On On On
On Off Off
Off Off On
Off
Off
Off
On
Off
Off
Off
Off
NOTE: The LINE LED refers only to the presence or absence of a signal at the port and does not otherwise apply to the operation of the module.

2-9
2
2 - 10
3
CoreDirector Switch Maintenance
CHAPTER 3 MAINTENANCE
OVERVIEW
CoreDirector Switch or CoreDirector CI Switch system maintenance ensures continued performance of all system components in the network. Maintenance tasks can involve direct handling of the equipment or can be software-related tasks. Authorized personnel perform the software-related maintenance tasks using the Craft Interface, the TL1 command set, or the Node Manager software. The publications listed in Table 3 on page xvi of this manual provide detailed information about the software interfaces. Maintenance tasks can be divided into the following three categories:
!
PreventiveRoutine tasks performed to ensure that the customers traffic operations are uninterrupted. CorrectiveTasks performed, usually in response to alarm condition(s), to repair or replace one or more system components no longer operating within their specified parameters. System UpgradesTasks performed to incorporate hardware or software enhancements.
The instructions in the Task-Oriented Practices (TOPs) serve as job aids to assist the user in performing the maintenance tasks. Table 3-1 lists the Maintenance TOPs (provided in Chapter 4 of this manual).
PREVENTIVE MAINTENANCE
CoreDirector Switch preventive maintenance consists of two types of activities:
!
Constant system performance monitoring to detect and correct degraded system performance before customer traffic is affected Fan filter maintenance
Fan Filter Maintenance

Ciena recommends that CoreDirector Switch air filters be removed and replaced every six months. Although the filters are washable, washing the filters is not recommended because cleaning removes the flame retardant coating. Replacing the filters every six months will ensure minimal contamination based on the environment and fan speed. It should be noted cleanliness varies from site to site. The CoreDirector Switch does not have the means to detect a particular percentage of reduction in air flow due to variables associated with the site and environment. The identified filters will remove 83 percent of all particles and meet UL and Bellcore NEBS standards. Note: Air filters play a vital role in allowing sufficient airflow to be channelled through the CoreDirector Switch chassis.
SYMPTOM There are no apparent signs that warrant or flag the necessity of an air filter replacement other than periodic Inspection and adhering to an established site maintenance schedule. An excessively dirty air filter, if not replaced, could cause airflow problems resulting in bay cooling alarms generated by the CoreDirector Switch.

3-1
3
Maintenance
MAINTENANCE GUIDELINES Ciena recommends the following to minimize air filter airflow restriction:
! !
CoreDirector Switch
Establish a maintenance schedule that identifies air filter replacement every six months. Replace the air filters (listed below) with factory replacement filters using TOP 032D. CoreDirector air filter, Ciena Part Number 410-6074-100 and Ciena part name Air Filter. CoreDirector CI air filter, Ciena Part Number 399-8005-001 and Ciena part name Air Filter.
Following these guidelines will help minimize issues associated with operating the CoreDirector Switch without adequate airflow for extended periods of time. To acquire air filters or additional information, refer to the section, Contacting Ciena inside the cover page of this manual, and contact Ciena Technical Support.
CORRECTIVE MAINTENANCE
Corrective maintenance is performed in response to system alarms. The integral alarm system monitors critical system and module components and signals (optical and electrical) and initiates an alarm each time that a specified threshold is exceeded. The system simultaneously indicates alarms on the LEDs of the modules and sends alarms to the Switching Network Manager. When the system indicates an alarm, the control center tries to clear the alarm. If the alarm cannot be cleared at the control center, the control center dispatches a technician to perform corrective action. If the technician isolates the trouble to a faulty module, the technician replaces the faulty module with a good spare. The technician returns faulty module to the Ciena Repair Depot for testing and repair. (Refer to TOP 072D Ciena Return Material Authorization (RMA) Procedure, for instructions to return components.)
SYSTEM UPGRADES
A Technical Support technician performs system hardware and software upgrades as required. When the CoreDirector Switch software or a hardware component has been upgraded in the Ciena factory, Ciena ships the upgraded software or hardware to the customer site. If the removal and installation of a module is required, the installer follows the appropriate TOPs.
TOPS FOR MAINTENANCE TASKS

The instructions in the Task-Oriented Practices (TOPs) serve as job aids to assist the user in performing the maintenance tasks. Table 3-1 lists the Maintenance TOPs; the specific TOPs are provided in Chapter 4 of this manual. Table 3-1. Maintenance: Hardware and Software Related TOPs Title TOP 001D Measuring Optical Power Level TOP 015D Verifying -48 VDC Supply Voltage TOP 016D Verifying System Grounding TOP 032D Removing and Installing an Air Filter TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 168D Removing and Installing a Circuit Breaker Module TOP 169D Removing and Installing a Cooling Fan Unit Page page 4-3 page 4-9 page 4-11 page 4-15 page 4-17 page 4-19 page 4-23
3-2
3
CoreDirector Switch Maintenance
Table 3-1. Maintenance: Hardware and Software Related TOPs (Continued) Title TOP 170D Removing and Installing a Control Module TOP 171D Removing and Installing a Switch Module TOP 172D Removing and Installing an Optical Module TOP 173D Removing and Installing a Line Module TOP 174D Removing and Installing a Timing Module TOP 175D Removing and Installing a PDU Display Module TOP 176D Removing and Installing a Fan Power Module TOP 177D Removing and Installing a CoreDirector CI I/O Module TOP 178D CoreDirector Switch Power Up TOP 183D Removing and Connecting the Alarms and Parallel Telemetry Cable TOP 185D Removing and Installing the PDU-B/P Cable TOP 187D Test LEDs Page page 4-27 page 4-35 page 4-41 page 4-53 page 4-73 page 4-77 page 4-81 page 4-85 page 4-89 page 4-91 page 4-97 page 4-99
TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch page 4-101 TOP 207D Adding Channel Capacity TOP 208D Configuration Database Backup and Restore TOP 209D Setting Up a CoreDirector Switch for Modem Access TOP 210D CoreDirector Switch Software Upgrade and Restore TOP 211D Software In-Service Reversion TOP 217D CoreDirector Switch Shutdown TOP 218D Pack Up a CoreDirector Switch System TOP 220D Test Line Modules and Optical Modules TOP 221D Test Optical Module TOP 223D Change CoreDirector Switch Name/IP Address TOP 261D Change NE CLI Login User ID and/or Password TOP 262D Recovery from Dual CM Failure TOP 270D Resetting the Primary Control Module (CM Switch) TOP 271D Resetting the Secondary Control Module (CM) TOP 274D IO Panel EEPROM Check TOP 275D Change CoreDirector Initial Install Settings TOP 276D LM-8 to LM-16 Upgrade TOP 278D Handling Circuit Packs Properly TOP 279D Prepare Site Terminal (or Laptop) for Software Transfer TOP 280D Resetting the Primary Timing Module (TM Switch) page 4-111 page 4-115 page 4-121 page 4-127 page 4-143 page 4-151 page 4-155 page 4-161 page 4-177 page 4-181 page 4-185 page 4-187 page 4-195 page 4-199 page 4-203 page 4-205 page 4-209 page 4-215 page 4-223 page 4-225

3-3
3
Maintenance CoreDirector Switch
Table 3-1. Maintenance: Hardware and Software Related TOPs (Continued) Title TOP 281D Resetting the Secondary Timing Module (TM) TOP 282D Decommissioning a CoreDirector Switch Page page 4-229 page 4-233
3-4
4
CoreDirector Switch Task Oriented Practices (TOPS)
CHAPTER 4 TASK ORIENTED PRACTICES (TOPS)

OVERVIEW
This chapter provides the Task-Oriented Practices (TOPs) needed to perform operations and maintenance tasks on the CoreDirector Switch or CoreDirector CI Switch. Table 4-1 lists the TOPs by number and title and provides the page reference. Portions of this chapter are intended solely as an outline of methodologies to be followed in performing procedures on the CoreDirector Switch. It is not intended as a step-by-step guide or a complete set of all procedures necessary and sufficient to complete all tasks. While every effort has been made to ensure that this document is complete and accurate at the time of printing, the information that it contains is subject to change. Ciena is not responsible for any additions to or alterations of the original document. Networks vary widely in their configurations, topologies, and traffic conditions. This document is intended as a general guide only. It has not been tested for all possible applications, and it may not be complete or accurate for some situations.
Users of this document are urged to heed warnings interspersed throughout the document, such as traffic disruption warnings. Table 4-1. Task-Oriented Practices TOP TOP 001D Measuring Optical Power Level TOP 007D Using the ACO Switch to Turn Off an Alarm TOP 015D Verifying -48 VDC Supply Voltage TOP 016D Verifying System Grounding TOP 032D Removing and Installing an Air Filter TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 168D Removing and Installing a Circuit Breaker Module TOP 169D Removing and Installing a Cooling Fan Unit TOP 170D Removing and Installing a Control Module TOP 171D Removing and Installing a Switch Module TOP 172D Removing and Installing an Optical Module TOP 173D Removing and Installing a Line Module TOP 174D Removing and Installing a Timing Module TOP 175D Removing and Installing a PDU Display Module TOP 176D Removing and Installing a Fan Power Module TOP 177D Removing and Installing a CoreDirector CI I/O Module TOP 178D CoreDirector Switch Power Up TOP 183D Removing and Connecting the Alarms and Parallel Telemetry Cable TOP 185D Removing and Installing the PDU-B/P Cable TOP 187D Test LEDs Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
Page page 4-3 page 4-7 page 4-9 page 4-11 page 4-15 page 4-17 page 4-19 page 4-23 page 4-27 page 4-35 page 4-41 page 4-53 page 4-73 page 4-77 page 4-81 page 4-85 page 4-89 page 4-91 page 4-97 page 4-99
4-1
4
Task Oriented Practices (TOPS) CoreDirector Switch
Table 4-1. Task-Oriented Practices (Continued) TOP TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface TOP 207D Adding Channel Capacity TOP 208D Configuration Database Backup and Restore TOP 209D Setting Up a CoreDirector Switch for Modem Access TOP 210D CoreDirector Switch Software Upgrade and Restore TOP 211D Software In-Service Reversion TOP 217D CoreDirector Switch Shutdown TOP 218D Pack Up a CoreDirector Switch System TOP 220D Test Line Modules and Optical Modules TOP 221D Test Optical Module TOP 223D Change CoreDirector Switch Name/IP Address TOP 261D Change NE CLI Login User ID and/or Password TOP 262D Recovery from Dual CM Failure TOP 270D Resetting the Primary Control Module (CM Switch) TOP 271D Resetting the Secondary Control Module (CM) TOP 274D IO Panel EEPROM Check TOP 275D Change CoreDirector Initial Install Settings TOP 276D LM-8 to LM-16 Upgrade TOP 278D Handling Circuit Packs Properly TOP 279D Prepare Site Terminal (or Laptop) for Software Transfer TOP 280D Resetting the Primary Timing Module (TM Switch) TOP 281D Resetting the Secondary Timing Module (TM) TOP 282D Decommissioning a CoreDirector Switch TOP 283D FTP Server Setup Page page 4-107 page 4-111 page 4-115 page 4-121 page 4-127 page 4-143 page 4-151 page 4-155 page 4-161 page 4-177 page 4-181 page 4-185 page 4-187 page 4-195 page 4-199 page 4-203 page 4-205 page 4-209 page 4-215 page 4-223 page 4-225 page 4-229 page 4-233 page 4-243
TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch page 4-101
4-2
4
TOP 001D MEASURING OPTICAL POWER LEVEL

OVERVIEW
This Task-Oriented Practice describes how to measure optical power levels on CoreDirector Switch or CoreDirector CI Switch Optical Modules (OMs) and optical ports. This procedure disrupts traffic if performed on traffic carrying OMs.
REQUIRED TOOLS
! ! ! ! ! ! !
ESD-guard wrist strap ESD-guard heel grounders Common hand tools Optical power meter 10base-T, RJ-45 crossover cable Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP CoreDirector Node Manager software
PREREQUISITES
!
The user must use proper module handling procedures. When handling, installing, or removing modules, the following precautions must be observed. Refer to TOP 278D Handling Circuit Packs Properly. Ensure modules are stored in ESD-protective packaging when not installed in an equipment shelf. Do not stack modules on or against each other. Pick up modules by the front handle, and do not touch components on the circuit board.
! !
The user must be familiar with CoreDirector Node Manager software. The user must have Node Manager Termination Point Provisioner privilege or Node Manager Troubleshooter (TS) privilege.
REFERENCED DOCUMENTS
! ! ! !
Ciena Standard Cleaning & Equipment Safety Practices TOP 172D Removing and Installing an Optical Module Node Manager User Guide TOP 278D Handling Circuit Packs Properly

4-3
4
Task Oriented Practices (TOPS) PROCEDURE
CoreDirector Switch
Warning
LASER RADIATION AVOID EXPOSURE TO BEAM CLASS 1 LASER PRODUCT

Laser emissions can cause eye damage. Never look directly into fiber connectors. Always assume that laser radiation is present, even when equipment is turned off.
Traffic Disruption Risk

Risk of Damage to Modules and Backplanes

Caution: Remove all optical connector dust caps from modules and backplane before installing modules.
Risk of Damage to Circuit Packs and Backplanes

850 1300
- - - C
ON dB/dBm
1300 1500
- - - - dBm
1500
B
OFF
- 15
.32
dBm
558B POWER METER
Figure 4-1. Optical Power Meter Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4-4
4
CoreDirector Switch
The steps in these procedures refer to Figure 4-1 above. This TOP consists of the following procedures:
! ! !
Task Oriented Practices (TOPS)
Prepare an OM in an LM-2 or LM-8 Line Module for testing. Prepare an optical port on an LM-16 Line Module for testing. Test the optical module or port.

Caution: If this procedure is being performed on a CoreDirector Switch system that is in service, coordinate this effort with NOC Personnel.
Prepare LM-2 or LM-8 OM for Testing STEP 1: Remove the OM using TOP 172D Removing and Installing an Optical Module. STEP 2: Disconnect the fiber from the transmit bulkhead connector. STEP 3: Clean the OM connector and the Test cable using Ciena Standard Cleaning & Equipment Safety Practices. STEP 4: Connect to the transmit connector of the OM. STEP 5: Reinstall the OM using TOP 172D Removing and Installing an Optical Module. STEP 6: Unlock the optical module/port: a. Select Go > Inventory. b. In the equipment tree, expand the CoreDirector node view until the desired OM/port is displayed and select the OM/port. c. In the details frame, select the Basic tab. d. In the Admin State field of the Details frame, select Unlocked from the Administrative State drop-down menu. e. To enable equipment alarms, select Alarm Reporting from the ARC State drop-down menu. f. Click Accept. STEP 7: Configure the OMs Physical Termination Point (PTP) using Node Manager User Guide, Creating a Physical Termination Point. STEP 8: Perform the optical power test (starting with Step 14). Prepare LM-16 Port for Testing STEP 9: Disconnect the fiber from the transmit bulkhead connector. STEP 10: Clean the Port and the Test cable using Ciena Standard Cleaning & Equipment Safety Practices. STEP 11: Connect to the transmit connector of the desired Port. STEP 12: Configure the Ports Physical Termination Point (PTP) using Node Manager User Guide, Creating a Physical Termination Point. STEP 13: Perform the optical power test (starting with Step 14). Optical Power Test STEP 14: Remove the dust cover (A on Figure 4-1), and connect fiber optic test cable connector to the power meter optical adapter. STEP 15: Set the switch (B) to the On position. Observe that a display is visible. STEP 16: Select the wavelength (C). Observe the options in the upper right corner of the display. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4-5
4
STEP 17: Select the dBm (D). STEP 18: Read the power level value on the meter display (E), and verify that results are within the ranges specified in Table 4-2. Table 4-2. Optical Output Power Ranges for OMs and Optical Ports Port Type 155/622 MR OM (includes LM-16) 2.5G SR OM 2.5G MR OM 2.5G LR OM (LR-1) 2.5G LR OM (LR-2) 10G SR OM (SR-1) 10G SR OM (SR-2) 10G MR OM (MR-2) 10G LR OM (LR-2) 10G WDM-1 OM 10G WDM-2 OM GbE SX GbE LX Output Power Range -15 dBm to -8 dBm -10 dBm to -3 dBm -5 dBm to 0 dBm -2 dBm to +3 dBm -2 dBm to +3 dBm -6 dBm to -1 dBm -5 dBm to -1 dBm -1 dBm to +2 dBm +2 dBm to +4 dBm +4.1 dBm to +7.0 dBm +4 dBm to +5 dBm -9.5 dBm to -4.0 dBm -9.5 dBm to -3.0 dBm
CoreDirector Switch
STEP 19: If required, record results on the applicable data sheet. STEP 20: Reconnect the fiber. --STOP-THIS CONCLUDES THE PROCEDURE
4-6
4
TOP 007D USING THE ACO SWITCH TO TURN OFF AN ALARM

OVERVIEW
This Task-Oriented Practice describes how to turn off an audible alarm using the Alarm Cut-Off (ACO) switch on the CoreDirector Switch Power Distribution Unit (PDU) or CoreDirector CI Switch Display Panel. The ACO switch enables a craftsperson to silence an audible alarm at the node. The ACO switch does not inhibit any other visible indication of the alarm. Furthermore, all subsequent alarms (including audible alarms), continue to be monitored and processed.
REQUIRED TOOLS
! !
ESD-guard wrist strap ESD-guard heel grounders
PREREQUISITES
!
The facility containing the CoreDirector Switch must be equipped with an audible alarm that is connected to the CoreDirector Switch.
!
None
PROCEDURE

STEP 1: To activate the ACO switch, press and momentarily hold the switch, then release. The audible alarm is immediately silenced. --STOP-THIS CONCLUDES THE PROCEDURE

4-7
4
4-8
4
TOP 015D VERIFYING -48 VDC SUPPLY VOLTAGE

OVERVIEW
This Task-Oriented Practice describes how to verify the -48 VDC supply voltage at the CoreDirector Switch or CoreDirector CI Switch using a digital multimeter (DMM).
REQUIRED TOOLS
! ! !
ESD-guard wrist strap ESD-guard heel grounders digital multimeter (DMM)
PREREQUISITES
!
Not Applicable
!
None Note: Observe all safety precautions when performing this procedure.
PROCEDURE
RISK OF PERSONAL INJURY

Warning: Negative 48 volts DC is present in the equipment. Contact can cause personal injury. Take appropriate safety precautions. Refer to Voltage Precaution in the General Safety Precautions on page page xx.


Caution: Performance of the following step may cause a traffic disruption. This instruction is intended as a general guide only, has not been tested for all possible applications or configurations, and may not be complete or accurate for some situations. A polycarbonate cover with meter probe access holes is installed over the power connections on the Power Distribution Unit (PDU). If necessary or if access holes do not exist, the cover can be removed by loosening four screws and removing the cover.
Note:

4-9
4
STEP 1: Connect the meter and measure the power at the lugs. Ensure the polarity is correct, as follows:
!
On a CoreDirector Switch (Figure 4-2): Connect the red (+) meter lead to lug A1, A2, B1, or B2 Connect the black (-) meter lead to lug A1R, A2R, B1R, or B2R) connect the meter and measure the voltage at the lugs. The reading must be within the specified range (-40 VDC to -60 VDC).
On a CoreDirector CI Switch (Figure 4-3): Connect the red (+) meter lead to lug -48DC Load A or -48 DC Load B Connect the black (-) meter lead to lug Return A or Return B) The reading must be within the specified range (-40 VDC to -60 VDC).
A1
A2
B1
B2 A1R A2R B1R B2R
Figure 4-2. CoreDirector Switch Power Distribution Unit -48 VDC Connections
CHASSIS GND
COVER SCREWS (4)
COVER SCREWS (4)
CABLE STRAIN RELIEF CLAMPS
CABLE STRAIN RELIEF CLAMPS RETURN B
RETURN A
A
-48V DC LOAD A
OFF 0 ON 1 OFF 0 ON 1
B
-48V DC LOAD B
Clear Cover Clear Cover Clear Cover
TERMINAL STUDS
Figure 4-3. CoreDirector CI Switch Power Distribution Unit -48 VDC Connections STEP 2: If required, record the measured results on Test Data Sheet 1 - CoreDirector Site Information or CoreDirector CI Site Information. CoreDirector Test Data Sheets are located in Appendix A and CoreDirector CI Test Data Sheets in Appendix B of this manual. STEP 3: If necessary, reinstall the polycarbonate cover, and tighten the four screws to secure the cover. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 10
4
TOP 016D VERIFYING SYSTEM GROUNDING

OVERVIEW
This Task-Oriented Practice describes how to verify proper CoreDirector Switch or CoreDirector CI Switch grounding of the rack and equipment. This procedure can only be performed when power is completely removed from the CoreDirector Switch or CoreDirector CI Switch.
REQUIRED TOOLS
! ! !
ESD-guard wrist strap ESD-guard heel grounders Digital ohmmeter
PREREQUISITES
!
Not Applicable
!
None
PROCEDURE



STEP 1: At the Battery Distribution Fuse Bay (BDFB), ensure that the circuit breakers supplying -48 VDC power to the Power Distribution Unit (PDU) are opened and tagged Out of Service. STEP 2: Turn on the ohmmeter and select the lowest (100-ohm or Rx1) resistance range. STEP 3: Touch the ohmmeter test leads together to ensure that the meter is working properly. The meter should read 0 ohms. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 11
4
STEP 4: Connect one ohmmeter test lead to a grounded cable lug on the PDU. STEP 5: Connect the other DMM test lead to the ground cable lug located on the equipment rack end of the PDU-to-equipment-rack ground cable strap.
! !
If ground is being tested on a CoreDirector system refer to Figure 4-4. If ground is being tested on a CoreDirector CI system refer to Figure 4-5. The reading must be less than 1 ohm. A resistance greater than 1 ohm indicates an improperly grounded system, and additional troubleshooting must be performed to rectify the problem.
STEP 6: Read the ohmmeter display.
STEP 7: If required, record the measured results on Test Data Sheet 1 - CoreDirector Site Information or CoreDirector CI Site Information. CoreDirector Test Data Sheets are located in Appendix A and CoreDirector CI Test Data Sheets in Appendix B of this manual. STEP 8: Remove the ohmmeter test lead from the grounded cable lug on the PDU, and connect it to facility ground. STEP 9: Read the ohmmeter display. The reading must be less than 1 ohm. A resistance greater than 1 ohm indicates an improperly grounded system, and additional troubleshooting must be performed to rectify the problem. STEP 10: If required, record the measured results on Test Data Sheet 1 - CoreDirector Site Information or CoreDirector CI Site Information. CoreDirector Test Data Sheets are located in Appendix A and CoreDirector CI Test Data Sheets in Appendix B of this manual.
GROUND CABLE BRACKETS
To C.O. or Building Ground

H-TAP WITH COVER EQUIPMENT RACK-TO-FACILITY GROUND STRAP PDU-TO-EQUIPMENT RACK GROUND STRAP
EQUIPMENT RACK (TOP RAIL)

FROM FACILITY BATTERY DISTRIBUTION FUSE BAY (BDFB)
PDU
Figure 4-4. CoreDirector Switch System Grounding Scheme (Typical)
4 - 12
4
GROUND CABLE BRACKETS
To C.O. or Building Ground
EQUIPMENT RACK-TO-FACILITY GROUND STRAP H-TAP WITH COVER
PDU-TO-EQUIPMENT RACK GROUND STRAP
EQUIPMENT RACK (TOP RAIL)
CABLE STRAIN RELIEF CLAMP
CHASSIS GND TERMINAL STUDS
PDU
FROM FACILITY BATTERY DISTRIBUTION FUSE BAY (BDFB) CIRCUIT BREAKER A CIRCUIT BREAKER B
RET A
-48V A
OFF 0
ON 1
OFF 0
ON 1
TOGGLE SWITCH EQUIPMENT RACK (SIDE RAIL)
Figure 4-5. CoreDirector CI Switch System Grounding Scheme (Typical) --STOP-THIS CONCLUDES THE PROCEDURE

4 - 13
4
4 - 14
4
TOP 032D REMOVING AND INSTALLING AN AIR FILTER

OVERVIEW
This Task-Oriented Practice describes how to remove and install the air filter in a CoreDirector Switch or CoreDirector CI Switch. Ciena recommends that CoreDirector air filters be removed and replaced every 6 months. Refer to Fan Filter Maintenance on page 3-1 for additional information. Note: An excessively dirty air filter, if not replaced, could cause airflow problems resulting in bay cooling alarms generated by the CoreDirector Switch.
REQUIRED TOOLS
! !
PREREQUISITES
!
CoreDirector Switch air filter, Ciena Part Number 410-6074-100 and Ciena part name AIRFILTER-CD-A. CoreDirector CI Switch air filter, Ciena Part Number 399-8005-001 and Ciena part name AIRFILTER-CI-A. Note: After the replacement air filter is installed, reorder spare replacement filters to ensure availability during the next maintenance cycle.
!
None
PROCEDURE

This is a single removal and installation procedure. Do not execute this procedure without a replacement air filter available. Remove Filter STEP 1: On the lower air inlet cover located at the bottom of the CoreDirector Switch chassis (Figure 4-6), turn the top two screws one quarter-turn counterclockwise, and remove the cover. STEP 2: Slide the filter out from its mounting tracks.

4 - 15
4
ACO LED
FAN A
FAN B
CONTROL M ODULE
........ .......
ALARM
MAINT
NORMAL
CONTROL M ODULE
CONTROL MODULE
........ .......
........ .......
Filtered Air Intake
CoreDirector Switch
CoreDirector CI Switch
Figure 4-6. Air Filter Locations Install Filter Note: When installing the filter, ensure that the airflow direction arrows on the front edge of the filter point toward the top of the rack.
STEP 3: Install the replacement filter into the mounting tracks, and slide the filter toward rear of the rack until it stops and is held in place by the filter retaining clips. STEP 4: Align the lower air inlet cover in the rack and turn the top screws clockwise one quarter-turn to tighten them. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 16
4
TOP 072D CIENA RETURN MATERIAL AUTHORIZATION (RMA) PROCEDURE

OVERVIEW
This Task-Oriented Practice describes how to obtain a Ciena Return Material Authorization (RMA) number and how to return a defective item (for example, a module) to Ciena.
REQUIRED TOOLS
! ! ! !
ESD-guard wrist strap ESD-guard heel grounders Common hand tools Antistatic bag or antistatic box
PREREQUISITES
!
The user must use proper module handling procedures. When handling, installing, or removing modules, the following precautions must be observed. Ensure modules are stored in ESD-protective packaging when not installed in an equipment shelf. Do not stack modules on or against each other. Pick up modules by the front handle, and do not touch components on the circuit board.
An antistatic bag or box must be available for the removed module
!
TOP 278D Handling Circuit Packs Properly
PROCEDURE

Caution: This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. All returned equipment must have a Ciena RMA number. Ciena is not responsible for any item returned without this identifier.
Note:
STEP 1: Obtain an RMA number by contacting the Ciena Customer Support Representative (CSR) and providing the following information: Serial number of item to be returned Model number of item to be returned Description of problem Return address and phone number Declaration of emergency or non-emergency condition

4 - 17
4
Note: Ciena assigns an RMA number, which is added to the RMA database and is used to track the defective item. The replacement item will be shipped to the customer, based upon the terms of the Customer Contract for Warranty (repair or replace).
STEP 2: Refer to TOP 278D Handling Circuit Packs Properly and follow proper module handling procedures. STEP 3: After the replacement item has been unpacked and installed, reuse the shipping container and packing materials to return the defective item to Ciena. If the defective item is a module, install clean dust caps over the optical connectors. If the shipping label is lost, use the following address to return the item: Ciena Corporation 900 International Drive Linthicum, MD 21090 ATTN: RMA Receiving STEP 4: Affix the preprinted air bill to the shipping container. STEP 5: Arrange for the shipper to collect the shipping container. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 18
4
TOP 168D REMOVING AND INSTALLING A CIRCUIT BREAKER MODULE

OVERVIEW
This Task-Oriented Practice describes how to remove and install a circuit breaker module from the front of the CoreDirector Switch or CoreDirector CI Switch Power Distribution Unit (PDU).
REQUIRED TOOLS
! ! ! ! ! !
ESD-guard wrist strap ESD-guard heel grounders Common hand tools 10base-T, RJ-45 crossover cable Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP CoreDirector Node Manager software
PREREQUISITES
!
The user must use proper module handling procedures. When handling, installing, or removing modules, the following precautions must be observed. Ensure modules are stored in ESD-protective packaging when not installed in an equipment shelf. Do not stack modules on or against each other. Pick up modules by the front handle, and do not touch components on the circuit board.
! !
The user must be familiar with CoreDirector Node Manager software. The user must have Node Manager Termination Point Provisioner privilege or Node Manager Troubleshooter (TS) privilege. Before performing this procedure, the following tasks must be performed: Current CoreDirector Switch alarms must be noted.
! ! !
TOP 015D Verifying -48 VDC Supply Voltage TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface
PROCEDURE
Negative 48 volts DC is present in the equipment. Contact can cause personal injury. Take appropriate safety precautions. If the feed power cannot be turned off when removing or installing a circuit breaker module, be careful not to touch or short the power receptacles inside the PDU circuit breaker module slot. These receptacles have a -48VDC potential on them. Refer to Voltage Precaution in the General Safety Precautions on page page xx.
Warning:

4 - 19
4

Caution: Performance of the following step may cause a traffic disruption. This instruction is intended as a general guide only, has not been tested for all possible applications or configurations, and may not be complete or accurate for some situations. Circuit breaker modules can be changed individually on a per-feed basis (A or B battery); while one circuit breaker is removed, the other feed keeps the CoreDirector Switch operational. Therefore, at the Battery Distribution Fuse Bay (BDFB), turn off only the circuit breaker corresponding to the circuit breaker module requiring removal or installation. If for some reason the desired individual feed (A or B battery) cannot be turned off, the circuit breaker module can be removed or installed with the feed power left on, as long as the circuit breaker module is switched to the OFF position.
Note:
This is a single removal and installation procedure. Do not execute this procedure without a replacement circuit breaker module available. This procedure consists of two tasks:
! !
To remove the module, Step 1 through Step 9 are performed. To install the module, Step 10 through Step 17 are performed.
Remove Circuit Breaker Module STEP 1: Establish a Node Manager session with the CoreDirector Switch. Note: Replaceable Unit alarms are reported while this procedure is performed.
STEP 2: At the BDFB, ensure that the circuit breakers supplying -48 VDC power to the desired PDU feed are open and tagged Out of Service. STEP 3: For the circuit breaker module being removed, verify that -48 VDC is not present by executing TOP 015D Verifying -48 VDC Supply Voltage. STEP 4: At the front of the CoreDirector Switch, remove the PDU cover: a. Pull outward on the lower corners of the cover to unsnap the stud fasteners. b. Lift the PDU cover off the top hinge screws. STEP 5: On the circuit breaker module being removed, position each circuit breaker to OFF. STEP 6: Loosen the two screws securing the circuit breaker module in the PDU. STEP 7: Lift up the circuit breaker module ejector handle, and slide the circuit breaker module out of the PDU. STEP 8: Disconnect the sensing wire connectors and completely remove the circuit breaker module. STEP 9: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 20
4
CoreDirector Switch
Install Circuit Breaker Module STEP 10: At the front of the CoreDirector Switch, connect the circuit breaker module sensing wire connector to the mating sensing wire connector inside the PDU circuit breaker module slot. STEP 11: Check the position of the sensing wire connector and the wires at the side of the circuit breaker module slot. If they will interfere with the mating of the circuit breaker module pins to the receptacles inside the PDU, move them out of the way. STEP 12: Slide the circuit breaker module firmly into the PDU. STEP 13: Tighten the two screws securing the circuit breaker module in the PDU. STEP 14: Close the BDFB circuit breaker that provides -48 VDC power to the circuit breaker module being installed, and remove the tag. STEP 15: Reset the circuit breaker module by setting each circuit breaker to the fully OFF position, then moving each circuit breaker to ON. STEP 16: Verify that there are no power related alarms or Replaceable Unit alarms. If power related alarms or Replaceable Unit alarms exist, refer to the Alarm and Trouble Clearing Procedure Manual and/or contact the next level of support. STEP 17: At the front of the CoreDirector Switch, replace the PDU front cover on the top hinge screws, and apply pressure on the lower left and lower right corners to snap it into place. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 21
4
4 - 22
4
TOP 169D REMOVING AND INSTALLING A COOLING FAN UNIT

OVERVIEW
This Task-Oriented Practice describes how to remove and install a CoreDirector Switch Cooling Fan Unit (CFU) or CoreDirector CI Switch Blower Module. When a CFU/Blower Module malfunctions or is removed from the rack, the remaining unit automatically compensates by switching to a higher speed.
REQUIRED TOOLS
! ! ! ! ! !
PREREQUISITES
!
The user must be trained in proper module handling procedures. When handling, installing, or removing modules, the following precautions must be observed. Ensure modules are stored in ESD-protective packaging when not installed in an equipment shelf. Do not stack modules on or against each other. Pick up modules by the front handle, and do not touch components on the circuit board.
! !
! ! !
Node Manager User Guide, Enabling/Disabling Module Alarm Reporting TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface
PROCEDURE

Caution: This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. Modules can be hot-swapped; CoreDirector power does not need to be removed.
Note:

4 - 23
4
This is a single removal and installation procedure. Do not execute this procedure without a replacement fan available.
! ! ! !
To lock and remove the CoreDirector CFU, Step 1 through Step 7 are performed. To lock and remove the CoreDirector CI Blower Module, Step 8 through Step 12 are performed. To install and unlock the CoreDirector CFU, Step 13 through Step 20 are performed. To install and unlock the CoreDirector CI Blower Module, Step 21 through Step 26 are performed.
Removing the CoreDirector CFU STEP 1: Establish a Node Manager session with the CoreDirector Switch. STEP 2: Disable module equipment alarm reporting as follows: Note: a. b. c. d. Replaceable Unit alarms are reported if module alarm reporting is not disabled.
From the menu bar, select Go > Inventory. In the equipment tree, expand the CoreDirector node view and select the desired module. In the details frame, select No Alarm Reporting from the ARC State drop-down menu. Click Accept.
STEP 3: At the front of the CoreDirector Switch, remove the PDU cover: a. Pull outward on the lower corners of the cover to unsnap the stud fasteners. b. Lift the PDU cover off the top hinge screws. STEP 4: Remove the fan cover: a. Turn the two fan cover screws counterclockwise one quarter-turn to loosen them. b. Swing the front cover up and lift it off the top hinge screw. STEP 5: Loosen the two screws securing the CFU in the fan shelf (Figure 4-7).
SCREWS
CD9909-4
Figure 4-7. CoreDirector Switch CFU STEP 6: Slide the CFU out of the shelf.
4 - 24
4
STEP 7: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. Removing the CoreDirector CI Blower Module STEP 8: Establish a Node Manager session with the CoreDirector CI Switch. STEP 9: Disable module equipment alarm reporting Note: a. b. c. d. Replaceable Unit alarms are reported if module alarm reporting is not disabled.
STEP 10: At the front of the CoreDirector CI loosen the two screws securing the blower module in the fan shelf (Figure 4-8). STEP 11: Slide the blower module out of the shelf. STEP 12: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure.
SCREWS Figure 4-8. CoreDirector CI Blower Module Installing the CoreDirector CFU STEP 13: At the front of the CoreDirector Switch, place the CFU between the guide rails and slide it back until it stops. STEP 14: Secure the CFU by tightening the two screws (Figure 4-7). STEP 15: Verify the following LED indications for the newly installed CFU module: - Green LED is lit. - Red LED is off. STEP 16: If the CFU is not operational, contact the next level of support. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 25
4
STEP 17: Reinstall the fan cover: a. Set the fan cover on the top hinge screws. b. Turn the screws clockwise one quarter-turn to tighten. STEP 18: Using the Node Manager session, enable module equipment alarm reporting as follows: a. b. c. d. From the menu bar, select Go > Inventory. In the equipment tree, expand the CoreDirector node view and select the desired module. In the details frame, select Alarm Reporting from the ARC State drop-down menu. Click Accept.
CoreDirector Switch
STEP 19: Verify that there are no cooling related alarms. If cooling related alarms exist, refer to the Alarm and Trouble Clearing Procedure Manual and/or contact the next level of support. STEP 20: At the front of the CoreDirector Switch, replace the PDU cover on the top hinge screws, and apply pressure on the lower left and lower right corners to snap it into place. Installing the CoreDirector CI Blower Module STEP 21: At the front of the CoreDirector CI Switch, place the blower module between the guide rails and slide it back until it stops. STEP 22: Secure the blower module by tightening the two screws (Figure 4-8). STEP 23: Using the Node Manager session, examine the values for Fan Speed and Load to ensure that the fan is operational. STEP 24: If the blower module is not operational, contact the next level of support. STEP 25: Using the Node Manager session, enable module equipment alarm reporting as follows: a. b. c. d. From the menu bar, select Go > Inventory. In the equipment tree, expand the CoreDirector node view and select the desired module. In the details frame, select Alarm Reporting from the ARC State drop-down menu. Click Accept.
STEP 26: Verify that there are no cooling related alarms. If cooling related alarms exist, refer to the Alarm and Trouble Clearing Procedure Manual and/or contact the next level of support. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 26
4
TOP 170D REMOVING AND INSTALLING A CONTROL MODULE

OVERVIEW
This Task-Oriented Practice describes how to remove and install a Control Module (CM) in a CoreDirector Switch or CoreDirector CI Switch. Normally, there are two CMs in a CoreDirector Switch system. In a CoreDirector Switch, one CM is in the extreme right module slot of Shelf A, and the other is in the extreme left module slot of Shelf C. In a CoreDirector CI Switch, the CMs are in the slots immediately on either side of the switch modules and timing modules. Note: If the primary CM needs to be removed, this procedure checks the status of the secondary CM and performs a CM switch to change the status of the CM to secondary prior to removal.
REQUIRED TOOLS
! ! ! ! !
ESD-guard wrist strap ESD-guard heel grounders Common hand tools 10base-T, RJ-45 crossover cable One or both of the following cables: 9-pin to 25-pin RS-232 serial cable (DB-9F to DB-25M straight cable) for connection to the CM. The 9-pin connector is configured for Data Terminal Equipment (DTE), and the 25-pin connector is configured for Data Communications Equipment (DCE). 9-pin to 9-pin RS-232 serial cable (DB-9F to DB-9F null modem cable) for connection to the backplane I/O panel. Both connectors of a null modem cable are configured for DTE.
! !
Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP CoreDirector Node Manager software
PREREQUISITES
!
! !
The user must be familiar with CoreDirector Node Manager software. The user must have Node Manager Termination Point Provisioner (TP) privilege or Node Manager Troubleshooter (TS) privilege. The user must be a registered system user with a valid user name and password to log in to the Command Line Interface (CLI). Before performing this procedure, the following tasks must be performed: Current CoreDirector Switch alarms must be noted. When replacing a module, the user must ensure that the replacement module is available and that the part number and revision level are correct.

4 - 27
4
Task Oriented Practices (TOPS) REFERENCED DOCUMENTS
! ! ! ! ! ! !
CoreDirector Switch
TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface TOP 262D Recovery from Dual CM Failure TOP 270D Resetting the Primary Control Module (CM Switch) TOP 271D Resetting the Secondary Control Module (CM) TOP 278D Handling Circuit Packs Properly
PROCEDURE

Caution: This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. Any module left incompletely seated (or partially removed) may cause the system to become susceptible to Electrostatic Discharge (ESD) effects.
Risk of Equipment Damage

Caution: Improper module removal or installation could result in bent pins. Follow the removal and insertion steps carefully.

If both CMs are failed, refer to TOP 262D Recovery from Dual CM Failure for the proper procedure to removing and replacing both CMs. Caution: In rare occasions, removing both CMs at the same time can result in traffic disruption. Ensure a replacement CM is operational and that the databases are synched prior to removing the primary CM. Ciena advises verification that the secondary CM database is synchronized to the primary CM prior to removing the primary CM. To prepare a CM for removal, perform Step 1 through Step 9. To remove the CM, perform Step 10 through Step 14. To install the CM, perform Step 15 through Step 22. To verify CM status, perform Step 23 and Step 25. Modules can be hot-swapped; CoreDirector power does not need to be turned off for these procedures to be performed. Disable module alarm reporting prior to removal and enable alarm reporting after installation. If required, refer to The Node Manager User Guide.
Note:
4 - 28
4
CoreDirector Switch
Prepare CM for Removal Note: Replaceable Unit alarms are reported if module alarm reporting is not disabled.
STEP 1: Using one of the following methods, identify the primary and secondary CM: At the CoreDirector Switch, observe the ACTIVE LED on the CM. Flashing indicates secondary CM and solid indicates primary CM. Note the CM roles. Establish a HyperTerminal (TOP 194D) to one of the CMs and log on using the appropriate username and password. (The default user name is superuser and the default password superuser1!.) From the CM CLI menu, type 2 to display general information about this CM and press Enter. Note the CM role. Establish a remote Telnet session to one of the CMs and log on using the appropriate username and password. (The default user name is superuser and the default password superuser1!.) From the Windows Start menu, select Run. Type telnet <CoreDirector IP address> and press Enter. From the CM CLI menu, type 2 to display general information about this CM and press Enter. Note the CM role. Establish a CoreDirector Node Manager session and click Go > Inventory. Select the desired CM from the Equipment tree and check standby status in the Details frame. Hot Standby indicates the secondary module. In Service indicates the primary module. STEP 2: If the Secondary CM requires removal, skip to Step 5. If the Primary CM requires removal, use one of the following methods to determine secondary CM synchronization state: At the CoreDirector Switch, observe the red Fail and yellow MAINT LED on the CM are off and the green ACTIVE LED is winking. Connect to the Secondary CM and from the CM CLI Menu, type 2 and press Enter to display general information about this CM. Verify that Current Role is Secondary (DB up to date). If not, secondary has not completed synchronization. Use Node Manager Inventory screen and ensure that Secondary CM Procedural Status is Synchronized and the Operational State is Enable. STEP 3: If the secondary CM is not synchronized with the primary CM, perform TOP 271D Resetting the Secondary Control Module (CM). STEP 4: After the secondary CM reboot and synchronization are complete, perform TOP 270D Resetting the Primary Control Module (CM Switch) to switch the CM role. Note: After a CM switch, the CM takes about three minutes to be fully functional; therefore, OSRP link mesh restoration times are extended.
STEP 5: If required, establish a CoreDirector Node Manager session. STEP 6: Disable secondary CM alarm reporting as follows: Note: Replaceable Unit alarms are reported if module alarm reporting is not disabled.

4 - 29
4
a. b. c. d.
CoreDirector Switch
STEP 7: At the front of the CoreDirector Switch, loosen the two screws securing the CM. STEP 8: If required, establish a HyperTerminal or remote Telnet session to the CM to be removed and log on using the appropriate username and password. (The default user name is superuser and the default password superuser1!.) a. From the CM CLI Menu, type the number to select Operations Menu and press Enter. b. Enter option number to Reset This CM and press Enter. c. Type Y to confirm message to reset CM. Note: If required, refer to TOP 270D Resetting the Primary Control Module (CM Switch) or TOP 271D Resetting the Secondary Control Module (CM) to reset the CM.
STEP 9: Continue procedure within three minutes of issuing the reset to remove the CM. Remove CM

Caution: Improper module removal could result in bent pins. Follow the removal steps carefully.

Caution: This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. Any module left incompletely seated (or partially removed) may cause the system to become susceptible to Electrostatic Discharge (ESD) effects. All CoreDirector modules are designed such that when inserted, the air gaps between the faceplates are minimal. This provides a continuous low impedance ground path for Electromagnetic Interference and Susceptibility compliance, ESD compliance, and a path to chassis ground for safety. However, the tight tolerance could cause the module face plate to be bound in the slot and difficult to remove. If required, loosen the faceplate screws of the adjacent modules on either side as needed and then remove the module.
Note:
STEP 10: Simultaneously apply equal pressure and move both the ejectors into the open position (perpendicular to the module faceplate). Take care to use equal pressure and remove the module using the guide rails in a level straight-backward motion. STEP 11: If a cable is connected to the Craft RS-232 port on the CM, disconnect the cable. STEP 12: Place the module in an ESD-guard antistatic bag.
4 - 30
4
If the CM is not immediately replaced with a spare, use the Node Manager session to delete the module from inventory then proceed to Step 19 and close the open slot by installing a Control Module filler panel model CM-BLANK and end this procedure (no further action is required). If the correct blank is not available, contact Ciena Technical Support.
Note:
STEP 13: Check slot backplane connector and verify no bent pins are present. If CoreDirector is suspected of having damage, stop this procedure and contact Ciena Technical Support for assistance. STEP 14: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. --STOP-THIS CONCLUDES THE PROCEDURE Install CM

Caution: Improper module installation could result in bent pins. Follow the insertion steps carefully.

Caution: This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. Any module left incompletely seated (or partially removed) may cause the system to become susceptible to Electrostatic Discharge (ESD) effects. When replacing a module, ensure that the replacement module part number and revision level are correct. All CoreDirector modules are designed such that when inserted, the air gaps between the faceplates are minimal. This provides a continuous low impedance ground path for Electromagnetic Interference and Susceptibility compliance, ESD compliance, and a path to chassis ground for safety. There could be insufficient space for the module face plate to fit securely against the chassis. If required, loosen the faceplate screws of the adjacent modules on either side as needed and then install the module.
Note:
STEP 15: At the front of the CoreDirector Switch, check CM slot backplane connector and verify no bent pins are present. If CoreDirector is suspected of having damage, stop this procedure and contact Ciena Technical Support for assistance. STEP 16: Remove the replacement CM from the ESD-guard antistatic bag by holding the front faceplate and carefully sliding the replacement CM from the ESD-guard antistatic bag. For support of the module, one hand can be placed under the pan (the side without board components). Note: If the circuit pack was incorrectly inserted with the faceplate facing the wrong direction, place one hand under the pan and carefully rotate the circuit pack so the circuit pack can be removed from the bag.

4 - 31
4
If the bag is not large enough to rotate the circuit pack, place one hand under the pan and carefully remove the circuit pack from the bag until the face plate can be grabbed. This should be done over a flat surface since there is a possibility of dropping the circuit pack. Never pull the circuit pack out of the bag by applying pressure to the pan and the component boards. Such handling can cause damage to certain boards that do not have added stiffeners to support such pressure (for example, the VI processor daughter board). To prevent damage to circuit packs, always handle the circuit packs by the faceplate side.
Note:
STEP 17: Inspect the module connector block for damage or misalignment. Do this by visually inspecting each of the connector blocks to verify that they are properly seated and flush on the Printed Circuit Board (PCB). As a second inspection method, look at the top of all the blocks; they should appear planar and horizontally aligned. Refer to TOP 278D Handling Circuit Packs Properly for additional information. If connector block is suspected of having damage, repeat Step 12 through Step 14 with the damaged module and continue the procedure at Step 15 with another replacement module. STEP 18: Check slot backplane connector and verify no bent pins are present. If backplane connector is suspected of having damage, contact Ciena Technical Support for assistance. STEP 19: Install the module as follows: a. Insert the module into the guide rails of the designated slot. Slowly slide the module into the slot by pushing on the module faceplate until the top and bottom ejectors engage the ejector bracket and begin to rotate as shown in Figure 4-9. Take care to insert the module using the guide rails in a level, straight-forward motion and visually inspect for proper CM faceplate fit while moving both ejectors into the closed position. If required, loosen the faceplate screws of the adjacent modules as needed and then reinstall the circuit pack. b. Simultaneously apply equal pressure to move both the ejectors into the closed position. c. Ensure that the faceplate is flush against the chassis then tighten faceplate screws.

Caution: Improper module insertion could result in bent pins. Carefully install the module in accordance with the following step. Do not engage handles independently.
STEP 20: If required, use Node Manager to enable alarm reporting as follows: a. b. c. d. From the menu bar, select Go > Inventory. In the equipment tree, expand the CoreDirector node view and select the desired module. In the details frame, select Alarm Reporting from the ARC State drop-down menu. Click Accept.
4 - 32
4
Figure 4-9. CM Insertion
STEP 21: Verify CM has completed the boot sequence by performing one of the following: a. At the CoreDirector Switch, observe the ACTIVE LED on the CM. Flashing indicates secondary CM and solid indicates primary CM. b. From Inventory on Node Manager, select the appropriate CM from the Inventory Equipment Tree and note the Operational State. c. Verify that Serial #, Card Type, CLEI, Asmb. Part #, Mfg. Date, Model ID, Ext. Model ID, and ECI fields contain the appropriate information. STEP 22: If the fields are empty or do not contain the appropriate information or if ACTIVE LED is not green, perform the following: a. Verify if a CM red alarm is present.

4 - 33
4
If a CM red alarm indication exists, perform TOP271D to reset the secondary CM and reseat the module. If the problem persists, contact the next level of technical support. Verify CM Synchronization Secondary CM synchronization can take between 30 minutes and several hours depending upon database size and CoreDirector Switch activity. Contact Ciena Technical Support if the secondary CM database does not synchronize with the primary CM.
Note:
STEP 23: If secondary CM not present, go to Step 25. STEP 24: Monitor secondary CM synchronization state using one of the following methods until the replaced CM synchronizes with the primary CM:
!
Connect to the Secondary CM and from the CM CLI Menu, type 2 and press Enter to display general information about this CM. Verify that Current Role is Secondary (DB up to date). If not, secondary has not completed synchronization. If current roles displays Primary, repeat Step 23 on the other CM. At the CoreDirector Switch, observe the red Fail and yellow MAINT LED on the CM are off and the green ACTIVE LED is winking. Use Node Manager Inventory screen and ensure that Secondary CM Procedural Status is Synchronized and the Operational State is Enable.
STEP 25: If a CM red alarm indication exists, perform TOP 271D Resetting the Secondary Control Module (CM) procedure and unplug and reseat the secondary CM. If the problem persists, contact the next level technical support. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 34
4
TOP 171D REMOVING AND INSTALLING A SWITCH MODULE

OVERVIEW
This Task-Oriented Practice describes how to remove and install a Switch Module (SM) in a CoreDirector Switch or CoreDirector CI Switch. In the CoreDirector Switch, slots B-1 through B-15 are designated as SM slots. In the CoreDirector CI Switch, slots A-SM-1 through A-SM-4 are designated as SM slots.
REQUIRED TOOLS
! ! ! ! ! !
PREREQUISITES
!
! !
The user must be familiar with CoreDirector Node Manager software. The user must have Node Manager Termination Point Provisioner privilege or Node Manager Troubleshooter (TS) privilege. Before performing this procedure, the following tasks must be performed: Current CoreDirector Switch alarms must be noted. When replacing a module, the user must ensure that the replacement module is available and that the part number and revision level are correct.
! ! ! !
Node Manager User Guide TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface TOP 278D Handling Circuit Packs Properly

4 - 35
4
CoreDirector Switch


Caution: Performance of the following procedure may cause a traffic disruption. Step 1 ensures that the minimum number of SMs will be present after the SM is removed to support existing traffic.
To prepare a SM for removal, perform Step 1 through Step 3. To remove the SM, perform Step 4 through Step 8. To install the SM, perform Step 9 through Step 18. Note: Disable module alarm reporting prior to removal and enable alarm reporting after installation. If required, refer to The Node Manager User Guide. Replaceable Unit alarms are reported if module alarm reporting is not disabled.
Prepare SM for Removal STEP 1: Using the information in Table 4-3 and Table 4-4,ensure that removing an SM leaves the minimum number of SMs still installed in the CoreDirector Switch for the number of installed OMs and optical ports. Note: UPSR/SNCP requires a minimum of 14 SMs for the CoreDirector and 4 SMs for the Coredirector CI.
Table 4-3. Mapping Primary SMs to Supported LM OMs/Ports on CoreDirector Switch Number of Primary SMs Installed 1 2 3 4 5 6 7 Line Module Type 0 Maximum number of ports supported LM-2 (OMs) LM-8 (OMs) LM-20 (OPs) 0 0 0 0 0 3 0 0 1 6 0 0 2 9 0 0 3 9 0 0 3 9 0 1 4 16 10 1 4 16 10 8 1 4 16 10 9 1 4 16 10 10 1 4 16 10 11 1 4 16 10 12 2 8 16 20 13 2 8 16 20 14 2 8 16 20
LM-16 (OPs & EPs) 0
4 - 36
4
Table 4-4. Mapping Primary SMs to Supported LM OMs/Ports on CoreDirector CI Switch Number of Primary SMs Installed 1 2 3 Line Module Type 0 Maximum number of ports supported LM-2 (OMs) LM-8 (OMs) LM-20 (OPs) 0 0 0 0 3 12 0 1 6 16 10 2 8 16 20 4 2 8 16 20
LM-16 (OPs & EPs) 0
STEP 2: Establish a Node Manager session with the CoreDirector Switch. STEP 3: Lock the module as follows: Note: a. b. c. d. e. Remove SM STEP 4: At the front of the CoreDirector Switch, loosen the two screws securing the SM. STEP 5: Simultaneously apply equal pressure and move both the ejectors into the open position (perpendicular to the module faceplate). Take care to use equal pressure and remove the module using the guide rails in a level straight-backward motion. Replaceable Unit alarms are reported if module alarm reporting is not disabled.
From the menu bar, select Go > Inventory. From the equipment tree, expand the node view and select the desired module. In the details frame, change the ARC State to No Alarm Reporting and click Accept. Select Locked from the Admin State drop-down menu. Select Prepare to Unseat Card and click Accept.

STEP 6: Place the module in an ESD-guard antistatic bag. If the SM is not immediately replaced with a spare, use the Node Manager session to delete the module from inventory then proceed to Step 12, and close the open slot by installing an Switch Module filler panel model SM-Blank and end this procedure (no further action is required). If the correct blank is not available, contact Ciena Technical Support.
Note:
STEP 7: Check slot backplane connector and verify no bent pins are present. If CoreDirector is suspected of having damage, stop this procedure and contact Ciena Technical Support for assistance. STEP 8: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. --STOP-THIS CONCLUDES THE PROCEDURE Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 37
4
Install SM Note: When replacing a module, ensure that the replacement module part number and revision level are correct.
CoreDirector Switch
STEP 9: At the front of the CoreDirector Switch, remove the replacement module from the ESD-guard antistatic bag. STEP 10: Inspect the module connector block for damage or misalignment. Do this by visually inspecting each of the connector blocks to verify that they are properly seated and flush on the Printed Circuit Board (PCB). As a second inspection method, look at the top of all the blocks; they should appear planar and horizontally aligned. Refer to TOP 278D Handling Circuit Packs Properly for additional information. If connector block is suspected of having damage, repeat Step 6 through Step 8 with the damaged module and continue the procedure at Step 9 with another replacement module. STEP 11: Check slot backplane connector and verify no bent pins are present. If backplane connector is suspected of having damage, contact Ciena Technical Support for assistance. STEP 12: Slowly slide the module into the designated slot by pushing on the module faceplate until the top and bottom ejectors engage the ejector bracket and begin to rotate as shown in Figure 4-10. Take care insert the module using the guide rails in a level, straight-forward motion.

STEP 13: Tighten the two screws to secure the SM. STEP 14: Verify that the SM is operational by observing that the green ACTIVE LED is lit. When an SM is replaced or reinserted but does not come up in 60 seconds, reseat the SM. If the SM still does not come up then replace and RMA the SM. STEP 15: If required, use the Node Manager session to unlock the module as follows: a. From the Node Manager menu bar, select Go > Inventory. b. From the equipment tree, expand the CoreDirector node view and select the SM installed in Step 12. c. In the details frame, select Unlocked from the Admin State drop-down menu. d. In the Details frame, change ARC State to Alarm Reporting and click Accept. STEP 16: Verify that Serial #, Card Type, CLEI, Asmb. Part #, Mfg. Date, Model ID, Ext. Model ID, and ECI fields contain the appropriate information. STEP 17: Verify that there are no Replaceable Unit or Data Plane Health Failure related alarms. The SM does not have a microprocessor and relies on dedicated hardware to control LEDs. Under certain failure conditions the LEDs might get out of sync with the alarm state as indicated by the CM to ON-Center Switching Manager (CSM) Software or Node Manager. Craft Interface personnel should rely on CSM Software and Node Manager statements of alarms/conditions for SM related alarms.
Note:
STEP 18: If related alarms exist, refer to the Alarm and Trouble Clearing Procedure Manual and/or contact the next level of support. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 38
4
Figure 4-10. SM Insertion --STOP-THIS CONCLUDES THE PROCEDURE

4 - 39
4
4 - 40
4
TOP 172D REMOVING AND INSTALLING AN OPTICAL MODULE

OVERVIEW
This Task-Oriented Practice describes how to remove and install an Optical Module (OM) in an LM-8 or LM-2 Line Module (LM). This procedure is applicable in the following three situations:
!
An OM is removed and reinstalled in the same slot from which it was removed. Alternatively, the original OM, installed site fiber cables, and replacement OM all have the same type of connectors. The original OM and installed site fiber cables have SC connectors, and the replacement OM has LC connectors. The original OM and installed site fiber cables have LC connectors, and the replacement OM has SC connectors.
REQUIRED TOOLS
! ! ! ! ! !
ESD guard wrist strap ESD guard heel grounders Common hand tools 10base-T, RJ-45 crossover cable Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP CoreDirector Node Manager software Note: If the connector type on a replacement OM does not match the connector type of the original OM and the installed site fiber cables, fiber pigtail cables and adapters will be necessary as noted in Table 4-5 on page 4-46.
PREREQUISITES
!
The user must follow proper module-handling procedures. When handling, installing, or removing modules, the following precautions must be observed. Refer to TOP 278D Handling Circuit Packs Properly. Store modules in ESD protective packaging when they are not installed in an equipment shelf. Do not stack modules on or against each other. Pick up modules by the front handle, and do not touch components on the circuit board.
! !
The user must be familiar with CoreDirector Node Manager software. The user must have Node Manager Termination Point Provisioner privilege or Node Manager Troubleshooter (TS) privilege. Before performing this procedure, the following tasks must be performed: Line-side alarms or line-side span switch activity on the adjacent nodes must be cleared. OM UPSR, VLSR, or TAP associations must be deleted. Current CoreDirector Switch alarms must be noted. When replacing a module, the user must ensure that the replacement module is available and that the part number and revision level are correct.
! !
Ciena Standard Cleaning & Equipment Safety Practices Node Manager User Guide

4 - 41
4
! ! !
CoreDirector Switch
TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface TOP 278D Handling Circuit Packs Properly
PROCEDURE
Warning:


Caution: This procedure affects traffic if performed on an OM that is carrying traffic. Performance of the following step may cause a traffic disruption. This instruction is intended as a general guide only, has not been tested for all possible applications or configurations, and may not be complete or accurate for some situations. Modules can be hot-swapped; CoreDirector power does not need to be removed. Lock modules prior to removal and unlock modules after installation. If required, refer to the Node Manager User Guide.
Note:
Summary The sequence of tasks for replacing an OM is as follows: 1. Remove traffic from the OM and lock the OM or port. (Refer to Preparing an Optical Module for Removal on page 4-43.) 2. Label all cables connected to the front of the OM. 3. Remove the installed OM.
! !
For an OM in an LM-2 Line Module, refer to Removing an LM-2 OM on page 4-44. For an OM in an LM-8 Line Module, refer to Removing an LM-8 OM on page 4-45. 4. If the replacement OM connectors are different from those on the removed OM, remove the cables from the front of the switch back to the IMP or fiber management panel. Remove the covers from the fiber management equipment. 5. Install an OM blank or an OM in the empty slot. If the replacement OM connectors are different from those on the removed OM, use fiber adapters and 1-meter (3.28-foot) SC-to-LC pigtail fiber cables to connect the OM to the site fiber cables. (Refer to Installing Replacement OMs with Dissimilar Connector Types on page 4-46.) Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 42
4
CoreDirector Switch
!
If the replacement OM connectors are the same as those on the removed OM, follow the instructions in one of the following sections: For an OM in an LM-2 Line Module, refer to Installing an LM-2 OM on page 4-47. For an OM in an LM-8 Line Module, refer to Installing an LM-8 OM on page 4-49.
Preparing an Optical Module for Removal Note: Loss of Signal (LOS) or Replaceable Unit alarms are reported if this procedure is performed on unlocked modules.
STEP 1: Establish a Node Manager session with the CoreDirector Switch. STEP 2: If the OM is not carrying traffic, proceed with Step 6. If the traffic-carrying OM is on the Line side, proceed to Step 3. If the traffic-carrying OM is on Drop side Working, proceed to Step 4. If the traffic-carrying OM is on Drop side Protection, proceed to Step 5. STEP 3: If the traffic-carrying OM is on the Line side: a. Collect all associated OSRP data on the neighboring nodes of the traffic-carrying OM. b. Establish an additional Node Manager session with the neighboring node and access the associated OM. c. Lock the OM on the traffic-carrying OM of the local node to trigger protection. Refer to Step 6 below if required. d. Immediately lock the associated OM in the neighbor node to complete the protection trigger. Refer to Step 6 below if required. e. Proceed with the instructions provided in Removing an LM-2 OM on page 4-44 to remove an LM-2 OM or Removing an LM-8 OM on page 4-45 to remove an LM-8 OM. Note: After the OM is replaced, unlock the OM on the local node and neighboring node and revert traffic as necessary.
STEP 4: If the traffic-carrying OM is on the Drop side Working: a. At the Drop side equipment, perform a manual protection switch to move traffic off the trafficcarrying OM. b. From the Node Manager menu bar, click Go > Protection. c. In the list frame, click the APS Groups tab, then select each OM pair and check the protection status to determine if Service is on the working side. No request indicates that Service is on the working side. d. Click Administer. e. Perform a manual switch to move traffic off the traffic-carrying OM. f. Lock the OM. Refer to Step 6 if required. g. Proceed with the instructions provided in Removing an LM-2 OM on page 4-44 to remove an LM-2 OM or Removing an LM-8 OM on page 4-45 to remove an LM-8 OM. Note: After the OM is replaced, release the manual protection switch at the Drop side equipment to restore service.
STEP 5: If the traffic-carrying OM is on Drop side Protection, ensure that the drop side protection LM is not protecting the working side. Proceed to Step 6. STEP 6: Lock the OM as follows: a. From the menu bar, select Go > Inventory. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 43
4
b. c. d. e.
CoreDirector Switch
From the equipment tree, expand the CoreDirector node view and select desired OM. From the Details frame, select the Basic tab. In the details frame, select Locked from the Admin State drop-down menu. To disable equipment alarms, select No Alarm Reporting from the ARC State drop-down menu. f. Click Accept. g. If required, click Yes to confirm the action. h. Proceed with the instructions provided in Removing an LM-2 OM on page 4-44 to remove an LM-2 OM or Removing an LM-8 OM on page 4-45 to remove an LM-8 OM.
Removing an LM-2 OM STEP 1: Identify each fiber. Tag the fibers with the appropriate OM slot or port and identify Tx and Rx. Tag the OM with the appropriate OM slot. Before disconnecting any fiber cables, observe the fiber cable routing and connections. Ensure that proper routing and connections are maintained when the OM is reinstalled or a new OM is installed. On an LM-2 LM, the fiber connectors are at an angle that causes a cable from one OM to pass across the front of the other installed OM. Before removing an OM, the fiber in front of the module must be safely moved to one side.
Note:
STEP 2: Disconnect the fibers from the OM to be removed and move the disconnected fibers out of the way. If the connector type on the replacement OM is different from the connector type on the original OM, it may be necessary to remove the fiber cables back to the Interbay Management Panel (IMP) or fiber raceway on a CoreDirector Switch or to the fiber management panel on a CoreDirector CI NA or ETSI rack installation.
Note:
STEP 3: Move other fiber cables out of the way as follows: a. At the curved fiber support above or below the LM where the OM is installed, identify the fiber coming from the OM that is not being removed. b. Increase the slack in the identified fiber by slipping the fiber over the lip and off its fiber support; move the fiber to the next support position. c. Move the fiber to the side, and attach it to the neighboring fiber using a loop of Velcro (Figure 4-11). Ensure that the moved fiber is not in the path of the OM to be removed.
Figure 4-11. Fiber Moved Out of the Path of an OM to Be Removed
4 - 44
4
STEP 4: Loosen the two screws on the OM faceplate and use the handle on the OM to slowly and carefully slide the OM all the way out of the LM using the OM guide rails. Do not twist or otherwise stress the module. Take care to use equal pressure and remove the module using the guide rails in a level straight-backward motion. STEP 5: Place dust covers on the fiber connectors, and place the OM in an ESD-guard antistatic bag. If the OM is not immediately replaced with a spare, use the Node Manager session to administratively remove the module from inventory (Step 6). Close the open slot by installing an Optical Module filler panel model OM-BLANK-2 or OM-BLANK-2-A. Install protective caps over the connectors of the disconnected fibers and end this procedure. No further action is required.
Note:
If the OM to be installed is the same as the model that was removed, proceed to Step 7. If the OM to be installed is a different type from the one that was removed, perform Step 6. STEP 6: When an OM is replaced by one of a different type or is not replaced with a spare, the physically removed OM must also be administratively removed from the system using Node Manager. To remove the OM using Node Manager, perform the following steps: Note: If applicable, remove the OM from any protection group or Test Access Port (TAP) associations before deleting the OM.
a. From the Node Manager menu bar, select Go > Inventory. b. From the equipment tree, click the icon of the removed OM. c. In the details frame, click Delete. Observe that the OM is removed from the equipment tree. STEP 7: Perform the required Return Materials Authorization (RMA) procedure for the replaced OM in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. Removing an LM-8 OM Note: Before disconnecting any fiber cables, observe the fiber cable routing and connections. Ensure that proper routing and connections are maintained when the OM is reinstalled or a new OM is installed.
STEP 1: Establish slack in the fiber cable to allow the OM to be moved as follows: a. At the curved fiber support above or below the LM where the OM is installed, identify the fiber coming from the OM to be removed. b. Slip the identified fiber off the fiber support to provide slack for moving the OM. STEP 2: Identify each fiber. Tag the fibers with the appropriate OM slot or port and identify Tx and Rx. Tag the OM with the appropriate OM slot. STEP 3: Remove the OM as follows: a. Loosen the two screws on the OM faceplate and use the handle on the OM to slowly and carefully slide the OM out of the LM using the OM guide rails until the fiber connections on the OM are fully exposed. Do not twist or otherwise stress the module. Take care to use equal pressure and remove the module using the guide rails in a level straight-back motion. b. Disconnect the fiber cables from the OM connectors. If the connector type on the replacement OM is different from the connector type on the original OM, it may be necessary to remove the fiber cables back to the IMP or fiber raceway on a CoreDirector Switch or to the fiber management panel on a CoreDirector CI NA or ETSI rack installation.
Note:

4 - 45
4
c. Carefully slide the OM the rest of the way out of the LM using the OM guide rails. Do not twist or otherwise stress the module. Take care to use equal pressure and remove the module using the guide rails in a level straight-back motion. STEP 4: Place dust covers on the fiber connectors, and place the OM in an ESD-guard antistatic bag. If the OM is not immediately replaced with a spare, use the Node Manager session to administratively remove the module from inventory (Step 5). Close the open slot by installing an Optical Module filler panel model OM-BLANK-8 or OM-BLANK-8-A. Install protective caps over the connectors of the disconnected fibers and end this procedure. No further action is required.
Note:
If the OM to be installed is the same as the model that was removed, proceed to Step 6. If the OM to be installed is a different type from the one that was removed, perform Step 5. STEP 5: When an OM is replaced by one of a different type or is not replaced with a spare, the physically removed OM must also be administratively removed from the system using Node Manager. To remove the OM using Node Manager, perform the following steps: Note: If applicable, remove the OM from any protection group or Test Access Port (TAP) association before deleting the OM.
a. From the Node Manager menu bar, select Go > Inventory. b. From the equipment tree, click the icon of the removed OM. c. In the details frame, click Delete. Observe that the OM is removed from the equipment tree. STEP 6: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. Installing Replacement OMs with Dissimilar Connector Types Because CoreDirector OMs are available with both LC and SC connectors, it is possible that a replacement OM will have a connector type that is different from the connectors on both the original OM and the installed site fiber cables. In this situation, fiber pigtail cables and adapters are required to connect the replacement OM. Table 4-5 lists the specific cable and adapter needed for each replacement situation. Table 4-5. Pigtail Cables and Adapter for OM Installation Connector Type Replacement OM Female SC Female LC Pigtail Site Fiber Male LC Male SC Male-to-male SC-to-LC Male-to-male SC-to-LC Female LC/LC Female SC/SC Adapter
The connection sequence is as follows: 1. Connect the matching end of a fiber pigtail to the connector on the OM (Figure 4-12 or Figure 4-13). 2. Route the fiber pigtail to the fiber management panel, IMP, or fiber raceway on the equipment rack. 3. Use an adapter to connect the fiber pigtail to the installed site fiber cable.
4 - 46
4
4. Route the slack as appropriate through the IMP or fiber management panel. Ensure that inside the IMP or fiber management panel, the adapter does not rest on top of a fiber spool. Note: Figure 4-12 and Figure 4-13 show 2.5G OMs; the same connection procedure also applies to 10G OMs.
LC-to-LC Adapter Site Fiber with LC Connectors
SC Connectors on the OM
SC-to-LC Fiber Pigtail Figure 4-12. Connecting an SC OM to an LC Site Fiber
SC-to-SC Adapter Site Fiber with SC Connectors
LC Connectors on the OM
LC-to-SC Fiber Pigtail Figure 4-13. Connecting an LC OM to an SC Site Fiber
Installing an LM-2 OM
Risk of Damage to Modules

Ensure that the power levels do not exceed specifications when changing among very short reach, short reach, medium reach, and long reach OMs. Refer to Table 4-6 for the maximum input power levels for each OM type. Take extra care when connecting the fiber cables to an OM and when sliding the module into the LM slot not to twist or otherwise stress the module. Improper handing can damage the modules. When replacing a module, ensure that the replacement module part number and revision level are correct. If the OM is the same OM removed in Step 4 on page 4-45, ensure that the OM is installed in the slot identified and tagged in Step 1 on page 4-44. Ensure that proper routing and connections are maintained when the OM is reinstalled or a new OM is installed.
Caution:
Note:

4 - 47
4
Table 4-6. 10G Optical Module Input Power Levels Optical Module 10G SR OM (SR-1) 10G SR OM (SR-2) 10G MR OM (MR-2) 10G LR OM (LR-2) 10G WDM-1 OM 10G WDM-2 OM Maximum Input Power -11 dBm to -1 dBm -14 dBm to -1 dBm -27 dBm to -1 dBm -24 dBm to -7 dBm -14.3 dBm to -1.3 dBm -14 dBm to -2 dBm
STEP 1: Verify that no fibers from the other OM in the same LM are in the path of the OM to be installed. If a fiber from the other OM is in the path of the OM to be installed, secure the fiber as described in Step 3 on page 4-44. STEP 2: Remove the OM from its ESD-guard antistatic bag. STEP 3: Install the OM in the LM as follows: a. Use the handle on the OM to slowly and carefully slide the OM all the way into the LM using the OM guide rails. Do not twist or otherwise stress the module. Take care to use equal pressure and insert the module using the guide rails in a level straight-ahead motion. b. Tighten the screws on the OM faceplate. c. Remove the Velcro loop from the fiber that was positioned out of the way. d. Move fiber into position in one of the following ways: If the OM being installed has the same connector type as the one that was removed, move the slack fiber back to the proper curved fiber support above or below the LM, and slip the cable over the lip and onto the support. If the OM being installed has different connectors from the one that was removed, follow the instructions in Installing Replacement OMs with Dissimilar Connector Types on page 4-46. e. Remove the dust caps and clean all optical connections in accordance with Ciena Standard Cleaning and Equipment Safety Practices. f. Connect the previously identified and tagged fiber cables to the OM connectors or fiber pigtail connectors. STEP 4: Using the Node Manager session, unlock the OM as follows: From the menu bar, select Go > Inventory. In the equipment tree, expand the CoreDirector node view and select the desired OM. Select the Basic tab of the Inventory screen. In the ARC State field of the Details frame, select Alarm Reporting from the ARC State dropdown menu. e. From the equipment tree, expand the CoreDirector node view and select the desired OM. f. In the Admin State field of the Details frame, select Unlocked from the Administrative State drop-down menu and click Accept. STEP 5: Verify that Serial #, Card Type, CLEI, Asmb. Part #, Mfg. Date, Model ID, Ext. Model ID, and ECI fields contain the appropriate information. If the fields are empty or do not contain the appropriate information, proceed to Step 7. STEP 6: At the CoreDirector Switch, verify the following LED indications for the newly installed OMs: Green ACTIVE LED is lit. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
a. b. c. d.
4 - 48
4
CoreDirector Switch
MAINT LED is off. LINE LED is off. FAIL LED is off. STEP 7: If the fields are empty or do not contain the appropriate information or if the OM is not operational, refer to the Alarm and Trouble Clearing Procedure Manual and/or contact the next level of support. Verify that the Node Manager application does not display a UEQ alarm for the OM. If a UEQ alarm is displayed, clear the alarm by administratively locking and unlocking the OM.
Note:
STEP 8: If the OM was not carrying traffic, proceed with Step 9. If the replaced OM was the Line side OM, unlock all OMs on the local node and neighboring nodes and revert traffic as necessary. If the replaced OM was Drop side Working, release the manual protection switch at the drop side equipment to restore service. If the replaced OM was Drop side Protection, ensure that the OM on the local node is unlocked. STEP 9: If applicable, use Node Manager Go > Monitoring > Statistics > Real Time Stats and select the TTP Real Time Stats tab to monitor optical ports in accordance with local practices. STEP 10: If applicable, repeat Step 1 through Step 9 for the other OM to be installed in the LM-2 line module. --STOP-THIS CONCLUDES THE PROCEDURE Installing an LM-8 OM

Ensure that power levels do not exceed specifications when changing among short reach, medium reach, and long reach OMs. Refer to Table 4-7 for the maximum input power levels for each OM type. Take extra care when connecting the fiber cables to an OM and when sliding the module into the LM slot not to twist or otherwise stress the module. Improper handing can damage the modules.
Caution:
Note:
When replacing a module, ensure that the replacement module part number and revision level are correct. If the OM is the OM removed in Step 3 on page 4-45, ensure that the OM is installed in the slot identified and tagged in Step 2 on page 4-45. Ensure that proper routing and connections are maintained when the OM is reinstalled or a new OM is installed.
Table 4-7. Optical Receiver Power Ranges for OMs and Optical Ports Port Type 155/622 MR OM 2.5G SR OM 2.5G MR OM Receiver Power Range -28 dBm to -8 dBm -18 dBm to -3 dBm -18 dBm to 0 dBm

4 - 49
4
Table 4-7. Optical Receiver Power Ranges for OMs and Optical Ports (Continued) Port Type 2.5G LR OM (LR-1) 2.5G LR OM (LR-2) Receiver Power Range -27 dBm to -9 dBm -28 dBm to -9 dBm
STEP 1: If the OM being installed has different connectors from the one that was removed, follow the instructions in Installing Replacement OMs with Dissimilar Connector Types on page 4-46 to prepare and route fibers for connection to the replacement OM. STEP 2: Remove the OM from its ESD guard antistatic bag. STEP 3: Install the OM in the LM as follows: a. Remove the dust caps and clean all optical connections in accordance with Ciena Standard Cleaning and Equipment Safety Practices. b. Connect the previously identified and tagged fiber cables to the OM connectors or fiber pigtail connectors. c. Use the handle on the OM to slowly and carefully slide the OM all the way into the LM using the OM guide rails. Do not twist or otherwise stress the module. Take care to use equal pressure and insert the module using the guide rails in a level straight-ahead motion. d. Tighten the screws on the OM faceplate. STEP 4: Using the Node Manager session, unlock the module as follows: From the menu bar, select Go > Inventory. In the equipment tree, expand the CoreDirector node view and select the desired OM. Select the Basic tab of the Inventory screen. In the ARC State field of the Details frame, select Alarm Reporting from the ARC State dropdown menu. e. In the Admin State field of the Details frame, select Unlocked from the Administrative State drop-down menu and click Accept. Note: If the OM installed is a different type from the one that was removed physically and administratively from the system (Step 5), ensure that the Interface Type and Configure Rate are set correctly. a. b. c. d.
STEP 5: Verify that Serial #, Card Type, CLEI, Asmb. Part #, Mfg. Date, Model ID, Ext. Model ID, and ECI fields contain the appropriate information. If the fields are empty or do not contain the appropriate information, proceed to Step 7. STEP 6: At the CoreDirector Switch, verify the following LED indications for the newly installed OMs: Green ACTIVE LED is lit. MAINT LED is off. LINE LED is off. FAIL LED is off. STEP 7: If the fields are empty or do not contain the appropriate information or if the OM is not operational, refer to the Alarm and Trouble Clearing Procedure Manual and/or contact the next level of support.
4 - 50
4
Note: Verify that the Node Manager application does not display a UEQ alarm for the OM. If a UEQ alarm is displayed, clear the alarm by administratively locking and unlocking the OM.
STEP 8: Replace the fiber of the OM onto the curved fiber support above or below the LM into which the OM is installed. STEP 9: If the OM was not carrying traffic, proceed with Step 10. If the replaced OM was the Line side OM, unlock all OMs on the local node and neighboring nodes and revert traffic as necessary. If the replaced OM was Drop side Working, release the manual protection switch at the Drop side equipment to restore service. If the replaced OM was Drop side Protection, ensure that the OM on the local node is unlocked. STEP 10: If applicable, use Node Manager Go > Monitoring > Statistics > Real Time Stats and select the TTP Real Time Stats tab to monitor optical ports in accordance with local practices. STEP 11: Repeat Step 2 through Step 10 for each OM to be installed in the LM-8 Line Module. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 51
4
4 - 52
4
TOP 173D REMOVING AND INSTALLING A LINE MODULE

OVERVIEW
This Task-Oriented Practice describes how to remove and install a CoreDirector Switch or CoreDirector CI Switch Line Module (LM). This procedure can be used on LMs that are carrying traffic.
REQUIRED TOOLS
! ! ! ! ! !
PREREQUISITES
!
The user must use proper module handling procedures. When handling, installing, or removing modules, the following precautions must be observed. Refer to TOP 278D Handling Circuit Packs Properly. Store modules in ESD protective packaging when they are not installed in an equipment shelf. Do not stack modules on or against each other. Pick up modules by the front faceplate, and do not touch components on the circuit board.
! !
! ! ! ! ! !
Ciena Standard Cleaning & Equipment Safety Practices Node Manager User Guide TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 172D Removing and Installing an Optical Module TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface TOP 278D Handling Circuit Packs Properly

4 - 53
4
CoreDirector Switch
Warning:


This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. All modules must be fully seated and latched into the chassis. If modules need to be removed and cannot be replaced with another module, replace with appropriate blank module. Any module left incompletely seated (or partially removed) may cause the system to become susceptible to Electrostatic Discharge (ESD) effects.
Caution:

This procedure affects traffic if performed on an LM that is carrying traffic. Move all traffic off of the LM prior to removal. This procedure could affect traffic if an LM is removed improperly. Ensure that Step 6 is performed to prepare the LM for removal prior to removing the LM. Performance of the following step may cause a traffic disruption. This instruction is intended as a general guide only, has not been tested for all possible applications or configurations, and may not be complete or accurate for some situations. Modules can be hot-swapped; CoreDirector power does not need to be removed. Lock modules prior to removal and unlock modules after installation. If required, refer to the Node Manager User Guide. If a CM switchover occurs during an LM replacement procedure while the LM is in HIR, the CoreDirector Switch does not recognize that the LM was replaced and leaves the LM in HIR. If a CM switchover occurs during LM replacement, reseat the LM.
Caution:
Note:
Summary This TOP includes the following tasks:

! ! ! ! !
Preparing a Line Module for Removal (below) Removing an LM-8 or LM-2 Line Module (page 4-56) Removing an LM-16 or Unprotected LM-16E (LM-16-STM-1E-A-U) Line Module (page 4-57) Removing a Protected LM-16E (LM-16-STM-1E-A) Line Module (page 4-59) Installing an LM-8 or LM-2 Line Module (page 4-61) Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 54
4
CoreDirector Switch
! !
Installing an LM-16 or Unprotected LM-16E (LM-16-STM-1E-A-U) Line Module (page 4-64) Installing a Protected LM-16E (LM-16-STM-1E-A) Line Module (page 4-66)
Preparing a Line Module for Removal STEP 1: Establish a Node Manager session with the CoreDirector Switch. STEP 2: If the LM is not carrying traffic, proceed with Step 6. If the traffic-carrying LM is on the Line side, proceed with Step 3. If the traffic-carrying LM is on the Drop side Working, proceed with Step 4. If the traffic-carrying LM is on the Drop side Protection, proceed with Step 5. STEP 3: If the traffic-carrying LM is on the Line Side: a. Collect all associated OSRP data on the neighboring nodes of the traffic-carrying LM. b. Establish an additional Node Manager session with the neighboring node and access the associated OM. c. Lock the OM PTP on the local node traffic-carrying LM to trigger protection. d. Immediately lock the associated OM PTP in the neighbor node to complete the protection trigger. e. Lock the remaining local-node OM PTPs one at a time and the associated OM PTPs on neighboring nodes. Note: f. After the LM is replaced, unlock all OMs on the local node and neighboring nodes and revert traffic as necessary.
Proceed with Step 6.
STEP 4: If the traffic-carrying LM is on the Drop Side Working, at the drop side equipment, perform a manual protection switch to move traffic off all the OMs connected to the traffic-carrying LM. a. Log on to the local node Node Manager and click Go > Protection. b. In the list frame, click the APS Groups tab. Then select each OM pair and check the protection status to determine if Service is on the working side. No request indicates that Service is on the working side. c. Click Administer. d. Perform a manual switch to move all traffic off the traffic-carrying LM. e. Lock all OMs on the traffic-carrying LM. Note: f. After the LM is replaced, release the manual protection switch at the Drop side equipment.
Proceed with Step 6.
STEP 5: If the traffic-carrying LM is on the Drop Side Protection: a. In Node Manager, click Go > Protection > Line Level > APS/MSP. Select the Traffic Flow tab and verify that the Drop side protection LM is not protecting the working side. b. Lock all OMs on the traffic-carrying LM. Note: After the LM is replaced, unlock all OMs on the local node.
c. Proceed with Step 6. STEP 6: To prevent Data Plane Health Failure alarms, disable module equipment alarm reporting as follows:

4 - 55
4
Note: a. b. c. d.
CoreDirector Switch
Data Plane Health Failure alarms are reported if modules are not locked before removing them.
From the menu bar, select Go > Inventory. In the equipment tree, expand the CoreDirector node view and select the desired module. In the details frame, select No Alarm Reporting from the ARC State drop-down menu. Select Prepare to Unseat Card and click Accept.
STEP 7: Identify and tag fiber cables and/or OMs associated with the LM to be removed. Continue with Removing an LM-8 or LM-2 Line Module on page 4-56 or Removing an LM-16 or Unprotected LM-16E (LM-16-STM-1E-A-U) Line Module on page 4-57. Removing an LM-8 or LM-2 Line Module


This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. All modules must be fully seated and latched into the chassis. If modules need to be removed and cannot be replaced with another module, replace with appropriate blank module. Any module left incompletely seated (or partially removed) may cause the system to become susceptible to Electrostatic Discharge (ESD) effects. Before disconnecting any fiber cables, observe fiber cable routing, connections, and OM placement. Ensure that proper routing, connections, and placement are maintained when the LM and associated OMs are re-installed. All CoreDirector modules are designed such that when inserted, the air gaps between the faceplates are minimal. This provides a continuous low impedance ground path for Electromagnetic Interference and Susceptibility compliance, ESD compliance, and a path to chassis ground for safety. However, the tight tolerance could cause the module face plate to be bound in the slot and difficult to remove. If required, loosen the faceplate screws of the adjacent modules on either side as needed and then remove the module.
Caution:
Note:
STEP 1: Disconnect fiber cables and remove OMs as follows: a. At the front of the CoreDirector Switch, remove the optical fibers from the curved fiber supports above and below the LM that will be removed. b. Refer to TOP 172D Removing and Installing an Optical Module, and remove the OMs. Note: Depending upon local practices, fibers may not need to be removed from the OMs if the same OMs are reinstalled in the replacement LM.
c. Install dust caps on the OM fiber connectors if applicable. d. Place the removed OMs in appropriate ESD-guard antistatic bags.
4 - 56
4
STEP 2: Remove and retain any OM blanks from the LM being removed. These OM blanks will be used when reinstalling a replacement LM. STEP 3: Remove the LM as follows: a. Loosen the two screws holding the LM in place. b. Simultaneously apply equal pressure to move both the ejectors into the open position (that is, perpendicular to the module faceplate). c. Slide the module out of the CoreDirector chassis. Take care to use equal pressure and remove the module using the guide rails in a level straight-backward motion. STEP 4: Place the module in an ESD guard antistatic bag. STEP 5: Check the slot backplane connector and verify that no bent pins are present. If the CoreDirector Switch is suspected of having damage, stop this procedure and contact Ciena Technical Support for assistance. If the LM to be installed is the same as the model removed, proceed to Step 8. If the LM to be installed is a different type from the LM removed, proceed to Step 6. Note: If the LM is not immediately replaced with a spare, use the Node Manager session to administratively remove the module from inventory (Step 6), then proceed to Step 7.
STEP 6: When an LM is replaced by one of a different type or is not replaced with a spare, the physically removed LM must also be administratively removed from the system inventory using Node Manager. To remove the LM using Node Manager, perform the following steps: Note: If applicable, remove the LM from any protection group and ensure that the LM is not carrying any traffic before deleting the LM.
a. From the Node Manager Menu Bar, select Go > Inventory. b. From the Equipment tree, click the icon of the removed LM. c. In the details frame, click Delete. Observe that the LM is removed from the equipment tree. STEP 7: If a replacement LM will not immediately be installed, close the open slot by installing module filler panel model LM-BLANK, LM-SC-BLANK, or LM-LC-BLANK and end this procedure (no further action is required). If the correct blank is not available, contact Ciena Technical Support. STEP 8: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. --STOP-THIS CONCLUDES THE PROCEDURE Removing an LM-16 or Unprotected LM-16E (LM-16-STM-1E-A-U) Line Module


4 - 57
4
This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. All modules must be fully seated and latched into the chassis. If modules need to be removed and cannot be replaced with another module, replace with appropriate blank module. Any module left incompletely seated (or partially removed) may cause the system to become susceptible to Electrostatic Discharge (ESD) effects. Before disconnecting any fiber cables, observe fiber cable routing, connections, and OM placement. Ensure that proper routing, connections, and placement are maintained when the LM and associated OMs are re-installed. All CoreDirector modules are designed such that when inserted, the air gaps between the faceplates are minimal. This provides a continuous low impedance ground path for Electromagnetic Interference and Susceptibility compliance, ESD compliance, and a path to chassis ground for safety. However, the tight tolerance could cause the module face plate to be bound in the slot and difficult to remove. If required, loosen the faceplate screws of the adjacent modules on either side as needed and then remove the module.
Caution:
Note:
STEP 1: Disconnect the fiber cables as follows: a. At the front of the CoreDirector Switch, remove the optical fibers from the curved fiber supports above and below the LM that will be removed. b. Disconnect the fiber cables from the optical port connectors and install dust caps on the cable connectors if available. c. Install dust caps on the optical port connectors in the LM if available. The dust caps from the replacement LM can be used after the replacement LM is installed. STEP 2: Remove the LM as follows: a. Loosen the two screws holding the LM in place. b. Simultaneously apply equal pressure to move both ejectors into the open position (that is, perpendicular to the module faceplate). c. Slide the module out of the CoreDirector chassis. Take care to use equal pressure and remove the module using the guide rails in a level straight-backward motion. STEP 3: Place the module in an ESD-guard antistatic bag. STEP 4: Check the slot backplane connector and verify that no bent pins are present. If the CoreDirector Switch is suspected of having damage, stop this procedure and contact Ciena Technical Support for assistance. If the LM to be installed is the same model that was removed, proceed to Step 7 below. If the LM to be installed is a different model from the LM removed, proceed to Step 5. Note: If the LM is not immediately replaced with a spare, use the Node Manager session to administratively remove the module from inventory (Step 5). Then proceed to Step 6 below.
STEP 5: When an LM is replaced by one of a different type or is not replaced with a spare, the physically removed LM must also be administratively removed from the system inventory. To remove the LM using Node Manager, perform the following steps:
4 - 58
4
CoreDirector Switch
Note:
If applicable, remove the LM from any protection group and ensure that the LM is not carrying any traffic before deleting the LM.
a. From the Node Manager Menu Bar, select Go > Inventory. b. From the Equipment tree, click the icon of the removed LM. c. In the details frame, click Delete. Observe that the LM is removed from the equipment tree. STEP 6: If a replacement LM will not immediately be installed, close the open slot by installing module filler panel model LM-BLANK, LM-SC-BLANK, or LM-LC-BLANK and end this procedure (no further action is required). If the correct blank is not available, contact Ciena Technical Support. STEP 7: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. --STOP-THIS CONCLUDES THE PROCEDURE Removing a Protected LM-16E (LM-16-STM-1E-A) Line Module


This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. All modules must be fully seated and latched into the chassis. If modules need to be removed and cannot be replaced with another module, replace with appropriate blank module. Any module left incompletely seated (or partially removed) may cause the system to become susceptible to Electrostatic Discharge (ESD) effects. When replacing a module, ensure that the replacement module part number and revision level are correct. All CoreDirector modules are designed such that when inserted, the air gaps between the faceplates are minimal. This provides a continuous low impedance ground path for Electromagnetic Interference and Susceptibility compliance, ESD compliance, and a path to chassis ground for safety. However, there could be insufficient space for the circuit pack face plate to fit securely against the chassis. If required, loosen the faceplate screws of the adjacent modules on either side as needed and then install the module.
Caution:
Note:
STEP 1: Remove protected equipment configuration cover as follows: a. At the LM to be removed, loosen three captives screws securing protected equipment configuration cover b. Remove cover. STEP 2: Remove the Bridge Modules from LM and I/O-16-E as follows: a. Starting at the top of the LM-16-STM-1E-A to be removed, pull bridge module from LM and I/ O-16-E while exercising care not to bend the four-pin connector pins. b. Repeat Step 2 a. for remaining seven Bridge Modules. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 59
4
c. Remove cover. STEP 3: Remove the three alignment plates from LM and I/O-16-E as follows: a. Loosen the two screws securing each alignment plate to the LM and I/O-16-E then lift the alignment plate off of the LM and I/O-16-E. b. Repeat for remaining two alignment plates. STEP 4: Remove the LM as follows: a. Loosen the two screws holding the LM in place. b. Simultaneously apply equal pressure to move both ejectors into the open position (that is, perpendicular to the module faceplate). c. Slide the module out of the CoreDirector chassis. Take care to use equal pressure and remove the module using the guide rails in a level straight-backward motion. STEP 5: Place the module in an ESD-guard antistatic bag. STEP 6: Check the slot backplane connector and verify that no bent pins are present. If the CoreDirector Switch is suspected of having damage, stop this procedure and contact Ciena Technical Support for assistance. If the LM to be installed is the same model that was removed, proceed to Step 8 below. If the LM to be installed is a different model from the LM removed, proceed to Step 7. Note: If the LM is not immediately replaced with a spare, use the Node Manager session to administratively remove the module from inventory (Step 7). Then proceed to Step 8 below.
CoreDirector Switch
STEP 7: When an LM is replaced by one of a different type or is not replaced with a spare, the physically removed LM must also be administratively removed from the system inventory. To remove the LM using Node Manager, perform the following steps: a. From the Node Manager Menu Bar, select Go > Inventory. b. From the Equipment tree, click the icon of the removed LM. c. In the details frame, click Delete. Observe that the LM is removed from the equipment tree. STEP 8: If a replacement LM will not immediately be installed, close the open slot by installing module filler panel model LM-BLANK, LM-SC-BLANK, or LM-LC-BLANK and end this procedure (no further action is required). If the correct blank is not available, contact Ciena Technical Support. STEP 9: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 60
4
CoreDirector Switch
Installing an LM-8 or LM-2 Line Module


This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. All modules must be fully seated and latched into the chassis. If modules need to be removed and cannot be replaced with another module, replace with appropriate blank module. Any module left incompletely seated (or partially removed) may cause the system to become susceptible to Electrostatic Discharge (ESD) effects. When replacing a module, ensure that the replacement module part number and revision level are correct. All CoreDirector modules are designed such that when inserted, the air gaps between the faceplates are minimal. This provides a continuous low impedance ground path for Electromagnetic Interference and Susceptibility compliance, ESD compliance, and a path to chassis ground for safety. However, there could be insufficient space for the module face plate to fit securely against the chassis. If required, loosen the faceplate screws of the adjacent modules on either side as needed and then install the module.
Caution:
Note:
STEP 1: Identify the line module shelf and slot where the LM will be installed. STEP 2: From the front of the CoreDirector Switch, check the LM slot backplane connector and verify that no bent pins are present. If the CoreDirector Switch is suspected of having damage, stop this procedure and contact Ciena Technical Support for assistance. STEP 3: Remove the replacement module from the ESD-guard antistatic bag by holding the front faceplate and carefully sliding the replacement module from the bag. To support the module, one hand can be placed under the pan (the side without board components). If the module was incorrectly inserted into the ESD bag with the faceplate facing the wrong direction, place one hand under the pan and carefully rotate the circuit pack so the module can be removed from the bag. If the bag is not large enough to rotate the module, place one hand under the pan and carefully remove the module from the bag until the face plate can be grasped. This should be done over a flat surface since there is a possibility of dropping the module. Never pull the module out of the bag by applying pressure to the pan and the component boards. Such handling can cause damage to certain boards that do not have added stiffeners to support such pressure (for example, the VI processor daughter board). To prevent damage to modules, always handle the modules by the faceplate side.
Note:

4 - 61
4
STEP 4: Inspect the module connector block for damage or misalignment. Do this by visually inspecting each of the connector blocks to verify that they are properly seated and flush on the Printed Circuit Board (PCB). As a second inspection method, look at the top of all the blocks; they should appear planar and horizontally aligned. Refer to TOP 278D Handling Circuit Packs Properly for additional information. If the connector block is suspected of having damage, place the module back in its ESD bag and return the damaged module as described in Step 8 on page 4-57. Repeat this task with another replacement module. STEP 5: Install the module as follows: a. Insert the module into the guide rails of the designated slot. Slowly slide the module into the slot by pushing on the module faceplate until the top and bottom ejectors engage the ejector bracket and begin to rotate as shown in Figure 4-14. Take care to insert the module using the guide rails in a level, straight-forward motion and visually inspect for proper LM faceplate fit while moving both ejectors into the closed position. If required, loosen the faceplate screws of the adjacent modules on either side as needed and then install the circuit pack. b. Simultaneously apply equal pressure to move both the ejectors into the closed position. Note: If multiple LMs are being installed, do not tighten the faceplate screws until after the last LM is installed and the slot alignment checked.
c. Ensure that the faceplate is flush against the chassis then tighten faceplate screws. STEP 6: Using the Node Manager session, enable module equipment alarm reporting as follows: a. b. c. d. From the menu bar, select Go > Inventory. In the equipment tree, expand the CoreDirector node view and select the desired module. In the details frame, select Alarm Reporting from the ARC State drop-down menu. Click Accept.
STEP 7: The self-test diagnostics and auto-configuration take approximately 5 minutes to complete. After this time has elapsed, verify the following conditions: In Node Manager, the Serial #, Card Type, CLEI, Asmb. Part #, Mfg. Date, Model ID, Ext. Model ID, and ECI fields contain the appropriate information. At the front of the CoreDirector Switch, the module LEDs on the newly installed LM display the following indications: Green ACTIVE LED is illuminated. MAINT LED is off. FAIL LED is off. STEP 8: If the fields are empty or do not contain the appropriate information or if the LM STAT LED or optical port AF (ACT/FAIL) LED continues to illuminate red: a. Test the backplane by installing a second module of the same type (if available) into the same slot. If its LM STAT LED turns off, return the original module to Ciena in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. b. Refer to the Alarm and Trouble Clearing Procedure Manual and/or contact the next level of support.
4 - 62
4
Figure 4-14. LM Insertion
STEP 9: Refer to TOP 172D Removing and Installing an Optical Module and reinstall the OMs identified and tagged when the original LM was removed. STEP 10: Replace the optical fibers on the curved fiber supports above or below the LM that was removed. STEP 11: If the LM was not carrying traffic, proceed with Step 13. If the replaced LM was a line side LM, unlock all OMs on the local node and neighboring nodes and revert traffic as necessary. If the replaced LM was Drop side Working, release the manual protection switch at the Drop side equipment. If the replaced LM was Drop side Protection, ensure that all OMs on the local node are unlocked. STEP 12: Install Optical Module filler panels (Part Number OM-BLANK or OM-BLANK-8A) in any open OM slots. STEP 13: Repeat this procedure for each additional LM-2 or LM-8 module to be installed. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 63
4
Installing an LM-16 or Unprotected LM-16E (LM-16-STM-1E-A-U) Line Module


Caution:
Note:
STEP 1: Identify the line module shelf and slot into which the LM will be installed. STEP 2: From the front of the CoreDirector Switch, check the LM slot backplane connector and verify that no bent pins are present. If the CoreDirector Switch is suspected of having damage, stop this procedure and contact Ciena Technical Support for assistance. STEP 3: Remove the replacement module from the ESD-guard antistatic bag by holding the front faceplate and carefully sliding the replacement module from the bag. To support the module, one hand can be placed under the pan (the side without board components). If the module was incorrectly inserted into the ESD bag with the faceplate facing the wrong direction, place one hand under the pan and carefully rotate the circuit pack so the module can be removed from the bag. If the bag is not large enough to rotate the module, place one hand under the pan and carefully remove the module from the bag until the face plate can be grasped. This should be done over a flat surface since there is a possibility of dropping the module. Never pull the module out of the bag by applying pressure to the pan and the component boards. Such handling can cause damage to certain boards that do not have added stiffeners to support such pressure (for example, the VI processor daughter board). To prevent damage to modules, always handle the modules by the faceplate side.
Note:
4 - 64
4
STEP 4: Inspect the module connector block for damage or misalignment. Do this by visually inspecting each of the connector blocks to verify that they are properly seated and flush on the Printed Circuit Board (PCB). As a second inspection method, look at the top of all the blocks; they should appear planar and horizontally aligned. Refer to TOP 278D Handling Circuit Packs Properly for additional information. If the connector block is suspected of having damage, place the module back in its ESD bag and return the damaged module as described in Step 7 on page 4-59. Repeat this step with another replacement module. STEP 5: Install the module as follows: a. Insert the module into the guide rails of the designated slot. Slowly slide the module into the slot by pushing on the module faceplate until the top and bottom ejectors engage the ejector bracket and begin to rotate as shown in Figure 4-14. Take care to insert the module using the guide rails in a level, straight-forward motion and visually inspect for proper LM faceplate fit while moving both ejectors into the closed position. If required, loosen the faceplate screws of the adjacent modules on either side as needed and then install the circuit pack. b. Simultaneously apply equal pressure to move both ejectors into the closed position. Note: If multiple LMs are being installed, do not tighten the faceplate screws until after the last LM is installed and the slot alignment checked.
c. Ensure that the faceplate is flush against the chassis then tighten faceplate screws. After the module has been inserted into the system backplane, a series of power-up diagnostic self-tests are executed. Following the successful conclusion of the self-tests, an LM-16 module is automatically configured by the CM. This configuration includes defaulting each port for OC-12 support.
Note:
STEP 6: The self-test diagnostics and auto-configuration take approximately five minutes to complete. After this time has elapsed, verify that the Serial #, Card Type, CLEI, Asmb. Part #, Mfg. Date, Model ID, Ext. Model ID, and ECI fields contain the appropriate information. If the fields are empty or do not contain the appropriate information, refer to the Alarm and Trouble Clearing Procedure Manual and/or contact the next level of support. STEP 7: Using the Node Manager session, enable module equipment alarm reporting as follows: a. b. c. d. From the menu bar, select Go > Inventory. In the equipment tree, expand the CoreDirector node view and select the desired module. In the details frame, select Alarm Reporting from the ARC State drop-down menu. Click Accept.
STEP 8: At the front of the CoreDirector Switch, observe the module and port LEDs on the newly installed LM. Verify that the LEDs show the following indications: LM STAT illuminates green. LM MAINT is off. AF (ACT/FAIL) LEDs for ports illuminate green. Other port LEDs may illuminate, depending on the operational status of the port. Refer to Table 4-8 for additional information about the port LEDs. STEP 9: If the fields are empty or do not contain the appropriate information or if the LM STAT LED or optical port AF (ACT/FAIL) continues to illuminate red: a. Test the backplane by installing a second module of the same type (if available) into the same slot. If its LM STAT LED turns off, return the original LM to Ciena in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 65
4
b. Refer to the Alarm and Trouble Clearing Procedure Manual and/or contact the next level of support. STEP 10: Remove the dust caps and clean all optical connections in accordance with Ciena Standard Cleaning and Equipment Safety Practices. STEP 11: Identify and reconnect the fiber cables disconnected from the removed LM. STEP 12: If applicable, use Node Manager Go > Monitoring > Statistics > Real Time Stats and select the TTP Real Time Stats tab to monitor optical ports in accordance with local practices. STEP 13: If the LM was not carrying traffic, proceed with Step 14. If the replaced LM was Drop side Working, release the manual protection switch at the Drop side equipment. If the replaced LM was Drop side Protection, ensure that all OMs on the local node are unlocked. STEP 14: Repeat this procedure for each additional LM-16 module that requires installation. Table 4-8. LM-16 Optical Port LED States M (MAINT) (Yellow) Off L (LINE) (Yellow) Off AF (ACT/FAIL) State (Red) On (Green) Off Optical port is held in RESET, or there is a hardware failure, or software is not yet running from local Flash memory. Run-time image diagnostics, configuration, and initialization. Optical port is in a maintenance state and is safe for removal (for example, Admin Locked). Alarms are not generated. Optical port is operational, but the port has no fiber connected or is not receiving proper framing. Loss of Signal (LOS) and Loss of Frame (LOF) alarms are generated. Optical port is in an unlocked, laser-on state (for example, Admin Unlocked), and the port has fiber connected and is receiving proper framing. Power is off.
Flashing On
On On
On Off
Off Off
Off
On
Off
On
Off
Off
Off
On
Off
Off
Off
Off
--STOP-THIS CONCLUDES THE PROCEDURE Installing a Protected LM-16E (LM-16-STM-1E-A) Line Module

4 - 66
4
Caution:
Note:
STEP 15: Identify the line module shelf and slots where the LM-16-STM-1E-A protected equipment configuration will be installed. STEP 16: At the front of the CoreDirector switch, remove the four sequential blank filler panels (if applicable) from identified slots. STEP 17: Inspect the backplane connector for each slot and verify that no connector pins are bent. If the CoreDirector Switch is suspected of having damage, contact Ciena Technical Support for assistance. IO-16-E Installation STEP 18: Remove the module from the ESD-guard antistatic bag by holding the front faceplate and carefully sliding the module from the bag. To support the module, one hand can be placed under the pan (the side without board components). If the module was incorrectly inserted into the ESD bag with the faceplate facing the wrong direction, place one hand under the pan and carefully rotate the circuit pack so the module can be removed from the bag. If the bag is not large enough to rotate the module, place one hand under the pan and carefully remove the module from the bag until the face plate can be grasped. This should be done over a flat surface since there is a possibility of dropping the module. Never pull the module out of the bag by applying pressure to the pan and the component boards. Such handling can cause damage to certain boards that do not have added stiffeners to support such pressure (for example, the VI processor daughter board). To prevent damage to modules, always handle the modules by the faceplate side.
Note:
STEP 19: Inspect the module connector block for damage or misalignment. Do this by visually inspecting each of the connector blocks to verify that they are properly seated and flush on the Printed Circuit Board (PCB). As a second inspection method, look at the top of all the blocks; they should appear planar and horizontally aligned. Refer to TOP 278D Handling Circuit Packs Properly for additional

4 - 67
4
information. If the connector block is suspected of having damage, place the module back in its ESD bag and return the damaged module as described in Step 7 on page 4-59. Repeat this step with another replacement module. STEP 20: Install the IO-16-E module as follows: a. Insert the module into the guide rails of the center two designated slots. Slowly slide the module into the slots by pushing on the module faceplate until the top and bottom ejectors engage the ejector bracket and begin to rotate as shown in Figure 4-14. Take care to insert the module using the guide rails in a level, straight-forward motion and visually inspect for proper faceplate fit while moving both upper and lower ejectors into the closed position. b. Simultaneously apply equal pressure to move both upper and lower ejectors into the closed position. c. Ensure that the faceplate is flush against the chassis.
Figure 4-15. Module Insertion LM-16-STM-1E-A Installation STEP 21: Remove the LM-16-STM-1E-A module from the ESD-guard antistatic bag by holding the front faceplate and carefully sliding the replacement module from the bag. To support the module, one hand can be placed under the pan (the side without board components).
4 - 68
4
If the module was incorrectly inserted into the ESD bag with the faceplate facing the wrong direction, place one hand under the pan and carefully rotate the circuit pack so the module can be removed from the bag. If the bag is not large enough to rotate the module, place one hand under the pan and carefully remove the module from the bag until the face plate can be grasped. This should be done over a flat surface since there is a possibility of dropping the module. Never pull the module out of the bag by applying pressure to the pan and the component boards. Such handling can cause damage to certain boards that do not have added stiffeners to support such pressure (for example, the VI processor daughter board). To prevent damage to modules, always handle the modules by the faceplate side.
Note:
STEP 22: Inspect the module connector block for damage or misalignment. Do this by visually inspecting each of the connector blocks to verify that they are properly seated and flush on the Printed Circuit Board (PCB). As a second inspection method, look at the top of all the blocks; they should appear planar and horizontally aligned. Refer to TOP 278D Handling Circuit Packs Properly for additional information. If the connector block is suspected of having damage, place the module back in its ESD bag and return the damaged module as described in Step 7 on page 4-59. Repeat this step with another replacement module. The shelves in the CoreDirector Switches and CoreDirector CI Switches contain fiber management guides that are color-coded black and gray to match the ejectors of the Line Modules and Control Modules. When modules are being installed, ensure they are oriented so the color of the module ejectors matches the adjacent fiber management guides.
Note:
STEP 23: Install the LM-16-STM-1E-A module as follows: a. Insert the module into the guide rails on the designated slot to the left or right of the IO-16-E. Slowly slide the module into the slots by pushing on the module faceplate until the top and bottom ejectors engage the ejector bracket and begin to rotate as shown in Figure 4-14. Take care to insert the module using the guide rails in a level, straight-forward motion and visually inspect for proper LM faceplate fit while moving both upper and lower ejectors into the closed position. b. Simultaneously apply equal pressure to move both upper and lower ejectors into the closed position. c. Ensure that the faceplate is flush against the chassis. Alignment Plate Installation Three alignment plates secure each LM-16-STM-1E-A to the IO-16-E. STEP 24: Starting at the top of the LM-16-STM-1E-A, place the alignment plate over the LM-16-STM-1E-A and align the alignment plate holes with the floating RF connectors on the LM-16-STM-1E-A and IO-16-E. STEP 25: Secure the alignment plate using 2 screws as shown in Figure 4-16. STEP 26: Repeat Step 24 and Step 25 for the remaining two alignment plates.

4 - 69
4
LM-16-E IO-16-E LM-16-E
Alignment Plates (6) Bridge Modules (16) Covers (2) (EMI Gaskets Not Shown) Figure 4-16. Alignment Plate Installation Bridge Module Installation The bridge module uses a four-pin connector in the upper left side of the module for power and ground that mates with a connector on the LM-16-STM-1E-A. The bridge module also has floating RF connectors that bridge signals between four LM-16-STM-1E-A connectors and four connectors on the IO-16-E.

Caution: Improper module installation could result in bent pins. Follow the insertion steps carefully. When installing the bridge modules, ensure that the four-pin connector pins are properly aligned with the LM-16-STM-1E-A connector prior to apply pressure to seat the module.
4 - 70
4
STEP 27: Starting at the top of the left-side LM-16-STM-1E-A, install the bridge modules as follows: a. Align the module power and ground pins with the four pin connector on the LM-16-STM-1E-A as shown in Figure 4-17. Ensure that the floating RF connectors are properly aligned with the LM-16-STM-1E-A and IO-16-E connectors.
4-Pin Power and Ground Connector
Floating RF Connectors
Figure 4-17. Bridge Module Insertion b. Slowly slide the bridge module pins into the connector by applying pressure on the sides of the bridge module. Take care to insert the module using a straight-forward motion while visually inspecting for proper pin alignment. c. Ensure that the module is flush against the LM-16-STM-1E-A and IO-16-E faceplates. STEP 28: Repeat Step 27 for the remaining seven bridge modules. STEP 29: At the top of the right-side LM-16-STM-1E-A, repeat Step 27 and Step 28. Protected Equipment Configuration Cover Installation STEP 30: Position the Protected equipment configuration cover over the Bridge Modules and floating RF connectors. STEP 31: Secure cover using supplied captive screws. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 71
4
4 - 72
4
TOP 174D REMOVING AND INSTALLING A TIMING MODULE

OVERVIEW
This Task-Oriented Practice describes how to remove and install a CoreDirector Switch or CoreDirector CI Switch Timing Module (TM). Normally, there are two TMs in a CoreDirector Switch system. In the CoreDirector Switch, one TM is in the extreme right module slot of Shelf B and the other is in the extreme left module slot of Shelf B. In the CoreDirector CI Switch, the TMs are on either side of the I/O module in the center of the single system shelf. The TM cannot be guaranteed to operate within its specified performance limits for the first 24 hours after power-on. During this period, the TM is still capable of performing its functions; however, network pointer adjustments may be detected.
Note:
REQUIRED TOOLS
! ! ! ! ! !
ESD-guard wrist strap ESD-guard heel grounders Common hand tools 10base-T, RJ-45 crossover cable CoreDirector Node Manager software Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP
PREREQUISITES
!
The user must use proper module handling procedures. When handling, installing, or removing modules, the following precautions must be observed. Refer to TOP 278D Handling Circuit Packs Properly on page 1-215. Ensure modules are stored in ESD-protective packaging when not installed in an equipment shelf. Do not stack modules on or against each other. Pick up modules by the front handle, and do not touch components on the circuit board.
! !
! ! ! ! !
Node Manager User Guide TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface TOP 278D Handling Circuit Packs Properly

4 - 73
4
CoreDirector Switch

Caution:
Modules can be hot-swapped; CoreDirector power does not need to be turned off for these procedures to be performed. Note: After a TM switchover, the TM takes about 2 minutes to assume the primary TM tasks, including APS. To prepare a TM for removal, Step 1 and Step 2 are performed. To remove a TM, Step 3 through Step 7 are performed. To install a TM, Step 8 through Step 17 are performed. Prepare TM for Removal STEP 1: Establish a Node Manager session with the CoreDirector Switch. STEP 2: Disable TM alarm reporting as follows: Note: Replaceable Unit alarms are reported if module alarm reporting is not disabled.
a. From the menu bar, select Go > Inventory. b. From the equipment tree, expand the CoreDirector node view and select the desired TM. c. In the Details frame, change the ARC State to No Alarm Reporting and click Accept. Remove TM STEP 3: At the front of the CoreDirector Switch, loosen the two screws holding the TM in place. STEP 4: Simultaneously apply equal pressure and move both the ejectors into the open position (perpendicular to the module faceplate). Take care to use equal pressure and remove the module using the guide rails in a level straight-backward motion.

Caution:
4 - 74
4
CoreDirector Switch
STEP 5: Place the TM in an ESD-guard antistatic bag. If the TM is not immediately replaced with a spare, use the Node Manager session to delete the module from inventory then proceed to Step 8 and close the open slot by installing a Timing Module filler panel model TM-BLANK. If the correct blank is not available, contact Ciena Technical Support.
Note:
STEP 6: Check slot backplane connector and verify no bent pins are present. If CoreDirector Switch is suspected of having damage, stop this procedure and contact Ciena Technical Support for assistance. STEP 7: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. --STOP-THIS CONCLUDES THE PROCEDURE Install TM Note: When replacing a module, ensure that the replacement module part number and revision level are correct.
STEP 8: At the front of the CoreDirector Switch, check LM slot backplane connector and verify no bent pins are present. If CoreDirector Switch is suspected of having damage, stop this procedure and contact Ciena Technical Support for assistance. STEP 9: At the front of the CoreDirector Switch, remove the module from its ESD-guard antistatic bag. STEP 10: Inspect the module connector block for damage or misalignment. Do this by visually inspecting each of the connector blocks to verify that they are properly seated and flush on the Printed Circuit Board (PCB). As a second inspection method, look at the top of all the blocks; they should appear planar and horizontally aligned. Refer to TOP 278D Handling Circuit Packs Properly for additional information. If connector block is suspected of having damage, repeat Step 5 through Step 7 with the damaged module and continue the procedure at Step 8 with another replacement module. STEP 11: Slowly slide the module into the designated slot by pushing on the module faceplate until the top and bottom ejectors engage the ejector bracket and begin to rotate as shown in Figure 4-18. Take care to insert the module using the guide rails in a level, straight-forward motion.

Caution:
STEP 12: Tighten the two retaining screws to secure the TM in place. STEP 13: If required, use Node Manager to enable alarm reporting as follows: a. From the Node Manager menu bar, select Go > Inventory. b. From the equipment tree, expand the CoreDirector node view and select the TM installed in Step 11. c. In the Details frame, change the ARC State to Alarm Reporting and click Accept.

4 - 75
4
Figure 4-18. TM Insertion STEP 14: Verify that Serial #, Card Type, CLEI, Asmb. Part #, Mfg. Date, Model ID, Ext. Model ID, and ECI fields contain the appropriate information. STEP 15: If the fields are empty or do not contain the appropriate information, proceed to Step 17. STEP 16: The TM becomes operational after completing its boot process. This could take up to fifteen minutes. Verify that the TM becomes operational by observing that the green ACTIVE LED is lit. STEP 17: Verify that there are no Replaceable Unit or timing related alarms. If the fields are empty or do not contain the appropriate information, or if related alarms exist, refer to the Alarm and Trouble Clearing Procedure Manual and/or contact the next level of support. The TM cannot be guaranteed to operate within its specified performance limits for the first 24 hours after power-on. During this period, the TM is still capable of performing its functions; however, network pointer adjustments may be detected. --STOP-THIS CONCLUDES THE PROCEDURE
Note:
4 - 76
4
TOP 175D REMOVING AND INSTALLING A PDU DISPLAY MODULE

OVERVIEW
This Task-Oriented Practice describes how to remove and install a CoreDirector Switch or CoreDirector CI Switch Power Distribution Unit (PDU) Display module from the front of the PDU.
REQUIRED TOOLS
! ! ! ! ! !
PREREQUISITES
!
! !
! ! ! !
TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 187D Test LEDs TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface TOP 278D Handling Circuit Packs Properly

4 - 77
4
CoreDirector Switch


PDU Display modules can be hot-swapped; CoreDirector power does not need to be turned off for these procedures to be performed. This is a single removal and installation procedure. Do not execute this procedure without a replacement PDU Display module available. Note: This procedure consists of two tasks:
! !
To remove the module, Step 1 through Step 7 are performed. To install the module, Step 8 through Step 15 are performed.
Prepare PDU Display Module for Removal STEP 1: Establish a Node Manager session with the CoreDirector Switch. Note: Replaceable Unit alarms are reported when this procedure is performed.
Remove PDU Display Module STEP 2: At the front of the CoreDirector Switch, remove the PDU cover: a. Pull outward on the lower corners of the cover to unsnap the stud fasteners. b. Lift the PDU cover off the top hinge screws. STEP 3: Loosen the two screws that hold the PDU Display module in place (Figure 4-19). STEP 4: Gently pull forward on the PDU Display module to disconnect the power connector. STEP 5: Rotate the PDU Display module up to allow access to the signal connector, and unplug the signal connector. STEP 6: Place the PDU Display module in an ESD-guard antistatic bag. STEP 7: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure.
4 - 78
4
Screws
PDU Display Module
Figure 4-19. Power Distribution Unit for CoreDirector Switch Install PDU Display Module Note: When replacing a module, ensure that the replacement module part number and revision level are correct.
STEP 8: At the front of the CoreDirector Switch, remove the module from its ESD-guard antistatic bag. STEP 9: Connect the PDU Display module signal connector to the mating connector on the PDU. STEP 10: Gently push the PDU Display module into the blind mate power connector inside the PDU. STEP 11: Tighten the two retaining screws to secure the PDU Display module in place in the PDU. STEP 12: Verify that the POWER indicator on the PDU Display module is lit. STEP 13: Refer to TOP 187D Test LEDs on page 1-99 to test the LED indicators. STEP 14: Using the Node Manager session, verify that there are no Replaceable Unit alarms. If related Replaceable Unit alarms exist, refer to the Alarm and Trouble Clearing Procedure Manual and/or contact the next level of support. STEP 15: At the front of the CoreDirector Switch, replace the PDU front cover on the top hinge screws, and apply pressure on the lower left and lower right corners to snap the cover into place. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 79
4
4 - 80
4
TOP 176D REMOVING AND INSTALLING A FAN POWER MODULE

OVERVIEW
This Task-Oriented Practice describes how to remove and install a CoreDirector Switch fan power module from the Power Distribution Unit (PDU). This TOP applies only to the CoreDirector Switch. Blower Module assemblies in the CoreDirector CI Switch have built-in fan power modules. Fan Power modules can be hot-swapped; CoreDirector power does not need to be turned off for these procedures to be performed.
Note:
REQUIRED TOOLS
! ! ! ! ! !
PREREQUISITES
!
! !
! ! ! !
Node Manager User Guide TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface TOP 278D Handling Circuit Packs Properly

4 - 81
4
CoreDirector Switch


Disable module alarm reporting prior to removal and enable alarm reporting after installation. If required, refer to The Node Manager User Guide. This is a single removal and installation procedure. Do not execute this procedure without a replacement fan power module available. Note: This procedure consists of two tasks:
!
To disable module equipment alarm reporting and remove the module, Step 1 through Step 6 are performed. To install and enable module equipment alarm reporting the module, Step 7 through Step 11 are performed.
Prepare Fan Power Module for Removal STEP 1: Establish a Node Manager session with the CoreDirector Switch. STEP 2: Disable Alarm reporting as follows: Note: a. b. c. d. Replaceable Unit alarms are reported if module alarm reporting is not disabled.
Remove Fan Power Module STEP 3: At the front of the CoreDirector Switch, remove the PDU cover: a. Pull outward on the lower corners of the cover to unsnap the stud fasteners. b. Lift the PDU cover off the top hinge screws. STEP 4: Loosen the two screws holding the fan power module in place in the PDU. STEP 5: Slide the fan power module out of the PDU. STEP 6: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure.
4 - 82
4
CoreDirector Switch
Install Fan Power Module STEP 7: Slide the fan power module into the PDU. STEP 8: Tighten the two screws holding the fan power module in place in the PDU. STEP 9: If required, use Node Manager to enable alarm reporting as follows: a. b. c. d. From the menu bar, select Go > Inventory. In the equipment tree, expand the CoreDirector node view and select the desired module. In the details frame, select Alarm Reporting from the ARC State drop-down menu. Click Accept.
STEP 10: Verify that there are fan power or cooling related alarms. If fan power or cooling related alarms exist, refer to the Alarm and Trouble Clearing Procedure Manual and/or contact the next level of support. STEP 11: At the front of the CoreDirector Switch, replace the PDU front cover on the top hinge screws, and apply pressure on the lower left and lower right corners to snap it into place. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 83
4
4 - 84
4
TOP 177D REMOVING AND INSTALLING A COREDIRECTOR CI I/O MODULE

OVERVIEW
This Task-Oriented Practice describes how to remove and install CoreDirector CI Switch Input/Output (I/O) module. The CoreDirector Switch I/O panel can be removed and replaced by Ciena personnel only. It is not recommended for customer removal and replacement. On a CoreDirector CI Switch, the I/O panel is on a module at the front of the chassis between the Timing Modules.

Warning Negative 48 volts DC is present beneath the backplane cover in the CoreDirector Switch. Contact Ciena Technical Support for CoreDirector I/O Panel replacement. The following procedure is only for the CoreDirector CI I/O Module replacement.
REQUIRED TOOLS
! ! ! ! ! !
PREREQUISITES
!
! !
! ! ! ! !
Node Manager User Guide TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface TOP 278D Handling Circuit Packs Properly

4 - 85
4
CoreDirector Switch

I/O panels can be hot-swapped; CoreDirector power does not need to be turned off for these procedures to be performed. To prepare any I/O Panel for removal, Step 1 through Step 2 are performed Note: To remove a CoreDirector CI Switch I/O panel, Step 3 through Step 7 are performed. To install a CoreDirector CI Switch I/O panel, Step 8 through Step 14 are performed. Prepare I/O Module for Removal STEP 1: Establish a Node Manager session with the CoreDirector CI Switch. STEP 2: Start a HyperTerminal session using TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch to view events.

Warning Negative 48 volts DC is present beneath the backplane cover in the CoreDirector Switch. Contact Ciena Technical Support for CoreDirector I/O Panel replacement. The following procedure is for the CoreDirector CI I/O Module removal only.
Remove CoreDirector CI Switch I/O Module STEP 3: At the front of the CoreDirector CI Switch, identify and tag then disconnect the cables from the connectors on the I/O panel. STEP 4: Loosen the two screws holding the I/O panel in place. STEP 5: Slide the I/O panel out of the slot. STEP 6: Place the I/O panel in an ESD-guard antistatic bag. STEP 7: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. --STOP-THIS CONCLUDES THE PROCEDURE

Warning Negative 48 volts DC is present beneath the backplane cover in the CoreDirector Switch. Contact Ciena Technical Support for CoreDirector I/O Panel installation. The following procedure is for the CoreDirector CI I/O Module installation only.
Install CoreDirector CI Switch I/O Module STEP 8: At the front of the Coredirector CI Switch, remove the modular I/O panel from its ESD-guard antistatic bag. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 86
4
STEP 9: Slide the replacement I/O panel fully into the slot. STEP 10: Tighten the two screws to secure the I/O panel in place. STEP 11: Connect the cables to the connectors on the I/O panel as tagged and identified in Step 3. STEP 12: Reestablish the Node Manager session. STEP 13: Stop the HyperTerminal program and disconnect the cable. STEP 14: Verify that all alarms associated with the disconnection of the PDU backplane cable have reset and that both fans have resumed normal (low) speed. If related alarms exist, refer to the Alarm and Trouble Clearing Procedure Manual and/or contact the next level of support. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 87
4
4 - 88
4
TOP 178D COREDIRECTOR SWITCH POWER UP

OVERVIEW
This Task Orientated Practice describes how to power up a CoreDirector Switch or CoreDirector CI Switch after an emergency or planned shutdown.
REQUIRED TOOLS
! ! ! !
ESD-guard wrist strap ESD-guard heel grounders Basic hand tools Digital multimeter (DMM)
PREREQUISITES
! !
Experience in the use of a DMM Knowledge of the location of the Battery Distribution Fuse Bay (BDFB) circuit breakers that provide -48 VDC power to the CoreDirector Switch PDU Familiarity with site lockout/tagout procedures
! ! !
TOP 015D Verifying -48 VDC Supply Voltage TOP 187D Test LEDs TOP 170D Removing and Installing a Control Module
PROCEDURE




4 - 89
4
STEP 1: Contact Network Operations Center personnel prior to powering up the CoreDirector Switch. STEP 2: Close the Battery Distribution Fuse Bay (BDFB) circuit breakers that provide -48 VDC power to the PDU. STEP 3: Verify that the -48 VDC supply voltage is present at the PDU power entry points using TOP 015D Verifying -48 VDC Supply Voltage. STEP 4: Refer to TOP 170D Removing and Installing a Control Module, Remove CM procedure and partially remove the C-CM. STEP 5: At the front of the Power Distribution Unit (PDU), lift the PDU faceplate. STEP 6: Turn on the four circuit breakers. STEP 7: Verify that the green POWER indicator is lit on the display panel. STEP 8: On a CoreDirector Switch, verify that the green LEDs are lit on both fan power modules. Note: If the Power or fan power module green indicators fail to light, turn off the four circuit breakers on the PDU and correct the problem before continuing with this procedure.
STEP 9: At the front of the Power Distribution Unit (PDU), close the PDU faceplate. STEP 10: Wait approximately 30 minutes for the system to reboot and stabilize. Note: In a single functioning CM scenario, user intervention is required. The user is prompted to continue the boot process with the existing DB on the CM.
STEP 11: Test the LED indicators using TOP 187D Test LEDs and note any LEDs that fail to light. STEP 12: Inspect the CoreDirector Switch indicators and module LEDs and note any red LEDs or other alarm indicators at the PDU or any module. STEP 13: Refer to TOP 170D Removing and Installing a Control Module, Install CM procedure and install the C-CM partially removed in Step 4. STEP 14: Contact the Network Operations Center and advise of any red alarm indications seen in Step 12, and obtain the current alarm status of the CoreDirector Switch. STEP 15: Clear any alarms indicated by the Operations Center using the applicable Trouble Clearing Procedures (TCPs) found in the CoreDirector Switch Alarm and Trouble Clearing Procedure Manual. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 90
4
TOP 183D REMOVING AND CONNECTING THE ALARMS AND PARALLEL TELEMETRY CABLE
OVERVIEW
This Task-Oriented Practice describes how to connect CoreDirector Switch or CoreDirector CI Switch alarms and parallel telemetry cable to the I/O panel. Because many types of dry alarms may be routed through the I/O panel to the Control Modules, this TOP provides the pin assignments only for the connection to the I/O panel ALARM connector.
REQUIRED TOOLS
! ! !
ESD-guard wrist strap ESD-guard heel grounders Common hand tools
PREREQUISITES
!
Not Applicable
!
Not Applicable
PROCEDURE


For cable removal, perform Step 1 and Step 2. For cable installation, perform Step 3 and Step 4. Remove Alarms And Parallel Telemetry Cable STEP 1: At the I/O panel on the rear of the CoreDirector Switch rack or on the front of the CoreDirector CI Switch chassis, loosen the two screws securing the cable connector to I/O panel ALARM connector. STEP 2: Lift the cable connector away from ALARM connector. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 91
4
Install Alarms And Parallel Telemetry Cable The CoreDirector Switch and CoreDirector CI Switch use different I/O panel connectors. Refer to Figure 4-20, Figure 4-21, and Table 4-9 for CoreDirector CI I/O panel cable and pinout information. Refer to Figure 4-22 (page 4-95) and Figure 4-23 (page 4-96) for CoreDirector I/O panel cable and pinout information.
CoreDirector Switch
Note:
STEP 3: Place the cable connector on the I/O panel ALARM connector. STEP 4: Tighten the two screws securing the cable connector to the ALARM connector. --STOP-THIS CONCLUDES THE PROCEDURE
100 2% ft (30.48 m) 2.00 in. (5.08 cm) 2.00 in. (5.08 cm)
Wire Wrap End Termination
AMP 748367-1 DSUB CONN (Shielded) Pin 1
P1
Figure 4-20. CoreDirector CI Alarm Cable Assembly
Pin 62 Pin 42
Pin 43 Pin 22
Pin 21
Pin 1
Figure 4-21. CoreDirector CI Alarm Cable Connector
4 - 92
178
177
4
Table 4-9. CoreDirector CI Alarm Cable Pin Assignments Pin # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 Signal Name PT17_N_F PT17_P_F PT16_N_F PT16_P_F GND PTI1_N_F PTI1_P_F PTI0_N_F PI10_P_F GND CRIT_VIS_CM_F CRIT_VIS_NC_F CRIT_VIS_NO_F MIN_AUD_CM_F MIN_AUD_NC_F MIN_AUD_NO_F GND PWRFL_CM_F PWRFL_NC_F PWRFL_NO_F PTI5_N_F PTI5_P_F PTI4_N_F PTI4_P_F GND PTO3_N_F PTO3_P_F PTO2_N_F PTO2_P_F GND Signal Description Parallel Telemetry Input-7(N) Parallel Telemetry Input-7(P) Parallel Telemetry Input-6(N) Parallel Telemetry Input-6(P) Ground Parallel Telemetry Input-1(N) Parallel Telemetry Input-1(P) Parallel Telemetry Input-0(N) Parallel Telemetry Input-0(P) Ground Critical Visible Common Critical Visible Normally Closed Critical Visible Normally Open Minor Audible Common Minor Audible Normally Closed Minor Audible Normally Open Ground Power Fail Common Power Fail Normally Closed Power Fail Normally Open Parallel Telemetry Input-5(N) Parallel Telemetry Input-5(P) Parallel Telemetry Input-4(N) Parallel Telemetry Input-4(P) Ground Parallel Telemetry Output-3(N) Parallel Telemetry Output-3(P) Parallel Telemetry Output-2(N) Parallel Telemetry Output-2(P) Ground Wire Color (Solid/Tracer) White/Black Black/White White/Brown Brown/White Black/Green White/Red Red/White White/Orange Orange/White Green/Black Black/Violet Black/Gray Brown/Red ----------------------Brown/Orange Brown/Yellow Brown/Green Brown/Blue Brown/Violet Brown/Gray Red/Orange White/Yellow Yellow/White White/Green Green/White Yellow/Brown White/Blue Blue/White White/Violet Violet/White Green/Brown Red/Yellow Red/Green Red/Blue Blue/Brown Red/Violet
------------------------ Unused
CRIT_AUD_CM_F Critical Audio Common CRIT_AUD_NC_F Critical Audio Normally Closed CRIT_AUD_NO_F Critical Audio Normally Open GND MAJ_VIS_CM_F Ground Major Visible Common

4 - 93
4
Table 4-9. CoreDirector CI Alarm Cable Pin Assignments (Continued) Pin # 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 Signal Name MAJ_VIS_NC_F MAJ_VIS_NO_F GND Signal Description Major Visible Normally Closed Major Visible Normally Open Ground Wire Color (Solid/Tracer) Red/Gray Orange/Yellow Violet/Brown ------------------------------------------------------------------White/Gray Gray/White Black/Brown Brown/Black ----------------------Black/Red Red/Black Black/Orange Orange/Black Gray/Brown Orange/Green Blue/Black Violet/Black ----------------------Gray/Black Red/Brown Orange/Brown Orange/Red Black/Yellow Yellow/Black
------------------------ Unused ------------------------ Unused ------------------------ Unused PTI3_N_F PTI3_P_F PTI2_N_F PTI2_P_F PTO1_N_F PTO1_P_F PTO0_N_F PTO0_P_F GND MIN_VIS_CM_F MIN_VIS_NC_F MIN_VIS_NO_F Parallel Telemetry Input-3(N) Parallel Telemetry Input-3(P) Parallel Telemetry Input-2(N) Parallel Telemetry Input-2(P) Parallel Telemetry Output-1(N) Parallel Telemetry Output-1(P) Parallel Telemetry Output-0(N) Parallel Telemetry Output-0(P) Ground Minor Visible Common Minor Visible Normally Closed Minor Visible Normally Open
------------------------ Unused
------------------------ Unused MAJ_AUD_CM_F Major Audible Common MAJ_AUD_NC_F MAJ_AUD_NO_F GND ACO_IN_N_F ACO_IN_P_F Major Audible Normally Closed Major Audible Normally Open Ground Alarm Cutoff Input (N) Alarm Cutoff Input (P)
4 - 94
4
50-PIN CONNECTOR 22-GAUGE SOLID CABLE, 25-PAIR, DUAL SHIELD (OR EQUIVALENT)
Figure 4-22. CoreDirector Alarms Cable Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
LENGTH TO BE DETERMINED BY SITE REQUIREMENTS.
4 - 95
4
SHIELD GROUND
PTO0 P
WIRE-WRAP
PTO0 N
Cut drain wire off at jacket end.
Twist/wrap foil shield securely around exposed drain wire at terminating end.
Figure 4-23. CoreDirector Alarms Cable Pinouts Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 96
4
TOP 185D REMOVING AND INSTALLING THE PDU-B/P CABLE

OVERVIEW
This Task-Oriented Practice describes how to remove and install the CoreDirector Switch PDU-B/P cable on the CoreDirector Switch. Note: This TOP applies only to the CoreDirector Switch. It is not necessary for the CoreDirector CI Switch.
REQUIRED TOOLS
! ! !
PREREQUISITES
!
Not Applicable
!
TOP 072D Ciena Return Material Authorization (RMA) Procedure
PROCEDURE

Warning Negative 48 volts DC is present in the equipment. Contact can cause personal injury. Take appropriate safety precautions. Refer to Voltage Precaution in the General Safety Precautions on page page xx.

To remove the PDU-B/P cable, Step 1 through Step 5 are performed. To install the PDU-B/P cable, Step 6 through Step 10 are performed. Remove PDU-B/P Cable STEP 1: At the rear of the Power Distribution Unit (PDU), loosen the two screws securing the upper PDUB/P cable connector to the PDU. STEP 2: Remove the PDU-B/P cable connector from the PDU. STEP 3: Loosen the two screws securing the connector at the other end of the PDU-B/P cable to the Input/ Output (I/O) panel.

4 - 97
4
STEP 4: Remove the PDU-B/P cable connector from the I/O panel. Note: Disconnecting the PDU backplane cable generates alarms and causes both fans to switch to high speed.
CoreDirector Switch
STEP 5: Complete the required Return Material Authorization (RMA) procedure in accordance with TOP 072D, Ciena Return Material Authorization (RMA) Procedure. --STOP-THIS CONCLUDES THE PROCEDURE Install PDU-B/P Cable STEP 6: Connect the PDU-B/P cable connector to the I/O panel. STEP 7: Tighten the two screws securing the PDU-B/P cable connector to the I/O panel. STEP 8: Connect the connector at the other end of the PDU-B/P cable to the PDU. STEP 9: Tighten the two screws securing the PDU-B/P cable connector to the PDU. STEP 10: Verify that all alarms associated with the disconnection of the PDU backplane cable have reset and that both fans have resumed normal (low) speed. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 98
4
TOP 187D TEST LEDS

OVERVIEW
This Task-Oriented Practice describes how to test the CoreDirector Switch or CoreDirector CI Switch system Light Emitting Diodes (LEDs).
REQUIRED TOOLS
! !
PREREQUISITES
!
Not Applicable
! ! ! ! ! ! !
TOP 169D Removing and Installing a Cooling Fan Unit TOP 170D Removing and Installing a Control Module TOP 171D Removing and Installing a Switch Module TOP 172D Removing and Installing an Optical Module TOP 173D Removing and Installing a Line Module TOP 174D Removing and Installing a Timing Module TOP 176D Removing and Installing a Fan Power Module
PROCEDURE

STEP 1: While the switch is operating, open the front access doors to the Power Distribution Unit (PDU) (CoreDirector Switch only) and fan units. STEP 2: Observe the CoreDirector Switch LEDs presently lit on the display panel or module, fans, and fan power modules (CoreDirector Switch only). STEP 3: On a CoreDirector Switch, open the front access doors to Shelf A, Shelf B, and Shelf C. On a CoreDirector CI Switch, open the front access door to Shelf A. STEP 4: Observe the CoreDirector Switch LEDs presently lit on each Control Module (CM), Switch Module (SM), Optical Module (OM), Line Module (LM), and Timing Module (TM). STEP 5: Press the LED switch on the display panel or module (Figure 4-24). STEP 6: Verify that all system LEDs on the PDU, fans, fan power modules, CMs, SMs, OMs, LMs, and TMs are lit. STEP 7: If required, record the measured results on Test Data Sheet 1 - CoreDirector Site Information or CoreDirector CI Site Information. CoreDirector Test Data Sheets are located in Appendix A and CoreDirector CI Test Data Sheets in Appendix B of this manual.

4 - 99
4
STEP 8: Press the LED switch again and verify that all system LEDs on switch components (except the LEDs observed in Step 1) are turned off.
POWER CRITICAL MAJOR MINOR ACO LED POWER A POWER B FAN SHELF SHELF A SHELF B SHELF C
A BATTERY
ACO LED
POWER GOOD
FAN 1 POWER MODULE
POWER CRITICAL MAJOR MINOR

B BATTERY
POWER A POWER B FAN SHELF MODULE SHELF
LED Test Switch CoreDirector Switch Display Panel
LED Test Switch CoreDirector CI Switch Display Module
Figure 4-24. LED Test Switch STEP 9: If any system LED on the CoreDirector Switch PDU fails to light, replace the PDU display board in accordance with TOP 175D. STEP 10: If any system LED on a CM fails to light, replace the CM in accordance with TOP 170D Removing and Installing a Control Module. STEP 11: If any system LED on an SM fails to light, replace the SM in accordance with TOP 171D Removing and Installing a Switch Module. STEP 12: If any system LED on an OM fails to light, replace the OM in accordance with TOP 172D Removing and Installing an Optical Module. STEP 13: If any system LED on an LM fails to light, replace the LM in accordance with TOP 173D Removing and Installing a Line Module. STEP 14: If any system LED on a TM fails to light, replace the TM in accordance with TOP 174D Removing and Installing a Timing Module. STEP 15: If any system LED on a fan unit fails to light, replace the fan in accordance with TOP 169D Removing and Installing a Cooling Fan Unit. STEP 16: If any system LED on a fan power module fails to light, replace the fan power module in accordance with TOP 176D Removing and Installing a Fan Power Module. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 100
4
TOP 194D CONNECTING TO THE CM AND USING A LAPTOP TO CONFIGURE THE COREDIRECTOR SWITCH
OVERVIEW
This Task-Oriented Practice describes how to connect to the CoreDirector Switch or CoreDirector CI Switch Control Module (CM) using a laptop computer.
REQUIRED TOOLS
! ! !
ESD-guard wrist strap ESD-guard heel grounders One or both of the following cables: 9-pin to 25-pin RS-232 serial cable (DB-9F to DB-25M straight cable) for connection to the CM. The 9-pin connector is configured for Data Terminal Equipment (DTE), and the 25-pin connector is configured for Data Communications Equipment (DCE). 9-pin to 9-pin RS-232 serial cable (DB-9F to DB-9F null modem cable) for connection to the backplane I/O panel. Both connectors of a null modem cable are configured for DTE.
! !
Laptop computer running Windows NT, Windows 2000, or Windows XP HyperTerminal available on the laptop computer
PREREQUISITES
!
! !
The user must be familiar with CoreDirector Node Manager software. The user must have Node Manager Termination Point Provisioner privilege or Node Manager Troubleshooter (TS) privilege. The craftsperson must be a registered system user with a valid user name and password to log in to the Command Line Interface (CLI). The user must have a knowledge of TL1 commands and of using the CoreDirector Switch TL1 Interface Manual.
! !
CoreDirector Switch TL1 Interface Manual TOP 278D Handling Circuit Packs Properly

4 - 101
4
CoreDirector Switch
Warning:



Performance of the following step may cause a traffic disruption. This instruction is intended as a general guide only, has not been tested for all possible applications or configurations, and may not be complete or accurate for some situations. To connect to the Craft connector on the CM, perform Step 1 and Step 3 through Step 19. Caution: To connect to the Craft connector on the I/O panel, perform Step 2 through Step 19. STEP 1: Use the 9-pin to 25-pin RS-232 serial cable for this step. At the front of the CoreDirector Switch or CoreDirector CI Switch, connect the cable to the connector labeled Craft on the CM being accessed. Refer to Table 4-10 for pinout information and Figure 4-25 for the connector location. Table 4-10. 25-Pin Connector Pin Assignments for the RS-232 Serial Cable Pin 1 2 3 4 5 6 7 8 9 10 11 12 13 GND Transmit Data Receive Data Request To Send Clear To Send Data Set Ready GND Data Carrier Detect NC NC NC NC NC Signal 14 15 16 17 18 19 20 21 22 23 24 25 Pin NC NC NC NC NC NC Data Terminal Ready NC NC NC NC NC Signal
NOTE: All signals are described from the perspective of the laptop PC. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 102
4
CRAFT (RS-232 DCE)
FAIL MAINT ACTIVE
200390
Figure 4-25. Control Module (CM) Front View STEP 2: Use the 9-pin to 9-pin null modem serial cable for this step. At the I/O panel, connect the null modem cable to A-CM for connection to CM 1 or to C-CM for connection to CM 2. Refer to Table 4-11 for pinout information. Figure 4-26 shows the I/O panel location. Figure 4-27 identifies the I/ O connectors for the CoreDirector Switch, and Figure 4-28 shows the I/O connectors for the CoreDirector CI Switch.
ACO LED
FAN A
FAN B
I/O Panel
CONTROL MODULE
CONTROL MODULE
........ .......
........ .......
SWITCH MODULE
SWITCH MODULE
SWITCH MODULE
SWITCH MODULE
CoreDirector Switch (Rear View) CoreDirector CI Switch (Front View)
Figure 4-26. CoreDirector Switch I/O Panel Locations

4 - 103
4
SONET
164
C-CM
RS-232
A-CM RS-232 DTE
SDH (T1)
165
Figure 4-27. I/O Panel Top View (CoreDirector Switch)
A-CM 1
A-CM 2
MAIN
ETHERNET
AUX
RS-232 DTE
RS-232 RS-232 Craft Interfaces DTE
BITS
Figure 4-28. I/O Panel Connectors (CoreDirector CI Switch)
SONET I/O MODULE
A L A R M
Alarm Interfaces
4 - 104
4
Table 4-11. RS-232 Craft Connector Pin Designation Pin 1 2 3 4 5 6 7 8 9 Carrier Detect Receive Data Transmit Data Data Terminal Ready GND Data Set Ready Request To Send Clear To Send Ring Indicator Signal
NOTE: Use a null modem serial cable between this connector and a laptop PC.
STEP 3: Connect the opposite end of the cable to the serial port (COM1) on the laptop PC. STEP 4: Apply power to the laptop PC. STEP 5: Start the HyperTerminal program and create a new connection with the Com port settings, as follows:
! ! ! ! !
Bits per second - 19200 Data Bits - 8 Parity - None Stop Bits - 1 Flow Control - None
STEP 6: At the HyperTerminal prompt on the PC, press Enter and enter the User Name and Password. STEP 7: The CM CLI Menu is displayed (Figure 4-29). Note: The CLI Menu display responses in this procedure are typical and may not exactly match the actual responses.
---C I E N A C O R E D I R E C T O R ------C M C L I M E N U -------------------------------------------------------------------1. Display current install settings ---2. Display general information about this CM ---3. Enter Upgrade mode ---4. Enter Backup and Restore mode ---5. Revert to previous version and database ---6. Change CLI Login User ID ---7. Change CLI Login Password ---8. Reset Timing Plane for Firmware Upgrade ---9. Operations Menu ---10. Software Configuration Menu ---11. Change install settings ---12. Logout -------------------------------------------------------------Enter Choice (? for help anytime):
Figure 4-29. CM CLI Menu Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 105
4
STEP 8: Type 1 and press Enter to display the current install settings. STEP 9: Type 2 and press Enter to display the general information about the CM. STEP 10: Type 3 and press Enter to display the Upgrade menu. Type 10 and press Enter to return to the CM CLI menu. STEP 11: Type 4 and press Enter to display the Backup and Restore menu. Type 11 and press Enter to return to the CM CLI menu. STEP 12: Type 5 and press Enter to display the Revert menu. Type 5 and press Enter to return to the CM CLI menu. STEP 13: Type 6 and press Enter to change the CLI login user ID. Type 7 and press Enter to change the CLI login password. STEP 14: Type 8 and press Enter to reset the timing plane for firmware upgrade. STEP 15: Type 9 and press Enter to display the Operations Menu. Type 5 and press Enter to return to the CM CLI menu. STEP 16: Type 10 and press Enter to display the Software Configuration Menu. Type 3 and press Enter to return to the CM CLI Menu. STEP 17: Type 11 and press Enter to Change install settings. STEP 18: Type 12 and press Enter to log out of the CM CLI Menu. STEP 19: Stop the HyperTerminal program and disconnect the cable. --STOP-THIS CONCLUDES THE PROCEDURE
CoreDirector Switch
4 - 106
4
TOP 195D CONNECTING AND LOGGING ON TO NODE MANAGER VIA THE ETHERNET INTERFACE
OVERVIEW
This Task-Oriented Practice describes how to connect and log on to the CoreDirector Switch or CoreDirector CI Switch Node Manager software. For additional information, refer to CoreDirector Node Manager User Guide.
REQUIRED TOOLS
! ! ! ! ! !
PREREQUISITES
! ! !
The user must be familiar with Microsoft Windows software. The user must be familiar with CoreDirector Node Manager software. The user must have Node Manager Termination Point Provisioner privilege or Node Manager Troubleshooter (TS) privilege.
!
CoreDirector Node Manager User Guide
PROCEDURE

Caution: Notify appropriate personnel before removing operation-critical components.
Warning:


4 - 107
4
To establish a CoreDirector Node Manager connection, Step 1 through Step 4 are performed. To log on to CoreDirector Node Manager, Step 5 through Step 7 are performed. Establish CoreDirector Node Manager Connection STEP 1: Connect the 10Base-T RJ-45 Ethernet cable to the 10/100 Ethernet connector on the I/O panel, as follows:
! !
Connector A-CM AUX provides connection to CM 1 Connector C-CM AUX provides connection to CM 2. Figure 4-30 shows the Input/Output (I/O) panel locations, Figure 4-31 shows the I/O panel, connectors on the CoreDirector Switch, and Figure 4-32 I/O panel connectors on the CoreDirector CI Switch.
ACO LED
FAN A
FAN B
I/O Panel
CONTROL MODULE
CONTROL MODULE
........ .......
........ .......
SWITCH MODULE
SWITCH MODULE
SWITCH MODULE
SWITCH MODULE
CoreDirector Switch (Rear View) CoreDirector CI Switch (Front View)
Figure 4-30. CoreDirector Switch I/O Panel Location
4 - 108
4
CoreDirector Switch
10/100 Ethernet
144
Alarm
BITS 2 C-CM AUX A-CM AUX C-CM MAIN A-CM MAIN BITS 1
PDU A-CM RS-232 DTE C-CM RS-232 DTE
T1 I/O Panel (SONET)

Timing Interface (BITS 1 and BITS 2) 10/100 Ethernet
Alarm
A-CM MAIN C-CM MAIN A-CM AUX C-CM AUX
145
PDU C-CM RS-232 DTE A-CM RS-232 DTE
E1 I/O Panel (SDH) Figure 4-31. I/O Panel Connectors on the CoreDirector Switch
A-CM 1
A-CM 2
A-CM 1
A-CM 2
MAIN
MAIN
ETHERNET
ETHERNET
AUX
AUX
RS-232 DTE
RS-232 Craft Interfaces
RS-232 DTE
BITS 1 BITS
BITS 2 TX TX
RX
RX
Figure 4-32. I/O Panel Connectors on the CoreDirector CI Switch Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
SONET I/O MODULE
SDH I/O MODULE
A L A R M
Alarm Interfaces
A L A R M
148
SONET (T1)
SDH (E1)
4 - 109
4
STEP 2: Connect the opposite end of the cable to the Ethernet connector on the PC. STEP 3: Apply power to the PC. STEP 4: At the Windows NT, Windows 2000, or Windows XP desktop, select Start > Programs > Node Manager for CoreDirector > Node Manager 4.0.x. The Node Manager command window opens and is minimized. Log On To The Coredirector Node Manager Connection STEP 5: After the connection is established, the Node ManagerNew Node Login dialog box opens. The Node URL and User Name fields may appear with default entries. To enter a node name, use one of the following formats: Domain Name (for example, venus.lab.dept.xyz.com) Domain Name:HTTPport (for example, venus.lab.dept.xyz.com:8080) Node Name:IPAddress (for example, venus:11.120.30.11) Node Name:IPAddress:HTTPport (for example, venus:11.120.30.11:8080) All node names are case-sensitive.
Note:
STEP 6: Enter the user name and password in the User Name and Password fields. STEP 7: Click OK. The Administration > System Configuration screen is displayed. After successfully logging in, losing or regaining connectivity may cause an HA DCN dialog box to appear. Node Manager will not respond until OK or Exit (depending on the dialog box) is clicked. To access this dialog box, use ALT-Tab to traverse through the list of windows. --STOP-THIS CONCLUDES THE PROCEDURE
Note:
4 - 110
4
TOP 207D ADDING CHANNEL CAPACITY

OVERVIEW
This TOP describes how to add CoreDirector Switch or CoreDirector CI Switch channel capacity. Adding channel capacity consists of adding Optical Modules (OMs) only, adding Line Modules (LMs) only, or adding LMs and OMs. This TOP also defines the testing required to ensure that the OMs, LMs, and applicable Switch Modules (SMs) are operational prior to customer acceptance.
REQUIRED TOOLS
! ! ! ! ! ! !
ESD-guard wrist strap ESD-guard heel grounders Common hand tools 10base-T, RJ-45 crossover cable CoreDirector Node Manager software Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP Synchronous Optical Network (SONET) test set (Digital Lightwaves ASA-PKG-OC48c or equivalent)
PREREQUISITES
! ! !
The user must be familiar with CoreDirector Node Manager software. The user must have Node Manager Account Administrator privilege. The user must be familiar with using a SONET test set (Digital Lightwaves ASA-PKG-OC48c or equivalent).
! ! ! ! !
TOP 171D Removing and Installing a Switch Module TOP 172D Removing and Installing an Optical Module TOP 173D Removing and Installing a Line Module TOP 220D Test Line Modules and Optical Modules TOP 221D Test Optical Module
PROCEDURE
Warning:



4 - 111
4
Caution: Notify appropriate personnel before removing operation-critical components. Performance of the following procedure may cause a traffic disruption. This instruction is intended as a general guide only, has not been tested for all possible applications or configurations, and may not be complete or accurate for some situations.
To install additional OMs to existing LMs, perform Step 1 through Step 3. To install additional LMs, perform Step 4 and Step 5. To install additional LMs and OMs, perform Step 6 through Step 8. Install Additional OMs STEP 1: Using the information outlined in Table 4-12 and Table 4-13, ensure that at least the minimum number of SMs are installed in the CoreDirector Switch for the number of OMs being installed. If there are not enough SMs present for the additional OMs, contact Ciena Technical Support to order the necessary SMs and refer to TOP 171D Removing and Installing a Switch Module to install the SMs. Note: UPSR/SNCP requires a minimum of 14 SMs for the CoreDirector and 4 SMs for the Coredirector CI.
Table 4-12. Mapping Primary SMs to Supported LM OMs/Ports on CoreDirector Switch Number of Primary SMs Installed 1 2 3 4 5 6 7 Line Module Type 0 Maximum number of ports supported LM-2 (OMs) LM-8 (OMs) LM-20 (OPs) 0 0 0 0 0 3 0 0 1 6 0 0 2 9 0 0 3 9 0 0 3 9 0 1 4 16 10 1 4 16 10 8 1 4 16 10 9 1 4 16 10 10 1 4 16 10 11 1 4 16 10 12 2 8 16 20 13 2 8 16 20 14 2 8 16 20
LM-16 (OPs & EPs) 0
Table 4-13. Mapping Primary SMs to Supported LM OMs/Ports on CoreDirector CI Switch Number of Primary SMs Installed 1 2 3 Line Module Type 0 Maximum number of ports supported LM-2 (OMs) LM-8 (OMs) LM-20 (OPs) 0 0 0 0 3 12 0 1 6 16 10 2 8 16 20 4 2 8 16 20
LM-16 (OPs & EPs) 0
STEP 2: Install required OMs in accordance with TOP 172D Removing and Installing an Optical Module. Note: Testing modules is optional. Test modules only if required to do so by local practices.
4 - 112
4
STEP 3: Test any installed OMs in accordance with the appropriate steps in TOP 220D Test Line Modules and Optical Modules and TOP 221D Test Optical Module. --STOP-THIS CONCLUDES THE PROCEDURE Install Additional LMs All CoreDirector modules are designed such that when inserted, the air gaps between the faceplates are minimal. This provides a continuous low impedance ground path for Electromagnetic Interference and Susceptibility compliance, ESD compliance, and a path to chassis ground for safety. However, there could be insufficient space for the module face plate to fit securely against the chassis. If required, loosen the faceplate screws of the adjacent modules on either side as needed and then install the module. If multiple LMs are being installed, do not tighten the faceplate screws until after the last LM is installed and the slot alignment checked.
Note:
STEP 4: Install new LMs in accordance with TOP 173D Removing and Installing a Line Module. Note: Testing modules is optional. Test modules only if required to do so by local practices.
STEP 5: Test any installed LMs in accordance with the appropriate steps in TOP 220D Test Line Modules and Optical Modules. Note: Spare OMs may be needed to test all OM slots in the newly installed LM. If no spare OMs are available at the site, obtain OMs from Ciena Technical Support and return when testing is completed. --STOP-THIS CONCLUDES THE PROCEDURE Install Additional LMs and OMs All CoreDirector modules are designed such that when inserted, the air gaps between the faceplates are minimal. This provides a continuous low impedance ground path for Electromagnetic Interference and Susceptibility compliance, ESD compliance, and a path to chassis ground for safety. However, there could be insufficient space for the module face plate to fit securely against the chassis. If required, loosen the faceplate screws of the adjacent modules on either side as needed and then install the module. If multiple LMs are being installed, do not tighten the faceplate screws until after the last LM is installed and the slot alignment checked.
Note:
STEP 6: Install new LMs in accordance with TOP 173D Removing and Installing a Line Module. STEP 7: Install required OMs in accordance with TOP 172D Removing and Installing an Optical Module. Note: Testing modules is optional. Test modules only if required to do so by local practices.

4 - 113
4
STEP 8: Test any installed LMs and OMs in accordance with the appropriate steps in TOP 220D Test Line Modules and Optical Modules and TOP 221D Test Optical Module. Note: Spare OMs may be needed to test all OM slots in the newly installed LM. If no spare OMs are available at the site, obtain OMs from Ciena Technical Support and return when testing is completed. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 114
4
TOP 208D CONFIGURATION DATABASE BACKUP AND RESTORE

OVERVIEW
This Task-Oriented Practice describes how to back up and restore the CoreDirector Switch or CoreDirector CI Switch Network Element (NE) configuration database at the node level using CM CLI. ON-Center Switching Manager (CSM) Software users should refer to the LightWorks ON-Center Management Suite documentation set for the appropriate CSM Software procedure.
REQUIRED TOOLS
The following are required for all installations:
!
Personal Computer (PC) or laptop computer running Windows NT, Windows 2000, or Windows XP HyperTerminal available on PC WFTPD (by Texas Imperial Software) File Transfer Protocol (FTP) software or another 32-bit FTP software package with which Craft Interface personnel are familiar FTP server PC for storing database backup files ESD-guard wrist strap ESD-guard heel grounders One or both of the following cables: 9-pin to 25-pin RS-232 serial cable (DB-9F to DB-25M straight cable) for connection to the CM. The 9-pin connector is configured for Data Terminal Equipment (DTE), and the 25-pin connector is configured for Data Communications Equipment (DCE). 9-pin to 9-pin RS-232 serial cable (DB-9F to DB-9F null modem cable) for connection to the backplane I/O panel. Both connectors of a null modem cable are configured for DTE.
! !
The following are required when the procedure is performed at the NE.
! ! !
PREREQUISITES
! !
Disable firewalls on the FTP server or the file transfer will not work. Craft Interface personnel must be registered system users with valid user names and passwords to log into the Command Line Interface (CLI). Craft Interface personnel must have knowledge in the use, setup, and configuration of HyperTerminal software. Craft Interface personnel must have knowledge in the use, setup, and configuration of FTP software on the FTP server.
!
TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch

4 - 115
4
CoreDirector Switch

To connect to the CM, Step 1 through Step 4 are performed. To configure an FTP server for file transfer, Step 5 through Step 12 are performed. To back up the configuration database files to an FTP server, Step 13 through Step 23 are performed. To restore the configuration database files to an FTP server, Step 24 through Step 38 are performed. Note: If the upgrade is performed from the CSM Software workstation, refer to the CSM Software documentation and perform the CSM Software Backup on Demand (Manual) procedure.
Connect to CoreDirector Switch Note: The CLI Menu display responses in the following procedure are typical and may not exactly match the actual responses.
STEP 1: Connect to the CoreDirector Switch in one of the following ways:

!
Connect a cable from the Craft port on the CM to the laptop computer, and start a HyperTerminal program in accordance with TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch. From the PC, launch a Telnet session to the CoreDirector Switch virtual Internet Protocol (IP) address from the Windows Start menu, as follows: a. Select Run. b. Type telnet <CoreDirector IP address>. c. Press Enter. The CM CLI Login prompt is displayed:
STEP 2: Log in to the CoreDirector CLI at an administrator level. STEP 3: If required, select the option to return to the CM CLI Menu. The CM CLI Menu is displayed. STEP 4: If a database backup file location is already established, obtain the appropriate FTP location (IP address), FTP user name, and password and proceed to Step 13. Configure FTP Server STEP 5: From the CM CLI menu, type 1 and press Enter to select Display current install settings. The current install settings are displayed. Step 6 through Step 12 outline one method of setting up a backup file directory structure on an FTP server using WFTPD FTP software by Texas Imperial Software. Other methods or directory structure/names can be used to accomplish the same task.
Note:
4 - 116
4
STEP 6: Note the CM name. The CM name is used as the New User ID in the FTP software setup steps later in this procedure. STEP 7: At the FTP server PC, start the WFTPD application. Note: Disable firewalls on the FTP server or the file transfer will not work.
STEP 8: At the WFTPD window, click the security tab and select user/rights. STEP 9: Select New User and type user name noted in Step 6. STEP 10: Type the same characters entered in Step 9 for Password and Verify Password. STEP 11: Type the desired file location where backup files are to be stored (for example, D:\FTPROOT\Neptune) in the Home Directory box and click the Restricted to Home block. The D:\FTPROOT\Neptune file location in Step 11 is an individual folder where the backup file will be stored on the FTP server. This individual folder isolates these backup.lnt files from others and allows the user to keep them separate. The file location must also be created in the corresponding directory (in this case, D:\) of the FTP server. Click Rights and ensure that the Read, Create files/directories, overwrite/ delete, list directories are checked, then click Done.
Note:
STEP 12: Click Logging > Log Options and ensure that all blocks are checked except Winsock Calls, then click OK. Back Up Configuration Database Files STEP 13: From the CM CLI menu, type the option number to Enter Backup and Restore mode and press Enter. The Backup and Restore Menu is displayed (Figure 4-33).
---C I E N A C O R E D I R E C T O R ------B A C K U P A N D R E S T O R E M E N U -------------------------------------------------------------------1. Specify IP Address of FTP site ---2. Specify user id for FTP ---3. Specify password for FTP ---4. Display above settings - - - - - - - - - - - - - - - - - - ---5. Verify Restore ---6. Initiate Backup ---7. Transfer Backup Archive to FTP Server - - - - - - - - - - - - - - - - - - ---8. Transfer Restore Archive from FTP Server ---9. Initiate Restore ---10. Commit to Restored Database ---11. Return to CM CLI Menu -------------------------------------------------------------Enter Choice (? for help anytime):
Figure 4-33. Backup and Restore Menu STEP 14: Type 1 and press Enter to select Specify IP Address of FTP Site. STEP 15: Type the configuration database backup FTP server address (for example, 10.5.55.39) and press Enter. STEP 16: Type 2 and press Enter to select Specify user id for FTP and type the user ID (established in Step 9) and press Enter.

4 - 117
4
STEP 17: Type 3 and press Enter to select Specify password for FTP and type the password (established in Step 10) and press Enter. STEP 18: Type 4 and press Enter to select Display above settings and verify that displayed settings are correct. STEP 19: If changes are required, repeat Step 14 through Step 18 and correct as necessary. STEP 20: Type 6 and press Enter to select Initiate Backup. STEP 21: Type 7 and press Enter to select Transfer Backup Archive to FTP Server. The following prompt is displayed:
Enter the database backup filename:
STEP 22: Type the database backup filename using the following characters and specify.lnt for the filename extension. For example: backup1.lnt. Characters that can be used are: A to Z, a to z, 0 to 9, - (hyphen) _(underscore) ~(tilde) After the backup archive is transferred to the FTP server, observe that the Backup and Restore Menu is displayed (Figure 4-33). STEP 23: Type 11 and press Enter to return to the CLI menu. Restore Configuration Database Files

Do not remove the CM during this procedure. The primary CM undergoing restore is programmed to become primary in the event that the process is interrupted. If the CM is removed, then reinstalled in another CoreDirector Switch or reinstalled in the same CoreDirector Switch at a later date, the CM takes control and continues the DB restore. Contact Ciena Technical Support if the CM is removed during the DB restore procedure. Log off all Node Manager user sessions prior to restoring the configuration database files. If the Ring configuration is changed after backing up the database, restoring the original configuration causes a traffic hit when the SNCs discover that the protection class for the new configuration is no longer applicable move to the new configuration.
Caution:
Note:
STEP 24: From the CM CLI menu, type the option number to Enter Backup and Restore mode and press Enter. The Backup and Restore Menu is displayed (Figure 4-33). STEP 25: Type 1 and press Enter to select Specify IP Address of FTP Site. STEP 26: Type the configuration database backup FTP server address (for example, 10.5.55.39) and press Enter. STEP 27: Type 2 and press Enter to select Specify user id for FTP. STEP 28: Type the user (established in Step 9) and press Enter.
4 - 118
4
STEP 29: Type 3 and press Enter to select Specify password for FTP. STEP 30: Type the password (established in Step 10) and press Enter. STEP 31: Type 4 and press Enter to select Display above settings; verify that the displayed settings are correct. STEP 32: If changes are required, repeat Step 25 through Step 31 and correct as necessary. STEP 33: Type 8 and press Enter to select Transfer Restore Archive from FTP Server. The following prompt is displayed:
Enter the database backup filename:
STEP 34: Type the database backup filename .lnt for the filename extension (for example, backup1.lnt). STEP 35: Type 9 and press Enter to select Initiate Restore. STEP 36: Type 5 and press Enter to select Verify Restore STEP 37: Type 10 and press Enter to select Commit to Restored Database. Note: The CM reboots to commit to the restored database.
STEP 38: Wait approximately 5 to 10 minutes for the CoreDirector Switch to stabilize. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 119
4
4 - 120
4
TOP 209D SETTING UP A COREDIRECTOR SWITCH FOR MODEM ACCESS

OVERVIEW
This Task-Oriented Practice describes how to set up a CoreDirector Switch or CoreDirector CI Switch for modem access. Connecting to the CoreDirector Switch through a modem enables remote users to issue TL1 commands to the CoreDirector Switch. The CoreDirector Switch does not support CoreDirector Node Manager sessions by modem.
REQUIRED TOOLS
! !
Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP HyperTerminal available on PC
PREREQUISITES
!
Two external modems: 3Com U.S. Robotics Fax Modem 56K, Model No. 5686 First modem labeled Modem to PC Second modem labeled Modem to CoreDirector Note: Once configured, modems are not interchangeable and cannot be used for other applications.
Two RS-232C cables: CoreDirector Switch to modem cableDB-9 female connector/DB-25 male connector PC to ModemPC-specific, typically DB-9 female connector/DB-25 male connector
! !
Two analog phone lines The craftsperson must be a registered system user with a valid user name and password to log in to the Command Line Interface (CLI). The user must have a knowledge of TL1 commands and of using the CoreDirector Switch TL1 Administration and Reference Manual. The Craftsperson must have knowledge using and configuring a fax modem.
!
None
PROCEDURE


4 - 121
4
Caution: Performance of the following step may cause a traffic disruption. This instruction is intended as a general guide only, has not been tested for all possible applications or configurations, and may not be complete or accurate for some situations. Connecting to the CoreDirector Switch by modem enables remote Command Line Interface functions only. CoreDirector Node Manager cannot be used through modem connectivity. CoreDirector Node Manager only works over an IP Ethernet connection.
Note:
STEP 1: Start the HyperTerminal program. Then create a new connection choosing a CoreDirector Switch name (example: CD172), an icon, and the COM port to use. Modify the Com port settings as follows:
! ! ! ! !
Bits per second - 19200 Data Bits - 8 Parity - None Stop Bits - 1 Flow Control - None
Test Modems STEP 2: Set the Initial DIP Switch Configuration for the modem labeled Modem to PC using the settings outlined in Table 4-14. Table 4-14. DIP Switch Settings for the Modem to PC DIP Switch 1 2 3 4 5 6 7 8 Off On Off On Off Off On Position On Ignore DTR Provide verbal (word) result codes Enable result codes Command Mode Local Echo Suppression (suppress echo) Disables auto answer Set DCD to normal behavior Load Y0 - Y4 configuration from NVRAM Enable command recognition Function
Note:
DIP switch setting changes become active upon modem power reset.
STEP 3: Connect the modem to the PC and to the modem power source. Type the commands in order listed in Table 4-15. Observe that OK is returned as a result string after each AT command. Note: If the OK string does not show up or characters are not echoed by the modem, verify the correctness of the Com port settings and cabling.
4 - 122
4
Table 4-15. Software Command Configuration Command AT ATZ3 ATI4 AT&B1 AT&C1 AT&U10 ATQ2 AT&W0 ATY0 Command Comment Basic response check from modem Sets modem to default factory settings &F0, generic template Reports current settings Lock speed on serial port to current 19200 rate Provide normal DCD signal Minimum connection speed allowed of 19200 bps Quiet mode; result codes only in originate mode Write current configuration to NVRAM template 0 Use Template 0 settings
Note:
The CoreDirector Switch supports only the 19200 rate.
STEP 4: Repeat Step 2 and Step 3 for the modem labeled Modem to CD. Configure CD Modem STEP 5: Turn off the modem labeled Modem to CD, and change the DIP switches as outlined in Table 416. Table 4-16. Modem to CoreDirector Switch DIP Switch Settings DIP Switch 1 2 3 4 5 6 7 8 Off Off On Off Off Off Off Position On Ignore DTR Provide verbal (word) result codes Suppress result codes Command mode local echo suppression (suppress echo) Enable auto answer on first ring Set DCD to normal behavior Load Y0-Y4 configuration from NVRAM Disable command recognition Function

4 - 123
4
It is critical that the modem settings be compatible with the Settings in Table 416. In particular, any setting that is called Echo, Display Local Commands, Disable Echo, or Enable Echo must be set to prevent characters from being sent to the CoreDirector Switch. For a specific modem, the setting could either be ON or OFF. An incorrect configuration of the modem can affect a CoreDirector Switch after a power failure. CoreDirector CLI has a countdown that can stop the boot process if characters are received at the CM console port. If the modem local echo is active, the CM's own echoed-back characters at the countdown act like user input and prevent the normal boot from completing autonomously; more user input at the CLI Configuration Menu would then be required to let the boot process complete. After these settings are entered, the CD modem will not respond to AT commands. It can be used only to connect to the CoreDirector Switch and to be ready to answer to an incoming call from the Modem to PC modem.
Caution:
Note:
STEP 6: Using the DB-9 to DB-25 cable and an analog phone line, connect the modem labeled Modem to CD to one of the following connectors on the I/O panel (See Figure 4-34 & Figure 4-35):
! !
Connector A-CM for connection to CM 1 Connector C-CM for connection to CM 2.
STEP 7: Connect the modem to the modem power source and apply power to the modem. Refer to Table 4-17 for pinout information. Figure 4-34 shows the I/O panel location. Figure 4-35 identifies the rear I/O panel connector designations. If performing this procedure on a CoreDirector CI Switch, the I/O panel is located in Shelf A, and the modem connections are made to A-CM 1 or A-CM 2. Table 4-17. RS-232 Craft Connector Pin Designation Pin 1 2 3 4 5 6 7 8 9 Signal Carrier Detect Receive Data Transmit Data Data Terminal Ready Gnd Data Set Ready Request to Send Clear to Send Ring Indicator
Note:
4 - 124
4
Rear IO Panel
C-CM RS 232 DTE Modem Hookup
A-CM RS 232 DTE Modem Hookup
Figure 4-34. CoreDirector Switch Rear I/O Panel Location

10/100 ETHERNET
BITS 2 ALARM C-CM AUX A-CM AUX C-CM MAIN A-CM MAIN BITS 1
CD9916-4
PDU A-CM RS 232 DTE C-CM RS 232 DTE
Figure 4-35. CoreDirector Switch Rear I/O PanelTop View Setup PC Modem STEP 8: Connect the Modem to PC modem to the PC and to an analog phone line. Connect the modem to the modem power source and turn on the modem. STEP 9: From the HyperTerminal window, type AT and press Enter to dial from the PC to the CoreDirector Switch. An OK response from the modem ensures a good connection. Type ATD and the phone number (example: ATD5551234) Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 125
4
Note: It might be necessary to use ATDP (for Pulse dialing) or ATDT (for Tone dialing). If going through a PBX, a comma or two for pause lapses may be necessary between the dial-out-number and the rest of the phone number (for example: ATD 9,5551234).
STEP 10: To begin CoreDirector Switch CLI interaction, from the HyperTerminal prompt on the PC, press Enter and type the User Name and Password. The CM CLI Menu is displayed.(Figure 4-36) Note: The CLI Menu display responses in the following procedure are typical and may not exactly match the actual responses. The following steps correspond to the CLI menu shown.
Figure 4-36. CM CLI Menu STEP 11: Type 1 and press Enter to display the current install settings. STEP 12: Type 2 and press Enter to display the general information about the CM. STEP 13: Type 3 and press Enter to display the Upgrade menu. Type 10 and press Enter to return to the CM CLI menu. STEP 14: Type 4 and press Enter to display the Backup and Restore menu. Type 11 and press Enter to return to the CM CLI menu. STEP 15: Type 5 and press Enter to display the Revert menu. Type 5 and press Enter to return to the CM CLI menu. STEP 16: Type 6 and press Enter to change the CLI login user ID. Type 7 and press Enter to change the CLI login password. STEP 17: Type 8 and press Enter to reset the timing plane for firmware upgrade. STEP 18: Type 9 and press Enter to display the Operations Menu. Type 5 and press Enter to return to the CM CLI menu. STEP 19: Type 10 and press Enter to display the Software Configuration Menu. Type 3 and press Enter to return to the CM CLI Menu. STEP 20: Type 11 and press Enter to Change install settings. STEP 21: Type 12 and press Enter to log out of the CM CLI Menu. STEP 22: To end the remote session, type 11 and press Enter to Logout from the CM CLI Menu. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 126
4
TOP 210D COREDIRECTOR SWITCH SOFTWARE UPGRADE AND RESTORE

OVERVIEW
This Task-Oriented Practice describes how to perform a CoreDirector Switch or CoreDirector CI Switch inservice system software upgrade from R2.1.2 or later. Contact Ciena Technical Support to upgrade to R4.0 from releases prior to R2.1.2. This procedure includes a software upgrade preparation checklist, loading the software on the File Transfer Protocol (FTP) server, and upgrading the CoreDirector Network Element (NE) software. Refer to the CoreDirector Node Manager Software Release Document (SRD) or CoreDirector Node Manager User Guide for Node Manager installation instruction.

Caution: This equipment contains devices that are sensitive to Electrostatic Discharge (ESD). Wear grounding straps when handling equipment, and follow approved ESD procedures.

This procedure may affect traffic if the user attempts to restore to a previous database configuration. Perform this procedure during a planned maintenance window. This instruction is intended as a general guide only, has not been tested for all possible applications or configurations, and may not be complete or accurate for some situations. Software release 4.0 includes enhanced diagnostics which may detect failures not visible in previous releases. Refer to the R4.0 Alarm and Trouble Clearing Procedure Manual if any Replaceable Unit Problem alarms are present after the upgrade. Refer to the applicable CoreDirector LWOS Software Release Document for any installation upgrade issues (Section 9.1). The CLI Menu display responses in the following procedures are typical and may not exactly match the actual responses encountered.
Caution:
Note:
REQUIRED TOOLS
!
Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP with the following software available: Ciena CoreDirector Node Manager software that corresponds to the currently installed CoreDirector software release Ciena CoreDirector Node Manager software that corresponds to the CoreDirector software upgrade release HyperTerminal application or equivalent FTP server application or equivalent (such as wftpd32.exe or equivalent) The wftp FTP software is available at http://www.texis.com.
! !

4 - 127
4
! ! !
CoreDirector Switch
Common hand tools 10base-T, RJ-45 crossover cable One or both of the following cables: 9-pin to 25-pin RS-232 serial cable (DB-9F to DB-25M straight cable) for connection to the CM. The 9-pin connector is configured for Data Terminal Equipment (DTE), and the 25-pin connector is configured for Data Communications Equipment (DCE). 9-pin to 9-pin RS-232 serial cable (DB-9F to DB-9F null modem cable) for connection to the backplane I/O panel. Both connectors are configured for DTE.
Spare CM. Ciena highly suggests that customers have a dedicated spare CM on each site with the most updated software release and database version. This CM should be synchronized before the upgrade and again after the upgrade.
PREREQUISITES
The ability to perform configuration changes/deletion in existing object names that use invalid special characters may be lost after a software upgrade. If the user is certain that only valid special characters, as defined by Ciena, were used for object names in the existing software releases, proceed with instructions in this document. If the user has used invalid special characters or is not certain that valid characters were used, the user should stop this procedure and contact Ciena tech support before proceeding further. A list of valid special characters can be found in the Software Release Document (SRD) for each software release.
Note:
! !
The user must be familiar with CoreDirector Node Manager software. The user must be familiar with CoreDirector Switch software and must have Account Administrator privileges. The user must be a registered system user with a valid user name and password to log in to the Command Line Interface (CLI). Log the CM telnet connection session for all of the upgrade duration. The user must use proper module handling procedures. When handling, installing, or removing modules, the following precautions must be observed. Refer to TOP 278D Handling Circuit Packs Properly. Ensure modules are stored in ESD-protective packaging when not installed in an equipment shelf. Do not stack modules on or against each other. Pick up modules by the front handle, and do not touch components on the circuit board.
The following prerequisites are required when the procedure is performed at the NE.
!
CONFIGURATION INFORMATION
CLI command menus shown in this document reflect CoreDirector Switch Software Release 4.0.
REFERENCE DOCUMENTS
! ! ! ! !
TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface TOP 208D Configuration Database Backup and Restore TOP 211D Software In-Service Reversion TOP 271D Resetting the Secondary Control Module (CM) Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 128
4
CoreDirector Switch
! !
TOP 278D Handling Circuit Packs Properly TOP 279D Prepare Site Terminal (or Laptop) for Software Transfer
PROCEDURE

Caution: This procedure is only to be used to upgrade from R2.1.2 or later to R4.0. Contact Ciena Technical Support to upgrade to R4.0 from releases prior to R2.1.2.
The software upgrade procedure consists of the following tasks:

! ! ! ! ! !
Prepare for Software Upgrade Load Software on FTP Server Copy and Save Current Installation Settings Back Up CoreDirector Database Upgrade CoreDirector NE Software Launch Node Manager Session Note: Do not "upgrade" to an earlier release. Refer to TOP 211D Software In-Service Reversion to restore a CoreDirector Switch to the previous software release.
Before upgrading software on a node: Before beginning any procedure, back up CoreDirector Switch databases that are scheduled for upgrade (refer to TOP 208D Configuration Database Backup and Restore). The database backup is performed to save the current database information in case a reversion to the original NE software is necessary.
Note:
! !
Log off all Node Manager user sessions. If using the Switching Network Manager application, unmanage and then re-manage the CoreDirector Switch using the Network Map, or otherwise ensure proper synchronization between the Switching Network Manager and the CoreDirector Switch. Coordinate this maintenance action with the appropriate operations center personnel. Set up an FTP server with a user defined to use the following parameters (refer to TOP 279D Prepare Site Terminal (or Laptop) for Software Transfer for additional information): User name = upgrade Password = upgrade The user will require read and list subdirectory rights.
! !

4 - 129
4
Prepare for Software Upgrade Note: Step 1 through Step 26 can be performed anytime prior to the upgrade procedure and are not required to be conducted during the maintenance window.
CoreDirector Switch
Prior to the software upgrade, the user must perform Step 1 through Step 26 to health check the current database. The checklist is provided to ensure that the software upgrade goes smoothly and is successful. The user should take the necessary actions to remove any inconsistencies identified by the checklist. Note: The check list also provides optional activities that can be performed to highlight areas of concern or draw attention to the current network configuration and overall status.
This checklist can be performed outside of the maintenance window at user convenience prior to the upgrade using Node Manager. Upon completion of the checklist, if any database inconsistencies have been detected, the user must remove them prior to performing the software upgrade. This ensures that certain risks are avoided and that the upgrade will succeed. STEP 1: Establish a Node Manager session with the CoreDirector Switch in accordance with TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface and record results of the following steps in Table 4-20 on page 135. STEP 2: From Inventory, verify the NE equipment configuration status state and Ext. Model ID for circuit packs installed as follows: Circuit packs include Control Modules (CMs), Timing Modules (TMs), and Line Modules (LMs). If circuit pack is present (that is, installed), verify that Ext. Model ID information contains the appropriate module information and is not empty. Note: If the Ext. Model ID information is blank or contains an unsupported value, replace the module prior to the upgrade or a Replaceable Unit Type Mismatch alarm will be raised after the upgrade completes.
If a circuit pack is present (that is, installed), verify that the Hardware Revision complies with the revisions listed in the applicable R4.0 SRD. If a circuit pack is present (that is, installed), verify that Status section information displays: ARC State is Alarm Reporting Administrative State is Unlocked. Operational State is Enabled. Alarm Status is No Alarm. Note: If a circuit pack is installed but has Administrative State of Locked and/or ARC State is No Alarm Reporting, verify that alarms are meant to be suppressed and not reported. In addition, verify that the corresponding TTP is Locked as well.
STEP 3: From Inventory, verify the NE equipment configuration status state for every circuit pack not installed as follows: If circuit pack is not present (that is, not installed), verify that Status section information displays: Administrative State as Locked Operational State as Disabled Alarm Status as No Alarm Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 130
4
Verify that the circuit pack Delete button is not bold. If the button is bold, click Delete to properly remove the circuit pack from inventory. If upgrading from R3.0.0 to a later release, administratively unlock LMs and TMs that are HIR and verify that the relevant Replaceable Unit Problem (RUP) alarm posts. If a circuit pack has Prepare to Unseat Card state selected, the module has been placed in HIR and the Availability Status is Failed. The circuit pack requires replacement or must be removed from the NE, removed from any protection group or Test Access Port (TAP) associations, then deleted.
Note:
STEP 4: Verify that Clock Source configuration is set correctly and operating as expected. Ensure that both the clock source and clocking provided are up and clear of any errors (not toggling up and down). Ensure that BITS clock sources are operational as expected and that expected clock quality is detected. Correct any failures (refer to Failure Reasons section under Timing Configure tab or alarms for additional information). Ensure that Line Timing references are up and that no errors are being reported (that is, SD errors). Take the appropriate action necessary to correct any discrepancies. Verify that any E1 External clock source (CAS or CCS) has not configured the Encoding as AMI. This is particularly important when upgrading to R4.0 or later because AMI encoding is not supported in R3.0.0 and later releases. The risk is that both references will not be requalified after the upgrade and will stay in LOF. If both references are AMI-encoded, change at least one reference to HDB3 before upgrading or change the NE timing to line timing.
Note:
STEP 5: Clear all outstanding alarms being reported by the system.

Caution: Software Release 4.0 includes enhanced diagnostics that may detect failures not visible in R2.1 or earlier. Refer to the R4.0 Alarm and Trouble Clearing Procedure Manual if any Replaceable Unit Problem alarms are present after the upgrade.
STEP 6: Verify the Physical Termination Point (PTP) Status state for all optical interface modules or ports to verify operational state and to ensure that the laser is enabled or disabled correctly. Note: Actions to correct the discrepancy are optional and will not affect the software upgrade, but are provided for normal maintenance notification.
PTP is in a working state if Status section information displays: Admin State as Unlocked Operational State as Enabled If the port or module is Unlocked and Disabled, take the necessary actions to correct the problem to return Operational State to Enabled or lock the PTP. Example: Near-End has port state of Locked and Enabled, but Far-End has port state of Unlocked and Disabled. Need to Either change Far-End port Admin State to Locked to clear alarm, which changes Operational State to Enabled, or Unlock port on the Near-End to clear Far-End port alarm.
Note:

4 - 131
4
PTP is in a nonoperational state if the Status section information displays: Admin State as Locked Operational State as Disabled Note which ports are Drop side ports. Disable LAP-D on these ports if not already disabled. STEP 7: Verify the LM state for all LMs associated in LM 1+1 Configurations to ensure that they are all Unlocked and Not Failed. If an LM is found to be in different state, verify that the appropriate action is taken to return the module to a Unlocked and Operational state by replacing module if required, or take it out of Hold In Reset (Prepare to Unseat Card state) or remove it and delete it as well as all its database associations (its optical ports or modules from APS groups and LM 1+1 Configuration associations) as appropriate. (Refer to FSB 009-2003-322 for additional information.) If the module cannot be deleted, insert a spare module until the software upgrade is completed. The spare module can be removed after completion of software upgrade. Initiating a software upgrade with an incorrect LM configuration (missing module) will impact the success of the upgrade and may result in the rollback to the previous release software and, in the worst case, to both CMs control plane failure.
Note:
STEP 8: Verify the state of each Automatic Protection Switch (APS) Group and ensure that the state of each APS group is as expected. Ensure that both working and protect lines are available (optional). While the state of the associated working and protect lines do not directly affect the software upgrade, it was identified to address the traffic risk associated if a line failure should occur during the upgrade that is carrying traffic and no alternative lines are available for protection or mesh restoration.
Note:
STEP 9: Verify the state of each Virtual Line Switch Ring (VLSR)/Unidirectional Path Switched Ring (UPSR) Group and ensure that the VLSR/UPSR group state is as expected. Ensure that both working and protect lines are available (optional). While the state of the associated working and protect lines do not directly affect the software upgrade, it was identified to address the associated traffic risk if a line failure should occur during the upgrade that is carrying traffic and no alternative lines are available for protection or mesh restoration.
Note:
STEP 10: Record all Subnetwork Connections (SNCs) that have the Admin State of Locked. If possible, record the home and current routes of all working and locked SNCs to verify that they are functioning as expected so that the necessary actions can be corrected or documentation changed as necessary (optional). STEP 11: Verify that the status of all local OSRP links have Hello State of Two-Way Inside with the exception of protect and drop lines. Determine reason for difference and take the necessary corrective actions as required to change Hello State (that is, Admin State may be Locked). TwoWay Inside Hello State is necessary for the NE to advertise available bandwidth for network usage. For example, if port on Far-End is experiencing a failure, an LOS port alarm and Unknown Hello State is normal. STEP 12: Verify that all cross-connects (XCONs) have the Operational State of Enabled. Record all Disabled XCONs (optional).
4 - 132
4
STEP 13: Verify that all software loopbacks are disabled or record which ports have a loopback enabled (optional). Loopbacks are normally used for maintenance or troubleshooting activities only. STEP 14: Use CLI to verify that the available memory on the primary and secondary CMs is higher than 20 percent. a. Establish a serial connection or Telnet session to the appropriate CM. b. Log on using the appropriate user name and password. Note: The default user name is superuser and the default password superuser1!.
c. From the CM CLI Menu, select the option to Display general information about this CM and press Enter. CM general information is displayed as shown in the following typical example:
Current Role..........................Primary Current CM Instance...................CM0 Current Software Version..............4.0.x cnxxxxxx Current Software build timestamp......12/06/2003 08:35:29 Current Software build name...........R4.0_xxxxxx-4.0.x_txn Current Software change number........xxxxxx Current TXN Brand (System ID).........T0035927 Current time stamp on this CM ........06/24/2003 14:00:27 Available memory on this CM ..........177684668 / 230232480
%77
Memory usage per block size. Format: Size/#Reserved/#InUse: 84/14880/34469; 92/4646/28609; 108/23256/45305; 140/17686/35179; 204/345/6315; 332/225/3039; 588/684/236; 1100/871/349; 2124/59/69; 4172/27/37; 8268/16/32; 16460/29/87; 32844/2/42
d. Note the Current Role as either Primary or Secondary. Primary indicates current In-Service CM and secondary indicates Standby CM. e. Note Available memory on this CM. Ensure that the percentage of total available memory is higher than 20 percent. Also, the total memory capacity available on the CM is approximately 230 MB (this number may vary depending on the number of objects on the NE). If the available memory percentage is low or total memory differs, contact Ciena Technical Support for further assistance. STEP 15: Use CLI to determine if the secondary CM is fully synchronized with the primary CM. a. Establish a serial connection or Telnet session to the secondary CM. b. Log on using the appropriate user name and password. Note: The default user name is superuser and the default password superuser1!.
c. From the CM CLI Menu, select the option to Display general information about this CM and press Enter. d. Note Current Role and verify Secondary (DB up to date) message is displayed. e. If Current Role displays Primary, repeat on the other CM. f. If Current Role does not display (DB up to date), wait the appropriate time and periodicially check if synchronization has completed. Note: Synchronization time can take from 30 minutes to a few hours depending on database size or CoreDirector activity.
If an hour has passed and the CM has not completed synchronization, contact Ciena Technical Support for assistance to verify CM synchronization progress.

4 - 133
4
If a forced synchronization is required to reset the secondary CM in accordance with TOP 271D, Resetting the Secondary Control Module, the synchronization process time frame is restarted. Wait for the following message to be displayed on the HyperTerminal or serial connection only:
Ps2 secondary publishing availability = 1
This indicates that the secondary CM is now fully synchronized with the primary CM. STEP 16: Verify that invalid special characters (Table 4-18) are not used in the existing database configuration. Depending upon the existing and the target software release, the valid character lists may differ. Always refer to the appropriate SRD for additional information. For example, the use of white spaces (that is, blanks) differs between releases (Table 4-19). Make the necessary changes as applicable. Table 4-18. Invalid Special Characters/Characters to Avoid Character \ (backslash / (forward slash) & (ampersand) (double quote) < (less than) > (greater than) (single quote) . (period) , (comma - not supported in objects created using TL1) | (pipe) (spaces, white spaces or blanks) * (asterisk) N N N N N N N Y Y Y Y Y Supported Recommended NA NA NA NA NA NA NA N N N N N N N
? (question mark - not supported in objects created using Y TL1) : (colon - not supported in objects created using TL1) Y
Table 4-19. Handling Spaces by Release Release Pre R2.1.0 R2.1.0 - R2.1.3 Behavior Description Leading/trailing/in-between white spaces were admitted into the system as is. Leading/trailing spaces were allowed and stripped off. In-between white spaces are considered legal.
R2.1.4 and higher Leading/trailing spaces are not allowed. In-between white spaces are still allowed.
4 - 134
4
STEP 17: Periodically ensure that the spare CMs have been synchronized so that they have the most current NE software release and database on them. Spare synchronization can be performed anytime prior to the upgrade or after an upgrade. This is to ensure that a backup spare CM is always available.

Caution: Software reinstall and database restore options are available only to the same software release that the CM is currently running.
a. Remove existing secondary CM in accordance to TOP 170D, Removing and Installing a Control Module, and place in ESD antistatic bag. Insert spare CM and allow spare CM to synchronize with the primary CM. Note: Synchronization time can take from 30 minutes to a few hours depending on the database size or the CoreDirector activity.
b. Verify that new secondary CM has completed synchronization using CLI and look for DB up to date message or wait for the Ps2 secondary publishing availability = 1 to be displayed on a HyperTerminal session to the CM. STEP 18: Ciena highly recommends that a static IP route be temporarily created for the TMs and LMs if available. This will greatly assist Ciena Technical Support to identify and isolate the root cause of any issue that may occur during the software upgrade. The static route can be removed after the software upgrade is successfully completed. STEP 19: Complete the checklist in Table 4-20. Table 4-20. Software Upgrade Preparation Checklist Step Number Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 Step 14 Step 15 Step 16 Step 17 Step 18 Description Inventory Configuration Inventory Configuration Clocking Configuration Alarms TTP State LM State and Associations APS Groups VLSR/UPSR Groups Locked SNCs OSRP Link State XCON State Software Loopbacks Available Memory Check Secondary Database Synchronization Invalid Special Characters Synchronize Spare CMs Static Route for LMs and TMs User Signature

4 - 135
4
STEP 20: When the checklist has been completed, schedule a maintenance window to upgrade the NE. Load Software on FTP Server STEP 21: Copy the CoreDirector software upgrade file to the laptop computer or an FTP server.

Caution: Incorrect software load for the CoreDirector Switch product type may result in a catastrophic failure. There is a difference between the CoreDirector Switch and the CoreDirector CI Switch load. Ensure that the correct software load is copied to the FTP server and downloaded to the appropriate equipment.
STEP 22: If loading software onto a CoreDirector Switch, copy module files R4.0_xxxxxx-Release 4.0_txn_cd.lnt into the Software Release directory (example- \ftproot). If loading software onto a CoreDirector CI Switch, copy module files R4.0_xxxxxx-Release 4.0_txn_ci.lnt from the CD-ROM into the Software Release directory (example- \ftproot). STEP 23: Start the FTP Server application (wftpd32.exe) or equivalent. Copy and Save Current Installation Settings STEP 24: At the HyperTerminal or Telnet session to the primary CM, press Enter and log on to the CoreDirector CM CLI using the appropriate user name and password. The default user name is superuser and the default password superuser1!. Ciena recommends establishing connections to both CMs during the upgrade and ensuring that both sessions are being logged. If something unexpected happens during the upgrade process, Ciena Technical Support will look at the logged information.
Note:
The CoreDirector CM CLI menu is displayed. STEP 25: From the CoreDirector CM CLI Menu, type the option number to Display the current install settings and press Enter. Note: Document the CoreDirector Switch settings before proceeding to the next step. Copying and pasting the settings using Microsoft Word, Notepad, or another similar program is recommended.
Back Up CoreDirector Database Back up the CoreDirector database files before performing the upgrade. The database backup is performed to save the current database information in case a reversion to the original NE software is necessary. If the upgrade is performed from the CSM Software workstation, refer to the ON-Center Switching Manager (CSM) Software documentation and perform the Backup on Demand (Manual) procedure.
Note:
STEP 26: Back up the CoreDirector database files (refer to TOP 208D Configuration Database Backup and Restore). The CoreDirector database files can only be backed up from the primary CM. Upgrade CoreDirector NE Software STEP 27: From the CM CLI Menu, type the option number to Enter Upgrade mode and press Enter. The Upgrade Menu is displayed. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 136
4
STEP 28: From the Upgrade Menu, type the option number to Download and process a new load and press Enter. The Transfer Software Load menu is displayed. If too many software loads are already on the CM, CLI returns the following warning:
Too many versions loaded, please delete a version!
Note:
Type the menu option to List the available versions, and press Enter and note the version to delete. Type the menu option to Select a version to delete and press Enter then enter the noted version and press Enter. Type the menu option to Delete selected version and press Enter.
STEP 29: From the Transfer Software Load Menu, type the option number to Specify the IP Address of the FTP site and press Enter. The FTP site may be a PC or laptop. STEP 30: Type the IP Address of the Element Management System (EMS) server, laptop, or PC that contains the software to be transferred (for example, 10.5.55.29) and press Enter STEP 31: Type the option number to List all load archives available at this site and press Enter. A list of software loads currently available on the File Transfer FTP site entered in Step 30 is displayed (for example, R4.0_xxxxxx-4.0.1_txn_cd.lnt). If list cannot be obtained, check FTP server setup. The FTP server should have a user already set up as described in TOP 279D Prepare Site Terminal (or Laptop) for Software Transfer.
Note:
STEP 32: Type the option number to Set the load archive name and press Enter. Type the name of the load to transfer (obtained from list in Step 31) and press Enter (for example, R4.0_1699724.0.1_txn_cd.lnt). Type the load name as displayed, observing capital letters only where specified. STEP 33: Type the option number to Display above settings and press Enter. The software load and server names are displayed (for example, R4.0_xxxxxx-4.0.1_txn_cd.lnt and 10.5.55.39, respectively). STEP 34: Verify that the displayed information is correct. If modifications are needed, repeat Step 29 through Step 33. STEP 35: Type the option number to Transfer load archive and press Enter. The following message is displayed:
Commencing transfer...please standby...
STEP 36: After approximately two minutes, the following message is displayed if the transfer was successful:
Load transferred successfully!
STEP 37: Type the option number to Unarchive and validate load archive and press Enter. The following message is displayed:
Commencing unarchive and validate...please standby...
After approximately three or four minutes, the following message is displayed:

Load Unarchived and validated!
STEP 38: Type the option number to Delete load archive and press Enter. The following typical message is displayed: Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 137
4
Archive (e.g.: R2.1_xxxxx-2.1.5_txn_cd.lnt) deleted
STEP 39: Type the option number to Return to Upgrade menu and press Enter. The Upgrade menu is displayed. STEP 40: From the Upgrade Menu, type the option number to List available software versions and press Enter. The available software versions are displayed as shown in the following example:
Currently available software versions: 2.1.5 3.0.2
This information will be used in Step 42. At this point, the CoreDirector Switch has downloaded the new code but has not activated it. The preceding steps have not committed a code upgrade to the CoreDirector Switch. If a database backup has not been performed, do so now. The following steps are the actual acceptance and usage of the new code. If there is a catastrophic failure on the CMs, refer to TOP 211D Software In-Service Reversion to restore the CoreDirector Switch to its previous database state.
Note:
STEP 41: Type the option number to Select version to upgrade to and press Enter. The following message is displayed:
RECOMMEND: Database should be backed up before performing an upgrade! Enter version for upgrade:
STEP 42: Type the version for upgrade and press Enter. (This information was obtained in Step 40) STEP 43: Type the option number to Start upgrade and press Enter. The following message is displayed:
Upgrade started!
STEP 44: Type the option number to Invoke upgrade program and press Enter. The following upgrade program message is displayed:
Invoking Upgrade Program. Please standby for result...
STEP 45: After approximately three minutes, observe that the following message is displayed after the upgrade program completes:
Upgrade Program done!
Note:
Up to this point, it is possible to back out of the procedure. Performing Step 46 initiates the switchover to the new software and is the point of no return. If the upgrade should fail, immediately contact Ciena Technical Support.
STEP 46: Type the option number to Switch to the upgrade and press Enter. The following message is displayed:
Setting boot image path to: (e.g.: /pack/4.0.x/CM_sym.zelf); This CM will now reboot...please standby...
4 - 138
4
Do not remove the CM during this procedure. The primary CM undergoing upgrade is programmed to become primary in the event that the process is interrupted. If the CM is removed, reinstalled in another CoreDirector Switch, or reinstalled in the same CoreDirector Switch at a later date, the CM takes control and continues the upgrade. Contact Ciena Technical Support if the CM is removed during the upgrade procedure. The CM boot process can take 30 minutes to several hours depending upon database size and CoreDirector activity. Contact Ciena Technical Support if the secondary CM database does not synchronize with the primary CM.
Caution:
Note:
Observe both CM HyperTerminal sessions and ensure that both HyperTerminal sessions are being logged. If something unexpected happens during the upgrade process, Ciena Technical Support will look at the logged information. Note: Then Node Manager software can be installed on the site PC or laptop during the CM boot process.
As the Primary CM reboots, the Secondary CM will assume the Primary CM functions. If there is a catastrophic failure on the primary CM (the one that has just accepted the new code), the CM that is now the current Primary will remain as the Primary CM and will reformat and reload the current revision of code and database onto the failed or replaced CM. The following alarms will be displayed
!
Bay Alarms: Appropriate Shelf LED for primary CM and Major alarm LED on Power Display Panel (PDP) lit Primary CM red FAIL and yellow MAINT LEDs (as the CM starts to reboot) lit Primary CM red FAIL and yellow MAINT flashing
Management Alarms: Major Replaceable Unit Problem for CM Alarm bubble in Inventory tab for shelf and CM
As the Primary CM completes its reboot with the new software, the Primary CM resets the Secondary CM, the LMs, and the TMs. If there is a catastrophic failure on both the primary and secondary CMs, the CoreDirector Switch is in free-run, meaning that both CMs are offline and the CoreDirector Switch CMs will lose connectivity to Node Manager or equivalent. Indications of this failure are that the CMs reboot continuously; continuous reboot messages are displayed at the HyperTerminal sessions. If this occurs, the CoreDirector Switch will be operational and traffic will not be affected. In case of this failure, please refer to TOP 211D Software In-Service Reversion. The following alarms will be displayed:
!
Bay Alarms: Shelf A, B, C LEDs lit LM LEDs red, then yellow or green, depending on TM LEDs red and yellow flashing, then red with yellow, then green Shelf B alarm cleared Secondary CM red FAIL and yellow MAINT LEDs (as the CM starts to reboot)

4 - 139
4
Secondary CM red FAIL and yellow MAINT flashing The Secondary CM will reboot a total of three times to change its boot settings, to load the new code, and to synchronize with the Primary database. The following alarms will be displayed
!
CoreDirector Switch
Bay Alarms: Appropriate Shelf LED lit until the secondary CM finishes rebooting
On the Secondary CM Terminal HyperTerminal session, the message Ps2 secondary publishing availability = 1 indicates that the CoreDirector Switch Secondary CM has completed the synchronization process with the Primary and is ready. If a failure occurs to the secondary other than hardware (does not complete its upgrade procedures), please contact Ciena Technical Support for assistance in changing the boot parameters. Line Modules and Timing Modules automatically reboot after the CM reboot completes. After a CoreDirector Switch software upgrade is completed, the CoreDirector Switch must be unmanaged and then re-managed using the Network Map or CoreDirector Summary windows of the CSM Software application. This ensures a proper synchronization between the CSM Software and the CoreDirector Switch.
Note:
Launch Node Manager Session STEP 47: Launch the corresponding version of Node Manger and log in. Note: The Node Manger code version and the CoreDirector Switch software release code version must match.
STEP 48: Ensure that the software version on all circuit packs reflects the new software version. If any circuit packs display the old software version, contact Ciena Technical Support and refer to TOP 211D, Software In-Service Reversion to perform the in-service reversion procedure. Do not go to Step 49. If all circuit packs reflect the new software version, go to Step 49. STEP 49: Verify that Serial #, Card Type, CLEI, Asmb. Part #, Mfg. Date, Model ID, Ext. Model ID, and ECI fields contain the appropriate information. If the fields are empty or do not contain the appropriate information, contact Ciena Technical Support. STEP 50: Verify that all settings are correct and that the alarms are as expected (TL1, Node Manager Alarm Summary, Node Manager equipment tree, CM/TM/LM/SM Operational States and PDP).
4 - 140
4
Software Release 4.0 includes enhanced diagnostics that may detect failures not visible in earlier releases. Refer to the R4.0 Alarm and Trouble Clearing Procedure Manual if any Replaceable Unit Problem alarms are present after the upgrade. Prior to enabling the O-UNI feature, ensure that the entire network is upgraded to R3.0 or later. If a user cannot log on, he should contact an Account Administrator to change the user account password. After logging in to Node Manager, if there is a TGS Firmware Mismatch warning for both TMs, perform Step 51 through Step 60. Otherwise, no action is required and the software upgrade is complete. --STOP-THIS CONCLUDES THE PROCEDURE Clear TGS Firmware Mismatch Note: Before the TGS firmware is upgraded, there should be at least one good timing reference available to the TM; otherwise, the upgrade will not complete.
Caution:
Note:
Note:
STEP 51: At the primary CM HyperTerminal or Telnet session, press Enter and log on to the CoreDirector CM CLI using the appropriate user name and password. The CoreDirector CM CLI menu is displayed. STEP 52: At the CM CLI Menu, type the option number to Reset Timing Plane for Firmware Upgrade and press Enter. At this point the TM Firmware upgrade process will proceed for each TM in an alarm state. Only one TM will upgrade at a time. STEP 53: Wait 20 minutes for the secondary TM TGS Firmware Mismatch and Clock Mode Not Normal alarms to clear. If the alarms clear, go to Step 57. The TGS Firmware Mismatch Alarm will clear after 5 minutes, but the CM must wait for the timing reference to stabilize, which can take 15 minutes. If a failure occurs, it is usually because the TM failed to find a stable timing reference in the allotted time.
Note:
STEP 54: If the alarm does not clear, contact the next level of support. Ensure that a stable timing reference is available and, if required, replace the secondary TM in accordance with TOP 174D, Removing and Installing a Timing Module.

Caution: Ensure that a stable timing reference is available and that the replaced secondary TM is operational before clearing the primary TM TGS Firmware mismatch alarm.

4 - 141
4
Note: After the TM is replaced, the new TGS firmware is automatically loaded because of the power on reset. Wait for the secondary Clock Mode Not Normal alarm to clear before proceeding to Step 55 to upgrade the primary TM TGS firmware.
STEP 55: If required, at the primary CM HyperTerminal or Telnet session, press Enter and log on to the CoreDirector CM CLI using the appropriate user name and password. The CoreDirector CM CLI menu is displayed. STEP 56: At the CM CLI Menu, type the option number to Reset Timing Plane for Firmware Upgrade and press Enter. At this point, the TM Firmware upgrade process will proceed for the primary TM. STEP 57: Wait 5 minutes for the primary TM TGS Firmware Mismatch to clear. STEP 58: If the alarm does not clear, contact the next level of support and replace the primary TM in accordance with TOP 174D, Removing and Installing a Timing Module. STEP 59: Type the option number to Logout and press Enter. The UserID: prompt appears. STEP 60: Close the Telnet window. Note: Any Clock Mode Not Normal alarms should clear within 15 minutes. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 142
4
TOP 211D SOFTWARE IN-SERVICE REVERSION

OVERVIEW
The software reversion feature is available on Software Releases 2.1.0 and higher. This Task-Oriented Practice describes how to perform a CoreDirector Switch or CoreDirector CI Switch in-service software reversion from a ON-Center Switching Manager (CSM) Software workstation or on equipment at the CoreDirector Switch. This procedure is only applicable on CoreDirector Switches running software releases 2.1.0 and higher.

Changes to the current database are lost when a different database is installed. Existing connections may be rerouted because of differences between the current database and the database associated with the selected software version. Software reversion must be performed from the primary CM. If a CM switch occurs during the reversion, a warning message is displayed and additional steps must be performed. Refer to Step 14. Use this procedure only to revert to R2.1.0 or later. Contact Ciena technical support to revert to software releases prior to R2.1.0. After reverting to an earlier version of the system software, it is necessary to install a version of Node Manager that is compatible with the reverted software load. The TM firmware image is not automatically reverted during the software reversion. When the TM firmware is different between the software images, the TGS Firmware Mismatch warning is asserted. Refer to the Alarm and Trouble Clearing Procedure Manual for the procedure to clear the TGS Firmware Mismatch.
Caution:
Note:
REQUIRED TOOLS
!
Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP with the following software available: CoreDirector Node Manager software that corresponds to the CoreDirector Switch software release HyperTerminal application or equivalent
! ! ! ! !
ESD-guard wrist strap ESD-guard heel grounders Common hand tools 10base-T, RJ-45 crossover cable One or both of the following cables: 9-pin to 25-pin RS-232 serial cable (DB-9F to DB-25M straight cable) for connection to the CM. The 9-pin connector is configured for Data Terminal Equipment (DTE), and the 25-pin connector is configured for Data Communications Equipment (DCE). 9-pin to 9-pin RS-232 serial cable (DB-9F to DB-9F null modem cable) for connection to the backplane I/O panel. Both connectors are configured for DTE.

4 - 143
4
Task Oriented Practices (TOPS) PREREQUISITES
! !
CoreDirector Switch
The user must be familiar with CoreDirector Node Manager software. The user must be familiar with CoreDirector Switch software and must have Account Administrator privileges. The user must be a registered system user with a valid user name and password to log in to the Command Line Interface (CLI). Before performing this procedure, the following tasks must be performed: Current CoreDirector Switch alarms must be noted. Resolve all Repeatable Unit alarms prior to performing the upgrade. Ensure all LMs are not Held In Reset (HIR).
The following prerequisites are required when the procedure is performed at the NE.
!
REFERENCE DOCUMENTS
! !
TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch TOP 278D Handling Circuit Packs Properly
PROCEDURE

Caution: Performance of the following procedure may cause a traffic disruption. This instruction is intended as a general guide only, has not been tested for all possible applications or configurations, and may not be complete or accurate for some situations. Ensure that any circuit pack replaceable unit alarms are resolved prior to performing this procedure.
Verify and clear all outstanding alarms prior to performing the in-service reversion. Log off all Node Manager user sessions prior to reinstalling the CoreDirector Switch system software to avoid Interface Definition Language (IDL) version mismatch issues. Note: After a software reversion, the CoreDirector Switch must be unmanaged, then re-managed using the Network Map or NE Summary windows of the Switching Network Manager application. This ensures a proper synchronization between the Switching Network Manager and the CoreDirector Switch. Before reverting software on a node:
! !
Verify and clear all outstanding CoreDirector Switch alarms. Log off all Node Manager user sessions.
4 - 144
4
CoreDirector Switch
!
If using the Switching Network Manager application, unmanage and then re-manage the CoreDirector Switch using the Network Map, or otherwise ensure proper synchronization between the Switching Network Manager and the CoreDirector Switch. Coordinate this maintenance action with the appropriate operations center personnel.
To perform the system software reversion, perform Step 1 through Step 20. To revert to an earlier version of CoreDirector Node Manager software, perform Step 21 through Step 24. Prepare for System Software Reversion STEP 1: Establish a Node Manager session with the CoreDirector Switch. STEP 2: Document and clear the current alarm state as appropriate (TL1, Node Manager Alarm Summary, Node Manager equipment tree, circuit pack operational state, and Power Distribution Panel (PDP)).

Caution: Resolve all Repeatable Unit alarms prior to performing the upgrade. Ensure all LMs are not Held In Reset (HIR).
STEP 3: Ensure all LMs are not Held In Reset (HIR). a. Using Node Manager, click Go > Inventory. b. Select each LM and ensure that the Prepare to Unseat Card check box is clear (the LM is not in HIR state) and Note any LMs that are HIR. If any LM is HIR, go to Step c. If no LMs are HIR, go to Step 4. c. If the LM is HIR, ensure that the LM ARC State is not in the No Alarm Reporting If the LM ARC State is not in the No Alarm Reporting, change the ARC State to Alarm Reporting and click Accept. d. Remove HIR LM(s) and delete HIR LMs from inventory in accordance with the procedures outlined in TOP 173D. e. Repeat Step c and Step d for each LM noted in Step b. STEP 4: Connect to the CoreDirector Switch in one of the following ways:
!
Connect a cable from the Craft port on the primary CM to the laptop computer, and start a HyperTerminal program in accordance with TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch. Connect a cable from the I/O Craft port for the primary CM to the laptop computer, and start a HyperTerminal program in accordance with TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch. From the CSM Software workstation, launch a Telnet session to the CoreDirector Switch virtual Internet Protocol (IP) address from the Windows Start menu, as follows: a. Select Run. b. Type telnet <CoreDirector IP address>. c. Press Enter.
Identify CMs And Synchronization State STEP 5: Using one of the following methods, identify the primary and secondary CM (this information is used in Step 6):

4 - 145
4
!
CoreDirector Switch
At the CoreDirector Switch, observe that the ACTIVE LED on the CM. Flashing indicates Secondary and solid indicates Primary CM. Use the CoreDirector Switch CM CLI Menu as follows: Log on to the CM CLI Menu using the appropriate user name and password. (The default user name is superuser and the default password superuser1!.) From the CM CLI Menu, type 2 to Display general information about this CM and press Enter. Note the current role for this CM Primary or Secondary (DB up to date). Note: Synchronization message - DB up to date message only available in R2.1.0 or later.
From the Node Manager software, do the following: Select Go > Inventory on the menu bar. From the equipment tree, select the desired CM. Check the standby status in the Details frame. Hot Standby indicates the secondary module. In Service indicates the primary module. Note: This information may also be obtained by clicking the Administration icon and selecting System Configuration > IP Addresses. The active CM has a flag next to it.
STEP 6: Ensure the Secondary CM is fully synchronized with the Primary CM either by physically looking at LEDs or by information noted in Step 5. To force synchronization between the Primary and Secondary CMs, perform TOP 271D Resetting the Secondary Control Module (CM). Because the secondary CM is in standby mode, this procedure is low-risk with minimal impact. Secondary CM synchronization can take from 30 minutes to several hours depending upon database size and CoreDirector Switch activity. Contact Ciena Technical Support if the secondary CM database does not synchronize with the primary CM.
Note:
On the HyperTerminal session (serial connection) the following message is displayed after the Secondary CM has completed the reboot process:
Ps2 secondary publishing availability=1
This message indicates that the secondary CM is fully synchronized with the primary CM. Perform System Software Reversion Note: Software reversion must be performed from the primary CM.
STEP 7: At the HyperTerminal or Telnet prompt, access the CM CLI Menu. STEP 8: From the CM CLI Menu, type the option number to Revert to previous version and database and press Enter. The Revert Menu is displayed. STEP 9: From the Revert Menu, type the option number to Display this CM's boot image path and press Enter. The path and boot image file name are displayed. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 146
4
STEP 10: Type the option number to List available versions and press Enter. A list of currently available versions is displayed. Make note of the version to revert to. STEP 11: Type the option number to Select version to revert to and press Enter. A message is displayed warning of the consequences of changing the system software version (Figure 4-37).
************************************************************** *** WARNING! *** REVERTING to a previous version implies **************** all of the following: ************************************************************** a) Database to be applied will be the one USED FOR THE LAST TIME in that version. b) All cards will be control plane rebooted (as in an Upgrade). c) Any provisioned or persisted database changes in the current database that did not exist in the previous database will be LOST. Re-routing of existing connections may happen due to differences between the current database and the one in the version selected. ************************************************************** QUIT this menu now if the points above are unacceptable. **************************************************************
Figure 4-37. Software Reversion Warning Message STEP 12: Press Enter to return to the Revert Menu. STEP 13: To stop the software reversion process, type the option number to Return to CM CLI Menu and press Enter. To continue with the software reversion process, type the option number to Switch to selected version and database and press Enter. The following (typical) messages are displayed:
Setting boot image path to: /pack/FG21_93676/CM_sym.zelf This CM will now reboot...please stand by...
When the CM reboots, remote connections to CLI are terminated. STEP 14: A software reversion is successful only if the operation is attempted on the CM where the last software upgrade was performed; otherwise, as in the case in which there has been a CM switchover since the last upgrade, the software detects and reports the warning message as displayed in Figure 4-38.
********************************************************************** *** WARNING! *** The software version you are trying to revert to has an empty database. After reversion the NE will come up empty. This will result in a loss of traffic. There are two basic choices from this point onwards: a) Continue with reversion on this CM. After the TXN comes up with a factory database, perform a Database Restore of a database obtained while the TXN was in the proper software version. b) Do NOT continue with Revert operation on this CM. It is possible that the other CM has a Database associated to the software version to revert to. To try if this is true, this CM has to be rebooted so that the other one can become Primary and the Revert operation can be requested on it. ********************************************************************** QUIT this menu now if option (a) in unacceptable. **********************************************************************
Figure 4-38. Empty Database Warning Continue the reversion or quit the menu, reset this CM, and restart this procedure at Step 1. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 147
4
Note: In most cases option b is the correct choice because the other CM was likely the one where the last upgrade took place. In this case, reboot this CM (making it the Secondary CM), then restart this procedure at Step 1 or contact Technical Support.
STEP 15: When the reversion of the CoreDirector Switch is successful to a software build of R2.1.0 or later, continue the procedure at Step 21 to install an earlier version of CoreDirector Node Manager software. After the reversion is complete and if the reversion was to a software load prior to R2.1.0, perform Step 16 through Step 19 to delete R4.0.1 from the CM. STEP 16: From the CM CLI Menu, type the option number to Enter Upgrade mode and press Enter. The Upgrade Menu is displayed. STEP 17: From the Upgrade Menu, type the option number to List available versions and press Enter. STEP 18: Type the option number to Select a version to delete and press Enter. STEP 19: Type the option number to Delete selected version and press Enter. STEP 20: After the deletion is complete, proceed to Step 21 to install an earlier version of CoreDirector Node Manager software. Install Earlier Version of CoreDirector Node Manager Software STEP 21: If applicable, back up the existing CoreDirector Node Manager env.TXT file. The existing env.TXT file is overwritten during CoreDirector Node Manager software reversion. Copying or renaming the env.TXT file preserves the login screen default node Universal Resource Locators (URLs). After installing the CoreDirector Node Manager software, the default node URLs can be copied from the old env.TXT file to the reverted env.TXT file. STEP 22: Uninstall the currently installed version of CoreDirector Node Manager. STEP 23: Insert the desired version of the CoreDirector Node Manager Compact Disc Read Only Memory (CD-ROM) into the CD-ROM drive and follow the installation Wizard instructions. STEP 24: If applicable, redefine the default node URLs, as follows: a. Open the old env.TXT file and copy the default node URLs from the hosts= line under the ## Property: HOSTS heading. b. Open the new env.TXT file and paste the default node URLs. STEP 25: Launch the corresponding version of Node Manger and log in. Note: The Node Manger code version and the CoreDirector Switch software release code version must match.
STEP 26: Ensure that the software version on all circuit packs reflects the current software version. If any circuit packs display do not display the current software version, contact Ciena Technical Support.
4 - 148
4
STEP 27: Verify that Serial #, Card Type, CLEI, Asmb. Part #, Mfg. Date, Model ID, Ext. Model ID, and ECI fields contain the appropriate information. If the fields are empty or do not contain the appropriate information, contact Ciena Technical Support. STEP 28: Verify that all settings are correct and that the alarms are as expected (TL1, Node Manager Alarm Summary, Node Manager equipment tree, CM/TM/LM/SM Operational States and PDP). --STOP-THIS CONCLUDES THE PROCEDURE

4 - 149
4
4 - 150
4
TOP 217D COREDIRECTOR SWITCH SHUTDOWN

OVERVIEW
This Task Orientated Practice describes how to perform a CoreDirector Switch or CoreDirector CI Switch emergency shutdown or, if time permits, a planned shutdown in anticipation of maintenance or system removal from a network.
TRAFFIC RISK
This procedure is traffic-affecting.

In the event of an emergency shutdown, all unprotected traffic both to and from the CoreDirector Switch will be disconnected from the network. A planned shutdown is also traffic affecting if it is not properly coordinated with the Network Operations Center (NOC) and if traffic is not rerouted. Do not shut down the CoreDirector Switch during a planned shutdown until given permission from the NOC.
Caution:
REQUIRED TOOLS
Emergency Shutdown ! ESD-guard wrist strap
! ! !
ESD-guard heel grounders Basic hand tools Digital multimeter (DMM)
Planned Shutdown (in addition to tools listed above) ! 10BaseT, RJ-45 Ethernet cable
!
One or both of the following cables: 9-pin to 25-pin RS-232 serial cable (DB-9F to DB-25M straight cable) for connection to the CM. The 9-pin connector is configured for Data Terminal Equipment (DTE), and the 25-pin connector is configured for Data Communications Equipment (DCE). 9-pin to 9-pin RS-232 serial cable (DB-9F to DB-9F null modem cable) for connection to the backplane I/O panel. Both connectors of a null modem cable are configured for DTE.
Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP
PREREQUISITES
Emergency Shutdown ! Experience in the use of a DMM
!
Knowledge of the location of the Battery Distribution Fuse Bay (BDFB) circuit breakers that provide -48 VDC power to the CoreDirector Switch PDU Familiarity with site lockout/tagout procedures
Planned Shutdown (in addition to conditions listed above) ! Craft interface personnel must be registered system users with valid user names and passwords to log into the Command Line Interface (CLI).

4 - 151
4
!
CoreDirector Switch
Craft interface personnel must have knowledge of the use, setup, and configuration of HyperTerminal software. Craft interface personnel must have knowledge of the use, setup, and configuration of FTP software on the FTP server.
REFERENCE DOCUMENTS
! ! ! !
TOP 015D Verifying -48 VDC Supply Voltage TOP 208D Configuration Database Backup and Restore TOP 270D Resetting the Primary Control Module (CM Switch) TOP 271D Resetting the Secondary Control Module (CM)
PROCEDURE

Warning Negative 48 volts DC is present in the equipment. Contact can cause personal injury. Take appropriate safety precautions. Refer to Voltage Precaution in the General Safety Precautions on page page xx.


Caution: Performance of the following step may cause a traffic disruption. This instruction is intended as a general guide only, has not been tested for all possible applications or configurations, and may not be complete or accurate for some situations. A CoreDirector Switch is not to be powered down unless explicit instructions are obtained from the Network Operation Center (NOC).
Note: Emergency Shutdown
STEP 1: Contact Operations Center personnel and ensure that all traffic has been re-routed from the CoreDirector Switch to be powered down. STEP 2: At the front of the PDU, remove the PDU faceplate and set the four circuit breakers to OFF. STEP 3: Open the Battery Distribution Fuse Bay (BDFB) circuit breakers that provide -48 VDC power to PDU and lockout/tagout as DO NOT ENERGIZE. STEP 4: Verify that -48 VDC supply voltage is not present at the PDU power entry points using TOP 015D Verifying -48 VDC Supply Voltage. STEP 5: Replace the PDU faceplate removed in Step 2.
4 - 152
4
CoreDirector Switch
Planned Shutdown STEP 6: Contact the Operations Center and verify the completion of a database backup. If a database backup is not already completed by personnel at the Operations Center, perform a CoreDirector Switch Configuration Database Backup in accordance with TOP 208D Configuration Database Backup and Restore, and report completion to Operations Center personnel. STEP 7: Contact Operations Center personnel and ensure that all traffic has been re-routed from the CoreDirector Switch to be powered down. Step 8 through Step 10 are time critical steps that remove power from the CoreDirector while the secondary and primary CMs are rebooting. Perform Step 9 and Step 10 within three minutes of resetting the secondary CM. If the three minute window is missed, repeat Step 8 through Step 10 so that power is removed from the CoreDirector while the secondary and primary CMs are rebooting.
Note:
STEP 8: Refer to TOP 271D Resetting the Secondary Control Module (CM) and reset the secondary CM. STEP 9: Refer to TOP 270D Resetting the Primary Control Module (CM Switch) and reset the primary CM. STEP 10: At the front of the PDU, remove the PDU faceplate and set the four circuit breakers to OFF. STEP 11: Open the Battery Distribution Fuse Bay (BDFB) circuit breakers that provide -48 VDC power to PDU and lockout/tagout as DO NOT ENERGIZE. STEP 12: Verify that -48 VDC supply voltage is not present at PDU power entry points in accordance with TOP 015D Verifying -48 VDC Supply Voltage. STEP 13: Replace the PDU faceplate removed in Step 10. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 153
4
4 - 154
4
TOP 218D PACK UP A COREDIRECTOR SWITCH SYSTEM

OVERVIEW
This Task-Oriented Practice describes how to pack the CoreDirector Switch or CoreDirector CI ETSI or NA Rack Package in to a Universal shipping container with the caster assemblies installed. The CoreDirector Switch and CoreDirector CI Switch products will hereinafter be referred to as CoreDirector Switch. Unless otherwise specifically stated, the use of CoreDirector Switch reflects both the CoreDirector Switch and the CoreDirector CI Switch.
REQUIRED TOOLS
! !
Common hand tools for packing wooden containers Material handling equipment (for example, a pallet jack or a forklift) Note: The CoreDirector Switch must be packed with the shipping container in an upright position.
PREREQUISITES
!
The user must be familiar with equipment installation.
LIFT WARNING
The equipment is heavy. Unassisted, improper handling, or improper lifting techniques can cause personal injury. Take appropriate safety precautions. A fully loaded CoreDirector Switch can weigh 1000 pounds (454 kilograms) when fully populated and a CoreDirector CI NA or ETSI Rack can weigh 500 pounds (227 kilograms) when fully populated. Three persons are required: two to hold and tilt the cabinet and one to install the casters. Exercise extreme caution when moving the CoreDirector Switch rack. Until it is secured in the crate, the fully loaded rack is very unstable.
Warning:

Caution: This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. The CoreDirector Universal shipping container dimensions are 94 inches by 48 inches by 48 inches (239 cm x 122 cm x 122 cm). A minimum space of 11 feet at the front of the crate is required to crate the CoreDirector Switch safely.
Note:
REFERENCE DOCUMENTS
! !
CoreDirector Hardware Installation Manual NA and ETSI Rack Packages Hardware Installation Manual
PROCEDURE
STEP 1: Attach the caster assemblies to the bottom of the CoreDirector rack, as follows (Figure 4-39):

4 - 155
4
a. At the CoreDirector Switch rack, carefully tilt the rack to one side and install one caster assembly to the opposite side using two 1/2-13 X 1 bolts with washers. b. Carefully tilt the rack on the side with the casters in place and install the other set of casters using two 1/2-13 X 1 bolts with washers.
Caster Assemblies Figure 4-39. CoreDirector Switch Caster Assemblies (Installed)

Caution: This equipment contains devices that are sensitive to Electrostatic Discharge. Ensure that the grounding chains are used to secure the CoreDirector Switch to the Caster Assemblies and touch the ground.
STEP 2: For the CoreDirector CI ETSI Rack, refer to the NA and ETSI Rack Packages Hardware Installation Manual and remove the fiber management panels. STEP 3: Locate the CoreDirector Switch universal shipping container and move it to the CoreDirector Switch packing area. STEP 4: Remove the wood screws securing the twist keys on the latches to the container front. STEP 5: If the shipping container is not in an upright position, raise the shipping container to an upright position. Note: The front panel of the shipping container is used as a ramp to move the rack into the container. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 156
4
STEP 6: Release the latches on the front panel of the shipping container as follows: a. Rotate the twist key into its operational position (that is, perpendicular to the surface of the container panel). Refer to Figure 4-40. b. Turn the twist key counterclockwise to release the locking plate on the latch. c. When the locking plate is clear of the locking pin, pull the latch free of the locking pin. d. Flip the twist key back down against the surface of the container front panel.
184
Close Latch
186
Open Latch
Figure 4-40. Latches on the Shipping Container STEP 7: Tilt the panel down to form a ramp (Figure 4-41). Ensure that the latches are folded out of the way as the ramp comes down to rest on the floor.
187
Ramp
Figure 4-41. Ramp for Unloading the Rack Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 157
4
STEP 8: Inspect the Shockwatch label attached inside the left side panel of the shipping container (Figure 4-42). If the indicator on the label is white, proceed with Step 9. If the indicator on the label is red, replace the Shockwatch label.
Figure 4-42. Shockwatch Label Inside the Shipping Crate STEP 9: Remove the eight wing nuts and flat washers securing the inner brace panel and remove the panel.
Wing Nuts
Figure 4-43. Opening the Inner Brace Panel Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 158
4
STEP 10: At the bottom of the crate, remove nuts, flat washers, and threaded rod securing the wood braces to the floor of the shipping container.
LIFT WARNING
The equipment is heavy. Unassisted, improper handling, or improper lifting techniques can cause personal injury. Take appropriate safety precautions. A fully loaded CoreDirector Switch can weigh 1000 pounds (454 kilograms) when fully populated and a CoreDirector CI NA or ETSI Rack can weigh 500 pounds (227 kilograms) when fully populated. Three persons are required: two to hold and tilt the cabinet and one to install the casters. Exercise extreme caution when moving the CoreDirector Switch rack. Until it is secured in the crate, the fully loaded rack is very unstable.
Warning:
STEP 11: With the CoreDirector rack standing on the floor, add ESD shrink wrap or pink poly to the equipment in accordance with local guidelines. STEP 12: Carefully roll the CoreDirector rack up the ramp and into the shipping container. STEP 13: Ensure that all CoreDirector CI ETSI Rack fiber management panels and/or CoreDirector hardware panels are secured to the inner side panel using velcro strips. STEP 14: At the bottom of the crate, install nuts, flat washers, and threaded rod removed in Step 10. STEP 15: Install the inner brace with the letters ETSI facing out when packing the CoreDirector CI ETSI Rack package or with the letters CD and NA facing out when packing a CoreDirector Switch rack or For the CoreDirector Switch rack and CoreDirector CI NA rack, position the inner brace with the letters CD and NA facing out. For the CoreDirector CI ETSI rack, position the inner brace with the letters ETSI facing out. STEP 16: Secure the inner brace using the eight wing nuts and flat washers removed in Step 9. STEP 17: Tilt the ramp panel up and secure as follows: a. Rotate the twist key to fully open the latch. Refer to Figure 4-40. b. Align the locking plate to the locking pin. c. Turn the twist key clockwise to secure the locking plate to the latch. STEP 18: Flip the twist key back down against the surface of the container front panel. STEP 19: Install the wood screws to secure the latch twist keys removed in Step 4. STEP 20: Complete any paperwork in accordance with local practices and notify the appropriate people that the CoreDirector Rack is ready for shipment. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 159
4
4 - 160
4
TOP 220D TEST LINE MODULES AND OPTICAL MODULES

OVERVIEW
This Task-Oriented Practice describes the optional procedure for testing CoreDirector Switch or CoreDirector CI Switch Line Modules (LMs) and Optical Modules (OMs) or ports using the CoreDirector Node Manager software. It also includes procedures for testing LM-16 integrated OMs. Testing is accomplished by using a combination of diagnostic loops, cross-connects, and fiber jumpers to daisy chain the desired quantity of LMs and OMs together while monitoring a Synchronous Optical Network (SONET) test set to verify a locked, clean signal. This procedure in its entirety should be used only during turn-up and test or on non-traffic carrying systems because this procedure includes optional tests that remove partial power from the CoreDirector Switch. The procedure also removes Control Modules (CMs) and Switch Modules to test all aspects of the LMs and OMs. Do not perform the optional test steps on traffic-carrying systems.
Note:
REQUIRED TOOLS
! ! ! ! !
ESD-guard wrist strap ESD-guard heel grounders Common hand tools 10base-T, RJ-45 crossover cable One or both of the following cables: 9-pin to 25-pin RS-232 serial cable (DB-9F to DB-25M straight cable) for connection to the CM. The 9-pin connector is configured for Data Terminal Equipment (DTE), and the 25-pin connector is configured for Data Communications Equipment (DCE). 9-pin to 9-pin RS-232 serial cable (DB-9F to DB-9F null modem cable) for connection to the backplane I/O panel. Both connectors of a null modem cable are configured for DTE. Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP CoreDirector Node Manager software Insulated screwdrivers (standard flatblade and Phillips) Digital optical test set (for example, Digital Lightwave ASA-PKG-OC48c or equivalent) capable of SONET and/or SDH Bit Error Rate (BER) testing down to the OC-3/12 level, with necessary fiber jumpers (6-foot (2-meter) recommended), FC-to-SC adapters, SC-to-LC adapters, and FC attenuators Optical cleaning kit (containing cleaning sticks authorized to clean LC connectors) and an optical fiber scope Optical power meter equipped with an LC adapter For testing the LM-16e Line Module, an STM1-E test set. LC-to-LC small fiber test jumpers for LM-16 testing (6-inch/15-centimeter recommended). As many as 15 fiber jumpers are needed for testing a single LM-16. (Double this figure for each additional LM-16 that requires testing.) BER testing cannot be performed without the fiber jumpers. SC-to-SC small fiber test jumpers for LM-8 or LM-2 testing (6-inch (15-centimeter) recommended). Eight fiber jumpers are needed for testing a single LM-8. (Double this figure for each additional LM-8 that requires testing.) Two fiber jumpers are needed for testing a single LM2 (double this figure for each additional LM-2 that requires testing). BER testing cannot be performed without the fiber jumpers.
! ! ! !
! ! ! !

4 - 161
4
! ! !
CoreDirector Switch
SC-to-SC couplers (for LM-8/LM-2 testing) SC-to-LC couplers (for LM-16 testing) SC-to-LC adapter cables (for LM-16 testing)
PREREQUISITES
!
! !
The user must be familiar with CoreDirector Node Manager software. The user must have Node Manager Connection Point (CP), Termination Point Provisioner (TP) or Node Manager Troubleshooter (TS) privilege. Before performing this procedure, the following tasks must be performed: Current CoreDirector Switch alarms must be noted.
REFERENCE DOCUMENTS
! ! ! ! ! ! !
Node Manager User Guide, Creating and Deleting Cross Connects TOP 170D Removing and Installing a Control Module TOP 171D Removing and Installing a Switch Module TOP 172D Removing and Installing an Optical Module TOP 173D Removing and Installing a Line Module TOP 174D Removing and Installing a Timing Module TOP 221D Test Optical Module
PROCEDURE
Warning:


Caution: Performance of the following step may cause a traffic disruption. This instruction is intended as a general guide only, has not been tested for all possible applications or configurations, and may not be complete or accurate for some situations. Before starting the test, visually inspect the CoreDirector Switch and verify that no red alarm LEDs are lit. Alarms indications will need to be corrected in order to effectively perform this test. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
Note:
4 - 162
4
To test LM-8 or LM-2 Line Modules and their optical modules, perform Step 1 through Step 54. To test LM-16 Line Modules and their integrated optical ports, perform Step 55 through Step 82. To test LM-16-STM-1E Line Modules and their integrated optical ports, perform Step 83 through Step 86. Test LM-8/LM-2 Optical Modules STEP 1: Establish a Node Manager session with the CoreDirector Switch. STEP 2: Refer to TOP 172D Removing and Installing an Optical Module on page 1-41 and remove the OM. STEP 3: Connect a SONET test to the transmit (identified by an arrow pointing away from the connector) and receive (identified by an arrow pointing toward the connector) FC bulkhead connectors on the OM. STEP 4: Refer to TOP 172D Removing and Installing an Optical Module on page 1-41 and reinstall the OM. STEP 5: Refer to TOP 221D Test Optical Module on page 1-177 to test the OM. STEP 6: Record the results on LM and OM LED Status and Functional Test CoreDirector Test Data Sheets or LM and OM LED Status and Functional Test CoreDirector CI Test Data Sheets. Test Data Sheets are located in Appendix A and Appendix B. STEP 7: Refer to TOP 172D Removing and Installing an Optical Module on page 1-41 and remove the next OM. STEP 8: Connect the transmit to the receive using a fiber optic jumper.

Caution: Ensure that the power levels do not exceed specifications in the following steps when testing OMs and Optical Ports. Damage can result from daisychaining or looping back MR, LR, or WDM OMs. Refer to Table 4-21 for the power ranges for each OM type. Use attenuation as required to ensure that the maximum input levels are not exceeded.
Table 4-21. Optical Output Power Ranges for OMs and Optical Ports Port Type 155/622 MR OM (includes LM-16) 2.5G SR OM 2.5G MR OM 2.5G LR OM (LR-1) 2.5G LR OM (LR-2) 10G SR OM (SR-1) 10G SR OM (SR-2) 10G MR OM (MR-2) 10G LR OM (LR-2) 10G WDM-1 OM 10G WDM-2 OM GbE SX GbE LX Output Power Range -15 dBm to -8 dBm -10 dBm to -3 dBm -5 dBm to 0 dBm -2 dBm to +3 dBm -2 dBm to +3 dBm -6 dBm to -1 dBm -5 dBm to -1 dBm -1 dBm to +2 dBm +2 dBm to +4 dBm +4.1 dBm to +7.0 dBm +4 dBm to +5 dBm -9.5 dBm to -4 dBm -9.5 dBm to -3 dBm Receiver Power Range -28 dBm to -8 dBm -18 dBm to -3 dBm -18 dBm to 0dBm -27 dBm to -9 dBm -28 dBm to -9 dBm -11 dBm to -1 dBm -14 dBm to -1 dBm -27 dBm to -1 dBm -24 dBm to -7 dBm -14.3 dBm to -1.3 dBm -14 dBm to -2 dBm -17 dBm to 0 dBm -20.5 dBm to -3 dBm

4 - 163
4
STEP 9: Refer to Node Manager User Guide, Creating and Deleting Cross Connects and configure a cross connect between the two OMs (Figure 4-44). STEP 10: Verify that the SONET test set configured in Step 3 is locked and error-free. STEP 11: Record the results on LM and OM LED Status and Functional Test CoreDirector Test Data Sheets or LM and OM LED Status and Functional Test CoreDirector CI Test Data Sheets. STEP 12: Remove the jumper installed in Step 8. Refer to TOP 172D Removing and Installing an Optical Module on page 1-41.
LM
Test Set
T R
OM 1
T R
Fiber Optic Jumpers
OM 2
Cross Connect
Figure 4-44. OM Test with Cross Connect STEP 13: Connect that OMs transmit to the receive and the receive to the transmit of the next OM to be tested. Refer to Figure 4-45.

Caution: Ensure that the power levels do not exceed specifications in the following steps when testing OMs and Optical Ports. Damage can result from daisychaining or looping back MR, LR, or WDM OMs. Refer to Table 4-21 on page 163 for the power ranges for each OM type. Use attenuation as required to ensure that the maximum input levels are not exceeded.
LM
R T est S et T
T R
OM 1
T R
OM 2
C ro s s Connect
T R
F ib e r O p tic Ju m p e rs
OM 3
D ia g n o stic L o op b a c k
Figure 4-45. OM Test with Jumpers and Cross Connect
4 - 164
4
STEP 14: Configure a diagnostic loopback on the OM connected in Step 12 in accordance with TOP 221D Test Optical Module on page 1-177. Refer to Figure 4-45 for the test setup. STEP 15: Verify that the SONET test set configured in Step 3 is locked and error-free. STEP 16: Record the results on LM and OM LED Status and Functional Test CoreDirector Test Data Sheets or LM and OM LED Status and Functional Test CoreDirector CI Test Data Sheets.

Caution: Ensure that the power levels do not exceed specifications in the following steps when testing OMs and Optical Ports. Damage can result from daisy chaining or looping back MR, LR, or WDM OMs. Refer to Table 4-21 on page 163 for the power ranges for each OM type. Use attenuation as required to ensure that the maximum input levels are not exceeded.
STEP 17: Continue to connect all desired OMs together for testing using any or all of the processes outlined in Step 3 through Step 15. Refer to Figure 4-46 for an example of an LM with eight OMs. STEP 18: Record the results on LM and OM LED Status and Functional Test CoreDirector Test Data Sheets or LM and OM LED Status and Functional Test CoreDirector CI Test Data Sheets. Note: The number of OMs in each configuration may vary. The setup displayed in Figure 4-46 should be modified to meet the desired configuration. If this test is being performed as part of an initial customer turn-up and test, each unused LM slot in Shelf A and C must be tested to ensure that the CoreDirector Switch backplane is operational. To accomplish this, perform Step 19 through Step 26; otherwise, proceed to Step 27 to continue this test.
Note:
STEP 19: Remove the LM configured in Step 17. STEP 20: Install the LM in the first unused slot to be tested in accordance with TOP 173D Removing and Installing a Line Module. STEP 21: Configure the necessary Physical Termination Points (PTPs), Connection Termination Points (CTPs), cross connects, and diagnostic loopbacks on the OMs in the LM slot to be tested using any or all of the processes in Step 3 through Step 15. STEP 22: Verify that the SONET test set configured in Step 3 is locked and error-free for a period of 15 minutes. Refer to Figure 4-46 for an example of an LM with eight OMs. STEP 23: Record the results on LM and OM LED Status and Functional Test CoreDirector Test Data Sheets or LM and OM LED Status and Functional Test CoreDirector CI Test Data Sheets in the area corresponding with the LM slot that was tested. STEP 24: Delete the PTPs, CTPs, cross connects, and diagnostic loopbacks created in Step 21. STEP 25: Repeat Step 19 through Step 24 for each LM slot until all unused slots have been tested. STEP 26: Reinstall the LM in the original slot in accordance with TOP 173D Removing and Installing a Line Module and repeat Step 17. STEP 27: Continue to connect all desired LMs and OMs together for testing, using any or all of the processes in Step 3 through Step 17. Refer to Figure 4-47 for an example of two LMs with eight OMs.

4 - 165
4
R Test Set T
T R
OM 1
T R
OM 2
T R
OM 3
T R
OM 4
Cross Connect
T R
Fiber Optic Jumpers
OM 5
T R
OM 6
T R
OM 7
T R
OM 8
Figure 4-46. Complete LM Test Setup

a

Caution: Ensure that the power levels do not exceed specifications in the following steps when testing OMs and Optical Ports. Damage can result from daisychaining or looping back MR, LR, or WDM OMs. Refer to Table 4-21 on page 163 for the power ranges for each OM type. Use attenuation as required to ensure that the maximum input levels are not exceeded.
STEP 28: Record the results on LM and OM LED Status and Functional Test CoreDirector Test Data Sheets or LM and OM LED Status and Functional Test CoreDirector CI Test Data Sheets. Note: The following steps are optional and should not be performed on a live, trafficcarrying system.
STEP 29: When the final configuration of LMs and OMs is achieved, verify that the SONET test set configured in Step 3 is locked and error-free. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 166
4
R Test Set T
LM 1
T OM 1 R T OM 2 R T OM 3 R T OM 4 R
Cross Connect
LM "N"
Cross Connect
T OM 5 R
Fiber Optic Jumpers Fiber Optic Jumpers
T OM 6 R T OM 7 R T OM 8 R
Figure 4-47. Two LM Test Setup STEP 30: Place the A BATTERY circuit breaker in the OFF position and verify that the SONET test set has remained locked and error-free. STEP 31: Set the A BATTERY circuit breaker to the ON position and verify that the SONET test set has remained locked and error-free. STEP 32: Record the results on Module LED Status and Redundancy Tests CoreDirector Test Data Sheets or Module LED Status and Redundancy Tests CoreDirector CI Test Data Sheets. STEP 33: Remove the primary Control Module (CM), which is identified by a green ACTIVE LED, from Shelf A (CM A) or Shelf C (CM B) in accordance with TOP 170D Removing and Installing a Control Module. STEP 34: Verify that the SONET test set has remained locked and error-free. Verify that the remaining CM is now the primary CM with a green ACTIVE LED. STEP 35: Reinstall the CM and verify that the SONET test set has remained locked and error-free. STEP 36: Verify that this CM is now the secondary CM, which is identified by a blinking green ACTIVE LED. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 167
4
STEP 37: Record the results on Module LED Status and Redundancy Tests CoreDirector Test Data Sheets or Module LED Status and Redundancy Tests CoreDirector CI Test Data Sheets. STEP 38: Repeat Step 33 for the other CM. STEP 39: Remove the primary Timing Module (TM), which is identified by a green ACTIVE LED, from Shelf B in accordance with TOP 174D Removing and Installing a Timing Module. STEP 40: Verify that the SONET test set has remained locked and error-free. Verify that the remaining TM is now the primary TM with a green ACTIVE LED. STEP 41: Reinstall the TM and verify that the SONET test set has remained locked and error-free. STEP 42: Verify that this TM is now the secondary TM, which is identified by a blinking green ACTIVE LED. STEP 43: Record the results on Module LED Status and Redundancy Tests CoreDirector Test Data Sheets or Module LED Status and Redundancy Tests CoreDirector CI Test Data Sheets. STEP 44: Repeat Step 39 for the second TM in Shelf B. STEP 45: Using the Node Manager Inventory screen, note which Switch Modules (SMs) are standby and which SMs are primary. STEP 46: Remove a primary SM from Shelf B in accordance with TOP 171D Removing and Installing a Switch Module. STEP 47: Verify that the SONET test set has remained locked and error- free. Using the Node Manager Inventory screen, verify that a standby SM is now a primary SM. STEP 48: Reinstall the SM and verify that the SONET test set has remained locked and error- free. STEP 49: Record the results on Module LED Status and Redundancy Tests CoreDirector Test Data Sheets or Module LED Status and Redundancy Tests CoreDirector CI Test Data Sheets. STEP 50: Repeat Step 45 for each additional SM in Shelf B. STEP 51: Allow the final configuration established in Step 29 to run for a minimum of 8 hours or whatever time frame is determined by the customer. STEP 52: Record the results on LM and OM LED Status and Functional Test CoreDirector Test Data Sheets or LM and OM LED Status and Functional Test CoreDirector CI Test Data Sheets. STEP 53: Remove all jumpers and attenuators installed during this test in accordance with TOP 172D Removing and Installing an Optical Module. STEP 54: Complete LM and OM LED Status and Functional Test CoreDirector Test Data Sheets or LM and OM LED Status and Functional Test CoreDirector CI Test Data Sheets. --STOP-THIS CONCLUDES THE PROCEDURE Test LM with Integrated Optical Ports STEP 55: Remove the dust caps from the integrated optical port to be tested, and clean its optical connectors in accordance with Ciena Standard Cleaning & Equipment Safety Practices. STEP 56: Clean fiber test jumpers (6-inch (15-centimeter) recommended) in accordance with Ciena Standard Cleaning & Equipment Safety Practices.
Risk of Damage to LC Connectors

Caution: To prevent damage to the LC connector and/or its attached fiber, be careful when handling the fiber and when inserting the connector into or extracting the connector from an LM integrated optical port.
4 - 168
4
STEP 57: Verify that the LM ports are unlocked. At the site terminal Node Manager Inventory screen, expand the equipment tree to display the installed LM. The Administrative State in the Status field should indicate Unlocked. If an icon for the LM is not displayed in the equipment tree, it indicates that CoreDirector Node Manager doesnt recognize the Line Module. Contact Ciena technical support for assistance. Refer to the copyright page of this document for contact information.
Note:
! !
If the Status field indicates Unlocked, go to Step 58. If the Status field indicates Locked, select Unlocked from the Administrative State drop-down menu and click the Accept button. Go to Step 58. a. Connect the power meter to the transmit side of the optical port.
STEP 58: Measure the output power (dBm) of the optical port using an optical power meter.
Warning:

b. Verify that the optical port is unlocked. Select the optical port to be tested from the equipment tree. At the CoreDirector Node Manager Inventory screen, select the Basic tab. The Administrative State in the Status field should indicate Unlocked. If the Status field indicates Unlocked, continue with the next step. If the Status field indicates Locked, select Unlocked from the Administrative State dropdown menu and click the Accept button. Then continue with the next step. c. Verify that the results of the optical power test, made on the optical port are within the acceptable range identified in Table 4-21. If required, record the test results in Table 4-22. Table 4-22. Optical Power Level Data Sheet Optical Port ID OP1 OP2 OP3 OP4 OP5 OP6 OP7 OP8 OP9 OP10 Optical Port Output Power Level (dBm) Optical Port ID OP11 OP12 OP13 OP14 OP15 OP16 OP17 OP18 OP19 OP20 Optical Port Output Power Level (dBm)

4 - 169
4
d. Lock the optical port. At the CoreDirector Node Manager Inventory screen, select Locked from the Administrative State drop-down menu, and click the Accept button. e. Disconnect the optical power meter from the transmit side of the optical port.
Receiver Damage from Out-of-Range Input Signal

Caution: Never allow an input optical signal to exceed the upper threshold of the integrated optical port; receiver damage will result. Use a variable attenuator to test the lower threshold level.
STEP 59: Clean the digital optical test set leads in accordance with Ciena Standard Cleaning & Equipment Safety Practices. If the test set uses either FC or SC connectors, then adapter cables (SC-to-LC or FC-to-LC) must be used during the BER test. These fiber adapter cables must also be properly cleaned.
Note:
STEP 60: Connect the digital optical test set to the transmit and receive LC connectors of the optical port. Ensure that the test set is generating an OC-12 BER test pattern. STEP 61: Set up a diagnostic loopback on the optical port. At the CoreDirector Node Manager menu bar, select Go > Diagnostics > Line Loopback. Select Facility with Framer from the Line Loopback Type list, and click the Accept button. The optical test setup, after the diagnostic has been activated, should match the setup shown in Figure 4-48. STEP 62: Reset the test set error counter. Verify that the digital optical test set connected to the optical port is locked and running an error-free BER test. If the BER test is not running error-free: a. Verify that the diagnostic loopback is properly configured. b. Verify that the test set is generating the proper OC rate BER test. c. Verify that the fiber optic cables used for the BER test were properly cleaned and are making solid contact with the test set and optical port connectors. d. Contact Ciena technical support for assistance. Reference the copyright page of this document for contact information. STEP 63: Drop the diagnostic loopback on the optical port. At the Line Loopback screen, select None from the Line Loopback Type list and click the Accept button. STEP 64: Reset the test set error counter. Verify that the digital optical test set connected to the optical port is no longer locked and is counting BER test errors.
Optical Test Set
R T
OP 1
R
Diagno stic Lo opback
Figure 4-48. Test Set-up (Diagnostic Loopback)
FRONT OF LM-
4 - 170
4
CoreDirector Switch
STEP 65: Unlock the optical port: a. b. c. d. e. f. Select Go > Inventory. In the equipment tree, expand the CoreDirector node view until the desired port is displayed. Select the port. Select the Basic tab of the Inventory screen. In the Admin State field of the Details frame, select Unlocked from the Administrative State drop-down menu. Click Accept. The green LED on the front of the OM or port illuminates, indicating an unlocked administrative state (output signal enabled).
STEP 66: Repeat Step 1 through Step 58 to prepare the next optical port for testing. Continue this procedure from Step 67. Note: The digital optical test set connected to the first optical port on the LM will remain attached for the duration of this procedure.
STEP 67: Connect an LC-to-LC fiber optic jumper between the transmit and receive Optical Modules on the optical port as illustrated in Figure 4-49.
Optical Test Set
R T
OP 1
R
Cross Co nnect
OP 2
R
Fiber Test Jumper
Figure 4-49. Test Set-up (Fiber Jumper and Cross Connect) STEP 68: Establish a Connection Termination Point (CTP) on the first optical port in the daisychain. a. Click the first optical port of the daisychain from the expanded equipment tree. b. At the CoreDirector Node Manager Configuring screen, click the Connection TPs tab and then the Details tab. c. Click New and then type a CTP name (for example, lmop1). d. In the Time Slot Map, click the desired time slots to use for the test. Click individual boxes for single time slots. For multiple slot entries, hold down the shift key, click the left-most time slot box in a series, then click the right-most box and, finally, release the shift key. e. Verify that the entry in the Supporting TP field matches the optical port that was selected in sub-step a. Correct this entry if necessary. f. Click Accept. STEP 69: Repeat Step 68 on the next optical port in the daisychain. When the CTP has been established, continue this procedure from Step 70. STEP 70: Provision a cross-connect between the optical ports on which CTPs were established during Step 69. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
FRONT OF LM-
4 - 171
4
a. At the CoreDirector Node Manager menu bar, click Provisioning and then the Cross Connects tab. b. Click New and then type a Cross Connect Name (for example, lmop1-lmop2). An optional Label name can also be typed. c. Click the grey browser box, located to the right of the From End Point field, and then the CTP tab. d. Click the entry from the CTP list that matches the optical port on which a CTP was established during Step 69, and then click OK. e. Click the gray browser box, located to the right of the To End Point field, and then the CTP tab. f. Click the entry from the CTP list that matches the optical port on which a CTP was established during Step 69, and then click OK. g. At the Provisioning screen, click the Accept button. STEP 71: Reset the test set error counter. Verify that the digital optical test set connected to the optical port is locked and running an error-free BER test. If the BER test is not running error-free: a. Verify that the diagnostic loopback is properly configured. b. Verify that the test set is generating the proper OC rate BER test. c. Verify that the fiber optic cables and test jumpers used for the BER test were properly cleaned and are making solid contact with the test set and optical port connectors. d. Contact Ciena technical support for assistance. Reference the copyright page of this document for contact information. STEP 72: Remove the fiber optic jumper that was installed during Step 67. STEP 73: Repeat Step 55 through Step 58 to prepare the next optical port for testing. Continue this procedure from Step 74. STEP 74: Connect fiber optic LC-to-LC jumpers between the transmit and receive of the last optical port tested to the next optical port (Figure 4-50).
O ptical Test S et
R T
OP 1
R
C ro ss C o nnect
OP 2
R
Fiber T est Jumpers
OP 3
R FRONT OF LMD iagno stic Lo o pback
Figure 4-50. Test Set-up (Fiber Jumpers, Diagnostic Loopback, and Cross-Connect) STEP 75: Set up a diagnostic loopback on the optical port. At the CoreDirector Node Manager menu bar, select Go > Diagnostics > Line Loopback. Select Facility with Framer from the Line Loopback Type list and click the Accept button. The optical test setup, after the diagnostic has been activated, should match the illustration contained in Figure 4-50.
4 - 172
4
STEP 76: Reset the test set error counter. Verify that the digital optical test set connected to the optical port is locked and running an error-free BER test. If the BER test is not running error-free: a. Verify that the diagnostic loopback is properly configured. b. Verify that the test set is generating the proper OC rate BER test. c. Verify that the fiber optic cables and test jumpers used for the BER test were properly cleaned and are making solid contact with the test set and optical port connectors. d. Contact Ciena technical support for assistance. Reference the copyright page of this document for contact information. STEP 77: Drop the diagnostic loopback on the optical port. At the Diagnostics screen, select None from the Loopback Type list and click the Accept button. STEP 78: Reset the test set error counter. Verify that the digital optical test set connected to the optical port during Step 60 is no longer locked and is counting BER test errors. STEP 79: Unlock the optical module. a. b. c. d. e. f. Select Go > Inventory. In the equipment tree, expand the CoreDirector node view until the desired OM is displayed. Select the module. Select the Basic tab of the Inventory screen. In the Admin State field of the Details frame, select Unlocked from the Administrative State drop-down menu. Click Accept. The green LED on the front of the OM or port illuminates, indicating an unlocked administrative state (output signal enabled).
STEP 80: Repeat Step 68 through Step 79 to prepare the next optical module for testing. Continue this procedure from Step 81. STEP 81: Repeat Step 55 through Step 80 to configure and test the remaining LM-16 optical ports. An example of a single LM-16 with all 16 ports set up for testing is illustrated in Figure 4-51. An example of two LM-16s set up for testing is illustrated in Figure 4-52. Note: Allow the final LM test configuration to run for a minimum of 8 hours or whatever time frame is requested by the customer.
STEP 82: Perform the following actions before connecting site fiber to the newly installed and tested LM-16 Line Module: a. b. c. d. e. Drop all diagnostic optical port loopbacks. Delete all optical port cross-connects. Delete all CTP entries. Lock all optical ports from the CoreDirector Node Manager Configuring screen. Remove all fiber optic test jumpers including the test set leads.
Caution:
Air Flow Advisory High Temperature Damage Communications Degradation

Ensure that module filler panels are installed in every unused system slot, including OM slots. Leaving open slots can lead to overheating and degradation or failure of the electronic components on adjacent modules.

4 - 173
4
LM-16
Optical Test Set
R T
T R T R T R
OP 1
OP 2
OP 3
FRONT OF LM-16
T R T R T R T R
OP 4
OP 5
OP 6
OP 7
Fiber Test Jumpers
T R T R T R T R T R T R T R T R T R
OP 8
Cross Connects
OP 9
OP 10
OP 11
OP 12
OP 13
OP 14
OP 15
OP 16
Figure 4-51. Test Setup for One 16-port (LM-16) Line Module
4 - 174
4
LM-16 LM-N
Optical R Test Set T
T R T R T R T R T R T R T R T R T R T R T R T R T R T R T R T R
OP 1
T R T R
Cross Connects
OP 1
OP 2
OP 2
OP 3
T R T R T R T R T R T R T R T R T R T R T R T R T R T R
OP 3
OP 4
OP 4
Fiber Test Jumpers
OP 5
OP 5
OP 6
OP 6
Figure 4-52. Test Setup for Two Integrated Optics Line Modules (LM-16 Shown)

FRONT OF LM-16
OP 7
OP 7
OP 8
OP 8
OP 9
OP 9
OP 10
OP 10
OP 11
OP 11
OP 12
OP 12
OP 13
OP 13
OP 14
OP 14
OP 15
OP 15
OP 16
OP 16
4 - 175
4
Testing LM-16-STM-1E Modules Test each port on the LM-16-STM-1E module as follows: STEP 83: Place the port in facility loopback. Note: The LM-16-STM-1E ports cannot be daisy chained for testing.
CoreDirector Switch
STEP 84: Connect an STM-1e test set to the port and verify that there are no bit errors. STEP 85: Verify that the cable loss between the CoreDirector port and the dropside equipment does not exceed 12.7 dB (unprotected LM-16-STM-1E) or 9 dB (protected LM-16-STM-1E). STEP 86: Repeat Step 83 through Step 85 for each of the remaining LM-16e ports. Note: Prior to connecting the LM-16-STM-1E ports to dropside equipment, verify the functionality of the equipment. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 176
4
TOP 221D TEST OPTICAL MODULE

OVERVIEW
This Task-Oriented Practice describes the procedure for testing a CoreDirector Switch or CoreDirector CI Switch Optical Module (OM) using the CoreDirector Node Manager software and a network test OM-2.5G. This procedure describes how to configure a test circuit using an existing network test OM-2.5G to test OMs. For the OM-10G, the test uses four OC-48c/STM-16c Bit Error Rate (BER) tests to test all 192 OM-10G channels. This procedure can be used to test OM-622, OM-2.5G, or LM-16 optical ports.
REQUIRED TOOLS
! ! ! !
ESD-guard wrist strap ESD-guard heel grounders 10base-T, RJ-45 crossover cable SONET/SDH test set with a 10G (OC-192/STM-64) optical connector capable of testing an OC48c circuit. CoreDirector Node Manager software Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP
! !
PREREQUISITES
!
! ! !
The user must be familiar with CoreDirector Node Manager software. The user must have Node Manager Connection Provisioner (CP) privilege or higher. There must be a 2.5G (OC-48/STM-16) OM available within the CoreDirector network with a fiber loop to use for testing over the network. This OM must be accessible for the test signal that will be sent during testing.
REFERENCE DOCUMENTS
! ! ! ! ! ! !
TOP 001D Measuring Optical Power Level TOP 171D Removing and Installing a Switch Module TOP 172D Removing and Installing an Optical Module TOP 173D Removing and Installing a Line Module TOP 278D Handling Circuit Packs Properly Node Manager User Guide Alarm and Trouble Clearing Procedure Manual

4 - 177
4
CoreDirector Switch

Caution: Notify appropriate personnel before removing operation-critical components. Performance of the following step may cause a traffic disruption. This instruction is intended as a general guide only, has not been tested for all possible applications or configurations, and may not be complete or accurate for some situations.
Warning:

STEP 1: Refer to TOP 001D Measuring Optical Power Level and perform the optical power output test.

Caution: Ensure that the power levels do not exceed specifications in the following steps when testing OMs and Optical Ports. Damage can result from daisychaining or looping back MR, LR, or WDM OMs. Refer to Table 4-23 for the power ranges for each OM type. Use attenuation as required to ensure that the maximum input levels are not exceeded.
Table 4-23. Optical Output Power Ranges for OMs and Optical Ports Port Type 155/622 MR OM (includes LM-16) 2.5G SR OM 2.5G MR OM 2.5G LR OM (LR-1) 2.5G LR OM (LR-2) 10G SR OM (SR-1) 10G SR OM (SR-2) 10G MR OM (MR-2) 10G LR OM (LR-2) 10G WDM-1 OM 10G WDM-2 OM GbE SX GbE LX Output Power Range -15 dBm to -8 dBm -10 dBm to -3 dBm -5 dBm to 0 dBm -2 dBm to +3 dBm -2 dBm to +3 dBm -6 dBm to -1 dBm -5 dBm to -1 dBm -1 dBm to +2 dBm +2 dBm to +4 dBm +4.1 dBm to +7.0 dBm +4 dBm to +5 dBm -9.5 dBm to -4 dBm -9.5 dBm to -3 dBm Receiver Power Range -28 dBm to -8 dBm -18 dBm to -3 dBm -18 dBm to 0 dBm -27 dBm to -9 dBm -28 dBm to -9 dBm -11 dBm to -1 dBm -14 dBm to -1 dBm -27 dBm to -1 dBm -24 dBm to -7 dBm -14.3 dBm to -1.3 dBm -14 dBm to -2 dBm -17 dBm to 0 dBm -20.5 dBm to -3 dBm
4 - 178
4
STEP 2: Identify the network test OM-2.5G that will be used to cross-connect to the OM or port to be tested. STEP 3: Establish a Node Manager session to the CoreDirector Switch with the OM or port to be tested and log on as Account Administrator. STEP 4: Ensure that the LM and OM are unlocked in Inventory and that ALS is disabled, and verify that there are no alarms raised against the OM. If required, refer to the Node Manager User Guide for information on administratively unlocking modules and disabling ALS, and refer to the Alarm and Trouble Clearing Procedure Manual for alarm information. STEP 5: Establish a Node Manager session to the CoreDirector Switch that contains the network test OM2.5G. STEP 6: Verify that the network test OM-2.5G and associated LM-8 are unlocked in Inventory, that ALS is disabled, and that there are no alarms raised against the OM. STEP 7: Depending on the network configuration, verify that the OM-2.5G has the necessary attenuation and fiber optic loopback installed or the diagnostic loopback enabled. STEP 8: Connect the test set to the OM or port to be tested. If necessary, insert attenuators on the fiber links connecting the test set to the OM or port. STEP 9: Set up the test set for a Bit Error Rate (BER) test. For the OM-10G, The first OC-48c/STM-16c BER test uses STS channels 1-48, the second test uses channels 49-96, the third uses 97-144, and the fourth uses channels 145-192. STEP 10: Create the appropriate Connection Termination Points (CTPs) and establish the necessary cross connect(s) or a Subnetwork Connection (SNC) between the OM or port to be tested and the network test OM-2.5G using the STS channels indicated in Step 9 for the appropriate BER test. Refer to the Node Manager User Guide for more information on manual cross connects and creating SNCs. STEP 11: Unlock the OM or port to be tested CTP. If the network test OM-2.5G is configured for a diagnostic loopback, do not unlock the OM-2.5G CTP. If the OM-2.5G is configured with a fiber loopback, unlock the OM-2.5G CTP. Note: If a diagnostic loopback was used on the OM-2.5G, do not unlock the OM-2.5G port.
STEP 12: Verify the test set shows a good test signal being returned from the Far-End OM-2.5G. STEP 13: Inject three path errors into the test set and verify the errors are being returned. STEP 14: Restart the test to clear the counters and monitor for 15 minutes to ensure there are no errors between the OMs. STEP 15: After 15 error-free minutes have elapsed, stop the test and delete the cross connects or SNC. STEP 16: If testing the OM-10G, repeat Step 9 through Step 14 for the remaining STS time slots. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 179
4
4 - 180
4
TOP 223D CHANGE COREDIRECTOR SWITCH NAME/IP ADDRESS

OVERVIEW
This Task-Oriented Practice describes how to change the CoreDirector Switch or CoreDirector CI Switch name (TID) or IP address.

The CoreDirector Switch name (TID) and IP Address cannot be changed once a system is deployed and configured unless all traffic is removed, the CM hard disk drives are reformatted, and software is reloaded. The CoreDirector Switch name, as configured during Turn-up and Test, is used during provisioning to identify various VLSR, designated transit lists, and SNC attributes. The name is stored and used throughout the CoreDirector Switch network. Changing the CoreDirector Switch name on the local node does not change the name stored throughout the network. This procedure applies to a stand-alone CoreDirector Switch system. Users of the ON-Center Switching Manager (CSM) Software application should refer to the section on managing and unmanaging NEs in the CSM Software User Guide for further information.
Caution:
Note:
REQUIRED TOOLS
! ! ! ! !
! !
PREREQUISITES
!
The user must follow proper module handling procedures. When handling, installing, or removing modules, the following precautions must be observed. Refer to TOP 278D Handling Circuit Packs Properly. Ensure modules are stored in ESD-protective packaging when not installed in an equipment shelf. Do not stack modules on or against each other. Pick up modules by the front handle, and do not touch components on the circuit board.

4 - 181
4
! !
CoreDirector Switch
The user must be familiar with CoreDirector Node Manager software. The user must be a registered system user with a valid user name and password to log in to the Command Line Interface (CLI).
REFERENCE DOCUMENTS
! ! ! ! ! !
Node Manager User Guide TOP 170D Removing and Installing a Control Module TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch TOP 270D Resetting the Primary Control Module (CM Switch) TOP 271D Resetting the Secondary Control Module (CM) TOP 278D Handling Circuit Packs Properly
PROCEDURE

Caution: This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. Verify and clear or document all outstanding CoreDirector Switch alarms using applicable Trouble-Clearing Procedures (TCPs). Log off all Node Manager user sessions before performing this procedure. Disable module alarm reporting prior to removal and enable alarm reporting after installation. If required, refer to The Node Manager User Guide.
Note:
Prepare for Procedure STEP 1: In a dual CM system, refer to TOP 170D Removing and Installing a Control Module and perform the Prepare CM for Removal and Remove CM procedures to remove the secondary CM. STEP 2: Perform TOP 270D Resetting the Primary Control Module (CM Switch) to reset the primary CM. STEP 3: During CM bootup, press the Enter key when the countdown appears. The countdown occurs approximately 4 to 5 minutes after bootup begins. The CM Config Menu is displayed. STEP 4: From the CM Config Menu, type the option number to Display current settings and press Enter. Observe and note the CM name and CoreDirector's Main Management IP address. STEP 5: To change the CoreDirector name, type the option number to Set CM Name and press Enter. Type the CM name (for example, 145) and press Enter. STEP 6: To change the CoreDirector main management IP address, type the option number to Set CoreDirectors Main Management IP Address and press Enter. Type the IP address (for example,192.168.238.145) and press Enter.
4 - 182
4
STEP 7: Type the option number to Display current settings and press Enter. Verify that the current settings are correct and repeat Step 5 and Step 6 if required. STEP 8: Type the option number to Commit current settings and press Enter. STEP 9: Wait approximately 5 to 10 minutes for CM to complete the boot process and stabilize. STEP 10: Verify that the red alarm LED on the CM is off and that the Normal LED is lit, indicating that the CM is in primary mode. If the CM red alarm indication still exists, perform TOP 270D Resetting the Primary Control Module (CM Switch). If the problem persists, contact your next level technical support. STEP 11: In a dual CM system, refer to TOP 170D Removing and Installing a Control Module and perform the Install CM and Verify CM Synchronization procedures to re-install the secondary CM. STEP 12: Verify the NE name/IP Address change. Establish a Node Manager session, select Go > Administration > System Configuration > Basic and observe that the screen reflects the correct Switch Name and Main Management IP Address. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 183
4
4 - 184
4
TOP 261D CHANGE NE CLI LOGIN USER ID AND/OR PASSWORD

OVERVIEW
This Task-Oriented Practice changes the CoreDirector Switch or CoreDirector CI Switch Network Element (NE) Command Line Interface (CLI) Login User ID and/or password from a Switching Network Manager workstation or on equipment at the CoreDirector Network Element (NE).
REQUIRED TOOLS
! !
Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP HyperTerminal available on PC ESD-guard wrist strap ESD-guard heel grounders One or both of the following cables: 9-pin to 25-pin RS-232 Data Communications Equipment (DCE) serial cable (DB-9 to DB-25 straight cable) for connection to the Control Module (CM) 9-pin to 9-pin RS-232 Data Terminating Equipment (DTE) null modem serial cable for connection to the backplane Input/Output (I/O) Panel
The following are required when the in-service upgrade is performed at the NE.
! ! !
PREREQUISITES
!
The craftsperson must be a registered system user with a valid user name and password to log in to the Command Line Interface (CLI).
REFERENCE DOCUMENTS
!
PROCEDURE

STEP 1: Establish a connection to the CoreDirector Switch Control Modules (CMs) using one of the following methods: Note: Ciena recommends that a HyperTerminal or serial connection be used since additional messaging is provided to the display terminal.
Establish a HyperTerminal session (TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch). Enable logging to help in identifying events during the upgrade. Establish a Telnet session to appropriate serial connection on terminal server that is directly connected to CoreDirector Switch CMs. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 185
4
a. From the Windows Start menu, select Run. b. Type telnet <CoreDirector IP address> and press Enter. Note: The primary CM and secondary CM IP addresses can be determined using Node Manager by selecting Go > Administration > System Configuration.
CoreDirector Switch
STEP 2: From a HyperTerminal, press Enter and enter the User Id and Password. From a Telnet session, enter the User Id and Password. The CoreDirector Switch CLI Login prompt is displayed. STEP 3: Log in to the CoreDirector Switch CLI at an administrator level. STEP 4: If required, select the option to return to the CM CLI Menu The CM CLI Menu is displayed.
Figure 4-53. CoreDirector Switch CM CLI Menu STEP 5: To change the CLI user login ID, type the option number to Change CLI Login User ID and press Enter. Type the new login ID and press Enter. STEP 6: To change the CLI login password, type the option number to Change CLI Login Password and press Enter. Type the new login password and press Enter. STEP 7: Type the option number to Logout and press Enter to log out of the CM CLI Menu. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 186
4
TOP 262D RECOVERY FROM DUAL CM FAILURE

OVERVIEW
This Task-Oriented Practice describes the method to recover from a CoreDirector Switch or CoreDirector CI Switch dual Control Module (CM) failure. In the case of a single CM failure when there is another functioning CM installed in the CoreDirector Switch, the replacement CM synchronizes with the data stored on the functioning CM and this procedure is not required. The CoreDirector Switch is designed to continue to pass traffic in the event that both the primary and secondary CMs fail. If both CMs fail, the CoreDirector Switch is not managed, and data free-runs through the CoreDirector Switch. When both CMs fail, the CoreDirector Switch cannot react to mesh restoration requests or new provisioning requests. The CoreDirector Switch is still able to respond to APS and VLSR switch requests. When a CM is first installed in a CoreDirector Switch, the CM reads and stores location identifying information (called a brand) from the CoreDirector Switch I/O panel. If the CM is removed and reinstalled, the CM boot process matches the stored brand information against the CoreDirector Switch brand information to verify that the CM belongs to the CoreDirector Switch. If the CM belongs to the CoreDirector Switch, the boot process continues.

Notify appropriate personnel before performing this procedure. There is a traffic disruption risk associated with Step 13. Caution: If the replacement CM belongs to the CoreDirector Switch, a 20-second countdown timer is displayed approximately 2 to 5 minutes after the CM is installed. Failure to interrupt the 20-second countdown timer will disrupt traffic if the CM has an out-of-date database or the incorrect software version and an out-of-date database. Read and understand this procedure in its entirety prior to installing a replacement CM. Contact Ciena Technical Support if there are any questions concerning this procedure.
If the CM does not belong (brand mismatch), the boot process halts and manual input is required. There are two possible types of brand mismatch as follows:
!
Product Mismatch - The replacement CM was previously installed in a different type of CoreDirector. In this case, the proper CoreDirector Switch software must be loaded, the CM configuration must be changed, and the database must be restored. The replacement CM being installed in a CoreDirector CI Switch was previously installed in a CoreDirector Switch. The replacement CM being installed in a CoreDirector Switch was previously installed in a CoreDirector CI Switch.
Brand Mismatch - The replacement CM being installed has a brand acquired from a different switch of the same type. In this case, the proper CoreDirector Switch software might need to be loaded (if the CM contains a different version of software), the CM configuration must be changed, and the database must be restored. The replacement CM being installed in a CoreDirector CI Switch was previously installed in a different CoreDirector CI Switch. The replacement CM being installed in a CoreDirector Switch was previously installed in a different CoreDirector Switch.

4 - 187
4
Table 4-24 lists the possible CM branding scenarios and provides a summary of the actions required. Table 4-24. CM Branding Mismatch Scenarios Branding Mismatch Software Version Mismatch Yes Branding Mismatch No Yes Product Mismatch N/A Action Interrupt countdown and restore database. Interrupt countdown, contact Ciena to install proper software, and restore database. Change CM configuration and restore database. Contact Ciena to install proper software, change CM configuration, and restore database. Contact Ciena to install proper software, change CM configuration, and restore database.
No Branding Mismatch No
This TOP also provides steps to restore a database on the CM after a software install. The database restore menu has the same look as the restore portion of the backup and restore menu. This procedure maintains the system configuration established in the last backed up version of the database. Any provisioning performed or any SNCs routed through this system after the most recent backup will be lost. (SNCs will be released, resulting in dropped traffic.) The user should follow the local internal guidelines for identifying new SNCs that are not included in the most recent backup. According to these internal guidelines, the user should obtain any necessary releases and be prepared to rebuild any such SNCs following the completion of this procedure. Alternatively, the user can temporarily reroute any such SNCs around the CoreDirector Switch network prior to executing this procedure.
REQUIRED TOOLS
! ! ! !
ESD-guard wrist strap ESD-guard heel grounders Common hand tools One or both of the following cables: 9-pin to 25-pin RS-232 serial cable (DB-9F to DB-25M straight cable) for connection to the CM. The 9-pin connector is configured for Data Terminal Equipment (DTE), and the 25-pin connector is configured for Data Communications Equipment (DCE). 9-pin to 9-pin RS-232 serial cable (DB-9F to DB-9F null modem cable) for connection to the backplane I/O panel. Both connectors of a null modem cable are configured for DTE.
! ! ! !
Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP 10base-T, RJ-45 crossover cable CoreDirector Node Manager software HyperTerminal available on the PC
PREREQUISITES
!
The user must use proper module handling procedures. When handling, installing, or removing modules, the following precautions must be observed. Refer to TOP 278D Handling Circuit Packs Properly. Ensure modules are stored in ESD-protective packaging when not installed in an equipment shelf. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 188
4
Do not stack modules on or against each other. Pick up modules by the front handle, and do not touch components on the circuit board.
! ! !
Configuration information for the CoreDirector Switch must be available. Access to the CoreDirector Switch configuration database backup file must be available. Access to the appropriate software release to install on the CM if the CM software version is not exactly the same as the version running on the CoreDirector Switch must be available. The Craftsperson must be a registered system user with a valid user name and password to log on to the Command Line Interface (CLI) and CoreDirector Node Manager.
! ! ! ! ! !
TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 170D Removing and Installing a Control Module TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch TOP 270D Resetting the Primary Control Module (CM Switch) TOP 271D Resetting the Secondary Control Module (CM) TOP 278D Handling Circuit Packs Properly
PROCEDURE


The CLI menu responses in the following procedures are typical and may not exactly match the actual responses. This procedure consists of the following tasks: Note:
! ! !
Remove the failed CMs (page 4-190). Install the first CM (page 4-190). If there is a brand mismatch, do one of the following: Confirm the configuration settings (page 4-191), or Download a previously backed up database (page 4-192).
! !
If there is a product mismatch, contact Ciena Technical Support. Install the secondary CM (page 4-193).

4 - 189
4
Remove Failed CMs The CM contains volatile information that can help Ciena Technical personnel identify and isolate problems on the CM. Information based upon the last assert or reset of the module can be retrieved. The following steps use TOP 270D and TOP 271D to attempt to establish communications to the failed CMs, reboot the failed CMs, and remove the CMs within three minutes of issuing the reboot command.
CoreDirector Switch
Note:
The Command Line Interface (CLI) provides the capability to reset CMs from the Operations Menu. Ciena recommends that any reboots of the CM be performed exclusively through the CM CLI interface. Additionally, it is highly recommended that CMs should be pulled from a CoreDirector Switch or CoreDirector CI Switch system only when it has been determined that the card requires replacement. If the CM requires replacement, the CM should be reset prior to removal and should be removed within three minutes following the reboot. STEP 1: At the CoreDirector Switch, loosen the two screws securing the failed CM to the CoreDirector Switch chassis. STEP 2: Refer to TOP 270D Resetting the Primary Control Module (CM Switch) and TOP 271D Resetting the Secondary Control Module (CM) to attempt to communicate with the failed CMs. If communications can be established, reset the CMs from the CLI Operations menu and proceed to Step 3 within 3 minutes of issuing the reset to remove the CMs. If communications cannot be established, proceed to Step 3. STEP 3: Place the top and bottom ejectors in the open position (perpendicular to the module faceplate); then slide the CM out of the slot. STEP 4: If a cable is connected to the Craft RS-232 port on the first failed CM, disconnect the cable. STEP 5: Place the failed module in an ESD-guard antistatic bag. STEP 6: Repeat steps Step 1 through Step 5 for the second failed CM. STEP 7: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. Install First CM STEP 8: Power up the laptop computer, start the HyperTerminal program, and connect the RS-232 cable to the PC Com port. Refer to TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch on page 1-101 for HyperTerminal settings. STEP 9: Remove the replacement CM from its ESD-guard antistatic bag. STEP 10: Slide the CM halfway into the designated slot. Connect the cable from the laptop computer to the Craft RS-232 port on the CM front panel. STEP 11: Slide the CM fully into the slot and place the top and bottom ejectors in the closed position (parallel to the module faceplate). STEP 12: At the HyperTerminal prompt on the PC, press Enter. The RAM Test messages are immediately displayed. If RAM test messages are not immediately displayed on the PC, immediately unseat the CM from its slot, and go back to Step 8 to verify PC connectivity and HyperTerminal settings. Failure to unseat the CM may cause a total loss of CoreDirector Switch cross-connects. If RAM Test messages are displayed on the PC, proceed to Step 13. STEP 13: After approximately 2 to 5 minutes, one of two possible messages is displayed.
4 - 190
4
a. A 20-second countdown timer is displayed if the CM was previously installed and branded in the CoreDirector Switch.

Caution: Failure to interrupt the 20-second countdown timer can disrupt traffic. The CM could have the wrong software version or an out-of-data database. Although the CM was previously branded by the CoreDirector Switch, it probably has been unseated for a long time and the database is stale.
If a 20-second countdown timer is displayed, immediately press Enter (before the countdown reaches 0) to interrupt the countdown. The software version must be verified and the database must be restored. Proceed to Step 14. b. A message is displayed notifying the user that the CM has been moved from another CoreDirector Switch. If there is a brand mismatch, the CM was branded by another CoreDirector Switch. A brand mismatch requires configuring the CM and restoring the database. Proceed to Step 14. If there is a product mismatch, contact Ciena Technical Support. A product mismatch requires installing the correct product software, configuring the CM configuration settings, and restoring the database. Verify Software Version STEP 14: From the console output, search for the following text:
Loading group properties from
STEP 15: Confirm that the software version running on the CM is exactly the version running in the CoreDirector Switch. If the software version does not match exactly, contact Ciena Technical Support. A software version mismatch requires installing the correct software version, configuring the CM configuration settings, and restoring the database. STEP 16: If a 20-second countdown timer was displayed in Step 13, proceed to Step 24. If there was a brand mismatch in Step 13, proceed to Step 17. CM Configuration Settings The CM configuration must be changed to match the CoreDirector Switch if there was a brand mismatch in Step 13. STEP 17: Press Enter to display the following CoreDirector Switch CLI Login prompt:
Core Director CLI Login UserId:
STEP 18: Log on to the CM CLI menu using the appropriate user name and password. (The default user name is superuser and the default password superuser1!.) The CM Config menu is displayed. STEP 19: Type the option number to Display current settings and press Enter. The current configuration settings are displayed. STEP 20: Type the option number to Set CoreDirector Switch name and press Enter. It is extremely critical that the CoreDirector Switch name is correct. If the CoreDirector Switch name is changed, traffic will be dropped after the settings are committed and the CM reboots. STEP 21: Configure all CoreDirector IP addresses, netmasks, port numbers, and OSRP addresses, all of which must be unique. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 191
4
It is extremely critical to check and correct all CoreDirector IP addresses, netmasks, and port numbers because the previous values could very likely be wrong. If the settings are valid for this CoreDirector Switch, type the option number to Commit settings and press Enter. To set new values, choose options 1 through 21 from the CLI Config menu one at a time and enter the necessary values, then type the option number to Commit settings and press Enter. STEP 22: The Database Configuration menu, which has the following options, is displayed. Restore Database Restore Factory (default) database Accept Database on disk which is OK (neither Old, nor Default)
STEP 23: Select the Restore Database option and proceed to Step 27. Download Database STEP 24: Press Enter to display the Login prompt. STEP 25: Log on to the CoreDirector Switch CLI (the default user name is superuser and the default password superuser1!.). The CM Config menu is displayed. STEP 26: Type the option number to Enter Backup and Restore mode and press Enter. The Backup and Restore menu is displayed. STEP 27: Type the option number to Specify IP Address of FTP site and press Enter, then type the IP address of the FTP site containing the desired CoreDirector Switch database and press Enter. STEP 28: Type the option number to Specify user id for FTP and press Enter, then type the user ID for FTP and press Enter. STEP 29: Type the option number to Specify password for FTP and press Enter, then type the password for FTP and press Enter. STEP 30: Type the option number to Display above settings and press Enter to display the settings entered in Step 27 and Step 28. STEP 31: Type the option number to Transfer Restore Archive from FTP Server and press Enter to transfer the restore archive from the FTP server. The following messages are displayed:
Commencing transfer...please standby... Database transferred successfully!
Note:
The database load transfer can take from 2 seconds to a minute, depending on the geographical location of the FTP server site.
STEP 32: Type the option number to Initiate Restore and press Enter to initiate the restore action. STEP 33: Type the option number to Commit to Restored Database and press Enter to commit to the restored database. STEP 34: Type the option number to Return to Transfer Software Load Menu and press Enter to return to the Transfer Software Load menu. STEP 35: From the Transfer Software Load menu, type the option number to Commit to this load and press Enter to commit to this load.
4 - 192
4
CoreDirector Switch
The following message is displayed:
Committed to new load, CM will reboot...
STEP 36: After the CM boots, all other cards reboot. Wait 5 minutes and proceed to Step 37. After the CoreDirector Switch reboot is completed, the CoreDirector Switch must be unmanaged and then remanaged using the Network Map or CoreDirector Summary windows of the CSM Software application. This ensures a proper synchronization between the CSM Software and the CoreDirector Switch.
Note:
Installing the Second CM STEP 37: Remove the second CM replacement module from its ESD-guard antistatic bag. STEP 38: Connect a cable from the laptop computer to the Craft RS-232 port on the CM front panel. STEP 39: Slide the CM fully into its designated slot, then place the top and bottom ejectors in the closed position (that is, parallel to the faceplate). STEP 40: The secondary CM reboots three times to complete the synchronization process. The process can take from 30 minutes to a few hours depending on database size or CoreDirector activity. Contact Ciena Technical Support if the database has not synchronized after 60 minutes. Launch Node Manager Session STEP 41: Launch the corresponding version of Node Manger and log on. Note: The Node Manger code version and the CoreDirector Switch software release code version must match.
STEP 42: Verify that all settings are correct and that the alarms are as expected (TL1, Node Manager Alarm Summary, Node Manager equipment tree, CM/TM/LM/SM Operational States, and PDP). --STOP-THIS CONCLUDES THE PROCEDURE

4 - 193
4
4 - 194
4
TOP 270D RESETTING THE PRIMARY CONTROL MODULE (CM SWITCH)

OVERVIEW
This Task-Oriented Practice resets the CoreDirector Switch or CoreDirector CI Switch Primary Control Module (CM) on equipment at the CoreDirector Switch. This procedure includes steps to ensure that the Secondary CM database is synchronized to the Primary CM before resetting the Primary CM.
REQUIRED TOOLS
! ! ! ! !
! !
PREREQUISITES
!
! !
The user must be familiar with CoreDirector Node Manager software. The user must have Node Manager Termination Point Provisioner privilege or Node Manager Troubleshooter (TS) privilege. Before performing this procedure, the following tasks must be performed: Current CoreDirector Switch alarms must be noted. The craftsperson must be a registered system user with a valid user name and password to log in to the Command Line Interface (CLI).
! ! ! !
TOP 170D Removing and Installing a Control Module TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch TOP 271D Resetting the Secondary Control Module (CM) TOP 278D Handling Circuit Packs Properly

4 - 195
4
CoreDirector Switch


Caution: This procedure could affect traffic if the Primary CM is reset when the Secondary CM database is not synchronized to the Primary CM. The CLI Menu display responses in the following procedure are typical and may not exactly match the actual responses.
Note:
To prepare to reset the Primary CM, perform Step 1 and Step 2. To connect to the CM, perform Step 3 through Step 5. To determine the CM role, perform Step 6 through Step 8. To reset the Primary CM, perform Step 9 through Step 12. To verify CM status, perform Step 13 through Step 14. Prepare to Reset the Primary Control Module STEP 1: Establish a Node Manager session with the CoreDirector Switch. Note: Replaceable Unit alarms are reported if module alarm reporting is not disabled.
STEP 2: Determine CM Role as follows: a. From the menu bar, select Go > Inventory. b. From the equipment tree, expand the CoreDirector node view and select the desired CM. c. From the Details frame, note the Procedural Status: Reporting indicates Primary CM. Synchronizing or Synchronized indicates Secondary CM. d. If the Procedural Status is not Reporting, select the other CM. Connect To The Primary And Secondary CMs STEP 3: Establish Hyperterminal or Telnet sessions to both CoreDirector CMs:
!
Start a HyperTerminal session using TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch. Launch a Telnet session to the CoreDirector Switch virtual Internet Protocol (IP) address: a. From the Windows Start menu, select Run. b. Type telnet <CoreDirector IP address> and press Enter.
STEP 4: Log in to CoreDirector CLI using the appropriate user name and password. (The default user name is superuser and the default password superuser1!.)
4 - 196
4
STEP 5: If required, select the option to return to the CM CLI Menu The CM CLI Menu is displayed. Determine CM Roles STEP 6: From the CM CLI Menu for each session, type the option number to select Display general information about this CM and press Enter. The current CM information is displayed. STEP 7: Note the Current Role information (Primary or Secondary) for this CM. Note: Knowing the current CM role is required to ensure that the correct CM is reset. Do not use the Reset This CM option on the Primary CM unless the Secondary CM database is synchronized to the Primary CM.
STEP 8: Verify that the current role for the secondary CM is Secondary (DB up to date).

Caution: DB up to date indicates that the Secondary CM database is synchronized to the Primary CM database. Do not reset the Primary CM unless the Secondary CM database is synchronized to the Primary CM.
Reset the Primary CM STEP 9: From the primary CM CLI Menu session, type the option number to select Operations Menu and press Enter. The Operations Menu is displayed. Note: OSRP link mesh restorations can not take place within three minutes of a CM switch. The CM is not fully functioning in the first three minutes and mesh restoration times will be extended.
STEP 10: Type the option number to Reset This CM and press Enter. Observe that the following (typical) message is displayed:
WARNING: This operation is very CRITICAL and INTRUSIVE to the system. a) It is completely unnecessary if the other CM is rebooting by itself. b) Ensure there is NO CLI SESSION on the other CM attempting to do the same operation. Failing to comply with this condition locks the Control Plane and that is only solved by a power reset of the whole TXN. c) If you intend to reboot both CMs: reset only one CM at a time and allow the first one to come up completely before proceeding to reset the other one. Are you ABSOLUTELY sure you want to continue with the reset of the other CM? (Y/N)
STEP 11: Type Y and press Enter to confirm message and reboot the Primary CM. STEP 12: If this procedure is performed as a part of TOP 170D Removing and Installing a Control Module, end this procedure and continue TOP 170D Removing and Installing a Control Module within three minutes of resetting the CM. Note: A Replaceable Unit Alarm is posted while the CM reboots. The alarm automatically clears when module is detected as operational.

4 - 197
4
Verify CM Synchronization Secondary CM synchronization can take between 30 minutes and several hours depending upon database size and CoreDirector Switch activity. Contact Ciena Technical Support if the secondary CM database does not synchronize with the primary CM.
CoreDirector Switch
Note:
STEP 13: Monitor secondary CM synchronization state using one of the following methods until the replaced CM synchronizes with the primary CM:
!
Connect to the Secondary CM and from the CM CLI Menu, type 2 and press Enter to display general information about this CM. Verify that Current Role is Secondary (DB up to date). If not, secondary has not completed synchronization. If current roles displays Primary, repeat Step 3 on the other CM. At the CoreDirector Switch, observe the red Fail and yellow MAINT LED on the CM are off and the green ACTIVE LED is winking. Use Node Manager Inventory screen and ensure that Secondary CM Procedural Status is Synchronized and the Operational State is Enable.
4 - 198
4
TOP 271D RESETTING THE SECONDARY CONTROL MODULE (CM)

OVERVIEW
This Task-Oriented Practice resets the CoreDirector Switch or CoreDirector CI Switch secondary Control Module (CM) on equipment at the CoreDirector Switch.
REQUIRED TOOLS
! ! ! ! !
! !
PREREQUISITES
!
! !
! ! !
TOP 170D Removing and Installing a Control Module TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch TOP 278D Handling Circuit Packs Properly

4 - 199
4
CoreDirector Switch

Note:
The CLI Menu display responses in the following procedure are typical and may not exactly match the actual responses.
To prepare to reset the Secondary CM, perform Step 1 and Step 2. To connect to the CM, perform Step 3 through Step 5. To determine the CM role, perform Step 6 and Step 7. To reset the Secondary CM, perform Step 8 through Step 11. To verify CM status, perform Step 12 and Step 13. Prepare to Reset the Secondary Control Module STEP 1: Establish a Node Manager session with the CoreDirector Switch. Note: Replaceable Unit alarms are reported if module alarm reporting is not disabled.
STEP 2: Determine CM Role as follows: a. From the menu bar, select Go > Inventory. b. From the equipment tree, expand the CoreDirector node view and select the desired CM. c. From the Details frame, note the Procedural Status: Reporting indicates Primary CM. Synchronizing or Synchronized indicates Secondary CM. d. If the Procedural Status is Reporting, select the other CM. Connect to the Primary and Secondary CMs STEP 3: Establish Hyperterminal or Telnet sessions to both CoreDirector CMs:
!
Start a HyperTerminal session using TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch. Launch a Telnet session to the CoreDirector Switch virtual Internet Protocol (IP) address, as follows: a. From the Windows Start menu, select Run. b. Type telnet <CoreDirector IP address> and press Enter.
STEP 4: Log in to CoreDirector CLI using the appropriate user name and password. (The default user name is superuser and the default password superuser1!.) STEP 5: If required, select the option to return to the CM CLI Menu The CM CLI Menu is displayed.
4 - 200
4
CoreDirector Switch
Determine CM Roles STEP 6: From the CM CLI Menu for each session, type the option number to select Display general information about this CM and press Enter. The current CM information is displayed. STEP 7: Note the Current Role information (Primary or Secondary) for this CM. Note: Reset the Secondary CM STEP 8: From the secondary CM CLI Menu, type the option number to select Operations Menu and press Enter. The Operations Menu is displayed. Note: Ensure that the secondary CM is being reset in the following steps. Knowing the current CM role is required to ensure that the correct CM is reset.
STEP 9: Type the option number to Reset This CM and press Enter. Observe that the following (typical) message is displayed:
WARNING: This operation is very CRITICAL and INTRUSIVE to the system. a) It is completely unnecessary if the other CM is rebooting by itself. b) Ensure there is NO CLI SESSION on the other CM attempting to do the same operation. Failing to comply with this condition locks the Control Plane and that is only solved by a power reset of the whole TXN. c) If you intend to reboot both CMs: reset only one CM at a time and allow the first one to come up completely before proceeding to reset the other one. Are you ABSOLUTELY sure you want to continue with the reset of the other CM? (Y/N)
STEP 10: Type Y and press Enter to confirm message and reboot the Secondary CM. STEP 11: If this procedure is performed as a part of TOP 170D Removing and Installing a Control Module, end this procedure and continue TOP 170D Removing and Installing a Control Module within three minutes of resetting the CM. Note: A Replaceable Unit Alarm is posted while the CM reboots. The alarm automatically clears when module is detected as operational.
Verify CM Synchronization Secondary CM synchronization can take between 30 minutes and several hours depending upon database size and CoreDirector Switch activity. Contact Ciena Technical Support if the secondary CM database does not synchronize with the primary CM.
Note:
STEP 12: Monitor secondary CM synchronization state using one of the following methods until the replaced CM synchronizes with the primary CM:
!
Connect to the Secondary CM and from the CM CLI Menu, type 2 and press Enter to display general information about this CM. Verify that Current Role is Secondary (DB up to date). If not, secondary has not completed synchronization. If current roles displays Primary, repeat Step 3 on the other CM.

4 - 201
4
!
CoreDirector Switch
At the CoreDirector Switch, observe the red Fail and yellow MAINT LED on the CM are off and the green ACTIVE LED is winking. Use Node Manager Inventory screen and ensure that Secondary CM Procedural Status is Synchronized and the Operational State is Enable.
4 - 202
4
TOP 274D IO PANEL EEPROM CHECK

OVERVIEW
This Task-Oriented Practice describes the method of connecting to the CoreDirector Switch or CoreDirector CI Switch Control Module (CM) using a laptop computer or using CoreDirector Node Manager to check the IO Panel EEPROM. The IO Panel EEPROM stores the System ID (or brand) used by the CM Branding feature to identify the installed CMs. A CM is considered alien if the CM brand does not match the CoreDirector Switch ID.
REQUIRED TOOLS
! !
Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP HyperTerminal available on PC ESD-guard wrist strap ESD-guard heel grounders One or both of the following cables: 9-pin to 25-pin RS-232 Data Communications Equipment (DCE) serial cable (DB-9 to DB-25 straight cable) for connection to the CM. 9-pin to 9-pin RS-232 Data Terminating Equipment (DTE) null modem serial cable for connection to the Backplane I/O Panel
! ! !
PREREQUISITES
!
The craftsperson must be a registered system user with a valid user name and password to log into the Command Line Interface (CLI) or CoreDirector Node Manager.
! !
TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch
PROCEDURE

Caution: This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. The CLI displays shown in the following procedure are typical and may not exactly match the actual displays seen during this process.
Note:
To use CoreDirector Node Manager to check the EEPROM, Step 1 through Step 5 are performed. To use CoreDirector Switch CLI to check the EEPROM, Step 6 through Step 9 are performed.

4 - 203
4
CoreDirector Node Manager IO Panel EEPROM Check STEP 1: Establish a Node Manager session with the CoreDirector Switch and log on as Account Administrator. STEP 2: From the CoreDirector Node Manager menu bar, select Go > Inventory. The Inventory screen is displayed. STEP 3: In the equipment tree, expand the CoreDirector node view. STEP 4: From the equipment tree, select 1-IOPanel-1. STEP 5: In the Details frame, note the IO Module Serial #. If the Serial # is blank, the IO Panel must be replaced. Proceed to Step 10. If the Serial # is present, the EEPROM is functioning correctly. End this procedure. CoreDirector Switch CLI IO Panel EEPROM Check STEP 6: Connect to the CoreDirector Switch in one of the following ways:
!
CoreDirector Switch
STEP 7: Log in to the CoreDirector Switch CLI at an administrator level. The CM CLI Menu is displayed. STEP 8: From the CM Config Menu, type the number corresponding to Display general information about this CM, and press Enter. STEP 9: Note the Current TXN Brand (System ID). If the Current TXN Brand (System ID) is blank, the IO Panel must be replaced. Proceed to Step 10. If the Current TXN Brand (System ID) is present, the EEPROM is functioning correctly. End this procedure. STEP 10: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 204
4
TOP 275D CHANGE COREDIRECTOR INITIAL INSTALL SETTINGS

OVERVIEW
This Task-Oriented Practice describes the method of connecting to the CoreDirector Switch or CoreDirector CI Switch Control Module (CM) using a laptop computer and configuring the auxiliary internet protocol (IP) network configuration and OSI System ID. The Change install settings CM CLI Menu option enables the user to remotely change the CoreDirector OSI System ID and change the CoreDirector CM and CM Auxiliary IP addresses and netmasks. In Software Release 2.1 and later, the main and auxiliary IP addresses must be in the same subnet. If the software detects that any of the five external IP addresses is not in the same subnet during initialization, a warning in the serial port or Telnet session is logged. The High Availability Data Communications Network Access feature will not be fully functional until the external IP addresses are in the same subnet.
REQUIRED TOOLS
! !
Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP HyperTerminal available on PC ESD-guard wrist strap ESD-guard heel grounders One or both of the following cables: 9-pin to 25-pin RS-232 Data Communications Equipment (DCE) serial cable (DB-9 to DB-25 straight cable) for connection to the CM. 9-pin to 9-pin RS-232 Data Terminating Equipment (DTE) null modem serial cable for connection to the Backplane I/O Panel
The following are required when the procedure is performed at the Network Element (NE).
! ! !
PREREQUISITES
!
The craftsperson must be a registered system user with a valid user name and password to log into the Command Line Interface (CLI). The CoreDirector Switch auxiliary IP Address and netmask data.
!
PROCEDURE

Caution: This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. The CLI displays shown in the following procedure are typical and may not exactly match the actual displays seen during this process.
Note:

4 - 205
4
STEP 1: Connect to the CoreDirector Switch in one of the following ways:
!
CoreDirector Switch
STEP 2: Log in to the CoreDirector Switch CLI at an administrator level. The CM CLI Menu is displayed. STEP 3: From the CM Config Menu, type the number corresponding to Change install settings, and press Enter. From the Change Install Settings Menu, type the number corresponding to Display current install settings, and press Enter. Observe that the following (typical) information is displayed and note the current install settings:
CoreDirector name.....................................txn145 CoreDirector's Main Management IP address.............192.168.238.145 CoreDirector's Main Management IP address netmask.....255.255.255.0 CoreDirector's Internal Network Base address..........10.145 A-CM's Main IP address................................192.168.238.149 A-CM's Main IP address netmask........................255.255.255.0 C-CM's Main IP address................................192.168.238.153 C-CM's Main IP address netmask........................255.255.255.0 CoreDirector IP gateway address.......................192.168.238.1 A-CM's Auxiliary IP address...........................unknown A-CM's Auxiliary IP address netmask...................unknown C-CM's Auxiliary IP address...........................unknown C-CM's Auxiliary IP Address netmask...................unknown OSRP Node Address...................45.000000010001000100010145.00000000ffff.00 CoreDirector CORBA BOA Main Port Number...............unknown CoreDirector TLI Module Port Number...................10201 CoreDirector HTTP Port Number.........................80 CoreDirector Echo Port Number.........................30003 Management Ethernet Port Revertive....................false CoreDirector TL1 Maximum User Number..................6 CoreDirector OSI System ID............................111111111111 Current System time: .................................11/04/2003 16:08:37
STEP 4: To change A-CM's Auxiliary IP address, type the option number to set A-CM's Auxiliary IP address and press Enter. a. Type the A-CM Auxiliary IP address (for example, 192.168.236.145) and press Enter. b. Note that the Install Settings Menu is displayed. STEP 5: To change A-CM's Auxiliary IP address netmask, type the option number to set A-CM's Auxiliary IP address netmask and press Enter. a. Type the A-CM Auxiliary IP address netmask (for example, 255.255.255.0) and press Enter. b. Note that the Install Settings Menu is displayed. STEP 6: To change C-CM's Auxiliary IP address, type the option number to set A-CM's Auxiliary IP address and press Enter. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 206
4
a. Type the C-CM Auxiliary IP address (for example, 192.168.237.145) and press Enter. b. Note that the Install Settings Menu is displayed. STEP 7: To change C-CM's Auxiliary IP address netmask, type the option number to set A-CM's Auxiliary IP address netmask and press Enter. a. Type the C-CM Auxiliary IP address netmask (for example, 255.255.255.0) and press Enter. b. Note that the Install Settings Menu is displayed. STEP 8: To change CoreDirector OSI System ID, type the option number to set CoreDirector OSI System ID and press Enter. a. Type the OSI System ID (for example, 192168238145) and press Enter. b. Note that the Install Settings Menu is displayed. STEP 9: Type the option number to Display current install settings and press Enter then ensure that the values displayed are correct. a. If the values are not correct, go to Step 10. b. To back out the changes and restore the initial install settings, go to Step 11. c. If the values are correct, go to Step 12. STEP 10: Repeat Step 4 through Step 9 as required and input the correct values. STEP 11: To back out of the change and not change the CoreDirector initial install settings, repeat Step 4 through Step 8 to return the install settings to the values noted in Step 8 then type the option number to Return to CM CLI Menu and press Enter. STEP 12: To commit the new settings and reset the CMs, type the option number to Commit to new settings and press Enter. Note: OSRP link mesh restorations can not take place within three minutes of a CM switch. The CM is not fully functioning in the first three minutes and mesh restoration times will be extended.
STEP 13: Wait approximately 5 to 10 minutes for the CoreDirector Switch to stabilize. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 207
4
4 - 208
4
TOP 276D LM-8 TO LM-16 UPGRADE

OVERVIEW
This Task-Oriented Practice describes how to perform an in-service Line Module (LM) upgrade from a LM8 to LM-16 in a CoreDirector Switch or CoreDirector CI Switch. In the CoreDirector Switch, LMs are located in slots A-2 through A-16 and slots C-1 through C-15. In the CoreDirector CI Switch, LMs occupy two groups of slots; 1 through 4 (left side of the system shelf) and 5 through 8 (right side of the system shelf). The following procedure moves active traffic in a LM-8 1+1 configuration to the working LM-8, de-provisions and replaces the protect LM-8 with an LM-16, and re-provisions the protection scheme. Note: Use this procedure to remove and install LMs that carry traffic.
REQUIRED TOOLS
The optical interfaces on the LM-16 Line Module require LC-type connectors on a 1.6-mm to 2.0-mm Simplex Single-Mode Fiber (SMF) assembly. The LCtype connectors on the LM-16 module are not physically compatible with SCtype connectors that may be used in the LM-8 and require SC-to-LC adapter cables in cases where site fiber terminated with LC-type connectors are not available. The LM-16 is normally used for add/drop ports. When replacing an existing LM-8 with LM-16, the LM-16 does not support OSRP and therefore cannot be used for mesh protection.
Note:
! ! ! ! ! !
PREREQUISITES
!
The user must use proper module handling procedures. When handling, installing, or removing modules, the following precautions must be observed. Refer to TOP 278D Handling Circuit Packs Properly on page 1-215. Make sure modules are stored in ESD-protective packaging when not installed in an equipment shelf. Do not stack modules on or against each other. Pick up modules by the front handle, and do not touch components on the circuit board.
! !

4 - 209
4
! ! ! ! ! !
CoreDirector Switch
Node Manager User Guide TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 172D Removing and Installing an Optical Module TOP 173D Removing and Installing a Line Module TOP 195D Connecting and Logging On to Node Manager via the Ethernet Interface TOP 278D Handling Circuit Packs Properly
PROCEDURE
Warning:



Caution: This procedure affects traffic if performed on a LM that is carrying traffic. Performance of the following step may cause a traffic disruption. This instruction is intended as a general guide only, has not been tested for all possible applications or configurations, and may not be complete or accurate for some situations. Modules can be hot-swapped; CoreDirector power does not need to be removed. Lock modules prior to removal and unlock modules after installation. If required, refer to Node Manager User Guide.
Note:
To Prepare for Line Module Upgrade, Step 1 and Step 2 are performed. To Verify APS Switch State, Step 3 and Step 4 are performed. To Delete APS 1+1 Groups, Step 5 through Step 8 are performed. To Delete LM 1+1 Configuration, Step 9 and Step 10 are performed. To Lock and Remove OMs, Step 11 through Step 21 are performed. To Remove and Replace the LM, Step 22 through Step 39 are performed.
4 - 210
4
CoreDirector Switch
Prepare for Line Module Upgrade STEP 1: Perform this procedure during a planned maintenance window. STEP 2: Establish a Node Manager session with the CoreDirector Switch. Note: Verify APS Switch State STEP 3: From the Node Manager menu bar, click Go > Protection > Line Level > APS/MSP. STEP 4: Verify that the APS group is IDLE by performing the following: Select the appropriate APS Group that contains the LM to be swapped. Click Traffic Flow tab. Verify both working and protect lines are Idle. If switch is active, click Administer and move traffic back onto Working Optical Module (OM). Data Plane Health Failure alarms are reported if this procedure is performed on unlocked modules.
Delete APS 1+1 Groups Note: Prior to deleting the APS 1+1 group, ensure that there are no active switches associated with the group.
STEP 5: Click Go > Protection > Line Level > APS/MSP. STEP 6: Select the APS group that has an OM that resides on the LM being swapped. Note: After an APS group is highlighted, additional information is displayed in the Details frame. If LM A-4 is being swapped, then all APS groups that display OMs A-4-1 through A-4-8 must be deleted.
- From the Details frame select Add/Remove PUs. - From the Add/Remove Protection Units window select the working OM and click Remove (The protect OM should be removed automatically). - Click Close to close the dialog box. - Click Accept to apply the changes. STEP 7: Select the APS Group selected in Step 6 and click Delete. STEP 8: Repeat Step 6 and Step 7 for each APS group that has an OM that resides on the LM being swapped. Delete LM 1+1 Configuration Note: All APS 1+1 groups associated with the LM 1+1 configuration must be deleted prior to deleting the LM 1+1 configuration.
STEP 9: From the menu bar, click Go > Protection > Line Level > LM 1+1. STEP 10: In the List frame highlight the Configuration Name that contains the LM being swapped and click Delete.

4 - 211
4
Lock and Remove OMs
CoreDirector Switch

Caution: Performance of the following steps could disrupt traffic. Locking an OM is service affecting on OMs that are carrying traffic.
STEP 11: In the equipment tree, expand the CoreDirector node view until the desired OM or port is displayed and select the OM. STEP 12: From the menu bar, click Go > Inventory and in the details frame, select the Basic tab. STEP 13: In the Admin State field of the Details frame, select Locked from the Administrative State dropdown menu and click Accept. Click the Yes box in the pop-up window. STEP 14: Lock each OM on the LM in inventory by clicking Inventory and selecting the OM from the equipment tree. Change Admin State to Locked in the Details frame and click Accept. STEP 15: Remove the door on the shelf of the LM being replaced, and locate the LM. STEP 16: Trace the fibers and pull slack so the OMs can be safely pulled. STEP 17: Identify each fiber by tagging with appropriate OM slot or port, Tx/Rx. STEP 18: Refer to TOP 172D Removing and Installing an Optical Module and unseat the OM. STEP 19: Remove the fibers from the OM. STEP 20: Place dust covers on fiber connectors, and place the OM in an anti-static bag. STEP 21: Repeat Step 16 through Step 20 for all OMs that reside on the LM being swapped. Remove and Replace the LM STEP 22: From the Equipment tree on the Inventory screen select the LM being swapped. In the ARC State field of the Details frame, select No Alarm Reporting from the ARC State drop-down menu. STEP 23: Click the check box to Prepare to unseat card click Accept. STEP 24: Remove the LM and place it in an anti-static bag. STEP 25: After the LM is removed, the Delete button in the Details frame becomes active. Click Delete. STEP 26: Refer to TOP 173D Removing and Installing a Line Module and install the LM-16. STEP 27: At the LM-16, remove the dust caps from the optical port (OP) where fibers are to be connected and clean the optical connectors in accordance with Ciena Standard Cleaning & Equipment Safety Practices.

Caution: Never allow an input optical signal to exceed the -8 dBm upper threshold of the Optical Port or receiver damage will result.
STEP 28: From the menu bar, click Go > Inventory. STEP 29: Select the Physical TP tab. STEP 30: At the Details frame, verify that the OP is configured for the required rate as indicated in the Rate Information box. - If it is not set to the desired rate, click the down arrow and select the desired rate and click Accept.
4 - 212
4
STEP 31: Clean the fibers to be connected to the LM-16 in accordance with Ciena Standard Cleaning & Equipment Safety Practices and connect to the appropriate OP. STEP 32: From the menu bar, click Go > Inventory. STEP 33: Select the Basic tab. STEP 34: Change the Admin State of the OP to Unlocked and click the Accept button. STEP 35: At the LM-16 OP, verify the following LED indications: green OP LED is illuminated M (Maintenance) LED is OFF L (Line) LED is OFF green AF (Active/Fail) LED is illuminated
STEP 36: Repeat Step 27 through Step 35 for each OP to be placed in service. STEP 37: Repeat Step 3 through Step 36 for each LM that will be replaced. STEP 38: Re-provision protection scheme(s). STEP 39: Package the removed OMs and LMs and perform the Return Material Authorization (RMA) procedure in accordance with TOP 072D Ciena Return Material Authorization (RMA) Procedure. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 213
4
4 - 214
4
TOP 278D HANDLING CIRCUIT PACKS PROPERLY

OVERVIEW
This Task-Oriented Practice describes the proper circuit pack handling procedures for CoreDirector Switch. In addition, this TOP provides the procedures to use when removing a circuit pack from or inserting a circuit pack into an ESD-guard antistatic bag. Improper handling or added pressure to sensitive circuit pack components (for example, the VI processor daughter board on the Line Module) can have these consequences:
! !
A damaged board that will not function properly when the unit is in operational use A misdiagnosed failure analysis report for a returned (RMA) unit
Proper handling prevents such damage to the unit.

This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. All modules must be fully seated and latched into the chassis. If modules need to be removed and cannot be replaced with another module, replace with the appropriate blank module. Any module left incompletely seated (or partially removed) may cause the system to become susceptible to Electrostatic Discharge (ESD) effects.
Caution:
REQUIRED TOOLS
The following are required for all circuit pack removals and installations:
! ! ! !
ESD-guard wrist strap ESD-guard heel grounders Common hand tools Antistatic bag or antistatic box
PREREQUISITES
!
The user must use proper circuit pack handling procedures. When handling, installing, or removing circuit packs, the following precautions must be observed. Ensure circuit packs are stored in ESD-protective packaging when not installed in an equipment shelf. Do not stack circuit packs on or against each other. Pick up circuit packs by the front handle, and do not touch components on circuit board.
An antistatic bag or box must be available for the removed circuit pack
REFERENCE DOCUMENTS
! ! ! ! ! !
TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 170D Removing and Installing a Control Module TOP 171D Removing and Installing a Switch Module TOP 172D Removing and Installing an Optical Module TOP 173D Removing and Installing a Line Module TOP 174D Removing and Installing a Timing Module

4 - 215
4
CoreDirector Switch

This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. All modules must be fully seated and latched into the chassis. If modules need to be removed and cannot be replaced with another module, replace with the appropriate blank module. Any module left incompletely seated (or partially removed) may cause the system to become susceptible to Electrostatic Discharge (ESD) effects.
Caution:
! ! ! ! !
Precautions for Handling and Storing Circuit Packs on page 1-216 Removing a Circuit Pack from an Antistatic Bag on page 1-217 Inserting a Circuit Pack into an Antistatic Bag on page 1-218 Handling Optical Modules on page 1-218 Handling Circuit Packs During Installation on page 1-219
Precautions for Handling and Storing Circuit Packs Industry experience has shown that all devices containing integrated circuits can be damaged by static electricity that builds up on work surfaces and personnel. The effect of Electrostatic Discharge (ESD) damage may be immediate failure or it may manifest itself as a latent failure affecting the reliability of the equipment. Observe the following precautions to avoid static charges and discharges:
!
Assume that all circuit packs contain solid state electronic components that can be damaged by ESD. When handling circuit packs (for example, storing, installing, or removing), always wear a grounded wrist strap or wear a heel strap and stand on a grounded, static-dissipating floor mat. Handle all circuit packs by the faceplate or latch and by the top and bottom outermost edges. Never touch the components, conductors, or connector pins. If possible, do not remove circuit packs from antistatic packaging until they are ready for use. If possible, open all circuit pack packaging at a static-safe work station using properly grounded wrist straps and static-dissipating table mats. Always store and transport circuit packs in static-safe packaging. When removing circuit packs from an enclosure, immediately place them in static-safe packages. Do not leave modules partially installed in the CoreDirector slot. Ensure that the backplane protective covers or caps are removed from the circuit packs before installing them in equipment shelves. Do not stack circuit packs directly on or against each other. Store all circuit packs in the original protective packaging container. Do not stack circuit packs without the use of the original protective packaging containers. Do not leave modules partially installed in the CoreDirector slot.
! !
! !
To avoid physical damage to circuit packs, observe the following precautions:

!
! !
4 - 216
4
CoreDirector Switch
Removing a Circuit Pack from an Antistatic Bag Note: Be sure to handle the circuit pack only from the front faceplate side. Never handle the circuit pack from the backplane side.
STEP 1: Wearing an ESD-guard wrist strap, open the ESD-guard antistatic bag STEP 2: Holding the front faceplate, carefully slide the circuit pack from the antistatic bag. For support of the circuit pack, one hand can be placed under the pan (the side without board components). If the circuit pack was incorrectly inserted with the faceplate facing the wrong direction, place one hand under the pan and carefully rotate the circuit pack so the circuit pack can be removed from the bag. If the bag is not large enough to rotate the circuit pack, place one hand under the pan and carefully remove the circuit pack from the bag until the face plate can be grabbed. This should be done over a flat surface since there is a possibility of dropping the circuit pack. Never pull the circuit pack out of the bag by applying pressure to the pan and the component boards (Figure 4-54). Such handling can cause damage to certain boards that do not have added stiffeners to support such pressure (for example, the VI processor daughter board). To prevent damage to circuit packs, always handle the circuit packs by the faceplate side.
Note:
Handling the VI board can result in circuit pack failures Circuit Pack Faceplate
Figure 4-54. Improper Circuit Pack Handling --STOP-THIS CONCLUDES THE PROCEDURE

4 - 217
4
Inserting a Circuit Pack into an Antistatic Bag Note: Handle the circuit pack only from the front faceplate side. Never handle the circuit pack from the side that contains the backplane connectors.
CoreDirector Switch
STEP 1: Wearing an ESD-guard wrist strap, follow the appropriate TOP to remove the circuit pack from the CoreDirector Switch (Table 4-25). STEP 2: Using the ejectors, carefully slide the circuit pack out of the slot. STEP 3: Support the circuit pack under the pan and carefully slide the circuit pack, backplane connector edge first, into the ESD-guard antistatic bag. (Figure 4-55). Note: Do not insert the circuit pack faceplate-first into the antistatic bag.
VI Board Location
Front Faceplate Antistatic Bag Figure 4-55. Inserting a Circuit Pack into an Antistatic Bag STEP 4: Fold the antistatic bag opening toward the back side of the pan. STEP 5: Perform the required Return Material Authorization (RMA) procedure in accordance with TOP 027D. --STOP-THIS CONCLUDES THE PROCEDURE Handling Optical Modules When handling Optical Modules (OMs), note the following guidelines:
!
Always hold the circuit pack by the handle only; do not touch board components (Figure 4-56).
Figure 4-56. Removing an OM from Its Antistatic Bag

! !
Remove the covers from all optical connectors before installing the OM. Take extra care when connecting the fiber cables to an OM and when sliding the OM into the LM slot to not to twist or otherwise stress the OM. Improper handing can damage circuit packs. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 218
4
CoreDirector Switch
Handling Circuit Packs During Installation Follow the appropriate Task-Oriented Practice (TOP) (Table 4-25) to install the circuit pack in the CoreDirector Switch. Note the following guidelines: Table 4-25. Circuit Pack Installation TOPs TOP Number 170D 171D 172D 173D 174D Title Removing and Installing a Control Module Removing and Installing a Switch Module Removing and Installing an Optical Module Removing and Installing a Line Module Removing and Installing a Timing Module
Inspect the module connector block for damage or misalignment. Do this by visually inspecting each of the connector blocks to verify that they are properly seated and flush on the Printed Circuit Board (PCB). As a second inspection method, look at the top of all the blocks; they should appear planar and horizontally aligned. If any of the individual blocks appear to be mis-seated or out-of-alignment, place the module back into the ESD-guard antistatic bag and return in accordance with TOP 072D, Ciena Return Material Authorization (RMA) Procedure. Figure 4-57 and Figure 4-58 show the correct connector block alignment of a line module.
Figure 4-57. Correct Connector Block Alignment Planar View (LM-8 shown)
Figure 4-58. Correct Connector Block Alignment Planar Top View (LM-8 shown)

4 - 219
4
!
CoreDirector Switch
Check slot backplane connector and verify no bent pins are present. If backplane connector is suspected of having damage, contact Ciena Technical Support for assistance. All CoreDirector modules are designed such that when inserted, the air gaps between the faceplates are minimal. This provides a continuous low impedance ground path for Electromagnetic Interference and Susceptibility compliance, ESD compliance, and a path to chassis ground for safety. There could be insufficient space for the circuit pack face plate to fit securely against the chassis. If required, loosen the faceplate screws of the adjacent modules on either side as needed and then install the circuit pack.
Note:
For CMs, LMs, TMs, and SMs, slowly slide the module into the designated slot by pushing on the module faceplate until the top and bottom ejectors engage the ejector bracket and begin to rotate as shown in Figure 4-59. Take care to insert the module using the guide rails in a level, straightforward motion and visually inspect for proper LM faceplate fit while moving both ejectors into the closed position. If required, loosen the faceplate screws of the adjacent modules on either side as needed and then install the circuit pack. Simultaneously apply equal pressure and move both ejectors to the closed position. Ensure that the faceplate is flush against the chassis then tighten faceplate screws. Note: The CoreDirector Switch meets Insertion Force requirements in GR-78 for maximum force to install and remove circuit packs.
LM/TM CM Figure 4-59. Module Insertion (CM and LM/TM Shown)

!
If inserting an LM, do not use the handles on the OMs to push the module into the chassis.
4 - 220
4
CoreDirector Switch
!
Take extra care when sliding modules to not to twist or otherwise stress the module. Improper handing can damage the modules. Do not leave modules partially installed in the CoreDirector slot. As an OM is being installed, hold the module by the handle on the front, and use the other hand to support the back of the circuit board (Figure 4-60).
! !
Figure 4-60. Installing OMs
Note:
As the OM slides into the slot in the LM, ensure that the plane of the OM circuit board is perpendicular to the plane of the LM faceplate (Figure 4-60). Otherwise, components on the OM can scrape on the sides of the slot and be sheared off the circuit board.
--STOP-THIS CONCLUDES THE PROCEDURE

4 - 221
4
4 - 222
4
TOP 279D PREPARE SITE TERMINAL (OR LAPTOP) FOR SOFTWARE TRANSFER
OVERVIEW
System upgrade software (CoreDirector Switch or CoreDirector CI Switch) is downloaded to the primary CM through a File Transfer Protocol (FTP) application running on the site terminal (or laptop computer). This Task-Oriented Practice describes how to copy system upgrade software files from a CD-ROM to the FTP directory, and how to install and configure the common FTP software package, WFTPD. WFTPD software by Texas Imperial Software or another FTP application must be running in order to transfer files from the site terminal (or laptop). Files for transfer are copied from the CoreDirector Switch Compact Disc (CD) to the D:\FTPROOT folder. If the site terminal (or laptop) hard drive is not partitioned and does not have a D drive, then the file transfer can be performed from C:\FTPROOT.
Note:
REQUIRED TOOLS
! ! ! !
Personal Computer (PC) running Windows NT, Windows 2000, or Windows XP HyperTerminal available on PC CoreDirector Switch software CD-ROM WFTPD (by Texas Imperial Software) File Transfer Protocol (FTP) server application or equivalent (such as wftpd32.exe or equivalent) The wftp FTP software is available at http://www.texis.com. FTP server PC for storing database backup files
PREREQUISITES
!
Disable firewalls on the FTP server or the file transfer will not work.
!
None
PROCEDURE
To copy system upgrade files to the site terminal (or laptop), perform Step 1 through Step 7. To install and configure WFTPD software, perform Step 8 through Step 16. STEP 1: Insert the CoreDirector Switch software CD-ROM into the site terminal (or laptop) CD-ROM drive. STEP 2: Double-click the My Computer icon on the site terminal (or laptop) Desktop. STEP 3: Double-click the D hard drive icon. This is the drive on which the FTP directory is created. If the site terminal (or laptop) does not have a D drive, then double-click the C drive icon. STEP 4: Create the directory D:\FTPROOT. If there is no D drive on the site terminal (or laptop), then create the directory C:\FTPROOT.

4 - 223
4
STEP 5: Return to the My Computer root level. Double-click the CD-ROM drive icon. CoreDirector Switch and CoreDirector CI Switch software builds are both available on the CD-ROM. When copying software files from the CD-ROM to the site terminal (or laptop) during Step 6, ensure that the correct .lnt and .zelf files for the system type are copied.
Note:
STEP 6: Copy the CoreDirector Switch system upgrade software (.lnt and .zelf) files from the CD-ROM to the D:\FTPROOT (or C:\FTPROOT) directory or the appropriate folder. The FTP application uses these files during the file transfer. STEP 7: Return to the My Computer root level. Double-click the CD-ROM drive icon. STEP 8: Double-click the wftpd32.exe icon and follow the installation instructions. STEP 9: At the WFTPD window, click the security tab and select user/rights. STEP 10: Select New User and then type upgrade as the user name. Click OK. STEP 11: Type upgrade as the New Password and as the Verify Password. Click OK. STEP 12: Type the directory path name containing the system upgrade files (D:\FTPROOT or C:\FTPROOT) in the Home Directory box. Click the Restricted to Home block. STEP 13: Click Rights and ensure that the Read, Write, and List blocks are checked. Click Done when completed. STEP 14: Click Logging and ensure that all blocks are checked except for Winsock Calls. Click OK when completed. STEP 15: If using the site terminal for software transfer, then obtain the site terminal Internet Protocol (IP) Address from the Start menu. a. b. c. d. Click Start. From the start menu, click Run. Type command and click OK. From the command window that is displayed, type ipconfig and press Enter. Write down the site terminal IP Address that is displayed (for example, 10.5.55.39) and retain this information for later use.
STEP 16: If using a laptop for software transfer, then change the IP Address of the laptop to a Static address that is in the same Network Domain as the CoreDirector Switch Main Management IP Address. Note: a. b. c. d. e. f. The following steps show how to configure IP address in a Win2000 PC.
Click Start. From the start menu, click Settings and then click Control Panel. Double click the Network icon. From the Network window, click Protocol tab. Click TCP/IP Protocol, and then click Properties. From the TCP/IP Properties window, select Specify an IP address. Type the Main Management IP Address of the CoreDirector Switch (for example, if the CoreDirector Switch Main Management IP Address is 192.168.238.145 then type an IP address such as 192.168.238.142). g. Type the Subnet Mask (for example, 255.255.255.0) and Default Gateway (for example, 192.168.238.1). Obtain any additional Subnet Mask and Gateway information from the site network administrator. h. Click OK. --STOP-THIS CONCLUDES THE PROCEDURE Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 224
4
TOP 280D RESETTING THE PRIMARY TIMING MODULE (TM SWITCH)

OVERVIEW
This Task-Oriented Practice resets the CoreDirector Switch or CoreDirector CI Primary Timing Module (TM) on equipment at the CoreDirector Switch. This procedure includes steps to check the secondary TM status before resetting the Primary TM.

Caution: Only perform this procedure when called for by a trouble clearing procedure or as directed by Ciena Technical Support. Do not perform this procedure without contacting Ciena Technical Support.
REQUIRED TOOLS
! ! ! ! !
! !
PREREQUISITES
!
! !

4 - 225
4
! ! ! !
CoreDirector Switch
TOP 174D Removing and Installing a Timing Module TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch TOP 278D Handling Circuit Packs Properly TOP 281D Resetting the Secondary Timing Module (TM)
PROCEDURE


Caution: This procedure could affect traffic if the Primary TM is reset when the Secondary TM Standby Status in not Hot standby. The CLI Menu display responses in the following procedure are typical and may not exactly match the actual responses.
Note:
To Prepare to Reset the Primary Timing Module, perform Step 1 and Step 2. To Connect to the CM, perform Step 3 through Step 6. To Reset the Primary TM, perform Step 7 through Step 11. To Verify TM Status, perform Step 12 through Step 14. Prepare to Reset the Primary Timing Module STEP 1: Establish a Node Manager session with the CoreDirector Switch. Note: Replaceable Unit alarms are reported if module alarm reporting is not disabled.
STEP 2: Determine TMs Role as follows: a. From the menu bar, select Go > Inventory. b. From the equipment tree, expand the CoreDirector node view and select TM1. c. From the Details frame, note the Procedural Status: Providing Service indicates Primary TM. Hot standby indicates Secondary TM. d. From the equipment tree, select the primary TM. e. In the Status box, change ARC State to No Alarm Reporting and click Accept. f. From the equipment tree, select the secondary TM (the secondary TM status will be checked in Step 11 after the primary TM is reset).
4 - 226
4
CoreDirector Switch
Connect to the CM STEP 3: At the CoreDirector Switch, connect to a CM and do one of the following:
!
Start a HyperTerminal session using TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch. Launch a Telnet session to the CoreDirector Switch virtual Internet Protocol (IP) address: a. From the Windows Start menu, select Run. b. Type telnet <CoreDirector IP address> and press Enter.
STEP 4: From a HyperTerminal session, press Enter and enter the User Id and Password. From a Telnet session, enter the User Id and Password. The CoreDirector Switch CLI Login prompt is displayed. STEP 5: Log in to the CoreDirector Switch CLI at an administrator level. STEP 6: If required, select the option to return to the CM CLI Menu The CM CLI Menu is displayed. Reset the Primary TM

Caution: Do not reset the Primary TM unless the Secondary TM Standby Status is Hot standby.
STEP 7: From the CM CLI Menu, type the option number to select Operations Menu and press Enter. The Operations Menu is displayed. STEP 8: From the Operations Menu, type the option number to Reset TM module and press Enter. STEP 9: Enter the primary TM (TM-1 or TM-2) and press Enter. Observe that the following message is displayed:
WARNING: The operation that you are about to invoke may be service affecting! Please confirm to continue with the reset of this TM? (Y/N)
STEP 10: Type Y and press Enter to confirm message and reboot the Primary TM. Observe that the following message is displayed:
TM reset request was successfully invoked.
STEP 11: From the Node Manager session, verify the Standby Status of the secondary TM established in Step 2 is now In service.

Caution: If the status is not In service or if timing alarms are generated, contact the next level of support immediately.
Verify TM Status STEP 12: From the Node Manager session, select the TM reset in Step 9. STEP 13: Verify that the Procedural Status for this TM is Hot Standby.

4 - 227
4
It normally takes up to five minutes for the TM to reboot. If the TM Procedural Status is not Hot standby after 10 minutes, perform TOP 281D Resetting the Secondary Timing Module (TM). If the problem persists, contact the next level technical support.
Note:
STEP 14: If required, change the TM ARC State to Alarm Reporting and click Accept. --STOP-THIS CONCLUDES THE PROCEDURE
4 - 228
4
TOP 281D RESETTING THE SECONDARY TIMING MODULE (TM)

OVERVIEW
This Task-Oriented Practice resets the CoreDirector or CoreDirector CI Secondary Timing Module (TM) on equipment at the CoreDirector Switch.

Caution: Only perform this procedure when called for by a trouble clearing procedure or as directed by Ciena Technical Support. Do not perform this procedure without contacting Ciena Technical Support.
REQUIRED TOOLS
! ! ! ! !
! !
PREREQUISITES
!
! !
! !
TOP 174D Removing and Installing a Timing Module TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch

4 - 229
4
! ! !
CoreDirector Switch
TOP 278D Handling Circuit Packs Properly TOP 280D Resetting the Primary Timing Module (TM Switch) Alarm and Trouble Clearing Procedure Manual
PROCEDURE


Caution: This procedure could affect traffic if the Primary TM is not In Service when the Secondary TM is reset. The CLI Menu display responses in the following procedure are typical and may not exactly match the actual responses.
Note:
To Prepare to Reset the Secondary Timing Module, perform Step 1 and Step 2. To Connect to the CM, perform Step 3 through Step 6. To Reset the Secondary TM, perform Step 7 through Step 10. To Verify TM Status, perform Step 11 through Step 13. Prepare to Reset the Secondary Timing Module STEP 1: Establish a Node Manager session with the CoreDirector Switch. Note: Replaceable Unit alarms are reported if module alarm reporting is not disabled.
STEP 2: Determine TMs Role as follows: a. From the menu bar, select Go > Inventory. b. From the equipment tree, expand the CoreDirector node view and select TM1. c. From the Details frame, note the Procedural Status: Providing service indicates Primary TM. Hot standby indicates Secondary TM. d. From the equipment tree, select TM2. e. From the Details frame, note the Procedural Status: Providing service indicates Primary TM. Hot standby indicates Secondary TM. f. From the equipment tree, select the secondary TM. g. In the Status box, change ARC State to No alarm reporting and click Accept. h. From the equipment tree, select the primary TM (the primary TM status will be checked in Step 10 after the secondary TM is reset).
4 - 230
4
Connect to the CM STEP 3: At the CoreDirector Switch, connect to a CM and do one of the following:
!
Start a HyperTerminal session using TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch. Launch a Telnet session to the CoreDirector virtual Internet Protocol (IP) address: a. From the Windows Start menu, select Run. b. Type telnet <CoreDirector IP address> and press Enter.
STEP 4: From a HyperTerminal session, press Enter and enter the User Id and Password. From a Telnet session, enter the User Id and Password. The CoreDirector CLI Login prompt is displayed. STEP 5: Log in to the CoreDirector CLI at an administrator level. STEP 6: If required, select the option to return to the CM CLI Menu The CM CLI Menu is displayed. Reset the Secondary TM

Caution: Do not reset the Secondary TM unless the primary TM is In Service. STEP 7: From the CM CLI Menu, type the option number to select Operations Menu and press Enter. The Operations Menu is displayed. STEP 8: From the Operations Menu, type the option number to Reset TM module and press Enter. STEP 9: Enter the secondary TM (TM-1 or TM-2) and press Enter. Observe that the following message is displayed:
TM reset request was successfully invoked.
STEP 10: From the Node Manager session, verify the Standby Status of the primary TM established in Step 2 is still In service.

Caution: If the status is not In service or if timing alarms are generated, contact the next level of support immediately.
Verify TM Status STEP 11: From the Node Manager session, select the TM reset in Step 9. STEP 12: Verify that the current role for this TM is Hot Standby. It normally takes up to five minutes for the TM to reboot. If the TM Procedural Status is not Hot standby after 10 minutes, proceed to Step 13. Then refer to the Alarm and Trouble Clearing Procedure Manual to clear the alarm that occurs after the TM is unlocked.
Note:
STEP 13: Unlock the TM by changing ARC State to Alarm Reporting and click Accept. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 231
4
4 - 232
4
TOP 282D DECOMMISSIONING A COREDIRECTOR SWITCH

OVERVIEW
This Task-Oriented Practice provides instructions to decommission an active CoreDirector Switch and remove it from its installed location.
Caution:

Do not perform this procedure without contacting Ciena Technical Support.
REQUIRED TOOLS
! ! !
PREREQUISITES
!
ESD-protective packaging must be available for all modules removed from the CoreDirector Switch. An approved shipping crate with hardware and a set of rack casters must be available for the CoreDirector rack. Appropriate packaging materials must be available for any accessory equipment that is removed from the CoreDirector rack. The user must follow proper module handling procedures when removing and handling modules. Refer to TOP 278D, Handling Circuit Packs Properly. The user should notify the Network Operations Center (NOC) that a Network Element (NE) is being removed from the network and should request permission to begin the procedure.
REFERENCE DOCUMENTS
! ! ! ! ! ! ! !
TOP 015D Verifying -48 VDC Supply Voltage TOP 072D Ciena Return Material Authorization (RMA) Procedure TOP 170D Removing and Installing a Control Module TOP 171D Removing and Installing a Switch Module TOP 172D Removing and Installing an Optical Module TOP 173D Removing and Installing a Line Module TOP 174D Removing and Installing a Timing Module TOP 278D Handling Circuit Packs Properly

4 - 233
4
CoreDirector Switch


Caution: This is a traffic-affecting procedure and must be properly coordinated with the NOC before starting the procedure. Do not continue until the proper safeguards are in place.
Preparation STEP 1: Contact the NOC and verify that all traffic has been removed from the CoreDirector Switch. STEP 2: Power down the switch as follows: a. At the CoreDirector Switch, open the PDU cover and set the circuit breakers to the OFF position. b. At the Battery Distribution Fuse Bay (BDFB), open the circuit breakers that provide -48 VDC power to the PDU, and tag them as DO NOT ENERGIZE. c. Verify that -48 VDC supply voltage is not present at the PDU power entry points using TOP 015D, Verifying -48 VDC Supply Voltage. STEP 3: Remove the front covers from the CoreDirector Switch and set them aside. STEP 4: Note the routing of all optical cables connected to the CoreDirector modules. Label all cables as required. Removing System Modules Refer to TOP 173D Removing and Installing a Line Module as required to perform the following steps. STEP 1: Remove and package all 10G OMs as follows: a. b. c. d. Disconnect all optical cables from the 10G OMs. Completely loosen the retaining screws at the top and bottom of each OM faceplate. Rotate the ejector levers to the open position to unseat the OM connector from the LM. Carefully slide the OM out of the LM, being careful not to scrape any OM components against the edges of the OM slot. e. If covers are available for the OM optical connectors, install covers over all the optical connectors. f. Place the OM into appropriate anti-static packaging. STEP 2: Remove and package all LM-8 2.5G or 155/622M OMs as follows: a. Completely loosen the retaining screws at the top and bottom of each OM faceplate. b. Using the T-handle, carefully slide the OM out of the LM, being careful not to scrape any OM components against the edges of the slot. c. Disconnect the optical cables from the OM. d. If covers are available for the OM optical connectors, install covers over all the optical connectors. e. Place the OM into appropriate anti-static packaging. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 234
4
STEP 3: Remove and package all Protected Equipment configuration LM-STM-1E LMs as follows: a. b. c. d. e. Disconnect the optical cables from the LM. Remove protected equipment configuration cover. Remove the Bridge Modules from LM and I/O-16-E. Remove the alignment plates from LM and I/O-16-E. Completely loosen the retaining screws at the top and bottom of each LM faceplate and I/O-16-E. f. Remove both LMs and I/O-16-E. g. Place the LMs and I/O-16-E into appropriate anti-static packaging. STEP 4: Remove and package all LM-20-E LMs as follows: a. b. c. d. a. b. c. d. Disconnect the optical cables from the LM GbE transceivers. Remove the LM GbE transceivers. Carefully slide the module out of the CoreDirector shelf slot. Place the LM and LM GbE transceivers into appropriate anti-static packaging. Completely loosen the retaining screws at the top and bottom of each module faceplate. Use the extractor levers to disconnect the module from the CoreDirector backplane. Carefully slide the module out of the CoreDirector shelf slot. Place the module into appropriate anti-static packaging.
STEP 5: Remove and package remaining LM, TS, TM, and LM modules as follows:
Disconnecting Power and Ground STEP 1: Disconnect the power cables as follows: a. Label all power cables. b. At the rear of the CoreDirector rack, remove the polycarbonate cover from the terminal block. c. Using a 3/8-inch socket or wrench, remove the nuts and washers securing the lugs to the terminal block, and disconnect the power cables. d. Replace the nuts and washers and polycarbonate cover on the terminal block. e. Cut and remove any cable ties or lacing that secure the power cables to the CoreDirector rack. STEP 2: Disconnect the facility ground cable as follows: a. Label the facility ground cable. b. Remove the hardware securing the ground cable to the CoreDirector rack and disconnect the cable. c. Cut and remove any cable ties or lacing that secure the ground cable to the CoreDirector rack. Removing Accessory Equipment STEP 1: If Interbay Management Panels (IMPs) are installed for fiber management, remove the panels from the CoreDirector rack as follows: a. Remove the fiber cables from the fiber management spools. b. Disconnect the fiber management panels from the mounting brackets. c. Remove the mounting brackets from the CoreDirector rack. STEP 2: If a rear kickplate is installed, remove the screws that secure the kickplate to the CoreDirector system rack, and set the kickplate aside. STEP 3: If filler boxes are installed at the base of the rack, remove the boxes as follows: a. If AC outlets are installed in the filler boxes, turn off the AC power source to the outlets. b. Remove the cover from each filler box. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 235
4
c. If fiber cables are routed through the filler boxes from under the floor, remove the cables from the fiber management inserts. d. Disconnect the power cables from the AC outlets in the filler boxes. e. Loosen the screws securing the filler boxes to the CoreDirector rack. f. Lift the filler boxes off the mounting screws. STEP 4: If an I/O panel cover is installed, remove the cover as follows: a. At the bottom of the I/O panel cover, completely loosen the captive screws securing the cover to each side of the rack. b. At the top of the I/O panel cover, loosen the screws securing the panel to each side of the rack. c. Lift the cover to disengage the top mounting keyholes, and slide the cover down until it clears the power lugs on the I/O panel. d. Remove the mounting screws from the rack. STEP 5: Disconnect all timing and Ethernet cables from the I/O panel. Detach the Rack from the Floor and Overhead Bracing Note: Certain rack installations may have a ground isolation plate installed between the rack base and the floor.
STEP 1: In a concrete floor installation, unbolt the CoreDirector rack from the floor as follows: a. b. c. d. Remove the lower air inlet cover from the rack. Remove the torque nuts securing the base of the rack to the floor. Remove the washers and hold-down plates from the threaded rods. Remove the threaded rods from the floor anchors.
STEP 2: In a raised floor installation, unbolt the CoreDirector rack from the floor as follows: a. Remove floor tiles as necessary to access the mounting hardware under the CoreDirector rack. b. Remove the lower air inlet cover from the rack. c. Remove the torque nuts securing the base of the rack to the floor. d. Remove the washers and hold-down plates from the threaded rods. e. Remove the nuts and washers from the threaded rods that are attached to the concrete floor under the CoreDirector rack. f. Remove the threaded rods. STEP 3: If the rack is attached to overhead bracing, remove the overhead auxiliary framing as follows: a. b. c. d. e. Remove the upper nut and clamp around the framing bars. Remove the insulating sleeve around the threaded rod. Loosen the lower nut until the lower clamp is free of the framing bars. Remove the bottom nut holding the threaded rod to the CoreDirector rack. Remove the rod and remaining hardware from the rack.
Preparing the Rack for Crating STEP 1: Attach the casters to the rack as follows: a. Carefully tilt the rack to one side and attach one set of casters to the opposite side using two Grade 5, 5/8-11 X 1 1/2 bolts with washers. b. Carefully tilt the rack toward the side with the casters in place and attach the second set of casters using two Grade 5, 5/8-11 X 1 1/2 bolts with washers. c. Securely tighten all bolts. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 236
4
CoreDirector Switch
STEP 2: Reattach all the covers to the CoreDirector rack. Crating the Rack Load the CoreDirector Switch into the shipping container as follows: STEP 1: If necessary, secure the crate back panel to the crate base using the two back panel braces with screws or nails (Figure 4-61).
Back Panel Brace Figure 4-61. Back Panel Attached to Base STEP 2: Place the front cover horizontally, positioning the holes on the cover on the dowels at the bottom front of the crate base (Figure 4-62). This creates a ramp for rolling the CoreDirector rack onto the crate base.

4 - 237
4
Dowels
Figure 4-62. Ramp STEP 3: Place the front and top retainer blocks under the ramp as braces (Figure 4-63).
Figure 4-63. Ramp Blocks in Place STEP 4: Carefully roll the CoreDirector rack up the ramp and onto the crate base. STEP 5: To secure the rear of the CoreDirector rack, install the rear block using two wing nuts, flat washers, and lock washers (Figure 4-64).
4 - 238
4
Figure 4-64. Rear Block STEP 6: To secure the front of the CoreDirector rack, install the front and top blocks (ramp supports) using four wing nuts, flat washers, and lock washers (Figure 4-65).
Wing Nuts Figure 4-65. Front and Top Blocks
Note:
The front wheels of the casters may have to be rotated inward in order to allow room for the front block to fit flush on its mounting.
STEP 7: Install the four side braces (marked 1, 2, 3, and 4) using two nuts, flat washers, and lock washers on each (Figure 4-66).

4 - 239
4
Figure 4-66. Side Braces STEP 8: Using a two-person team, slide the side and top crate panels into place around the CoreDirector rack and secure them with lag bolts (Figure 4-67) There are four bolts along each side and three across the bottom of each panel.
4 - 240
4
Bolt Locations
Bolt Detail
Figure 4-67. Bolts on the Side Panel STEP 9: Secure the front panel with four lag bolts on each side. STEP 10: If necessary, transport the CoreDirector crate to the shipping area. STEP 11: Notify appropriate personnel that the CoreDirector crate is ready for shipment. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 241
4
4 - 242
4
TOP 283D FTP SERVER SETUP

OVERVIEW
This Task-Oriented Practice prepares the site terminal or laptop for software transfer. System upgrade software for the CoreDirector Switch or CoreDirector CI Switch is downloaded to the primary CM through a File Transfer Protocol (FTP) application running on a site terminal or laptop computer. The procedure in this section describes how to copy system upgrade software files from a CD-ROM to the FTP directory, and how to install and configure the common FTP software package, WFTPD. WFTPD software by Texas Imperial Software or another FTP application must be running in order to transfer files from the site terminal or laptop. Files for transfer are copied from the CoreDirector Compact Disc (CD) to the D:\FTPROOT folder. If the site terminal or laptop hard drive is not partitioned and does not have a D drive, the file transfer can be performed from C:\FTPROOT.
Note:
REQUIRED TOOLS
! ! ! ! !
! !
PREREQUISITES
!
The user must use proper module handling procedures. When handling, installing, or removing modules, the following precautions must be observed. Refer to TOP 278D Handling Circuit Packs Properly on page 1-215. Ensure that modules are stored in ESD-protective packaging when not installed in an equipment shelf. Do not stack modules on or against each other. Pick up modules by the front handle, and do not touch components on the circuit board.
! !
The user must be familiar with CoreDirector Node Manager software. The user must have Node Manager Termination Point Provisioner privilege or Node Manager Troubleshooter (TS) privilege. Before performing this procedure, the following tasks must be performed: Current CoreDirector Switch alarms must be noted. The craftsperson must be a registered system user with a valid user name and password to log on to the Command Line Interface (CLI).

4 - 243
4
! ! ! ! !
CoreDirector Switch
TOP 174D Removing and Installing a Timing Module TOP 194D Connecting to the CM and Using a Laptop to Configure the CoreDirector Switch TOP 278D Handling Circuit Packs Properly TOP 280D Resetting the Primary Timing Module (TM Switch) Alarm and Trouble Clearing Procedure Manual
PROCEDURE

Caution: This equipment contains Electrostatic Discharge (ESD) sensitive devices. Wear grounding straps when handling equipment and follow ESD procedures. The CLI Menu display responses in the following procedure are typical and may not exactly match the actual responses.
Note:
Prepare Site Terminal or Laptop for Software Transfer To copy system upgrade files to the site terminal or laptop and to install and configure WFTPD software, perform the following steps. STEP 1: Insert the CoreDirector CD-ROM into the site terminal or laptop CD-ROM drive. STEP 2: Double-click the My Computer icon on the Desktop. STEP 3: Double-click the D hard drive icon. This is the drive on which the FTP directory is created. -If the site terminal or laptop does not have a D drive, double-click the C drive icon. STEP 4: Create the directory D:\FTPROOT. If there is no D drive on the site terminal or laptop, create the directory C:\FTPROOT. STEP 5: Return to the My Computer root level and double-click the CD-ROM drive icon. CoreDirector and CoreDirector CI software builds are both available on the CD-ROM. When copying software files from the CD-ROM to the site terminal or laptop during Step 6, make sure that the correct .lnt and .zelf files for the system type are copied. Incompatible differences between these system types (for example, number of shelves and capacity) will affect management efforts if the incorrect system software is downloaded to the primary CM during the software upgrade procedure.
Note:
STEP 6: Copy the CoreDirector system upgrade software files (.lnt and .zelf) from the CD-ROM to the D:\FTPROOT (or C:\FTPROOT) directory or the appropriate folder. The FTP application uses these files during the file transfer. Note: If an FTP software package is already installed on the site terminal or laptop by the site administrator, proceed to Step 15 on page 4-245.
STEP 7: Return to the My Computer root level and double-click the CD-ROM drive icon. STEP 8: Double-click the wftpd32.exe icon and follow the installation instructions. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
4 - 244
4
STEP 9: At the WFTPD window, click the security tab and select user/rights. STEP 10: Select New User and then type upgrade as the user name. Click OK. STEP 11: Type upgrade as the New Password and as the Verify Password. Click OK. STEP 12: Type the directory path name containing the system upgrade files (D:\FTPROOT or C:\FTPROOT) in the Home Directory box. Click the Restricted to Home block. STEP 13: Click Rights and verify that Read, Write, and List are selected. Click Done when completed. STEP 14: Click Logging and verify that all check boxes are selected except Winsock Calls. Click OK when completed. STEP 15: If the site terminal is being used for the software transfer, obtain the site terminal Internet Protocol (IP) address as follows: a. b. c. d. Click Start. From the start menu, click Run. Type command and click OK. From the command window that is displayed, type ipconfig and press Enter. Write down the site terminal IP address that is displayed (for example, 10.5.55.39) and retain this information for later use.
STEP 16: If a laptop is being used for software transfer, change the IP address of the laptop to a static address that is in the same network domain as the CoreDirector Main Management IP Address. To change the IP address: Note: a. b. c. d. e. f. The following steps show how to configure IP address in a Win2000 PC.
Click Start. From the start menu, click Settings and then click Control Panel. Double click the Network icon. From the Network window, click Protocol tab. Click TCP/IP Protocol, and then click Properties. From the TCP/IP Properties window, select Specify an IP address. Type the Main Management IP Address of the CoreDirector Switch (for example, if the CoreDirector Main Management IP Address is 192.168.238.145, type an IP address such as 192.168.238.142). g. Type the Subnet Mask (for example, 255.255.255.0) and Default Gateway (for example, 192.168.238.1). Obtain any additional Subnet Mask and Gateway information from the site network administrator. h. Click OK. --STOP-THIS CONCLUDES THE PROCEDURE

4 - 245
4
4 - 246
A
CoreDirector Switch CoreDirector Test Data Sheets
APPENDIX A COREDIRECTOR TEST DATA SHEETS

OVERVIEW
This section provides the test data sheets used in conjunction with the tasks required to test and verify proper system configuration and operation of the CoreDirector Switch. The data sheets include the following:
!
Data Sheet A-1 - CoreDirector Site Information Site Info (Section A) Pre-Test Check (Section B) System Grounding Tests () (Section C) Return Isolation Tests (Section D) PDU Voltage Test (VDC) (Section E) Power Terminal Isolation (Section F) LED Test (Section G) Fan Alarm Generation (Section H) Software Version (Section I) BITS DB-15 Port Test () (Section J) BITS DB-15 Cable Test () (Section K) SSU BNC Connector Test () (Section L) Data Sheet A-2 - CoreDirector Inventory Data Sheet A-3 - CoreDirector Spare Hardware Inventory and Testing Data Sheet A-4 - Module LED Status and Redundancy Tests Data Sheet A-5 - LM and OM LED Status and Functional Test Data Sheet A-6 - CoreDirector CM Configuration Parameters
! ! ! ! !
USING TEST DATA SHEETS

Test data sheets are used to record configuration and performance test data.

A-1
A
CoreDirector Test Data Sheets CoreDirector Switch
A-2
A
Data Sheet A-1. CoreDirector Site Information
Section A: Site Info Customer: Site: Route: Span Name: System: Bay Position: Onsite Supervisor: Ciena Lead Engineer: Ciena Test Engineers: Section F: Power Terminal Isolation A1 to B1 () A1 to B2 () Section B: Pre-Test Check Equipment Inventory (Data Sheet A-2) Area Clean Rack(s) Numbered Shelves and Systems Labeled Power and Misc Cabling BDFB Breakers Installed Fuse Panel/ Fuses Available Fiber Routed Fiber Labels on Both Ends Fiber Raceway Installed All Filler Panels Installed Section C: System Grounding Tests () PDU-to-Equipment Rack Ground Equipment Rack-to-Facility Ground Section H: Fan Alarm Generation Fan 1: Major (Replaceable Unit Missing) Fan 1: Minor (Fan Unit Not Synchronized) Fan 1: Critical (Bay Cooling Problem) Fan 2: Major (Replaceable Unit Missing) Fan 2: Minor (Fan Unit Not Synchronized) Fan 2: Critical (Bay Cooling Problem) Measured Other alarms noted (specify which fan): Y/N Section G: LED Test All LEDs lit Y/N Y/N Corrected A2 to B1 () A2 to B2 () Measured Date: WARNING: Verify correct polarity: Red lead to Neg (-) terminal; Black lead to Pos (+) terminal. Section E: PDU Voltage Test (VDC) A1 to A1R A2 to A2R B1 to B1R B2 to B2R NEG 48 VDC NEG 48 VDC NEG 48 VDC NEG 48 VDC Measured
Section D: Return Isolation Tests A1R to B1R Terminal Isolation () A1R to B2R Terminal Isolation () A2R to B1R Terminal Isolation () A2R to B2R Terminal Isolation ()
Measured
Section I: Software Version
Note: Explain problems and record corrective action taken on attached Discrepancy List.

A-3
A
Data Sheet A-1. CoreDirector Site Information (Continued)
Section J: BITS DB-15 Port Test () Pin 2 to outer shell open Pin 4 to outer shell open
Y/N
Section L: SSU BNC Connector Test () J2 (BITS 2 RX) center conductor to outer shell 80 to 100 J3 (BITS 1 RX) center conductor to outer shell 80 to 10 J6 (BITS 2 TX) center conductor to outer shell 10 M (open) J7 (BITS 1 TX) center conductor to outer shell 10 M (open) J2 (BITS 2 RX) outer shell to chassis ground 10 M (open) J3 (BITS 1 RX) outer shell to chassis ground 10 M (open) J6 (BITS 2 TX) outer shell to chassis ground 1 J7 (BITS 1 TX) outer shell to chassis ground 1
Y/N
Section K: BITS DB-15 Cable Test () Y/N BITS 1: Pin 2 to outer shell open BITS 1: Pin 4 to outer shell open BITS 2: Pin 2 to outer shell open BITS 2: Pin 4 to outer shell open
Note: Explain problems and record corrective action taken on attached Discrepancy List.
Discrepancy List
A-4
A
Data Sheet A-2. CoreDirector Inventory Module FPM 1 FPM 2 FM 1 FM 2 C/B C/B CM A CM B TM 1 TM 2 SM SM SM SM SM SM SM SM SM SM SM SM SM SM SM LM A1* OM OM OM OM OM OM OM OM Slot PDU PDU FM-1 FM-2 A-BAT B-BAT A-CM C-CM B-TM 1 B-TM 2 B-1 B-2 B-3 B-4 B-5 B-6 B-7 B-8 B-9 B-10 B-11 B-12 B-13 B-14 B-15 A-1 A-1-1 A-1-2 A-1-3 A-1-4 A-1-5 A-1-6 A-1-7 A-1-8 Part Number Hardware Revision Serial Number
*LM-16 Line Modules and LM-20 Line Modules use integrated Optical Ports (OPs). These OPs cannot be inventoried.

A-5
A
Data Sheet A-2. CoreDirector Inventory (Continued) Module LM A2* OM OM OM OM OM OM OM OM LM A3* OM OM OM OM OM OM OM OM LM A4* OM OM OM OM OM OM OM OM Slot A-2 A-2-1 A-2-2 A-2-3 A-2-4 A-2-5 A-2-6 A-2-7 A-2-8 A-3 A-3-1 A-3-2 A-3-3 A-3-4 A-3-5 A-3-6 A-3-7 A-3-8 A-4 A-4-1 A-4-2 A-4-3 A-4-4 A-4-5 A-4-6 A-4-7 A-4-8 Part Number Hardware Revision Serial Number
A-6
A

A-7
A
A-8
A

A-9
A
A - 10
A
Data Sheet A-2. CoreDirector Inventory (Continued) Module LM C1* OM OM OM OM OM OM OM OM LM C2* OM OM OM OM OM OM OM OM LM C3* OM OM OM OM OM OM OM OM Slot C-1 C-1-1 C-1-2 C-1-3 C-1-4 C-1-5 C-1-6 C-1-7 C-1-8 C-2 C-2-1 C-2-2 C-2-3 C-2-4 C-2-5 C-2-6 C-2-7 C-2-8 C-3 C-3-1 C-3-2 C-3-3 C-3-4 C-3-5 C-3-6 C-3-7 C-3-8 Part Number Hardware Revision Serial Number

A - 11
A
A - 12
A

A - 13
A
Data Sheet A-2. CoreDirector Inventory (Continued) Module LM C10* OM OM OM OM OM OM OM OM LM C11 OM OM OM OM OM OM OM OM LM C12 OM OM OM OM OM OM OM OM LM C13* OM OM OM OM OM OM Slot C-10 C-10-1 C-10-2 C-10-3 C-10-4 C-10-5 C-10-6 C-10-7 C-10-8 C-11 C-11-1 C-11-2 C-11-3 C-11-4 C-11-5 C-11-6 C-11-7 C-11-8 C-12 C-12-1 C-12-2 C-12-3 C-12-4 C-12-5 C-12-6 C-12-7 C-12-8 C-13 C-13-1 C-13-2 C-13-3 C-13-4 C-13-5 C-13-6 Part Number Hardware Revision Serial Number
A - 14
A
Data Sheet A-2. CoreDirector Inventory (Continued) Module OM OM LM C14* OM OM OM OM OM OM OM OM LM C15* OM OM OM OM OM OM OM OM LM C16* OM OM OM OM OM OM OM OM Slot C-13-7 C-13-8 C-14 C-14-1 C-14-2 C-14-3 C-14-4 C-14-5 C-14-6 C-14-7 C-14-8 C-15 C-15-1 C-15-2 C-15-3 C-15-4 C-15-5 C-15-6 C-15-7 C-15-8 C-16 C-16-1 C-16-2 C-16-3 C-16-4 C-16-5 C-16-6 C-16-7 C-16-8 Part Number Hardware Revision Serial Number

A - 15
A
A - 16
A
Data Sheet A-3. CoreDirector Spare Hardware Inventory and Testing Module Type FPM FPM Fan Unit Fan Load: Fan Speed Fan Unit Fan Load: Fan Speed CM CM TM TM SM SM SM LM LM LM OM OM OM OM OM Air Filter Air Filter Air Filter N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A Part Number Hardware Revision N/A N/A N/A N/A Serial Number Test Result N/A N/A N/A N/A Date

A - 17
A
Data Sheet A-4. Module LED Status and Redundancy Tests Module FPM 1 FPM 2 Fan 1 Fan 2 C/B C/B CM A CM B TM 1 TM 2 SM SM SM SM SM SM SM SM SM SM SM SM SM SM SM PDU PDU FM-1 FM-2 A-BAT B-BAT A-CM C-CM B-TM1 B-TM2 B-1 B-2 B-3 B-4 B-5 B-6 B-7 B-8 B-9 B-10 B-11 B-12 B-13 B-14 B-15 Slot Module LED Status Redundancy Checks
Note: Indicate either Pass or Fail in the appropriate field for LED Status or Redundancy Checks
A - 18
A
Data Sheet A-5. LM and OM LED Status and Functional Test Module/ Port LM A1* Slot A-1 1 A-1-1 2 A-1-2 3 A-1-3 4 A-1-4 5 A-1-5 6 A-1-6 7 A-1-7 8 A-1-8 9 A-1-9 10 A-1-10 11 A-1-11 12 A-1-12 13 A-1-13 14 A-1-14 15 A-1-15 16 A-1-16 17 A-1-17 18 A-1-18 19 A-1-19 20 A-1-20 LM A2* A-2 1 A-2-1 2 A-2-2 3 A-2-3 4 A-2-4 5 A-2-5 6 A-2-6 7 A-2-7 8 A-2-8 9 A-2-9 10 A-2-10 11 A-2-11 12 A-2-12 13 A-2-13 14 A-2-14 Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
Module LED Status
OM Output Power Level
Normal Signal Flow
OCC to CoreStream (OM-10G WDM Only)
A - 19
A
Data Sheet A-5. LM and OM LED Status and Functional Test (Continued) Module/ Port Slot Module LED Status OM Output Power Level Normal Signal Flow OCC to CoreStream (OM-10G WDM Only)
15 A-2-15 16 A-2-16 17 A-2-17 18 A-2-18 19 A-2-19 20 A-2-20 LM A3* A-3 1 A-3-1 2 A-3-2 3 A-3-3 4 A-3-4 5 A-3-5 6 A-3-6 7 A-3-7 8 A-3-8 9 A-3-9 10 A-3-10 11 A-3-11 12 A-3-12 13 A-3-13 14 A-3-14 15 A-3-15 16 A-3-16 17 A-3-17 18 A-3-18 19 A-3-19 20 A-3-20 LM A4* A-4 1 A-4-1 2 A-4-2 3 A-4-3 4 A-4-4 5 A-4-5 6 A-4-6 7 A-4-7 8 A-4-8
A - 20
A
9 A-4-9 10 A-4-10 11 A-4-11 12 A-4-12 13 A-4-13 14 A-4-14 15 A-4-15 16 A-4-16 17 A-4-17 18 A-4-18 19 A-4-19 20 A-4-20 LM A5* A-5 1 A-5-1 2 A-5-2 3 A-5-3 4 A-5-4 5 A-5-5 6 A-5-6 7 A-5-7 8 A-5-8 9 A-5-9 10 A-5-10 11 A-5-11 12 A-5-12 13 A-5-13 14 A-5-14 15 A-5-15 16 A-5-16 17 A-5-17 18 A-5-18 19 A-5-19 20 A-5-20 LM A6* A-6 1 A-6-1 2 A-6-2

A - 21
A
3 A-6-3 4 A-6-4 5 A-6-5 6 A-6-6 7 A-6-7 8 A-6-8 9 A-6-9 10 A-6-10 11 A-6-11 12 A-6-12 13 A-6-13 14 A-6-14 15 A-6-15 16 A-6-16 17 A-6-17 18 A-6-18 19 A-6-19 20 A-6-20 LM A7* A-7 1 A-7-1 2 A-7-2 3 A-7-3 4 A-7-4 5 A-7-5 6 A-7-6 7 A-7-7 8 A-7-8 9 A-7-9 10 A-7-10 11 A-7-11 12 A-7-12 13 A-7-13 14 A-7-14 15 A-7-15 16 A-7-16 17 A-7-17
A - 22
A
18 A-7-18 19 A-7-19 20 A-7-20 LM A8* A-8 1 A-8-1 2 A-8-2 3 A-8-3 4 A-8-4 5 A-8-5 6 A-8-6 7 A-8-7 8 A-8-8 9 A-8-9 10 A-8-10 11 A-8-11 12 A-8-12 13 A-8-13 14 A-8-14 15 A-8-15 16 A-8-16 17 A-8-17 18 A-8-18 19 A-8-19 20 A-8-20 LM A9* A-9 1 A-9-1 2 A-9-2 3 A-9-3 4 A-9-4 5 A-9-5 6 A-9-6 7 A-9-7 8 A-9-8 9 A-9-9 10 A-9-10 11 A-9-11

A - 23
A
12 A-9-12 13 A-9-13 14 A-9-14 15 A-9-15 16 A-9-16 17 A-9-17 18 A-9-18 19 A-9-19 20 A-9-20 LM A10* A-10 1 A-10-1 2 A-10-2 3 A-10-3 4 A-10-4 5 A-10-5 6 A-10-6 7 A-10-7 8 A-10-8 9 A-10-9 10 A-10-10 11 A-10-11 12 A-10-12 13 A-10-13 14 A-10-14 15 A-10-15 16 A-10-16 17 A-10-17 18 A-10-18 19 A-10-19 20 A-10-20 LM A11* A-11 1 A-11-1 2 A-11-2 3 A-11-3 4 A-11-4 5 A-11-5
A - 24
A
6 A-11-6 7 A-11-7 8 A-11-8 9 A-11-9 10 A-11-10 11 A-11-11 12 A-11-12 13 A-11-13 14 A-11-14 15 A-11-15 16 A-11-16 17 A-11-17 18 A-11-18 19 A-11-19 20 A-11-20 LM A12* A-12 1 A-12-1 2 A-12-2 3 A-12-3 4 A-12-4 5 A-12-5 6 A-12-6 7 A-12-7 8 A-12-8 9 A-12-9 10 A-12-10 11 A-12-11 12 A-12-12 13 A-12-13 14 A-12-14 15 A-12-15 16 A-12-16 17 A-12-17 18 A-12-18 19 A-12-19 20 A-12-20

A - 25
A
Data Sheet A-5. LM and OM LED Status and Functional Test (Continued) Module/ Port LM A13* Slot A-13 1 A-13-1 2 A-13-2 3 A-13-3 4 A-13-4 5 A-13-5 6 A-13-6 7 A-13-7 8 A-13-8 9 A-13-9 10 A-13-10 11 A-13-11 12 A-13-12 13 A-13-13 14 A-13-14 15 A-13-15 16 A-13-16 17 A-13-17 18 A-13-18 19 A-13-19 20 A-13-20 LM A14* A-14 1 A-14-1 2 A-14-2 3 A-14-3 4 A-14-4 5 A-14-5 6 A-14-6 7 A-14-7 8 A-14-8 9 A-14-9 10 A-14-10 11 A-14-11 12 A-14-12 13 A-14-13 14 A-14-14 Module LED Status OM Output Power Level Normal Signal Flow OCC to CoreStream (OM-10G WDM Only)
A - 26
A
15 A-14-15 16 A-14-16 17 A-14-17 18 A-14-18 19 A-14-19 20 A-14-20 LM A15* A-15 1 A-15-1 2 A-15-2 3 A-15-3 4 A-15-4 5 A-15-5 6 A-15-6 7 A-15-7 8 A-15-8 9 A-15-9 10 A-15-10 11 A-15-11 12 A-15-12 13 A-15-13 14 A-15-14 15 A-15-15 16 A-15-16 17 A-15-17 18 A-15-18 19 A-15-19 20 A-15-20 LM A16* A-16 1 A-16-1 2 A-16-2 3 A-16-3 4 A-16-4 5 A-16-5 6 A-16-6 7 A-16-7 8 A-16-8

A - 27
A
9 A-16-9 10 A-16-10 11 A-16-11 12 A-16-12 13 A-16-13 14 A-16-14 15 A-16-15 16 A-16-16 17 A-16-17 18 A-16-18 19 A-16-19 20 A-16-20 LM C1* C-1 1 C-1-1 2 C-1-2 3 C-1-3 4 C-1-4 5 C-1-5 6 C-1-6 7 C-1-7 8 C-1-8 9 C-1-9 10 C-1-10 11 C-1-11 12 C-1-12 13 C-1-13 14 C-1-14 15 C-1-15 16 C-1-16 17 C-1-17 18 C-1-18 19 C-1-19 20 C-1-20 LM C2* C-2 1 C-2-1 2 C-2-2
A - 28
A
3 C-2-3 4 C-2-4 5 C-2-5 6 C-2-6 7 C-2-7 8 C-2-8 9 C-2-9 10 C-2-10 11 C-2-11 12 C-2-12 13 C-2-13 14 C-2-14 15 C-2-15 16 C-2-16 17 C-2-17 18 C-2-18 19 C-2-19 20 C-2-20 LM C3* C-3 1 C-3-1 2 C-3-2 3 C-3-3 4 C-3-4 5 C-3-5 6 C-3-6 7 C-3-7 8 C-3-8 9 C-3-9 10 C-3-10 11 C-3-11 12 C-3-12 13 C-3-13 14 C-3-14 15 C-3-15 16 C-3-16 17 C-3-17

A - 29
A
18 C-3-18 19 C-3-19 20 C-3-20 LM C4* C-4 1 C-4-1 2 C-4-2 3 C-4-3 4 C-4-4 5 C-4-5 6 C-4-6 7 C-4-7 8 C-4-8 9 C-4-9 10 C-4-10 11 C-4-11 12 C-4-12 13 C-4-13 14 C-4-14 15 C-4-15 16 C-4-16 17 C-4-17 18 C-4-18 19 C-4-19 20 C-4-20 LM C5* C-5 1 C-5-1 2 C-5-2 3 C-5-3 4 C-5-4 5 C-5-5 6 C-5-6 7 C-5-7 8 C-5-8 9 C-5-9 10 C-5-10 11 C-5-11
A - 30
A
12 C-5-12 13 C-5-13 14 C-5-14 15 C-5-15 16 C-5-16 17 C-5-17 18 C-5-18 19 C-5-19 20 C-5-20 LM C6* C-6 1 C-6-1 2 C-6-2 3 C-6-3 4 C-6-4 5 C-6-5 6 C-6-6 7 C-6-7 8 C-6-8 9 C-6-9 10 C-6-10 11 C-6-11 12 C-6-12 13 C-6-13 14 C-6-14 15 C-6-15 16 C-6-16 17 C-6-17 18 C-6-18 19 C-6-19 20 C-6-20 LM C7* C-7 1 C-7-1 2 C-7-2 3 C-7-3 4 C-7-4 5 C-7-5

A - 31
A
6 C-7-6 7 C-7-7 8 C-7-8 9 C-7-9 10 C-7-10 11 C-7-11 12 C-7-12 13 C-7-13 14 C-7-14 15 C-7-15 16 C-7-16 17 C-7-17 18 C-7-18 19 C-7-19 20 C-7-20 LM C8* C-8 1 C-8-1 2 C-8-2 3 C-8-3 4 C-8-4 5 C-8-5 6 C-8-6 7 C-8-7 8 C-8-8 9 C-8-9 10 C-8-10 11 C-8-11 12 C-8-12 13 C-8-13 14 C-8-14 15 C-8-15 16 C-8-16 17 C-8-17 18 C-8-18 19 C-8-19 20 C-8-20
A - 32
A
Data Sheet A-5. LM and OM LED Status and Functional Test (Continued) Module/ Port LM C9* Slot C-9 1 C-9-1 2 C-9-2 3 C-9-3 4 C-9-4 5 C-9-5 6 C-9-6 7 C-9-7 8 C-9-8 9 C-9-9 10 C-9-10 11 C-9-11 12 C-9-12 13 C-9-13 14 C-9-14 15 C-9-15 16 C-9-16 17 C-9-17 18 C-9-18 19 C-9-19 20 C-9-20 LM C10* C-10 1 C-10-1 2 C-10-2 3 C-10-3 4 C-10-4 5 C-10-5 6 C-10-6 7 C-10-7 8 C-10-8 9 C-10-9 10 C-10-10 11 C-10-11 12 C-10-12 13 C-10-13 14 C-10-14 Module LED Status OM Output Power Level Normal Signal Flow OCC to CoreStream (OM-10G WDM Only)

A - 33
A
15 C-10-15 16 C-10-16 17 C-10-17 18 C-10-18 19 C-10-19 20 C-10-20 LM C11* C-11 1 C-11-1 2 C-11-2 3 C-11-3 4 C-11-4 5 C-11-5 6 C-11-6 7 C-11-7 8 C-11-8 9 C-11-9 10 C-11-10 11 C-11-11 12 C-11-12 13 C-11-13 14 C-11-14 15 C-11-15 16 C-11-16 17 C-11-17 18 C-11-18 19 C-11-19 20 C-11-20 LM C12* C-12 1 C-12-1 2 C-12-2 3 C-12-3 4 C-12-4 5 C-12-5 6 C-12-6 7 C-12-7 8 C-12-8
A - 34
A
9 C-12-9 10 C-12-10 11 C-12-11 12 C-12-12 13 C-12-13 14 C-12-14 15 C-12-15 16 C-12-16 17 C-12-17 18 C-12-18 19 C-12-19 20 C-12-20 LM C13* C-13 1 C-13-1 2 C-13-2 3 C-13-3 4 C-13-4 5 C-13-5 6 C-13-6 7 C-13-7 8 C-13-8 9 C-13-9 10 C-13-10 11 C-13-11 12 C-13-12 13 C-13-13 14 C-13-14 15 C-13-15 16 C-13-16 17 C-13-17 18 C-13-18 19 C-13-19 20 C-13-20 LM C14* C-14 1 C-14-1 2 C-14-2

A - 35
A
3 C-14-3 4 C-14-4 5 C-14-5 6 C-14-6 7 C-14-7 8 C-14-8 9 C-14-9 10 C-14-10 11 C-14-11 12 C-14-12 13 C-14-13 14 C-14-14 15 C-14-15 16 C-14-16 17 C-14-17 18 C-14-18 19 C-14-19 20 C-14-20 LM C15* C-15 1 C-15-1 2 C-15-2 3 C-15-3 4 C-15-4 5 C-15-5 6 C-15-6 7 C-15-7 8 C-15-8 9 C-15-9 10 C-15-10 11 C-15-11 12 C-15-12 13 C-15-13 14 C-15-14 15 C-15-15 16 C-15-16 17 C-15-17
A - 36
A
18 C-15-18 19 C-15-19 20 C-15-20 LM C16* C-16 1 C-16-1 2 C-16-2 3 C-16-3 4 C-16-4 5 C-16-5 6 C-16-6 7 C-16-7 8 C-16-8 9 C-16-9 10 C-16-10 11 C-16-11 12 C-16-12 13 C-16-13 14 C-16-14 15 C-16-15 16 C-16-16 17 C-16-17 18 C-16-18 19 C-16-19 20 C-16-20

A - 37
A
Data Sheet A-6. CoreDirector CM Configuration Parameters CM Configuration Parameters CM name: CoreDirector main management IP address: CoreDirector main management IP address netmask CoreDirector internal network base address: A-CM main IP address: A-CM main IP address netmask: C-CM main IP address: C-CM main IP address netmask: CoreDirector IP gateway address: OSRP node address: A-CM auxiliary IP address (optional): A-CM auxiliary IP address netmask (optional): C-CM auxiliary IP address (optional): C-CM auxiliary IP address netmask (optional): CoreDirector CORBA BOA main port number (optional): CoreDirector TLI module port number (optional): CoreDirector HTTP port number (optional): CoreDirector echo port number (optional): CoreDirector OSI System ID (optional):
A - 38
B
CoreDirector Switch CoreDirector CI Test Data Sheets
APPENDIX B COREDIRECTOR CI TEST DATA SHEETS

OVERVIEW
This section provides the test data sheets used in conjunction with the tasks required to test and verify proper system configuration and operation of the CoreDirector CI Switch. The data sheets include the following:
!
Data Sheet B-1 Site Information (Section A) Pre-Test Checklist (Section B) System Grounding Test (Section D) Minus 48VDC Supply (PDU) Voltage Test (Section E) Light Emitting Diode (LED) Test (Section G) Fan Alarm Generation Test (Section H) Data Sheet B-2 - CoreDirector CI Timing Cable Tests BITS RJ-45 Cable Test (Section A and Section B) BITS BNC Coaxial Cable Test (Section C and Section D) Data Sheet B-3 - CoreDirector CI Inventory Data Sheet B-4 - CoreDirector CI Spare Hardware Inventory and Testing Data Sheet B-5 - Module LED Status and Redundancy Tests Data Sheet B-6 - LM and OM LED Status and Functional Test Data Sheet B-7 - CoreDirector CI CM Configuration Parameters
! ! ! ! !
USING TEST DATA SHEETS

Test data sheets are used to record configuration and performance test data.

B-1
B
CoreDirector CI Test Data Sheets CoreDirector Switch
B-2
B
Data Sheet B-1. CoreDirector CI Site Information
Section A: Site Info
Date:
Section D: System Grounding Tests () Measured
Customer: Site: Route: Span Name: System: Bay Position: Onsite Supervisor: Ciena Lead Engineer: Ciena Test Engineers:
Section B: Pre-Test Check
PDU-to-Equipment Rack Ground Equipment Rack-to-Facility Ground
WARNING: Verify correct polarity: Red lead to Neg (-) terminal; Black lead to Pos (+) terminal
Section E: PDU Voltage Test (VDC)
Measured
A to A RET B to B RET Y/N Corrected
NEG 48 VDC NEG 48 VDC Measured
Section F: Terminal Isolation
Equipment Inventory (Data Sheet B-4) Area Clean Rack(s) Numbered Shelves and Systems Labeled Power and Misc Cabling BDFB Breakers Installed Fuse Panel/ Fuses Available Fiber Routed Fiber Labels on Both Ends Blank Filler Panels Installed
Section C: Software Version
A to B Return Terminal Isolation () A to B Power Terminal Isolation () Y/ N
Section G: LED Test
All LEDs lit Y/ N
Section H: Fan Alarm Generation
Fan 1: Major (Replaceable Unit Missing) Fan 1: Minor (Fan Unit Not Synchronized) Fan 1: Critical (Bay Cooling Problem) Fan 2: Major (Replaceable Unit Missing) Fan 2: Minor (Fan Unit Not Synchronized) Fan 2: Critical (Bay Cooling Problem) Other alarms noted (specify which fan):
Note: Explain problems and record corrective action taken on attached Discrepancy List. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
B-3
B
Data Sheet B-2. CoreDirector CI Timing Cable Tests
Section A: BITS RJ-45 Cable Test () (BITS 1) Color Y/N Section B: BITS RJ-45 Cable Test () Color (BITS 2) Y/N
Pin 1 to far end wire 1 Pin 2 to far end wire 1 Cable shield to wire for Pin 1open Cable shield to Pin 1 open Cable shield to wire for Pin 2 open Cable shield to Pin 2 open
Section C: BITS BNC Connector Test ()
Pin 1 to far end wire 1 Pin 2 to far end wire 1 Cable shield to wire for Pin 1open Cable shield to Pin 1 open Cable shield to wire for Pin 2 open Cable shield to Pin 2 open Y/N
BITS 1 TX center conductor to outer shell open BITS 1 RX center conductor to outer shell 70-90 BITS 2 TX center conductor to outer shell open BITS 2 RX center conductor to outer shell 70-90 BITS 1 TX outer shell to chassis ground 1 BITS 2 TX outer shell to chassis ground 1 BITS 1 RX outer shell to chassis ground open BITS 2 RX outer shell to chassis ground open Note: Explain problems and record corrective action taken on attached Discrepancy List. Discrepancy List
B-4
B
Data Sheet B-3. CoreDirector CI Inventory Module FM 1 FM 2 C/B C/B CM A CM B TM 1 TM 2 SM SM SM SM LM 1 * OM OM OM OM OM OM OM OM LM 2 * OM OM OM OM OM OM OM OM LM 3* OM OM OM Slot FM-1 FM-2 A-BAT B-BAT A-CM1 A-CM2 A-TM 1 A-TM 2 A-SM1 A-SM2 A-SM3 A-SM4 A-1 A-1-1 A-1-2 A-1-3 A-1-4 A-1-5 A-1-6 A-1-7 A-1-8 A-2 A-2-1 A-2-2 A-2-3 A-2-4 A-2-5 A-2-6 A-2-7 A-2-8 A-3 A-3-1 A-3-2 A-3-3 Part Number Hardware Revision Serial Number
*LM-16 Line Modules and LM-20 Line Modules use integrated ports. Integrated ports cannot be inventoried. Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
B-5
B
Data Sheet B-3. CoreDirector CI Inventory (Continued) Module OM OM OM OM OM LM 4* OM OM OM OM OM OM OM OM LM 5 * OM OM OM OM OM OM OM OM LM A6* OM OM OM OM OM OM OM OM LM A7* OM Slot A-3-4 A-3-5 A-3-6 A-3-7 A-3-8 A-4 A-4-1 A-4-2 A-4-3 A-4-4 A-4-5 A-4-6 A-4-7 A-4-8 A-5 A-5-1 A-5-2 A-5-3 A-5-4 A-5-5 A-5-6 A-5-7 A-5-8 A-6 A-6-1 A-6-2 A-6-3 A-6-4 A-6-5 A-6-6 A-6-7 A-6-8 A-7 A-7-1 Part Number Hardware Revision Serial Number
*LM-16 Line Modules and LM-20 Line Modules use integrated ports. Integrated ports cannot be inventoried.
B-6
B
Data Sheet B-3. CoreDirector CI Inventory (Continued) Module OM OM OM OM OM OM OM OM OM OM OM OM OM OM OM Slot A-7-2 A-7-3 A-7-4 A-7-5 A-7-6 A-7-7 A-7-8 A-8-1 A-8-2 A-8-3 A-8-4 A-8-5 A-8-6 A-8-7 A-8-8 Part Number Hardware Revision Serial Number
*LM-16 Line Modules and LM-20 Line Modules use integrated ports. Integrated ports cannot be inventoried. Data Sheet B-4. CoreDirector CI Spare Hardware Inventory and Testing Module FPM Fan Fan Load: Fan Speed: CM TM SM SM LM LM OM OM OM OM Air Filter N/A N/A N/A N/A N/A N/A Part Number Hardware Revision N/A N/A Serial Number Test Result N/A Date N/A

B-7
B
Data Sheet B-5. Module LED Status and Redundancy Tests Module FM 1 FM 2 C/B C/B CM A CM B TM 1 TM 2 SM SM SM SM FM-1 FM-2 A-BAT B-BAT A-CM1 A-CM2 A-TM1 A-TM2 A-SM1 A-SM2 A-SM3 A-SM4 Data Sheet B-6. LM and OM LED Status and Functional Test Module/ Port LM 1* Slot A-1 1 A-1-1 2 A-1-2 3 A-1-3 4 A-1-4 5 A-1-5 6 A-1-6 7 A-1-7 8 A-1-8 9 A-1-9 10 A-1-10 11 A-1-11 12 A-1-12 13 A-1-13 14 A-1-14 15 A-1-15 16 A-1-16 17 A-1-17 18 A-1-18 19 A-1-19 Module LED Status OM Output Power Level Normal Signal Flow OCC to CoreStream (OM-10G WDM Only) Slot Module LED Status Redundancy Checks
Note: Indicate either Pass or Fail in the appropriate field for LED Status or Redundancy Checks.
B-8
B
Data Sheet B-6. LM and OM LED Status and Functional Test (Continued) Module/ Port LM 2* Slot A-2 1 A-2-1 2 A-2-2 3 A-2-3 4 A-2-4 5 A-2-5 6 A-2-6 7 A-2-7 8 A-2-8 9 A-2-9 10 A-2-10 11 A-2-11 12 A-2-12 13 A-2-13 14 A-2-14 15 A-2-15 16 A-2-16 17 A-2-17 18 A-2-18 19 A-2-19 20 A-2-20 LM 3* A-3 1 A-3-1 2 A-3-2 3 A-3-3 4 A-3-4 5 A-3-5 6 A-3-6 7 A-3-7 8 A-3-8 9 A-3-9 10 A-3-10 11 A-3-11 12 A-3-12 13 A-3-13 Module LED Status OM Output Power Level Normal Signal Flow OCC to CoreStream (OM-10G WDM Only)
20 A-1-20

B-9
B
Data Sheet B-6. LM and OM LED Status and Functional Test (Continued) Module/ Port Slot Module LED Status OM Output Power Level Normal Signal Flow OCC to CoreStream (OM-10G WDM Only)
14 A-3-14 15 A-3-15 16 A-3-16 17 A-3-17 18 A-3-18 19 A-3-19 20 A-3-20 LM 4* A-4 1 A-4-1 2 A-4-2 3 A-4-3 4 A-4-4 5 A-4-5 6 A-4-6 7 A-4-7 8 A-4-8 9 A-4-9 10 A-4-10 11 A-4-11 12 A-4-12 13 A-4-13 14 A-4-14 15 A-4-15 16 A-4-16 17 A-4-17 18 A-4-18 19 A-4-19 20 A-4-20 LM 5* A-5 1 A-5-1 2 A-5-2 3 A-5-3 4 A-5-4 5 A-5-5 6 A-5-6 7 A-5-7
B - 10
B
8 A-5-8 9 A-5-9 10 A-5-10 11 A-5-11 12 A-5-12 13 A-5-13 14 A-5-14 15 A-5-15 16 A-5-16 17 A-5-17 18 A-5-18 19 A-5-19 20 A-5-20 LM 6* A-6 1 A-6-1 2 A-6-2 3 A-6-3 4 A-6-4 5 A-6-5 6 A-6-6 7 A-6-7 8 A-6-8 9 A-6-9 10 A-6-10 11 A-6-11 12 A-6-12 13 A-6-13 14 A-6-14 15 A-6-15 16 A-6-16 17 A-6-17 18 A-6-18 19 A-6-19 20 A-6-20 LM 7* A-7 1 A-7-1

B - 11
B
2 A-7-2 3 A-7-3 4 A-7-4 5 A-7-5 6 A-7-6 7 A-7-7 8 A-7-8 9 A-7-9 10 A-7-10 11 A-7-11 12 A-7-12 13 A-7-13 14 A-7-14 15 A-7-15 16 A-7-16 17 A-7-17 18 A-7-18 19 A-7-19 20 A-7-20 LM 8* A-8 1 A-8-1 2 A-8-2 3 A-8-3 4 A-8-4 5 A-8-5 6 A-8-6 7 A-8-7 8 A-8-8 9 A-8-9 10 A-8-10 11 A-8-11 12 A-8-12 13 A-8-13 14 A-8-14 15 A-8-15 16 A-8-16
B - 12
B
17 A-8-17 18 A-8-18 19 A-8-19 20 A-8-20 Data Sheet B-7. CoreDirector CI CM Configuration Parameters CM Configuration Parameters CM name: CoreDirector main management IP address: CoreDirector main management IP address netmask CoreDirector internal network base address: CM A main IP address: CM A main IP address netmask: CM B main IP address: CM B main IP address netmask: CoreDirector IP gateway address: OSRP node address: CM A auxiliary IP address (optional): CM A auxiliary IP address netmask (optional): CM B auxiliary IP address (optional): CM B auxiliary IP address netmask (optional): CoreDirector CORBA BOA main port number (optional): CoreDirector TL1 module port number (optional): CoreDirector HTTP port number (optional): CoreDirector echo port number (optional): CoreDirector OSI System ID (optional):

B - 13
B
B - 14
G
CoreDirector Switch Glossary
GLOSSARY
This glossary contains acronyms and definitions for terms used by Ciena. These have been selected so as to not conflict with definitions originated by Telcordia, ISO, ITU-T or other standards bodies. Some terms have been defined in ways specific to the CoreDirector Switch and CoreDirector CI Switch products while not conflicting with standard definitions. In some cases, informal definitions have been included with the more formal, technical definition. This is intended to explain the term in relation to the CoreDirector Switch or CoreDirector CI Switch. The glossary is divided into two sections: Abbreviations/Acronyms and Definitions and Terminology and Definitions.
ABBREVIATIONS AND ACRONYMS

Abbreviation/Acronym Definition
A
ACO ANSI ASIC Alarm Cutoff American National Standards Institute Application-specific Integrated Circuit
B
BDFB BELLCORE BER BERT BIP BITS Battery Distribution Fuse Bay See Telcordia Bit Error Rate Bit Error Rate Test Bit Interleaved Parity Building Integrated Timing Source
C
CLEITM CLI CM CO CO GND CTP Common Language Equipment Identifier Command Line Interface Control Module Central Office Central Office Ground Connection Termination Point

G-1
G
Glossary
CoreDirector Switch
D
dB dBm DC DCE DMM DTE Decibel Decibel reference in milliwatts Direct Current Data Communications Equipment Digital Multimeter Data Terminating Equipment
E
E1 EIA EMI EPS ESD Service or line operating at the European E1 rate (2.048 Mb/s) Electronic Industries Association Electromagnetic Interference Equipment Protection Switching Electrostatic Discharge
F
FCC FTP Federal Communications Commission File Transfer Protocol
G
GTP GUI Group Termination Point Graphical User Interface
H
I/O IP IR ISO Input/Output Internet Protocol Intermediate Reach. Category for SONET and SDH transmitters and receivers. Typical transmission distance of 2-10 Km. International Standards Organization L LED LM LOM Light Emitting Diode Line Module List of Materials
G-2
G
CoreDirector Switch
Abbreviation/Acronym LR Definition Long Reach. Category for SONET and SDH transmitters and receivers. Typical transmission distance up to 80 Km.
Glossary
I
NE NEBS NEC NOCC Network Element (node) Network Equipment Building Standards National Electric Code Network Operations Control Center
J
OC OC-1 OC-3 OC-12 OC-48 OC-192 OC-N OCXO OM OSHA OSI Optical Carrier (asynchronous) Optical Carrier level 1, SONET bit rate = 51.84 Mbps Optical Carrier level 3, SONET bit rate = 155.52 Mbps Optical Carrier level 12, SONET bit rate = 622.08 Mbps Optical Carrier level 48, SONET bit rate = 2.4 Gbps Optical Carrier level 192, SONET bit rate = 9.6 (10) Gbps Optical Carrier where N denotes a multiple of 51.84 Mbps Oven-Controlled Crystal Oscillator Optical Module Occupational Safety and Health Act Open Systems Interconnection
K
PC PDU PTP(s) Personal Computer Power Distribution Unit Physical Termination Point(s)
L
RMA RTN RTS Return Materials Authorization Return Request to Send

G-3
G
Glossary
CoreDirector Switch
M
SDH SFP SM SNC Synchronous Digital Heirarchy Small Form Factor Pluggable Switch Module SubNetwork Connection. A type of connection whose route is dynamically determined; it may be regroomed, it may be meshprotected to another route if a line fails, and so forth. Specific paths may also be forced or encouraged by the use of DTLs. Synchronous Optical Network Short Reach. Category for SONET transmitters and receivers. Typical transmission distance of 2 Km or less. Software Release Document Synchronization Status Messaging Synchronous Transport Mode - SDH counterpart to STS. Synchronous Transport Signal. The units used for the size of a logical connection. Where N denotes a multiple of 51.84 Mb/s
SONET SR SRD SSM STM STS STS-n
N
T1 TCP TCP/IP TFTP TL-1 CLI TM TOP TP TTP Service or line operating at the DS-1 rate (1.544 Mb/s) Transmission Control Protocol Transmission Control Protocol/Internet Protocol Trivial File Transfer Protocol Transaction Language One, Command Line Interface Timing Module Task Oriented Procedure Termination Point Trail Termination Point
G-4
G
CoreDirector Switch TERMINOLOGY
Term Definition
Glossary
A
Alarm An abnormal condition which exists in a network element that may negatively impact network traffic. An alarm is a condition that has duration in time and remains in effect until it is cleared. (1) Limited Operation. The condition in a fiber optic link when operation is limited by the power of the received signal (rather than by bandwidth or by distortion). (2) The decrease in magnitude of power of a signal in transmission between points. A term used for expressing the total losses on an optical fiber consisting of the ratio of light output to light input. Attenuation is usually measured in decibels per kilometer (db/km) at a specific wavelength. Typical multi-mode wavelengths are 850 and 1300 nanometers (nm); single mode, at 1300 and 1500 nm. NOTE: When specifying attenuation, it is important to note if it is nominal or average room temperature value, or maximum over operating range.
Attenuation
B
Backplane The high-speed communications line to which the CoreDirector Switch modules are physically connected. Status information about the CoreDirector Switch modules is communicated by way of the backplane; no fiber optic signals are carried over the backplane. Distribution point for DC power at central office. A unit equipment rack. (1) Percentage of bits in a transmittal received in error. (2) The number of coding violations detected in a unit of time, usually one second. (3) Specifies expected frequency of errors; compares the ratio of incorrectly transmitted bits to correctly transmitted bits.
Battery Distribution Fuse Bay (BFDB) Bay Bit Error Rate (BER)
C
Cable Rack Central Office (CO) Metallic structure in a ladder configuration, on which cables are run. (1) The place where communications common carriers terminate customer lines and locate switching equipment that interconnects those lines. (2) A location where switching, transmission and power equipment that provide telephone service are centralized. The individual who is responsible for equipment in a centralized equipment location. When an alarm is cleared it may indicate that the problem condition causing the alarm has been addressed and/or resolved by a technician.
Central Office Engineer Cleared

G-5
G
Glossary
Term Coaxial Cable Definition A type of cable used for high frequency transmission. It consists of a central conductor surrounded by insulation, which in turn, is surrounded by a circular outer conductor. A type of connection whose route is not flexible; a series of OSRP links from start node to end node must be specified and specific Synchronous Optical Network (SONET) or Synchronous Digital Heirarchy (SDH) lines, when chosen, cannot be changed. It corresponds to a sequence of permanent cross connections set up on the network. If a line fails, there is no mesh protection; the connection waits until the line comes back up. A transport entity that terminates a link connection and support an optical carrier (OC-n). CTPs typically do not process or monitor the characteristic information (with the exception of Synchronous Optical Network [SONET] Path CTPs and intermediate monitoring).
CoreDirector Switch
Cross connect
CTP
D
Data Communications Equipment (DCE) In a data station, the equipment that provides the signal conversion and coding between the Data Terminal Equipment (DTE) and the line. The DCE may be separate equipment or an integral part of the DTE or of intermediate equipment. A DCE may perform other functions usually performed at the network end of the line. The number of bits of information transmitted per second as in a data transmission link. Typically expressed as megabits per second (mb/ s) That part of a data station that serves as a data source (originates data for transmission), a data sink (accepts transmitted data), or both. An electronic tool to measure electric current, resistance or voltage; also called a multimeter. An alternate route that mesh protection uses if the current route fails.
Data Rate
Data Terminating Equipment (DTE) Digital Multimeter Diverse Route
E
Electromagnetic Interference Electronics Industries Association (EIA) Electrostatic Discharge (ESD) Electrostatic Discharge Strap Any electrical or electromagnetic interference that causes undesirable responses, or degradation. A standards association that publishes test procedures. The discharge of high voltage caused by static charging. ESD-guard wrist band worn by technicians that terminates at the CoreDirector Switch ESD ground jack to provide a fixed resistance to ground. Protects the technician and system from electrostatic discharge.
G-6
G
CoreDirector Switch
Term Express (or through) OC-48 Definition An OC-48 that continues through FOTS equipment (for example, two co-located end terminals or an ITS regenerator/PLAN repeater) onto an adjacent FOTS.
Glossary
F
Fiber Fiber Optic Cable A physical transmission facility containing one or more spans (connecting possibly multiple CoreDirector Switch pairs) A transmission medium that uses glass or plastic fibers, rather than copper wire, to transport data or voice signals. The signal is imposed on the fiber by way of pulses (modulation) of light from a laser or a Light-emitting Diode (LED). Because of its high bandwidth and lack of susceptibility to interference, fiber optic cable is used in long-haul or noisy applications. A single or multiple fiber that is used to connect one unit of equipment to another within an equipment frame. A method for the transmission of information (sound, pictures, or data). Light is modulated and transmitted over high purity, hair-thin fibers of glass. The bandwidth capacity of fiber optic cable is much greater than that of conventional cable or copper wire. Building or underground fiber optic cable.
Fiber Optic Jumper Fiber Optics
Fiber Plant
G
Jumper Fiber optic cable that has connectors installed on both ends.
H
Open Systems Interconnection (OSI) Referring to the OSI reference model, a logical structure for network operations standardized by the International Standards Organization (ISO). The OSI model organizes the communications process into seven different categories and places the categories in a layered sequence based on their relationship to other users. Layers 7 through 4 deal with end to end communications between the message source and the message destination, while layers 3 through 1 deal with network access.
I
Physical Termination Point Physical address which identifies a termination or crossover connection point for switching optical transport signals. Refers to the physical location of an Optical Module within a CoreDirector Switch. Fiber optic cable that has connectors installed on one end.
Pigtail

G-7
G
Glossary
Term Definition
CoreDirector Switch
J
Receiver Sensitivity The optical power required by a receiver for low error signal transmission. In the case of digital signal transmission, the mean optical power is usually quoted in Watts or dBm (decibels referenced to 1 milliwatt). The current function of an APS, MSP, VLSR, or MSPring line (working or protect).
Role
K
Sensitivity Service Type Switching Network Manager Synchronous Digital Hierarchy (SDH) Synchronous Optical Network (SONET) For a fiber-optic receiver, the minimum optical power required to achieve a specified level of performance, such as a BER. SONET Logical Connection (SLC) or Transparent Logical Connection (TLC). Manages individual and networks of optical switching elements. ITU-TSS international standard for transmission over optical fiber. (1) A set of standards for transmitting digital information over optical networks. Synchronous indicates that all pieces of the SONET signal can be tied to a single clock. (2) A ITU-T standard for synchronous transmission up to multi-gigabit speeds. (3) A standard for fiber optics. (1) SONET standard for transmission over OC-1 optical fiber at 51.84 Mb/s. (2) A SONET frame including overhead and payload capacity. The basic SONET frame is the STS-1. STS-1s can be multiplexed or concatenated with no additional overhead. STS-n denotes a multiple of 51.84 Mb/s.
Synchronous Transport Signal (STS, STS-n)
L
Telcordia Transmission Control Protocol/Internet Protocol (TCP/IP) Telcordia Technologies, Inc., formerly BELLCORE (BELL Communications Research, Inc.) A set of protocols developed to link dissimilar computers across many kinds of networks.
M
UTC Universal Time Coordinated; formerly Greenwich Mean Time (GMT)
N
Wrist Straps An grounded, electrically-conductive band worn by a technician to protect equipment from electrostatic discharge.
G-8
I
CoreDirector Switch
INDEX
Index
alarm cable assembly CoreDirector 4-95 CoreDirector CI 4-92 connecting alarms and parallel telemetry cable (TOP 183D) 4-91 removing and installing PDU-B/P cable (TOP 185D) 4-97 change CLI login user ID (TOP 261D) 4-185 CLI login user password (TOP 261D) 4-185 CoreDirector IP address (TOP 223D) 4-181 CoreDirector name (TOP 223D) 4-181 initial install settings (TOP 275D) 4-205 channel capacity, adding (TOP 207D) 4-111 Ciena return material authorization (RMA) procedures (TOP 072D) 4-17 circuit breaker module remove and install (TOP 168D) 4-19 CISPR ii CLI login change password (TOP 261D) 4-185 change user ID (TOP 261D) 4-185 CLI, software interface 1-2 CM switch (TOP 270D) 4-195 color rules for LEDs 1-6 compliance information 1-i configuration database backup and restore (TOP 208) 4-115 configuring CoreDirector auxiliary IP addresses (TOP 275D) 4-205 conformity declaration ii connecting alarms and parallel telemetry cable (TOP 183D) 4-91 to Node Manager via the Ethernet interface (TOP 195D) 4-107 to the Control Module using a Laptop (TOP 194D 4-101 connectors 1-2, 1-7, 1-12 alarm 1-12 BITS 1-11 CoreDirector alarm pin assignment 4-96 CoreDirector CI alarm 4-92 CoreDirector CI alarm pin assignment 4-93 Ethernet 1-11 for LM-16 1-12 front I/O panel (CoreDirector CI) 1-8 power distribution 1-7 rear I/O panel (CoreDirector) 1-8 RS 232 1-11
Symbols
1-2
Numerics
-48VDC supply voltage, verifying (TOP 015D) 4-9
A
about this manual xv ACO ACO switch 1-2 alarm cutoff (ACO) 1-3 indicator 1-5 using the ACO switch to turn off an alarm (TOP 007D) 4-7 air filter, remove and install (TOP 032D) 4-15 alarm critical 1-5 turning off using ACO switch (TOP 007D) 4-7 alarm connector 1-12, 4-92, 4-93, 4-96 alarm cutoff See ACO alarm indicators 1-5 APS 1+1 groups, delete 4-211 APS switch state, verify 4-211
B
backup database (TOP 208D) 4-115 basic color rules, LEDs 1-6 basic module states pattern 1-6 bay alarm state 1-5 BITS connectors 1-11 blower module 4-23 bold text xix broken fiber xxiii
C
cables Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
I-1
I
Index
connectors, dissimilar 4-46 control module (CM) 2-3 connecting to using a laptop (TOP 194D) 4101 identifying 1-14 recovery from dual CM failure (TOP 262D) 4187 remove and install (TOP 170D) 4-27 controls 1-2 conventions, documentation 1-xvii CoreDirector power up (TOP 178D) 4-89 CoreDirector shutdown (TOP 217D) 4-151 corrective maintenance 3-2 critical alarm indicator 1-5
CoreDirector Switch E
EEPROM, IO Panel check (TOP 274D) 4-203 electrostatic discharge See ESD EMC Directive ii ESD xxii Ethernet connectors 1-11
F
failure hardware 1-6 power distribution 1-5 fan filter maintenance 3-1 remove and install air filter (TOP 032D) 4-15 fan module remove and install (TOP 169D) 4-23 fan power module (FPM) remove and install (TOP 176D) 4-81 fan shelf indicator CoreDirector 1-5 CoreDirector CI 1-5 fan, remove and install (TOP 169D) 4-23 FCC ii fiber, broken xxiii FTP server setup (TOP 283D) 4-243 software 4-243
D
data sheets CoreDirector A-1 CoreDirector CI B-1 database, backup and restore (TOP 208D) 4-115 decommissioning a CoreDirector Switch (TOP 281D) 4-233 definitions terminology G-5 delete APS 1+1 groups 4-211 delete LM 1+1 configuration 4-211 details frame 1-xviii diagnostics, initial 1-7, 2-4 disclaimer 1-i display panel indicators 1-4 dissimilar connector types 4-46 document comments iii ordering information iii printing history iii related documents iii release notes iii standards ii document conventions xvii bold text xix GUI elements xviii terminology xix documentation, related xvi dust caps xxiii
G
general precautions warnings and cautions xx green LED, basic meanings 1-6 grounding, verifying system (TOP 016D) 4-11 GUI elements 1-xviii guidelines, maintenance 3-2
H
hand tools 1-1 handling modules properly (TOP 278D) 4-215 Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
I-2
I
CoreDirector Switch
hardware components, location of 1-12 control module 2-3 line module 2-4 optical module 2-2 power distribution unit 1-3 release numbering 1-xvii switch module 2-3 timing module 2-2 hardware failure, indicator 1-6 hardware features 1-2 hardware overview 2-1 hazardous materials ii
Index
laser safety warning 1-i LED test switch 1-3 LEDs 1-4 color rules 1-6 line module meanings 2-4 optical ports on LM-16 line module 2-8 LEDs, testing (TOP 187D) 4-99 lifting techniques xxi Light Emitting Diodes (LEDs) control module 2-3 fan 1-5 LED test 1-5 module LEDs 2-2 optical module 2-2 switch module 2-3 test (TOP 187D) 4-99 timing module 2-2 Line Module (LM) populated, testing 4-173 remove and install (TOP 173D) 4-53 test (TOP 220D) 4-161 line module (LM) LEDs 2-4 Light Emitting Diodes (LEDs) line module 2-4 LM-16 2-4 LM-16 LEDs 2-8 LM-2 2-4 LEDs 2-4 LM-8 2-4 LEDs 2-5 LM-TUG3 2-4 naming 1-13, 1-14 list frame 1-xviii LM 1+1 configuration, delete 4-211 LM-16 line module LEDs meanings 2-8 optical ports 2-8 LM-2 Line Module LEDs meanings 2-4 LM-8 line module LEDs meanings 2-5
I
I/O module location 1-8 I/O Panel remove and install (TOP 177D) 4-85 indicators 1-2, 1-4 ACO 1-3 basic module states pattern 1-6 module boot sequence 1-7 redundant module states 1-7 testing 1-5 initial module diagnostics 1-7, 2-4 initialization, indicating 1-6 interfaces software 1-2 interference ii IO panel EEPROM check (TOP 274D) 4-203 IP address change (TOP 223D) 4-181 configuring auxiliary (TOP 275D) 4-205
L
laptop IP address setting for FTP 4-245 how to procedure 4-224 preparing for software transfer 4-244 laser class 1-i product notice 1-i laser product notice 1-i Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
I-3
I
Index
LM-8 to LM-16 upgrade (TOP 276D) 4-209 locations, component, identifying 1-12 logging on to Node Manager via the Ethernet interface (TOP195D) 4-107
CoreDirector Switch
optical module naming 1-15 Optical Module (OM) remove and install (TOP 172D) 4-41 test (TOP 220D and 221D) 4-161, 4-177 optical module (OM) 2-2 optical modules and ports 1-15 optical port 1-12 optical port connectors 1-12 optical port groups 1-15 optical ports 1-15 optical power level 4-3 optical power level, measuring (TOP 001D) 4-3 optical power level, measuring (TOP) 001D) 4-3 OSI System ID, configuring (TOP 275D) 4-205 overview 1-1 overview, hardware 2-1
M
maintenance 1-1 corrective 3-2 fan filter 3-1 preventive 3-1 system upgrades 3-2 maintenance guidelines 3-2 maintenance state, indicating 1-7 maintenance tasks 3-2 maintenance-related TOPs 3-2 major alarm indicator 1-5 measuring optical power level 4-3 measuring optical power level (TOP 001D) 4-3 Menu bar in the GUI 1-xviii minor alarm indicator 1-5 modem access, setting up (TOP 209D) 4-121 modem access, setting up CoreDirector for (TOP 209D) 4-121 module boot sequence 1-7 module shelf indicator 1-5 module slots, identifying 1-13 modules basic states pattern 1-6 boot sequence 1-7 redundant states 1-7 modules, handling properly (TOP 278D) 4-215
P
pack up CoreDirector (TOP 218D) 4-155 packing up a CoreDirector system (TOP 218D) 4155 parallel telemetry cable and alarms, connecting (TOP 183D) 4-91 password, CLI, changing (TOP 261D) 4-185 patterns, LED 1-6 port group, optical 1-15 ports 1-15 position, module, identifying 1-14, 1-15 power A and B indicators 1-5 power arm failure 1-5 power distribution LEDs 1-5 power distribution circuitry failure 1-5 Power Distribution Unit (PDU) remove and install display (TOP 175D) 4-77 remove and install PDU-B/P cable (TOP 185D) 4-97 power distribution unit (PDU) 1-3 connectors 1-7, 1-12 power indicator 1-5 power up procedure (TOP 178D) 4-89 precautions xx prepare site terminal (or laptop) for software transfer (TOP 279) 4-223 Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
N
Node Manager establishing connection (TOP 195D) 4-108 logging onto (TOP 195D) 4-110
O
operations 1-1 software 2-1 optical connectors, protecting xxiii optical fibers, handling xxiii
I-4
I
CoreDirector Switch
prerequisites xvi preventive maintenance 3-1 primary module role, indicating 1-7 printing history iii publications, related iii, xvi
Index
reset state, indicating 1-6, 1-7, 2-4 resource naming 1-12 restore database (TOP 208D) 4-115 return material authorization (RMA) procedures (TOP 072D) 4-17 reversion, software, in-service (TOP 211D) 4-143 revision history 1-xvii revision sequencing 1-xvii RS 232 connectors 1-11
R
ramp for uncrating 4-156 recovery from dual CM failure (TOP 262D) 4-187 recovery, dual CM failure (TOP 262D) 4-187 red LED, basic meanings 1-6 redundant module states 1-7 redundant modules states pattern 1-7 related documents iii related publications xvi remove and install air filter (TOP 032D) 4-15 circuit breaker module (TOP 168D) 4-19 Control Module (TOP 170D) 4-27 fan module (TOP 169D) 4-23 fan power module (TOP 176D) 4-81 I/O Panel (TOP 177D) 4-85 Line Module (TOP 173D) 4-53 Optical Module (TOP 172D) 4-41 PDU Display Module (TOP 175D) 4-77 PDU-B/P cable (TOP 185D) 4-97 Switch Module (TOP 171D) 4-35 Timing Module (TOP 174D) 4-73 remove and install air filter (TOP 032D) 4-15 removing and installing circuit breaker module (TOP 168D) 4-19 control module (TOP 170D) 4-27 fan power module (TOP 176D) 4-81 fan unit (TOP 169D) 4-23 I/O module (TOP 177D) 4-85 Line Module (TOP 173D) 4-53 Optical Module (TOP 172D) 4-41 PDU display module (TOP 175D) 4-77 PDU-B/P cable (TOP 185D) 4-97 Switch Module (TOP 171D) 4-35 Timing Module (TOP 174) 4-73 required tools 1-1 reset primary Control Module (TOP 270D) 4-195 primary Timing Module (TOP 280D) 4-225 secondary Control Module (TOP 271D) 4-199 secondary Timing Module (TOP 281D) 4-229 Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191
S
safety See general precautions SC-to-LC adapter cables 1-12 SDH I/O module (CoreDirector CI) 1-11 SDH I/O panel (CoreDirector) 1-10 secondary CM, resetting (TOP 271D) 4-199 secondary module role, indicating 1-7 secondary TM, resetting (TOP 281D) 4-229 selection tree 1-xviii setting up a CoreDirector switch for modem access (TOP 209D) 4-121 shelf A 1-12 shelf B 1-12 shelf C 1-12 shelf failure indicators CoreDirector 1-5 CoreDirector CI 1-5 shelves 1-12 shutdown, CoreDirector (TOP 217D) 4-151 site terminal copying system upgrade software 4-244 how to procedure 4-223 file transfer upgrading system files 4-245 See Control Modules IP address setting for FTP 4-245 how to procedure 4-224 WFTPD software configuring for file transfer 4-245 how to procedure 4-224 loading software 4-244 how to procedure 4-224 overview 4-223, 4-243 software 2-1
I-5
I
Index
in-service downgrade (TOP 211D) 4-143 interfaces 1-2 operations 2-1 release numbering 1-xvii software in-service reversion (TOP 211D) 4-143 software in-service upgrade (TOP 210D) 4-127 software interfaces 1-2 command line interface 1-2 Node Manager 1-2 Switching Network Manager 1-2 TL1 1-2 SONET I/O module (CoreDirector CI) 1-11 SONET I/O panel (CoreDirector) 1-10 static electricity precautions xxii Switch Module (SM) remove and install (TOP 171D) 4-35 switch module (SM) 2-3 identifying 1-14 Switching 3-2 system ground ground scheme CoreDirector 4-12 system messages, text representation 1-xviii system shelves, naming 1-12 system software overview 4-244 system software, upgrading 4-243 system upgrades 3-2 system-level indicators 1-4
CoreDirector Switch
LED Status Test A-18 Site Information A-3, A-4, B-3 Status/Functional Test A-19, B-8 CoreDirector CI overview B-1 types LED status test B-8 testing Line Modules and Optical Modules (TOP 220D) 4-161 Optical Module (TOP 221D) 4-177 testing LEDs (TOP 187D) 4-99 Timing Module (TM) remove and install (TOP 174D) 4-73 timing module (TM) 2-2 identifying 1-14 TM switch (TOP 270D) 4-225 tools 1-1 TOP 207D adding channel capacity 4-111 top shelf 1-12 toxic emissions ii trademarks ii traffic interruption, avoiding xxiv Turn-up & Test prerequisites xvi
U
upgrade LM-8 to LM-16 (TOP 276D) 4-209 upgrade, software, inservice (TOP 210D) 4-127 upgrades overview 3-2 USEPA ii user ID, CLI, changing (TOP 261D) 4-185 using the ACO switch to turn off an alarm (TOP 007D) 4-7
T
tabs in the GUI xviii tasks, maintenance 3-2 Telcordia document standards ii terminology xix test LEDs (TOP 187D) 4-99 Line Module (TOP 220D) 4-161 Optical Module (TOP 220D and 221D) 4-161, 4-177 test data sheets CoreDirector overview A-1 types Inventory A-5, B-5
V
verify APS switch state 4-211 verifying -48VDC supply voltage (TOP 015D) 4-9 system grounding (TOP 016D) 4-11 voltage precautions xx
I-6
I
CoreDirector Switch W
warning laser safety i warnings and cautions xx weight precautions xxi
Index
Y
yellow LED, basic meanings 1-6

I-7
I
Index CoreDirector Switch
I-8

009 2004 191 - CoreDirector

Uploaded by

Document Information

Original Description:

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

009 2004 191 - CoreDirector

Uploaded by

Copyright:

Available Formats

COREDIRECTOR

MULTI-SERVICE OPTICAL SWITCH

MAINTENANCE AND UPGRADE MANUAL

Ciena Confidential and Proprietary

Ciena Confidential and Proprietary

LASER RADIATION EXPOSURE

Class 1 Laser Product Notice

Part 15 of the Federal Communications Commission (FCC): Interference

Environmental Impact Statement

Telcordia Document Standards

CISPR Declaration of Conformity

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

CoreDirector Switch RELEASE NOTES AND DOCUMENT UPDATES

DOCUMENT ORDERING INFORMATION

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Preface ADDITIONAL PRODUCT INFORMATION

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

THIS PAGE INTENTIONALLY LEFT BLANK

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

THIS PAGE INTENTIONALLY LEFT BLANK

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

ABOUT THIS MANUAL

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Introduction RELATED PUBLICATIONS

Table 3. CoreDirector Switch R4.0 Documentation Part Number Title

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

CoreDirector Switch REVISION HISTORY

Revision Number Sequencing

The revision number sequencing format of Ciena technical publications is as follows:

Revision History of This Manual

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Directory tree (like Windows Explorer)

Inputs and Responses

[ ] standing in for the variable; a description of the variables in Italic

Drop-down box selections Select Unlocked or Locked from the list.

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Introduction GENERAL SAFETY PRECAUTIONS

General Warnings and Cautions

Voltage Precaution RISK OF PERSONAL INJURY

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Lift Precautions LIFT WARNING

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Static Electricity Precautions Risk of Damage to Circuit Packs and Backplanes

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Fiber Break and Damaged Fiber Precautions

When handling, installing, or removing modules, observe the following precautions.

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

Operating Temperature Refer to Telcordia Generic Requirements GR-63-CORE, Section 4.1.2.

Relative Humidity Refer to Telcordia Generic Requirements GR-63-CORE, Section 4.1.2.

Storage Temperature Refer to Telcordia Generic Requirements GR-63-CORE, Section 4.1.1.

Traffic Disruption Precaution Traffic Disruption Risk

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

The procedures in this manual are presented as Task-Oriented Practices (TOPs).

Maintenance and Upgrade Manual February 11, 2005 - Revision A 009-2004-191

HARDWARE FEATURES OF THE COREDIRECTOR SWITCH