user manual

Manuals Brands Cisco Systems Manuals Security Camera Security Camera ONS 15600

Corporate Headquarters

Cisco Systems, Inc.

170 West Tasman Drive

San Jose, CA 95134-1706

USA

http://www.cisco.com

Tel: 408 526-4000

800 553-NETS (6387)

Fax: 408 526-4100

Cisco ONS 15600 Reference Manual

Product and Documentation Release 7.2

Last Updated: August 2012

Text Part Number: 78-17815-01

Summary of content (350 pages)

PAGE 1

Cisco ONS 15600 Reference Manual Product and Documentation Release 7.2 Last Updated: August 2012 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
PAGE 2

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
PAGE 3

CONTENTS About this Manual xxiii Revision History xxiv Document Objectives Audience xxiv xxiv Related Documentation xxiv Document Conventions xxv Obtaining Optical Networking Information xxxi Where to Find Safety and Warning Information xxxi Cisco Optical Networking Product Documentation CD-ROM Obtaining Documentation and Submitting a Service Request CHAPTER 1 Shelf and Backplane Hardware 1.1 Installation Overview 1.2 Bay Installation 1.3 Front Door xxxi xxxi 1-1 1-1 1-2 1-4 1.
PAGE 4

Contents 1.11.3 OGI Cables 1-19 1.11.4 Optical Card Cable Routing 1.11.5 Card Replacement 1-20 CHAPTER 2 Card Reference 1-20 2-1 2.1 Card Overview 2-1 2.1.1 Card Summary 2-1 2.1.2 Card Compatibility 2-2 2.2 TSC Card 2-3 2.2.1 TSC Slots and Connectors 2-3 2.2.2 TSC Faceplate and Block Diagram 2-4 2.2.3 TSC Card-Level Indicators 2-5 2.2.4 TSC Network-Level Indicators 2-5 2.2.5 TSC Push-Button Switches 2-6 2.3 SSXC Card 2-6 2.3.1 SSXC Switch Matrix 2-6 2.3.2 SSXC Slots and Connectors 2-7 2.3.
PAGE 5

Contents 2.7.2 2.7.3 2.7.4 2.7.5 OC192/STM64 SR/SH 4 Port 1310 Faceplate and Block Diagram 2-18 OC192/STM64 SR/SH 4 Port 1310 Card-Level Indicators 2-18 OC192/STM64 SR/SH 4 Port 1310 Network-Level Indicators 2-19 OC192/STM64 SR/SH 4 Port 1310 Card OGI Connector Pinout 2-19 2.8 ASAP Card 2-19 2.8.1 ASAP Connectors 2-20 2.8.2 ASAP Covers and Plugs 2-21 2.8.3 ASAP Card Faceplate and Block Diagram with 4PIOs Installed 2.8.4 4PIO Module Faceplate 2-22 2.8.5 1PIO Module Faceplate 2-22 2.8.
PAGE 6

Contents 4.5.2 Network View 4-9 4.5.2.1 CTC Node Colors 4-10 4.5.2.2 Network View Tabs 4-11 4.5.2.3 Link Consolidation 4-11 4.5.3 Card View 4-12 4.5.4 Export and Print CTC Data 4-14 4.6 CTC Card Reset 4-15 4.7 TSC Card Database 4-15 4.8 Software Load Revert CHAPTER 5 Security 4-16 5-1 5.1 Users IDs and Security Levels 5-1 5.2 User Privileges and Policies 5-1 5.2.1 User Privileges by Security Level 5-2 5.2.2 Security Policies 5-5 5.2.2.1 Superuser Privileges for Provisioning Users 5-5 5.2.2.
PAGE 7

Contents 7.3 Cross-Connect Card Bandwidth 7-12 7.4 DCC Tunnels 7-12 7.4.1 Traditional DCC Tunnels 7.4.2 IP-Encapsulated Tunnels 7-12 7-13 7.5 Multiple Destinations for Unidirectional Circuits 7.6 Path Protection Circuits 7-13 7-13 7.7 Protection Channel Access Circuits 7-15 7.8 BLSR STS and VT Squelch Tables 7-16 7.8.1 BLSR STS Squelch Table 7-16 7.8.2 BLSR VT Squelch Table 7-17 7.9 Path Trace 7-17 7.10 Automatic Circuit Routing 7-18 7.10.1 Bandwidth Allocation and Routing 7-19 7.10.
PAGE 8

Contents 8.5.2 Two-Fiber BLSR to Four-Fiber BLSR 8-14 8.5.3 Add or Remove a Node from a Topology 8-14 CHAPTER 9 Management Network Connectivity 9.1 IP Networking Overview 9-1 9-1 9.2 ONS 15600 IP Addressing Scenarios 9-2 9.2.1 Scenario 1: CTC and ONS 15600s on the Same Subnet 9-2 9.2.2 Scenario 2: CTC and ONS 15600s Connected to Router 9-3 9.2.3 Scenario 3: Using Proxy ARP to Enable an ONS 15600 Gateway 9.2.4 Scenario 4: Default Gateway on CTC Computer 9-5 9.2.
PAGE 9

Contents 9.7.9 OSI/IP Networking Scenarios 9-44 9.7.9.1 OSI/IP Scenario 1: IP OSS, IP DCN, ONS GNE, IP DCC, and ONS ENE 9-45 9.7.9.2 OSI/IP Scenario 2: IP OSS, IP DCN, ONS GNE, OSI DCC, and Other Vendor ENE 9-45 9.7.9.3 OSI/IP Scenario 3: IP OSS, IP DCN, Other Vendor GNE, OSI DCC, and ONS ENE 9-47 9.7.9.4 OSI/IP Scenario 4: Multiple ONS DCC Areas 9-49 9.7.9.5 OSI/IP Scenario 5: GNE Without an OSI DCC Connection 9-50 9.7.9.6 OSI/IP Scenario 6: IP OSS, OSI DCN, ONS GNE, OSI DCC, and Other Vendor ENE 9-51 9.
PAGE 10

Contents 11.3.2 11.3.3 11.3.4 11.3.5 11.3.6 Alarm Profile Buttons 11-10 Alarm Profile Editing 11-11 Alarm Severity Option 11-11 Row Display Options 11-11 Alarm Profile Applications 11-11 11.4 Alarm Filter 11-12 11.5 Alarm Suppression 11-12 11.5.1 Alarms Suppressed for Maintenance 11-13 11.5.2 Alarms Suppressed by User Command 11-13 11.6 External Alarms and Controls 11-13 11.6.1 External Alarm Input 11-14 11.6.2 External Control Output 11-14 11.6.
PAGE 11

Contents 13.6 SNMP Management Information Bases 13-5 13.6.1 IETF-Standard MIBs for ONS 15600 13-5 13.6.2 Proprietary ONS 15600 MIBs 13-6 13.7 SNMP Trap Content 13-6 13.7.1 Generic and IETF Traps 13.7.2 Variable Trap Bindings 13-7 13-7 13.8 Proxy Over Firewalls 13-11 13.8.1 Remote Monitoring 13-12 13.8.2 64-Bit RMON Monitoring over DCC 13-12 13.8.2.1 Row Creation in MediaIndependentTable 13-12 13.8.2.2 Row Creation in cMediaIndependentHistoryControlTable 13.8.3 HC-RMON-MIB Support 13-12 13.8.
PAGE 12

Contents A.1.7 External LAN Interface A-3 A.1.8 TL1 Craft Interface A-3 A.1.9 Modem Interface A-3 A.1.10 Alarm Interface A-3 A.1.11 BITS Interface A-3 A.1.12 System Timing A-3 A.1.13 Database Storage A-4 A.1.14 Environmental Specifications A.1.15 Power Specifications A-4 A-4 A.2 Card Specifications A-5 A.2.1 TSC Card Specifications A-5 A.2.2 SSXC Specifications A-6 A.2.3 OC48/STM16 LR/LH 16 Port 1550 Specifications A-6 A.2.4 OC48/STM16 SR/SH 16 Port 1310 Specifications A-8 A.2.
PAGE 13

Contents C.4 CTC Default Settings C-39 INDEX Cisco ONS 15600 Reference Manual, R7.
PAGE 14

Contents Cisco ONS 15600 Reference Manual, R7.
PAGE 15

F I G U R E S Figure 1-1 ONS 15600 with Dollies Installed Figure 1-2 ONS 15600 Front Door Figure 1-3 Bay Label Figure 1-4 Laser Warning Label Figure 1-5 Plastic Rear Cover Figure 1-6 PDU Bus Bar Cover Figure 1-7 Rear of the ONS 15600, Including the CAP Figure 1-8 CAP Faceplate and Connections Figure 1-9 Alarm Pin Assignments on the CAP Figure 1-10 BITS Timing Connections on the CAP Figure 1-11 Front and Rear Bay Ground Holes Figure 1-12 Fan-Tray Assembly Figure 1-13 Air Filter and
PAGE 16

Figures Figure 2-15 Bail Clasp XFP (Unlatched) Figure 2-16 Bail Clasp XFP (Latched) Figure 2-17 ONS 15600 Filler Card Figure 3-1 ONS 15600 in a 1+1 Protected Configuration 3-2 Figure 3-2 ONS 15600 in an Unprotected Configuration 3-3 Figure 4-1 Legal Disclaimer Tab Figure 4-2 CTC Window Elements in the Node View (Default Login View) Figure 4-3 Terminal Loopback Indicator Figure 4-4 Facility Loopback Indicator Figure 4-5 Network Displayed in CTC Network View 4-10 Figure 4-6 CTC Card V
PAGE 17

Figures Figure 8-11 Path-Protected Mesh Network Figure 8-12 PPMN Virtual Ring Figure 9-1 Scenario 1: CTC and ONS 15600s on Same Subnet Figure 9-2 Scenario 2: CTC and ONS 15600s Connected to Router Figure 9-3 Scenario 3: Using Proxy ARP Figure 9-4 Scenario 4: Default Gateway on a CTC Computer Figure 9-5 Scenario 5: Static Route with One CTC Computer Used as a Destination Figure 9-6 Scenario 5: Static Route with Multiple LAN Destinations Figure 9-7 Scenario 6: OSPF Enabled Figure 9-8 Scena
PAGE 18

Figures Figure 9-34 OSI/IP Scenario 5: GNE Without an OSI DCC Connection Figure 9-35 OSI/IP Scenario 6: IP OSS, OSI DCN, ONS GNE, OSI DCC, and Other Vendor ENE Figure 9-36 OSI/IP Scenario 7: OSI OSS, OSI DCN, Other Vender GNE, OSI DCC, and ONS NEs 9-53 Figure 9-37 OSI/IP Scenario 8: OSI OSS, OSI DCN, ONS GNE, OSI DCC, and Other Vender NEs 9-55 Figure 10-1 ONS 15600 Ethernet Frame Transport Figure 10-2 Ethernet Framing Figure 10-3 Buffering and Flow Control Figure 10-4 Autonegotiation Figu
PAGE 19

T A B L E S Table 1-1 Power Requirements for an Individual Fan Table 1-2 Slot and Card Symbols Table 1-3 Card Ports and Line Rates Table 2-1 ONS 15600 Cards and Descriptions Table 2-2 ONS 15600 Software Release Compatibility Per Card Table 2-3 TSC Card-Level Indicators Table 2-4 TSC Network-Level Indicators Table 2-5 TSC Card Push-Button Switches Table 2-6 SSXC Card-Level Indicators Table 2-7 OC48/STM16 LR/LH 16 Port 1550 Card-Level Indicators Table 2-8 OC48/STM16 LR/LH 16 Port 1550 Ne
PAGE 20

Tables Table 4-5 Node Status Table 4-6 Network View Tabs and Subtabs Table 4-7 Link Icons Table 4-8 Card View Tabs and Subtabs Table 4-9 Table Data with Export Capability Table 5-1 ONS 15600 Security Levels—Node View Table 5-2 ONS 15600 Security Levels—Network View Table 5-3 ONS 15600 User Idle Times Table 5-4 Shared Secret Character Groups 5-9 Table 6-1 SSM Generation 1 Message Set 6-3 Table 6-2 SSM Generation 2 Message Set 6-4 Table 7-1 STS Mapping Using CTC Table 7-2 ONS 1560
PAGE 21

Tables Table 9-14 OSI Virtual Router Constraints Table 9-15 IP Over CLNS Tunnel IOS Commands Table 9-16 OSI Actions from the CTC Provisioning Tab Table 9-17 OSI Actions from the CTC Maintenance Tab Table 11-1 Alarms Column Descriptions Table 11-2 Color Codes for Alarms and Conditions Table 11-3 TL1 Port-Based Alarm Numbering Scheme Table 11-4 Alarm Window Table 11-5 Conditions Display Table 11-6 Conditions Column Description Table 11-7 History Column Description Table 11-8 Alarm Prof
PAGE 22

Tables Table A-8 OC192/STM64 SR/SH 4 Port 1310 Card Specifications Table A-9 ASAP Card Specifications Table A-10 Filler Card Specifications Table A-11 SFP Specifications (4PIO Only) A-12 Table A-12 XFP Specifications (1PIO Only) A-12 Table A-13 ASAP Card 4PIO DWDM SFP Specifications Table A-14 Power and Noise Limited Performances Table A-15 Single-Mode Fiber SFP/XFP Port Cabling Specifications Table B-1 ONS 15600 Service State Primary States and Primary State Qualifiers Table B-2 ONS 1
PAGE 23

About this Manual Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
PAGE 24

About this Manual Revision History Date Notes March 2007 Revision History Table added for the first time August 2007 Updated voltage and current rating in section A.1.15 Power Specifications. September 2008 Added a note in Card Default Settings and Node Default Settings section of Appendix C, Network Element Defaults. April 2010 Updated the section “SNMP Overview” in the chapter “SNMP”. November 2011 Updated the section “Path Trace” in the chapter “Circuits and Tunnels”.
PAGE 25

About this Manual For an update on End-of-Life and End-of-Sale notices, refer to http://cisco.com/en/US/products/hw/optical/ps4533/prod_eol_notices_list.html. Document Conventions This publication uses the following conventions: Note Caution Convention Application boldface Commands and keywords in body text. italic Command input that is supplied by the user. [ Keywords or arguments that appear within square brackets are optional.
PAGE 26

About this Manual Warning IMPORTANT SAFETY INSTRUCTIONS This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device.
PAGE 27

About this Manual Avvertenza IMPORTANTI ISTRUZIONI SULLA SICUREZZA Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di intervenire su qualsiasi apparecchiatura, occorre essere al corrente dei pericoli relativi ai circuiti elettrici e conoscere le procedure standard per la prevenzione di incidenti.
PAGE 28

About this Manual Cisco ONS 15600 Reference Manual, R7.
PAGE 29

About this Manual Aviso INSTRUÇÕES IMPORTANTES DE SEGURANÇA Este símbolo de aviso significa perigo. Você se encontra em uma situação em que há risco de lesões corporais. Antes de trabalhar com qualquer equipamento, esteja ciente dos riscos que envolvem os circuitos elétricos e familiarize-se com as práticas padrão de prevenção de acidentes. Use o número da declaração fornecido ao final de cada aviso para localizar sua tradução nos avisos de segurança traduzidos que acompanham o dispositivo.
PAGE 30

About this Manual Cisco ONS 15600 Reference Manual, R7.
PAGE 31

About this Manual Obtaining Optical Networking Information This section contains information that is specific to optical networking products. For information that pertains to all of Cisco, refer to the Obtaining Documentation and Submitting a Service Request section. Where to Find Safety and Warning Information For safety and warning information, refer to the Cisco Optical Transport Products Safety and Compliance Information document that accompanied the product.
PAGE 32

About this Manual Cisco ONS 15600 Reference Manual, R7.
PAGE 33

C H A P T E R 1 Shelf and Backplane Hardware This chapter provides a description of Cisco ONS 15600 shelf and backplane hardware. Card and cable descriptions are provided in Chapter 2, “Card Reference.” To install equipment, refer to the Cisco ONS 15600 Procedure Guide. Chapter topics include: • 1.1 Installation Overview, page 1-1 • 1.2 Bay Installation, page 1-2 • 1.3 Front Door, page 1-4 • 1.4 Rear Covers, page 1-5 • 1.5 Cable Routing, page 1-7 • 1.6 Customer Access Panel, page 1-7 • 1.
PAGE 34

Chapter 1 Shelf and Backplane Hardware 1.2 Bay Installation door of the ONS 15600 allows access to the shelf assembly, fan-tray assembly, and cable-management area. The customer access panel (CAP) on the back of the shelf provides access to alarm contacts, external interface contacts, and timing contacts. Power and ground terminals are located on the top left and right sides of the bay. Caution Voltage to the alarm circuits should not exceed –48 VDC.
PAGE 35

Chapter 1 Shelf and Backplane Hardware 1.2 Bay Installation ONS 15600 with Dollies Installed 96607 Figure 1-1 The ONS 15600 shelf measures 25 inches high, 19-9/16 inches wide, and 23 inches deep (63.5 cm H x 49.7 cm W x58.3 cm D). A maximum of three ONS 15600s can fit in a custom seven-foot equipment rack. The ONS 15600 that ships within a rack is 83-7/8 inches high, 23-5/8 inches wide, and 23-5/8 inches deep (213 cm H x 60 cm W x 60 cm D). Note Cisco supports only one ONS 15600 shelf per bay.
PAGE 36

Chapter 1 Shelf and Backplane Hardware 1.3 Front Door 1.3 Front Door The ONS 15600 features a door to the front compartment that you can open by releasing the latches on the bottom left and right sides of the door. The front door provides access to the shelf, cable-management tray, and fans (Figure 1-2). Figure 1-2 ONS 15600 Front Door Door pivot point Door latches 78395 ESD jack You can remove the front door of the ONS 15600 to provide unrestricted access to the front of the shelf.
PAGE 37

Chapter 1 Shelf and Backplane Hardware 1.4 Rear Covers Bay Label 81219 Figure 1-3 The front door also has a Class I laser warning (Figure 1-4). Laser Warning Label 83121 Figure 1-4 1.4 Rear Covers The ONS 15600 has an optional plastic rear cover that is held in place with six 6-32 x 3/8 inch Phillips screws. This plastic cover provides additional protection for the cables and connectors on the backplane (Figure 1-5). Cisco ONS 15600 Reference Manual, R7.
PAGE 38

Chapter 1 Shelf and Backplane Hardware 1.4 Rear Covers Plastic Rear Cover 81213 Figure 1-5 Figure 1-6 shows the bus bar covers. Cisco ONS 15600 Reference Manual, R7.
PAGE 39

Chapter 1 Shelf and Backplane Hardware 1.5 Cable Routing PDU Bus Bar Cover 83442 Figure 1-6 1.5 Cable Routing The narrow and wide cable routing modules (CRMs) can be installed on the sides of the bay to manage and contain the optical cables as they are routed away from the bay. You can use both types of fiber routing systems with overhead or under-floor cabling. 1.6 Customer Access Panel The Customer Access Panel (CAP) is located in the middle of the rear of the shelf.
PAGE 40

Chapter 1 Shelf and Backplane Hardware 1.6 Customer Access Panel Rear of the ONS 15600, Including the CAP 78389 Figure 1-7 Slot 1 Slot 11 Slot 2 Slot 12 Slot 3 Slot 4 Slot 13 Slot 14 The ONS 15600 CAP provides the following: • BITS T1 (100 ohm) interfaces via wire-wrap pins. • Two Ethernet interfaces via RJ-45 connectors with internal transformer isolation. • An EIA/TIA-232 craft interface via DB-9 connectors. This interface is surge-protected and provides EMI filtering.
PAGE 41

Chapter 1 Shelf and Backplane Hardware 1.6 Customer Access Panel • Four audio alarm interfaces via a DB-15 connector that is surge-protected and EMI-filtered. The audio alarm indication is provided by the Timing and Shelf Controller (TSC) card and this interface can receive a signal to disable the audio alarm. • Four visual alarm interfaces via a DB-15 connector that is surge-protected and EMI-filtered.
PAGE 42

Chapter 1 Shelf and Backplane Hardware 1.7 Alarm, Timing, LAN, and Craft Pin Connections If the CAP fails, the node raises an EQPT alarm. You can replace the CAP on an in-service system without affecting traffic. To replace a CAP, refer to the Cisco ONS 15600 Procedure Guide. Always replace the CAP during a maintenance window. 1.7 Alarm, Timing, LAN, and Craft Pin Connections Caution Always use the supplied ESD wristband when working with a powered ONS 15600 or any ONS 15600 components.
PAGE 43

Chapter 1 Shelf and Backplane Hardware 1.7.
PAGE 44

Chapter 1 Shelf and Backplane Hardware 1.7.3 LAN Installation 5 EXTERNAL 16 15 14 13 12 11 ALARMS 10 9 8 7 6 5 4 3 2 1 BITS - A BITS Timing Connections on the CAP BITS - B Figure 1-10 5 + OUT 4 4 3 3 + IN 2 2 1 1 10 9 8 7 5 4 3 2 + IN 1 GROUND 78511 FRAME 6 + OUT 64k E1/T1 64k E1/T1 See Chapter 6, “Timing,” for more information. 1.7.
PAGE 45

Chapter 1 Shelf and Backplane Hardware 1.8 Power Distribution Unit 1.8 Power Distribution Unit The PDU consists of a mounting chassis, A- and B-side power modules, an alarm module, and a rear I/O unit. The ONS 15600 PDU has LEDs that alert you to Critical, Major, Minor, and remote alarms on the node. Each module can support three 100A input power feeds, 48 VDC power load (based on a fully loaded ONS 15600 shelf). The PDU supplies six 50A power feeds to the shelves.
PAGE 46

Chapter 1 Shelf and Backplane Hardware 1.9 Power and Ground Description Figure 1-11 Front and Rear Bay Ground Holes PDU frame ground cable 96611 Bay grounding holes The main power connections are made at the PDU side terminals at the top of the bay. To install redundant power feeds, use four power cables and ground cables. For a single power feed, only two power cables and one ground cable (all rated for at least 125-A capacity) are required.
PAGE 47

Chapter 1 Shelf and Backplane Hardware 1.10 Fan-Tray Assembly 1.10 Fan-Tray Assembly The fan-tray assembly is located at the top of the ONS 15600 shelf front compartment. The fan-tray assembly has three removable drawers that hold two fans each and fan-control circuitry for the ONS 15600 (Figure 1-12). You should only need to access the fans if a fan fails. Fan-Tray Assembly 71045 Figure 1-12 1.10.
PAGE 48

Chapter 1 Shelf and Backplane Hardware 1.10.2 Fan Speed and Failure Air Filter and one Fan Tray Pulled Out 78564 Figure 1-13 1.10.2 Fan Speed and Failure If one or more fans fail on the fan-tray assembly, replace the fan tray where that fan resides. You cannot replace individual fans. The red FAN LED on the front of the fan tray turns on when one or more fans fail. For fan-tray replacement instructions, refer to the Cisco ONS 15600 Procedures Guide.
PAGE 49

Chapter 1 Shelf and Backplane Hardware 1.11 Cards and Slots increases appropriately. At initial turn-up, the default fan speed is high until the node initializes. If both TSC cards fail, the fans automatically shift to high speed. If a single TSC card fails, the active TSC card will still control the fan speed. Table 1-1 shows the power requirements for an individual fan in a fan tray. Table 1-1 Power Requirements for an Individual Fan Condition Watts Amps BTU/Hr.
PAGE 50

Chapter 1 Shelf and Backplane Hardware 1.11.2 ASAP Card Cables Table 1-3 Card Ports and Line Rates Card Ports Line Rate per Port OC48/STM16 LR/LH 16 Port 1550; 4 physical interfaces; 4 ports per interface, OC48/STM16 SR/SH 16 Port 1310 totalling 16 OC-48 ports per card 2488.32 Mbps (STS-48, STS-48c) OC192/STM64 LR/LH 4 Port 1550; 4 physical interfaces; 1 port per interface, OC192/STM64 SR/SH 4 Port 1310 totalling 4 OC-192 ports per card 9.95 Gbps (STS-192, STS-192c) 1.11.
PAGE 51

Chapter 1 Shelf and Backplane Hardware 1.11.3 OGI Cables Molex Incorporated 5224 Katrine Ave. Downers Grove, IL 605151-800-522-6752 (630) 512-8787 (800) 213-4237 This fiber boot can also be obtained with part number from the following vendor: Tyco Electronics (www.tycoelectronics.custhelp.com) P.O. Box 3608 Harrisburg, PA 17175 1.11.3 OGI Cables The ONS 15600 faceplate has OGI connectors that terminate in either SC, ST, or FC connectors. Figure 1-16 shows the OGI to SC cable breakout for the OC-48 card.
PAGE 52

Chapter 1 Shelf and Backplane Hardware 1.11.4 Optical Card Cable Routing Figure 1-17 OGI Pin Breakout White ridge this side P1 (Blue) P2 (Orange) P3 (Green) P4 (Brown) P5 (Gray) Alignment pins (male) P6 (White) P7 (Red) 96521 P8 (Black) 1.11.4 Optical Card Cable Routing The ONS 15600 has a cable-management tray with discrete fiber routing paths for each optical card’s cables. Each fiber routing path has a plastic cable latch for securing the cables in the fiber routing path.
PAGE 53

Chapter 1 Shelf and Backplane Hardware 1.11.5 Card Replacement Note An improper removal (IMPROPRMVL) alarm is raised whenever a card pull is performed, unless the card is deleted in CTC first. The alarm will clear after the card replacement is complete. If the alarm does not clear, refer to the “Alarm Troubleshooting” chapter in the Cisco ONS 15600 Troubleshooting Guide. Cisco ONS 15600 Reference Manual, R7.
PAGE 54

Chapter 1 Shelf and Backplane Hardware 1.11.5 Card Replacement Cisco ONS 15600 Reference Manual, R7.
PAGE 55

C H A P T E R 2 Card Reference This chapter describes Cisco ONS 15600 card features and functions. Chapter topics include: • 2.1 Card Overview, page 2-1 • 2.2 TSC Card, page 2-3 • 2.3 SSXC Card, page 2-6 • 2.4 OC48/STM16 LR/LH 16 Port 1550 Card, page 2-8 • 2.5 OC48/STM16 SR/SH 16 Port 1310 Card, page 2-11 • 2.6 OC192/STM64 LR/LH 4 Port 1550 Card, page 2-14 • 2.7 OC192/STM64 SR/SH 4 Port 1310 Card, page 2-17 • 2.8 ASAP Card, page 2-19 • 2.9 Filler Card, page 2-28 • 2.8.
PAGE 56

Chapter 2 Card Reference 2.1.2 Card Compatibility Table 2-1 ONS 15600 Cards and Descriptions (continued) Card Description For Additional Information... OC48 1550 The OC48/STM16 LR/LH 16 Port 1550 card provides 16 long-range, Telcordia GR-253-CORE compliant, SONET OC-48 ports per card. See the “2.4 OC48/STM16 LR/LH 16 Port 1550 Card” section on page 2-8. OC48 1310 The OC48/STM16 SR/SH 16 Port 1310 card provides See the 16 short-range, Telcordia GR-253-CORE compliant, “2.
PAGE 57

Chapter 2 Card Reference 2.2 TSC Card 2.2 TSC Card Note Caution For hardware specifications, see the “A.2.1 TSC Card Specifications” section on page A-5. Do not operate the ONS 15600 with an unprotected, single TSC card or a single SSXC card installed. Always operate the shelf with one active card and one protect card for each of these control cards. The TSC card performs all system-timing functions for each ONS 15600.
PAGE 58

Chapter 2 Card Reference 2.2.2 TSC Faceplate and Block Diagram 2.2.2 TSC Faceplate and Block Diagram Figure 2-1 shows the TSC card faceplate and a block diagram of the card.
PAGE 59

Chapter 2 Card Reference 2.2.3 TSC Card-Level Indicators 2.2.3 TSC Card-Level Indicators Table 2-3 describes the functions of the card-level LEDs on the TSC card faceplate. Table 2-3 TSC Card-Level Indicators Indicator Color Definition STAT Red Indicates a hardware fault; this LED is off during normal operation. Replace the card if the STAT LED persists. During diagnostics, the LED flashes quickly during initialization and slowly during configuration synchronization.
PAGE 60

Chapter 2 Card Reference 2.2.5 TSC Push-Button Switches 2.2.5 TSC Push-Button Switches Table 2-5 describes the functions of the push-button switches on the TSC card faceplate. Table 2-5 TSC Card Push-Button Switches Push-Button Function ACO Extinguishes external audible (environmental) alarms. When this button is activated, the amber-colored ACO LED turns on. LAMP TEST Verifies that all the LEDs in the shelf are functioning properly.
PAGE 61

Chapter 2 Card Reference 2.3.2 SSXC Slots and Connectors 2.3.2 SSXC Slots and Connectors Install an SSXC card in Slot 6 and a second SSXC card in Slot 8 for redundancy. (Slots 7 and 9 are also occupied by the SSXC faceplates.) The SSXC card has no external interfaces. All SSXC card interfaces are provided on the ONS 15600 backplane. 2.3.3 SSXC Faceplate and Block Diagram Figure 2-2 shows the SSXC card faceplate and a block diagram of the card.
PAGE 62

Chapter 2 Card Reference 2.3.4 SSXC Card-Level Indicators 2.3.4 SSXC Card-Level Indicators Table 2-6 describes the functions of the card-level LEDs on the SSXC card faceplate. Table 2-6 SSXC Card-Level Indicators Indicator Color Definition STAT Red Indicates a hardware fault; this LED is off during normal operation. Replace the card if the STAT LED persists. During diagnostics, the LED flashes quickly during initialization and slowly during configuration synchronization.
PAGE 63

Chapter 2 Card Reference 2.4.2 OC48/STM16 LR/LH 16 Port 1550 Faceplate and Block Diagram 2.4.2 OC48/STM16 LR/LH 16 Port 1550 Faceplate and Block Diagram Figure 2-3 shows the OC48/STM16 LR/LH 16 Port 1550 faceplate and a block diagram of the card.
PAGE 64

Chapter 2 Card Reference 2.4.3 OC48/STM16 LR/LH 16 Port 1550 Card-Level Indicators 2.4.3 OC48/STM16 LR/LH 16 Port 1550 Card-Level Indicators Table 2-7 describes the functions of the card-level LEDs on the OC48/STM16 LR/LH 16 Port 1550 card. Table 2-7 OC48/STM16 LR/LH 16 Port 1550 Card-Level Indicators Indicator Color Description STAT LED Red Indicates a hardware fault; this LED is off during normal operation. Replace the card if the STAT LED persists.
PAGE 65

Chapter 2 Card Reference 2.5 OC48/STM16 SR/SH 16 Port 1310 Card Table 2-9 OC48/STM16 LR/LH 16 Port 1550 Card OGI Connector Pinout (continued) Connector OGI Pin and Card Port 4 1 2 Transmit 16 Receive 16 3 4 Transmit 15 Receive 15 5 6 Transmit 14 Receive 14 7 8 Transmit 13 Receive 13 2.5 OC48/STM16 SR/SH 16 Port 1310 Card Note For card specifications, see the “A.2.4 OC48/STM16 SR/SH 16 Port 1310 Specifications” section on page A-8.
PAGE 66

Chapter 2 Card Reference 2.5.2 OC48/STM16 SR/SH 16 Port 1310 Faceplate and Block Diagram 2.5.2 OC48/STM16 SR/SH 16 Port 1310 Faceplate and Block Diagram Figure 2-4 shows the OC48/STM16 SR/SH 16 Port 1310 faceplate and block diagram.
PAGE 67

Chapter 2 Card Reference 2.5.3 OC48/STM16 SR/SH 16 Port 1310 Card-Level Indicators 2.5.3 OC48/STM16 SR/SH 16 Port 1310 Card-Level Indicators Table 2-10 describes the functions of the card-level LEDs on the OC48/STM16 SR/SH 16 Port 1310 card. Table 2-10 OC48/STM16 SR/SH 16 Port 1310 Card-Level Indicators Indicator Color Description STAT LED Red Indicates a hardware fault; this LED is off during normal operation. Replace the card if the STAT LED persists.
PAGE 68

Chapter 2 Card Reference 2.6 OC192/STM64 LR/LH 4 Port 1550 Card Table 2-12 OC48/STM16 SR/SH 16 Port 1310 Card OGI Connector Pinout (continued) Connector OGI Pin and Card Port 3 1 4 2 3 4 5 6 7 8 Transmit 12 Receive 12 Transmit 11 Receive 11 Transmit 10 Receive 10 Transmit 9 Receive 9 1 3 5 7 8 2 Transmit 16 Receive 16 4 Transmit 15 Receive 15 6 Transmit 14 Receive 14 Transmit 13 Receive 13 2.6 OC192/STM64 LR/LH 4 Port 1550 Card Note For card specifications, see the “A.2.
PAGE 69

Chapter 2 Card Reference 2.6.2 OC192/STM64 LR/LH 4 Port 1550 Faceplate and Block Diagram 2.6.2 OC192/STM64 LR/LH 4 Port 1550 Faceplate and Block Diagram Figure 2-5 shows the OC192/STM64 LR/LH 4 Port 1550 faceplate and a block diagram of the card.
PAGE 70

Chapter 2 Card Reference 2.6.3 OC192/STM64 LR/LH 4 Port 1550 Card-Level Indicators 2.6.3 OC192/STM64 LR/LH 4 Port 1550 Card-Level Indicators Table 2-13 describes the functions of the card-level LEDs on the OC192/STM64 LR/LH 4 Port 1550 card. Table 2-13 OC192/STM64 LR/LH 4 Port 1550 Card-Level Indicators Indicator Color Description STAT LED Red Indicates a hardware fault; this LED is off during normal operation. Replace the unit if the STAT LED persists.
PAGE 71

Chapter 2 Card Reference 2.7 OC192/STM64 SR/SH 4 Port 1310 Card Table 2-15 OC192/STM64 LR/LH 4 Port 1550 Card OGI Connector Pinout (continued) Connector OGI Pin and Card Port 4 1 2 3 4 5 6 7 8 — — Transmit 4 Receive 4 — — — — 2.7 OC192/STM64 SR/SH 4 Port 1310 Card Note For card specifications, see the “A.2.6 OC192/STM64 SR/SH 4 Port 1310 Specifications” section on page A-10.
PAGE 72

Chapter 2 Card Reference 2.7.2 OC192/STM64 SR/SH 4 Port 1310 Faceplate and Block Diagram 2.7.2 OC192/STM64 SR/SH 4 Port 1310 Faceplate and Block Diagram Figure 2-6 shows the OC192/STM64 SR/SH 4 Port 1310 faceplate and block diagram.
PAGE 73

Chapter 2 Card Reference 2.7.4 OC192/STM64 SR/SH 4 Port 1310 Network-Level Indicators Table 2-16 OC192/STM64 SR/SH 4 Port 1310 Card-Level Indicators (continued) Indicator Color Description SRV LED Green The service mode of the card. Green indicates that the card is in use, amber indicates that the card is out of service, and off indicates that the card is either booting or has no power applied. LASER ON Green The green LASER ON LED indicates that at least one of the card’s lasers is active. 2.7.
PAGE 74

Chapter 2 Card Reference 2.8.1 ASAP Connectors The ASAP card provides up to 16 Telcordia GR-253-CORE compliant, SONET OC-3, OC-12, OC-48, or Gigabit Ethernet ports, or up to 4 Telcordia GR-253-CORE compliant, SONET OC-192 ports, in any combination of line rates. The ASAP card, when used with the 4-Port I/O (4PIO) module, has up to 16 physical connector adapters (known as Small Form-factor Pluggables [SFPs]). The SFP ports operate at up to 2488.320 Mbps over a single-mode fiber.
PAGE 75

Chapter 2 Card Reference 2.8.2 ASAP Covers and Plugs 2.8.2 ASAP Covers and Plugs The covers and plugs that are shipped with the ASAP carrier card, 4PIOs, 1PIOs, and SFPs/XFPs must be used in configurations where any of the these slots are unoccupied. 2.8.3 ASAP Card Faceplate and Block Diagram with 4PIOs Installed Figure 2-7 shows the ASAP card faceplate, with four 4PIOs installed, and block diagram.
PAGE 76

Chapter 2 Card Reference 2.8.4 4PIO Module Faceplate 2.8.4 4PIO Module Faceplate Figure 2-8 shows the 4PIO module faceplate. Figure 2-8 4PIO Module Faceplate 1 ASAP 4P IO 2 Hand tighten, or remove the label to tighten using a Phillips screwdriver 3 124039 4 2.8.5 1PIO Module Faceplate Figure 2-9 shows the 1PIO module faceplate. Figure 2-9 1PIO Module Faceplate ASAP 1P IO 151941 Hand tighten, or remove the label to tighten using a Phillips screwdriver Cisco ONS 15600 Reference Manual, R7.
PAGE 77

Chapter 2 Card Reference 2.8.6 ASAP Card-Level Indicators 2.8.6 ASAP Card-Level Indicators Table 2-20 describes the functions of the card-level LEDs on the ASAP carrier module. Table 2-20 ASAP Card-Level Indicators Indicator Color Description STAT LED Red Indicates a hardware fault; this LED is off during normal operation. Replace the unit if the STAT LED persists. During diagnostics, the LED flashes quickly during initialization and slowly during configuration synchronization.
PAGE 78

Chapter 2 Card Reference 2.8.8 ASAP Card Port Numbering (4PIO Installed) 2.8.8 ASAP Card Port Numbering (4PIO Installed) Figure 2-10 shows the installed 4PIO modules and corresponding port numbers for each SFP slot.
PAGE 79

Chapter 2 Card Reference 2.8.9 ASAP Card Port Numbering (1PIO Installed) 2.8.9 ASAP Card Port Numbering (1PIO Installed) Figure 2-11 shows the installed 1PIO modules and corresponding port numbers for each XFP slot. Figure 2-11 ASAP 1PIO Port Numbering ASAP CC STAT LASER ON SRV ASAP 1P IO Port (PPM Slot) 1-1 1PIO Module 1 ASAP 1P IO 1PIO Module 2 Port (PPM Slot) 2-1 159056 ASAP 1P IO 1PIO Module 3 Port (PPM Slot) 3-1 ASAP 1P IO 1PIO Module 4 151969 Port (PPM Slot) 4-1 2.8.
PAGE 80

Chapter 2 Card Reference 2.8.10 SFP Modules Table 2-22 lists the SFPs (PPMs) that are compatible with the ASAP card. Caution Table 2-22 Use only SFPs certified for use in Cisco Optical Networking Systems. The qualified Cisco SFP pluggable module’s top assembly numbers (TANs) are provided in Table 2-22. SFP Compatibility Card ASAP 4PIO only (ONS 15600 SONET/SDH) Compatible SFP (Cisco Product ID) Cisco Top Assembly Number (TAN) ONS-SE-2G-L2 ONS-SE-Z1 ONS-SI-622-L2 ONS-SI-155-L2 ONS-SC-2G-46.
PAGE 81

Chapter 2 Card Reference 2.8.11 XFP Description Actuator/Button SFP Figure 2-14 Bail Clasp SFP 63067 63066 Figure 2-13 2.8.11 XFP Description The 10-Gbps 1310-nm and 1550-nm XFP transceivers are integrated fiber optic transceivers that provide high-speed serial links at the following signaling rates: 9.95 Gbps, 10.31 Gbps, and 10.52 Gbps. The XFP integrates both the receiver and transmit path. The transmit side recovers and retimes the 10-Gbps serial data and passes it to a laser driver.
PAGE 82

Chapter 2 Card Reference 2.8.12 PPM Provisioning Bail Clasp XFP (Unlatched) Figure 2-16 Bail Clasp XFP (Latched) 115719 115720 Figure 2-15 XFP dimensions are: • Height 0.33 in. (8.5 mm) • Width 0.72 in. (18.3 mm) • Depth 3.1 in.
PAGE 83

Chapter 2 Card Reference 2.9 Filler Card The Filler card is used to fill unused optical (OC-N) traffic card slots in the ONS 15600 shelf. In Software Release 1.1 and later, the Filler card has a card presence indicator (CPI) that allows the shelf to report the presence of the filler card to CTC. The Filler card uses dummy backplane connectors and a standard faceplate to secure the card in the empty shelf slot. Figure 2-17 shows the Filler card body and faceplate.
PAGE 84

Chapter 2 Card Reference 2.9 Filler Card Cisco ONS 15600 Reference Manual, R7.
PAGE 85

C H A P T E R 3 Card Protection Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
PAGE 86

Chapter 3 Card Protection 3.1 Optical Port Protection Table 3-1 Port Protection Types Type Ports Description 1+1 Any optical Pairs a working optical port with a protect optical port. Protect ports must match the line rate of the working ports. For example, Port 1 of an OC-48 card can only be protected by another OC-48 port. Ports do not need to be in adjoining slots. For maximum protection, provision the ports/cards in Slots 1 to 4 as working and the ports/cards in Slots 11 to 14 as protect.
PAGE 87

Chapter 3 Card Protection 3.2 Unprotected Ports With 1+1 protection, any port can be assigned to protect the traffic of a corresponding working port. A working port must be paired with a protect port of the same type, for example, an OC-48 port must be paired with another OC-48 port. 1+1 span protection can be either revertive or nonrevertive.
PAGE 88

Chapter 3 Card Protection 3.3 External Switching Commands A Manual switch will switch traffic if the path has an error rate less than the signal degrade. A Force switch will switch traffic even if the path has signal degrade (SD) or signal fail (SF) conditions; however, a Force switch will not override an SF on a 1+1 protection scheme. A Force switch has a higher priority than a Manual switch.
PAGE 89

C H A P T E R 4 Cisco Transport Controller Operation This chapter describes Cisco Transport Controller (CTC), the Cisco ONS 15600 software interface that is stored on the Timing and Shelf Controller (TSC) card and downloaded to your workstation each time you log into the ONS 15600. For CTC setup and login information, refer to the Cisco ONS 15600 Procedure Guide. Chapter topics include: • 4.1 CTC Software Delivery Methods, page 4-1 • 4.2 CTC Installation Overview, page 4-2 • 4.
PAGE 90

Chapter 4 Cisco Transport Controller Operation 4.1.2 CTC Software Installed on the PC or UNIX Workstation 4.1.2 CTC Software Installed on the PC or UNIX Workstation When you connect to the ONS 15600, the TSC card automatically downloads the CTC software to your computer, where it is automatically installed if you have the correct Java Runtime Environment (JRE). The automatic download/installation process ensures that your computer is running the same CTC software version as the TSC you are accessing.
PAGE 91

Chapter 4 Cisco Transport Controller Operation 4.3 PC and UNIX Workstation Requirements Note You can also use TL1 commands to communicate with the ONS 15600 through VT100 terminals and VT100 emulation software, or you can telnet to an ONS 15600 using TL1 port 3083. Refer to the Cisco ONS SONET TL1 Command Guide for a comprehensive list of TL1 commands. 4.3 PC and UNIX Workstation Requirements To use CTC with an ONS 15600, your computer must have a web browser with the correct JRE installed.
PAGE 92

Chapter 4 Cisco Transport Controller Operation 4.4 CTC Login Table 4-1 Minimum Computer Requirements for CTC (continued) Area Requirements Web browser • PC: Netscape 4.76, Netscape 7.x, Internet Explorer 6.x • UNIX Workstation: Netscape 4.76, Netscape 7.x Notes For the PC, use JRE 1.4.2 or 5.0 with any supported web browser. For UNIX, use JRE 1.4.2 or 5.0with Netscape 7.x or JRE 1.3.1_02 with Netscape 4.76. Netscape 4.76 or 7.x is available at the following site: http://channels.netscape.
PAGE 93

Chapter 4 Cisco Transport Controller Operation 4.4.1 Legal Disclaimer network for more recent versions of the software. (For more information about the automatic download of the latest CTC JAR files, see the “4.1.2 CTC Software Installed on the PC or UNIX Workstation” section on page 4-2.) • The Disable Circuit Management option omits the discovery of circuits. To view circuits immediately after logging in, make sure that Disable Circuit Management is not checked.
PAGE 94

Chapter 4 Cisco Transport Controller Operation 4.4.2 Login Node Group 4.4.2 Login Node Group Login node groups display nodes that have only an IP connection. After you are logged into CTC, you can create a login node group from the Edit > Preferences menu. Login groups appear in the Additional Nodes list on the Login window. For example, if you logged into Node 1, you would see Node 2 and Node 3 because they have DCC connectivity to Node 1.
PAGE 95

Chapter 4 Cisco Transport Controller Operation 4.5.1 Node View 4.5.1 Node View Node view allows you to view and manage one ONS 15600 node (Figure 4-2). The status area shows the node name; number of Critical (CR), Major (MJ), and Minor (MN) alarms; IP address; session boot date and time; name of the current logged-in user; and user security level. 4.5.1.1 CTC Card Colors The graphic area of the CTC window depicts the ONS 15600 shelf assembly.
PAGE 96

Chapter 4 Cisco Transport Controller Operation 4.5.1 Node View Table 4-3 Node View Card Port Colors and Service States (continued) Port Color Service State Description Gray OOS-MA,DSBLD (Out-of-Service and Management, Disabled) The port is out-of-service and unable to carry traffic. Loopbacks are not allowed in this service state. Green IS-NR (In-Service and Normal) The port is fully operational and performing as provisioned.
PAGE 97

Chapter 4 Cisco Transport Controller Operation 4.5.2 Network View Table 4-4 Node View Tabs and Subtabs Tab Description Subtabs Alarms Lists current alarms (CR, MJ, MN) for the node and updates them in real time. — Conditions Allows you to retrieve a list of standing conditions on the node. — History Provides a history of node alarms including date, type, and severity of each alarm. The Session subtab displays alarms and events for the current session.
PAGE 98

Chapter 4 Cisco Transport Controller Operation 4.5.2 Network View Figure 4-5 Network Displayed in CTC Network View Dots indicate selected node 96494 Bold letters indicate Login node; icon color Asterisk indicates indicates node status topology host The graphic area displays a background image with colored node icons. A Superuser can set up the logical network view feature, which enables each user to see the same network view. Lines show DCC connections between the nodes.
PAGE 99

Chapter 4 Cisco Transport Controller Operation 4.5.2 Network View 4.5.2.2 Network View Tabs Table 4-6 lists the tabs and subtabs available in the network view.
PAGE 100

Chapter 4 Cisco Transport Controller Operation 4.5.3 Card View Table 4-7 Icon Link Icons Description PPC icon Server Trail icon Note Link consolidation is only available on non-detailed maps. Non-detailed maps display nodes in icon form instead of detailed form, meaning the nodes appear as rectangles with ports on the sides. Refer to the Cisco ONS 15600 Procedure Guide for more information about consolidated links. 4.5.3 Card View The card view provides information about individual ONS 15600 cards.
PAGE 101

Chapter 4 Cisco Transport Controller Operation 4.5.3 Card View Figure 4-6 CTC Card View Showing an OC-192 Card Use the card view tabs and subtabs, shown in Table 4-8, to provision and manage the ONS 15600. The subtabs, fields, and information displayed under each tab depend on the card type selected.
PAGE 102

Chapter 4 Cisco Transport Controller Operation 4.5.4 Export and Print CTC Data 4.5.4 Export and Print CTC Data CTC data exported in HTML format can be viewed with any web browser, such as Netscape Communicator or Microsoft Internet Explorer. To display the data, use the browser’s File > Open command to open the CTC data file. CTC data exported as comma separated values (CSV) or tab separated values (TSV) can be viewed in text editors, word processors, spreadsheets, and database management applications.
PAGE 103

Chapter 4 Cisco Transport Controller Operation 4.6 CTC Card Reset Table 4-9 Table Data with Export Capability (continued) View or Card Tab Subtab(s) OC-N Cards Alarms — Conditions — History Session, Card Circuits Circuits, Rolls Provisioning Line, Threshold, STS, Alarm Behavior Maintenance Loopback, Transceiver, Protection Performance — 4.
PAGE 104

Chapter 4 Cisco Transport Controller Operation 4.8 Software Load Revert Note The ONS 15600 does not allow you to restore a database from one node to another node. You can install a database from one node on another node by using the Configure Node option on the Maintenance > Database tab. 4.8 Software Load Revert Before you upgrade to Software Release 7.2, you must create a database backup.
PAGE 105

C H A P T E R 5 Security This chapter provides information about Cisco ONS 15600 user security. To provision security, refer to the Cisco ONS 15600 Procedure Guide. Chapter topics include: • 5.1 Users IDs and Security Levels, page 5-1 • 5.2 User Privileges and Policies, page 5-1 • 5.3 Audit Trail, page 5-6 • 5.4 RADIUS Security, page 5-7 5.1 Users IDs and Security Levels When you log in to an ONS 15600 for the first time, you use the CISCO15 user ID, which is provided with every ONS 15600 system.
PAGE 106

Chapter 5 Security 5.2.1 User Privileges by Security Level 5.2.1 User Privileges by Security Level Table 5-1 shows the actions that each security level allows in node view. An “X” indicates that the action is supported on the associated security levels.
PAGE 107

Chapter 5 Security 5.2.
PAGE 108

Chapter 5 Security 5.2.
PAGE 109

Chapter 5 Security 5.2.
PAGE 110

Chapter 5 Security 5.3 Audit Trail Table 5-3 ONS 15600 User Idle Times Security Level Default Idle Time Superuser 15 minutes Provisioning 30 minutes Maintenance 60 minutes Retrieve Unlimited 5.2.2.3 Superuser Password and Login Privileges A Superuser can perform ONS 15600 user creation and management tasks from the network or node (default login) view. In network view, a Superuser can add, edit, or delete users from multiple nodes at one time.
PAGE 111

Chapter 5 Security 5.3.1 Audit Trail Log Entries The audit trail is stored in persistent memory and is not corrupted by processor switches, resets or upgrades. However, if a user pulls both TSC cards, the audit trail log is lost. 5.3.
PAGE 112

Chapter 5 Security 5.4.2 Shared Secrets • A client The server runs on a central computer typically at the customer's site, while the clients reside in the dial-up access servers and can be distributed throughout the network. An ONS 15600 node operates as a client of RADIUS. The client is responsible for passing user information to designated RADIUS servers, and then acting on the response that is returned.
PAGE 113

Chapter 5 Security 5.4.2 Shared Secrets Table 5-4 Shared Secret Character Groups Group Examples Letters (uppercase and lowercase) A, B, C, D and a, b, c, d Numerals 0, 1, 2, 3 Symbols (all characters not defined as letters or numerals) Exclamation point (!), asterisk (*), colon (:) The stronger your shared secret, the more secure are the attributes (for example, those used for passwords and encryption keys) that are encrypted with it.
PAGE 114

Chapter 5 Security 5.4.2 Shared Secrets Cisco ONS 15600 Reference Manual, R7.
PAGE 115

C H A P T E R 6 Timing This chapter provides information about Cisco ONS 15600 timing. To provision timing, refer to the Cisco ONS 15600 Procedure Guide. Chapter topics include: • 6.1 Timing Parameters, page 6-1 • 6.2 Network Timing, page 6-2 • 6.3 Synchronization Status Messaging, page 6-3 6.1 Timing Parameters SONET timing parameters must be set for each ONS 15600 node.
PAGE 116

Chapter 6 Timing 6.2 Network Timing 6.2 Network Timing Figure 6-1 shows an ONS 15600 network timing example. Node 1 is set to external timing. Two timing references are Stratum 1 timing sources wired to the BITS input pins on the Node 1 backplane. The third reference is set to internal clock. The BITS output pins on the backplane of Node 3 are used to provide timing to outside equipment, such as a digital access line access multiplexer.
PAGE 117

Chapter 6 Timing 6.
PAGE 118

Chapter 6 Timing 6.3 Synchronization Status Messaging Table 6-1 SSM Generation 1 Message Set (continued) Message Quality Description ST2 3 Stratum 2 ST3 4 Stratum 3 SMC 5 SONET minimum clock ST4 6 Stratum 4 DUS 7 Do not use for timing synchronization RES — Reserved; quality level set by user Table 6-2 lists the Generation 2 message set.
PAGE 119

C H A P T E R 7 Circuits and Tunnels Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
PAGE 120

Chapter 7 Circuits and Tunnels 7.1 Overview Note In this chapter, “cross-connect” and “circuit” have the following meanings: cross-connect refers to the connections that occur within a single ONS 15600 to allow a circuit to enter and exit an ONS 15600. Circuit refers to the series of connections from a traffic source (where traffic enters the ONS 15600 network) to the destination (where traffic exits an ONS 15600 network). 7.
PAGE 121

Chapter 7 Circuits and Tunnels 7.2 Circuit Properties • Direction—The circuit direction, either two-way or one-way. • Status—The circuit status; for details, see the “7.2.2 Circuit Status” section on page 7-6. • Source—The circuit source in the format: node/slot/port/STS. If an ASAP PPM port is the circuit source, the port format is PIM-PPM-port, where pluggable interface module (PIM) and PPM values are 1 through 4 (for example, p1-1-1). PPMs have only one port.
PAGE 122

Chapter 7 Circuits and Tunnels 7.2.1 Concatenated STS Time Slot Assignments Note You cannot set up VT circuits to terminate on an ONS 15600 node. However, you can create both STS and VT circuits that have an ONS 15454 or ONS 15327 source and destination with an ONS 15600 as a pass-through node. For information on VT circuit creation and tunneling, refer to the circuit chapters in the Cisco ONS 15327 Reference Manual and the Cisco ONS 15454 Reference Manual.
PAGE 123

Chapter 7 Circuits and Tunnels 7.2.
PAGE 124

Chapter 7 Circuits and Tunnels 7.2.2 Circuit Status Table 7-1 STS Mapping Using CTC (continued) Starting STS STS-3c STS-6c STS-9c STS-12c STS-18c STS-24c STS-36c STS-48c STS-192c 178 Yes No No No No No No No No 181 Yes Yes Yes Yes Yes No No No No 184 Yes Yes Yes No Yes No No No No 187 Yes Yes No No Yes No No No No 190 Yes No No No Yes No No No No 7.2.
PAGE 125

Chapter 7 Circuits and Tunnels 7.2.3 Circuit States Table 7-2 Note ONS 15600 Circuit Status (continued) Status Definition/Activity DISCOVERED_TL1 A TL1-created circuit or a TL1-like, CTC-created circuit is complete. A complete path from source to destination(s) exists. PARTIAL_TL1 A TL1-created circuit or a TL1-like, CTC-created circuit is missing a cross-connect or circuit span (network link), and a complete path from source to destination(s) does not exist.
PAGE 126

Chapter 7 Circuits and Tunnels 7.2.4 Circuit Protection Types • Note After circuit creation, you can change a circuit state in the Edit Circuit window or from the Tools > Circuits > Set Circuit State menu. After you have created an initial circuit in a CTC session, the subsequent circuit states default to the circuit state of the initial circuit, regardless of which nodes in the network the circuits traverse or the node.ckt.state default setting.
PAGE 127

Chapter 7 Circuits and Tunnels 7.2.5 Circuit Information in the Edit Circuit Window Table 7-3 Circuit Protection Types (continued) Protection Type Description Protected The circuit is protected by diverse SONET topologies, for example a BLSR and a path protection, or a path protection and 1+1. Unknown A circuit has a source and destination on different nodes and communication is down between the nodes. This protection type appears if not all circuit components are known.
PAGE 128

Chapter 7 Circuits and Tunnels 7.2.5 Circuit Information in the Edit Circuit Window • Number of alarms on each node organized by severity • Port service states on the circuit route • Alarm state/color of most severe alarm on port • Loopbacks • Path trace states • Path selector states Figure 7-2 shows a bidirectional STS circuit routed on a path protection.
PAGE 129

Chapter 7 Circuits and Tunnels 7.2.5 Circuit Information in the Edit Circuit Window A notation within or by the squares or selector pentagons in detailed view indicates switches and loopbacks, including: • F = Force switch • M = Manual switch • L = Lockout switch • Arrow = Facility (outward) or terminal (inward) loopback Figure 7-3 shows an example of the Edit Circuit window with a terminal loopback.
PAGE 130

Chapter 7 Circuits and Tunnels 7.3 Cross-Connect Card Bandwidth 7.3 Cross-Connect Card Bandwidth The single shelf cross-connect card (SSXC) cross-connect cards perform port-to-port, time-division multiplexing (TDM). The STS matrix has the capacity for 6144 STS terminations. Because each STS circuit requires a minimum of two terminations, one for ingress and one for egress, the SSXC has a capacity for 3072 STS circuits.
PAGE 131

Chapter 7 Circuits and Tunnels 7.4.2 IP-Encapsulated Tunnels 7.4.2 IP-Encapsulated Tunnels An IP-encapsulated tunnel puts an SDCC in an IP packet at a source node and dynamically routes the packet to a destination node. To compare traditional DCC tunnels with IP-encapsulated tunnels, a traditional DCC tunnel is configured as one dedicated path across a network and does not provide a failure recovery mechanism if the path is down.
PAGE 132

Chapter 7 Circuits and Tunnels 7.6 Path Protection Circuits From the UPSR Switch Counts subtab, you can: • Perform maintenance switches on the circuit selector. • View switch counts for the selectors. Figure 7-4 Editing Path Protection Selectors On the UPSR Switch Counts tab, you can view switch counts for the selectors (Figure 7-5). Cisco ONS 15600 Reference Manual, R7.
PAGE 133

Chapter 7 Circuits and Tunnels 7.7 Protection Channel Access Circuits Figure 7-5 Viewing Path Protection Switch Counts If ONS 15600s are connected to a third-party network, you can create an open-ended path protection circuit to route a circuit through it. To do this, you create three circuits. One circuit is created on the source ONS 15600 network. This circuit has one source and two destinations, one at each ONS 15600 that is connected to the third-party network.
PAGE 134

Chapter 7 Circuits and Tunnels 7.8 BLSR STS and VT Squelch Tables • PCA circuits are routed on working channels when you upgrade a BLSR from one optical speed to a higher optical speed. For example, if you upgrade a two-fiber OC-48 BLSR to an OC-192, STSs 25 to 48 on the OC-48 BLSR become working channels on the OC-192 BLSR. 7.
PAGE 135

Chapter 7 Circuits and Tunnels 7.8.2 BLSR VT Squelch Table 7.8.2 BLSR VT Squelch Table BLSR VT squelch tables only appear on the node dropping VTs from a BLSR and are used to perform VT-level squelching when a node is isolated. VT squelching is supported on the ONS 15454 and the ONS 15327 platforms.
PAGE 136

Chapter 7 Circuits and Tunnels 7.
PAGE 137

Chapter 7 Circuits and Tunnels 7.10.1 Bandwidth Allocation and Routing 7.10.1 Bandwidth Allocation and Routing Within a given network, CTC routes circuits on the shortest possible path between source and destination based on the circuit attributes, such as protection and type. CTC considers using a link for the circuit only if the link meets the following requirements: • The link has sufficient bandwidth to support the circuit. • The link does not change the protection characteristics of the path.
PAGE 138

Chapter 7 Circuits and Tunnels 7.11 Manual Circuit Routing Note Automatic routing and its associated subfields are not available if both the Automatic Circuit Routing NE default and the Network Circuit Automatic Routing Overridable NE default are set to FALSE. For a full description of these defaults see Appendix C, “Network Element Defaults.” 7.11 Manual Circuit Routing Routing circuits manually allows you to: • Choose a specific path, not just the shortest path chosen by automatic routing.
PAGE 139

Chapter 7 Circuits and Tunnels 7.12 Constraint-Based Circuit Routing Table 7-8 Unidirectional STS Circuits No. of Inbound Links No. of Outbound Links No. of Sources No. of Drops Connection Type 1 1 — — One-way 1 2 — — path protection head end — 2 1 — path protection head end 2 — — 1+ path protection drop and continue 7.12 Constraint-Based Circuit Routing When you create circuits, you can choose Fully Protected Path to protect the circuit from source to destination.
PAGE 140

Chapter 7 Circuits and Tunnels 7.13 Bridge and Roll 7.13 Bridge and Roll The CTC Bridge and Roll wizard reroutes live traffic without interrupting service. The bridge process takes traffic from a designated “roll from” facility and establishes a cross-connect to the designated “roll to” facility. When the bridged signal at the receiving end point is verified, the roll process creates a new cross-connect to receive the new signal. When the roll completes, the original cross-connects are released.
PAGE 141

Chapter 7 Circuits and Tunnels 7.13.2 Roll Status – Manual—You must complete a manual roll after a valid signal is received. One-way destination rolls are always manual. • Roll Path—The fixed point of the roll object. • Roll From Path— The old path that is being rerouted. • Roll To Path—The new path where the Roll From Path is rerouted. • Complete—Completes a manual roll after a valid signal is received.
PAGE 142

Chapter 7 Circuits and Tunnels 7.13.3 Single and Dual Rolls 7.13.3 Single and Dual Rolls Circuits have an additional layer of roll types: single and dual. A single roll on a circuit is a roll on one of its cross-connects. Use a single roll to: • Change either the source or destination of a selected circuit (Figure 7-8 and Figure 7-9, respectively). • Roll a segment of the circuit onto another chosen circuit (Figure 7-10 on page 7-24). This roll also results in a new destination or a new source.
PAGE 143

Chapter 7 Circuits and Tunnels 7.13.3 Single and Dual Rolls Single Roll from One Circuit to Another Circuit (Source Changes) S Node 1 Node 2 S2 Node 3 Node 4 D 134274 Figure 7-11 Original leg New leg Note Create a Roll To Circuit before rolling a circuit with the source on Node 3 and the destination on Node 4. A dual roll involves two cross-connects. It allows you to reroute intermediate segments of a circuit, but keep the original source and destination.
PAGE 144

Chapter 7 Circuits and Tunnels 7.13.4 Two Circuit Bridge and Roll Dual Roll to Reroute to a Different Node S Node 1 Node 2 Node 3 Node 4 Original leg New leg Note D 83102 Figure 7-13 If a new segment is created on Nodes 3 and 4 using the Bridge and Roll wizard, the created circuit has the same name as the original circuit with the suffix _ROLL**. The circuit source is on Node 3 and the circuit destination is on Node 4. 7.13.
PAGE 145

Chapter 7 Circuits and Tunnels 7.15 Reconfigured Circuits • Circuits types must be a compatible. • Circuit directions must be compatible. You can merge a one-way and a two-way circuit, but not two one-way circuits in opposing directions. • Circuit sizes must be identical. • Circuit end points must send or receive the same framing format. • The merged circuits must become a DISCOVERED circuit.
PAGE 146

Chapter 7 Circuits and Tunnels 7.16 Server Trails When creating circuits or VCATs, you can choose a server trail link during manual circuit routing. CTC may also route circuits over server trail links during automatic routing. VCAT common-fiber automatic routing is not supported. Cisco ONS 15600 Reference Manual, R7.
PAGE 147

C H A P T E R 8 SONET Topologies and Upgrades Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
PAGE 148

Chapter 8 SONET Topologies and Upgrades 8.2 Point-to-Point and Linear ADM Configurations 8.2 Point-to-Point and Linear ADM Configurations You can configure ONS 15600s as a line of add/drop multiplexers (ADMs) by configuring one OC-N port as the working path and a second port as the protect path.
PAGE 149

Chapter 8 SONET Topologies and Upgrades 8.3.1 Two-Fiber BLSRs Figure 8-2 Four-Node, Two-Fiber BLSR STSs 1-24 (working) STSs 25-48 (protect) Node 0 STSs 1-24 (working) STSs 25-48 (protect) OC-48 Ring Node 1 = Fiber 1 Node 2 = Fiber 2 96671 Node 3 The SONET K1, K2, and K3 bytes carry the information that governs BLSR protection switches. Each BLSR node monitors the K bytes to determine when to switch the SONET signal to an alternate physical path.
PAGE 150

Chapter 8 SONET Topologies and Upgrades 8.3.1 Two-Fiber BLSRs Figure 8-3 Four-Node, Two-Fiber BLSR Traffic Pattern Sample Node 0 Node 3 OC-48 Ring Node 1 Fiber 1 Node 2 Fiber 2 96672 Traffic flow Figure 8-4 shows how traffic is rerouted following a line break between Node 0 and Node 3. • All circuits originating on Node 0 that carried traffic to Node 2 on Fiber 2 are switched to the protect bandwidth of Fiber 1.
PAGE 151

Chapter 8 SONET Topologies and Upgrades 8.3.2 Four-Fiber BLSRs Figure 8-4 Four-Node, Two-Fiber BLSR Traffic Pattern Following Line Break Node 0 Node 3 OC-48 Ring Node 1 Fiber 1 Node 2 Fiber 2 96673 Traffic flow 8.3.2 Four-Fiber BLSRs Four-fiber BLSRs double the bandwidth of two-fiber BLSRs. Because they allow span switching as well as ring switching, four-fiber BLSRs increase the reliability and flexibility of traffic protection.
PAGE 152

Chapter 8 SONET Topologies and Upgrades 8.3.2 Four-Fiber BLSRs Figure 8-5 Four-Node, Four-Fiber BLSR Node 0 Span 4 Span 1 Span 5 Span 8 OC-48 Ring Span 6 Node 1 Span 7 Span 3 Span 2 = Working fibers Node 2 = Protect fibers 131781 Node 3 Four-fiber BLSRs provide span and ring switching: • Span switching (Figure 8-6 on page 8-7) occurs when a working span fails.
PAGE 153

Chapter 8 SONET Topologies and Upgrades 8.3.2 Four-Fiber BLSRs Figure 8-6 Four-Fiber BLSR Span Switch Node 0 Span 4 Span 1 Span 5 Span 8 OC-48 Ring Span 6 Node 1 Span 7 Span 3 Span 2 = Working fibers Node 2 • = Protect fibers 131783 Node 3 Ring switching (Figure 8-7) occurs when a span switch cannot recover traffic, such as when both the working and protect fibers fail on the same span. In a ring switch, traffic is routed to the protect fibers throughout the full ring.
PAGE 154

Chapter 8 SONET Topologies and Upgrades 8.3.3 BLSR Bandwidth Figure 8-7 Four-Fiber BLSR Ring Switch Node 0 Span 4 Span 1 Span 5 Span 8 OC-48 Ring Span 6 Node 1 Span 7 Span 3 Span 2 = Working fibers Node 2 = Protect fibers 131784 Node 3 8.3.3 BLSR Bandwidth BLSR nodes can terminate traffic coming from either side of the ring. Therefore, BLSRs are suited for distributed node-to-node traffic applications such as interoffice networks and access networks.
PAGE 155

Chapter 8 SONET Topologies and Upgrades 8.3.4 BLSR Fiber Connections Table 8-2 Four-Fiber BLSR Capacity OC Rate Working Bandwidth Protection Bandwidth Ring Capacity OC-48 STS 1-48 (Fiber 1) STS 1-48 (Fiber 2) 48 x N1 – PT 2 OC-192 STS 1-192 (Fiber 1) STS 1-192 (Fiber 2) 192 x N – PT 1. N equals the number of ONS 15600 nodes configured as BLSR nodes. 2. PT equals the number of STS-1 circuits passed through ONS 15600 nodes in the ring (capacity can vary depending on the traffic pattern).
PAGE 156

Chapter 8 SONET Topologies and Upgrades 8.3.4 BLSR Fiber Connections Always plug the transmit (Tx) connector of an OC-N port at one node into the receive (Rx) connector of an OC-N port at the adjacent node. Cards display an SF LED when Tx and Rx connections are mismatched.
PAGE 157

Chapter 8 SONET Topologies and Upgrades 8.
PAGE 158

Chapter 8 SONET Topologies and Upgrades 8.4 Path-Protected Mesh Networks Figure 8-11 Path-Protected Mesh Network Source Node Node 3 Node 5 Node 2 Node 4 Node 1 Node 10 Node 8 Node 6 Node 7 Node 11 Node 9 c raffi ng t ki Wor Destination Node = Primary path = Secondary path 78706 Protect traffic If full protection is selected, CTC creates a second unique route between Nodes 3 and 9 that passes through Nodes 2, 1, and 11.
PAGE 159

Chapter 8 SONET Topologies and Upgrades 8.5 In-Service Topology Upgrades Figure 8-12 PPMN Virtual Ring ONS 15454 Node 5 ONS 15454 Node 1 OC-12 ONS 15454 Node 4 ONS 15454 Node 8 OC-12 32137 OC-48 ONS 15454 Node 6 ONS 15454 Node 2 ONS 15454 Node 3 ONS 15454 Node 7 8.5 In-Service Topology Upgrades Topology upgrades can be performed in-service to convert a live network to a different topology.
PAGE 160

Chapter 8 SONET Topologies and Upgrades 8.5.1 Point-to-Point or Linear ADM to Two-Fiber BLSR Note A database restore on all nodes in a topology returns converted circuits to their original topology. Note Open-ended path protection and DRI configurations do not support in-service topology upgrades. 8.5.1 Point-to-Point or Linear ADM to Two-Fiber BLSR A 1+1 point-to-point or linear ADM to two-fiber BLSR conversion is manual.
PAGE 161

C H A P T E R 9 Management Network Connectivity This chapter provides an overview of Cisco ONS 15600 data communications network (DCN) connectivity. Cisco optical network communication is based on IP, including communication between Cisco Transport Controller (CTC) computers and ONS 15600s, and communication among networked ONS 15600 nodes.
PAGE 162

Chapter 9 Management Network Connectivity 9.2 ONS 15600 IP Addressing Scenarios • IP subnetting can create ONS 15600 node groups, which allow you to provision nodes in a network that are not connected using the data communications channel (DCC). • Different IP functions and protocols allow you to achieve specific network goals. For example, Proxy Address Resolution Protocol (ARP) enables one LAN-connected ONS 15600 to serve as a gateway for ONS 15600s that are not connected to the LAN.
PAGE 163

Chapter 9 Management Network Connectivity 9.2.2 Scenario 2: CTC and ONS 15600s Connected to Router Figure 9-1 Scenario 1: CTC and ONS 15600s on Same Subnet CTC Workstation IP Address 192.168.1.100 Subnet Mask 255.255.255.0 Default Gateway = N/A Host Routes = N/A LAN A ONS 15600 #2 IP Address 192.168.1.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A SONET RING ONS 15600 #3 IP Address 192.168.1.30 Subnet Mask 255.255.255.
PAGE 164

Chapter 9 Management Network Connectivity 9.2.3 Scenario 3: Using Proxy ARP to Enable an ONS 15600 Gateway Figure 9-2 Scenario 2: CTC and ONS 15600s Connected to Router LAN A Int "A" Int "B" Router IP Address of interface “A” to LAN “A” 192.168.1.1 IP Address of interface “B” to LAN “B” 192.168.2.1 Subnet Mask 255.255.255.0 Default Router = N/A Host Routes = N/A LAN B CTC Workstation IP Address 192.168.1.100 Subnet Mask 255.255.255.0 Default Gateway = 192.168.1.
PAGE 165

Chapter 9 Management Network Connectivity 9.2.4 Scenario 4: Default Gateway on CTC Computer Figure 9-3 Scenario 3: Using Proxy ARP CTC Workstation IP Address 192.168.1.100 Subnet Mark at CTC Workstation 255.255.255.0 Default Gateway = N/A LAN A ONS 15600 #1 IP Address 192.168.1.10 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A SONET RING ONS 15600 #3 IP Address 192.168.1.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A 81202 ONS 15600 #2 IP Address 192.168.1.
PAGE 166

Chapter 9 Management Network Connectivity 9.2.5 Scenario 5: Using Static Routes to Connect to LANs Figure 9-4 Scenario 4: Default Gateway on a CTC Computer CTC Workstation IP Address 192.168.1.100 Subnet Mask at CTC Workstation 255.255.255.0 Default Gateway = 192.168.1.10 Host Routes = N/A LAN A ONS 15600 #1 IP Address 192.168.1.10 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A SONET RING ONS 15600 #3 IP Address 192.168.3.30 Subnet Mask 255.255.255.
PAGE 167

Chapter 9 Management Network Connectivity 9.2.5 Scenario 5: Using Static Routes to Connect to LANs Figure 9-5 Scenario 5: Static Route with One CTC Computer Used as a Destination Router IP Address of interface ”A” to LAN “A” 192.168.1.1 IP Address of interface “B” to LAN “B” 192.168.2.1 Subnet Mask 255.255.255.0 LAN A Int "A" CTC Workstation IP Address 192.168.1.100 Subnet Mask 255.255.255.0 Default Gateway = 192.168.1.1 Host Routes = N/A Int "B" LAN B ONS 15600 #1 IP Address 192.168.2.
PAGE 168

Chapter 9 Management Network Connectivity 9.2.6 Scenario 6: Using OSPF Figure 9-6 Scenario 5: Static Route with Multiple LAN Destinations LAN D Router #3 LAN C Router #2 Router #1 IP Address of interface ”A” to LAN “A” 192.168.1.1 IP Address of interface “B” to LAN “B” 192.168.2.1 Subnet Mask 255.255.255.0 LAN A CTC Workstation IP Address 192.168.1.100 Subnet Mask 255.255.255.0 Default Gateway = 192.168.1.1 Host Routes = N/A Int "A" Int "B" LAN B ONS 15600 #1 IP Address 192.168.2.
PAGE 169

Chapter 9 Management Network Connectivity 9.2.6 Scenario 6: Using OSPF you do not need to manually enter static routes for ONS 15600 subnetworks. Figure 9-7 shows the same network enabled for OSPF. When you are logged into a ONS 15600 node, CTC does not allow both a DCC interface and a LAN interface in the same nonzero OSPF area. Figure 9-7 Scenario 6: OSPF Enabled Router IP Address of interface “A” to LAN A 192.168.1.1 IP Address of interface “B” to LAN B 192.168.2.1 Subnet Mask 255.255.255.
PAGE 170

Chapter 9 Management Network Connectivity 9.2.6 Scenario 6: Using OSPF Figure 9-8 Scenario 6: OSPF Not Enabled LAN A Int "A" CTC Workstation IP Address 192.168.1.100 Subnet Mask 255.255.255.0 Default Gateway = 192.168.1.1 Host Routes = N/A Router IP Address of interface “A” to LAN A 192.168.1.1 IP Address of interface “B” to LAN B 192.168.2.1 Subnet Mask 255.255.255.0 Static Routes = Destination 192.168.3.20 Next Hop 192.168.2.10 Destination 192.168.4.30 Next Hop 192.168.2.
PAGE 171

Chapter 9 Management Network Connectivity 9.2.7 Scenario 7: Provisioning the ONS 15600 Proxy Server If multiple ONS 15600 nodes and routers are connected to the same LAN in OSPF backbone area 0 and a link between two routers breaks, the backbone OSPF area 0 could divide into multiple gateway network elements (GNEs). If this occurs, the CTC session connected to Router 1 will not be able to communicate with the ONS 15600 connected to Router 2.
PAGE 172

Chapter 9 Management Network Connectivity 9.2.7 Scenario 7: Provisioning the ONS 15600 Proxy Server Note If you launch CTC against a node through a NAT (Network Address Translation) or PAT (Port Address Translation) router and that node does not have proxy enabled, your CTC session starts and initially appears to be fine. However CTC never receives alarm updates and disconnects and reconnects every two minutes.
PAGE 173

Chapter 9 Management Network Connectivity 9.2.7 Scenario 7: Provisioning the ONS 15600 Proxy Server Figure 9-10 ONS 15600 Proxy Server with GNE and ENEs on the Same Subnet Remote CTC 10.10.20.10 10.10.20.0/24 Interface 0/0 10.10.20.1 Router A Interface 0/1 10.10.10.1 10.10.10.0/24 ONS 15600 GNE 10.10.10.100/24 ONS 15600 ENE 10.10.10.150/24 ONS 15600 ENE 10.10.10.250/24 ONS 15600 ENE 10.10.10.200/24 SONET 81208 Ethernet Local/Craft CTC 192.168.20.
PAGE 174

Chapter 9 Management Network Connectivity 9.2.7 Scenario 7: Provisioning the ONS 15600 Proxy Server Figure 9-11 shows the same proxy server implementation with ONS 15600 ENEs on different subnets. The ONS 15600 GNEs and ENEs are provisioned with the settings shown in Table 9-2. Figure 9-11 Scenario 7: ONS 15600 Proxy Server with GNE and ENEs on Different Subnets Remote CTC 10.10.20.10 10.10.20.0/24 Interface 0/0 10.10.20.1 Router A Interface 0/1 10.10.10.1 10.10.10.0/24 ONS 15600 GNE 10.10.10.
PAGE 175

Chapter 9 Management Network Connectivity 9.2.7 Scenario 7: Provisioning the ONS 15600 Proxy Server Figure 9-12 shows the Figure 9-11 implementation with ONS 15600 ENEs in multiple rings. The ONS 15600 GNEs and ENEs are provisioned with the settings shown in Table 9-2. Figure 9-12 Scenario 7: ONS 15600 Proxy Server With ENEs on Multiple Rings Remote CTC 10.10.20.10 10.10.20.0/24 Interface 0/0 10.10.20.1 Router A Interface 0/1 10.10.10.1 10.10.10.0/24 ONS 15600 GNE 10.10.10.100/24 ONS 15600 ENE 192.168.
PAGE 176

Chapter 9 Management Network Connectivity 9.2.7 Scenario 7: Provisioning the ONS 15600 Proxy Server Table 9-3 Proxy Server Firewall Filtering Rules Packets Arriving At: TSC Ethernet interface DCC interface Are Accepted if the IP Destination Address Is: • The ONS 15600 itself • The ONS 15600 subnet broadcast address • Within the 224.0.0.
PAGE 177

Chapter 9 Management Network Connectivity 9.2.8 Scenario 8: Dual GNEs on a Subnet Figure 9-13 Nodes Behind a Firewall IIOP port Firewall Private network ONS 15600 CTC computer IIOP port Port filtering External network ONS 15600 Protected network 78337 Unprotected network Figure 9-14 shows a CTC computer and ONS 15600s behind firewalls. For the computer to access the ONS 15600, you must provision the IIOP port on the CTC computer and on the ONS 15600. Each firewall can use a different IIOP port.
PAGE 178

Chapter 9 Management Network Connectivity 9.2.8 Scenario 8: Dual GNEs on a Subnet then reconnects through the remaining GNEs. GNE load balancing reduces the dependency on the launch GNE and DCC bandwidth, which enhances CTC performance. Figure 9-15 shows a network with dual GNEs on the same subnet. Figure 9-15 Scenario 8: Dual GNEs on the Same Subnet Remote CTC 10.10.20.10 10.10.20.0/24 Interface 0/0 10.10.20.1 Router A Interface 0/1 10.10.10.1 ONS 15600 GNE 10.10.10.100/24 ONS 15600 GNE 10.10.10.
PAGE 179

Chapter 9 Management Network Connectivity 9.3 Provisionable Patchcords Figure 9-16 shows a network with dual GNEs on different subnets. Figure 9-16 Scenario 8: Dual GNEs on Different Subnets Remote CTC 10.10.20.10 10.10.20.0/24 Interface 0/0 10.10.20.1 Router A Interface 0/2 10.20.10.1 10.10.10.0/24 10.20.10.0/24 ONS 15600 GNE 10.20.10.100/24 ONS 15600 GNE 10.10.10.100/24 ONS 15600 ENE 192.168.10.200/24 ONS 15600 ENE 192.168.10.250/24 Ethernet Local/Craft CTC 192.168.20.
PAGE 180

Chapter 9 Management Network Connectivity 9.4 Routing Table Table 9-5 ONS 15600 and ONS 15454 Client and Trunk Card Combinations in Provisionable Patchcords ONS 15454 Client Cards MXP_2.5G_10G/ ONS 15600 Trunk Cards TXP_MR_10G TXP(P)_MR_2.5G MXP_2.
PAGE 181

Chapter 9 Management Network Connectivity 9.4 Routing Table Figure 9-17 Viewing the ONS 15600 Routing Table Table 9-6 shows sample routing entries for an ONS 15600. Table 9-6 Sample Routing Table Entries Entry Destination Mask Gateway Interface 1 0.0.0.0 0.0.0.0 172.20.214.1 cpm0 2 172.20.214.0 255.255.255.0 172.20.214.92 cpm0 3 172.20.214.92 255.255.255.255 127.0.0.1 lo0 4 172.20.214.93 255.255.255.255 0.0.0.0 pdcc0 5 172.20.214.94 255.255.255.255 172.20.214.
PAGE 182

Chapter 9 Management Network Connectivity 9.5 External Firewalls • Gateway (172.20.214.92) is the gateway address. All outbound traffic belonging to this network is sent to this gateway. • Interface (cpm0) indicates that the ONS 15600 Ethernet interface is used to reach the gateway. Entry 3 shows the following: • Destination (172.20.214.92) is the destination host IP address. • Mask (255.255.255.255) is a 32-bit mask, meaning only the 172.20.214.92 address is a destination. • Gateway (127.0.0.
PAGE 183

Chapter 9 Management Network Connectivity 9.
PAGE 184

Chapter 9 Management Network Connectivity 9.6 Open GNE access-list access-list access-list access-list access-list access-list access-list access-list 100 100 100 100 100 100 100 100 remark remark permit remark remark permit remark remark *** Inbound ACL, CTC -> NE *** access-list access-list access-list access-list 101 101 101 101 remark *** Outbound ACL, NE -> CTC *** remark permit tcp host 10.10.10.100 host 192.168.10.
PAGE 185

Chapter 9 Management Network Connectivity 9.6 Open GNE Figure 9-18 Proxy and Firewall Tunnels for Foreign Terminations Remote CTC 10.10.20.10 10.10.20.0/24 Interface 0/0 10.10.20.1 Router A Interface 0/1 10.10.10.1 ONS 15600 GNE 10.10.10.100/24 ONS 15600 ENE 10.10.10.150/24 ONS 15600 ENE 10.10.10.250/24 ONS 15600 ENE 10.10.10.200/24 Non-ONS node Foreign NE 130.94.122.199/28 Ethernet Local/Craft CTC 192.168.20.20 SONET 115757 10.10.10.0/24 Cisco ONS 15600 Reference Manual, R7.
PAGE 186

Chapter 9 Management Network Connectivity 9.7 TCP/IP and OSI Networking Figure 9-19 shows a remote node connected to an ENE Ethernet port. Proxy and firewall tunnels are useful in this example because the GNE would otherwise block IP access between the PC and foreign node. This configuration also requires a firewall tunnel on the ENE. Figure 9-19 Foreign Node Connection to an ENE Ethernet Port Remote CTC 10.10.20.10 10.10.20.0/24 Interface 0/0 10.10.20.1 Router A Interface 0/1 10.10.10.
PAGE 187

Chapter 9 Management Network Connectivity 9.7.
PAGE 188

Chapter 9 Management Network Connectivity 9.7.2 Link Access Protocol on the D Channel 9.7.2 Link Access Protocol on the D Channel LAP-D is a data link protocol used in the OSI protocol stack. LAP-D is assigned when you provision an ONS 15600 SDCC as OSI-only.
PAGE 189

Chapter 9 Management Network Connectivity 9.7.3 OSI Connectionless Network Service CLNP uses network service access points (NSAPs) to identify network devices. The CLNP source and destination addresses are NSAPs. In addition, CLNP uses a network element title (NET) to identify a network-entity in an end system (ES) or intermediate system (IS). NETs are allocated from the same name space as NSAP addresses. Whether an address is an NSAP address or a NET depends on the network selector value in the NSAP.
PAGE 190

Chapter 9 Management Network Connectivity 9.7.3 OSI Connectionless Network Service Table 9-9 NSAP Fields (continued) Field Definition Description System System identifier The ONS 15600 system identifier is set to its IEEE 802.3 MAC address. Each ONS 15600 supports twelve OSI virtual routers. Each router NSAP system identifier is the ONS 15600 IEEE 802.3 MAC address + n, where n = 0 to 2. For the primary virtual router, n = 0.
PAGE 191

Chapter 9 Management Network Connectivity 9.7.4 OSI Routing The ONS 15600 main NSAP address is shown on the node view Provisioning > OSI > Main Setup subtab. This address is also the Router 1 primary manual area address, which is viewed and edited on Provisioning > OSI > Routers subtab. See the “9.7.7 OSI Virtual Routers” section on page 9-37 for information about the OSI router and manual area addresses in CTC. 9.7.4 OSI Routing OSI architecture includes ESs and ISs.
PAGE 192

Chapter 9 Management Network Connectivity 9.7.4 OSI Routing Level 1 and Level 2 OSI Routing ES ES Area 1 Area 2 IS IS IS ES Level 2 routing Level 1 routing IS ES Level 1 routing 131597 Figure 9-21 Domain When you provision an ONS 15600 for a network with NEs that use both the TCP/IP and OSI protocol stacks, you will provision it as one of the following: • Intermediate System Level 1—The ONS 15600 performs OSI IS functions.
PAGE 193

Chapter 9 Management Network Connectivity 9.7.5 TARP OSI routing begins when the ESs discover the nearest IS by listening to ISH packets. When an ES wants to send a packet to another ES, it sends the packet to one of the ISs on its directly attached network. The router then looks up the destination address and forwards the packet along the best route. If the destination ES is on the same subnetwork, the local IS knows this from listening to ESHs and forwards the packet appropriately.
PAGE 194

Chapter 9 Management Network Connectivity 9.7.5 TARP Table 9-10 TARP PDU Fields (continued) Field Abbreviation Size (bytes) Description TID Originator Length tar-oln 1 The number of octets that are in the tar-tor field. Protocol Address Length tar-pln 1 The number of octets that are in the tar-por field. TID of Target tar-ttg n = 0, 1, 2... TID value for the target NE. TID of Originator tar-tor n = 0, 1, 2... TID value of the TARP PDU originator.
PAGE 195

Chapter 9 Management Network Connectivity 9.7.5 TARP • Type— Indicates whether the TARP PDU was created through the TARP propagation process (dynamic) or manually created (static). Provisionable timers, shown in Table 9-12, control TARP processing.
PAGE 196

Chapter 9 Management Network Connectivity 9.7.6 TCP/IP and OSI Mediation 9.7.5.3 Manual TARP Adjacencies TARP adjacencies can be manually provisioned in networks where ONS 15600s must communicate across routers or non-SONET NEs that lack TARP capability. In CTC, manual TARP adjacencies are provisioned on the node view Provisioning > OSI > TARP > MAT (Manual Area Table) subtab. The manual adjacency causes a TARP request to hop through the general router or non-SONET NE, as shown in Figure 9-22.
PAGE 197

Chapter 9 Management Network Connectivity 9.7.7 OSI Virtual Routers Figure 9-23 T–TD Protocol Flow OSS GNE ENE TL1 TL1 Gateway TL1 Gateway ACSE ACSE Presentation Presentation Session Session TP4 TP4 TL1 UDP • TCP UDP TCP TL1 IPv4 ISIS / CLNS ISIS / CLNS LLC1 LAPD LAPD LAN LAN DCC DCC 131954 IPv4 LLC1 FT–TD—Performs an FTP conversion between FTAM and FTP.
PAGE 198

Chapter 9 Management Network Connectivity 9.7.8 IP-over-CLNS Tunnels • FT-TD • T-TD • LAN subnet OSI virtual router constraints depend on the routing mode provisioned for the node. Table 9-14 shows the number of IS L1s, IS L1/L2s, and DCCs that are supported by each router. An IS L1 and IS L1/L2 support one ES per DCC subnet and up to 100 ESs per LAN subnet.
PAGE 199

Chapter 9 Management Network Connectivity 9.7.8 IP-over-CLNS Tunnels IP-over-CLNS Tunnel Flow NE-D NE-C NE-B NE-A (GNE) EMS SNMP RMON HTTP FTP Telnet SNMP RMON HTTP FTP Telnet UDP TCP UDP TCP IPv4 GRE Tunnel CLNP CLNP CLNP CLNP LLC1 LAPD LAPD LAPD LAN DCC DCC DCC GRE Tunnel IPv4 IPv4 LAPD LLC1 LLC1 DCC LAN LAN 131956 Figure 9-25 9.7.8.
PAGE 200

Chapter 9 Management Network Connectivity 9.7.8 IP-over-CLNS Tunnels Table 9-15 IP Over CLNS Tunnel IOS Commands Step Step Purpose 1 Router (config) # interface ctunnel interface-number Creates a virtual interface to transport IP over a CLNS tunnel and enters interface configuration mode. The interface number must be unique for each CTunnel interface. 2 Router (config-if # ctunnel destination remote-nsap-address Configures the destination parameter for the CTunnel.
PAGE 201

Chapter 9 Management Network Connectivity 9.7.8 IP-over-CLNS Tunnels Figure 9-26 IP Over CLNS Tunnel Scenario 1: ONS NE to Other Vender GNE CTC 1 10.10.10.100/24 Router 2 Interface 0/0: 10.10.10.10/24 Interface 0/1: 10.10.20.10/24 39.840F.80.111111.0000.1111.1111.aaaaaaaaaaaa.00 IP DCN Router 1 Interface 0/0: 10.10.20.20/24 Interface 0/1: 10.10.30.10/24 39.840F.80. 111111.0000.1111.1111.bbbbbbbbbbbb.00 IP/OSI Vendor GNE 10.10.30.20/24 39.840F.80. 111111.0000.1111.1111.cccccccccccc.
PAGE 202

Chapter 9 Management Network Connectivity 9.7.8 IP-over-CLNS Tunnels CTunnel (IP over CLNS) on Router 1: ip routing clns routing interface ctunnel 102 ip address 10.10.30.30 255.255.255.0 ctunnel destination 39.840F.80.1111.0000.1111.1111.dddddddddddd.00 interface Ethernet0/1 clns router isis router isis net 39.840F.80.1111.0000.1111.1111.bbbbbbbbbbbb.00 Figure 9-27 IP Over CLNS Tunnel Scenario 2: ONS Node to Router CTC 1 10.10.10.100/24 Router 2 Interface 0/0: 10.10.10.10/24 Interface 0/1: 10.10.20.
PAGE 203

Chapter 9 Management Network Connectivity 9.7.8 IP-over-CLNS Tunnels 9.7.8.4 IP-Over-CLNS Tunnel Scenario 3: ONS Node to Router Across an OSI DCN Figure 9-28 shows an IP-over-CLNS tunnel from an ONS node to a router across an OSI DCN. The other vendor NE has an OSI connection to an IP DCN to which a CTC computer is attached. An OSI-only (LAP-D) SDCC is created between the ONS NE 1 and the other vender GNE.
PAGE 204

Chapter 9 Management Network Connectivity 9.7.9 OSI/IP Networking Scenarios Figure 9-28 IP-Over-CLNS Tunnel Scenario 3: ONS Node to Router Across an OSI DCN CTC 1 10.10.10.100/24 IP Router 2 Interface 0/0: 10.10.10.10/24 Interface 0/1: 10.10.20.10/24 39.840F.80.111111.0000.1111.1111.aaaaaaaaaaaa.00 OSI DCN Router 1 Interface 0/0: 10.10.20.20/24 Interface 0/1: 10.10.30.10/24 39.840F.80. 111111.0000.1111.1111.bbbbbbbbbbbb.
PAGE 205

Chapter 9 Management Network Connectivity 9.7.9 OSI/IP Networking Scenarios • All ONS 15600 NEs participating in an OSI network run OSI over PPP between themselves. This is needed so that other vendor GNEs can route TL1 commands to all ONS 15600 NEs participating in the OSI network. 9.7.9.1 OSI/IP Scenario 1: IP OSS, IP DCN, ONS GNE, IP DCC, and ONS ENE Figure 9-29 shows OSI/IP Scenario 1, the current ONS 15600 IP-based implementation, with an IP DCN, IP-over-PPP DCC, and OSPF routing.
PAGE 206

Chapter 9 Management Network Connectivity 9.7.9 OSI/IP Networking Scenarios Figure 9-30 OSI/IP Scenario 2: IP OSS, IP DCN, ONS GNE, OSI DCC, and Other Vendor ENE 1 CTC/CTM IP OSS IP IP IP DCN IP ONS GNE 2 3 4 IP and OSI/PPP/DCC OSI/LAP-D/DCC IP/OSPF ONS NE OSI/IS-IS Other vendor NE 5 ONS NE OSI/LAP-D/DCC Other vendor NE 131932 IP and OSI/PPP/DCC 1 The IP OSS manages ONS 15600 and other vendor NEs using TL1 and FTP. 2 The ONS 15600 GNE performs mediation for other vendor NEs.
PAGE 207

Chapter 9 Management Network Connectivity 9.7.9 OSI/IP Networking Scenarios OSS-initiated software downloads consist of two parts: the OSS to destination NE TL1 download request and the file transfer. The TL1 request is handled the same as described earlier. The ONS 15600 NEs use FTP for file transfers. OSI-only NEs use FTAM to perform file transfers. The FTAM protocol is carried over OSI between the OSI NE and the ONS 15600 GNE. The GNE mediation translates between FTAM to FTP. 9.7.9.
PAGE 208

Chapter 9 Management Network Connectivity 9.7.9 OSI/IP Networking Scenarios Figure 9-31 OSI/IP Scenario 3: IP OSS, IP DCN, Other Vendor GNE, OSI DCC, and ONS ENE 1 CTC/CTM IP OSS IP IP IP DCN IP OSI 2 3 Other vendor GNE OSI/LAP-D/DCC OSI/LAPD/DCC 4 IP and OSI/PPP/DCC ONS NE 2 Other vendor NE OSI/LAP-D/DCC Other vendor NE 131933 ONS NE 1 1 The IP OSS manages the ONS 15600 and other vendor NEs using TL1 and FTP.
PAGE 209

Chapter 9 Management Network Connectivity 9.7.9 OSI/IP Networking Scenarios Figure 9-32 OSI/IP Scenario 3 with OSI/IP-over-CLNS Tunnel Endpoint at the GNE 1 CTC/CTM IP OSS IP IP IP DCN 2 IP Other vendor GNE 4 3 OSI/LAP-D/DCC OSI/LAPD/DCC 5 IP and OSI/PPP/DCC ONS NE 2 Other vendor NE OSI/LAP-D/DCC Other vendor NE 131931 ONS NE 1 1 The IP OSS manages ONS and other vendor NEs using TL1 and FTP. 2 The router routes requests to the other vender GNE.
PAGE 210

Chapter 9 Management Network Connectivity 9.7.9 OSI/IP Networking Scenarios Figure 9-33 OSI/IP Scenario 4: Multiple ONS DCC Areas 1 CTC/CTM IP OSS IP IP IP DCN IP IP 2 2 OSI 2 Other vendor GNE OSI/ LAP-D/ DCC OSI/ LAP-D/ DCC OSI/ LAP-D/ DCC ONS NE ONS NE IP and OSI/PPP/DCC IP and OSI/PPP/DCC IP and OSI/PPP/DCC ONS NE ONS NE ONS NE 131934 ONS NE 1 The IP OSS manages ONS 15600 and other vendor NEs using TL1 and FTP.
PAGE 211

Chapter 9 Management Network Connectivity 9.7.9 OSI/IP Networking Scenarios Figure 9-34 OSI/IP Scenario 5: GNE Without an OSI DCC Connection 1 CTC/CTM IP OSS IP IP IP DCN IP IP 3 2 Other vendor GNE OSI/ LAP-D/ DCC ONS NE Other vendor NE IP and OSI/PPP/DCC OSI/LAP-D/DCC ONS NE Other vendor NE 131935 4 OSI/ LAP-D/ DCC 1 The IP OSS manages ONS 15600 and other vendor NEs using TL1 and FTP. 2 The other vendor GNE performs mediation on TL1 and FTP, so DCCs are OSI-only.
PAGE 212

Chapter 9 Management Network Connectivity 9.7.9 OSI/IP Networking Scenarios Figure 9-35 OSI/IP Scenario 6: IP OSS, OSI DCN, ONS GNE, OSI DCC, and Other Vendor ENE 1 CTC/CTM IP OSS IP IP OSI OSI OSI DCN 3 2 OSI IP 4 ONS GNE ONS GNE IP and OSI/PPP/DCC ONS GNE OSI/ LAP-D/ DCC Other vendor NE OSI/LAP-D/DCC Other vendor NE 131936 OSI/ LAP-D/ DCC 1 The IP OSS manages ONS 15600 and other vendor NEs using TL1 and FTP. 2 OSS IP traffic is tunneled through the DCN to the ONS 15600 GNE.
PAGE 213

Chapter 9 Management Network Connectivity 9.7.9 OSI/IP Networking Scenarios Figure 9-36 OSI/IP Scenario 7: OSI OSS, OSI DCN, Other Vender GNE, OSI DCC, and ONS NEs 1 2 CTC/CTM IP OSS IP OSI OSI OSI DCN OSI 3 Other vendor GNE OSI/ LAP-D/ DCC ONS NE 1 Other vendor NE 1 IP and OSI/PPP/DCC ONS NE 2 OSI/ LAP-D/ DCC OSI/LAP-D/DCC Other vendor NE 2 IP and OSI/PPP/DCC 131937 ONS NE 3 1 ONS 15600 NEs are managed by CTC/CTM only (TL1/FTP is not used).
PAGE 214

Chapter 9 Management Network Connectivity 9.7.9 OSI/IP Networking Scenarios • TL1 management is not required. • FTP file transfer is not required. • TL1 and FTAM to FTP mediation is not required. Management traffic between CTC/CTM and ONS 15600 NEs is carried over an IP-over-CLNS tunnel. A static route is configured on the ONS 15600 that terminates the tunnel (ONS 15600 NE 1) so that downstream ONS 15600 NEs (ONS 15600 NE 2 and 3) know how to reach CTC/CTM. 9.7.9.
PAGE 215

Chapter 9 Management Network Connectivity 9.7.9 OSI/IP Networking Scenarios Figure 9-37 OSI/IP Scenario 8: OSI OSS, OSI DCN, ONS GNE, OSI DCC, and Other Vender NEs 1 2 CTC/CTM IP OSS IP OSI OSI OSI DCN 3 OSI ONS GNE 4 IP and OSI/LAP-D/ DCC ONS NE 1 IP and OSI/PPP/DCC ONS NE 2 OSI/ LAP-D/ DCC Other vendor NE 1 OSI/LAP-D/DCC Other vendor NE 2 Other vendor NE 3 131938 OSI/PPP/DCC 1 The ONS NEs are managed by CTC/CTM only (TL1/FTP is not used).
PAGE 216

Chapter 9 Management Network Connectivity 9.7.10 OSI Provisioning in CTC 9.7.10 OSI Provisioning in CTC Table 9-16 shows the OSI actions that are performed from the node view Provisioning tab. Refer to the Cisco ONS 15600 Procedures Guide for OSI procedures and tasks. Table 9-16 OSI Actions from the CTC Provisioning Tab Tab Actions OSI > Main Setup OSI > TARP > Config • View and edit Primary Area Address. • Change OSI routing mode. • Change LSP buffers.
PAGE 217

C H A P T E R 10 Ethernet Operation This chapter describes the operation of the Cisco ONS 15600 ASAP Ethernet card. For Ethernet card specifications, refer to Appendix A, “Hardware Specifications.” For step-by-step Ethernet card circuit configuration procedures, refer to the Cisco ONS 15600 Procedure Guide. Refer to the Cisco ONS SONET TL1 Command Guide for TL1 provisioning commands. Chapter topics include: • 10.1 Any Service Any Port Card Application, page 10-1 • 10.
PAGE 218

Chapter 10 Ethernet Operation 10.2 Transport Functionality Each ASAP 4-port I/O (ASAP_4PIO) PIM is hot-pluggable while other ports on other PIMs are functioning. Each SFP is also hot-pluggable. Layer 1 Ethernet transport is implemented for Gigabit Ethernet (GE) interfaces. GE traffic is encapsulated by generic framing procedure (GFP), ITU X.86, or Cisco high-level data link control/LAN extension (HDLC/LEX) and mapped into a SONET payload.
PAGE 219

Chapter 10 Ethernet Operation 10.2 Transport Functionality Figure 10-1 ONS 15600 Ethernet Frame Transport SONET Backplane Connection Ethernet Port Ethernet Processing Ethernet Port Ethernet Processing SONET Line Card 124483 Ethernet Line Card (ASAP) SONET Line Card Matrix The ONS 15600 provides transport functionality of all frames arriving on the Ethernet interfaces. Frames arriving on each Ethernet interface are mapped onto their own SONET path.
PAGE 220

Chapter 10 Ethernet Operation 10.3 Ethernet Rates and Mapping A valid frame is defined as one with the following attributes: • Valid preamble + synchronization • Valid size • Valid cyclic redundancy check (CRC) • Valid interpacket gap 10.3 Ethernet Rates and Mapping This section explains the Ethernet frame format, encapsulation methods, path and circuit configurations, and oversubscription. 10.3.1 Frame Size The IEEE 802.3 frame format is supported on the GE interfaces.
PAGE 221

Chapter 10 Ethernet Operation 10.3.4 Oversubscription Note Mapping depends on the particular concatenation being supported on the card. It also depends on the concatenation being supported on all of the network elements (NEs) that the end-to-end circuit is being built through. For full line-rate mapping to ensure that no frames are dropped, a GE interface is mapped to either an STS-24c or an STS-48c. At the STS-24c rate, the effects of bandwidth expansion due to HDLC/GFP/ITU X.
PAGE 222

Chapter 10 Ethernet Operation 10.4.3 VLAN The bridge sends bridge packets to the PPP half-bridge, which converts them to routed packets and forwards them to other router processes. Likewise, the PPP half-bridge converts routed packets to Ethernet bridge packets and sends them to the bridge on the same Ethernet subnetwork. The ASAP line card is transparent to any Layer 2 and above protocol packets (the entire control plane). Any PPP Half Bridge control packets are transported out to the SONET interface.
PAGE 223

Chapter 10 Ethernet Operation 10.6 Autonegotiation flow control, it generates and obeys pause frames. When it uses asymmetric flow control, it only generates pause frames. Through management control, the Ethernet interface allows an operator to turn flow control ON or OFF (the default is ON).
PAGE 224

Chapter 10 Ethernet Operation 10.7 Gigabit EtherChannel/IEEE 802.3ad Link Aggregation Figure 10-4 Autonegotiation Ethernet links Router 15xxx Router 15xxx 124486 SONET network Autonegotiation Autonegotiation 10.7 Gigabit EtherChannel/IEEE 802.3ad Link Aggregation The end-to-end Ethernet link integrity feature can be used in combination with Gigabit EtherChannel (GEC) capability on attached devices.
PAGE 225

C H A P T E R 11 Alarm Monitoring and Management This chapter explains how to manage alarms with Cisco Transport Controller (CTC), which includes: • 11.1 Overview, page 11-1 • 11.2 Alarms, Conditions, and History, page 11-1 • 11.3 Alarm Profiles, page 11-9 • 11.4 Alarm Filter, page 11-12 • 11.5 Alarm Suppression, page 11-12 • 11.6 External Alarms and Controls, page 11-13 To troubleshoot specific alarms, refer to the Cisco ONS 15600 Troubleshooting Guide. 11.
PAGE 226

Chapter 11 Alarm Monitoring and Management 11.2 Alarms, Conditions, and History Table 11-1 describes in the information in the Alarms window.
PAGE 227

Chapter 11 Alarm Monitoring and Management 11.2 Alarms, Conditions, and History Figure 11-1 shows the CTC node view Alarms window. Figure 11-1 Viewing Alarms in CTC Node View Alarms and conditions appear in one of five background colors, listed in Table 11-2, to communicate severity.
PAGE 228

Chapter 11 Alarm Monitoring and Management 11.2.1 Alarm Window Software Releases 7.0 and later have TL1 port-based alarm numbering that identifies an alarmed synchronous transport signal (STS) by its STS on a port rather than the STS on the optical card. The numbering is present in the STS alarm TL1 AID. The numbering scheme is described in Table 11-3.
PAGE 229

Chapter 11 Alarm Monitoring and Management 11.2.3 Conditions Window Figure 11-2 Select the Affected Circuits Option for an Alarm When the user selects the Select Affected Circuits option, the Circuits window opens to show the circuits that are affected by the alarm. 11.2.3 Conditions Window The Conditions window displays retrieved fault conditions. A condition is a fault or status detected by ONS 15600 hardware or software.
PAGE 230

Chapter 11 Alarm Monitoring and Management 11.2.4 Conditions Window Actions 11.2.4 Conditions Window Actions Table 11-5 shows the actions you can perform in the Conditions window. Table 11-5 Conditions Display Button Action Retrieve Retrieves the current set of all existing fault conditions, as maintained by the alarm manager, from the ONS 15600. Filter Allows you to change the Conditions window display to only show the conditions that meet a certain severity level or occur in a specified time.
PAGE 231

Chapter 11 Alarm Monitoring and Management 11.2.5 History Window Table 11-6 lists the Conditions window column headings and the information recorded in each column. Table 11-6 Conditions Column Description Column Information Recorded Date Date and time of the condition Node Shows the name of the node where the condition or alarm occurred. (Visible in network view.
PAGE 232

Chapter 11 Alarm Monitoring and Management 11.2.5 History Window Figure 11-4 Viewing All Alarms Reported for a Node Table 11-7 describes the information in the History window. Table 11-7 History Column Description Column Information Recorded Num An incrementing count of alarm or condition messages. (The column is hidden by default; to view it, right-click a column and choose Show Column > Num.) Ref The reference number assigned to the alarm or condition.
PAGE 233

Chapter 11 Alarm Monitoring and Management 11.2.6 Alarm History Actions Table 11-7 History Column Description (continued) Column Information Recorded Description Description of the condition Cond Condition name 11.2.6 Alarm History Actions You can retrieve and view the history of alarms and conditions, as well as Transient conditions (passing notifications of processes as they occur) in the CTC History window.
PAGE 234

Chapter 11 Alarm Monitoring and Management 11.3.2 Alarm Profile Buttons Figure 11-5 Node View Alarm Profiles Window Showing the Default Profiles of Listed Alarms 11.3.2 Alarm Profile Buttons The Alarm Profiles window has six buttons at the bottom. Table 11-8 describes each of the alarm profile buttons. Table 11-8 Alarm Profile Buttons Button Description New Adds a new alarm profile. Load Loads a profile to a node or a file. Store Saves profiles on a node (or nodes) or in a file.
PAGE 235

Chapter 11 Alarm Monitoring and Management 11.3.3 Alarm Profile Editing 11.3.3 Alarm Profile Editing Table 11-9 describes the five profile-editing options available when you right-click an alarm item in the profile column (such as Default). Table 11-9 Alarm Profile Editing Options Button Description Store Saves a profile in a node or in a file. Rename Changes a profile name. Clone Creates a new profile that contains the same alarm severity settings as the profile being cloned.
PAGE 236

Chapter 11 Alarm Monitoring and Management 11.4 Alarm Filter Alarm profiles form a hierarchy. A node-level alarm profile applies to all cards in the node except cards that have their own profiles. A card-level alarm profile applies to all ports on the card except ports that have their own profiles. At the node level, you can apply profile changes on a card-by-card basis or set a profile for the entire node.
PAGE 237

Chapter 11 Alarm Monitoring and Management 11.5.1 Alarms Suppressed for Maintenance 11.5.1 Alarms Suppressed for Maintenance When you place a port in OOS,MT administrative state, this raises the alarm suppressed for maintenance (AS-MT) alarm in the Conditions and History windows1 and causes subsequently raised alarms for that port to be suppressed.
PAGE 238

Chapter 11 Alarm Monitoring and Management 11.6.1 External Alarm Input 11.6.1 External Alarm Input You can provision each alarm input separately. Provisionable characteristics of external alarm inputs include: • Alarm type • Alarm severity (CR, MJ, MN, NA, and NR) • Alarm-trigger setting (open or closed) • Virtual wire associated with the alarm • CTC alarm log description (up to 63 characters) 11.6.2 External Control Output You can provision each alarm output separately.
PAGE 239

Chapter 11 Alarm Monitoring and Management 11.6.3 Virtual Wires for External Alarms in Mixed Networks Figure 11-7 Virtual Wires Seen from an ONS 15600 Cisco ONS 15600 Reference Manual, R7.
PAGE 240

Chapter 11 Alarm Monitoring and Management 11.6.3 Virtual Wires for External Alarms in Mixed Networks Cisco ONS 15600 Reference Manual, R7.
PAGE 241

C H A P T E R 12 Performance Monitoring Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
PAGE 242

Chapter 12 Performance Monitoring 12.2 Intermediate-Path Performance Monitoring the node continues to count the errors during a given accumulation period. If 0 is entered as the threshold value, the performance monitoring parameter is disabled. Figure 12-1 shows the Provisioning > SONET Thresholds tabs for an OC-48/STM-16 card.
PAGE 243

Performance Monitoring 12.2 Intermediate-Path Performance Monitoring Figure 12-2 shows the Provisioning > SONET STS tabs for an OC-48 card. Figure 12-2 SONET STS tab STS Tab for Enabling IPPM Provisioning tab Card view 96724 Chapter 12 IPPM enables LTE cards to monitor near-end path PM data on individual synchronous transport signal (STS) payloads.
PAGE 244

Chapter 12 Performance Monitoring 12.3 Pointer Justification Count 12.3 Pointer Justification Count Pointers are used to compensate for frequency and phase variations. Pointer justification counts indicate timing differences on SONET networks. When a network is not synchronized, frequency and phase variations occur on the transported signal. Excessive frequency and phase variations can cause terminating equipment to slip.
PAGE 245

Chapter 12 Performance Monitoring 12.4 Performance-Monitoring Parameter Definitions PPJC is a count of path-detected (PPJC-Pdet) or path-generated (PPJC-Pgen) positive pointer justifications depending on the specific PM name. NPJC is a count of path-detected (NPJC-Pdet) or path-generated (NPJC-Pgen) negative pointer justifications depending on the specific PM name. A consistent pointer justification count indicates clock synchronization problems between nodes.
PAGE 246

Chapter 12 Performance Monitoring 12.4 Performance-Monitoring Parameter Definitions Table 12-2 Performance Monitoring Parameters (continued) Parameter Definition ES-PFE Far-End STS Path Errored Seconds (ES-PFE) is a count of the seconds when at least one STS path BIP error was detected. An AIS-P defect (or a lower-layer, traffic-related, far-end defect) or an LOP-P defect can also cause an STS ES-PFE.
PAGE 247

Chapter 12 Performance Monitoring 12.4 Performance-Monitoring Parameter Definitions Table 12-2 Performance Monitoring Parameters (continued) Parameter Definition OPR Optical Power Received (OPR) is represented by the percentage of the normal optical receive power of the card port. The high optical power received (OPR-HIGH) threshold is the percentage of the calibrated receive optical power when a high receive power TCA occurs.
PAGE 248

Chapter 12 Performance Monitoring 12.4 Performance-Monitoring Parameter Definitions Table 12-2 Performance Monitoring Parameters (continued) Parameter Definition PSD (1+1) In a 1+1 protection scheme, Protection Switching Duration (PSD) applies to the length of time, in seconds, that service is carried on another line. For a working line, PSD is a count of the number of seconds that service was carried on the protection line.
PAGE 249

Chapter 12 Performance Monitoring 12.5 Optical Card Performance Monitoring Table 12-2 Performance Monitoring Parameters (continued) Parameter Definition SES-PFE Far-End STS Path Severely Errored Seconds (SES-PFE) is a count of the seconds when K (2400) or more STS path BIP errors were detected. An AIS-P defect (or a lower-layer, traffic-related, far-end defect) or an LOP-P defect can also cause an SES-PFE.
PAGE 250

Chapter 12 Performance Monitoring 12.5.
PAGE 251

Chapter 12 Performance Monitoring 12.5.2 Physical Layer Parameters 12.5.2 Physical Layer Parameters The ONS 15600 retrieves the OPR, OPT, and LBC from the line card and stores these values with the PM counts for the 15-minute and 1-day periods. You can retrieve current OPR, OPT, and LBC values for each port by displaying the card view in CTC and clicking the Maintenance > Transceiver tabs. The physical layer performance parameters consist of normalized and non-normalized values of LBC, OPT, and OPR.
PAGE 252

Chapter 12 Performance Monitoring 12.6.2 ASAP Card Ethernet Performance Monitoring Parameters 1. SONET path performance monitoring parameters increment only if IPPM is enabled. For additional information, see the “12.2 Intermediate-Path Performance Monitoring” section on page 12-2. To monitor SONET path performance monitoring parameters, log into the far-end node directly. 2. For information about troubleshooting path protection switch counts, refer to the Cisco ONS 15600 Troubleshooting Guide. 3.
PAGE 253

Chapter 12 Performance Monitoring 12.6.2 ASAP Card Ethernet Performance Monitoring Parameters Table 12-6 ASAP Ethernet Statistics Parameters (continued) Parameter Meaning Tx Multicast Packets Number of broadcast packets transmitted since the last counter reset. Rx Bytes Number of bytes received since the last counter reset. Tx Bytes Number of bytes transmitted since the last counter reset.
PAGE 254

Chapter 12 Performance Monitoring 12.6.2 ASAP Card Ethernet Performance Monitoring Parameters Table 12-6 ASAP Ethernet Statistics Parameters (continued) Parameter Meaning etherStatsBroadcastPkts The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets. etherStatsMulticastPkts The total number of good packets received that were directed to a multicast address.
PAGE 255

Chapter 12 Performance Monitoring 12.6.2 ASAP Card Ethernet Performance Monitoring Parameters Table 12-6 ASAP Ethernet Statistics Parameters (continued) Parameter Meaning dot3StatsInternalMacTransmitErrors A count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error.
PAGE 256

Chapter 12 Performance Monitoring 12.6.2 ASAP Card Ethernet Performance Monitoring Parameters Table 12-7 Note maxBaseRate for STS Circuits STS maxBaseRate STS-1 51840000 STS-3c 155000000 STS-6c 311000000 STS-12c 622000000 Line utilization numbers express the average of ingress and egress traffic as a percentage of capacity. 12.6.2.3 ASAP Card Ether Ports History Window The Ethernet Ether Ports History window lists past Ethernet statistics for the previous time intervals.
PAGE 257

Chapter 12 Performance Monitoring 12.6.2 ASAP Card Ethernet Performance Monitoring Parameters Table 12-9 ASAP Card POS Ports Parameters (continued) Parameter Meaning Tx Octets Number of bytes transmitted (to the SONET/SDH path) after the bytes undergoing HLDC encapsulation by the policy engine. Rx Shorts Number of packets below the minimum packet size received. Rx Runts Total number of frames received that are less than 5 bytes.
PAGE 258

Chapter 12 12.6.2 ASAP Card Ethernet Performance Monitoring Parameters Cisco ONS 15600 Reference Manual, R7.
PAGE 259

C H A P T E R 13 SNMP This chapter explains Simple Network Management Protocol (SNMP) as implemented by the Cisco ONS 15600. For SNMP setup information, refer to the Cisco ONS 15600 Procedure Guide. Chapter topics include: • 13.1 SNMP Overview, page 13-1 • 13.2 Basic SNMP Components, page 13-2 • 13.3 SNMP External Interface Requirement, page 13-4 • 13.4 SNMP Version Support, page 13-4 • 13.5 SNMP Message Types, page 13-4 • 13.6 SNMP Management Information Bases, page 13-5 • 13.
PAGE 260

Chapter 13 SNMP 13.2 Basic SNMP Components Note It is recommended that the SNMP Manager timeout value be set to 60 seconds. Under certain conditions, if this value is lower than the recommended time, the TCC card can reset. However, the response time depends on various parameters such as object being queried, complexity, and number of hops in the node, etc. Note The CERENT-MSDWDM-MIB.mib, CERENT-FC-MIB.mib, and CERENT-GENERIC-PM-MIB.
PAGE 261

Chapter 13 SNMP 13.2 Basic SNMP Components Figure 13-2 Example of the Primary SNMP Components Management Entity NMS Agent Agent Management Database Management Database Management Database 33930 Agent Managed Devices An agent (such as SNMP) residing on each managed device translates local management information data, such as performance information or event and error information caught in software traps, into a readable form for the management system.
PAGE 262

Chapter 13 SNMP 13.3 SNMP External Interface Requirement 13.3 SNMP External Interface Requirement Since all SNMP requests come from a third-party application, the only external interface requirement is that a third-part SNMP client application can upload RFC 3273 SNMP MIB variables in the etherStatsHighCapacityTable, etherHistoryHighCapacityTable, or mediaIndependentTable. 13.4 SNMP Version Support The ONS 15600 supports SNMPv1 and SNMPv2c traps and get requests.
PAGE 263

Chapter 13 SNMP 13.6 SNMP Management Information Bases 13.6 SNMP Management Information Bases This section contains the following information: • 13.6.1 IETF-Standard MIBs for ONS 15600, page 13-5 lists IETF-standard MIBs that are implemented in the ONS 15600 and shows their compilation order. • 13.6.2 Proprietary ONS 15600 MIBs, page 13-6 lists proprietary MIBs for the ONS 15600 and shows their compilation order. 13.6.
PAGE 264

Chapter 13 SNMP 13.6.2 Proprietary ONS 15600 MIBs Table 13-2 IETF Standard MIBs Implemented in the ONS 15600 System (continued) RFC1 Number Module Name Title/Comments 2674 P-BRIDGE-MIB-rfc2674.mib Q-BRIDGE-MIB-rfc2674.
PAGE 265

Chapter 13 SNMP 13.7.1 Generic and IETF Traps 13.7.1 Generic and IETF Traps Table 13-4 contains information about the generic threshold and performance monitoring MIBs that can be used to monitor any network element (NE) contained in the network. The ONS 15600 supports the generic IETF traps listed in Table 13-4. Table 13-4 ONS 15600 Generic Traps Trap From RFC No. MIB Description coldStart RFC1213-MIB Agent up, cold start. warmStart RFC1213-MIB Agent up, warm start.
PAGE 266

Chapter 13 SNMP 13.7.2 Variable Trap Bindings Table 13-5 Group B 15600 SNMPv2 Trap Variable Bindings (continued) (Variable Binding Associated Trap Name(s) Number) SNMPv2 Variable Bindings (1) dsx3LineStatus (2) dsx3LineStatusLastChange The value of MIB II's sysUpTime object at the time this DS3/E3 entered its current line status state. If the current state was entered prior to the last reinitialization of the proxy-agent, then the value is zero.
PAGE 267

Chapter 13 SNMP 13.7.2 Variable Trap Bindings Table 13-5 Group D 15600 SNMPv2 Trap Variable Bindings (continued) (Variable Binding Associated Trap Name(s) Number) SNMPv2 Variable Bindings failureDetectedExternal ToTheNE (from CERENT-600-mib) Description (1) cerentGenericNodeTime The time that an event occurred. (2) cerentGenericAlarmState The alarm severity and service-affecting status. Severities are Minor (MN), Major (MJ), and Critical (CR).
PAGE 268

Chapter 13 SNMP 13.7.2 Variable Trap Bindings Table 13-5 Group E 15600 SNMPv2 Trap Variable Bindings (continued) (Variable Binding Associated Trap Name(s) Number) SNMPv2 Variable Bindings performanceMonitorThr (1) esholdCrossingAlert (2) (from CERENT-600-mib) cerentGenericNodeTime The time that an event occurred. cerentGenericAlarmState The alarm severity and service-affecting status. Severities are Minor (MN), Major (MJ), and Critical (CR).
PAGE 269

Chapter 13 SNMP 13.8 Proxy Over Firewalls Table 13-5 Group F 15600 SNMPv2 Trap Variable Bindings (continued) (Variable Binding Associated Trap Name(s) Number) SNMPv2 Variable Bindings All other traps (from CERENT-600-MIB) not listed above Description (1) cerentGenericNodeTime The time that an event occurred. (2) cerentGenericAlarmState The alarm severity and service-affecting status. Severities are Minor (MN), Major (MJ), and Critical (CR).
PAGE 270

Chapter 13 SNMP 13.8.1 Remote Monitoring For security reasons, the SNMP proxy feature must be enabled at all receiving and transmitting NEs to function. For instructions to do this, refer to the Cisco ONS 15600 Procedure Guide. 13.8.1 Remote Monitoring The ONS 15600 incorporates RMON to allow network operators to monitor Ethernet facility performance and events. Software R7.
PAGE 271

Chapter 13 SNMP 13.8.4 Ethernet Statistics RMON Group 13.8.4 Ethernet Statistics RMON Group The Ethernet Statistics group contains the basic statistics monitored for each subnetwork in a single table called the etherStatsTable. 13.8.4.1 Row Creation in etherStatsTable The SetRequest PDU for creating a row in this table should contain all the values needed to activate a row in a single set operation, and an assigned status variable to createRequest.
PAGE 272

Chapter 13 SNMP 13.8.5 History Control RMON Group The historyControlTable maximum row size is determined by multiplying the number of ports on a card by the number of sampling periods. For example, an ONS 15600 E100 card contains 24 ports, which multiplied by periods allows 96 rows in the table. An E1000 card contains 14 ports, which multiplied by four periods allows 56 table rows.
PAGE 273

Chapter 13 SNMP 13.8.5 History Control RMON Group 13.8.5.8 Alarm Table The NMS uses the alarmTable to determine and provision network performance alarmable thresholds. 13.8.5.9 Get Requests and GetNext Requests These PDUs are not restricted. 13.8.5.10 Row Deletion in alarmTable To delete a row from the table, the SetRequest PDU should contain an alarmStatus value of 4 (invalid). A deleted row can be recreated. Entries in this table are preserved if the SNMP agent is restarted. 13.8.5.
PAGE 274

Chapter 13 SNMP 13.8.5 History Control RMON Group Cisco ONS 15600 Reference Manual, R7.
PAGE 275

A A P P E N D I X Hardware Specifications Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
PAGE 276

Appendix A Hardware Specifications A.1.3 Cards • Single Shelf Cross Connect (SSXC): Slots 6/7, 8/9 A.1.3 Cards The ONS 15600 has the following cards: • TSC • SSXC • ASAP • OC48/STM16 LR16 1550 • OC48/STM16 SR16 1310 • OC192/STM64 LR4 1550 • OC192/STM64 SR4 1310 A.1.
PAGE 277

Appendix A Hardware Specifications A.1.7 External LAN Interface A.1.7 External LAN Interface The external LAN interface has the following specifications: • 10/100BaseT Ethernet • Backplane access: RJ-45 connector A.1.8 TL1 Craft Interface The craft interface has the following specifications: • Speed: 9600 bps • Backplane (CAP) access: EIA/TIA-232 DB-9 type connector A.1.
PAGE 278

Appendix A Hardware Specifications A.1.13 Database Storage A.1.13 Database Storage The ONS 15600 has the following database storage specifications: • Nonvolatile memory: 512 MB, IDE FLASH memory A.1.14 Environmental Specifications The ONS 15600 has the following environmental specifications: • Operating temperature: 23 to 122 degrees Fahrenheit (–5 to +50 degrees Celsius) • Operating humidity: 5 to 95%, noncondensing A.1.
PAGE 279

Appendix A Hardware Specifications A.2 Card Specifications A.2 Card Specifications This section provides specifications for the TSC, SSXC, OC48/STM16 LR/LH 16 Port 1550, OC48/STM16 SR/SH 16 Port 1310, OC192/STM64 LR/LH 4 Port 1550, OC192/STM64 SR/SH 4 Port 1310, ASAP, and Filler cards. A.2.1 TSC Card Specifications Table A-3 shows the TSC card specifications.
PAGE 280

Appendix A Hardware Specifications A.2.2 SSXC Specifications A.2.2 SSXC Specifications Table A-4 shows the SSXC card specifications. Table A-4 SSXC Card Specifications Specification Type Description Cross-connect Connection setup time: 7 microseconds Latency: 0.5 microseconds Operating temperature 23 to 122 degrees Fahrenheit (–5 to +50 degrees Celsius) Operating humidity 5 to 95%, noncondensing Dimensions Height: 16.50 in. (419 mm) Width: 2.36 in. (60 mm) Depth: 18.31 in.
PAGE 281

Appendix A Hardware Specifications A.2.3 OC48/STM16 LR/LH 16 Port 1550 Specifications Table A-5 OC48/STM16 LR/LH 16 Port 1550 Card Specifications (continued) Specification Type Description Receiver Max. receiver level: –9 dBm Min.
PAGE 282

Appendix A Hardware Specifications A.2.4 OC48/STM16 SR/SH 16 Port 1310 Specifications A.2.4 OC48/STM16 SR/SH 16 Port 1310 Specifications Table A-6 shows the OC48/STM16 SR/SH 16 Port 1310 card specifications. Table A-6 OC48/STM16 SR/SH 16 Port 1310 Card Specifications Specification Type Description Line Bit rate: 2.49 Gbps Code: Scrambled NRZ Fiber: 1310 nm single-mode Loopback mode: Facility Connectors: OGI Compliance: SONET Telcordia GR-253 Transmitter Max. transmitter output power: –3 dBm Min.
PAGE 283

Appendix A Hardware Specifications A.2.5 OC192/STM64 LR/LH 4 Port 1550 Specifications A.2.5 OC192/STM64 LR/LH 4 Port 1550 Specifications Table A-7 shows the OC192/STM64 LR/LH 4 Port 1550 card specifications. Table A-7 OC192/STM64 LR/LH 4 Port 1550 Card Specifications Specification Type Description Line Bit rate: 9.96 Gbps Code: Scrambled NRZ Fiber: 1550 nm Single mode Transmitter Max. transmitter output power: +7 dBm Min.
PAGE 284

Appendix A Hardware Specifications A.2.6 OC192/STM64 SR/SH 4 Port 1310 Specifications A.2.6 OC192/STM64 SR/SH 4 Port 1310 Specifications Table A-8 shows the OC192/STM64 SR/SH 4 Port 1310 card specifications. Table A-8 OC192/STM64 SR/SH 4 Port 1310 Card Specifications Specification Type Description Line Bit rate: 9.96 Gbps Code: Scrambled NRZ Fiber: 1310 nm single mode Transmitter Max. transmitter output power: –1 dBm Min.
PAGE 285

Appendix A Hardware Specifications A.2.7 ASAP Specifications A.2.7 ASAP Specifications Table A-9 shows the ASAP card specifications. Table A-9 ASAP Card Specifications Specification Type Description Carrier Card (CC) Contains slots for four pluggable ASAP I/O cards, which can be used to provide a variety of optical line interfaces. The CC provides 4 electrical STS-48 or Gigabit Ethernet signals to each ASAP I/O card (for 16 total) and 16 redundant electrical STS-48 matrix interfaces to the backplane.
PAGE 286

Appendix A Hardware Specifications A.2.8 Filler Card Specifications A.2.8 Filler Card Specifications Table A-10 shows the Filler card specifications. Table A-10 Filler Card Specifications Specification Type Description Dimensions Height: 16.50 in. (419 mm) Width:1.50 in. (38 mm) Depth: 18.31 in. (465 mm) Card weight: 2.5 lb (1.134 kg) A.3 SFP/XFP Specifications Table A-11 and Table A-12 list the specifications for available SFPs and XFPs for the Cisco ONS 15600.
PAGE 287

Appendix A Hardware Specifications A.3 SFP/XFP Specifications Table A-13 lists the available DWDM SFPs. Table A-13 ASAP Card 4PIO DWDM SFP Specifications SFP Product ID Interface Wavelength1 ONS-SC-2G-30.3 OC-48/STM16 1530.3 nm ONS-SC-2G-31.1 OC-48/STM16 1531.1 nm ONS-SC-2G-31.9 OC-48/STM16 1531.9 nm ONS-SC-2G-32.6 OC-48/STM16 1532.6 nm ONS-SC-2G-34.2 OC-48/STM16 1534.2 nm ONS-SC-2G-35.0 OC-48/STM16 1535.0 nm ONS-SC-2G-35.8 OC-48/STM16 1535.8 nm ONS-SC-2G-36.6 OC-48/STM16 1536.
PAGE 288

Appendix A Hardware Specifications A.3 SFP/XFP Specifications Table A-14 describes the power and noise limited performances parameters for the OC-SC-2G series SFPs. Table A-14 Parameter Input power range Power and Noise Limited Performances Power Limited Performances –9 to –28 dBm At BER = 10 PRBS23 –12 Noise Limited Performances with SONET framed –9 to –22 dBm 622 Mbps – 2.0 Gbps at OSNR1 of 20 dB, 0.1 nm bandwidth At BER = 10–12 with SONET framed PRBS23 At OSNR of 16 dB at 0.1 nm bandwidth. 2.
PAGE 289

B A P P E N D I X Administrative and Service States This appendix describes administrative and service states for Cisco ONS 15600 cards, ports, and cross-connects. For circuit state information, see Chapter 7, “Circuits and Tunnels.” Entity states are based on the generic state model defined in Telcordia GR-1093-CORE, Issue 2 and ITU-T X.731. The following sections are included: • B.1 Service States, page B-1 • B.2 Administrative States, page B-2 • B.3 Service State Transitions, page B-3 B.
PAGE 290

Appendix B Administrative and Service States B.2 Administrative States Table B-2 ONS 15600 Secondary States Secondary State Definition AINS (Automatic In-Service) The entity is delayed before transitioning to the IS-NR service state. The transition to IS-NR depends on correction of conditions, or on a soak timer. Alarm reporting is suppressed, but traffic is carried.
PAGE 291

Appendix B Administrative and Service States B.3 Service State Transitions B.3 Service State Transitions This section describes the transition from one service state to the next for cards, ports, and cross-connects. A service state transition is based on the action performed on the entity. Note When an entity is put in the OOS,MT administrative state, the ONS 15600 suppresses all standing alarms on that entity. All alarms and events appear on the Conditions tab.
PAGE 292

Appendix B Administrative and Service States B.3.1 Card Service State Transitions Table B-4 ONS 15600 Card Service State Transitions (continued) Current Service State Action Next Service State OOS-AU,MEA Pull the card. OOS-AU,UEQ Delete the card. OOS-AUMA,UAS if the card is valid OOS-AUMA,MEA & UAS if the card is invalid OOS-AU,SWDL OOS-AU,UEQ OOS-AUMA,FLT & MT OOS-AUMA,MEA & MT Change the administrative state to OOS,MT. OOS-AU,MEA & MT Restart completed. IS-NR Pull the card.
PAGE 293

Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions Table B-4 ONS 15600 Card Service State Transitions (continued) Current Service State Action Next Service State OOS-AUMA,UAS Pull the card. OOS-AUMA,UAS & UEQ Provision an invalid card. OOS-AU,MEA Provision a valid card. OOS-AU,SWDL Insert a valid card. OOS-AU,SWDL Insert an invalid card. OOS-AUMA,MEA & UAS Preprovision a card. OOS-AU,AINS & UEQ Change the administrative state to IS.
PAGE 294

Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions Table B-5 ONS 15600 Port and Cross-Connect Service State Transitions (continued) Current Service State Action Next Service State OOS-AU,AINS Put the port or cross-connect in the IS administrative state. IS-NR Put the port or cross-connect in the OOS,MT administrative state. OOS-MA,MT Put the port or cross-connect in the OOS,DSBLD. OOS-MA,DSBLD Alarm/condition is raised.
PAGE 295

Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions Table B-5 ONS 15600 Port and Cross-Connect Service State Transitions (continued) Current Service State Action Next Service State OOS-MA,DSBLD Put the port or cross-connect in the IS administrative state. IS-NR Put the port or cross-connect in OOS-AU,AINS the IS,AINS administrative state. OOS-MA,LPBK & MT OOS-MA,MT Put the port or cross-connect in the OOS,MT. OOS-MA,MT Release the loopback.
PAGE 296

Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions Cisco ONS 15600 Reference Manual, R7.
PAGE 297

C A P P E N D I X Network Element Defaults Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
PAGE 298

Appendix C Network Element Defaults C.2 Card Default Settings settings except those relating to protection (1+1 bidirectional switching, 1+1 reversion time, 1+1 revertive switching, bidirectional line switched ring [BLSR] ring reversion time, BLSR ring revertive switching, BLSR span reversion time, and BLSR span revertive switching), which apply to subsequent provisioning.
PAGE 299

Appendix C Network Element Defaults C.2.2 Threshold Defaults C.2.2 Threshold Defaults Threshold default settings define the default cumulative values (thresholds) beyond which a threshold crossing alert (TCA) will be raised, making it possible to monitor the network and detect errors early. Card threshold default settings are provided as follows: • PM thresholds—(OC-N and ASAP cards) Can be expressed in counts or seconds; includes line, electrical path, and SONET thresholds.
PAGE 300

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-1 OC192_4 Card Default Settings (continued) Default Name Default Value Default Domain OC192_4.config.sts.IPPMEnabled FALSE TRUE, FALSE OC192_4.physicalthresholds.warning.15min.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1, LBC-LOW + 2 .. 255 OC192_4.physicalthresholds.warning.15min.LBC-LOW 20 (%) 0, 1, 2 .. LBC-HIGH OC192_4.physicalthresholds.warning.15min.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1, OPR-LOW + 2 .. 255 OC192_4.
PAGE 301

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-1 OC192_4 Card Default Settings (continued) Default Name Default Value Default Domain OC192_4.pmthresholds.line.nearend.15min.PSD-S 300 (seconds) 0 - 900 OC192_4.pmthresholds.line.nearend.15min.PSD-W 300 (seconds) 0 - 900 OC192_4.pmthresholds.line.nearend.15min.SES 1 (seconds) 0 - 900 OC192_4.pmthresholds.line.nearend.15min.UAS 3 (seconds) 0 - 900 OC192_4.pmthresholds.line.nearend.1day.
PAGE 302

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-1 OC192_4 Card Default Settings (continued) Default Name Default Value Default Domain OC192_4.pmthresholds.sts1.nearend.15min.ES 12 (seconds) 0 - 900 OC192_4.pmthresholds.sts1.nearend.15min.FC 10 (count) 0 - 72 OC192_4.pmthresholds.sts1.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 OC192_4.pmthresholds.sts1.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 OC192_4.pmthresholds.sts1.nearend.15min.
PAGE 303

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-1 OC192_4 Card Default Settings (continued) Default Name Default Value Default Domain OC192_4.pmthresholds.sts12c+.nearend.1day.CV 750 (B3 count) 0 - 207360000 OC192_4.pmthresholds.sts12c+.nearend.1day.ES 600 (seconds) 0 - 86400 OC192_4.pmthresholds.sts12c+.nearend.1day.FC 40 (count) 0 - 6912 OC192_4.pmthresholds.sts12c+.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 OC192_4.pmthresholds.sts12c+.nearend.1day.
PAGE 304

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-1 OC192_4 Card Default Settings (continued) Default Name Default Value Default Domain OC192_4.pmthresholds.sts3c.nearend.1day.SES 7 (seconds) 0 - 86400 OC192_4.pmthresholds.sts3c.nearend.1day.UAS 10 (seconds) 0 - 86400 C.2.3.2 OC48_16 Card Default Settings Table C-2 lists the OC48-16 card default settings. Table C-2 OC48_16 Card Default Settings Default Name Default Value OC48_16.config.line.
PAGE 305

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-2 OC48_16 Card Default Settings (continued) Default Name Default Value Default Domain OC48_16.pmthresholds.line.farend.1day.CV 212600 (B2 count) 0 - 212371200 OC48_16.pmthresholds.line.farend.1day.ES 864 (seconds) 0 - 86400 OC48_16.pmthresholds.line.farend.1day.FC 40 (count) 0 - 6912 OC48_16.pmthresholds.line.farend.1day.SES 4 (seconds) 0 - 86400 OC48_16.pmthresholds.line.farend.1day.UAS 10 (seconds) 0 - 86400 OC48_16.
PAGE 306

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-2 OC48_16 Card Default Settings (continued) Default Name Default Value Default Domain OC48_16.pmthresholds.section.nearend.1day.ES 5000 (seconds) 0 - 86400 OC48_16.pmthresholds.section.nearend.1day.SEFS 5000 (seconds) 0 - 86400 OC48_16.pmthresholds.section.nearend.1day.SES 5000 (seconds) 0 - 86400 OC48_16.pmthresholds.sts1.farend.15min.CV 15 (B3 count) 0 - 2160000 OC48_16.pmthresholds.sts1.farend.15min.
PAGE 307

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-2 OC48_16 Card Default Settings (continued) Default Name Default Value Default Domain OC48_16.pmthresholds.sts12c+.farend.1day.CV 750 (B3 count) 0 - 207360000 OC48_16.pmthresholds.sts12c+.farend.1day.ES 600 (seconds) 0 - 86400 OC48_16.pmthresholds.sts12c+.farend.1day.FC 40 (count) 0 - 6912 OC48_16.pmthresholds.sts12c+.farend.1day.SES 7 (seconds) 0 - 86400 OC48_16.pmthresholds.sts12c+.farend.1day.
PAGE 308

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-2 OC48_16 Card Default Settings (continued) Default Name Default Value Default Domain OC48_16.pmthresholds.sts3c.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 OC48_16.pmthresholds.sts3c.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 OC48_16.pmthresholds.sts3c.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 OC48_16.pmthresholds.sts3c.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 OC48_16.pmthresholds.sts3c.nearend.15min.
PAGE 309

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.config.oc192.line.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS ASAP_4.config.oc192.line.SyncMsgIn TRUE FALSE, TRUE ASAP_4.config.oc192.sts.IPPMEnabled FALSE TRUE, FALSE ASAP_4.config.oc3.line.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 ASAP_4.config.oc3.line.SDBER 1.00E-07 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 ASAP_4.config.
PAGE 310

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.physicalthresholds.oc12.warning.1day.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1, LBC-LOW + 2 .. 255 ASAP_4.physicalthresholds.oc12.warning.1day.LBC-LOW 20 (%) 0, 1, 2 .. LBC-HIGH ASAP_4.physicalthresholds.oc12.warning.1day.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1, OPR-LOW + 2 .. 255 ASAP_4.physicalthresholds.oc12.warning.1day.
PAGE 311

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.physicalthresholds.oc3.alarm.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1, OPR-LOW + 2 .. 255 ASAP_4.physicalthresholds.oc3.alarm.OPR-LOW 50 (%) -1, 0, 1 .. OPR-HIGH ASAP_4.physicalthresholds.oc3.alarm.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1, OPT-LOW + 2 .. 255 ASAP_4.physicalthresholds.oc3.alarm.OPT-LOW 80 (%) 0, 1, 2 .. OPT-HIGH ASAP_4.
PAGE 312

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.physicalthresholds.oc48.warning.15min.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1, OPT-LOW + 2 .. 255 ASAP_4.physicalthresholds.oc48.warning.15min.OPT-LOW 80 (%) 0, 1, 2 .. OPT-HIGH ASAP_4.physicalthresholds.oc48.warning.1day.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1, LBC-LOW + 2 .. 255 ASAP_4.physicalthresholds.oc48.warning.1day.
PAGE 313

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.pmthresholds.oc12.line.nearend.1day.PSD-W 0 (seconds) 0 - 86400 ASAP_4.pmthresholds.oc12.line.nearend.1day.SES 4 (seconds) 0 - 86400 ASAP_4.pmthresholds.oc12.line.nearend.1day.UAS 10 (seconds) 0 - 86400 ASAP_4.pmthresholds.oc12.section.nearend.15min.CV 10000 (B1 count) 0 - 2151900 ASAP_4.pmthresholds.oc12.section.nearend.15min.
PAGE 314

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.pmthresholds.oc12.sts1.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 ASAP_4.pmthresholds.oc12.sts1.nearend.1day.SES 7 (seconds) 0 - 86400 ASAP_4.pmthresholds.oc12.sts1.nearend.1day.UAS 10 (seconds) 0 - 86400 ASAP_4.pmthresholds.oc12.sts12c+.farend.15min.CV 75 (B3 count) 0 - 2160000 ASAP_4.pmthresholds.oc12.sts12c+.farend.15min.
PAGE 315

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.pmthresholds.oc12.sts3c-9c.farend.1day.CV 250 (B3 count) 0 - 207360000 ASAP_4.pmthresholds.oc12.sts3c-9c.farend.1day.ES 200 (seconds) 0 - 86400 ASAP_4.pmthresholds.oc12.sts3c-9c.farend.1day.FC 40 (count) 0 - 6912 ASAP_4.pmthresholds.oc12.sts3c-9c.farend.1day.SES 7 (seconds) 0 - 86400 ASAP_4.pmthresholds.oc12.sts3c-9c.farend.1day.
PAGE 316

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.pmthresholds.oc192.line.nearend.15min.PSC 1 (count) 0 - 600 ASAP_4.pmthresholds.oc192.line.nearend.15min.PSC-R 1 (count) 0 - 600 ASAP_4.pmthresholds.oc192.line.nearend.15min.PSC-S 1 (count) 0 - 600 ASAP_4.pmthresholds.oc192.line.nearend.15min.PSC-W 1 (count) 0 - 600 ASAP_4.pmthresholds.oc192.line.nearend.15min.
PAGE 317

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.pmthresholds.oc192.sts1.farend.1day.CV 125 (B3 count) 0 - 207360000 ASAP_4.pmthresholds.oc192.sts1.farend.1day.ES 100 (seconds) 0 - 86400 ASAP_4.pmthresholds.oc192.sts1.farend.1day.FC 40 (count) 0 - 6912 ASAP_4.pmthresholds.oc192.sts1.farend.1day.SES 7 (seconds) 0 - 86400 ASAP_4.pmthresholds.oc192.sts1.farend.1day.
PAGE 318

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.pmthresholds.oc192.sts12c+.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 ASAP_4.pmthresholds.oc192.sts12c+.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 ASAP_4.pmthresholds.oc192.sts12c+.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 ASAP_4.pmthresholds.oc192.sts12c+.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 ASAP_4.pmthresholds.
PAGE 319

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.pmthresholds.oc192.sts3c-9c.nearend.1day.FC 40 (count) 0 - 6912 ASAP_4.pmthresholds.oc192.sts3c-9c.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 ASAP_4.pmthresholds.oc192.sts3c-9c.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 ASAP_4.pmthresholds.oc192.sts3c-9c.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 ASAP_4.
PAGE 320

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.pmthresholds.oc3.section.nearend.15min.ES 500 (seconds) 0 - 900 ASAP_4.pmthresholds.oc3.section.nearend.15min.SEFS 500 (seconds) 0 - 900 ASAP_4.pmthresholds.oc3.section.nearend.15min.SES 500 (seconds) 0 - 900 ASAP_4.pmthresholds.oc3.section.nearend.1day.CV 100000 (B1 count) 0 - 206582400 ASAP_4.pmthresholds.oc3.section.nearend.1day.
PAGE 321

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.pmthresholds.oc3.sts3c.farend.15min.ES 20 (seconds) 0 - 900 ASAP_4.pmthresholds.oc3.sts3c.farend.15min.FC 10 (count) 0 - 72 ASAP_4.pmthresholds.oc3.sts3c.farend.15min.SES 3 (seconds) 0 - 900 ASAP_4.pmthresholds.oc3.sts3c.farend.15min.UAS 10 (seconds) 0 - 900 ASAP_4.pmthresholds.oc3.sts3c.farend.1day.
PAGE 322

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.pmthresholds.oc48.line.farend.1day.UAS 10 (seconds) 0 - 86400 ASAP_4.pmthresholds.oc48.line.nearend.15min.CV 21260 (B2 count) 0 - 2212200 ASAP_4.pmthresholds.oc48.line.nearend.15min.ES 87 (seconds) 0 - 900 ASAP_4.pmthresholds.oc48.line.nearend.15min.FC 10 (count) 0 - 72 ASAP_4.pmthresholds.oc48.line.nearend.15min.
PAGE 323

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.pmthresholds.oc48.sts1.farend.15min.ES 12 (seconds) 0 - 900 ASAP_4.pmthresholds.oc48.sts1.farend.15min.FC 10 (count) 0 - 72 ASAP_4.pmthresholds.oc48.sts1.farend.15min.SES 3 (seconds) 0 - 900 ASAP_4.pmthresholds.oc48.sts1.farend.15min.UAS 10 (seconds) 0 - 900 ASAP_4.pmthresholds.oc48.sts1.farend.1day.
PAGE 324

Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.pmthresholds.oc48.sts12c+.farend.1day.UAS 10 (seconds) 0 - 86400 ASAP_4.pmthresholds.oc48.sts12c+.nearend.15min.CV 75 (B3 count) 0 - 2160000 ASAP_4.pmthresholds.oc48.sts12c+.nearend.15min.ES 60 (seconds) 0 - 900 ASAP_4.pmthresholds.oc48.sts12c+.nearend.15min.FC 10 (count) 0 - 72 ASAP_4.pmthresholds.oc48.sts12c+.nearend.15min.
PAGE 325

Appendix C Network Element Defaults C.3 Node Default Settings Table C-3 ASAP Card Default Settings (continued) Default Name Default Value Default Domain ASAP_4.pmthresholds.oc48.sts3c-9c.nearend.15min.SES 3 (seconds) 0 - 900 ASAP_4.pmthresholds.oc48.sts3c-9c.nearend.15min.UAS 10 (seconds) 0 - 900 ASAP_4.pmthresholds.oc48.sts3c-9c.nearend.1day.CV 250 (B3 count) 0 - 207360000 ASAP_4.pmthresholds.oc48.sts3c-9c.nearend.1day.ES 200 (seconds) 0 - 86400 ASAP_4.pmthresholds.oc48.sts3c-9c.nearend.
PAGE 326

Appendix C Network Element Defaults C.3 Node Default Settings Table C-4 • Security Policy settings—Set the allowable failed logins before lockout, idle user timeout for each user-level, optional lockout duration or manual unlock enabled, password reuse and change frequency policies, number of characters difference between the old and new password, password aging by security level, enforced single concurrent session per user, and option to disable inactive user after a set inactivity period.
PAGE 327

Appendix C Network Element Defaults C.3 Node Default Settings Table C-4 Node Default Settings (continued) Default Name Default Value Default Domain NODE.general.NtpSntpServer 0.0.0.0 IP Address NODE.general.ReportLoopbackConditionsOnOOS-MTPorts FALSE FALSE, TRUE NODE.general.TimeZone (GMT-06:00 ) Central Time (US & Canada) (For applicable time zones, see Table C-5.) NODE.general.UseDST TRUE TRUE, FALSE NODE.network.general.AlarmMissingBackplaneLAN FALSE TRUE, FALSE NODE.network.general.
PAGE 328

Appendix C Network Element Defaults C.3 Node Default Settings Table C-4 Node Default Settings (continued) Default Name Default Value Default Domain NODE.osi.subnet.ISH 10 (sec) 10, 20, 30 .. 1000 NODE.osi.subnet.LANISISCost 20 1, 2, 3 .. 63 NODE.osi.subnet.LDCCISISCost 40 1, 2, 3 .. 63 NODE.osi.subnet.SDCCISISCost 60 1, 2, 3 .. 63 NODE.osi.tarp.L1DataCache TRUE FALSE, TRUE NODE.osi.tarp.L2DataCache FALSE FALSE, TRUE NODE.osi.tarp.LANStormSuppression TRUE FALSE, TRUE NODE.osi.tarp.
PAGE 329

Appendix C Network Element Defaults C.3 Node Default Settings Table C-4 Node Default Settings (continued) Default Name Default Value Default Domain NODE.protection.blsr.SpanRevertive TRUE TRUE, FALSE NODE.security.emsAccess.AccessState NonSecure NonSecure, Secure NODE.security.emsAccess.IIOPListenerPort (May reboot node) 57790 (port #) 0 - 65535 NODE.security.grantPermission.ActivateRevertSoftware Superuser Provisioning, Superuser NODE.security.grantPermission.
PAGE 330

Appendix C Network Element Defaults C.3 Node Default Settings Table C-4 Node Default Settings (continued) Default Name Default Value Default Domain NODE.security.legalDisclaimer.LoginWarningMessage WAR field NINGThis system is restricted to authorized users for business purposes. Unauthorize d
access is a violation of the law. This service may be monitored for administrativ e
and security reasons. By proceeding, you consent to this monitoring. NODE.
PAGE 331

Appendix C Network Element Defaults C.3 Node Default Settings Table C-4 Node Default Settings (continued) Default Name Default Value Default Domain NODE.security.passwordAging.superuser.AgingPeriod 45 (days) 20 - 90 NODE.security.passwordAging.superuser.WarningPeriod 5 (days) 20-Feb NODE.security.passwordChange.CannotChangeNewPassword FALSE TRUE, FALSE NODE.security.passwordChange.CannotChangeNewPasswordForNDays 20 (days) 20 - 95 NODE.security.passwordChange.
PAGE 332

Appendix C Network Element Defaults C.3 Node Default Settings Table C-4 Node Default Settings (continued) Default Name Default Value Default Domain NODE.timing.bits-2.Coding B8ZS B8ZS, AMI NODE.timing.bits-2.Framing ESF ESF, D4 NODE.timing.bits-2.State IS IS, OOS,DSBLD, OOS,MT, IS,AINS NODE.timing.general.Mode External External, Line NODE.timing.general.
PAGE 333

Appendix C Network Element Defaults C.3.1 Time Zones Table C-4 Node Default Settings (continued) Default Name Default Value Default Domain NODE.timing.general.Revertive FALSE TRUE, FALSE NODE.timing.general.SSMMessageSet Generation 2 Generation 1, Generation 2 C.3.1 Time Zones Table C-5 lists the time zones that apply for node time zone defaults.
PAGE 334

Appendix C Network Element Defaults C.3.
PAGE 335

Appendix C Network Element Defaults C.
PAGE 336

Appendix C Network Element Defaults C.4 CTC Default Settings • Network Circuit Automatic Routing Overridable—Set by default whether or not a user creating circuits can change (override) the Automatic Circuit Routing setting (also provisionable as a default). When this default is set to TRUE it enables users to change whether or not Route Automatically is selected in the check box.
PAGE 337

I N D EX alarm profiles Numerics description 1+1 optical port protection description compare 3-2 create linear ADM configuration 8-2 point-to-point configuration 8-2 revertive and nonrevertive 3-3 1PIO module A-11 2-22 11-9 list by node load 11-10 save 11-10 11-10 port numbers alarm suppression with OOS,MT Alarm window port-level LEDs 2-23 audible 2-25 11-4 11-4 change default severities. See alarm profiles ASAP card specifications A-11 2-22 port numbers create profiles.
PAGE 338

Index description timing 2-19 Ethernet performance monitoring 12-12 1-11 bandwidth Ether Ports History window 12-16 allocation and routing Ether Port Statistics window 12-12 four-fiber BLSR capacity Ether Ports Utilization window faceplate 2-21 overview 2-2 specifications 12-15 A-1 installation 12-11 label 2-23 port numbering 1-2 1-5 bidirectional line switched ring.
PAGE 339

Index card colors Release 5.02 and 7.0 caveat 4-7 card protection STS squelch table 7-16 See also 1+1 optical port protection STS time slot assignments unprotected VT squelch table 3-3 cards 7-4 7-17 Cisco Transport Controller. See CTC optical. See OC-N cards CMS. See CTC common control.
PAGE 340

Index computer requirements exporting data install 4-14 4-2 legal disclaimer login link icon 4-11 tunneling 7-12 4-10 view non-DCC nodes 4-6 DCN 4-14 reverting to earlier load based on TCP/IP protocol suite 4-16 9-26 in IP-over-CLNS tunnel scenarios 4-1 specifications A-2 routers default user ID network.
PAGE 341

Index electrical codes BLSR bandwidth reuse 8-9 end network element.
PAGE 342

Index firewalls external 9-22 not enabled SNTP 9-11 grounding 1-13 9-12 tunnels, setting up in CTC 9-24 tunnels for foreign termination with port filtering H 9-25 9-16 hard reset FLT secondary service state B-2 4-15 hardware specification A-1 four-fiber BLSR. See BLSR high-capacity RMON 13-12 front door hop equipment access label 9-7 1-4 1-4 I idle time G 5-5 idle user timeout gateway default 5-5 IEEE 802.
PAGE 343

Index OSPF LBC parameter 9-8 overview legal disclaimer, CTC 9-2 Proxy ARP and gateway linear ADM 9-4 static routes connecting to LANs IP-encapsulated tunnel line rates 9-6 8-2 1-18 line timing between an ONS node and another vendor GNE between an ONS node and a router 9-41 between an ONS node and a router across an OSI DCN 9-43 9-38 9-40 6-1 link aggregation link diversity 10-8 7-21 lockout settings 5-6 logged in users 5-6 9-39 invalid attempts 12-2 node groups IS,AINS admini
PAGE 344

Index ASAP card settings C-12 card default tables CTC defaults description O C-2 OC-192 long-reach card C-39 block diagram C-1 node defaults 2-15 card-level LEDs C-29 OC-192 card settings connectors C-3 OC-48 card settings 2-16 2-14 default settings C-8 description networks C-3 2-14 building circuits 7-1 faceplate building tunnels 7-1 network-level LEDs 2-15 default configuration.
PAGE 345

Index software compatibility specifications open GNE 2-2 Open Shortest Path First. See OSPF A-6 OC-48 short-reach card block diagram connectors optical protection.
PAGE 346

Index ASAP card parameters IPPM PPMN 12-11 PPMs.
PAGE 347

Index PSC (BLSR) parameter PSC parameter restrictions on two-circuit rolls 12-7 12-7 single 7-24 7-23 PSC-R parameter 12-7 states PSC-S parameter 12-7 unprotected circuits PSC-W parameter PSD (1+1) parameter PSD parameter 12-8 PSD-S parameter 12-8 9-20 RS-232 port.
PAGE 348

Index SES-LFE parameter SES-L parameter timing parameters 12-8 topologies 12-8 SES-PFE parameter 6-1 8-1 Spanning Tree Protocol, Gigabit EtherChannel 12-9 SES-P parameter 12-8 SPE See synchronous payload envelope SES-S parameter 12-9 squelch tables set-request, definition 13-4 SFPs/XFPs bail clasp (illustration) compatibility SSM 6-3 SST B-1 7-16 SSXC card 2-27 bandwidth 2-26, 2-27 7-12 description 2-25, 2-27 block diagram dimensions 2-26 connectors specifications shared
PAGE 349

Index destination host or network timing 9-20 superusers BITS. See BITS assign login privileges change security policies description BITS pins 5-6 external or line 5-5 installation 5-1 grant privileges to provisioning users idle time SWDL secondary service state B-2 synchronization status messaging.
PAGE 350

Index push-button switches slots virtual 2-6 2-3 links 9-19 soft reset 4-15 rings 8-12 software 4-1 wires 11-14 software compatibility specifications VLAN 2-2 10-6 VT squelch table A-5 7-17 tunnels DCC 7-12 firewall, setting up in CTC IP encapsulated 7-13 IP-over-CLNS overview W 9-24 WAN 9-38 9-2 warnings 7-1 international two-fiber BLSR.