-
Cisco ONS 15454 Reference Manual Product and Documentation Release 8.5.x July 2010 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
-
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.
-
C O N T E N T S About this Manual xli Revision History xli Document Objectives Audience xliv xlv Related Documentation xlv Document Conventions xlv Obtaining Optical Networking Information li Where to Find Safety and Warning Information li Cisco Optical Networking Product Documentation CD-ROM Obtaining Documentation and Submitting a Service Request CHAPTER 1 Shelf and Backplane Hardware 1.1 Overview li lii 1-1 1-2 1.2 Rack Installation 1-3 1.2.1 Reversible Mounting Bracket 1-4 1.2.
-
Contents 1.5.6 SMB EIA 1-28 1.5.7 AMP Champ EIA 1-29 1.5.8 UBIC-V EIA 1-32 1.5.9 UBIC-H EIA 1-34 1.5.10 EIA Replacement 1-38 1.6 Coaxial Cable 1-38 1.7 DS-1 Cable 1-38 1.7.1 Twisted Pair Wire-Wrap Cables 1-38 1.7.2 Electrical Interface Adapters 1-39 1.8 UBIC-V Cables 1-40 1.9 UBIC-H Cables 1-45 1.10 Ethernet Cables 1-51 1.11 Cable Routing and Management 1-53 1.11.1 Fiber Management 1-54 1.11.2 Fiber Management Using the Tie-Down Bar 1-55 1.11.3 Coaxial Cable Management 1-56 1.11.
-
Contents CHAPTER 2 Common Control Cards 2-1 2.1 Common Control Card Overview 2-1 2.1.1 Cards Summary 2-1 2.1.2 Card Compatibility 2-3 2.1.3 Cross-Connect Card Compatibility 2-3 2.2 TCC2 Card 2-6 2.2.1 TCC2 Card Functionality 2-7 2.2.2 TCC2 Card-Level Indicators 2-8 2.2.3 Network-Level Indicators 2-9 2.2.4 Power-Level Indicators 2-10 2.3 TCC2P Card 2-10 2.3.1 TCC2P Functionality 2-11 2.3.1.1 System Timing Functions 2-12 2.3.2 TCC2P Card-Level Indicators 2-14 2.3.3 Network-Level Indicators 2-14 2.3.
-
Contents 2.7.6 Data Communications Channel CHAPTER 3 Electrical Cards 2-33 3-1 3.1 Electrical Card Overview 3-1 3.1.1 Card Summary 3-1 3.1.2 Card Compatibility 3-3 3.2 Bit Error Rate Testing 3-4 3.3 EC1-12 Card 3-5 3.3.1 EC1-12 Slots and Connectors 3-5 3.3.2 EC1-12 Faceplate and Block Diagram 3-5 3.3.3 EC1-12 Hosted by XCVT, XC10G, or XC-VXC-10G 3.3.4 EC1-12 Card-Level Indicators 3-6 3.3.5 EC1-12 Port-Level Indicators 3-7 3-6 3.4 DS1-14 and DS1N-14 Cards 3-7 3.4.
-
Contents 3.9 DS3-12E and DS3N-12E Cards 3-21 3.9.1 DS3-12E and DS3N-12E Slots and Connectors 3-22 3.9.2 DS3-12E Faceplate and Block Diagram 3-22 3.9.3 DS3-12E and DS3N-12E Card-Level Indicators 3-24 3.9.4 DS3-12E and DS3N-12E Port-Level Indicators 3-25 3.10 DS3XM-6 Card 3-25 3.10.1 DS3XM-6 Slots and Connectors 3-25 3.10.2 DS3XM-6 Faceplate and Block Diagram 3-25 3.10.3 DS3XM-6 Hosted By XCVT, XC10G, or XC-VXC-10G 3.10.4 DS3XM-6 Card-Level Indicators 3-26 3.10.5 DS3XM-6 Port-Level Indicators 3-27 3.
-
Contents 4.6 OC12 LR/STM4 LH 1550 Card 4-13 4.6.1 OC12 LR/STM4 LH 1550 Card-Level Indicators 4-14 4.6.2 OC12 LR/STM4 LH 1550 Port-Level Indicators 4-15 4.7 OC12 IR/STM4 SH 1310-4 Card 4-15 4.7.1 OC12 IR/STM4 SH 1310-4 Card-Level Indicators 4-17 4.7.2 OC12 IR/STM4 SH 1310-4 Port-Level Indicators 4-17 4.8 OC48 IR 1310 Card 4-17 4.8.1 OC48 IR 1310 Card-Level Indicators 4-18 4.8.2 OC48 IR 1310 Port-Level Indicators 4-19 4.9 OC48 LR 1550 Card 4-19 4.9.1 OC48 LR 1550 Card-Level Indicators 4-20 4.9.
-
Contents 4.18.2 Ports and Line Rates 4-43 4.18.3 15454_MRC-12 Card-Level Indicators 4-45 4.18.4 15454_MRC-12 Port-Level Indicators 4-46 4.19 MRC-2.5G-4 Multirate Card 4-46 4.19.1 Slot Compatibility by Cross-Connect Card 4.19.2 Ports and Line Rates 4-48 4.19.3 MRC-2.5G-4 Card-Level Indicators 4-49 4.19.4 MRC-2.5G-4 Port-Level Indicators 4-49 4-48 4.20 OC192SR1/STM64IO Short Reach and OC192/STM64 Any Reach Cards 4-50 4.20.1 OC192SR1/STM64IO Short Reach and OC192/STM64 Any Reach Card-Level Indicators 4.20.
-
Contents 5.5.2 E1000-2-G Port-Level Indicators 5-13 5.5.3 Cross-Connect Compatibility 5-13 5.6 G1000-4 Card 5-14 5.6.1 STS-24c Restriction 5-15 5.6.2 G1000-4 Card-Level Indicators 5-15 5.6.3 G1000-4 Port-Level Indicators 5-15 5.6.4 Slot Compatibility 5-16 5.7 G1K-4 Card 5-16 5.7.1 STS-24c Restriction 5-17 5.7.2 G1K-4 Compatibility 5-18 5.7.3 G1K-4 Card-Level Indicators 5-18 5.7.4 G1K-4 Port-Level Indicators 5-18 5.8 ML100T-12 Card 5-19 5.8.1 ML100T-12 Card-Level Indicators 5-20 5.8.
-
Contents 5.14.3 Cross-Connect and Slot Compatibility 5.15 Ethernet Card GBICs and SFPs 5-36 5.15.1 Compatibility by Card 5-37 5.15.2 GBIC Description 5-38 5.15.3 G1K-4 DWDM and CWDM GBICs 5.15.4 SFP Description 5-41 CHAPTER 6 Storage Access Networking Cards 5-36 5-39 6-1 6.1 FC_MR-4 Card Overview 6-1 6.1.1 FC_MR-4 Card-Level Indicators 6-3 6.1.2 FC_MR-4 Port-Level Indicators 6-4 6.1.3 FC_MR-4 Compatibility 6-4 6.2 FC_MR-4 Card Modes 6-4 6.2.1 Line-Rate Card Mode 6-4 6.2.2 Enhanced Card Mode 6-5 6.2.
-
Contents 7.3.1 1+1 Protection 7-13 7.3.2 Optimized 1+1 Protection 7.4 Unprotected Cards 7-13 7-14 7.5 External Switching Commands CHAPTER 8 7-14 Cisco Transport Controller Operation 8-1 8.1 CTC Software Delivery Methods 8-1 8.1.1 CTC Software Installed on the TCC2/TCC2P Card 8-1 8.1.2 CTC Software Installed on the PC or UNIX Workstation 8.2 CTC Installation Overview 8-4 8.3 PC and UNIX Workstation Requirements 8.4 ONS 15454 Connection 8-3 8-4 8-7 8.5 CTC Login 8-7 8.5.
-
Contents 9.2.2.2 Idle User Timeout 9-7 9.2.2.3 User Password, Login, and Access Policies 9.2.2.4 Secure Access 9-8 9-7 9.3 Audit Trail 9-8 9.3.1 Audit Trail Log Entries 9-8 9.3.2 Audit Trail Capacities 9-9 9.4 RADIUS Security 9-9 9.4.1 RADIUS Authentication 9.4.2 Shared Secrets 9-10 CHAPTER 10 Timing 9-9 10-1 10.1 Timing Parameters 10.2 Network Timing 10-1 10-2 10.3 Synchronization Status Messaging 10-3 10.3.1 SONET SSM Messages 10-4 10.3.
-
Contents 11.11 BLSR STS and VT Squelch Tables 11-22 11.11.1 BLSR STS Squelch Table 11-22 11.11.2 BLSR VT Squelch Table 11-23 11.12 IEEE 802.17 Resilient Packet Ring Circuit Display 11.13 Section and Path Trace 11-23 11-24 11.14 Path Signal Label, C2 Byte 11-25 11.15 Automatic Circuit Routing 11-27 11.15.1 Bandwidth Allocation and Routing 11-28 11.15.2 Secondary Sources and Destinations 11-28 11.16 Manual Circuit Routing 11-29 11.17 Constraint-Based Circuit Routing 11-33 11.
-
Contents 12.2.4 BLSR Application Example 12-10 12.2.5 BLSR Fiber Connections 12-13 12.3 Path Protection 12-14 12.4 Dual-Ring Interconnect 12-19 12.4.1 BLSR DRI 12-19 12.4.2 Path Protection DRI 12-23 12.4.3 Path Protection/BLSR DRI Handoff Configurations 12.5 Comparison of the Protection Schemes 12.6 Subtending Rings 12-26 12-28 12-29 12.7 Linear ADM Configurations 12-31 12.8 Path-Protected Mesh Networks 12-31 12.9 Four-Shelf Node Configurations 12-33 12.10 STS around the Ring 12-34 12.
-
Contents 13.4 External Firewalls 13.5 Open GNE 13-25 13-27 13.6 TCP/IP and OSI Networking 13-29 13.6.1 Point-to-Point Protocol 13-30 13.6.2 Link Access Protocol on the D Channel 13-31 13.6.3 OSI Connectionless Network Service 13-31 13.6.4 OSI Routing 13-34 13.6.4.1 End System-to-Intermediate System Protocol 13-36 13.6.4.2 Intermediate System-to-Intermediate System Protocol 13-36 13.6.5 TARP 13-37 13.6.5.1 TARP Processing 13-38 13.6.5.2 TARP Loop Detection Buffer 13-39 13.6.5.
-
Contents 14.3 Alarm Information 14-2 14.3.1 Viewing Alarms With Each Node’s Time Zone 14-4 14.3.2 Controlling Alarm Display 14-4 14.3.3 Filtering Alarms 14-4 14.3.4 Viewing Alarm-Affected Circuits 14-5 14.3.5 Conditions Tab 14-5 14.3.6 Controlling the Conditions Display 14-6 14.3.6.1 Retrieving and Displaying Conditions 14-6 14.3.6.2 Conditions Column Descriptions 14-6 14.3.6.3 Filtering Conditions 14-7 14.3.7 Viewing History 14-7 14.3.7.1 History Column Descriptions 14-8 14.3.7.
-
Contents 15.5.3.1 DS-1 Facility Data Link Performance Monitoring 15-18 15.5.4 DS3-12 and DS3N-12 Card Performance Monitoring Parameters 15-18 15.5.5 DS3-12E and DS3N-12E Card Performance Monitoring Parameters 15-19 15.5.6 DS3i-N-12 Card Performance Monitoring Parameters 15-21 15.5.7 DS3XM-6 Card Performance Monitoring Parameters 15-23 15.5.8 DS3XM-12 Card Performance Monitoring Parameters 15-25 15.5.9 DS3/EC1-48 Card Performance Monitoring Parameters 15-27 15.
-
Contents 16.3 SNMP External Interface Requirement 16.4 SNMP Version Support 16-4 16.5 SNMP Message Types 16-4 16-4 16.6 SNMP Management Information Bases 16-5 16.6.1 IETF-Standard MIBs for the ONS 15454 16-5 16.6.2 Proprietary ONS 15454 MIBs 16-6 16.6.3 Generic Threshold and Performance Monitoring MIBs 16.7 SNMP Trap Content 16-9 16.7.1 Generic and IETF Traps 16.7.2 Variable Trap Bindings 16.8 SNMP Community Names 16.9 Proxy Over Firewalls 16-7 16-9 16-10 16-16 16-16 16.
-
Contents APPENDIX A Hardware Specifications A-1 A.1 Shelf Specifications A-1 A.1.1 Bandwidth A-1 A.1.2 Configurations A-2 A.1.3 Cisco Transport Controller A-2 A.1.4 External LAN Interface A-2 A.1.5 TL1 Craft Interface A-2 A.1.6 Modem Interface A-2 A.1.7 Alarm Interface A-3 A.1.8 EIA Interface A-3 A.1.9 BITS Interface A-3 A.1.10 System Timing A-3 A.1.11 System Power A-3 A.1.12 Fan Tray A-4 A.1.13 System Environmental Specifications A.1.14 Dimensions A-4 A.2 SFP, XFP, and GBIC Specifications A.
-
Contents A.6 Optical Card Specifications A-27 A.6.1 OC3 IR 4/STM1 SH 1310 Card Specifications A-28 A.6.2 OC3 IR/STM1SH 1310-8 Card Specifications A-29 A.6.3 OC12 IR/STM4 SH 1310 Card Specifications A-30 A.6.4 OC12 LR/STM4 LH 1310 Card Specifications A-31 A.6.5 OC12 LR/STM4 LH 1550 Card Specifications A-32 A.6.6 OC12 IR/STM4 SH 1310-4 Specifications A-33 A.6.7 OC48 IR 1310 Card Specifications A-34 A.6.8 OC48 LR 1550 Card Specifications A-35 A.6.9 OC48 IR/STM16 SH AS 1310 Card Specifications A-35 A.6.
-
Contents B.3 Service State Transitions B-3 B.3.1 Card Service State Transitions B-3 B.3.2 Port and Cross-Connect Service State Transitions B-5 B.3.3 Pluggable Equipment Service State Transitions B-10 APPENDIX C Network Element Defaults C-1 C.1 Network Element Defaults Description C-1 C.2 Card Default Settings C-2 C.2.1 Configuration Defaults C-2 C.2.2 Threshold Defaults C-3 C.2.3 Defaults by Card C-4 C.2.3.1 DS-1 Card Default Settings C-4 C.2.3.2 DS1/E1-56 Card Default Settings C-7 C.2.3.
-
F I G U R E S Figure 1-1 Cisco ONS 15454 ANSI Dimensions Figure 1-2 Mounting an ONS 15454 in a Rack Figure 1-3 The ONS 15454 Front Door Figure 1-4 Cisco ONS 15454 Deep Door Figure 1-5 ONS 15454 Front Door Ground Strap 1-9 Figure 1-6 Removing the ONS 15454 Front Door 1-10 Figure 1-7 Front-Door Erasable Label Figure 1-8 Laser Warning on the Front-Door Label Figure 1-9 Backplane Covers Figure 1-10 Removing the Lower Backplane Cover Figure 1-11 Backplane Attachment for Cover Figure 1-12
-
Figures Figure 1-31 Crossover Cable Figure 1-32 Managing Cables on the Front Panel Figure 1-33 Fiber Capacity 1-54 Figure 1-34 Tie-Down Bar 1-55 Figure 1-35 AEP Printed Circuit Board Assembly Figure 1-36 AEP Block Diagram Figure 1-37 AEP Wire-Wrap Connections to Backplane Pins Figure 1-38 Alarm Input Circuit Diagram Figure 1-39 Alarm Output Circuit Diagram Figure 1-40 Detectable Filler Card Faceplate Figure 1-41 Ground Posts on the ONS 15454 Backplane Figure 1-42 ONS 15454 Backplan
-
Figures Figure 3-12 DS3XM-12 Faceplate and Block Diagram Figure 4-1 OC3 IR 4/STM1 SH 1310 Faceplate and Block Diagram 4-6 Figure 4-2 OC3IR/STM1 SH 1310-8 Faceplate and Block Diagram 4-8 Figure 4-3 OC12 IR/STM4 SH 1310 Faceplate and Block Diagram 4-10 Figure 4-4 OC12 LR/STM4 LH 1310 Faceplate and Block Diagram 4-12 Figure 4-5 OC12 LR/STM4 LH 1550 Faceplate and Block Diagram 4-14 Figure 4-6 OC12 IR/STM4 SH 1310-4 Faceplate and Block Diagram Figure 4-7 OC48 IR 1310 Faceplate and Block Diag
-
Figures Figure 5-7 ML100T-12 Faceplate and Block Diagram Figure 5-8 ML100X-8 Faceplate and Block Diagram 5-22 Figure 5-9 ML1000-2 Faceplate and Block Diagram 5-24 Figure 5-10 ML-MR-10 Faceplate and Block Diagram 5-26 Figure 5-11 CE-100T-8 Faceplate and Block Diagram 5-29 Figure 5-12 CE-1000-4 Faceplate and Block Diagram 5-32 Figure 5-13 CE-MR-10 Faceplate and Block Diagram 5-35 Figure 5-14 GBICs with Clips (left) and with a Handle (right) Figure 5-15 CWDM GBIC with Wavelength Appropr
-
Figures Figure 11-4 Two VT1.5 Circuits in a BLSR Figure 11-5 Traditional DCC Tunnel Figure 11-6 VT1.
-
Figures Figure 12-16 Layout of Node ID 0 in the OC-3 Path Protection Example in Figure 12-15 Figure 12-17 Layout of Node IDs 1 to 3 in the OC-3 Path Protection Example in Figure 12-15 Figure 12-18 ONS 15454 Traditional BLSR Dual-Ring Interconnect (Same-Side Routing) Figure 12-19 ONS 15454 Traditional BLSR Dual-Ring Interconnect (Opposite-Side Routing) Figure 12-20 ONS 15454 Integrated BLSR Dual-Ring Interconnect Figure 12-21 Integrated BLSR DRI on the Edit Circuits Window Figure 12-22 ONS 1545
-
Figures Figure 13-16 IP Scenario 9: ONS 15454 GNE and ENEs on the Same Subnet with Secure Mode Enabled 13-22 Figure 13-17 IP Scenario 9: ONS 15454 GNE and ENEs on Different Subnets with Secure Mode Enabled 13-23 Figure 13-18 Proxy and Firewall Tunnels for Foreign Terminations Figure 13-19 Foreign Node Connection to an ENE Ethernet Port Figure 13-20 ISO-DCC NSAP Address Figure 13-21 OSI Main Setup Figure 13-22 Level 1 and Level 2 OSI Routing Figure 13-23 Manual TARP Adjacencies Figure 13-2
-
Figures Figure 15-8 Monitored Signal Types for the DS3-12 and DS3N-12 Cards Figure 15-9 PM Read Points on the DS3-12 and DS3N-12 Cards Figure 15-10 Monitored Signal Types for the DS3-12E and DS3N-12E Cards Figure 15-11 PM Read Points on the DS3-12E and DS3N-12E Cards Figure 15-12 Monitored Signal Types for the DS3i-N-12 Cards Figure 15-13 PM Read Points on the DS3i-N-12 Cards Figure 15-14 Monitored Signal Types for the DS3XM-6 Card Figure 15-15 PM Read Points on the DS3XM-6 Card Figure 15-1
-
T A B L E S Table 1-1 EIA Types Compatible with the 15454-SA-ANSI Only Table 1-2 EIA Configurations Compatible with the 15454-SA-ANSI and the 15454-SA-HD Table 1-3 MiniBNC Protection Types and Slots Table 1-4 J-Labeling Port Assignments for a Shelf Assembly Configure with Low-Density Electrical Cards (A Side) 1-24 Table 1-5 J-Labeling Port Assignments for a Shelf Assembly Configured with Low-Density Electrical Cards (B Side) 1-25 Table 1-6 J-Labeling Port Assignments for a Shelf Configured wit
-
Tables Table 1-31 Craft Interface Pin Assignments Table 1-32 Slot and Card Symbols Table 1-33 Card Ports, Line Rates, and Connectors Table 1-34 ONS 15454 Software and Hardware Compatibility—XC and XCVT Configurations Table 1-35 ONS 15454 Software and Hardware Compatibility—XC10G and XC-VXC-10G Configurations Table 2-1 Common Control Card Functions Table 2-2 Common-Control Card Software Release Compatibility Table 2-3 Common-Control Card Cross-Connect Compatibility Table 2-4 Electrical Card
-
Tables Table 3-9 DS3/EC1-48 Slot Restrictions Table 3-10 DS3/EC1-48 Card-Level Indicators Table 3-11 DS3i-N-12 Card-Level Indicators Table 3-12 DS3-12E and DS3N-12E Card-Level Indicators Table 3-13 DS3XM-6 Card-Level Indicators 3-27 Table 3-14 DS3XM-12 Shelf Configurations 3-28 Table 3-15 DS3XM-12 Features Table 3-16 DS3XM-12 Card-Level Indicators 3-32 Table 4-1 Optical Cards for the ONS 15454 4-2 Table 4-2 Optical Card Software Release Compatibility Table 4-3 OC3 IR 4/STM1 SH 1310
-
Tables Table 5-1 Ethernet Cards for the ONS 15454 Table 5-2 Ethernet Card Software Compatibility Table 5-3 E100T-12 Card-Level Indicators 5-6 Table 5-4 E100T-12 Port-Level Indicators 5-6 Table 5-5 E100T-G Card-Level Indicators 5-8 Table 5-6 E100T-G Port-Level Indicators 5-8 Table 5-7 E1000-2 Card-Level Indicators 5-10 Table 5-8 E1000-2 Port-Level Indicators 5-11 Table 5-9 E1000-2-G Card-Level Indicators 5-13 Table 5-10 E1000-2-G Port-Level Indicators 5-13 Table 5-11 G1000-4 Car
-
Tables Table 7-2 Supported 1:N Protection by Electrical Card Table 7-3 EIA Connectors Per Side Table 7-4 Electrical Card Protection By EIA Type Table 8-1 JRE Compatibility Table 8-2 Computer Requirements for CTC 8-5 Table 8-3 ONS 15454 Connection Methods 8-7 Table 8-4 Node View Card Colors Table 8-5 Node View Card Statuses Table 8-6 Node View Card Port Colors and Service States Table 8-7 Node View Tabs and Subtabs Table 8-8 Network View Tabs and Subtabs Table 8-9 Node Status Shown
-
Tables Table 11-12 Bidirectional STS/VT/Regular Multicard EtherSwitch/Point-to-Point (Straight) Ethernet Circuits Table 11-13 Unidirectional STS/VT Circuit Table 11-14 Multicard Group Ethernet Shared Packet Ring Circuit Table 11-15 Bidirectional VT Tunnels Table 11-16 Switch Times Table 11-17 ONS 15454 Card VCAT Circuit Rates and Members Table 11-18 ONS 15454 VCAT Card Capabilities Table 11-19 Protection options for Open-Ended VCAT Circuits Table 11-20 Roll Statuses Table 12-1 ONS 15454
-
Tables Table 14-5 Conditions Column Description Table 14-6 History Column Description Table 14-7 Alarm Profile Buttons Table 14-8 Alarm Profile Editing Options Table 15-1 Electrical Cards that Report RX and TX Direction for TCAs Table 15-2 ONS 15454 Line Terminating Equipment Table 15-3 Performance Monitoring Parameters Table 15-4 EC1-12 Card PMs Table 15-5 DS1/E1-56 Card PMs Table 15-6 DS1-14 and DS1N-14 Card PMs 15-17 Table 15-7 DS3-12 and DS3N-12 Card PMs 15-19 Table 15-8 DS3-12
-
Tables Table 16-2 IETF Standard MIBs Implemented in the ONS 15454 System Table 16-3 ONS 15454 Proprietary MIBs Table 16-4 cerentGenericPmThresholdTable Table 16-5 32-Bit cerentGenericPmStatsCurrentTable 16-8 Table 16-6 32-Bit cerentGenericPmStatsIntervalTable 16-8 Table 16-7 Supported Generic IETF Traps Table 16-8 Supported ONS 15454 SNMPv2 Trap Variable Bindings Table 16-9 RMON History Control Periods and History Categories Table 16-10 OIDs Supported in the AlarmTable Table A-1 Fan Tr
-
Tables Table C-17 OC-192 Card Default Settings Table C-18 OC192-XFP Default Settings Table C-19 MRC-12 Card Default Settings Table C-20 MRC-2.5G-4 Card Default Settings Table C-21 Node Default Settings Table C-22 Time Zones Table C-23 CTC Default Settings C-54 C-59 C-65 C-82 C-101 C-118 C-121 Cisco ONS 15454 Reference Manual, R8.5.
-
Tables Cisco ONS 15454 Reference Manual, R8.5.
-
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.
-
About this Manual Date Notes November 2007 Updated 1+1 Protection section in Card Protection chapter. Updated Shelf Configurations section in Electrical Cards chapter. January 2008 Updated cabling details for ONS-SE-ZE-EL SFP. February 2008 March 2008 April 2008 May 2008 • Removed the line stating support for XCVT card in the Cross Connect and Slot Compatability subsection under the ML100X-8 Card section in the Ethernet Cards chapter.
-
About this Manual Date July 2008 August 2008 September 2008 November 2008 December 2008 January 2009 February 2009 March 2009 April 2009 May 2009 Notes • Updated the 15454_MRC-12 Port-Level Indicators section, in the Optical Cards chapter to show the correct number and status of the Rx indicator. • Updated the MRC-2.5G-4 Port-Level Indicators section, in the Optical Cards chapter to show the correct number and status of the Rx indicator.
-
About this Manual Date Notes • Updated the Figure AEP Wire-Wrap Connections to Backplane Pins in Chapter 1, Shelf and Backplane Hardware. • Updated the 1.17.1 Card Slot Requirements section in Chapter 1, Shelf and Backplane Hardware. • Updated “OC-N Speed Upgrades” in Chapter 12, SONET Topologies and Upgrades. • Updated Table 1-2 in Chapter 1, Shelf and Backplane Hardware. • Updated the “Common-Control Card Software Release Compatibility” table in the chapter 2, Common Control Cards.
-
About this Manual Audience To use this publication, you should be familiar with Cisco or equivalent optical transmission hardware and cabling, telecommunications hardware and cabling, electronic circuitry and wiring practices, and preferably have experience as a telecommunications technician.
-
About this Manual Convention Application Ctrl The control key. For example, where Ctrl + D is written, hold down the Control key while pressing the D key. screen font Examples of information displayed on the screen. boldface screen font Examples of information that the user must enter. < Command parameters that must be replaced by module-specific codes. > Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the document.
-
About this Manual Attention IMPORTANTES INFORMATIONS DE SÉCURITÉ Ce symbole d'avertissement indique un danger. Vous vous trouvez dans une situation pouvant entraîner des blessures ou des dommages corporels. Avant de travailler sur un équipement, soyez conscient des dangers liés aux circuits électriques et familiarisez-vous avec les procédures couramment utilisées pour éviter les accidents.
-
About this Manual ¡Advertencia! INSTRUCCIONES IMPORTANTES DE SEGURIDAD Este símbolo de aviso indica peligro. Existe riesgo para su integridad física. Antes de manipular cualquier equipo, considere los riesgos de la corriente eléctrica y familiarícese con los procedimientos estándar de prevención de accidentes. Al final de cada advertencia encontrará el número que le ayudará a encontrar el texto traducido en el apartado de traducciones que acompaña a este dispositivo.
-
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.
-
About this Manual Cisco ONS 15454 Reference Manual, R8.5.
-
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.
-
About this Manual Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.
-
CH A P T E R 1 Shelf and Backplane Hardware 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.
-
Chapter 1 Shelf and Backplane Hardware 1.1 Overview Caution Unused card slots should be filled with a detectable filler card (Cisco P/N 15454-FILLER) or a non-detectable filler card (Cisco P/N 15454-BLANK). The filler card ensures proper airflow when operating the ONS 15454 without the front door attached, although Cisco recommends that the front door remain attached. Note The ONS 15454 is designed to comply with Telcordia GR-1089-CORE Type 2 and Type 4.
-
Chapter 1 Shelf and Backplane Hardware 1.2 Rack Installation • United States: National Fire Protection Association (NFPA) 70; United States National Electrical Code • Canada: Canadian Electrical Code, Part I, CSA C22.1 • Other countries: If local and national electrical codes are not available refer to IEC 364, Part 1 through Part 7 1.2 Rack Installation The ONS 15454 is mounted in a 19- or 23-in. (482.6- or 584.2-mm) equipment rack.
-
Chapter 1 Shelf and Backplane Hardware 1.2.1 Reversible Mounting Bracket Figure 1-1 Cisco ONS 15454 ANSI Dimensions Standard Door - Front View 18.25 in. (46.35 cm) Height Side View 16.78 in. (42.62 cm) 19 in. (48.26 cm) or 23 in. (58.42 cm) between mounting screw holes Width 5.015 in. (12.73 cm) 12.018 in. (30.52 cm) Depth Deep Door - Front View 18.25 in. (46.35 cm) Height Side View 16.78 in. (42.62 cm) 4.807 in. (12.20 cm) 13.810 in. (35.07 cm) Depth 240922 19 in. (48.26 cm) or 23 in. (58.
-
Chapter 1 Shelf and Backplane Hardware 1.2.2 Mounting a Single Node Caution When mounting the ONS 15454 in a frame with a nonconductive coating (such as paint, lacquer, or enamel) either use the thread-forming screws provided with the ONS 15454 shipping kit, or remove the coating from the threads to ensure electrical continuity. The shelf assembly comes preset for installation in a 23-inch (584.2 mm) rack, but you can reverse the mounting bracket to fit the smaller 19-inch (482.6 mm) rack. 1.2.
-
Chapter 1 Shelf and Backplane Hardware 1.2.3 Mounting Multiple Nodes 1.2.3 Mounting Multiple Nodes Most standard (Telcordia GR-63-CORE, 19-inch [482.6 mm] or 23-inch [584.2 mm]) seven-foot (2,133 mm) racks can hold four ONS 15454 shelves and a fuse and alarm panel. However, unequal flange racks are limited to three ONS 15454 shelves and a fuse and alarm panel or four ONS 15454 shelves and a fuse and alarm panel from an adjacent rack.
-
Chapter 1 Shelf and Backplane Hardware 1.3 Front Door Figure 1-3 The ONS 15454 Front Door CISCO ONS 15454 Optical Network System Door lock Door button 33923 Viewholes for Critical, Major and Minor alarm LEDs The ONS 15454 ships with a standard door but can also accommodate a deep door and extended fiber clips (15454-DOOR-KIT) to provide additional room for cabling (Figure 1-4). Cisco ONS 15454 Reference Manual, R8.5.
-
Chapter 1 Shelf and Backplane Hardware 1.3 Front Door Figure 1-4 Cisco ONS 15454 Deep Door 115011 . The ONS 15454 door locks with a pinned hex key that ships with the ONS 15454. A button on the right side of the shelf assembly releases the door. You can remove the front door of the ONS 15454 to provide unrestricted access to the front of the shelf assembly. Before you remove the front door, you have to remove the ground strap of the front door (Figure 1-5). Cisco ONS 15454 Reference Manual, R8.5.
-
Chapter 1 Shelf and Backplane Hardware 1.3 Front Door ONS 15454 Front Door Ground Strap 71048 Figure 1-5 Figure 1-6 shows how to remove the front door. Cisco ONS 15454 Reference Manual, R8.5.
-
Chapter 1 Shelf and Backplane Hardware 1.3 Front Door Removing the ONS 15454 Front Door FAN 38831 Figure 1-6 FAIL CR IT MA J MIN Translucent circles for LED viewing Door hinge Assembly hinge pin Assembly hinge An erasable label is pasted on the inside of the front door (Figure 1-7). You can use the label to record slot assignments, port assignments, card types, node ID, rack ID, and serial number for the ONS 15454. Cisco ONS 15454 Reference Manual, R8.5.
-
Chapter 1 Shelf and Backplane Hardware 1.4 Backplane Covers Front-Door Erasable Label 61840 Figure 1-7 Note The front door label also includes the Class I and Class 1M laser warning (Figure 1-8). Laser Warning on the Front-Door Label 67575 Figure 1-8 1.4 Backplane Covers If a backplane does not have an EIA panel installed, it should have two sheet metal backplane covers (one on each side of the backplane) as shown in Figure 1-9 on page 1-12.
-
Chapter 1 Shelf and Backplane Hardware 1.4.1 Lower Backplane Cover Figure 1-9 Backplane Covers B A Backplane Sheet Metal Covers 32074 Lower Backplane Cover 1.4.1 Lower Backplane Cover The lower section of the ONS 15454 backplane is covered by either a clear plastic protector (15454-SA-ANSI) or a sheet metal cover (15454-SA-HD), which is held in place by five 6-32 x 1/2 inch screws.
-
Chapter 1 Shelf and Backplane Hardware 1.4.2 Rear Cover 1.4.2 Rear Cover The ONS 15454 has an optional clear plastic rear cover. This clear plastic cover provides additional protection for the cables and connectors on the backplane. Figure 1-11 shows the rear cover screw locations. Figure 1-11 Backplane Attachment for Cover 32073 Screw locations for attaching the rear cover You can also install the optional spacers if more space is needed between the cables and rear cover (Figure 1-12).
-
Chapter 1 Shelf and Backplane Hardware 1.4.3 Alarm Interface Panel 55374 S A UIT P N A -4 IN LE O B 65 2 N S A -C LE 0 TO TR S E O FO W -5 U R M at 7 C E B R ts V TI FE U M M dc S O O ax N R TI U S TO B N im . LE TI um IN N S S U G TA R O LL FA N A C TI E O . N Installing the Plastic Rear Cover with Spacers R E T C th AU 1 pr e TI io B O B r AT1 N A to : T se an R em 1 rv d ic te ov R in rm e E g T in po al w 2 bl er B oc fro A ks m T bo 2 th Figure 1-12 1.4.
-
Chapter 1 Shelf and Backplane Hardware 1.5 Electrical Interface Assemblies You can replace the AIP on an in-service system without affecting traffic (except Ethernet traffic on nodes running a software release earlier than Release 4.0). The circuit repair feature allows you to repair circuits affected by MAC address changes on one node at a time. Circuit repair works when all nodes are running the same software version.
-
Chapter 1 Shelf and Backplane Hardware 1.5.1 EIA Installation 1.5.1 EIA Installation Optional EIA backplane covers are typically preinstalled when ordered with the ONS 15454. A minimal amount of assembly might be required when EIAs are ordered separately from the ONS 15454. If you are installing EIAs after the shelf assembly is installed, plug the EIA into the backplane. The EIA has six electrical connectors that plug into six corresponding backplane connectors.
-
Chapter 1 Shelf and Backplane Hardware 1.5.
-
Chapter 1 Shelf and Backplane Hardware 1.5.
-
Chapter 1 Shelf and Backplane Hardware 1.5.3 BNC EIA type. Use RG-59/U cable to connect to the ONS 15454 BNC EIA. These cables are recommended to connect to a patch panel and are designed for long runs. You can use BNC EIAs for DS-3 (including the DS3XM-6 and DS3XM-12) or EC-1 cards. Figure 1-13 shows the ONS 15454 with preinstalled BNC EIAs. To install coaxial cable with BNC connectors, refer to the “Install Shelf and Backplane Cable” chapter in the Cisco ONS 15454 Procedure Guide.
-
Chapter 1 Shelf and Backplane Hardware 1.5.4 High-Density BNC EIA 1.5.3.2 BNC Insertion and Removal Tool Due to the large number of BNC connectors on the high-density BNC EIA, you might require a special tool for inserting and removing BNC EIAs (Figure 1-14). This tool also helps with ONS 15454 patch panel connections. BNC Insertion and Removal Tool 44552 Figure 1-14 This tool can be obtained with P/N 227-T1000 from: Amphenol USA (www.amphenol.
-
Chapter 1 Shelf and Backplane Hardware 1.5.
-
Chapter 1 Shelf and Backplane Hardware 1.5.5 MiniBNC EIA • DS3/EC1-48 MiniBNCs support available high-density cards in unprotected and 1:N protection (where N < 2) protection groups. Table 1-3 shows protection groups and their applicable slot assignments.
-
Chapter 1 Shelf and Backplane Hardware 1.5.5 MiniBNC EIA Figure 1-16 MiniBNC Backplane for Use in 1:N Protection Schemes Cisco ONS 15454 Reference Manual, R8.5.
-
Chapter 1 Shelf and Backplane Hardware 1.5.5 MiniBNC EIA Table 1-4 and Table 1-5 show the J-labeling and corresponding card ports for a shelf assembly configured with low-density electrical cards.
-
Chapter 1 Shelf and Backplane Hardware 1.5.
-
Chapter 1 Shelf and Backplane Hardware 1.5.
-
Chapter 1 Shelf and Backplane Hardware 1.5.
-
Chapter 1 Shelf and Backplane Hardware 1.5.6 SMB EIA MiniBNC Insertion and Removal Tool 115419 Figure 1-17 This tool can be obtained with P/N 227-T1000 from: Amphenol USA (www.amphenol.com) One Kennedy Drive Danbury, CT 06810 Phone: 203 743-9272 Fax: 203 796-2032 This tool can be obtained with P/N RT-1L from: Trompeter Electronics Inc. (www.trompeter.com) 31186 La Baya Drive Westlake Village, CA 91362-4047 Phone: 800 982-2629 Fax: 818 706-1040 1.5.
-
Chapter 1 Shelf and Backplane Hardware 1.5.
-
Chapter 1 Shelf and Backplane Hardware 1.5.7 AMP Champ EIA Because each DS1-14 card supports 14 DS-1 ports, only 56 pins (28 pairs) of the 64-pin connector are used. Prepare one 56-wire cable for each DS-1 facility installed. Figure 1-19 AMP Champ EIA Backplane 32070 AMP CHAMP connector Table 1-8 shows the pin assignments for the AMP Champ connectors on the ONS 15454 AMP Champ EIA. The EIA side marked “A” hosts six AMP Champ connectors.
-
Chapter 1 Shelf and Backplane Hardware 1.5.
-
Chapter 1 Shelf and Backplane Hardware 1.5.
-
Chapter 1 Shelf and Backplane Hardware 1.5.8 UBIC-V EIA You can install UBIC-Vs on one or both sides of the ONS 15454. As you face the rear of the ONS 15454 shelf assembly, the right side is the A side (15454-EIA-UBICV-A) and the left side is the B side (15454-EIA-UBICV-B). The diagrams adjacent to each row of SCSI connectors indicate the slots and ports that correspond with each SCSI connector in that row, depending on whether you are using a high-density (HD) or low-density (LD) configuration.
-
Chapter 1 Shelf and Backplane Hardware 1.5.9 UBIC-H EIA When installed with the deep door and cabling on the backplane, the ONS 15454 shelf measures approximately 17.5 inches (445 mm) deep when partially populated with backplane cables, 17.9 inches (455 mm) deep when fully populated, and 18.55 inches (471 mm) deep with the rear cover installed.
-
Chapter 1 Shelf and Backplane Hardware 1.5.9 UBIC-H EIA Figure 1-21 shows the A- and B-side connector labeling. UBIC-H EIA Connector Labeling 124533 Figure 1-21 Tables 1-11 and 1-12 show the J-labeling and corresponding card ports for a shelf assembly configured with low-density electrical cards. Cisco ONS 15454 Reference Manual, R8.5.
-
Chapter 1 Shelf and Backplane Hardware 1.5.
-
Chapter 1 Shelf and Backplane Hardware 1.5.
-
Chapter 1 Shelf and Backplane Hardware 1.5.10 EIA Replacement The A and B sides each host 16 high-density, 50-pin SCSI connectors. The A-side maps to Slots 1 through 6 and the B-side maps to Slots 12 through 17. In Software Releases prior to Release 5.0, UBIC-Hs support unprotected, 1:1, and 1:N (where N < 5) protection groups. In Software R5.0 and greater, UBIC-Hs additionally support available high-density cards in unprotected and 1:N protection (where N < 2) protection groups.
-
Chapter 1 Shelf and Backplane Hardware 1.7.2 Electrical Interface Adapters Caution Always use the supplied ESD wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly. If you use DS-1 electrical twisted-pair cables, equip the ONS 15454 with an SMB EIA on each side of the backplane where DS-1 cables will terminate.
-
Chapter 1 Shelf and Backplane Hardware 1.8 UBIC-V Cables 1.8 UBIC-V Cables Note Cisco Systems announced the end-of-sale and end-of-life dates for the Cisco ONS 15454 MSPP Universal BackPlane Interface Adapter, Vertical Orientation (UBIC-V), and its DS1 and DS3 Cables. For further details, refer to Product Bulletin No. EOL5039 at http://www.cisco.com/en/US/partner/prod/collateral/optical/ps5724/ps2006/prod_end-of-life_notice09 00aecd8052a481.html.
-
Chapter 1 Shelf and Backplane Hardware 1.
-
Chapter 1 Shelf and Backplane Hardware 1.8 UBIC-V Cables Figure 1-24 UBIC-V DS-1 Cable Schematic Diagram UBIC-V DS-1 Cable Shield to connector shell Pin 1 75Ω Signal To/From UBIC-V DS1 75Ω Port #1 1:1.15 Tip DS1 #1 100Ω Differential DS-1 To/From DSx Ring DS1 #1 FGND Pin 2 — FGnd Pin 3 — FGnd Pin 4 — FGnd Pin 5 75Ω Signal To/From UBIC-V DS1 75Ω Port #2 1:1.15 Tip DS1 #2 100Ω Differential DS-1 To/From DSx Ring DS1 #2 FGND To/From Customer DSX To/From SCSI connector on the UBIC-V EIA 1:1.
-
Chapter 1 Shelf and Backplane Hardware 1.
-
Chapter 1 Shelf and Backplane Hardware 1.8 UBIC-V Cables Table 1-18 UBIC-V DS-3/EC-1 SCSI Connector Pin Out (continued) Port SCSI Pin SCSI Pin Port #5 17 42 #11 FGnd 18 43 FGnd FGnd 19 44 FGnd FGnd 20 45 FGnd #6 21 46 #12 FGnd 22 47 FGnd FGnd 23 48 FGnd FGnd 24 49 FGnd Not connected 25 50 Not connected Figure 1-25 shows the UBIC-V DS-3/EC-1 cable schematic diagram. Cisco ONS 15454 Reference Manual, R8.5.
-
Chapter 1 Shelf and Backplane Hardware 1.
-
Chapter 1 Shelf and Backplane Hardware 1.9 UBIC-H Cables To support DS-3 or EC-1 signals, select the DS-3/EC-1 UBIC-H cable assembly (part number 15454-CADS3-H-). DS-1 cables for the UBIC-H have a maximum supported distance of 655 feet (199.6 m). DS-1 cables arrive with unterminated #24 AWG twisted pairs on the far end and are color coded as identified in Table 1-20.
-
Chapter 1 Shelf and Backplane Hardware Figure 1-26 Cable Connector Pins Pin 1 Pin 25 Pin 26 Pin 50 115171 1.9 UBIC-H Cables Table 1-19 identifies the UBIC-H SCSI connector pin assignments for the DS-1 cables as referenced from the EIA backplane to the SCSI connector. Note Conversion from the back plane’s single ended (unbalanced) 75-ohm signal to a differential (balanced) 100-ohm signal happens through the embedded transformer within the SCSI connector.
-
Chapter 1 Shelf and Backplane Hardware 1.9 UBIC-H Cables Table 1-19 UBIC-H DS-1 SCSI Connector Pin Out (continued) Port SCSI Pin SCSI Pin Port FGnd 23 48 FGnd FGnd 24 49 FGnd #13 25 50 #14 Figure 1-27 UBIC-H DS-1 Cable Schematic Diagram UBIC-H DS-1 Cable Shield to connector shell Pin 1 75Ω Signal To/From UBIC-H DS1 75Ω Port #1 1:1.
-
Chapter 1 Shelf and Backplane Hardware 1.
-
Chapter 1 Shelf and Backplane Hardware 1.9 UBIC-H Cables Table 1-21 UBIC-H DS-3/EC-1 SCSI Connector Pin Out (continued) Port SCSI Pin SCSI Pin Port #5 17 42 #11 FGnd 18 43 FGnd FGnd 19 44 FGnd FGnd 20 45 FGnd #6 21 46 #12 FGnd 22 47 FGnd FGnd 23 48 FGnd FGnd 24 49 FGnd Not connected 25 50 Not connected Figure 1-28 shows the UBIC-H DS-3/EC-1 cable schematic diagram Cisco ONS 15454 Reference Manual, R8.5.
-
Chapter 1 Shelf and Backplane Hardware 1.10 Ethernet Cables Figure 1-28 UBIC-H DS-3/EC-1 Cable Schematic Diagram DS-3/EC1 Cable Pin 1 DS-3 75Ω Port #1 Port #1 75Ω Signal To/From UBIC Pin 5 DS-3 75Ω Port #2 Port #2 75Ω Signal To/From FGND From/To Customer DSx Pin 42 DS-3 75Ω Port #11 Port #11 75Ω Signal To/From FGND Pin 46 DS-3 75Ω Port #12 Port #12 75Ω DS-3/EC1 signal coming to/from Tyco SCSI connector and being placed on 735A (or 735C) Coax 273809 75Ω Signal To/From 1.
-
Chapter 1 Shelf and Backplane Hardware 1.10 Ethernet Cables Table 1-22 E100-TX Connector Pinout Pin Cable Port 1 RD+ 2 RD– 3 TD+ 4 NC 5 NC 6 TD– 7 NC 8 NC Figure 1-29 shows the pin locations on 100BaseT connector. Figure 1-29 100BaseT Connector Pins H5436 1234567 8 Figure 1-30 shows the straight-through Ethernet cable schematic. Use a straight-through cable when connecting to a router or a PC.
-
Chapter 1 Shelf and Backplane Hardware 1.11 Cable Routing and Management Figure 1-31 shows the crossover Ethernet cable schematic. Use a crossover cable when connecting to a switch or hub. Crossover Cable Switch Switch 3 TD+ 6 TD– 3 TD+ 6 TD– 1 RD+ 2 RD– 1 RD+ 2 RD– H5579 Figure 1-31 1.
-
Chapter 1 Shelf and Backplane Hardware 1.11.1 Fiber Management Figure 1-32 Managing Cables on the Front Panel FAN FAIL CR IT MA J MIN 145262 Cable-routing channel posts Fold down front door 1.11.1 Fiber Management The jumper routing fins are designed to route fiber jumpers out of both sides of the shelf. Slots 1 to 6 exit to the left, and Slots 12 to 17 exit to the right.
-
Chapter 1 Shelf and Backplane Hardware 1.11.2 Fiber Management Using the Tie-Down Bar Table 1-23 provides the maximum capacity of the fiber channel for one side of a shelf, depending on fiber size and number of Ethernet cables running through that fiber channel. Table 1-23 Fiber Channel Capacity (One Side of the Shelf) Maximum Number of Fibers Exiting Each Side Fiber Diameter No Ethernet Cables One Ethernet Cable Two Ethernet Cables 1.6 mm (0.6 inch) 144 127 110 2 mm (0.
-
Chapter 1 Shelf and Backplane Hardware 1.11.3 Coaxial Cable Management 1.11.3 Coaxial Cable Management Coaxial cables connect to EIAs on the ONS 15454 backplane using cable connectors. EIAs feature cable-management eyelets for tie wrapping or lacing cables to the cover panel. 1.11.4 DS-1 Twisted-Pair Cable Management Connect twisted pair/DS-1 cables to SMB EIAs on the ONS 15454 backplane using cable connectors and DS-1 EIAs (baluns). 1.11.
-
Chapter 1 Shelf and Backplane Hardware 1.12.1 Wire-Wrap and Pin Connections Figure 1-35 AEP Printed Circuit Board Assembly 78471 Input Connector Output Connector Figure 1-36 shows the AEP block diagram. Figure 1-36 AEP Block Diagram AIC-I Interface (wire wrapping) TIA/EIA 485 In Alarm Relays Out Alarm Relays 78406 Inventory data (EEPROM) AEP/AIE CPLD Power Supply Each AEP alarm input port has provisionable label and severity. The alarm inputs have optocoupler isolation.
-
Chapter 1 Shelf and Backplane Hardware 1.12.1 Wire-Wrap and Pin Connections Figure 1-37 AEP Wire-Wrap Connections to Backplane Pins Table 1-24 shows the backplane pin assignments and corresponding signals on the AIC-I and AEP.
-
Chapter 1 Shelf and Backplane Hardware 1.12.1 Wire-Wrap and Pin Connections Figure 1-38 Alarm Input Circuit Diagram Station AEP/AIE 48 V GND max. 2 mA Input 1 VBAT– Input 48 78473 VBAT– Table 1-25 lists the connections to the external alarm sources.
-
Chapter 1 Shelf and Backplane Hardware 1.12.1 Wire-Wrap and Pin Connections Table 1-25 Alarm Input Pin Association (continued) AMP Champ Pin Number Signal Name AMP Champ Pin Number Signal Name 20 GND 46 ALARM_IN_26– 21 ALARM_IN_27– 47 ALARM_IN_28– 22 ALARM_IN_29– 48 GND 23 GND 49 ALARM_IN_30– 24 ALARM_IN_31– 50 N.C. 25 ALARM_IN_+ 51 GND1 26 ALARM_IN_0– 52 GND2 Figure 1-39 is a circuit diagram of the alarm outputs (Outputs 1 and 16 are shown in the example).
-
Chapter 1 Shelf and Backplane Hardware 1.13 Filler Card Table 1-26 Pin Association for Alarm Output Pins (continued) AMP Champ Pin Number Signal Name AMP Champ Pin Number Signal Name 7 N.C. 33 COM_4 8 COM_5 34 N.C. 9 NO_5 35 NO_6 10 N.C. 36 COM_6 11 COM_7 37 N.C. 12 NO_7 38 NO_8 13 N.C. 39 COM_8 14 COM_9 40 N.C. 15 NO_9 41 NO_10 16 N.C. 42 COM_10 17 COM_11 43 N.C. 18 NO_11 44 NO_12 19 N.C. 45 COM_12 20 COM_13 46 N.C. 21 NO_13 47 NO_14 22 N.
-
Chapter 1 Shelf and Backplane Hardware 1.14 Fan-Tray Assembly Figure 1-40 Detectable Filler Card Faceplate 124234 FILLER 1.14 Fan-Tray Assembly The fan-tray assembly is located at the bottom of the ONS 15454 bay assembly. The fan tray is a removable drawer that holds fans and fan-control circuitry for the ONS 15454. The front door can be left in place or removed before installing the fan-tray assembly.
-
Chapter 1 Shelf and Backplane Hardware 1.14.1 Fan Tray Units for ONS 15454 Cards The front of the fan-tray assembly has an LCD screen that provides slot- and port-level information for all ONS 15454 card slots, including the number of Critical, Major, and Minor alarms. For optical cards, you can use the LCD to determine if a port is in working or protect mode and is active or standby. The LCD also tells you whether the software load is SONET or SDH and the software version number.
-
Chapter 1 Shelf and Backplane Hardware 1.14.
-
Chapter 1 Shelf and Backplane Hardware 1.14.2 Fan Speed Table 1-27 Fan Tray Units for ONS 15454 Cards ONS 15454 Cards 15454E-FTA-48V (ETSI shelf) /15454-FTA3-T(ANSI shelf) 15454E-CC-FTA (ETSI shelf)/ 15454-CC-FTA (ANSI shelf) G1000-4 Yes Yes G1K-4 Yes Yes M100T-12 Yes Yes M100X-8 Yes Yes ML1000-2 Yes Yes ML-MR-10 No Yes CE-100T-8 Yes Yes CE-MR-10 No Yes CE-1000-4 Yes Yes FC_MR-4 Yes Yes 1.14.2 Fan Speed Fan speed is controlled by TCC2/TCC2P card temperature sensors.
-
Chapter 1 Shelf and Backplane Hardware 1.14.5 Pilot Fuse Caution Do not operate an ONS 15454 without the mandatory fan-tray air filter. Caution Inspect the air filter every 30 days, and clean the filter every three to six months. Replace the air filter every two to three years. Avoid cleaning the air filter with harsh cleaning agents or solvents. Refer to the Cisco ONS 15454 Troubleshooting Guide for information about cleaning and maintaining the fan-tray air filter. 1.14.
-
Chapter 1 Shelf and Backplane Hardware 1.16 Alarm, Timing, LAN, and Craft Pin Connections The ONS 15454 has redundant –48 VDC #8 power terminals on the shelf-assembly backplane. The terminals are labeled BAT1, RET1, BAT2, and RET2 and are located on the lower section of the backplane behind a clear plastic cover. To install redundant power feeds, use four power cables and one ground cable. For a single power feed, only two power cables (#10 AWG, 2.588 mm² [0.
-
Chapter 1 Shelf and Backplane Hardware 1.16 Alarm, Timing, LAN, and Craft Pin Connections A ONS 15454 Backplane Pinouts (Release 3.
-
Chapter 1 Shelf and Backplane Hardware 1.16.1 Alarm Contact Connections A ONS 15454 Backplane Pinouts B A B A B A B A B A B A B A A B A B A 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 3 4 4 4 4 BITS 4 4 LAN ENVIR 4 ALARMS IN FG1 FG2 Field BITS FG3 Pin A1 4 4 ACO X .
-
Chapter 1 Shelf and Backplane Hardware 1.16.2 Timing Connections Visual and audible alarms are typically wired to trigger an alarm light or bell at a central alarm collection point when the corresponding contacts are closed. You can use the Alarm Cutoff pins to activate a remote ACO for audible alarms. You can also activate the ACO function by pressing the ACO button on the TCC2/TCC2P card faceplate. The ACO function clears all audible alarm indications.
-
Chapter 1 Shelf and Backplane Hardware 1.16.4 TL1 Craft Interface Installation Table 1-30 LAN Pin Assignments Pin Field Backplane Pins RJ-45 Pins LAN 1 Connecting to data circuit-terminating equipment (DCE1, a hub or switch) B2 1 A2 2 B1 3 A1 6 B1 1 A1 2 B2 3 A2 6 LAN 1 Connecting to data terminal equipment (DTE) (a PC/workstation or router) 1. The Cisco ONS 15454 is DCE. 1.16.
-
Chapter 1 Shelf and Backplane Hardware 1.17.1 Card Slot Requirements Installing Cards in the ONS 15454 39391 Figure 1-44 FAN FAIL CR IT MAJ MIN Ejector Guide rail 1.17.1 Card Slot Requirements The ONS 15454 shelf assembly has 17 card slots numbered sequentially from left to right. Slots 1 to 6 and 12 to 17 are multiservice slots that are used for electrical, optical, and Ethernet cards (traffic cards).
-
Chapter 1 Shelf and Backplane Hardware 1.17.1 Card Slot Requirements Note Protection schemes and EIA types can affect slot compatibility. Table 1-32 Symbol Color/Shape Slot and Card Symbols Definition Orange/Circle Slots 1 to 6 and 12 to 17. Only install ONS 15454 cards with a circle symbol on the faceplate. Blue/Triangle Slots 5, 6, 12, and 13. Only install ONS 15454 cards with circle or a triangle symbol on the faceplate. Purple/Square TCC2/TCC2P slot, Slots 7 and 11.
-
Chapter 1 Shelf and Backplane Hardware 1.17.1 Card Slot Requirements Table 1-33 Card Ports, Line Rates, and Connectors (continued) Card Ports Line Rate per Port Connector Types Connector Location DS3/EC1-48 48 2.147 Gbps SMB or BNC Backplane 1 EC1-12 12 51.
-
Chapter 1 Shelf and Backplane Hardware 1.17.2 Card Replacement Table 1-33 Card Ports, Line Rates, and Connectors (continued) Card Ports Line Rate per Port Connector Types Connector Location 15454_MRC-12 12 Up to 2488.32 Mbps (STM-48), depending on SFP LC Faceplate MRC-2.5G-4 4 Up to 2488.32 Mbps (STS-48), depending on SFP LC Faceplate 9.95 Gbps (OC-192) LC Faceplate OC192SR1/STM64 1 IO Short Reach/ OC192/STM64 Any Reach3 1.
-
Chapter 1 Shelf and Backplane Hardware 1.18 Software and Hardware Compatibility 1.18 Software and Hardware Compatibility Table 1-34 shows ONS 15454 software and hardware compatibility for nodes configured with XC or XCVT cards for Releases 4.6, 4.7, 5.0, 6.0, 7.0, 7.2, 8.0, and 8.5. For software compatibility for a specific card, refer to the following URL: http://cisco.com/en/US/products/hw/optical/ps2006/prod_eol_notices_list.
-
Chapter 1 Shelf and Backplane Hardware 1.18 Software and Hardware Compatibility Table 1-34 ONS 15454 Software and Hardware Compatibility—XC1 and XCVT Configurations (continued) Hardware Shelf Assembly2 4.6.0x (4.6) 5.0.0x (5.0) 6.0.0x (6.0) 7.0.0x (7.0) 7.2.0x (7.2) 8.0.0x (8.0) 8.5.0x (8.
-
Chapter 1 Shelf and Backplane Hardware 1.18 Software and Hardware Compatibility Table 1-34 ONS 15454 Software and Hardware Compatibility—XC1 and XCVT Configurations (continued) Hardware Shelf Assembly2 4.6.0x (4.6) 5.0.0x (5.0) 6.0.0x (6.0) 7.0.0x (7.0) 7.2.0x (7.2) 8.0.0x (8.0) 8.5.0x (8.
-
Chapter 1 Shelf and Backplane Hardware 1.18 Software and Hardware Compatibility 5. Slots 1 to 4 and 14 to 17 give a total bandwidth of up to 622 Mb/s. Slots 5, 6 , 12 , and 13 give a total bandwidth of up to 2.5 Gb/s 6. These cards are designated as OC192-XFP in CTC. Table 1-35 shows ONS 15454 software and hardware compatibility for systems configured with XC10G or XC-VXC-10G cards for Releases 4.6, 4.7, 5.0, 6.0, 7.0, 7.2, 8.0, and 8.5.
-
Chapter 1 Shelf and Backplane Hardware 1.18 Software and Hardware Compatibility Table 1-35 ONS 15454 Software and Hardware Compatibility—XC10G and XC-VXC-10G Configurations (continued) Shelf Assembly1 Hardware 4.6.0x (4.6) 5.0.0x (5.
-
Chapter 1 Shelf and Backplane Hardware 1.18 Software and Hardware Compatibility Table 1-35 ONS 15454 Software and Hardware Compatibility—XC10G and XC-VXC-10G Configurations (continued) Shelf Assembly1 4.6.0x (4.
-
Chapter 1 Shelf and Backplane Hardware 1.18 Software and Hardware Compatibility 3. Slots 1 to 4 and 14 to 17 give a total bandwidth of up to 2.5 Gb/s. Slots 5, 6, 12 , and 13 give a total bandwidth of up to 10 Gb/s 4. These cards are designated as OC192-XFP in CTC. If an upgrade is required for compatibility, contact the Cisco Technical Assistance Center (TAC). For contact information, go to http://www.cisco.com/tac. Cisco ONS 15454 Reference Manual, R8.5.
-
CH A P T E R 2 Common Control Cards 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.
-
Chapter 2 Common Control Cards 2.1.1 Cards Summary Table 2-1 Common Control Card Functions Card Description For Additional Information... TCC2 The Advanced Timing, Communications, and Control See the “2.2 TCC2 Card” section on page 2-6. (TCC2) card is the main processing center for the ONS 15454 and provides system initialization, provisioning, alarm reporting, maintenance, and diagnostics.
-
Chapter 2 Common Control Cards 2.1.2 Card Compatibility 2.1.2 Card Compatibility Table 2-2 lists the Cisco Transport Controller (CTC) software release compatibility for each common-control card. In the tables below, “Yes” means cards are compatible with the listed software versions. Table cells with dashes mean cards are not compatible with the listed software versions. Table 2-2 Common-Control Card Software Release Compatibility Card R3.3 R3.4 R4.0 R4.1 R4.5 R4.6 R4.7 R5.0 R6.0 R7.0 R7.
-
Chapter 2 Common Control Cards 2.1.3 Cross-Connect Card Compatibility Table 2-3 Common-Control Card Cross-Connect Compatibility (continued) Card XCVT Card XC10G Card1 XC-VXC-10G Card1 AEP Yes Yes Yes 1. Requires SA-ANSI or SA-HD shelf assembly. 2. The TCC+ is not compatible with Software R4.5 or greater. 3. These cross-connect cards are compatible only during an upgrade. Table 2-4 lists the cross-connect card compatibility for each electrical card.
-
Chapter 2 Common Control Cards 2.1.
-
Chapter 2 Common Control Cards 2.2 TCC2 Card Table 2-6 Ethernet Card Cross-Connect Compatibility (continued) Ethernet Cards XCVT Card XC10G Card1 XC-VXC-10G Card1 G1K-4 Yes, in Slots 5, 6, 12, 13 Yes Yes ML100T-12 Yes, in Slots 5, 6, 12, 13 Yes Yes ML1000-2 Yes, in Slots 5, 6, 12, 13 Yes Yes ML-MR-10 No Yes Yes ML100X-8 Yes, in Slots 5, 6, 12, 13 Yes Yes CE-100T-8 Yes Yes Yes CE-1000-4 Yes Yes Yes CE-MR-10 Yes Yes Yes 1.
-
Chapter 2 Common Control Cards 2.2.
-
Chapter 2 Common Control Cards 2.2.2 TCC2 Card-Level Indicators The TCC2 card also originates and terminates a cell bus carried over the module. The cell bus supports links between any two cards in the node, which is essential for peer-to-peer communication. Peer-to-peer communication accelerates protection switching for redundant cards. The node database, IP address, and system software are stored in TCC2 card nonvolatile memory, which allows quick recovery in the event of a power or card failure.
-
Chapter 2 Common Control Cards 2.2.3 Network-Level Indicators Table 2-8 TCC2 Card-Level Indicators Card-Level LEDs Definition Red FAIL LED This LED is on during reset. The FAIL LED flashes during the boot and write process. Replace the card if the FAIL LED persists. ACT/STBY LED Indicates the TCC2 is active (green) or in standby (amber) mode. The ACT/STBY LED also provides the timing reference and shelf control.
-
Chapter 2 Common Control Cards 2.2.4 Power-Level Indicators 2.2.4 Power-Level Indicators Table 2-9 describes the two power-level LEDs on the TCC2 faceplate. Table 2-9 TCC2 Power-Level Indicators Power-Level LEDs Definition Green/Amber/Red PWR A LED The PWR A LED is green when the voltage on supply input A is between the low battery voltage (LWBATVG) and high battery voltage (HIBATVG) thresholds.
-
Chapter 2 Common Control Cards 2.3.
-
Chapter 2 Common Control Cards 2.3.1 TCC2P Functionality The TCC2P card also originates and terminates a cell bus carried over the module. The cell bus supports links between any two cards in the node, which is essential for peer-to-peer communication. Peer-to-peer communication accelerates protection switching for redundant cards. The node database, IP address, and system software are stored in TCC2P card nonvolatile memory, which allows quick recovery in the event of a power or card failure.
-
Chapter 2 Common Control Cards 2.3.1 TCC2P Functionality reference as the system-timing reference. You can provision any of the clock inputs as primary or secondary timing sources. A slow-reference tracking loop allows the TCC2P card to synchronize with the recovered clock, which provides holdover if the reference is lost. The minimum free-run accuracy, holdover stability, pull-in, and hold-in characteristics are as defined in ITU-T G.813 option I in Section 5, 6, and 10, ITU-T G.
-
Chapter 2 Common Control Cards 2.3.2 TCC2P Card-Level Indicators 2.3.2 TCC2P Card-Level Indicators The TCC2P faceplate has ten LEDs. Table 2-10 describes the two card-level LEDs on the TCC2P faceplate. Table 2-10 TCC2P Card-Level Indicators Card-Level LEDs Definition Red FAIL LED This LED is on during reset. The FAIL LED flashes during the boot and write process. Replace the card if the FAIL LED persists. ACT/STBY LED Indicates the TCC2P is active (green) or in standby (amber) mode.
-
Chapter 2 Common Control Cards 2.3.4 Power-Level Indicators 2.3.4 Power-Level Indicators Table 2-12 describes the two power-level LEDs on the TCC2P faceplate. Table 2-12 TCC2P Power-Level Indicators Power-Level LEDs Definition Green/Amber/Red PWR A LED The PWR A LED is green when the voltage on supply input A is between the low battery voltage (LWBATVG) and high battery voltage (HIBATVG) thresholds.
-
Chapter 2 Common Control Cards 2.4.1 XCVT Functionality Figure 2-3 XCVT Faceplate and Block Diagram XCVT FAIL ACT/STBY Input ports Output ports 0 0 Ports 0 1 2 STS ASIC1 3 4 0 Ports 1 1 2 2 3 3 4 4 5 5 5 6 1 STS ASIC2 2 3 4 5 6 6 7 7 8 8 9 VT ASIC 9 10 11 11 61341 10 33678 12931 2.4.1 XCVT Functionality The STS-1 switch matrix on the XCVT card consists of 288 bidirectional ports and adds a VT matrix that can manage up to 336 bidirectional VT1.
-
Chapter 2 Common Control Cards 2.4.2 VT Mapping The XCVT card works with the TCC2/TCC2P cards to maintain connections and set up cross-connects within the node. The cross-connect cards (such as the XCVT and XC10G), installed in Slots 8 and 10, are required to operate the ONS 15454. You can establish cross-connect (circuit) information through CTC. The TCC2/TCC2P cards establish the proper internal cross-connect information and relay the setup information to the XCVT card.
-
Chapter 2 Common Control Cards 2.4.
-
Chapter 2 Common Control Cards 2.5 XC10G Card Table 2-14 XCVT Card-Level Indicators Card-Level Indicators Definition Red FAIL LED Indicates that the cards processor is not ready. Replace the card if the red FAIL LED persists. ACT/STBY LED Indicates whether the XCVT card is active and carrying traffic (green) or in standby mode to the active XCVT card (amber). Green (Active) Amber (Standby) 2.5 XC10G Card Note For hardware specifications, see the “A.4.
-
Chapter 2 Common Control Cards 2.5.1 XC10G Functionality Figure 2-5 XC10G Faceplate and Block Diagram XC10G Line 1 FAIL Line 2 ACT/STBY Line 3 Line 4 uP Interface Span 1 Span 2 Cross-Connect Matrix Span 3 Span 4 Line 5 VT Cross-Connect Matrix Line 6 Line 7 Line 8 Ref Clk A FLASH Ref Clk B B a c k p l a n e RAM uP Interface TCCA ASIC SCL Link Protect SCL 61342 Main SCL uP 2.5.1 XC10G Functionality The XC10G card manages up to 672 bidirectional VT1.
-
Chapter 2 Common Control Cards 2.5.2 VT Mapping Caution Do not operate the ONS 15454 with only one XCVT or XC10G card. Two cross-connect cards of the same type (either two XCVT or two XC10G cards) must always be installed. Figure 2-6 shows the cross-connect matrix. Figure 2-6 XC10G Cross-Connect Matrix XC10G STS-1 Cross-connect ASIC (1152x1152 STS-1) Input Ports 8X STS-48 4X STS-192 Output Ports 1 1 2 2 . . . . . . . . 25 25 8X STS-48 4X STS-192 VT 1.
-
Chapter 2 Common Control Cards 2.5.3 XC10G Hosting DS3XM-6 or DS3XM-12 Table 2-15 VT Mapping (continued) ONS 15454 VT Number Telcordia Group/VT Number VT12 Group5/VT2 VT13 Group6/VT2 VT14 Group7/VT2 VT15 Group1/VT3 VT16 Group2/VT3 VT17 Group3/VT3 VT18 Group4/VT3 VT19 Group5/VT3 VT20 Group6/VT3 VT21 Group7/VT3 VT22 Group1/VT4 VT23 Group2/VT4 VT24 Group3/VT4 VT25 Group4/VT4 VT26 Group5/VT4 VT27 Group6/VT4 VT28 Group7/VT4 2.5.
-
Chapter 2 Common Control Cards 2.5.5 XCVT/XC10G/XC-VXC-10G Compatibility 2.5.5 XCVT/XC10G/XC-VXC-10G Compatibility The XC10G and XC-VXC-10G cards support the same features as the XCVT card. The XC10G or XC-VXC-10G cards are required for OC-192, OC-48 any-slot (AS), OC3-8, and OC12-4 operation. Do not use the XCVT card if you are using an OC-192, OC3-8, or OC12-4 card or if you install an OC-48 AS card in Slots 1 to 4 or 14 to 17.
-
Chapter 2 Common Control Cards 2.6.1 XC-VXC-10G Functionality Figure 2-7 XC-VXC-10G Faceplate and Block Diagram XC-VXC10G XC-VXC-10G Backplane Connectors SCL Bus FAIL IBPIA (2) ACT/STBY IBPIA (2) TCCA Clock FPGA STS-1 Cross Connect ASIC 2 VT Ports 2 VT Ports 6 AUX Ports FLASH 6 AUX Ports EDVT TULA GDX2 TU Cross Connect ASIC EEPROM Serial Port 2 VT Ports 2 VT Ports CPU VT Cross Connect ASIC DDR SDRAM DETLEF DDR FPGA 134364 CPLD TARAN GDX1 2.6.
-
Chapter 2 Common Control Cards 2.6.1 XC-VXC-10G Functionality At the STS level (high-order cross-connect), the XC-VXC-10G is always non-blocking (any STS-1 from the system can be cross-connected to any other STS-1 without limitation up to 1152 bidirectional STS-1 ports (576 STS-1 cross-connects). In addition, for “mixed” VT1.5 and VT2 grooming, 50% of the available VT resources (ports) are allocated to each VT circuit type.
-
Chapter 2 Common Control Cards 2.6.2 VT Mapping Figure 2-8 XC-VXC-10G Cross-Connect Matrix XC-XVC-10G STS-1 Cross-connect ASIC (1152x1152 STS-1) Input Ports 8X STS-48 4X STS-192 Output Ports 1 1 2 2 . . . . . . . . 20 20 8X STS-48 4X STS-192 6X STS-48 2X STS-48 (VT Ports) TUXC TU-3 Cross-connect ASIC (bypassed in SONETmode) VTXC VT 1.5/VT 2 Cross-connect ASIC 1344 bidirectional VT 1.5 cross-connects, or 1008 bidirectional VT 2 cross-connects, or Mixed grooming (50% VT1.
-
Chapter 2 Common Control Cards 2.6.3 XC-VXC-10G Hosting DS3XM-6 or DS3XM-12 Table 2-17 VT Mapping (continued) ONS 15454 VT Number Telcordia Group/VT Number VT14 Group7/VT2 VT15 Group1/VT3 VT16 Group2/VT3 VT17 Group3/VT3 VT18 Group4/VT3 VT19 Group5/VT3 VT20 Group6/VT3 VT21 Group7/VT3 VT22 Group1/VT4 VT23 Group2/VT4 VT24 Group3/VT4 VT25 Group4/VT4 VT26 Group5/VT4 VT27 Group6/VT4 VT28 Group7/VT4 2.6.
-
Chapter 2 Common Control Cards 2.6.5 XC-VXC-10G Compatibility 2.6.5 XC-VXC-10G Compatibility The XC-VXC-10G card supports the same features as the XC10G card. Either the XC10G or XC-VXC-10G card is required for OC-192, OC3-8, and OC12-4 operation and OC-48 AS operation. If you are using Ethernet cards, the E1000-2-G or the E100T-G must be used when the XC-VXC-10G cross-connect card is in use.
-
Chapter 2 Common Control Cards 2.7.1 AIC-I Card-Level Indicators Figure 2-9 AIC-I Faceplate and Block Diagram AIC-1 FAIL Fail PWR A B AIC-I Act ACT UDC-A UDC-B ACC INPUT/OUTPUT DCC-A DCC-B Express orderwire ACC (DTMF) Ring Local orderwire 12/16 x IN (DTMF) UDC-A Ring 4x IN/OUT UDC-B Ringer DCC-A Power Monitoring DCC-B RING Input LOW LED x2 AIC-I FPGA Output EOW RING EEPROM 78828 SCL links 2.7.
-
Chapter 2 Common Control Cards 2.7.2 External Alarms and Controls Table 2-19 AIC-I Card-Level Indicators (continued) Card-Level LEDs Description Green/Red PWR A LED The PWR A LED is green when a supply voltage within a specified range has been sensed on supply input A. It is red when the input voltage on supply input A is out of range. Green/Red PWR B LED The PWR B LED is green when a supply voltage within a specified range has been sensed on supply input B.
-
Chapter 2 Common Control Cards 2.7.3 Orderwire The output contacts can be provisioned to close on a trigger or to close manually. The trigger can be a local alarm severity threshold, a remote alarm severity, or a virtual wire: • Local NE alarm severity: A hierarchy of Not Reported, Not Alarmed, Minor, Major, or Critical alarm severities that you set to cause output closure. For example, if the trigger is set to Minor, a Minor alarm or above is the trigger.
-
Chapter 2 Common Control Cards 2.7.4 Power Monitoring The AIC-I supports selective dual tone multifrequency (DTMF) dialing for telephony connectivity, which causes one AIC-I card or all ONS 15454 AIC-I cards on the orderwire subnetwork to “ring.” The ringer/buzzer resides on the AIC-I. There is also a “ring” LED that mimics the AIC-I ringer. It flashes when a call is received on the orderwire subnetwork. A party line call is initiated by pressing *0000 on the DTMF pad.
-
Chapter 2 Common Control Cards 2.7.6 Data Communications Channel Table 2-21 UDC Pin Assignments RJ-11 Pin Number Description 1 For future use 2 TXN 3 RXN 4 RXP 5 TXP 6 For future use 2.7.6 Data Communications Channel The DCC features a dedicated data channel of 576 kbps (D4 to D12 bytes) between two nodes in an ONS 15454 network. Each AIC-I card provides two DCCs, DCC-A and DCC-B, through separate RJ-45 connectors on the front of the AIC-I card. Use a shielded RJ-45 cable.
-
Chapter 2 Common Control Cards 2.7.6 Data Communications Channel Cisco ONS 15454 Reference Manual, R8.5.
-
CH A P T E R 3 Electrical Cards This chapter describes Cisco ONS 15454 electrical card features and functions. For installation and card turn-up procedures, refer to the Cisco ONS 15454 Procedure Guide. For information on the electrical interface assemblies (EIAs), see the “1.5 Electrical Interface Assemblies” section on page 1-15. Chapter topics include: • 3.1 Electrical Card Overview, page 3-1 • 3.2 Bit Error Rate Testing, page 3-4 • 3.3 EC1-12 Card, page 3-5 • 3.
-
Chapter 3 Electrical Cards 3.1.1 Card Summary Table 3-1 Cisco ONS 15454 Electrical Cards Card Name Description For Additional Information EC1-12 The EC1-12 card provides 12 Telcordia-compliant, GR-253 STS-1 electrical ports per card. Each port operates at 51.840 Mbps over a single 750-ohm, 728A or equivalent coaxial span. See the “3.3 EC1-12 Card” section on page 3-5. DS1-14 The DS1-14 card provides 14 Telcordia-compliant GR-499 DS-1 ports. Each port operates at 1.
-
Chapter 3 Electrical Cards 3.1.2 Card Compatibility Table 3-1 Cisco ONS 15454 Electrical Cards (continued) Card Name Description For Additional Information DS3XM-6 (Transmux) See the “3.10 DS3XM-6 Card” The DS3XM-6 card provides six Telcordiasection on page 3-25. compliant GR-499-CORE M13 multiplexing functions. The DS3XM-6 converts six framed DS-3 network connections to 28x6 or 168 VT1.5s. DS3XM-12 (Transmux) See the “3.
-
Chapter 3 Electrical Cards 3.2 Bit Error Rate Testing 3.2 Bit Error Rate Testing The bit error rate testing (BERT) feature can be used to test the connectivity, error rate, and error count of the traffic running on an electrical input/output (I/O) card port. The BERT feature is currently supported for ONS 15454 DS1/E1-56 and DS3XM-12 electrical cards only.
-
Chapter 3 Electrical Cards 3.3 EC1-12 Card BERT Alarms The BERT feature can raise the following two alarms in CTC: • BERT_ENABL—Specifies that BERT feature is enabled. • BERT_SYNC_FAIL—Synchronization is necessary and occurs when the errors injected by the TPG reach the TPM and connectivity is established. The BERT_SYNC_FAIL alarm occurs when synchronization fails. Both the alarms are non-reportable conditions, non-service affecting, and no severity is associated with these two conditions. 3.
-
Chapter 3 Electrical Cards 3.3.3 EC1-12 Hosted by XCVT, XC10G, or XC-VXC-10G Figure 3-1 EC1-12 Faceplate and Block Diagram EC1 12 FAIL ACT/STBY SF main STS1 Line Interface Unit x12 STS-12/ 12xSTS-1 Mux/Demux ASIC BTC ASIC B a c k p l a n e 61344 protect STS1 STS-1 Framer 3.3.3 EC1-12 Hosted by XCVT, XC10G, or XC-VXC-10G All 12 STS-1 payloads from an EC1-12 card are carried to the XCVT, XC10G, or XC-VXC-10G card where the payload is further aggregated for efficient transport.
-
Chapter 3 Electrical Cards 3.3.5 EC1-12 Port-Level Indicators Table 3-4 EC1-12 Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the EC1-12 card processor is not ready. Replace the unit if the FAIL LED persists. Green ACT LED The green ACT LED indicates that the EC1-12 card is operational and ready to carry traffic.
-
Chapter 3 Electrical Cards 3.4.2 DS1-14 and DS1N-14 Slot Compatibility If you use the DS1N-14 as a standard DS-1 card in a 1:1 protection group, you can install the DS1N-14 card in Slots 1 to 6 or 12 to 17 on the ONS 15454. If you use the card’s 1:N functionality, you must install a DS1N-14 card in Slots 3 and 15. Each DS1N-14 port features DS-n-level outputs supporting distances of up to 655 feet (200 meters) depending on facility conditions. 3.4.
-
Chapter 3 Electrical Cards 3.4.4 DS1-14 and DS1N-14 Hosted by XCVT, XC10G, or XC-VXC-10G Figure 3-3 DS1N-14 Faceplate and Block Diagram DS1N14 FAIL ACT/STBY SF Protection Relay Matrix 14 Line Interface Units STS1 to 14 DS1 Mapper STS-1 / STS-12 Mux/Demux ASIC BTC ASIC B a c k p l a n e DRAM FLASH 61346 uP 33678 12931 3.4.4 DS1-14 and DS1N-14 Hosted by XCVT, XC10G, or XC-VXC-10G All 14 VT1.
-
Chapter 3 Electrical Cards 3.4.6 DS1-14 and DS1N-14 Port-Level Indicators Table 3-5 DS1-14 and DS1N-14 Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card processor is not ready. Replace the card if the red FAIL LED persists. ACT/STBY LED The green/amber ACT/STBY LED indicates whether the card is operational and ready to carry traffic (green) or in standby mode (amber).
-
Chapter 3 Electrical Cards 3.5.2 DS1/E1-56 Faceplate and Block Diagram Note The DS1/E1-56 card supports an errorless software-initiated cross-connect card switch when used in a shelf equipped with XC-VXC-10G and TCC2/TCC2P cards. You can install the DS1/E1-56 card in Slots 1 to 3 or 15 to 17 on the ONS 15454, but installing this card in certain slots will block the use of other slots.
-
Chapter 3 Electrical Cards 3.5.
-
Chapter 3 Electrical Cards 3.5.4 DS1/E1-56 Port-Level Indicators Table 3-7 DS1/E1-56 Card-Level Indicators Card-Level Indicators Description Red FAIL LED Indicates that the card processor is not ready. This LED is on during reset. The FAIL LED flashes during the boot process. Replace the card if the red FAIL LED persists in flashing. ACT/STBY LED When the ACT/STBY LED is green, the card is operational and ready to carry traffic.
-
Chapter 3 Electrical Cards 3.6.1 DS3-12 and DS3N-12 Slots and Connectors 3.6.1 DS3-12 and DS3N-12 Slots and Connectors You can install the DS3-12 or DS3N-12 card in Slots 1 to 6 or 12 to 17 on the ONS 15454. Each DS3-12 or DS3N-12 card port features DSX-level outputs supporting distances up to 137 meters (450 feet) depending on facility conditions. With the proper backplane EIA, the card supports BNC or SMB connectors. See the “7.
-
Chapter 3 Electrical Cards 3.6.3 DS3-12 and DS3N-12 Card-Level Indicators Figure 3-6 shows the DS3N-12 faceplate and a block diagram of the card. Figure 3-6 DS3N-12 Faceplate and Block Diagram DS3N 12 FAIL ACT/STBY Protection Relay Matrix 12 Line Interface Units DS3A ASIC BTC ASIC B a c k p l a n e 61348 SF 1345987 3.6.3 DS3-12 and DS3N-12 Card-Level Indicators Table 3-8 describes the three card-level LEDs on the DS3-12 and DS3N-12 card faceplates.
-
Chapter 3 Electrical Cards 3.6.4 DS3-12 and DS3N-12 Port-Level Indicators 3.6.4 DS3-12 and DS3N-12 Port-Level Indicators You can find the status of the 12 DS3-12 and 12 DS3N-12 card ports by using the LCD screen on the ONS 15454 fan-tray assembly. Use the LCD to view the status of any port or card slot; the screen displays the number and severity of alarms for a given port or slot. 3.7 DS3/EC1-48 Card Note For hardware specifications, see the “A.5.4 DS3/EC1-48 Card Specifications” section on page A-20.
-
Chapter 3 Electrical Cards 3.7.2 DS3/EC1-48 Faceplate and Block Diagram Caution Do not install a DS3/EC1-48 card in Slots 1 or 2 if you have installed an MXP_2.5G_10G card in Slot 3. Likewise, do not install a DS3/EC1-48 card in Slots 16 or 17 if you have installed an MXP_2.5G_10G card in Slot 15. If you do, the cards will interact and cause DS-3 bit errors. With the proper backplane EIA, the card supports BNC or SCSI (UBIC) connectors. See the “7.
-
Chapter 3 Electrical Cards 3.7.3 DS3/EC1-48 Card-Level Indicators Figure 3-7 DS3/EC1-48 Faceplate and Block Diagram DS3 EC1 48 FAIL ACT/STBY Main & Protect SCL Bus’s SF MAIN IBPIA ASIC (UBIC-V, UBIC-H, or HD MiniBNC) Transformers & Protection Mux/Relays 4x DS3/EC1 Framer/ Mapper/ LIU STS-48 Mapper FPGA PROTECT IBPIA ASIC 115955 48 DS3/EC1 Ports B a c k p l a n e Processor 3.7.3 DS3/EC1-48 Card-Level Indicators The DS3/EC1-48 card has three card-level LED indicators (Table 3-10).
-
Chapter 3 Electrical Cards 3.7.4 DS3/EC1-48 Port-Level Indicators Table 3-10 DS3/EC1-48 Card-Level Indicators Card-Level Indicators Description Red FAIL LED Indicates that the card processor is not ready. This LED is on during reset. The FAIL LED flashes during the boot process. Replace the card if the red FAIL LED persists in flashing. ACT/STBY LED When the ACT/STBY LED is green, the card is operational and ready to carry traffic.
-
Chapter 3 Electrical Cards 3.8.
-
Chapter 3 Electrical Cards 3.8.2 DS3i-N-12 Card-Level Indicators 3.8.2 DS3i-N-12 Card-Level Indicators Table 3-11 describes the three LEDs on the DS3i-N-12 card faceplate. Table 3-11 DS3i-N-12 Card-Level Indicators Card-Level LEDs Description Red FAIL LED Indicates that the card processor is not ready. This LED is on during reset. The FAIL LED flashes during the boot process. Replace the card if the red FAIL LED persists in flashing.
-
Chapter 3 Electrical Cards 3.9.1 DS3-12E and DS3N-12E Slots and Connectors • FEBE monitoring • FEAC status and loop code detection • Path trace byte support with TIM-P alarm generation The DS3-12E supports a 1:1 protection scheme, meaning it can operate as the protect card for one other DS3-12E card. The DS3N-12E can operate as the protect card in a 1:N (N <= 5) DS3 protection group.
-
Chapter 3 Electrical Cards 3.9.2 DS3-12E Faceplate and Block Diagram Figure 3-9 DS3-12E Faceplate and Block Diagram DS3 12E FAIL ACT SF main DS3-m1 protect DS3-p1 Line Interface Unit #1 DS3 ASIC BERT FPGA main DS3-m12 protect DS3-p12 Line Interface Unit #1 OHP FPGA BTC ASIC B a c k p l a n e Processor SDRAM Flash 61349 uP bus Figure 3-10 shows the DS3N-12E faceplate and a block diagram of the card. Cisco ONS 15454 Reference Manual, R8.5.
-
Chapter 3 Electrical Cards 3.9.3 DS3-12E and DS3N-12E Card-Level Indicators Figure 3-10 DS3N-12E Faceplate and Block Diagram DS3 N 12E FAIL ACT/STBY SF main DS3-m1 protect DS3-p1 Line Interface Unit #1 DS3 ASIC BERT FPGA main DS3-m12 protect DS3-p12 Line Interface Unit #1 OHP FPGA BTC ASIC B a c k p l a n e Processor SDRAM Flash 61350 uP bus 3.9.3 DS3-12E and DS3N-12E Card-Level Indicators Table 3-12 describes the three card-level LEDs on the DS3-12E and DS3N-12E card faceplates.
-
Chapter 3 Electrical Cards 3.9.4 DS3-12E and DS3N-12E Port-Level Indicators 3.9.4 DS3-12E and DS3N-12E Port-Level Indicators You can find the status of the DS3-12E and DS3N-12E card ports by using the LCD screen on the ONS 15454 fan-tray assembly. Use the LCD to quickly view the status of any port or card slot; the screen displays the number and severity of alarms for a given port or slot. 3.10 DS3XM-6 Card Note For hardware specifications, see the “A.5.
-
Chapter 3 Electrical Cards 3.10.3 DS3XM-6 Hosted By XCVT, XC10G, or XC-VXC-10G Figure 3-11 DS3XM-6 Faceplate and Block Diagram DS3XM 6 FAIL ACT SF Mapper unit Protection Relay Matrix 6 x Line Interface Units 6 x M13 Units DRAM 6 STS-1 / STS-12 Mux/Demux ASIC FLASH BTC ASIC B a c k p l a n e DC/DC unit 61351 uP 6 STS1 to 28 DS1 Mapper 1345987 3.10.3 DS3XM-6 Hosted By XCVT, XC10G, or XC-VXC-10G The DS3XM-6 card works in conjunction with the XCVT card.
-
Chapter 3 Electrical Cards 3.10.5 DS3XM-6 Port-Level Indicators Table 3-13 DS3XM-6 Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card processor is not ready. Replace the card if the red FAIL LED persists. ACT/STBY LED When the ACT/STBY LED is green, the DS3XM-6 card is operational and ready to carry traffic. When the ACT/STBY LED is amber, the DS3XM-6 card is operational and in standby in a 1:1 protection group.
-
Chapter 3 Electrical Cards 3.11.2 Ported Mode The DS3XM-12 supports three different backplane throughput configurations: • STS-48 when an XC10G or XC-VXC-10G card is used. This configuration supports the OC-48 rate in any slot. • STS-48 for the Slots 5, 6, 12, and 13 when an XCVT card is used. • STS-12 for Slot 1 through 4, and 7 through 12 slots when an XCVT card is used. This configuration is bandwidth-limiting in the portless mode of operation.
-
Chapter 3 Electrical Cards 3.11.5 Protection Modes 3.11.5 Protection Modes The DS3XM-12 card supports 1:1 and 1:N protection groups, where N <= 5. However, N <= 7 if one of the following conditions is true: • Only portless connections are used. • A combination of ported and portless connections is used but all the ported cards being protected are on the same side of the chassis as the protecting card.
-
Chapter 3 Electrical Cards 3.11.
-
Chapter 3 Electrical Cards 3.11.9 DS3XM-12 Card-Level Indicators Figure 3-12 DS3XM-12 Faceplate and Block Diagram DS3XM 12 FAIL ACT/STBY SF Main & Protect SCL Bus’s VT1.5 Mapped STS-1's (Both Modes) MAIN IBPIA ASIC 12 DS3 Transformers Ports & Protection Mux/Relays 12 Port DS3 LIU 4x DS3/VT1.5 Framer/ Mapper STS-24 Mapper FPGA PROTECT IBPIA ASIC B a c k p l a n e 115956 DS3 Mapped STS’1s (Portless Mode) Processor 3.11.
-
Chapter 3 Electrical Cards 3.11.10 DS3XM-12 Port-Level Indicators Table 3-16 DS3XM-12 Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card processor is not ready. It is steady while the self-test runs, and blinks during provisioning. Replace the card if the red FAIL LED persists. ACT/STBY LED Green (Active) When the ACT/STBY LED is green, the DS3XM-12 card is operational and ready to carry traffic.
-
CH A P T E R 4 Optical Cards 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.
-
Chapter 4 Optical Cards 4.1 Optical Card Overview • 4.20 OC192SR1/STM64IO Short Reach and OC192/STM64 Any Reach Cards, page 4-50 • 4.21 Optical Card SFPs and XFPs, page 4-52 4.1 Optical Card Overview Each card is marked with a symbol that corresponds to a slot (or slots) on the ONS 15454 shelf assembly. The cards are then installed into slots displaying the same symbols. See the “1.17 Cards and Slots” section on page 1-71 for a list of slots and symbols. 4.1.
-
Chapter 4 Optical Cards 4.1.1 Card Summary Table 4-1 Optical Cards for the ONS 15454 (continued) Card Port Description For Additional Information... OC12 LR/STM4 LH 1550 The OC12 LR/STM4 LH 1550 card provides one long-range OC-12 port and operates at 1550 nm. See the “4.6 OC12 LR/STM4 LH 1550 Card” section on page 4-13. OC12 IR/STM4 SH The OC12 IR/STM4 SH 1310-4 card provides four 1310-4 intermediate- or short-range OC-12 ports and operates at 1310 nm. See the “4.
-
Chapter 4 Optical Cards 4.1.2 Card Compatibility Table 4-1 Optical Cards for the ONS 15454 (continued) Card Port Description For Additional Information... 15454_MRC-12 The 15454_MRC-12 card provides up to twelve OC-3 See the or OC-12 ports, or up to four OC-48 ports. The card “4.18 15454_MRC-12 operates in Slots 1 to 6 and 12 to 17. Multirate Card” section on page 4-41. MRC-2.5G-4 The MRC-2.5G-4 card provides up to four OC-3/STM-1 or OC-12/STM-4 ports, or one OC-48/STM-16 ports.
-
Chapter 4 Optical Cards 4.1.2 Card Compatibility Table 4-2 Optical Card Software Release Compatibility Optical Card R3.3 R3.4 R4.0 R4.1 R4.51 R4.6 R4.71 R5.0 R6.0 R7.0 R7.2 R8.0 8.
-
Chapter 4 Optical Cards 4.2 OC3 IR 4/STM1 SH 1310 Card 4.2 OC3 IR 4/STM1 SH 1310 Card Note For hardware specifications, see the “A.6.1 OC3 IR 4/STM1 SH 1310 Card Specifications” section on page A-28. See Table 4-2 on page 4-5 for optical card compatibility. The OC3 IR 4/STM1 SH 1310 card provides four intermediate or short range SONET/SDH OC-3 ports compliant with ITU-T G.707, ITU-T G.957, and Telcordia GR-253-CORE. Each port operates at 155.52 Mbps over a single-mode fiber span.
-
Chapter 4 Optical Cards 4.2.1 OC3 IR 4/STM1 SH 1310 Card-Level Indicators You can install the OC3 IR 4/STM1 SH 1310 card in Slots 1 to 6 and 12 to 17. The card can be provisioned as part of a path protection or a linear add/drop multiplexer (ADM) configuration. Each interface features a 1310-nm laser and contains a transmit and receive connector (labeled) on the card faceplate. The card uses SC connectors. The OC3 IR 4/STM1 SH 1310 card supports 1+1 unidirectional or bidirectional protection switching.
-
Chapter 4 Optical Cards 4.3 OC3 IR/STM1 SH 1310-8 Card 4.3 OC3 IR/STM1 SH 1310-8 Card Note For hardware specifications, see the “A.6.2 OC3 IR/STM1SH 1310-8 Card Specifications” section on page A-29. See Table 4-2 on page 4-5 for optical card compatibility. The OC3 IR/STM1 SH 1310-8 card provides eight intermediate or short range SONET/SDH OC-3 ports compliant with ITU-T G.707, ITU-T G.957, and Telcordia GR-253-CORE. Each port operates at 155.52 Mbps over a single-mode fiber span.
-
Chapter 4 Optical Cards 4.3.1 OC3 IR/STM1 SH 1310-8 Card-Level Indicators You can install the OC3 IR/STM1 SH 1310-8 card in Slots 1 to 4 and 14 to 17. The card can be provisioned as part of a path protection or an ADM configuration. Each interface features a 1310-nm laser and contains a transmit and receive connector (labeled) on the card faceplate. The card uses LC connectors on the faceplate that are angled downward 12.5 degrees.
-
Chapter 4 Optical Cards 4.4 OC12 IR/STM4 SH 1310 Card The OC12 IR/STM4 SH 1310 card provides one intermediate or short range SONET OC-12 port compliant with ITU-T G.707, ITU-T G.957, and Telcordia GR-253-CORE. The port operates at 622.08 Mbps over a single-mode fiber span. The card supports VT, nonconcatenated (STS-1), or concatenated (STS-3c, STS-6c, or STS-12c) payloads. Figure 4-3 shows the OC12 IR/STM4 SH 1310 faceplate and a block diagram of the card.
-
Chapter 4 Optical Cards 4.4.1 OC12 IR/STM4 SH 1310 Card-Level Indicators The OC12 IR/STM4 SH 1310 detects LOS, LOF, LOP, AIS-L, and RDI-L conditions. Refer to the Cisco ONS 15454 Troubleshooting Guide for a description of these conditions. The card also counts section and line BIT errors. To enable APS, the OC12 IR/STM4 SH 1310 card extracts the K1 and K2 bytes from the SONET overhead to perform appropriate protection switches.
-
Chapter 4 Optical Cards 4.5 OC12 LR/STM4 LH 1310 Card Warning Note The laser is on when the optical card is booted. The port does not have to be in service for the laser to be on. Statement 293 The OC12 LR 1310 and OC12 LR/STM4 LH 1310 cards are functionally the same.
-
Chapter 4 Optical Cards 4.5.1 OC12 LR/STM4 LH 1310 Card-Level Indicators 4.5.1 OC12 LR/STM4 LH 1310 Card-Level Indicators Table 4-6 describes the three card-level LEDs on the OC12 LR/STM4 LH 1310 card. Table 4-6 OC12 LR/STM4 LH 1310 Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready. Replace the card if the red FAIL LED persists.
-
Chapter 4 Optical Cards 4.6.1 OC12 LR/STM4 LH 1550 Card-Level Indicators Figure 4-5 OC12 LR/STM4 LH 1550 Faceplate and Block Diagram OC12LR STM4LH 1550 FAIL ACT SF STS-12 Tx 1 Rx OC-12 Mux/ Demux Optical Transceiver Flash STS-12 BTC ASIC RAM Main SCI uP bus Protect SCI B a c k p l a n e 61355 uP 33678 12931 You can install the OC12 LR/STM4 LH 1550 card in Slots 1 to 4 and 14 to 17. The OC12 LR/STM4 LH 1550 can be provisioned as part of a two-fiber BLSR, path protection, or linear ADM.
-
Chapter 4 Optical Cards 4.6.2 OC12 LR/STM4 LH 1550 Port-Level Indicators Table 4-7 OC12 LR/STM4 LH 1550 Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready. Replace the card if the red FAIL LED persists. Green/Amber ACT LED The green ACT LED indicates that the card is operational and ready to carry traffic. The amber ACT LED indicates that the card is part of an active ring switch (BLSR).
-
Chapter 4 Optical Cards 4.
-
Chapter 4 Optical Cards 4.7.1 OC12 IR/STM4 SH 1310-4 Card-Level Indicators 4.7.1 OC12 IR/STM4 SH 1310-4 Card-Level Indicators Table 4-8 describes the three card-level LEDs on the OC12 IR/STM4 SH 1310-4 card. Table 4-8 OC12 IR/STM4 SH 1310-4 Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready. Replace the card if the red FAIL LED persists.
-
Chapter 4 Optical Cards 4.8.1 OC48 IR 1310 Card-Level Indicators Figure 4-7 OC48 IR 1310 Faceplate and Block Diagram OC48 IR 1310 FAIL ACT SF Tx 1 OC-48 Rx Optical Transceiver Flash Mux/ Demux RAM B a c k Main SCI p l a Protect SCI n e STS-48 BTC ASIC uP bus 61356 uP 33678 12931 You can install the OC48 IR 1310 card in Slots 5, 6, 12, and 13, and provision the card as a drop or span card in a two-fiber or four-fiber BLSR, path protection, or in an ADM (linear) configuration.
-
Chapter 4 Optical Cards 4.8.2 OC48 IR 1310 Port-Level Indicators Table 4-9 OC48 IR 1310 Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready. Replace the card if the red FAIL LED persists. Green/Amber ACT LED The green ACT LED indicates that the card is carrying traffic or is traffic-ready. The amber ACT LED indicates that the card is part of an active ring switch (BLSR).
-
Chapter 4 Optical Cards 4.9.1 OC48 LR 1550 Card-Level Indicators Figure 4-8 OC48 LR 1550 Faceplate and Block Diagram OC48 LR 1550 FAIL ACT SF Tx 1 Rx OC-48 Optical Transceiver Flash Mux/ Demux RAM uP bus B a c k Main SCI p l a Protect SCI n e STS-48 BTC ASIC 61359 uP 33678 12931 You can install OC48 LR 1550 cards in Slots 5, 6, 12, and 13 and provision the card as a drop or span card in a two-fiber or four-fiber BLSR, path protection, or ADM (linear) configuration.
-
Chapter 4 Optical Cards 4.9.2 OC48 LR 1550 Port-Level Indicators Table 4-10 OC48 LR 1550 Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready. Replace the card if the red FAIL LED persists. Green/Amber ACT LED The green ACT LED indicates that the card is carrying traffic or is traffic-ready. The amber ACT LED indicates that the card is part of an active ring switch (BLSR).
-
Chapter 4 Optical Cards 4.10.
-
Chapter 4 Optical Cards 4.10.2 OC48 IR/STM16 SH AS 1310 Port-Level Indicators Table 4-11 OC48 IR/STM16 SH AS 1310 Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready. Replace the card if the red FAIL LED persists. Green/Amber ACT LED The green ACT LED indicates that the card is carrying traffic or is traffic-ready. The amber ACT LED indicates that the card is part of an active ring switch (BLSR).
-
Chapter 4 Optical Cards 4.11.
-
Chapter 4 Optical Cards 4.11.2 OC48 LR/STM16 LH AS 1550 Port-Level Indicators Table 4-12 OC48 LR/STM16 LH AS 1550 Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready. Replace the card if the red FAIL LED persists. Green/Amber ACT LED The green ACT LED indicates that the card is carrying traffic or is traffic-ready. The amber ACT LED indicates that the card is part of an active ring switch (BLSR).
-
Chapter 4 Optical Cards 4.12 OC48 ELR/STM16 EH 100 GHz Cards Figure 4-11 OC48 ELR/STM16 EH 100 GHz Faceplate and Block Diagram OC48ELR STM16EH 100GHz 1560.61 FAIL ACT/STBY SF TX 1 RX OC-48 Optical Transceiver Flash Mux/ Demux RAM uP bus B a c k Main SCI p l a Protect SCI n e STS-48 BTC ASIC 61613 uP Nineteen of the cards operate in the blue band with spacing of 100 GHz on the ITU grid (1528.77 nm, 1530.33 nm, 1531.12 nm, 1531.90 nm, 1532.68 nm, 1533.47 nm, 1534.25 nm, 1535.04 nm, 1535.
-
Chapter 4 Optical Cards 4.12.1 OC48 ELR 100 GHz Card-Level Indicators ONS 15216 100-GHz filters, the link budget is reduced by the insertion loss of the filters plus an additional 2-dB power penalty. The wavelength stability of the OC48 ELR/STM16 EH 100 GHz cards is +/– 0.12 nm for the life of the product and over the full range of operating temperatures. Each interface contains a transmitter and receiver. The OC48 ELR/STM16 EH 100 GHz cards detect LOS, LOF, LOP, and AIS-L conditions.
-
Chapter 4 Optical Cards 4.13 OC48 ELR 200 GHz Cards Figure 4-12 OC48 ELR 200 GHz Faceplate and Block Diagram OC48 ELR 1530.33 FAIL ACT/STBY SF TX 1 RX OC-48 Optical Transceiver Flash Mux/ Demux RAM uP bus B a c k Main SCI p l a Protect SCI n e STS-48 BTC ASIC 61360 uP Nine of the cards operate in the blue band with spacing of 200 GHz on the ITU grid (1530.33 nm, 1531.90 nm, 1533.47 nm, 1535.04 nm, 1536.61 nm, 1538.19 nm, 1539.77 nm, 1541.35 nm, and 1542.94 nm).
-
Chapter 4 Optical Cards 4.13.1 OC48 ELR 200 GHz Card-Level Indicators The OC48 ELR 200 GHz cards support extended long-reach applications in conjunction with optical amplification. Using electro-absorption technology, the OC48 DWDM cards provide a solution at the lower extended long-reach distances. The OC48 ELR 200 GHz interface features a 1550-nm laser and contains a transmit and receive connector (labeled) on the card faceplate.
-
Chapter 4 Optical Cards 4.14.1 OC192 SR/STM64 IO 1310 Card-Level Indicators Warning The laser is on when the optical card is booted. The port does not have to be in service for the laser to be on. Statement 293 Figure 4-13 shows the OC192 SR/STM64 IO 1310 faceplate and block diagram.
-
Chapter 4 Optical Cards 4.14.2 OC192 SR/STM64 IO 1310 Port-Level Indicators Table 4-15 OC192 SR/STM64 IO 1310 Card-Level Indicators Card-Level LED Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready. This LED is on during reset. The FAIL LED flashes during the boot process. Replace the card if the red FAIL LED persists. ACT/STBY LED If the ACT/STBY LED is green, the card is operational and ready to carry traffic.
-
Chapter 4 Optical Cards 4.15.
-
Chapter 4 Optical Cards 4.15.2 OC192 IR/STM64 SH 1550 Port-Level Indicators Table 4-16 OC192 IR/STM64 SH 1550 Card-Level Indicators Card-Level LED Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready. This LED is on during reset. The FAIL LED flashes during the boot process. Replace the card if the red FAIL LED persists. ACT/STBY LED If the ACT/STBY LED is green, the card is operational and ready to carry traffic.
-
Chapter 4 Optical Cards 4.16 OC192 LR/STM64 LH 1550 Card Note You can differentiate this OC-192/STM-64 card (15454-OC192-LR2, 15454E-L64.2-1) from the OC-192/STM-64 card with the product ID 15454-OC192LR1550 by looking at the faceplate. This card does not have a laser on/off switch. Figure 4-15 shows the OC192 LR/STM64 LH 1550 (15454-OC192LR1550) faceplate and a block diagram of the card.
-
Chapter 4 Optical Cards 4.16 OC192 LR/STM64 LH 1550 Card Figure 4-16 Enlarged Section of the OC192 LR/STM64 LH 1550 (15454-OC192LR1550) Faceplate TX DANGER - INVISIBLE LASER RADIATION MAY BE EMITTED FROM THE END OF UNTERMINATED FIBER CABLE OR CONNECTOR. DO NOT STARE INTO BEAM OR VIEW DIRECTLY WITH OPTICAL INSTRUMENTS. RX ! Class 1M (IEC) Class 1 (CDRH) 67465 MAX INPUT POWER LEVEL - 10dBm Figure 4-17 shows the OC192 LR/STM64 LH 1550 (15454-OC192-LR2) faceplate and a block diagram of the card.
-
Chapter 4 Optical Cards 4.16 OC192 LR/STM64 LH 1550 Card Figure 4-17 OC192 LR/STM64 LH 1550 (15454-OC192-LR2) Faceplate and Block Diagram 1550 FAIL ACT/STBY SF OC-192/STM-64 STS Optical transceiver Demux CDR Mux SCL BTC ASIC TX 1 OC-192/STM-64 RX Optical transceiver Mux CK Mpy STS Mux SCL RX ! B a c k p l a n e MAX INPUT POWER LEVEL -7 dBm SRAM Flash Processor 115222 ADC x 8 Figure 4-18 shows an enlarged view of the faceplate warning on 15454-OC192LR1550.
-
Chapter 4 Optical Cards 4.16 OC192 LR/STM64 LH 1550 Card Figure 4-18 Enlarged Section of the OC192 LR/STM64 LH 1550 (15454-OC192-LR2) Faceplate 1550 FAIL ACT/STBY SF RX ! MAX INPUT POWER LEVEL -7 dBm TX 1 RX RX ! DATED JULY 26, 2001 LASER NOTICE No.50, AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO 115226 DATED JULY 26, 2001 LASER NOTICE No.50, AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO COMPLIES WITH 21 CFR 1040.10 COMPLIES WITH 21 CFR 1040.
-
Chapter 4 Optical Cards 4.16.1 OC192 LR/STM64 LH 1550 Card-Level Indicators The card port features a 1550-nm laser and contains a transmit and receive connector (labeled) on the card faceplate.The card uses a dual SC connector for optical cable termination. The card supports 1+1 unidirectional and bidirectional facility protection. It also supports 1:1 protection in four-fiber BLSR applications where both span switching and ring switching might occur.
-
Chapter 4 Optical Cards 4.17 OC192 LR/STM64 LH ITU 15xx.xx Card Sixteen distinct OC-192/STM-64 ITU 100 GHz DWDM cards comprise the ONS 15454 DWDM channel plan. Each OC192 LR/STM64 LH ITU 15xx.xx card provides one long-reach STM-64/OC-192 port per card, compliant with ITU-T G.707, ITU-T G.957, and Telcordia GR-253-CORE (except minimum and maximum transmit power, and minimum receive power). The port operates at 9.
-
Chapter 4 Optical Cards 4.17.1 OC192 LR/STM64 LH ITU 15xx.xx Card-Level Indicators Figure 4-20 OC192 LR/STM64 LH ITU 15xx.xx Block Diagram STM-64/ OC-192 STM-64 / OC192 Optical transceiver Demux CDR Demux SCL BTC ASIC STM-64 / OC192 Optical transceiver Mux CK Mpy SRAM Flash SCL B a c k p l a n e Processor 63121 ADC x 8 Mux STM-64/ OC-192 Note You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the OC192 LR/STM64 LH 15xx.xx card in a loopback.
-
Chapter 4 Optical Cards 4.17.2 OC192 LR/STM64 LH ITU 15xx.xx Port-Level Indicators Table 4-18 OC192 LR/STM64 LH ITU 15xx.xx Card-Level Indicators Card-Level LED Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready. This LED is on during reset. The FAIL LED flashes during the boot process. Replace the card if the red FAIL LED persists. ACT/STBY LED If the ACT/STBY LED is green, the card is operational and ready to carry traffic.
-
Chapter 4 Optical Cards 4.18.1 Slot Compatibility by Cross-Connect Card 15454_MRC-12 Card Faceplate and Block Diagram OC-3/12/48 (STM-1/4/16) COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE No. 50, DATED JULY 26, 2001 OC-3/12 (STM-1/4/) OC-3/12 (STM-1/4) OC-3/12/48 (STM-1/4/16) OC-3/12 (STM-1/4) OC-3/12 (STM-1/4) OC-3/12/48 (STM-1/4/16) OC-3/12 (STM-1/4) OC-3/12 (STM-1/4) OC-3/12/48 (STM-1/4/16) OC-3/12 (STM-1/4) OC-3/12 (STM-1/4) Main SCL Intfc.
-
Chapter 4 Optical Cards 4.18.2 Ports and Line Rates The maximum bandwidth of the 15454_MRC-12 card is determined by the cross-connect card, as shown in Table 4-19. Table 4-19 Maximum Bandwidth by Shelf Slot for the 15454_MRC-12 in Different Cross-Connect Configurations XC Card Type Maximum Bandwidth in Slots 1 through 4 Maximum Bandwidth and 14 through 17 in Slots 5, 6, 12, or 13 XCVT OC-12 OC-48 XC10G/XC-VXC-10G OC-48 OC-192 4.18.
-
Chapter 4 Optical Cards 4.18.2 Ports and Line Rates – If Port 10 is used as an OC-3, Ports 9, 11, and 12 can be used as an OC-3 or OC-12. – Any port can be used as an OC-12 or OC-3, as long as all of the above rules are followed. Table 4-20 shows the 15454_MRC-12 port availability and line rate for each port, based on total available bandwidth. To use the table, go to the rows for the bandwidth that you have available, as determined in Table 4-19.
-
Chapter 4 Optical Cards 4.18.
-
Chapter 4 Optical Cards 4.18.4 15454_MRC-12 Port-Level Indicators Table 4-21 15454_MRC-12 Card-Level Indicators Card-Level LED Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready. This LED is on during reset. The FAIL LED flashes during the boot process. Replace the card if the red FAIL LED persists. ACT/STBY LED If the ACT/STBY LED is green, the card is operational and ready to carry traffic.
-
Chapter 4 Optical Cards 4.19 MRC-2.5G-4 Multirate Card Note 1+1 protection must be configured between the same equipment type, using the same port number and line rate. Note Longer distances are possible in an amplified system using dispersion compensation. Figure 4-22 shows the MRC-2.5G-4 faceplate and block diagram. Figure 4-22 MRC-2.5G-4 Card Faceplate and Block Diagram Main SCL Intfc. Protect SCL Intfc.
-
Chapter 4 Optical Cards 4.19.1 Slot Compatibility by Cross-Connect Card 4.19.1 Slot Compatibility by Cross-Connect Card You can install MRC-2.5G-4 cards in Slots 1 through 6 and 12 through 17 with an XCVT, XC10G, or XC-VXC-10G. Note The MRC-2.5G-4 card supports an errorless software-initiated cross-connect card switch when used in a shelf equipped with XC-VXC-10G and TCC2/TCC2P cards. The maximum bandwidth of the MRC-2.5G-4 card is determined by the cross-connect card, as shown in Table 4-22.
-
Chapter 4 Optical Cards 4.19.3 MRC-2.5G-4 Card-Level Indicators Table 4-23 shows the 15454_MRC-4 port availability and line rate for each port, based on total available bandwidth. To use the table, go to the rows for the bandwidth that you have available, as determined in Table 4-22. Each row indicates what line rate can be provisioned for each port (identified in the MCR-4 Port Number row). The Ports Used column shows the total number of ports that can be used with each bandwidth scheme.
-
Chapter 4 Optical Cards 4.20 OC192SR1/STM64IO Short Reach and OC192/STM64 Any Reach Cards 4.20 OC192SR1/STM64IO Short Reach and OC192/STM64 Any Reach Cards Note For hardware specifications, see the “A.6.19 OC192SR1/STM64IO Short Reach Card Specifications” section on page A-47 and the “A.6.20 OC192/STM64 Any Reach Card Specifications” section on page A-47. See Table 4-2 on page 4-5 for optical card compatibility.
-
Chapter 4 Optical Cards 4.
-
Chapter 4 Optical Cards 4.20.1 OC192SR1/STM64IO Short Reach and OC192/STM64 Any Reach Card-Level Indicators 4.20.1 OC192SR1/STM64IO Short Reach and OC192/STM64 Any Reach Card-Level Indicators Table 4-25 describes the three card-level LEDs on the OC192SR1/STM64IO Short Reach and OC192/STM64 Any Reach cards. Table 4-25 OC192SR1/STM64IO Short Reach and OC192/STM64 Any Reach Card-Level Indicators Card-Level LED Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready.
-
Chapter 4 Optical Cards 4.21.1 Compatibility by Card Table 4-26 SFP and XFP Card Compatibility Compatible SFPs and XFPs (Cisco Product ID) Cisco Top Assembly Number (TAN) 15454_MRC-12 and MRC-2.5G-4 (ONS 15454 SONET/SDH) ONS-SC-2G-28.7=1 through ONS-SC-2G-60.
-
Chapter 4 Optical Cards 4.21.2 SFP Description Table 4-27 LED Based SFPs SFPs (Cisco Product ID) Cisco Top Assembly Number (TAN) ONS-SI-155-SR-MM SFP 10-2279-01 ONS-SI-622-SR-MM SFP 10-2280-01 ONS-SE-100-FX 10-2212-01 ONS-SI-100-FX 10-2350-01 4.21.2 SFP Description SFPs are integrated fiber optic transceivers that provide high-speed serial links from a port or slot to the network. Various latching mechanisms can be utilized on the modules.
-
Chapter 4 Optical Cards 4.21.3 XFP Description • Height 0.03 in. (8.5 mm) • Width 0.53 in. (13.4 mm) • Depth 2.22 in. (56.5 mm) SFP temperature ranges are: • COM—Commercial operating temperature range: 23 to 158 degrees Fahrenheit (–5 to 70 degrees Celsius) • EXT—Extended operating temperature range: 23 to185 degrees Fahrenheit (–5to 85 degrees Celsius) • IND—Industrial operating temperature range: –40 to 185 degrees Fahrenheit (–40 to 85 degrees Celsius) 4.21.
-
Chapter 4 Optical Cards 4.21.4 PPM Provisioning • Width 0.72 in. (18.3 mm) • Depth 3.1 in. (78 mm) XFP temperature ranges are: • COM—Commercial operating temperature range: 23 to 158 degrees Fahrenheit (–5 to 70 degrees Celsius) • EXT—Extended operating temperature range: 23 to185 degrees Fahrenheit (–5to 85 degrees Celsius) • IND—Industrial operating temperature range: –40 to 185 degrees Fahrenheit (–40 to 85 degrees Celsius) 4.21.
-
CH A P T E R 5 Ethernet Cards 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.
-
Chapter 5 Ethernet Cards 5.1 Ethernet Card Overview 5.1 Ethernet Card Overview The card overview section summarizes the Ethernet card functions and provides the software compatibility for each card. Note Each card is marked with a symbol that corresponds to a slot (or slots) on the ONS 15454 shelf assembly. The cards are then installed into slots displaying the same symbols. Refer to the Cisco ONS 15454 Procedure Guide for a list of slots and symbols. 5.1.
-
Chapter 5 Ethernet Cards 5.1.2 Card Compatibility Table 5-1 Ethernet Cards for the ONS 15454 (continued) Card Port Description For Additional Information... ML-MR-10 The ML-MR-10 card is a ten-port multilayer Ethernet card. The Ethernet ports support speeds of 10 Mbps, 100 Mbps, or 1000 Mbps through pluggable SFPs. See the “5.11 ML-MR-10 Card” section on page 5-25. CE-100T-8 The CE-100T-8 card provides eight IEEE-compliant, 10/100-Mbps ports.
-
Chapter 5 Ethernet Cards 5.2 E100T-12 Card Table 5-2 Ethernet Card Software Compatibility (continued) Ethernet Cards R2.2.2 R3.0.1 R3.1 R3.2 R3.3 R3.4 R4.0 R4.1 R4.5 R4.6 R4.7 R5.0 R6.0 R7.0 R7.2 R8.0 R8.5 CE-1000-4 — — — — — — — — — — — — — Yes Yes Yes Yes CE-MR-10 — — — — — — — — — — — — — — — — Yes 5.2 E100T-12 Card Note For hardware specifications, see the “A.7.1 E100T-12 Card Specifications” section on page A-48.
-
Chapter 5 Ethernet Cards 5.2.
-
Chapter 5 Ethernet Cards 5.2.2 E100T-12 Card-Level Indicators Note When making an STS-12c Ethernet circuit, the E-Series cards must be configured as single-card EtherSwitch. 5.2.2 E100T-12 Card-Level Indicators The E100T-12 card faceplate has two card-level LED indicators, described in Table 5-3.
-
Chapter 5 Ethernet Cards 5.3 E100T-G Card The ONS 15454 uses E100T-G cards for Ethernet (10 Mbps) and Fast Ethernet (100 Mbps). Each card provides 12 switched, IEEE 802.3-compliant, 10/100BaseT Ethernet ports that can independently detect the speed of an attached device (autosense) and automatically connect at the appropriate speed. The ports autoconfigure to operate at either half or full duplex and determine whether to enable or disable flow control. You can also configure Ethernet ports manually.
-
Chapter 5 Ethernet Cards 5.3.1 Slot Compatibility 5.3.1 Slot Compatibility You can install the E100T-G card in Slots 1 to 6 and 12 to 17. Multiple E-Series Ethernet cards installed in an ONS 15454 can act independently or as a single Ethernet switch. You can create logical SONET ports by provisioning a number of STS channels to the packet switch entity within the ONS 15454. Logical ports can be created with a bandwidth granularity of STS-1.
-
Chapter 5 Ethernet Cards 5.4 E1000-2 Card 5.4 E1000-2 Card Note For hardware specifications, see the “A.7.3 E1000-2 Card Specifications” section on page A-49. The ONS 15454 uses E1000-2 cards for Gigabit Ethernet (1000 Mbps). The E1000-2 card provides two IEEE-compliant, 1000-Mbps ports for high-capacity customer LAN interconnections. Each port supports full-duplex operation. The E1000-2 card uses GBIC modular receptacles for the optical interfaces. For details, see the “5.
-
Chapter 5 Ethernet Cards 5.4.1 Slot Compatibility Each E1000-2 card supports standards-based, Layer 2 Ethernet switching between its Ethernet interfaces and SONET interfaces on the ONS 15454. The IEEE 802.1Q VLAN tag logically isolates traffic (typically subscribers). Multiple E-Series Ethernet cards installed in an ONS 15454 can act together as a single switching entity or as independent single switches supporting a variety of SONET port configurations.
-
Chapter 5 Ethernet Cards 5.4.4 Cross-Connect Compatibility Table 5-8 E1000-2 Port-Level Indicators LED State Description Amber The port is active (transmitting and receiving data). Solid green The link is established. Off The connection is inactive, or traffic is unidirectional. 5.4.4 Cross-Connect Compatibility The E1000-2 is compatible with XCVT cards. The XC10G and XC-VXC-10G cards require the E1000-2-G card. 5.5 E1000-2-G Card Note For hardware specifications, see the “A.7.
-
Chapter 5 Ethernet Cards 5.
-
Chapter 5 Ethernet Cards 5.5.1 E1000-2-G Card-Level Indicators You can create logical SONET ports by provisioning STS channels to the packet switch entity within the ONS 15454. Logical ports can be created with a bandwidth granularity of STS-1. The ONS 15454 supports STS-1, STS-3c, STS-6c, or STS-12c circuit sizes. Note When making an STS-12c Ethernet circuit, the E-Series cards must be configured as a single-card EtherSwitch. 5.5.
-
Chapter 5 Ethernet Cards 5.6 G1000-4 Card 5.6 G1000-4 Card The G1000-4 card requires the XC10G card. The ONS 15454 uses G1000-4 cards for Gigabit Ethernet (1000 Mbps). The G1000-4 card provides four ports of IEEE-compliant, 1000-Mbps interfaces. Each port supports full-duplex operation for a maximum bandwidth of OC-48 on each card. The G1000-4 card uses GBIC modular receptacles for the optical interfaces. For details, see the “5.15 Ethernet Card GBICs and SFPs” section on page 5-36.
-
Chapter 5 Ethernet Cards 5.6.1 STS-24c Restriction switches (such as 1+1 automatic protection switching [APS], path protection configuration, or bidirectional line switch ring [BLSR]). Full provisioning support is possible through Cisco Transport Controller (CTC), Transaction Language One (TL1), or Cisco Transport Manager (CTM). The circuit sizes supported are STS-1, STS-3c, STS-6c, STS-9c, STS-12c, STS-24c, and STS-48c. 5.6.
-
Chapter 5 Ethernet Cards 5.6.4 Slot Compatibility Table 5-12 G1000-4 Port-Level Indicators Port-Level LED Status Description Off No link exists to the Ethernet port. Steady amber A link exists to the Ethernet port, but traffic flow is inhibited. For example, an unconfigured circuit, an error on line, or a nonenabled port might inhibit traffic flow. Solid green A link exists to the Ethernet port, but no traffic is carried on the port.
-
Chapter 5 Ethernet Cards 5.7.
-
Chapter 5 Ethernet Cards 5.7.2 G1K-4 Compatibility If STS-24c circuits are not being dropped on the card, the full 48 STSs bandwidth can be used with no restrictions (for example, using either a single STS-48c or 4 STS-12c circuits). Note The STS-24c restriction only applies when a single STS-24c circuit is dropped; therefore, you can easily minimize the impact of this restriction. Group the STS-24c circuits together on a card separate from circuits of other sizes.
-
Chapter 5 Ethernet Cards 5.8 ML100T-12 Card Table 5-14 G1K-4 Port-Level Indicators (continued) Port-Level LED Status Description Solid green A link exists to the Ethernet port, but no traffic is carried on the port. Flashing green A link exists to the Ethernet port, and traffic is carried on the port. The LED flash rate reflects the traffic rate for the port. 5.8 ML100T-12 Card Note For hardware specifications, see the “A.7.9 ML100T-12 Card Specifications” section on page A-51.
-
Chapter 5 Ethernet Cards 5.8.1 ML100T-12 Card-Level Indicators Figure 5-7 ML100T-12 Faceplate and Block Diagram ML100T 12 BPIA Main Rx ACT Packet Buffer 6MB FAIL 0 SMII Packet Buffer 6MB Packet Buffer 4MB BPIA Protect Rx RGGI RGGI 1 4 2 4xMag. 2 3 12 x RJ45 4 2 4 2 4xMag. Octal PHY 6 port 0 port port 1 2 port A DOS FPGA 2 BTC192 5 6 6 4 4xMag.
-
Chapter 5 Ethernet Cards 5.8.2 ML100T-12 Port-Level Indicators Table 5-15 ML100T-12 Card-Level Indicators Card-Level LEDs Description FAIL LED (Red) The red FAIL LED indicates that the card processor is not ready or that a catastrophic software failure occurred on the ML100T-12 card. As part of the boot sequence, the FAIL LED is turned on until the software deems the card operational. ACT LED (Green) The green ACT LED provides the operational status of the ML100T-12.
-
Chapter 5 Ethernet Cards 5.9.1 ML100X-8 Card-Level Indicators Figure 5-8 ML100X-8 Faceplate and Block Diagram ML 100X8 FAIL ACT Tx 0 Rx Tx 2 Rx Tx 3 Rx SFP SFP SFP SFP SFP Tx 4 Rx Tx 5 Rx PHY Network Processor Unit SFP SFP SONET Framer B a c k p l a n e SFP Tx 6 Rx TCAM 131786 Tx 1 Rx Packet Memory Tx 7 Rx The card features two virtual packet over SONET (POS) ports with a maximum combined bandwidth of STS-48.
-
Chapter 5 Ethernet Cards 5.9.2 ML100X-8 Port-Level Indicators Table 5-17 ML100X-8 Card-Level Indicators Card-Level LEDs Description FAIL LED (Red) The red FAIL LED indicates that the card processor is not ready or that a catastrophic software failure occurred on the ML100-FX card. As part of the boot sequence, the FAIL LED is turned on until the software deems the card operational. ACT LED (Green) The green ACT LED provides the operational status of the ML100-FX.
-
Chapter 5 Ethernet Cards 5.10.
-
Chapter 5 Ethernet Cards 5.10.2 ML1000-2 Port-Level Indicators Table 5-19 ML1000-2 Card-Level Indicators Card-Level LEDs Description SF LED (Red) The red FAIL LED indicates that the card processor is not ready or that a catastrophic software failure occurred on the ML1000-2 card. As part of the boot sequence, the FAIL LED is turned on until the software deems the card operational. ACT LED (Green) The green ACT LED provides the operational status of the ML1000-2.
-
Chapter 5 Ethernet Cards 5.11 ML-MR-10 Card To configure a ML-MR-10 card SONET STS circuit, refer to the “Create Circuits and Tunnels” chapter in the Cisco ONS 15454 Procedure Guide. Cisco IOS is used to provision the Layer 2 functions of the card. The ML-MR-10 card provides management for Layer 1 operations through CTC. You can use CTM for Layer 1 and Layer 2 monitoring and fault detection, and TL1 supports card inventory and equipment alarming.
-
Chapter 5 Ethernet Cards 5.11.1 ML-MR-10 Card-Level Indicators The ML-MR-10 card supports an Ethernet Virtual Connection (EVC), which is an instance of an association of two or more user network interfaces (UNI) for Ethernet services. For more information on EVC, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide. 5.11.1 ML-MR-10 Card-Level Indicators The ML-MR-10 card faceplate has two card-level LED indicators, described in Table 5-25.
-
Chapter 5 Ethernet Cards 5.12 CE-100T-8 Card 5.12 CE-100T-8 Card Note For hardware specifications, see the “A.7.6 CE-100T-8 Card Specifications” section on page A-50. The CE-100T-8 card provides eight RJ-45 10/100 Mbps Ethernet ports and an RJ-45 console port on the card faceplate. The CE-100T-8 card provides mapping of 10/100 Mbps Ethernet traffic into SONET STS-12 payloads, making use of low-order (VT1.
-
Chapter 5 Ethernet Cards 5.12 CE-100T-8 Card Figure 5-11 CE-100T-8 Faceplate and Block Diagram CE100T 8 Packet Buffer 3x0.
-
Chapter 5 Ethernet Cards 5.12.1 CE-100T-8 Card-Level Indicators For information on the CE-100T-8 QoS features, refer to the “CE-100T-8 Operations” chapter of the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide. 5.12.1 CE-100T-8 Card-Level Indicators The CE-100T-8 card faceplate has two card-level LED indicators, described in Table 5-23.
-
Chapter 5 Ethernet Cards 5.13 CE-1000-4 Card The CE-1000-4 card uses pluggable GBICs to transport Ethernet traffic over a SONET network. The CE-1000-4 provides four IEEE 802.3-compliant, 1000-Mbps Gigabit Ethernet ports at the ingress. At the egress, the CE-1000-4 card provides an integrated Ethernet over SONET mapper with four virtual ports to transfer Ethernet packets over a SONET network.
-
Chapter 5 Ethernet Cards 5.13 CE-1000-4 Card Note This is possible with CTC as it assumes the force command mode by default. However, to put members into or out of service using TL1, the force command mode must be set. Cross-connects can be added or removed from VCGs using CTC or TL1. This is service affecting as long as the VCG size (TXCOUNT) is not realigned with the loss of connections.
-
Chapter 5 Ethernet Cards 5.13.1 CE-1000-4 Card-Level Indicators 5.13.1 CE-1000-4 Card-Level Indicators The CE-1000-4 card faceplate has two card-level LED indicators, described in Table 5-25. Table 5-25 Note CE-1000-4 Card-Level Indicators Card-Level LEDs Description FAIL LED (Red) The red FAIL LED indicates that the card processor is not ready or that a catastrophic software failure occurred on the CE-1000-4 card.
-
Chapter 5 Ethernet Cards 5.14 CE-MR-10 Card 5.14 CE-MR-10 Card Note For hardware specifications, see the “A.7.7 CE-MR-10 Card Specifications” section on page A-51. The CE-MR-10 card provides ten IEEE 802.3-compliant 10/100/1000-Mbps Gigabit Ethernet ports at the ingress. At the egress, the CE-MR-10 card provides an integrated Ethernet-over-SONET mapper with ten virtual ports to transfer Ethernet packets over a SONET network.
-
Chapter 5 Ethernet Cards 5.14.
-
Chapter 5 Ethernet Cards 5.14.2 CE-MR-10 Port-Level Indicators Table 5-27 CE-MR-10 Card-Level Indicators Card-Level LEDs Description FAIL LED (Red) The red FAIL LED indicates that the card processor is not ready or that a catastrophic software failure occurred on the card. As part of the boot sequence, the FAIL LED is turned on until the software deems the card operational. ACT LED (Green) The green ACT LED provides the operational status of the CE-1000-4 card.
-
Chapter 5 Ethernet Cards 5.15.1 Compatibility by Card For all Ethernet cards, the type of GBIC or SFP plugged into the card is displayed in CTC and TL1. Cisco offers SFPs and GBICs as separate orderable products. 5.15.1 Compatibility by Card Table 5-29 shows the GBICs for the E1000-2-G, G1K-4, or CE-1000-4 cards. Note The GBICs are very similar in appearance. Check the GBIC label carefully before installing it.
-
Chapter 5 Ethernet Cards 5.15.
-
Chapter 5 Ethernet Cards 5.15.3 G1K-4 DWDM and CWDM GBICs Figure 5-14 GBICs with Clips (left) and with a Handle (right) Clip Handle Receiver Transmitter 51178 Receiver Transmitter 5.15.3 G1K-4 DWDM and CWDM GBICs DWDM (15454-GBIC-xx.x, 15454E-GBIC-xx.x) and CWDM (15454-GBIC-xxxx, 15454E-GBIC-xxxx) GBICs operate in an ONS 15454 G-Series card when the card is configured in Gigabit Ethernet Transponding mode or in Ethernet over SONET mode.
-
Chapter 5 Ethernet Cards 5.15.3 G1K-4 DWDM and CWDM GBICs Table 5-32 Blue Band Supported Wavelengths for DWDM GBICs 1530.33 nm 1531.12 nm 1531.90 nm 1532.68 nm 1534.25 nm 1535.04 nm 1535.82 nm 1536.61 nm 1538.19 nm 1538.98 nm 1539.77 nm 1540.56 nm 1542.14 nm 1542.94 nm 1543.73 nm 1544.53 nm Red Band 1546.12 nm 1546.92 nm 1547.72 nm 1548.51 nm 1550.12 nm 1550.92 nm 1551.72 nm 1552.52 nm 1554.13 nm 1554.94 nm 1555.75 nm 1556.55 nm 1558.17 nm 1558.98 nm 1559.79 nm 1560.
-
Chapter 5 Ethernet Cards 5.15.4 SFP Description Figure 5-16 G-Series with CWDM/DWDM GBICs in Cable Network Conventional GigE signals GigE / GigE / GigE over 's HFC CWDM/DWDM ONS Node Mux only with G-Series Cards with CWDM/DWDM GBICs CWDM/DWDM Demux only QAM 90954 VoD = Lambdas 5.15.4 SFP Description SFPs are integrated fiber-optic transceivers that provide high-speed serial links from a port or slot to the network. Various latching mechanisms can be utilized on the SFP modules.
-
Chapter 5 Ethernet Cards 5.15.4 SFP Description Actuator/Button SFP Figure 5-19 Bail Clasp SFP 63067 63066 Figure 5-18 Cisco ONS 15454 Reference Manual, R8.5.
-
CH A P T E R 6 Storage Access Networking Cards 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.
-
Chapter 6 Storage Access Networking Cards 6.1 FC_MR-4 Card Overview – Dual rate (1G/2G): MM (550 m) and SM (10 km) – Single rate (1G): SX (550 m) and LX (10 km) • SONET/SDH support – Four 1.0625-Gbps FC channels can be mapped into one of the following: SONET containers as small as STS1-1v (subrate) SDH containers as small as VC4-1v (subrate) SONET/SDH containers as small as STS-18c/VC4-6v (full rate) – Four 2.
-
Chapter 6 Storage Access Networking Cards 6.1.1 FC_MR-4 Card-Level Indicators Figure 6-1 FC_MR-4 Faceplate and Block Diagram FC_MR-4 FAIL ACT FLASH SDRAM MPC8250 Decode and Control PLD GBIC OPTICS Rx 1 Tx ACT/LNK Rx 2 GBIC OPTICS SERDES GBIC OPTICS Tx RUDRA FPGA TADM BTC 192 IBPIA ACT/LNK CDR + SONET FRAMER GBIC OPTICS Rx 3 Tx ACT/LNK Rx 4 Tx QDR MEMORY QUICKSILVER VCAT PROCESSOR IBPIA B A C K P L A N E DDR MEMORY 110595 ACT/LNK 6.1.
-
Chapter 6 Storage Access Networking Cards 6.1.2 FC_MR-4 Port-Level Indicators 6.1.2 FC_MR-4 Port-Level Indicators Each FC_MR-4 port has a corresponding ACT/LNK LED. The ACT/LNK LED is solid green if the port is available to carry traffic, is provisioned as in-service, and is in the active mode. The ACT/LNK LED is flashing green if the port is carrying traffic.
-
Chapter 6 Storage Access Networking Cards 6.2.2 Enhanced Card Mode – STS-1-Xv where X is 37 to 48 – STS-3c-Xv where X is 12 to 16 – VC4-Xv where X is 12 to 16 6.2.2 Enhanced Card Mode The features available in enhanced card mode are given in this section. 6.2.2.
-
Chapter 6 Storage Access Networking Cards 6.2.
-
Chapter 6 Storage Access Networking Cards 6.2.3 Link Integrity 6.2.3 Link Integrity The link integrity features are as follows: • Data port disabled if upstream data port is not able to send over SONET/SDH transport • Data port disabled if SONET/SDH transport is errored 6.2.
-
Chapter 6 Storage Access Networking Cards 6.4 FC_MR-4 Card GBICs • Path protection • BLSR • Unprotected • Protection channel access (PCA) The FC_MR-4 payloads can be transported over the following circuit types: Note • STS • STSn • STS-V Virtual Tributary (VT) and VT-V circuits are not supported. The FC_MR-4 card supports VCAT. See the “11.18 Virtual Concatenated Circuits” section on page 11-34 for more information about VCAT circuits. 6.
-
CH A P T E R 7 Card Protection This chapter explains the Cisco ONS 15454 card protection configurations. To provision card protection, refer to the Cisco ONS 15454 Procedure Guide. Chapter topics include: • 7.1 Electrical Card Protection, page 7-1 • 7.2 Electrical Card Protection and the Backplane, page 7-5 • 7.3 OC-N Card Protection, page 7-13 • 7.4 Unprotected Cards, page 7-14 • 7.5 External Switching Commands, page 7-14 7.
-
Chapter 7 Card Protection 7.1.1 1:1 Protection 7.1.1 1:1 Protection In 1:1 protection, a working card is paired with a protect card of the same type. If the working card fails, the traffic from the working card switches to the protect card. You can provision 1:1 to be revertive or nonrevertive. If revertive, traffic automatically reverts to the working card after the failure on the working card is resolved. Figure 7-1 shows an example of the ONS 15454 in a 1:1 protection configuration.
-
Chapter 7 Card Protection 7.1.2 1:N Protection 7.1.2 1:N Protection 1:N protection allows a single electrical card to protect up to five working cards of the same speed. 1:N cards have added circuitry to act as the protect card in a 1:N protection group. Otherwise, the card is identical to the standard card and can serve as a normal working card. The physical DS-1 or DS-3 interfaces on the ONS 15454 backplane use the working card until the working card fails.
-
Chapter 7 Card Protection 7.1.2 1:N Protection Table 7-2 Supported 1:N Protection by Electrical Card (continued) Working Card DS3/EC1-48 Protect Card Protect Group (Maximum) Working Slot Protection Slot DS3/EC1-48 N<2 3 5 1,2 7 6 16 , 17 DS3XM-12 (Transmux) DS3XM-12 (Transmux) N<5 DS3XM-12 (Transmux) DS3XM-12 (Transmux) N<7 (portless9) 8 15 1, 2, 4, 5, 6 3 12, 13, 14, 16, 17 15 1, 2, 4, 5, 6, 12, 13, 3 14, 15, 16, 17 1, 2, 3, 4, 5, 6, 12, 15 13, 14, 16, 17 1.
-
Chapter 7 Card Protection 7.2 Electrical Card Protection and the Backplane • Working cards can sit on either or both sides of the protect card. The following rules apply to portless 1:N protection groups in the ONS 15454: • Working and protect card groups can reside in the same card bank or different card banks (Side A or Side B). • The 1:N protect card can be installed in either Slot 3 or Slot 15 and protect working cards in both card banks.
-
Chapter 7 Card Protection 7.2 Electrical Card Protection and the Backplane Table 7-3 EIA Connectors Per Side Interfaces per Side Standard BNC High-Density BNC MiniBNC SMB UBIC-V and AMP Champ UBIC-H (SCSI) Maximum HD DS-1 interfaces (Tx and Rx) — — — — — 112 Maximum HD DS-3 interfaces (Tx and Rx) — — 96 — — 96 Table 7-4 shows the electrical card protection for each EIA type according to shelf side and slots.
-
Working Working Working Working Working Working Working TCC Working Cross-connect Cross-connect AIC TCC Working Working Working Working Working Working Working Working Working TCC Working Working Cross-connect Cross-connect AIC TCC Working Working Working Working Working Working Working Working TCC Cross-connect Cross-connect AIC TCC Working Working Working High-Density BNC Standard BNC MiniBNC SMB/UBIC/AMP Champ Working Working TCC Cross-connect AIC Cross-connect TCC
-
Chapter 7 Card Protection 7.2 Electrical Card Protection and the Backplane Figure 7-4 shows unprotected high-density electrical card schemes by EIA type. Figure 7-4 Unprotected High-Density Electrical Card Schemes for EIA Types 124963 Working Working TCC Cross-connect AIC Cross-connect TCC Working Working UBIC/MiniBNC Cisco ONS 15454 Reference Manual, R8.5.
-
Chapter 7 Card Protection 7.2 Electrical Card Protection and the Backplane Figure 7-5 shows 1:1 low-density card protection by EIA type.
-
Chapter 7 Card Protection 7.2 Electrical Card Protection and the Backplane Figure 7-6 shows 1:N protection for low-density electrical cards.
-
Chapter 7 Card Protection 7.2.1 Standard BNC Protection Figure 7-7 shows 1:1 high-density card protection by EIA type. Figure 7-7 1:1 Protection Schemes for High-Density Electrical Cards with UBIC or MiniBNC EIA Types 124964 Working Working Protect TCC Cross-connect AIC Cross-connect TCC Protect Working Working UBIC/MiniBNC 7.2.
-
Chapter 7 Card Protection 7.2.3 MiniBNC Protection 7.2.3 MiniBNC Protection When used with the MiniBNC EIA, the ONS 15454 supports unprotected, 1:1, or 1:N (N < 5) electrical card protection for DS-1, DS-3 and EC-1 signals, as outlined in Table 7-1 on page 7-2 and Table 7-2 on page 7-3.
-
Chapter 7 Card Protection 7.3 OC-N Card Protection 7.3 OC-N Card Protection The ONS 15454 provides two optical card protection methods, 1+1 protection and optimized 1+1 protection. This section covers the general concept of optical card protection. Specific optical card protection schemes depend on the optical cards in use. 7.3.1 1+1 Protection Any OC-N card can use 1+1 protection.
-
Chapter 7 Card Protection 7.4 Unprotected Cards Optimized 1+1 is fully compliant with Nippon Telegraph and Telephone Corporation (NTT) specifications. With optimized 1+1 port-to-port protection, ports on the protect card can be assigned to protect the corresponding ports on the working card. The working and protect cards do not have to be installed side by side in the node. A working card must be paired with a protect card of the same type and number of ports.
-
Chapter 7 Card Protection 7.5 External Switching Commands A Force switch has a higher priority than a Manual switch. Lockouts, which prevent traffic from switching to the protect port under any circumstance, can only be applied to protect cards (in 1+1 configurations). Lockouts have the highest priority. In a 1+1 configuration you can also apply a lock on to the working port. A working port with a lock on applied cannot switch traffic to the protect port in the protection group (pair).
-
Chapter 7 Card Protection 7.5 External Switching Commands Cisco ONS 15454 Reference Manual, R8.5.
-
CH A P T E R 8 Cisco Transport Controller Operation This chapter describes Cisco Transport Controller (CTC), the software interface for the Cisco ONS 15454. For CTC set up and login information, refer to the Cisco ONS 15454 Procedure Guide. Chapter topics include: • 8.1 CTC Software Delivery Methods, page 8-1 • 8.2 CTC Installation Overview, page 8-4 • 8.3 PC and UNIX Workstation Requirements, page 8-4 • 8.4 ONS 15454 Connection, page 8-7 • 8.5 CTC Login, page 8-7 • 8.
-
Chapter 8 Cisco Transport Controller Operation 8.1.1 CTC Software Installed on the TCC2/TCC2P Card When you upgrade CTC software, the TCC2/TCC2P cards store the new CTC version as the protect CTC version. When you activate the new CTC software, the TCC2/TCC2P cards store the older CTC version as the protect CTC version, and the newer CTC release becomes the working version.
-
Chapter 8 Cisco Transport Controller Operation 8.1.2 CTC Software Installed on the PC or UNIX Workstation Select the Maintenance > Software tabs in network view to display the software versions installed on all the network nodes (Figure 8-2). Figure 8-2 CTC Software Versions, Network View 159505 Maintenance tab 8.1.
-
Chapter 8 Cisco Transport Controller Operation 8.2 CTC Installation Overview Note Upgrading the CTC software will overwrite your existing software. You must restart CTC after the upgrade is complete. 8.2 CTC Installation Overview To connect to an ONS 15454 using CTC, you enter the ONS 15454 IP address in the URL field of Netscape Navigator or Microsoft Internet Explorer. After connecting to an ONS 15454, the following occurs automatically: 1.
-
Chapter 8 Cisco Transport Controller Operation 8.3 PC and UNIX Workstation Requirements Table 8-1 JRE Compatibility ONS Software Release JRE 1.2.2 Compatible JRE 1.3 Compatible JRE 1.4 Compatible JRE 5.0 Compatible ONS 15454 Release 2.2.1 and earlier Yes No No No ONS 15454 Release 2.2.2 Yes Yes No No ONS 15454 Release 3.0 Yes Yes No No ONS 15454 Release 3.1 Yes Yes No No ONS 15454 Release 3.2 Yes Yes No No ONS 15454 Release 3.
-
Chapter 8 Cisco Transport Controller Operation 8.3 PC and UNIX Workstation Requirements Table 8-2 Computer Requirements for CTC (continued) Area Requirements Operating System Notes • PC: Windows 98 (1st and 2nd editions), Check with the vendor for the latest patch/Service Pack level Windows ME, Windows NT 4.0 with Service Pack 6a, Windows 2000 with Service Pack 3, or Windows XP with Service Pack 1 • Workstation: Solaris versions 9 or 10 Java Runtime JRE 5.0 Environment JRE 5.
-
Chapter 8 Cisco Transport Controller Operation 8.4 ONS 15454 Connection 8.4 ONS 15454 Connection You can connect to the ONS 15454 in multiple ways. You can connect your PC directly the ONS 15454 (local craft connection) using the RJ-45 port on the TCC2/TCC2P card or the LAN pins on the backplane, connect your PC to a hub or switch that is connected to the ONS 15454, connect to the ONS 15454 through a LAN or modem, or establish TL1 connections from a PC or TL1 terminal.
-
Chapter 8 Cisco Transport Controller Operation 8.5.1 Legal Disclaimer The CTC Login window provides the following options to accelerate the login process. • The Disable Network Discovery option omits the discovery of nodes with data communications channel (DCC) connectivity. To access all nodes with DCC connectivity, make sure that Disable Network Discovery is not checked. If you have network discovery disabled, CTC will not poll the network for more recent versions of the software.
-
Chapter 8 Cisco Transport Controller Operation 8.6.1 Node View Figure 8-3 Node View (Default Login View) Menu bar Tool bar Status area Top pane Graphic area Tabs Subtabs 159506 Bottom pane Status bar 8.6.1 Node View Node view, shown in Figure 8-3, is the first view that appears after you log into an ONS 15454. The login node is the first node shown, and it is the “home view” for the session. Node view allows you to manage one ONS 15454 node.
-
Chapter 8 Cisco Transport Controller Operation 8.6.1 Node View The wording on a card in node view shows the status of a card (Active, Standby, Loading, or Not Provisioned). Table 8-5 lists the card statuses. Table 8-5 Node View Card Statuses Card Status Description Sby Card is in standby mode. Act Card is active. NP Card is not present. Ldg Card is resetting. Mis Card is mismatched. The port color in both card and node view indicates the port service state.
-
Chapter 8 Cisco Transport Controller Operation 8.6.1 Node View Table 8-6 Node View Card Port Colors and Service States (continued) Port Color Service State Description Green IS-NR (In-Service and Normal) The port is fully operational and performing as provisioned. The port transmits a signal and displays alarms; loopbacks are not allowed. Violet OOS-AU,AINS (Out-of-Service and Autonomous, Automatic In-Service) The port is out-of-service, but traffic is carried. Alarm reporting is suppressed.
-
Chapter 8 Cisco Transport Controller Operation 8.6.2 Network View Table 8-7 Node View Tabs and Subtabs (continued) Tab Description History Provides a history of node alarms including date, Session, Shelf type, and severity of each alarm. The Session subtab displays alarms and events for the current session. The Node subtab displays alarms and events retrieved from a fixed-size log on the node. Circuits Creates, deletes, edits, and maps circuits and rolls.
-
Chapter 8 Cisco Transport Controller Operation 8.6.2 Network View Figure 8-6 Network in CTC Network View Icon color indicates node status Dots indicate selected node 96939 Bold letters indicate login node, asterisk indicates topology host Note Nodes with DCC connections to the login node do not appear if you checked the Disable Network Discovery check box in the Login dialog box. The graphic area displays a background image with colored ONS 15454 icons.
-
Chapter 8 Cisco Transport Controller Operation 8.6.
-
Chapter 8 Cisco Transport Controller Operation 8.6.3 Card View 8.6.2.4 Link Consolidation CTC provides the ability to consolidate the DCC, general communications channel (GCC), optical transport section (OTS), provisionable patchcord (PPC), and server trail links shown in the network view. Link consolidation allows you to condense multiple inter-nodal links into a single link. The link consolidation sorts links by class; for example, all DCC links are consolidated together.
-
Chapter 8 Cisco Transport Controller Operation 8.6.3 Card View Figure 8-7 CTC Card View Showing a DS1 Card 159504 Card identification and status Note CTC provides a card view for all ONS 15454 cards except the TCC2, TCC2P, XCVT, XC10G, and XC-VXC-10G cards. Provisioning for these common control cards occurs at the node view; therefore, no card view is necessary. Use the card view tabs and subtabs shown in Table 8-12 to provision and manage the ONS 15454.
-
Chapter 8 Cisco Transport Controller Operation 8.6.4 Print or Export CTC Data Table 8-12 Card View Tabs and Subtabs (continued) Tab Description Subtabs Provisioning Provisions an ONS 15454 card.
-
Chapter 8 Cisco Transport Controller Operation 8.7 Using the CTC Launcher Application to Manage Multiple ONS Nodes The Table Contents option does not apply to all windows; for a list of windows that do not support print or export, see the Cisco ONS 15454 Procedure Guide. 8.7 Using the CTC Launcher Application to Manage Multiple ONS Nodes The CTC Launcher application is an executable file, StartCTC.exe, that is provided on Software Release 8.5 CDs for Cisco ONS products.
-
Chapter 8 Cisco Transport Controller Operation 8.7 Using the CTC Launcher Application to Manage Multiple ONS Nodes Figure 8-8 Static IP-Over-CLNS Tunnels Central office Other vendor GNE 1 ONS ENE 1 OSI/DCC Tunnel provisioning IP/DCC IP+ OSI IP-over-CLNS tunnel Tunnel provisioning IP DCN CTC Other vendor GNE 2 ONS ENE 2 IP/DCC OSI/DCC IP-over-CLNS Tunnel Tunnel tunnel provisioning provisioning 140174 IP Figure 8-9 shows the same network using TL1 tunnels.
-
Chapter 8 Cisco Transport Controller Operation 8.7 Using the CTC Launcher Application to Manage Multiple ONS Nodes Figure 8-9 TL1 Tunnels Central office Other vendor GNE 1 ONS ENE 1 OSI/DCC IP/DCC IP + OSI Tunnel provisioning TL1 tunnel IP DCN CTC IP Other vendor GNE 2 ONS ENE 2 OSI/DCC IP/DCC 140175 TL1 tunnel TL1 tunnels provide several advantages over static IP-over-CLNS tunnels. Because tunnel provisioning is needed only at the CTC computer, they are faster to set up.
-
Chapter 8 Cisco Transport Controller Operation 8.8 TCC2/TCC2P Card Reset Table 8-13 TL1 and Static IP-Over-CLNS Tunnels Comparison (continued) Static IP-Over-CLNS Category TL1 Tunnel Comments Potential to breach DCN Possible from DCC using IP. Not possible A potential exists to breach a DCN from a DCC using IP. This potential does not exist for TL1 tunnels.
-
Chapter 8 Cisco Transport Controller Operation 8.10 Software Revert operation should be part of a regular ONS 15454 maintenance program at approximately weekly intervals, and should also be completed when preparing an ONS 15454 for a pending natural disaster, such as a flood or fire. A database backup may be restored in two ways, partial or complete. A partial database restore operation restores only the provisioning data. A complete database restore operation restores both system and provisioning data.
-
CH A P T E R 9 Security This chapter provides information about Cisco ONS 15454 users and security. To provision security, refer to the Cisco ONS 15454 Procedure Guide. Chapter topics include: • 9.1 User IDs and Security Levels, page 9-1 • 9.2 User Privileges and Policies, page 9-1 • 9.3 Audit Trail, page 9-8 • 9.4 RADIUS Security, page 9-9 9.
-
Chapter 9 Security 9.2.1 User Privileges by CTC Action 9.2.1 User Privileges by CTC Action Table 9-1 shows the actions that each user privilege level can perform in node view.
-
Chapter 9 Security 9.2.
-
Chapter 9 Security 9.2.
-
Chapter 9 Security 9.2.
-
Chapter 9 Security 9.2.
-
Chapter 9 Security 9.2.2 Security Policies 9.2.2.2 Idle User Timeout Each ONS 15454 CTC or TL1 user can be idle during his or her login session for a specified amount of time before the CTC window is locked. The lockouts prevent unauthorized users from making changes. Higher-level users have shorter default idle periods and lower-level users have longer or unlimited default idle periods, as shown in Table 9-3.
-
Chapter 9 Security 9.3 Audit Trail 9.2.2.4 Secure Access Secure access is based on SSH and SSL protocols. Secure access can be enabled for EMS (applicable to CTC). When access is set to secure, CTC provides enhanced SFTP and SSH security when communicating with the node. For more information on how to enable EMS secure access, refer Cisco ONS 15454 Procedure Guide for instructions. 9.
-
Chapter 9 Security 9.3.2 Audit Trail Capacities • Connection Mode—Telnet, Console, SNMP • Category—Type of change (Hardware, Software, Configuration) • Status—Status of the user action (Read, Initial, Successful, Timeout, Failed) • Time—Time of change • Message Type—Whether the event is Success/Failure type • Message Details—Description of the change 9.3.2 Audit Trail Capacities The ONS 15454 is able to store 640 log entries.
-
Chapter 9 Security 9.4.2 Shared Secrets 9.4.2 Shared Secrets A shared secret is a text string that serves as a password between: • A RADIUS client and RADIUS server • A RADIUS client and a RADIUS proxy • A RADIUS proxy and a RADIUS server For a configuration that uses a RADIUS client, a RADIUS proxy, and a RADIUS server, the shared secret that is used between the RADIUS client and the RADIUS proxy can be different from the shared secret used between the RADIUS proxy and the RADIUS server.
-
CH A P T E R 10 Timing This chapter provides information about Cisco ONS 15454 SONET timing. To provision timing, refer to the Cisco ONS 15454 Procedure Guide. Chapter topics include: • 10.1 Timing Parameters, page 10-1 • 10.2 Network Timing, page 10-2 • 10.3 Synchronization Status Messaging, page 10-3 10.1 Timing Parameters SONET timing parameters must be set for each ONS 15454.
-
Chapter 10 Timing 10.2 Network Timing Caution Note Mixed timing allows you to select both external and line timing sources. However, Cisco does not recommend its use because it can create timing loops. Use this mode with caution. Only one port can be used for timing related provisioning per line card. 10.2 Network Timing Figure 10-1 shows an ONS 15454 network timing setup example. Node 1 is set to external timing. Two timing references are set to BITS.
-
Chapter 10 Timing 10.
-
Chapter 10 Timing 10.3.1 SONET SSM Messages 10.3.1 SONET SSM Messages SSM messages are either Generation 1 or Generation 2. Generation 1 is the first and most widely deployed SSM message set. Generation 2 is a newer version. If you enable SONET SSM for the ONS 15454, consult your timing reference documentation to determine which message set to use. Table 10-1 and Table 10-2 show the SONET Generation 1 and Generation 2 message sets.
-
Chapter 10 Timing 10.3.2 SDH SSM Messages Table 10-3 SDH SSM Messages (continued) Message Quality Description G812T 3 Transit node clock traceable G812L 4 Local node clock traceable SETS 5 Synchronous equipment DUS 6 Do not use for timing synchronization Cisco ONS 15454 Reference Manual, R8.5.
-
Chapter 10 Timing 10.3.2 SDH SSM Messages Cisco ONS 15454 Reference Manual, R8.5.
-
CH A P T E R 11 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.
-
Chapter 11 Circuits and Tunnels 11.1 Overview • 11.20 Merged Circuits, page 11-46 • 11.21 Reconfigured Circuits, page 11-47 • 11.22 VLAN Management, page 11-47 • 11.23 Server Trails, page 11-47 11.1 Overview You can create circuits across and within ONS 15454 nodes and assign different attributes to circuits. For example, you can: • Create one-way, two-way (bidirectional), or broadcast circuits. • Assign user-defined names to circuits. • Assign different circuit sizes.
-
Chapter 11 Circuits and Tunnels 11.2 Circuit Properties • Size—The circuit size. VT circuits are 1.5. STS circuit sizes are 1, 3c, 6c, 9c, 12c, 24c, 36c, 48c, and 192c. OCHNC sizes are Equipped non specific, Multi-rate, 2.5 Gbps No FEC (forward error correction), 2.5 Gbps FEC, 10 Gbps No FEC, and 10 Gbps FEC (OCHNC is DWDM only; refer to the Cisco ONS 15454 DWDM ProcedureGuide). VCAT circuits are VT1.5-nv, STS-1-nv, STS-3c-nv, and STS-12c-nv, where n is the number of members.
-
Chapter 11 Circuits and Tunnels 11.2.1 Concatenated STS Time Slot Assignments Figure 11-1 ONS 15454 Circuit Window in Network View 11.2.1 Concatenated STS Time Slot Assignments Table 11-1 shows the available time slot assignments for concatenated STSs when using CTC to provision circuits.
-
Chapter 11 Circuits and Tunnels 11.2.
-
Chapter 11 Circuits and Tunnels 11.2.
-
Chapter 11 Circuits and Tunnels 11.2.3 Circuit States Table 11-2 ONS 15454 Circuit Status (continued) Status Definition/Activity PARTIAL A CTC-created circuit is missing a cross-connect or network span, a complete path from source to destinations does not exist, or an alarm interface panel (AIP) change occurred on one of the circuit nodes and the circuit is in need of repair. (AIPs store the node MAC address.) In CTC, circuits are represented using cross-connects and network spans.
-
Chapter 11 Circuits and Tunnels 11.2.3 Circuit States • If all cross-connects in a circuit are in an Out-of-Service (OOS) service state, such as Out-of-Service and Management, Maintenance (OOS-MA,MT); Out-of-Service and Management, Disabled (OOS-MA,DSBLD); or Out-of-Service and Autonomous, Automatic In-Service (OOS-AU,AINS) service state, the circuit service state is Out-of-Service (OOS).
-
Chapter 11 Circuits and Tunnels 11.2.4 Circuit Protection Types Note Although ML-Series cards do not use the Telcordia GR-1093-CORE state model, you can also set a soak timer for ML-Series cards ports. The soak period is the amount of time that the ML-Series port remains in the Down state after an error-free signal is continuously received before changing to the Up state.
-
Chapter 11 Circuits and Tunnels 11.2.5 Circuit Information in the Edit Circuit Window Table 11-3 Circuit Protection Types (continued) Protection Type Description SPLITTER The circuit is protected by the protect transponder (TXPP_MR_2.5G) splitter protection. For splitter information, refer to the Cisco ONS 15454 DWDM Procedure Guide. Y-Cable The circuit is protected by a transponder or muxponder card Y-cable protection group. For more information, refer to the Cisco ONS 15454 DWDM Procedure Guide.
-
Chapter 11 Circuits and Tunnels 11.2.5 Circuit Information in the Edit Circuit Window • Alarm states of nodes on the circuit route • 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 By default, the working path is indicated by a green, bidirectional arrow, and the protect path is indicated by a purple, bidirectional arrow.
-
Chapter 11 Circuits and Tunnels 11.3 Cross-Connect Card Bandwidth Figure 11-2 BLSR Circuit Displayed on the Detailed Circuit Map 11.3 Cross-Connect Card Bandwidth The ONS 15454 XCVT, XC10G, and XC-VXC-10G cross-connect cards perform port-to-port, time-division multiplexing (TDM). XCVT, XC10G, and XC-VXC-10G cards perform STS, VT2 (XC-VXC-10G only), and VT1.5 multiplexing.
-
Chapter 11 Circuits and Tunnels 11.3 Cross-Connect Card Bandwidth For example, if you create a VT1.5 circuit from an STS-1 on a drop card, two VT matrix STS ports are used, as shown in Figure 11-3. If you create a second VT1.5 circuit from the same STS port on the drop card, no additional logical STS ports are used on the VT matrix. In fact, you can create up to 28 VT1.5 circuits using the same STS-1 port. However, if the next VT1.
-
Chapter 11 Circuits and Tunnels 11.3 Cross-Connect Card Bandwidth Figure 11-4 Two VT1.5 Circuits in a BLSR VT1.5 circuit #1 on STS-1 1 VT1.5 used on STS-1 27 VT1.5s available on STS-1 XCVT/XC10G Matrices Source STS Matrix Drop EC-1 4 STSs total used 20 STSs available OC-12 VT1.5 Matrix VT1.5 circuit #2 on STS-2 1 VT1.5 used on STS-2 27 VT1.5s available on STS-2 VT1.5 circuit #1 on STS-1 1 VT1.5 used on STS-1 27 VT1.
-
Chapter 11 Circuits and Tunnels 11.4 Portless Transmux Table 11-5 VT Matrix Port Usage for One VT1.5 Circuit Node Type No Protection BLSR Path Protection 1+1 Circuit source or destination node 2 2 3 2 Circuit pass-through node without VT tunnel 2 2 2 2 Circuit pass-through node with VT tunnel 0 0 0 0 Cross-connect card resources can be viewed on the Maintenance > Cross-Connect > Resource Usage tab. This tab shows: • STS-1 Matrix—The percent of STS matrix resources that are used.
-
Chapter 11 Circuits and Tunnels 11.5 DCC Tunnels Table 11-6 Portless Transmux Mapping for XCVT Drop Ports Physical Port Portless Port Pair 1, 2 13, 14 3, 4 15, 16 5, 6 17, 18 7, 8 19, 20 9, 10 21, 22 11, 12 23, 24 Table 11-7 lists the portless transmux for XCVT trunk ports and for XC10G or XC-VXC-10G any-slot ports.
-
Chapter 11 Circuits and Tunnels 11.5.1 Traditional DCC Tunnels 11.5.1 Traditional DCC Tunnels In traditional DCC tunnels, you can use the three LDCCs and the SDCC (when not used for ONS 15454 DCC terminations). A traditional DCC tunnel endpoint is defined by slot, port, and DCC, where DCC can be either the SDCC or one of the LDCCs. You can link LDCCs to LDCCs and link SDCCs to SDCCs. You can also link an SDCC to an LDCC, and an LDCC to an SDCC.
-
Chapter 11 Circuits and Tunnels 11.5.2 IP-Encapsulated Tunnels • All DCC tunnel connections are bidirectional. 11.5.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.
-
Chapter 11 Circuits and Tunnels 11.8.1 Monitor Circuits using portless ports as a source on DS3XM-12 Figure 11-6 VT1.5 Monitor Circuit Received at an EC1-12 Port ONS 15454 Node 1 ONS 15454 Node 2 XC XC VT1.5 Drop Test Set Port 1 EC1-12 OC-N OC-N DS1-14 45157 Class 5 Switch Port 2 VT1.5 Monitor 11.8.
-
Chapter 11 Circuits and Tunnels 11.9.1 Open-Ended Path Protection Circuits Note The XC-VXC-10G cross-connect card supports VT switching based on SF and SD bit error rate (BER) thresholds. The XC10G and XCVT cross-connect cards do not support VT switching based on SF and SD BER thresholds, and hence, in the path protection Selectors tab, the SF BER Level and SD BER Level columns display "N/A" for these cards.
-
Chapter 11 Circuits and Tunnels 11.9.2 Go-and-Return Path Protection Routing 11.9.2 Go-and-Return Path Protection Routing The go-and-return path protection routing option allows you to route the path protection working path on one fiber pair and the protect path on a separate fiber pair (Figure 11-8). The working path will always be the shortest path. If a fault occurs, both the working and protection fibers are not affected. This feature only applies to bidirectional path protection circuits.
-
Chapter 11 Circuits and Tunnels 11.11 BLSR STS and VT Squelch Tables • If BLSRs are provisioned as nonrevertive, PCA circuits are not restored automatically after a ring or span switch. You must switch the BLSR manually. • PCA circuits are routed on working channels when you upgrade a BLSR from a two-fiber to a four-fiber or from one optical speed to a higher optical speed.
-
Chapter 11 Circuits and Tunnels 11.11.2 BLSR VT Squelch Table 11.11.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.
-
Chapter 11 Circuits and Tunnels 11.13 Section and Path Trace • Circuit name • Type • Size • OCHNC Wlen • Direction • Protection • Status • Source • Destination • # of VLANs • # of Spans • State • Loopback Note CTC does not support the display of Cisco proprietary RPR circuit topologies. Note CTC does not support provisioning or maintenance of IEEE RPR rings. You must use Cisco IOS. For more information about IEEE 802.
-
Chapter 11 Circuits and Tunnels 11.14 Path Signal Label, C2 Byte Table 11-9 ONS 15454 Cards Capable of J1 Path Trace J1 Function Cards Transmit and Receive CE-Series DS1-14 1 DS1N-14 DS1/EC1-56 DS3-12E DS3i-N-12 DS3/EC1-48 DS3N-12E DS3XM-6 DS3XM-12 FC_MR-4 G-Series ML-Series Receive Only EC1-12 OC3 IR 4/STM1 SH 1310 OC3 IR 4/STM1 SH 1310-8 OC12/STM4-4 OC48 IR/STM16 SH AS 1310 OC48 LR/STM16 LH AS 1550 OC192 SR/STM64 IO 1310 OC192 LR/STM64 LH 1550 OC192 IR/STM SH 1550 OC192-XFP 1.
-
Chapter 11 Circuits and Tunnels 11.14 Path Signal Label, C2 Byte (LLC)/Subnetwork Access Protocol (SNAP) header fields on an Ethernet network; it allows a single interface to transport multiple payload types simultaneously. C2 byte hex values are provided in Table 11-10.
-
Chapter 11 Circuits and Tunnels 11.
-
Chapter 11 Circuits and Tunnels 11.15.1 Bandwidth Allocation and Routing Note • Circuit routing does not use links that are down. If you want all links to be considered for routing, do not create circuits when a link is down. • Circuit routing computes the shortest path when you add a new drop to an existing circuit. It tries to find the shortest path from the new drop to any nodes on the existing circuit.
-
Chapter 11 Circuits and Tunnels 11.16 Manual Circuit Routing Figure 11-9 Secondary Sources and Destinations Primary source Primary destination Vendor A network Vendor B network Secondary source 55402 Secondary destination ONS 15454 network Several rules apply to secondary sources and destinations: • CTC does not allow a secondary destination for unidirectional circuits because you can always specify additional destinations after you create the circuit.
-
Chapter 11 Circuits and Tunnels 11.
-
Chapter 11 Circuits and Tunnels 11.16 Manual Circuit Routing Figure 11-12 Ethernet Shared Packet Ring Routing Ethernet source Node 1 Node 2 Node 3 Node 4 55405 Ethernet destination • Multicard EtherSwitch circuits can have virtual path protection segments if the source or destination is not in the path protection domain.
-
Chapter 11 Circuits and Tunnels 11.
-
Chapter 11 Circuits and Tunnels 11.17 Constraint-Based Circuit Routing Table 11-15 Bidirectional VT Tunnels (continued) Connection Type Number of Inbound Links Number of Outbound Links Number of Sources Number of Destinations 1 — — — — — At Source Nodes Only VT tunnel endpoint — At Destination Nodes Only VT tunnel endpoint 1 Although virtual path protection segments are possible in VT tunnels, VT tunnels are still considered unprotected.
-
Chapter 11 Circuits and Tunnels 11.18 Virtual Concatenated Circuits 11.18 Virtual Concatenated Circuits Virtual concatenated (VCAT) circuits, also called VCAT groups (VCGs), transport traffic using noncontiguous TDM time slots, avoiding the bandwidth fragmentation problem that exists with contiguous concatenated (CCAT) circuits. The cards that support VCAT circuits are the CE-Series, FC_MR-4 (both line rate and enhanced mode), and ML-Series cards.
-
Chapter 11 Circuits and Tunnels 11.18.
-
Chapter 11 Circuits and Tunnels 11.18.3 Link Capacity Adjustment Table 11-16 Switch Times Type of circuit For CE100T-8 in ms CCAT 60 HO VCAT HO LCAS 1 90 90 LO VCAT 202 LO LCAS 202 1. The calculated number for HO LCAS includes all the inherent delays of the protocol. Also the CE-100-T numbers are for a group size of only three members. Note The switch time values shown in Table 11-16 does not include differential delay. The maximum differential delay for CE100T-8 is 122ms.
-
Chapter 11 Circuits and Tunnels 11.18.4 VCAT Circuit Size Note Protection switching for LCAS, SW-LCAS, and non-LCAS VCAT circuits might exceed 60ms. Traffic loss for VT VCAT circuits is approximately two times more than an STS VCAT circuit. You can minimize traffic loss by reducing path differential delay. 11.18.4 VCAT Circuit Size Table 11-17 lists supported VCAT circuit rates and number of members for each card.
-
Chapter 11 Circuits and Tunnels 11.18.5 Open-Ended VCAT • FC_MR-4 (line mode) card—All VCAT circuits using FC_MR-4 (line mode) cards have a fixed number of members; you cannot add or delete members. • ML-Series cards—All VCAT circuits using ML-Series cards have a fixed number of members; you cannot add or delete members. Table 11-18 summarizes the VCAT capabilities for each card.
-
Chapter 11 Circuits and Tunnels 11.18.5 Open-Ended VCAT Figure 11-16 Open-Ended VCAT Destination SONET/SDH Port VCAT-Destination VCAT-Source Source Destination SONET/SDH Port Non-CTC Managed Network 240645 CTC Managed Network Open-ended VCAT Circuit End-to-end VCAT Circuit Open-ended VCAT circuits can originate or terminate on any pair of OC-N ports and you can route open-ended VCAT circuits using any of the cards and ports supported by VCAT.
-
Chapter 11 Circuits and Tunnels 11.19 Bridge and Roll Table 11-19 Protection options for Open-Ended VCAT Circuits Routing Preferences Routing Mode Split fiber Manual/Auto Protection Options • Fully protected (Line only) • Unprotected • PCA • DRI Note Split fiber with secondary destinations Manual/Auto • Note • Path protection is not supported. Fully protected Line protection is not supported. DRI 11.
-
Chapter 11 Circuits and Tunnels 11.19.1 Rolls Window Figure 11-17 Rolls Window The Rolls window information includes: • Roll From Circuit—The circuit that has connections that will no longer be used when the roll process is complete. • Roll To Circuit—The circuit that will carry the traffic after the roll process is complete. The Roll To Circuit is the same as the Roll From Circuit if a single circuit is involved in a roll. • Roll State—The roll status; see the “11.19.
-
Chapter 11 Circuits and Tunnels 11.19.2 Roll Status • Roll From Circuit—The circuit that has connections that will no longer be used when the process is complete. • 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. You can do this when a manual roll is in a ROLL_PENDING status and you have not yet completed the roll or have not cancelled its sibling roll.
-
Chapter 11 Circuits and Tunnels 11.19.3 Single and Dual Rolls Note You can only reroute circuits in the DISCOVERED status. You cannot reroute circuits that are in the ROLL_PENDING status. 11.19.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 11-18 and Figure 11-19, respectively).
-
Chapter 11 Circuits and Tunnels 11.19.3 Single and Dual Rolls S Single Roll from One Circuit to Another Circuit (Destination Changes) Node 1 Node 2 D Node 3 Node 4 D2 78703 Figure 11-20 Original leg New leg Figure 11-21 shows one circuit rolling onto another circuit at the source.
-
Chapter 11 Circuits and Tunnels 11.19.4 Two Circuit Bridge and Roll Figure 11-22 S Dual Roll to Reroute a Link Node 1 Node 2 D 83268 Original leg New leg Figure 11-23 illustrates a dual roll involving two circuits.
-
Chapter 11 Circuits and Tunnels 11.19.5 Protected Circuits 11.19.5 Protected Circuits CTC allows you to roll the working or protect path regardless of which path is active. You can upgrade an unprotected circuit to a fully protected circuit or downgrade a fully protected circuit to an unprotected circuit with the exception of a path protection circuit. When using bridge and roll on path protection circuits, you can roll the source or destination or both path selectors in a dual roll.
-
Chapter 11 Circuits and Tunnels 11.21 Reconfigured Circuits 11.21 Reconfigured Circuits You can reconfigure multiple circuits, which is typically necessary when a large number of circuits are in the PARTIAL status. When reconfiguring multiple circuits, the selected circuits can be any combination of DISCOVERED, PARTIAL, DISCOVERED_TL1, or PARTIAL_TL1 circuits. You can reconfigure tunnels, VAP circuits, VLAN-assigned circuits, VCAT circuits, CTC-created circuits, and TL1-created circuits.
-
Chapter 11 Circuits and Tunnels 11.23.1 Server Trail Protection Types 11.23.1 Server Trail Protection Types The server trail protection type determines the protection type for any circuits that traverse it. A server trail link can be one of the following protection types: Note • Preemptible—PCA circuits will use server trails with the Preemptible attribute.
-
Chapter 11 Circuits and Tunnels 11.23.2 VCAT Circuit Routing over Server Trails 11.23.2.1 Shared Resource Link Group The Shared Resource Link Group (SRLG) attribute can be assigned to a server trail link using a commonly shared resource such as port, fiber or span. For example, if two server trail links are routed over the same fiber, an SRLG attribute can be assigned to these links. SRLG is used by Cisco Transport Manager (CTM) to specify link diversity.
-
Chapter 11 Circuits and Tunnels 11.23.2 VCAT Circuit Routing over Server Trails Cisco ONS 15454 Reference Manual, R8.5.
-
CH A P T E R 12 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.
-
Chapter 12 SONET Topologies and Upgrades 12.1 SONET Rings and TCC2/TCC2P Cards Table 12-1 ONS 15454 Rings with Redundant TCC2/TCC2P Cards Ring Type Maximum Rings per Node BLSRs 5 2-Fiber BLSR 5 4-Fiber BLSR 1 Path protection with SDCC 341,2 Path protection with LDCC 143,4 Cisco ONS 15454 Reference Manual, R8.5.
-
Chapter 12 SONET Topologies and Upgrades 12.2 Bidirectional Line Switched Rings Table 12-1 ONS 15454 Rings with Redundant TCC2/TCC2P Cards (continued) Ring Type Maximum Rings per Node Path protection with LDCC and SDCC 265 1. Total SDCC usage must be equal to or less than 84 SDCCs. 2. See the “12.3 Path Protection” section on page 12-14. 3. Total LDCC usage must be equal to or less than 28 LDCCs. 4. See the “12.3 Path Protection” section on page 12-14. 5.
-
Chapter 12 SONET Topologies and Upgrades 12.2.1 Two-Fiber BLSRs Figure 12-1 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 61938 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.
-
Chapter 12 SONET Topologies and Upgrades 12.2.1 Two-Fiber BLSRs Figure 12-2 Four-Node, Two-Fiber BLSR Traffic Pattern Sample Node 0 Node 3 OC-48 Ring Node 1 Fiber 1 Node 2 Fiber 2 61956 Traffic flow Figure 12-3 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.
-
Chapter 12 SONET Topologies and Upgrades 12.2.2 Four-Fiber BLSRs Figure 12-3 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 61957 Traffic flow 12.2.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.
-
Chapter 12 SONET Topologies and Upgrades 12.2.2 Four-Fiber BLSRs Figure 12-4 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 61932 Node 3 Four-fiber BLSRs provide span and ring switching: • Span switching (Figure 12-5 on page 12-8) occurs when a working span fails.
-
Chapter 12 SONET Topologies and Upgrades 12.2.2 Four-Fiber BLSRs Figure 12-5 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 61959 Node 3 Ring switching (Figure 12-6) 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.
-
Chapter 12 SONET Topologies and Upgrades 12.2.3 BLSR Bandwidth Figure 12-6 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 = Protect fibers Node 2 61960 Node 3 12.2.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.
-
Chapter 12 SONET Topologies and Upgrades 12.2.4 BLSR Application Example Table 12-3 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 N 1 – PT2 OC-192 STS 1-192 (Fiber 1) STS 1-192 (Fiber 2) 192 x N – PT 1. N equals the number of ONS 15454 nodes configured as BLSR nodes. 2. PT equals the number of STS-1 circuits passed through ONS 15454 nodes in the ring (capacity can vary depending on the traffic pattern).
-
Chapter 12 SONET Topologies and Upgrades 12.2.4 BLSR Application Example • The ONS 15454 OC-3 card supports a total of four OC-3 ports so that two additional OC-3 spans can be added at little cost.
-
Chapter 12 SONET Topologies and Upgrades 12.2.4 BLSR Application Example Figure 12-9 Shelf Assembly Layout for Node 0 in Figure 12-8 134608 DS3-12 DS3-12 OC3 OC3 OC48 OC48 TCC2/TCC2P Cross Connect AIC-I (Optional) Cross Connect TCC2/TCC2P Free Slot DS1-14 DS1-14 DS1N-14 DS1-14 DS1-14 Figure 12-10 shows the shelf assembly layout for the remaining sites in the ring. In this BLSR configuration, an additional eight DS-3s at Node IDs 1 and 3 can be activated.
-
Chapter 12 SONET Topologies and Upgrades 12.2.5 BLSR Fiber Connections 12.2.5 BLSR Fiber Connections Plan your fiber connections and use the same plan for all BLSR nodes. For example, make the east port the farthest slot to the right and the west port the farthest slot to the left. Plug fiber connected to an east port at one node into the west port on an adjacent node. Figure 12-11 shows fiber connections for a two-fiber BLSR with trunk cards in Slot 5 (west) and Slot 12 (east).
-
Chapter 12 SONET Topologies and Upgrades 12.3 Path Protection Connecting Fiber to a Four-Node, Four-Fiber BLSR West Node 1 Node 2 Tx Rx Tx Rx East West Slot Slot 12 13 Slot Slot 6 5 Tx Rx West East Slot Slot 12 13 Slot Slot 5 6 Slot Slot 12 13 Slot Slot 6 5 Tx Rx East Node 4 West East Slot Slot 12 13 Slot Slot 5 6 Node 3 Working fibers Protect fibers 61958 Figure 12-12 12.3 Path Protection Path Protection Configurations(PPC) provide duplicate fiber paths around the ring.
-
Chapter 12 SONET Topologies and Upgrades 12.3 Path Protection The path protection circuit limit is the sum of the optical bandwidth containing 84 section data communication channels (SDCCs) or 28 line data communication channels (LDCCs), divided by two if you are using redundant TCC2/TCC2P cards. The spans can be of any bandwidth from OC-3 to OC-192. The circuits can be of any size from VT1.5 to 192c. Figure 12-13 shows a basic four-node path protection configuration.
-
Chapter 12 SONET Topologies and Upgrades 12.3 Path Protection Figure 12-14 Path Protection with a Fiber Break Source ONS 15454 Node ID 0 Span 4 Span 5 Span 8 ONS 15454 Node ID 3 ONS 15454 Node ID 1 Span 6 Span 3 Span 1 Span 7 Span 2 Destination ONS 15454 Node ID 2 = Fiber 1 = Fiber 2 32639 Fiber break Figure 12-15 shows a common path protection application. OC-3 optics provide remote switch connectivity to a host Telcordia TR-303 switch.
-
Chapter 12 SONET Topologies and Upgrades 12.3 Path Protection Figure 12-15 Four-Port, OC-3 Path Protection TR-303 Switch ONS 15454 Node ID 0 8 DS-1s ONS 15454 Node ID 3 ONS 15454 Node ID 1 8 DS-1s = Fiber 1 8 DS-1s = Fiber 2 32149 ONS 15454 Node ID 2 Node ID 0 has four DS1-14 cards to provide 56 active DS-1 ports. The other sites only require two DS1-14 cards to handle the eight DS-1s to and from the remote switch.
-
Chapter 12 SONET Topologies and Upgrades 12.3 Path Protection Figure 12-16 Layout of Node ID 0 in the OC-3 Path Protection Example in Figure 12-15 134606 Free Slot Free Slot Free Slot Free Slot Free Slot Free Slot TCC2/TCC2P Cross Connect AIC-I (Optional) Cross Connect TCC2/TCC2P OC3 IR 4 1310 OC3 IR 4 1310 DS1-14 DS1-14 DS1-14 DS1-14 In the Figure 12-15 on page 12-17 example, Nodes IDs 1 to 3 each contain two DS1-14 cards and two OC3 IR 4 1310 cards. Eight free slots exist.
-
Chapter 12 SONET Topologies and Upgrades 12.4 Dual-Ring Interconnect 12.4 Dual-Ring Interconnect Dual-ring interconnect (DRI) topologies provide an extra level of path protection for circuits on interconnected rings. DRI allows users to interconnect BLSRs, path protection configurations, or a path protection with a BLSR, with additional protection provided at the transition nodes. In a DRI topology, ring interconnections occur at two or four nodes.
-
Chapter 12 SONET Topologies and Upgrades 12.4.1 BLSR DRI Figure 12-18 shows ONS 15454 nodes in a traditional BLSR-DRI topology with same-side routing. In Ring 1, Nodes 3 and 4 are the interconnect nodes, and in Ring 2, Nodes 8 and 9 are the interconnect nodes. Duplicate signals are sent between Node 4 (Ring 1) and Node 9 (Ring 2), and between Node 3 (Ring 1) and Node 8 (Ring 2). The primary nodes (Nodes 4 and 9) are on the same side, and the secondary nodes (Nodes 3 and 8) provide an alternative route.
-
Chapter 12 SONET Topologies and Upgrades 12.4.1 BLSR DRI Figure 12-19 shows ONS 15454 nodes in a traditional BLSR-DRI topology with opposite-side routing. In Ring 1, Nodes 3 and 4 are the interconnect nodes, and in Ring 2, Nodes 8 and 9 are the interconnect nodes. Duplicate signals are sent from Node 4 (Ring 1) to Node 8 (Ring 2), and between Node 3 (Ring 1) and Node 9 (Ring 2). In Ring 1, traffic at Node 4 is dropped (to Node 9) and continued (to Node 3).
-
Chapter 12 SONET Topologies and Upgrades 12.4.1 BLSR DRI Figure 12-20 ONS 15454 Integrated BLSR Dual-Ring Interconnect Node 1 Node 2 BLSR 1 Primary Secondary Node 3 Node 4 Node 8 Secondary Primary Node 5 BLSR 2 Node 7 Node 6 Primary Path (working) Secondary Path (protection) 115236 Service Selector Figure 12-21 shows an example of an integrated BLSR DRI on the Edit Circuits window. Cisco ONS 15454 Reference Manual, R8.5.
-
Chapter 12 SONET Topologies and Upgrades 12.4.2 Path Protection DRI Figure 12-21 Integrated BLSR DRI on the Edit Circuits Window 12.4.2 Path Protection DRI Figure 12-22 shows ONS 15454 nodes in a traditional drop-and-continue path protection DRI topology. In Ring 1, Nodes 4 and 5 are the interconnect nodes, and in Ring 2, Nodes 6 and 7 are the interconnect nodes. Duplicate signals are sent between Node 4 (Ring 1) and Node 6 (Ring 2), and between Node 5 (Ring 1) and Node 7 (Ring 2).
-
Chapter 12 SONET Topologies and Upgrades 12.4.2 Path Protection DRI Figure 12-22 ONS 15454 Traditional Path Protection Dual-Ring Interconnect Node 1 Node 3 UPSR Ring 1 Node 4 Node 2 Node 5 Duplicate Signals Node 6 Node 7 UPSR Ring 2 Pass-through Node Bridge Path Selector Primary Path, Primary Return Path, Primary Return Path, Secondary 85761 Primary Path, Secondary Figure 12-23 shows ONS 15454 nodes in an integrated DRI topology.
-
Chapter 12 SONET Topologies and Upgrades 12.4.2 Path Protection DRI Figure 12-23 ONS 15454 Integrated Path Protection Dual-Ring Interconnect DS1/EC1/DS3/GigE ONS 15454 Path Protection Configuration 1 ONS 15454 DRI Node 1 of 2 supporting two-rings with integrated STS-1 and VT1.
-
Chapter 12 SONET Topologies and Upgrades 12.4.3 Path Protection/BLSR DRI Handoff Configurations 12.4.3 Path Protection/BLSR DRI Handoff Configurations Path protection configurations and BLSRs can also be interconnected. In BLSR/path protectionDRI handoff configurations, primary and secondary nodes can be the circuit source or destination, which is useful when non-DCC optical interconnecting links are present. Figure 12-24 shows an example of a path protection to BLSR traditional DRI handoff.
-
Chapter 12 SONET Topologies and Upgrades 12.4.3 Path Protection/BLSR DRI Handoff Configurations Figure 12-25 ONS 15454 Path Protection to BLSR Integrated DRI Handoff Node 5 Node 1 Node 2 Path Protection Configuration Node 4 Node 3 BLSR Node 7 Node 8 Node 6 Bridge 115272 Path Selector Figure 12-26 shows a path protection to BLSR integrated DRI handoff on the Edit Circuits window. Cisco ONS 15454 Reference Manual, R8.5.
-
Chapter 12 SONET Topologies and Upgrades 12.5 Comparison of the Protection Schemes Figure 12-26 Path Protection to BLSR Integrated DRI Handoff on the Detailed Circuit Map 12.5 Comparison of the Protection Schemes Table 12-4 shows a comparison of the different protection schemes using OC-48 as an example.
-
Chapter 12 SONET Topologies and Upgrades 12.6 Subtending Rings 12.6 Subtending Rings The ONS 15454 supports up to 84 SONET SDCCs or 28 SONET LDCCs with TCC2/TCC2P cards. See Table 12-1 on page 12-2 for ring, SDCC, and LDCC information. Subtending rings reduce the number of nodes and cards required, and reduce external shelf-to-shelf cabling. Figure 12-27 shows an ONS 15454 with multiple subtending rings.
-
Chapter 12 SONET Topologies and Upgrades 12.6 Subtending Rings Figure 12-28 Path Protection Subtending from a BLSR Node 4 Node 1 Slot 5 Slot 6 Slot 13 Slot 12 Slot 13 Slot 12 BLSR Slot 6 Slot 5 Node 3 55303 Slot 5 Slot 12 Node 2 The ONS 15454 can support two BLSRs on the same node. This allows you to deploy an ONS 15454 in applications requiring SONET Digital Cross-connect Systems (DCSs) or multiple SONET add/drop multiplexers (ADMs). Figure 12-29 shows two BLSRs shared by one ONS 15454.
-
Chapter 12 SONET Topologies and Upgrades 12.7 Linear ADM Configurations After subtending two BLSRs, you can route circuits from nodes in one ring to nodes in the second ring. For example, in Figure 12-29 you can route a circuit from Node 1 to Node 7. The circuit would normally travel from Node 1 to Node 4 to Node 7. If fiber breaks occur, for example between Nodes 1 and 4 and Nodes 4 and 7, traffic is rerouted around each ring: in this example, Nodes 2 and 3 in Ring 1 and Nodes 5 and 6 in Ring 2. 12.
-
Chapter 12 SONET Topologies and Upgrades 12.8 Path-Protected Mesh Networks Figure 12-31 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 32136 Protect traffic PPMN also allows spans with different SONET speeds to be mixed together in “virtual rings.” Figure 12-32 shows Nodes 1, 2, 3, and 4 in a standard OC-48 ring.
-
Chapter 12 SONET Topologies and Upgrades 12.9 Four-Shelf Node Configurations Figure 12-32 ONS 15454 Node 5 PPMN Virtual Ring ONS 15454 Node 4 ONS 15454 Node 1 OC-12 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 12.9 Four-Shelf Node Configurations You can link multiple ONS 15454s using their OC-N cards (that is, create a fiber-optic bus) to accommodate more access traffic than a single ONS 15454 can support.
-
Chapter 12 SONET Topologies and Upgrades 12.10 STS around the Ring Figure 12-33 Four-Shelf Node Configuration Redundant OC-N Feed Up to 72 DS-3s, 84 DS-1s Redundant OC-N Bus ONS 15454, Node 1 Up to 72 DS-3s, 84 DS-1s Redundant OC-N Bus ONS 15454, Node 2 Up to 72 DS-3s, 84 DS-1s Redundant OC-N Bus ONS 15454, Node 3 ONS 15454, Node 4 32097 Up to 96 DS-3s, 112 DS-1s 12.
-
Chapter 12 SONET Topologies and Upgrades 12.11 OC-N Speed Upgrades Figure 12-34 STS Around the Ring ONS 15454 Node 2 Source ONS 15454 Node 1 ONS 15454 Node 3 ONS 15454 Node 4 240644 Drop 12.11 OC-N Speed Upgrades A span is the optical fiber connection between two ONS 15454 nodes. In a span (optical speed) upgrade, the transmission rate of a span is upgraded from a lower to a higher OC-N signal but all other span configuration attributes remain unchanged.
-
Chapter 12 SONET Topologies and Upgrades 12.11 OC-N Speed Upgrades • Four-port OC-3 to MRC-2.5G-4 • Single-port OC-12 to four-port OC-12 • Single-port OC-12 to OC-48 • Single-port OC-12 to OC-192 • Single-port OC-12 to MRC-12 • Single-port OC-12 to MRC-2.5G-4 • OC-48 to MRC-12 • OC-192 to OC192-XFP • OC-48 to OC192SR1/STM64IO Short Reach or OC192/STM64 Any Reach Table 12-5 lists permitted upgrades for Slots 5, 6, 12, and 13 (high-speed slots).
-
Chapter 12 SONET Topologies and Upgrades 12.11 OC-N Speed Upgrades Table 12-6 Upgrade Options for Slots 1 through 4 and 14 through 17 Cards Four-port OC-3 Eight-port OC-3 One-port OC-12 Four-port OC-12 OC-48 OC-192 MRC-2.
-
Chapter 12 SONET Topologies and Upgrades 12.11.1 Span Upgrade Wizard Note Span upgrades do not upgrade SONET topologies (for example, a 1+1 group to a two-fiber BLSR). Refer to the Cisco ONS 15454 Procedure Guide for topology upgrade procedures. 12.11.1 Span Upgrade Wizard The Span Upgrade Wizard automates all steps in the manual span upgrade procedure (BLSR, path protection, and 1+1).
-
Chapter 12 SONET Topologies and Upgrades 12.12.
-
Chapter 12 SONET Topologies and Upgrades 12.12.2 Point-to-Point or Linear ADM to Two-Fiber BLSR Figure 12-35 Unprotected Point-to-Point ADM to Path Protection Conversion ONS 15454 Node 1 ONS 15454 Node 4 OC-12 37 OC-48 ONS 15454 Node 8 12.12.2 Point-to-Point or Linear ADM to Two-Fiber BLSR A 1+1 point-to-point or linear ADM to a two-fiber BLSR conversion is manual.
-
Chapter 12 SONET Topologies and Upgrades 12.12.4 Two-Fiber BLSR to Four-Fiber BLSR 12.12.4 Two-Fiber BLSR to Four-Fiber BLSR CTC provides a wizard to convert two-fiber OC-48 or OC-192 BLSRs to four-fiber BLSRs. To convert the BLSR, you must install two OC-48 or OC-192 cards at each two-fiber BLSR node, then log into CTC and convert each node from two-fiber to four-fiber.
-
Chapter 12 SONET Topologies and Upgrades 12.12.5 Add or Remove a Node from a Topology Cisco ONS 15454 Reference Manual, R8.5.
-
CH A P T E R 13 Management Network Connectivity This chapter provides an overview of ONS 15454 data communications network (DCN) connectivity. Cisco Optical Networking System (ONS) network communication is based on IP, including communication between Cisco Transport Controller (CTC) computers and ONS 15454 nodes, and communication among networked ONS 15454 nodes.
-
Chapter 13 Management Network Connectivity 13.2 IP Addressing Scenarios • They can be connected to LANs through direct connections or a router. • IP subnetting can create multiple logical ONS 15454 networks within a single Class A, B, or C IP network. If you do not subnet, you will only be able to use one network from your Class A, B, or C network. • Different IP functions and protocols can be used to achieve specific network goals.
-
Chapter 13 Management Network Connectivity 13.2.1 IP Scenario 1: CTC and ONS 15454s on Same Subnet 13.2.1 IP Scenario 1: CTC and ONS 15454s on Same Subnet IP Scenario 1 shows a basic ONS 15454 LAN configuration (Figure 13-1). The ONS 15454s and CTC computer reside on the same subnet. All ONS 15454s connect to LAN A, and all ONS 15454s have DCC connections. Figure 13-1 IP Scenario 1: CTC and ONS 15454s on Same Subnet CTC Workstation IP Address 192.168.1.100 Subnet Mask 255.255.255.
-
Chapter 13 Management Network Connectivity 13.2.3 IP Scenario 3: Using Proxy ARP to Enable an ONS 15454 Gateway Figure 13-2 IP Scenario 2: CTC and ONS 15454 Nodes Connected to a Router 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" 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.
-
Chapter 13 Management Network Connectivity 13.2.3 IP Scenario 3: Using Proxy ARP to Enable an ONS 15454 Gateway IP Scenario 3 is similar to IP Scenario 1, but only one ONS 15454 (1) connects to the LAN (Figure 13-3). Two ONS 15454s (2 and 3) connect to ONS 15454 1 through the SONET DCC. Because all three ONS 15454s are on the same subnet, proxy ARP enables ONS 15454 1 to serve as a gateway for ONS 15454 2 and 3. Note This scenario assumes all CTC connections are to Node 1.
-
Chapter 13 Management Network Connectivity 13.2.4 IP Scenario 4: Default Gateway on a CTC Computer In Figure 13-4, Node 1 announces to Node 2 and 3 that it can reach the CTC host. Similarly, Node 3 announces that it can reach the ONS 152xx. The ONS 152xx is shown as an example; any network element (NE) can be set up as an additional host. Figure 13-4 IP Scenario 3: Using Proxy ARP with Static Routing CTC Workstation IP Address 192.168.1.100 Subnet Mark at CTC Workstation 255.255.255.
-
Chapter 13 Management Network Connectivity 13.2.5 IP Scenario 5: Using Static Routes to Connect to LANs Figure 13-5 IP 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 15454 #1 IP Address 192.168.1.10 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15454 #2 IP Address 192.168.2.20 Subnet Mask 255.255.255.
-
Chapter 13 Management Network Connectivity 13.2.5 IP Scenario 5: Using Static Routes to Connect to LANs Figure 13-6 IP 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 Static Routes Destination 192.168.3.0 Destination 192.168.4.0 Mask 255.255.255.0 Mask 255.255.255.0 Next Hop 192.168.2.10 Next Hop 192.168.2.
-
Chapter 13 Management Network Connectivity 13.2.5 IP Scenario 5: Using Static Routes to Connect to LANs Figure 13-7 IP Scenario 5: Static Route With Multiple LAN Destinations LAN D Router #3: IP Address of the interface connected to LAN-C = 192.168.5.10 IP Address of the interface connected to LAN-D = 192.168.6.1 Subnet Mask = 255.255.255.0 Static Routes: Destination = 192.168.0.0 Destination = 192.168.4.0 Mask = 255.255.255.0 Mask = 255.255.255.0 Next Hop = 192.168.5.1 Next Hop = 192.168.5.
-
Chapter 13 Management Network Connectivity 13.2.6 IP Scenario 6: Using OSPF 13.2.6 IP Scenario 6: Using OSPF Open Shortest Path First (OSPF) is a link state Internet routing protocol. Link state protocols use a “hello protocol” to monitor their links with adjacent routers and to test the status of their links to their neighbors. Link state protocols advertise their directly connected networks and their active links.
-
Chapter 13 Management Network Connectivity 13.2.6 IP Scenario 6: Using OSPF Figure 13-8 IP 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.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 15454 #1 IP Address 192.168.2.10 Subnet Mask 255.255.255.0 Default Router = 192.168.2.
-
Chapter 13 Management Network Connectivity 13.2.7 IP Scenario 7: Provisioning the ONS 15454 SOCKS Proxy Server Figure 13-9 IP 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.
-
Chapter 13 Management Network Connectivity 13.2.7 IP Scenario 7: Provisioning the ONS 15454 SOCKS Proxy Server The ONS 15454 gateway setting performs the following tasks: • Isolates DCC IP traffic from Ethernet (craft port) traffic and accepts packets based on filtering rules. The filtering rules (see Table 13-3 on page 13-17 and Table 13-4 on page 13-18) depend on whether the packet arrives at the ONS 15454 DCC or the TCC2/TCC2P Ethernet interface.
-
Chapter 13 Management Network Connectivity 13.2.7 IP Scenario 7: Provisioning the ONS 15454 SOCKS Proxy Server • External Network Element (ENE)—If set as an ENE, the ONS 15454 neither installs nor advertises default or static routes. CTC computers can communicate with the ONS 15454 using the TCC2/TCC2P craft port, but they cannot communicate directly with any other DCC-connected ONS 15454.
-
Chapter 13 Management Network Connectivity 13.2.7 IP Scenario 7: Provisioning the ONS 15454 SOCKS Proxy Server Figure 13-11 IP Scenario 7: ONS 15454 SOCKS 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 15454 GNE 10.10.10.100/24 ONS 15454 ENE 10.10.10.150/24 ONS 15454 ENE 10.10.10.250/24 ONS 15454 ENE 10.10.10.200/24 SONET 71673 Ethernet Local/Craft CTC 10.10.10.
-
Chapter 13 Management Network Connectivity 13.2.7 IP Scenario 7: Provisioning the ONS 15454 SOCKS Proxy Server Figure 13-12 IP Scenario 7: ONS 15454 SOCKS 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 15454 GNE 10.10.10.100/24 ONS 15454 ENE 192.168.10.150/24 ONS 15454 ENE 192.168.10.250/24 ONS 15454 ENE 192.168.10.200/24 SONET 71674 Ethernet Local/Craft CTC 192.168.10.
-
Chapter 13 Management Network Connectivity 13.2.7 IP Scenario 7: Provisioning the ONS 15454 SOCKS Proxy Server Figure 13-13 IP Scenario 7: ONS 15454 SOCKS 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 15454 GNE 10.10.10.100/24 ONS 15454 ENE 192.168.10.150/24 ONS 15454 GNE 10.10.10.200/24 ONS 15454 ENE 192.168.10.250/24 ONS 15454 ENE 192.168.60.150/24 ONS 15454 ENE 192.168.10.
-
Chapter 13 Management Network Connectivity 13.2.
-
Chapter 13 Management Network Connectivity 13.2.8 IP Scenario 8: Dual GNEs on a Subnet Figure 13-14 IP 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 15454 GNE 10.10.10.100/24 ONS 15454 GNE 10.10.10.150/24 ONS 15454 ENE 10.10.10.250/24 ONS 15454 ENE 10.10.10.200/24 Ethernet Local/Craft CTC 192.168.20.20 SONET 115258 10.10.10.0/24 Figure 13-15 shows a network with dual GNEs on different subnets.
-
Chapter 13 Management Network Connectivity 13.2.9 IP Scenario 9: IP Addressing with Secure Mode Enabled Figure 13-15 IP 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 15454 GNE 10.20.10.100/24 ONS 15454 GNE 10.10.10.100/24 ONS 15454 ENE 192.168.10.200/24 ONS 15454 ENE 192.168.10.250/24 Ethernet Local/Craft CTC 192.168.20.20 SONET 115259 Interface 0/1 10.10.10.1 13.2.
-
Chapter 13 Management Network Connectivity 13.2.9 IP Scenario 9: IP Addressing with Secure Mode Enabled enabled, the IP addresses provisioned for both TCC2P TCP/IP LAN ports must follow general IP addressing guidelines and must reside on different subnets from each other and the default router IP address.
-
Chapter 13 Management Network Connectivity 13.2.9 IP Scenario 9: IP Addressing with Secure Mode Enabled Figure 13-16 IP Scenario 9: ONS 15454 GNE and ENEs on the Same Subnet with Secure Mode Enabled 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 15454 GNE Backplane - 10.10.10.100/24 TCC2P - 176.20.20.40/24 ONS 15454 ENE 10.10.10.150/24 - Backplane 176.20.20.10/24 - TCC2P ONS 15454 ENE Backplane - 10.10.10.250/24 TCC2P - 176.20.20.
-
Chapter 13 Management Network Connectivity 13.2.9 IP Scenario 9: IP Addressing with Secure Mode Enabled Figure 13-17 IP Scenario 9: ONS 15454 GNE and ENEs on Different Subnets with Secure Mode Enabled 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 15454 GNE Backplane - 10.10.10.100/24 TCC2P - 176.20.20.40/24 ONS 15454 ENE 192.168.10.150/24 - Backplane 176.20.20.10/24 - TCC2P ONS 15454 ENE Backplane - 192.168.10.250/24 TCC2P - 176.20.
-
Chapter 13 Management Network Connectivity 13.3 Routing Table 13.3 Routing Table ONS 15454 routing information appears on the Maintenance > Routing Table tab. The routing table provides the following information: • Destination—Displays the IP address of the destination network or host. • Mask—Displays the subnet mask used to reach the destination host or network. • Gateway—Displays the IP address of the gateway used to reach the destination network or host.
-
Chapter 13 Management Network Connectivity 13.4 External Firewalls • Mask (255.255.255.255) is a 32 bit mask, meaning that only the 172.20.214.92 address is a destination. • Gateway (127.0.0.1) is a loopback address. The host directs network traffic to itself using this address. • Interface (lo0) indicates that the local loopback interface is used to reach the gateway. Entry 4 shows the following: • Destination (172.20.214.93) is the destination host IP address. • Mask (255.255.255.
-
Chapter 13 Management Network Connectivity 13.4 External Firewalls Table 13-6 Ports Used by the TCC2/TCC2P (continued) Port Function Action1 2361 TL1 D 3082 Raw TL1 D 3083 TL1 D 3 5001 BLSR server port D 5002 BLSR client port D 7200 SNMP alarm input port D 9100 EQM port D 9401 TCC boot port D 9999 Flash manager D 10240-12287 Proxy client D 57790 Default TCC listener port OK 1. D = deny, NA = not applicable, OK = do not deny 2.
-
Chapter 13 Management Network Connectivity 13.5 Open GNE access-list access-list access-list access-list access-list 100 100 100 100 100 remark *** allows initial contact with the 15454 using http (port 80) *** remark permit tcp host 192.168.10.10 host 10.10.10.100 eq 1080 remark *** allows CTC communication with the 15454 GNE (port 1080) *** remark 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.
-
Chapter 13 Management Network Connectivity 13.5 Open GNE Figure 13-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 15454 GNE 10.10.10.100/24 ONS 15454 ENE 10.10.10.150/24 ONS 15454 ENE 10.10.10.250/24 ONS 15454 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 115748 10.10.10.
-
Chapter 13 Management Network Connectivity 13.6 TCP/IP and OSI Networking Figure 13-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.1 ONS 15454 GNE 10.10.10.100/24 ONS 15454 ENE 10.10.10.150/24 ONS 15454 ENE 10.10.10.250/24 ONS 15454 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 115749 10.10.10.0/24 13.
-
Chapter 13 Management Network Connectivity 13.6.
-
Chapter 13 Management Network Connectivity 13.6.2 Link Access Protocol on the D Channel 13.6.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 15454 SDCC as OSI-only.
-
Chapter 13 Management Network Connectivity 13.6.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.
-
Chapter 13 Management Network Connectivity 13.6.3 OSI Connectionless Network Service Table 13-8 NSAP Fields (continued) Field Definition Description System System identifier The ONS 15454 system identifier is set to its IEEE 802.3 MAC address. Each ONS 15454 supports three OSI virtual routers. Each router NSAP system identifier is the ONS 15454 IEEE 802.3 MAC address + n, where n = 0 to 2. For the primary virtual router, n = 0.
-
Chapter 13 Management Network Connectivity 13.6.4 OSI Routing Figure 13-21 OSI Main Setup This address is also the Router 1 primary manual area address, which is viewed and edited on the Provisioning > OSI > Routers subtab. See the “13.6.7 OSI Virtual Routers” section on page 13-41 for information about the OSI router and manual area addresses in CTC. 13.6.4 OSI Routing OSI architecture includes ESs and ISs.
-
Chapter 13 Management Network Connectivity 13.6.4 OSI Routing In OSI networking, discovery is based on announcements. An ES uses the ES-IS protocol end system hello (ESH) message to announce its presence to ISs and ESs connected to the same network. Any ES or IS that is listening for ESHs gets a copy. ISs store the NSAP address and the corresponding subnetwork address pair in routing tables. ESs might store the address, or they might wait to be informed by ISs when they need such information.
-
Chapter 13 Management Network Connectivity 13.6.4 OSI Routing • Intermediate System Level 1/Level 2—The ONS 15454 performs IS functions. It communicates with IS and ES nodes that reside within its OSI area. It also communicates with IS L1/L2 nodes that reside in other OSI areas. This option should not be provisioned unless the node is connected to another IS L1/L2 node that resides in a different OSI area. The node must also be connected to all nodes within its area that are provisioned as IS L1/L2.
-
Chapter 13 Management Network Connectivity 13.6.5 TARP 13.6.5 TARP TARP is used when TL1 target identifiers (TIDs) must be translated to NSAP addresses. The TID-to-NSAP translation occurs by mapping TIDs to the NETs, then deriving NSAPs from the NETs by using the NSAP selector values (Table 13-8 on page 13-32). TARP uses a selective PDU propagation methodology in conjunction with a distributed database (that resides within the NEs) of TID-to-NET mappings.
-
Chapter 13 Management Network Connectivity 13.6.5 TARP Table 13-10 TARP PDU Types (continued) Type Description Actions 3 Sent as a response to Type 1, Type 2, or After a TARP Request (Type 1 or 2) PDU is received, Type 5 PDUs. a TARP Type 3 PDU is sent to the request originator. Type 3 PDUs do not use the TARP propagation procedures. 4 Sent as a notification when a change occurs locally, for example, a TID or NSAP change. It might also be sent when an NE initializes.
-
Chapter 13 Management Network Connectivity 13.6.5 TARP Table 13-12 TARP Processing Flow Process Find a NET that matches a TID Find a TID that matches a NET General TARP Flow 1. TARP checks its TDC for a match. If a match is found, TARP returns the result to the requesting application. 2. If no match is found, a TARP Type 1 PDU is generated and Timer T1 is started. 3. If Timer T1 expires before a match if found, a Type 2 PDU is generated and Timer T2 is started. 4.
-
Chapter 13 Management Network Connectivity 13.6.6 TCP/IP and OSI Mediation Figure 13-23 Manual TARP Adjacencies DCN Generic router Manual adjacency 131957 DCN 13.6.5.4 Manual TID to NSAP Provisioning TIDs can be manually linked to NSAPs and added to the TDC. Static TDC entries are similar to static routes. For a specific TID, you force a specific NSAP. Resolution requests for that TID always return that NSAP. No TARP network propagation or instantaneous replies are involved.
-
Chapter 13 Management Network Connectivity 13.6.7 OSI Virtual Routers Figure 13-24 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.
-
Chapter 13 Management Network Connectivity 13.6.7 OSI Virtual Routers Figure 13-26 Provisioning OSI Routers Each router has an editable manual area address and a unique NSAP System ID that is set to the node MAC address + n. For Router 1, n = 0. For Router 2, n = 1. For Router 3, n = 2. Each router can be enabled and connected to different OSI routing areas. However, Router 1 is the primary router, and it must be enabled before Router 2 and Router 3 can be enabled.
-
Chapter 13 Management Network Connectivity 13.6.8 IP-over-CLNS Tunnels Table 13-13 OSI Virtual Router Constraints Routing Mode IS L1 Router 1 Router 2 Router 3 per area IS L1/L2 per area DCC per IS End System Yes No No — — — IS L1 Yes Yes Yes 250 — 40 IS L1/L2 Yes Yes Yes 250 50 40 Each OSI virtual router has a primary manual area address. You can also create two additional manual area addresses.
-
Chapter 13 Management Network Connectivity 13.6.8 IP-over-CLNS Tunnels Figure 13-27 IP-over-CLNS Tunnel Flow NE-D NE-C NE-B NE-A (GNE) EMS 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 SNMP RMON 13.6.8.
-
Chapter 13 Management Network Connectivity 13.6.8 IP-over-CLNS Tunnels Table 13-14 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.
-
Chapter 13 Management Network Connectivity 13.6.8 IP-over-CLNS Tunnels Figure 13-28 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.
-
Chapter 13 Management Network Connectivity 13.6.8 IP-over-CLNS Tunnels 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 13-29 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.10/24 39.840F.80.111111.0000.1111.1111.
-
Chapter 13 Management Network Connectivity 13.6.8 IP-over-CLNS Tunnels ONS NE 1 IP-over-CLNS tunnel provisioning: • Destination: Router 2 IP address • Mask: 255.255.255.255 for host route (CTC 1 only), or 255.255.255.0 for subnet route (all CTC computers on the same subnet) • NSAP: Other vender GNE NSAP address • Metric: 110 • Tunnel Type: Cisco IP Router 2 IP-over-CLNS tunnel provisioning (sample Cisco IOS provisioning): ip routing clns routing interface ctunnel 102 ip address 10.10.30.30 255.
-
Chapter 13 Management Network Connectivity 13.6.9 OSI/IP Networking Scenarios Figure 13-30 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.
-
Chapter 13 Management Network Connectivity 13.6.9 OSI/IP Networking Scenarios • All ONS 15454 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 15454 NEs participating in the OSI network. 13.6.9.1 OSI/IP Scenario 1: IP OSS, IP DCN, ONS GNE, IP DCC, and ONS ENE Figure 13-31 shows OSI/IP Scenario 1, the current ONS 15454 IP-based implementation, with an IP DCN, IP-over-PPP DCC, and OSPF routing.
-
Chapter 13 Management Network Connectivity 13.6.9 OSI/IP Networking Scenarios Figure 13-32 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 15454 and other vendor NEs using TL1 and FTP. 2 The ONS 15454 GNE performs mediation for other vendor NEs.
-
Chapter 13 Management Network Connectivity 13.6.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 in the previous paragraph. The ONS 15454 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 15454 GNE. The GNE mediation translates between FTAM to FTP. 13.
-
Chapter 13 Management Network Connectivity 13.6.9 OSI/IP Networking Scenarios Figure 13-33 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 IP and OSI/PPP/DCC ONS NE 2 4 Other vendor NE OSI/LAP-D/DCC Other vendor NE 131933 ONS NE 1 1 The IP OSS manages the ONS 15454 and other vendor NEs using TL1 and FTP.
-
Chapter 13 Management Network Connectivity 13.6.9 OSI/IP Networking Scenarios Figure 13-34 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.
-
Chapter 13 Management Network Connectivity 13.6.9 OSI/IP Networking Scenarios Figure 13-35 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 15454 and other vendor NEs using TL1 and FTP.
-
Chapter 13 Management Network Connectivity 13.6.9 OSI/IP Networking Scenarios Figure 13-36 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 15454 and other vendor NEs using TL1 and FTP. 2 The other vendor GNE performs mediation on TL1 and FTP, so DCCs are OSI-only.
-
Chapter 13 Management Network Connectivity 13.6.9 OSI/IP Networking Scenarios Figure 13-37 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 15454 and other vendor NEs using TL1 and FTP. 2 OSS IP traffic is tunneled through the DCN to the ONS 15454 GNE.
-
Chapter 13 Management Network Connectivity 13.6.9 OSI/IP Networking Scenarios Figure 13-38 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 15454 NEs are managed by CTC/CTM only (TL1/FTP is not used).
-
Chapter 13 Management Network Connectivity 13.6.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 15454 NEs is carried over an IP-over-CLNS tunnel. A static route is configured on the ONS 15454 that terminates the tunnel (ONS 15454 NE 1) so that downstream ONS 15454 NEs (ONS 15454 NE 2 and 3) know how to reach CTC/CTM. 13.6.9.
-
Chapter 13 Management Network Connectivity 13.6.9 OSI/IP Networking Scenarios Figure 13-39 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).
-
Chapter 13 Management Network Connectivity 13.6.10 Provisioning OSI in CTC 13.6.10 Provisioning OSI in CTC Table 13-15 shows the OSI actions that are performed from the node view Provisioning tab. Refer to the Cisco ONS 15454 Procedure Guide for OSI procedures and tasks. Table 13-15 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.
-
Chapter 13 Management Network Connectivity 13.7 IPv6 Network Compatibility 13.7 IPv6 Network Compatibility Cisco ONS 15xxx products can function in an IPv6 network when an internet router that supports Network Address Translation - Protocol Translation (NAT-PT) is positioned between the GNE, such as an ONS 15454, and the client workstation. NAT-PT is defined in RFC-2766.
-
CH A P T E R 14 Alarm Monitoring and Management This chapter describes Cisco Transport Controller (CTC) alarm management. To troubleshoot specific alarms, refer to the Cisco ONS 15454 Troubleshooting Guide. Chapter topics include: • 14.1 Overview, page 14-1 • 14.2 LCD Alarm Counts, page 14-1 • 14.3 Alarm Information, page 14-2 • 14.4 Alarm Severities, page 14-9 • 14.5 Alarm Profiles, page 14-9 • 14.6 Alarm Suppression, page 14-13 • 14.7 External Alarms and Controls, page 14-14 14.
-
Chapter 14 Alarm Monitoring and Management 14.3 Alarm Information The ONS 15454 has a one-button update for some commonly viewed alarm counts. If you press the Slot button once and then wait eight seconds, the display automatically changes from a slot alarm count to a slot alarm summary. If you press the Port button to toggle to port-level display, you can use the Port button to toggle to a specific slot and to view each port’s port-level alarm count. Figure 14-1 shows the LCD panel layout.
-
Chapter 14 Alarm Monitoring and Management 14.3 Alarm Information Table 14-1 Note Alarms Column Descriptions (continued) Column Information Recorded Shelf For dense wavelength division multiplexing (DWDM) configurations, the shelf where the alarmed object is located. Visible in network view. Slot Slot where the alarm occurred (appears only in network and node view). Port Port where the alarm is raised. For STSTerm and VTTerm, the port refers to the upstream card it is partnered with.
-
Chapter 14 Alarm Monitoring and Management 14.3.1 Viewing Alarms With Each Node’s Time Zone 14.3.1 Viewing Alarms With Each Node’s Time Zone By default, alarms and conditions are displayed with the time stamp of the CTC workstation where you are viewing them. But you can set the node to report alarms (and conditions) using the time zone where the node is located by clicking Edit > Preferences, and clicking the Display Events Using Each Node’s Timezone check box. 14.3.
-
Chapter 14 Alarm Monitoring and Management 14.3.4 Viewing Alarm-Affected Circuits 14.3.4 Viewing Alarm-Affected Circuits A user can view which ONS 15454 circuits are affected by a specific alarm by positioning the cursor over the alarm in the Alarm window and right-clicking. A shortcut menu appears (Figure 14-2). When the user selects the Select Affected Circuits option, the Circuits window opens to show the circuits that are affected by the alarm. Figure 14-2 Select Affected Circuits Option 14.3.
-
Chapter 14 Alarm Monitoring and Management 14.3.6 Controlling the Conditions Display 14.3.6 Controlling the Conditions Display You can control the display of the conditions on the Conditions window. Table 14-4 shows the actions you can perform in the window. Table 14-4 Conditions Display Button Action Retrieve Retrieves the current set of all existing fault conditions, as maintained by the alarm manager, from the ONS 15454.
-
Chapter 14 Alarm Monitoring and Management 14.3.7 Viewing History Table 14-5 Conditions Column Description (continued) Column Information Recorded Path Width Width of the data path. Sev 1 Severity level: CR (Critical), MJ (Major), MN (Minor), NA (Not Alarmed), NR (Not Reported). SA1 Indicates a service-affecting alarm (when checked). Cond The error message/alarm name; these names are alphabetically defined in the “Alarm Troubleshooting” chapter of the Cisco ONS 15454 Troubleshooting Guide.
-
Chapter 14 Alarm Monitoring and Management 14.3.7 Viewing History If you check the History window Alarms check box, you display the node history of alarms. If you check the Events check box, you display the node history of Not Alarmed and transient events (conditions). If you check both check boxes, you retrieve node history for both. 14.3.7.1 History Column Descriptions Table 14-6 lists the History window column headings and the information recorded in each column.
-
Chapter 14 Alarm Monitoring and Management 14.3.8 Alarm History and Log Buffer Capacities on the card in the History > Card window, or a history of alarms, conditions, and transients that have occurred during your login session in the History > Session window. You can also filter the severities and occurrence period in these history windows. 14.3.8 Alarm History and Log Buffer Capacities The ONS 15454 alarm history log, stored in the TCC2/TCC2P RSA memory, contains four categories of alarms.
-
Chapter 14 Alarm Monitoring and Management 14.5.1 Creating and Modifying Alarm Profiles CTC can store up to ten active alarm profiles at any time to apply to the node. Custom profiles can take eight of these active profile positions. Two other profiles, Default profile and Inherited profile, are reserved by the NE, and cannot be edited.The reserved Default profile contains Telcordia GR-474 severities.
-
Chapter 14 Alarm Monitoring and Management 14.5.2 Alarm Profile Buttons Note Up to 10 profiles, including the two reserved profiles (Inherited and Default) can be stored in CTC. Wherever it is applied, the Default alarm profile sets severities to standard Telcordia GR-253 settings. In the Inherited profile, alarms inherit, or copy, severity from the next-highest level. For example, a card with an Inherited alarm profile copies the severities used by the node housing the card.
-
Chapter 14 Alarm Monitoring and Management 14.5.3 Alarm Profile Editing 14.5.3 Alarm Profile Editing Table 14-8 lists and describes the five profile-editing options available when you right-click an alarm item in the profile column. Table 14-8 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 profile that contains the same alarm severity settings as the profile being cloned.
-
Chapter 14 Alarm Monitoring and Management 14.5.6 Applying Alarm Profiles 14.5.6 Applying Alarm Profiles In CTC node view, the Alarm Behavior window displays alarm profiles for the node. In card view, the Alarm Behavior window displays the alarm profiles for the selected card. Alarm profiles form a hierarchy. A node-level alarm profile applies to all cards in the node except cards that have their own profiles.
-
Chapter 14 Alarm Monitoring and Management 14.6.2 Alarms Suppressed by User Command While the facility is in the OOS,MT state, any alarms or conditions that are raised and suppressed on it (for example, a transmit failure [TRMT] alarm) are reported in the Conditions window and show their normal severity in the Sev column. The suppressed alarms are not shown in the Alarms and History windows. (These windows only show AS-MT).
-
Chapter 14 Alarm Monitoring and Management 14.7.2 User Defined Alarm Types • Raised When—Open means that the normal condition is to not have current flowing through the contact, and the alarm is generated when current does flow; closed means that the normal condition is to have current flowing through the contact, and the alarm is generated when current stops flowing. • Description—CTC alarm log description (up to 63 characters).
-
Chapter 14 Alarm Monitoring and Management 14.7.3 External Controls Cisco ONS 15454 Reference Manual, R8.5.
-
CH A P T E R 15 Performance Monitoring Performance monitoring (PM) parameters are used by service providers to gather, store, set thresholds for, and report performance data for early detection of problems. In this chapter, PM parameters and concepts are defined for electrical cards, ethernet cards, optical cards, optical multirate cards, and storage access networking (SAN) cards in the Cisco ONS 15454. For information about enabling and viewing PM values, refer to the Cisco ONS 15454 Procedure Guide.
-
Chapter 15 Performance Monitoring 15.1 Threshold Performance Monitoring 15.1 Threshold Performance Monitoring Thresholds are used to set error levels for each PM parameter. You can set individual PM threshold values from the Cisco Transport Controller (CTC) card view Provisioning tab. For procedures on provisioning card thresholds, such as line, path, and SONET thresholds, refer to the Cisco ONS 15454 Procedure Guide.
-
Chapter 15 Performance Monitoring 15.2 Intermediate Path Performance Monitoring Table 15-1 Card Electrical Cards that Report RX and TX Direction for TCAs Line Path Near End Far End Near End Far End RX TX RX TX RX TX RX TX DS1-14 YES — YES — YES YES YES — DS1N-14 YES — YES — YES YES YES — Due to memory limitations and the number of TCAs generated by different platforms, you can manually add/modify the following two properties to the platform property file (CTC.
-
Chapter 15 Performance Monitoring 15.3 Pointer Justification Count Performance Monitoring ONS 15454 Software R3.0 and higher allows LTE cards to monitor near-end PM data on individual synchronous transport signal (STS) payloads by enabling IPPM. After enabling IPPM provisioning on the line card, service providers can monitor large amounts of STS traffic through intermediate nodes, thus making troubleshooting and maintenance activities more efficient.
-
Chapter 15 Performance Monitoring 15.4 Performance Monitoring Parameter Definitions 15.4 Performance Monitoring Parameter Definitions Table 15-3 gives definitions for each type of PM parameter found in this chapter. Table 15-3 Performance Monitoring Parameters Parameter Definition AISS-P AIS Seconds Path (AISS-P) is a count of one-second intervals containing one or more alarm indication signal (AIS) defects.
-
Chapter 15 Performance Monitoring 15.4 Performance Monitoring Parameter Definitions Table 15-3 Performance Monitoring Parameters (continued) Parameter Definition CVP-P Code Violation Path (CVP-P) is a code violation parameter for M23 applications. CVP-P is a count of P-bit parity errors occurring in the accumulation period. CV-S Section Coding Violation (CV-S) is a count of bit interleaved parity (BIP) errors detected at the section layer (that is, using the B1 byte in the incoming SONET signal).
-
Chapter 15 Performance Monitoring 15.4 Performance Monitoring Parameter Definitions Table 15-3 Performance Monitoring Parameters (continued) Parameter Definition ESR-SM Section Monitoring Errored Seconds Ratio (ESR-SM) indicates the errored seconds ratio recorded in the OTN section during the PM time interval. ES-S Section Errored Seconds (ES-S) is a count of the number of seconds when at least one section-layer BIP error was detected or an SEF or loss of signal (LOS) defect was present.
-
Chapter 15 Performance Monitoring 15.4 Performance Monitoring Parameter Definitions Table 15-3 Performance Monitoring Parameters (continued) Parameter Definition LOFC Loss of Frame Count (LOFC) LOSS-L Line Loss of Signal (LOSS-L) is a count of one-second intervals containing one or more LOS defects. NIOS Non-Idle Ordered Sets (NIOS) is a count of received packets containing non-idle ordered sets.
-
Chapter 15 Performance Monitoring 15.4 Performance Monitoring Parameter Definitions Table 15-3 Performance Monitoring Parameters (continued) Parameter Definition PPJC-PGEN-P Positive Pointer Justification Count, STS Path Generated (PPJC-PGEN-P) is a count of the positive pointer justifications generated for a particular path to reconcile the frequency of the SPE with the local clock.
-
Chapter 15 Performance Monitoring 15.4 Performance Monitoring Parameter Definitions Table 15-3 Performance Monitoring Parameters (continued) Parameter Definition PSD-R In a four-fiber BLSR, Protection Switching Duration-Ring (PSD-R) is a count of the seconds that the protection line was used to carry service. A count is only incremented if ring switching is used.
-
Chapter 15 Performance Monitoring 15.4 Performance Monitoring Parameter Definitions Table 15-3 Performance Monitoring Parameters (continued) Parameter Definition SES-SM Section Monitoring Severely Errored Seconds (SES-SM) indicates the severely errored seconds recorded in the OTN section during the PM time interval. SESR-PM Path Monitoring Severely Errored Seconds Ratio (SESR-PM) indicates the severely errored seconds ratio recorded in the OTN path during the PM time interval.
-
Chapter 15 Performance Monitoring 15.5 Performance Monitoring for Electrical Cards Table 15-3 Performance Monitoring Parameters (continued) Parameter Definition UASP-P Unavailable Seconds Path (UASP-P) is a count of one-second intervals when the DS-3 path is unavailable. A DS-3 path becomes unavailable when ten consecutive SESP-Ps occur. The ten SESP-Ps are included in unavailable time.
-
Chapter 15 Performance Monitoring 15.5.1 EC1-12 Card Performance Monitoring Parameters Note Figure 15-3 The XX in Figure 15-2 represents all PMs listed in Table 15-4 with the given prefix and/or suffix.
-
Chapter 15 Performance Monitoring 15.5.2 DS1/E1-56 Card Performance Monitoring Parameters Note If the CV-L(NE and FE) falls in the range 51-61 for EC1,then, the user might see discrepancy in the SES and the UAS-L values. However, ES-L will be in the nearest accuracy.
-
Chapter 15 Performance Monitoring 15.5.
-
Chapter 15 Performance Monitoring 15.5.3 DS1-14 and DS1N-14 Card Performance Monitoring Parameters Table 15-5 lists the PM parameters for the DS1/E1-56 card.
-
Chapter 15 Performance Monitoring 15.5.
-
Chapter 15 Performance Monitoring 15.5.4 DS3-12 and DS3N-12 Card Performance Monitoring Parameters 15.5.3.1 DS-1 Facility Data Link Performance Monitoring Facility Data Link (FDL) performance monitoring enables an ONS 15454 DS1N-14 card to calculate and report DS-1 error rate performance measured at both the near-end and far-end of the FDL. The far-end information is reported as received on the FDL in a performance report message (PRM) from an intelligent channel service unit (CSU).
-
Chapter 15 Performance Monitoring 15.5.
-
Chapter 15 Performance Monitoring 15.5.5 DS3-12E and DS3N-12E Card Performance Monitoring Parameters Figure 15-10 Monitored Signal Types for the DS3-12E and DS3N-12E Cards PTE PTE ONS 15454 ONS 15454 DS3 Signal DS3 Signal Fiber DS3E OC-N OC-N DS3E 78977 DS3E Path (DS3 XX) PMs Near and Far End Supported STS Path (STS XX-P) PMs Near and Far End Supported Note The XX in Figure 15-10 represents all PMs listed in Table 15-8 with the given prefix and/or suffix.
-
Chapter 15 Performance Monitoring 15.5.6 DS3i-N-12 Card Performance Monitoring Parameters Table 15-8 DS3-12E and DS3N-12E Card PMs Line (NE) Path (NE) STS Path (NE) Path (FE)1 STS Path (FE) CV-L ES-L SES-L LOSS-L AISS-P CV-P ES-P SAS-P2 SES-P UAS-P CVCP-P ESCP-P SASCP-P3 SESCP-P UASCP-P CV-P ES-P SES-P UAS-P FC-P CVCP-PFE ESCP-PFE SASCP-P SESCP-PFE UASCP-PFE CV-PFE ES-PFE SES-PFE UAS-PFE FC-PFE 1. The C-bit PMs (PMs that contain the text “CP-P”) are applicable only if the line format is C-bit.
-
Chapter 15 Performance Monitoring 15.5.
-
Chapter 15 Performance Monitoring 15.5.7 DS3XM-6 Card Performance Monitoring Parameters 15.5.7 DS3XM-6 Card Performance Monitoring Parameters Figure 15-14 shows the signal types that support near-end and far-end PMs.
-
Chapter 15 Performance Monitoring 15.5.
-
Chapter 15 Performance Monitoring 15.5.8 DS3XM-12 Card Performance Monitoring Parameters 15.5.8 DS3XM-12 Card Performance Monitoring Parameters Figure 15-16 shows the signal types that support near-end and far-end PMs.
-
Chapter 15 Performance Monitoring 15.5.
-
Chapter 15 Performance Monitoring 15.5.9 DS3/EC1-48 Card Performance Monitoring Parameters 15.5.9 DS3/EC1-48 Card Performance Monitoring Parameters Figure 15-18 shows the signal types that support near-end and far-end PMs.
-
Chapter 15 Performance Monitoring 15.5.
-
Chapter 15 Performance Monitoring 15.6 Performance Monitoring for Ethernet Cards Note If the CV-L(NE and FE) falls in the range 51-61 for DS3,then, the user might see discrepancy in the SES and the UAS-L values. However, ES-L will be in the nearest accuracy.
-
Chapter 15 Performance Monitoring 15.6.1 E-Series Ethernet Card Performance Monitoring Parameters Table 15-13 E-Series Ethernet Statistics Parameters (continued) Parameter Definition etherStatsUndersizePkts The total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed.
-
Chapter 15 Performance Monitoring 15.6.1 E-Series Ethernet Card Performance Monitoring Parameters 15.6.1.2 E-Series Ethernet Utilization Window The Utilization window shows the percentage of transmit (Tx) and receive (Rx) line bandwidth used by the Ethernet ports during consecutive time segments. The Mode field displays the real-time mode status, such as 100 Full, which is the mode setting configured on the E-Series port.
-
Chapter 15 Performance Monitoring 15.6.2 G-Series Ethernet Card Performance Monitoring Parameters 15.6.2 G-Series Ethernet Card Performance Monitoring Parameters CTC provides Ethernet performance information, including line-level parameters, port bandwidth consumption, and historical Ethernet statistics. The G-Series Ethernet performance information is divided into the Statistics, Utilization, and History tabbed windows within the card view Performance tab window. 15.6.2.
-
Chapter 15 Performance Monitoring 15.6.2 G-Series Ethernet Card Performance Monitoring Parameters Table 15-16 Note G-Series Ethernet Statistics Parameters (continued) Parameter Definition Rx Unicast Packets Number of unicast packets received since the last counter reset. Tx Unicast Packets Number of unicast packets transmitted. Rx Multicast Packets Number of multicast packets received since the last counter reset. Tx Multicast Packets Number of multicast packets transmitted.
-
Chapter 15 Performance Monitoring 15.6.3 ML-Series Ethernet Card Performance Monitoring Parameters 15.6.2.3 G-Series Ethernet History Window The Ethernet History window lists past Ethernet statistics for the previous time intervals. Depending on the selected time interval, the History window displays the statistics for each port for the number of previous time intervals as shown in Table 15-15 on page 15-31. The listed parameters are defined in Table 15-16 on page 15-32. 15.6.
-
Chapter 15 Performance Monitoring 15.6.3 ML-Series Ethernet Card Performance Monitoring Parameters Table 15-17 ML-Series Ether Ports PM Parameters (continued) Parameter Definition dot3StatsAlignmentErrors A count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. dot3StatsFCSErrors A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check.
-
Chapter 15 Performance Monitoring 15.6.3 ML-Series Ethernet Card Performance Monitoring Parameters Table 15-17 ML-Series Ether Ports PM Parameters (continued) Parameter Definition etherStatsMulticastPkts 1 The total number of good packets received that were directed to a multicast address. Note that this number does not include packets directed to the broadcast address.
-
Chapter 15 Performance Monitoring 15.6.3 ML-Series Ethernet Card Performance Monitoring Parameters 15.6.3.3 ML-Series Card Ether Ports History Window The Ethernet Ether Ports History window lists past Ethernet statistics for the previous time intervals. Depending on the selected time interval, the History window displays the statistics for each port for the number of previous time intervals as shown in Table 15-15 on page 15-31. The listed parameters are defined in Table 15-17 on page 15-34. 15.6.3.
-
Chapter 15 Performance Monitoring 15.6.3 ML-Series Ethernet Card Performance Monitoring Parameters Table 15-19 ML-Series POS Ports Parameters for GFP-F Mode Parameter Meaning etherStatsDropEvents Number of received frames dropped at the port level. rx PktsDroppedInternal Congestion Number of received packets dropped due to overflow in the frame buffer. gfpStatsRxFrame Number of received GFP frames. gfpStatsTxFrame Number of transmitted GFP frames.
-
Chapter 15 Performance Monitoring 15.6.3 ML-Series Ethernet Card Performance Monitoring Parameters Table 15-20 ML-Series RPR Span Parameters for 802.17 MIB (continued) Parameter Meaning gfpStatsRxTypeInvalid Number of receive packets dropped due to Client Data Frame UPI errors. rprSpanStatsInUcastClassC Frames Number of received (PHY to MAC) classC unicast frames. rprSpanStatsInUcastClassC Octets Number of received (PHY to MAC) classC unicast octets.
-
Chapter 15 Performance Monitoring 15.6.3 ML-Series Ethernet Card Performance Monitoring Parameters Table 15-20 ML-Series RPR Span Parameters for 802.17 MIB (continued) Parameter Meaning rprSpanStatsInOamOrgFrames Number of received (PHY to MAC) OAM Org frames processed by this MAC. rprSpanStatsInTopoAtdFrames Number of received (PHY to MAC) Topology ATD frames processed by this MAC.
-
Chapter 15 Performance Monitoring 15.6.3 ML-Series Ethernet Card Performance Monitoring Parameters Table 15-20 ML-Series RPR Span Parameters for 802.17 MIB (continued) Parameter Meaning rprSpanStatsOutCtrlFrames The number of transmitted (MAC to PHY) control frames generated by this MAC. This does not include control frames in transit, i.e. a multicast control frame received from a ringlet will be counted as In but not Out. This does not include Fairness or idle frames.
-
Chapter 15 Performance Monitoring 15.6.3 ML-Series Ethernet Card Performance Monitoring Parameters Table 15-20 ML-Series RPR Span Parameters for 802.17 MIB (continued) Parameter Meaning rprClientStatsInUcastClassA Octets Number of MAC to client classA unicast octets. rprClientStatsInMcastClassA Frames Number of MAC to client classA multicast and broadcast frames. rprClientStatsInMcastClassA Octets Number of MAC to client classA multicast and broadcast octets.
-
Chapter 15 Performance Monitoring 15.6.4 CE-Series Ethernet Card Performance Monitoring Parameters Table 15-20 ML-Series RPR Span Parameters for 802.17 MIB (continued) Parameter Meaning rprClientStatsOutBcastFrames Number of client to MAC broadcast frames. This is used only when deriving the multicast and broadcast packet counters for the interface MIB.
-
Chapter 15 Performance Monitoring 15.6.4 CE-Series Ethernet Card Performance Monitoring Parameters 15.6.4.1 CE-Series Card Ether Port Statistics Window The Ethernet Ether Ports Statistics window lists Ethernet parameters at the line level. The Statistics window provides buttons to change the statistical values shown. The Baseline button resets the displayed statistics values to zero. The Refresh button manually refreshes statistics. Auto-Refresh sets a time interval at which automatic refresh occurs.
-
Chapter 15 Performance Monitoring 15.6.4 CE-Series Ethernet Card Performance Monitoring Parameters Table 15-21 CE-Series Ether Port PM Parameters (continued) Parameter Definition dot3StatsSingleCollision A count of successfully transmitted frames on a particular interface for Frames2 which transmission is inhibited by exactly on collision. dot3StatsFrameTooLong A count of frames received on a particular interface that exceed the maximum permitted frame size.
-
Chapter 15 Performance Monitoring 15.6.4 CE-Series Ethernet Card Performance Monitoring Parameters Table 15-21 CE-Series Ether Port PM Parameters (continued) Parameter Definition etherStatsOctets The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets etherStatsCollisions2 Number of transmit packets that are collisions; the port and the attached device transmitting at the same time caused collisions.
-
Chapter 15 Performance Monitoring 15.6.4 CE-Series Ethernet Card Performance Monitoring Parameters Note Line utilization numbers express the average of ingress and egress traffic as a percentage of capacity. 15.6.4.3 CE-Series Card Ether Ports History Window The Ethernet Ether Ports History window lists past Ethernet statistics for the previous time intervals.
-
Chapter 15 Performance Monitoring 15.7 Performance Monitoring for Optical Cards Table 15-22 CE-Series Card POS Ports Parameters (continued) Parameter Definition gfpStatsCSFRaised ifInPayloadCrcErrors Number of GFP Client signal fail frames detected at the GFP-T receiver. 1 Received payload CRC errors. ifOutPayloadCrcErrors1 Transmitted payload CRC errors. hdlcPktDrops Number of received packets dropped before input. 1. Applicable only for CE100T-8, CE-MR-10 2. Applicable only for CE1000-4 15.6.
-
Chapter 15 Performance Monitoring 15.7 Performance Monitoring for Optical Cards Figure 15-20 Monitored Signal Types for the OC-3 Cards PTE PTE ONS 15454 ONS 15454 OC-3 Signal OC-3 Signal Fiber OC48 OC48 OC-3 78985 OC-3 STS Path (STS XX-P) PMs Near and Far End Supported Note The XX in Figure 15-20 represents all PMs listed in Table 15-23, Table 15-24, and Table 15-25 with the given prefix and/or suffix.
-
Chapter 15 Performance Monitoring 15.7 Performance Monitoring for Optical Cards Table 15-23 OC-3 Card PMs Section (NE) Line (NE) STS Path (NE) Line (FE) STS Path (FE)1 CV-S ES-S SES-S SEF-S CV-L ES-L SES-L UAS-L FC-L PSC (1+1) PSD (1+1) CV-P ES-P SES-P UAS-P FC-P PPJC-PDET NPJC-PDET PPJC-PGEN NPJC-PGEN PPJC-PDET-P PPJC-PGEN-P PJC-DIFF CV-LFE ES-LFE SES-LFE UAS-LFE FC-LFE CV-PFE ES-PFE SES-PFE UAS-PFE FC-PFE 1. The STS Path (FE) PMs are valid only for the OC3-4 card on ONS 15454.
-
Chapter 15 Performance Monitoring 15.
-
Chapter 15 Performance Monitoring 15.9 Performance Monitoring for Storage Access Networking Cards Figure 15-22 PM Read Points for the MRC-12 and the MRC-2.5G-4 Cards XC Card ONS 15454 MRC-12/MRC-2.
-
Chapter 15 Performance Monitoring 15.9.1 FC_MR-4 Statistics Window CTC provides FC_MR-4 performance information, including line-level parameters, port bandwidth consumption, and historical statistics. The FC_MR-4 card performance information is divided into the Statistics, Utilization, and History tabbed windows within the card view Performance tab window. 15.9.1 FC_MR-4 Statistics Window The Statistics window lists parameters at the line level.
-
Chapter 15 Performance Monitoring 15.9.2 FC_MR-4 Utilization Window Parameter Definition gfpStatsRxDistanceExtBuffers Number of buffer credit received for GFP-T receiver (valid only if distance extension is enabled). gfpStatsTxDistanceExtBuffers Number of buffer credit transmitted for GFP-T transmitter (valid only if distance extension is enabled). mediaIndStatsRxFramesTruncated Number of Fibre Channel frames received with frame size <= 36 bytes.
-
Chapter 15 Performance Monitoring 15.9.3 FC_MR-4 History Window Note Line utilization numbers express the average of ingress and egress traffic as a percentage of capacity. 15.9.3 FC_MR-4 History Window The History window lists past FC_MR-4 statistics for the previous time intervals. Depending on the selected time interval, the History window displays the statistics for each port for the number of previous time intervals as shown in Table 15-30.
-
Chapter 15 Performance Monitoring 15.9.3 FC_MR-4 History Window Cisco ONS 15454 Reference Manual, R8.5.
-
CH A P T E R 16 SNMP This chapter explains Simple Network Management Protocol (SNMP) as implemented by the Cisco ONS 15454. For SNMP setup information, refer to the Cisco ONS 15454 Procedure Guide. Chapter topics include: • 16.1 SNMP Overview, page 16-1 • 16.2 Basic SNMP Components, page 16-2 • 16.3 SNMP External Interface Requirement, page 16-4 • 16.4 SNMP Version Support, page 16-4 • 16.5 SNMP Message Types, page 16-4 • 16.6 SNMP Management Information Bases, page 16-5 • 16.
-
Chapter 16 SNMP 16.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 In Software Release 8.
-
Chapter 16 SNMP 16.2 Basic SNMP Components Figure 16-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.
-
Chapter 16 SNMP 16.3 SNMP External Interface Requirement 16.3 SNMP External Interface Requirement Since all SNMP requests come from a third-party application, the only external interface requirement is that a third-party SNMP client application should have the ability to upload RFC 3273 SNMP MIB variables in the etherStatsHighCapacityTable, etherHistoryHighCapacityTable, or mediaIndependentTable. 16.4 SNMP Version Support The ONS 15454 supports SNMPv1 and SNMPv2c traps and get requests.
-
Chapter 16 SNMP 16.6 SNMP Management Information Bases 16.6 SNMP Management Information Bases A managed object, sometimes called a MIB object, is one of many specific characteristics of a managed device. The MIB consists of hierarchically organized object instances (variables) that are accessed by network-management protocols such as SNMP. Section 16.6.1 lists the IETF standard MIBs implemented in the ONS 15454 SNMP agent. Section 16.6.2 lists the proprietary MIBs implemented in the ONS 15454. 16.6.
-
Chapter 16 SNMP 16.6.2 Proprietary ONS 15454 MIBs Table 16-2 IETF Standard MIBs Implemented in the ONS 15454 System (continued) RFC1 Number Module Name Title/Comments 2674 P-BRIDGE-MIB-rfc2674.mib Q-BRIDGE-MIB-rfc2674.
-
Chapter 16 SNMP 16.6.3 Generic Threshold and Performance Monitoring MIBs 16.6.3 Generic Threshold and Performance Monitoring MIBs A MIB called CERENT-GENERIC-PM-MIB allows network management stations (NMS) to use a single, generic MIB for accessing threshold and performance monitoring data of different interface types. The MIB is generic in the sense that it is not tied to any particular kind of interface.
-
Chapter 16 SNMP 16.6.3 Generic Threshold and Performance Monitoring MIBs syntax of cerentGenericPmStatsCurrentIndex is type cerentLocation, defined in CERENT-TC.mib. The syntax of cerentGenericPmStatsCurrentMonType is type cerentMonitor, defined in CERENT-TC.mib. The syntax of cerentGenericPmStatsCurrentPeriod is type cerentPeriod, defined in CERENT-TC.mib.
-
Chapter 16 SNMP 16.7 SNMP Trap Content 16.7 SNMP Trap Content The ONS 15454 uses SNMP traps to generate all alarms and events, such as raises and clears. The traps contain the following information: • Object IDs that uniquely identify each event with information about the generating entity (the slot or port; synchronous transport signal [STS] and Virtual Tributary [VT]; bidirectional line switched ring [BLSR], Spanning Tree Protocol [STP], etc.).
-
Chapter 16 SNMP 16.7.2 Variable Trap Bindings 16.7.2 Variable Trap Bindings Each SNMP trap contains variable bindings that are used to create the MIB tables. ONS 15454 traps and variable bindings are listed in Table 16-8. For each group (such as Group A), all traps within the group are associated with all of its variable bindings.
-
Chapter 16 SNMP 16.7.2 Variable Trap Bindings Table 16-8 Group Supported ONS 15454 SNMPv2 Trap Variable Bindings (continued) Variable Trap Name(s) Associated Binding with Number SNMPv2 Variable Bindings Description (4) cerent454AlarmState The alarm severity and service-affecting status. Severities are Minor, Major, and Critical. Service-affecting statuses are Service-Affecting and Non-Service Affecting. (5) snmpTrapAddress The address of the SNMP trap.
-
Chapter 16 SNMP 16.7.2 Variable Trap Bindings Table 16-8 Group D1 (cont.) D2 Supported ONS 15454 SNMPv2 Trap Variable Bindings (continued) Variable Trap Name(s) Associated Binding with Number SNMPv2 Variable Bindings Description (5) alarmRisingThreshold When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event is generated.
-
Chapter 16 SNMP 16.7.2 Variable Trap Bindings Table 16-8 Group Supported ONS 15454 SNMPv2 Trap Variable Bindings (continued) Variable Trap Name(s) Associated Binding with Number D2 (cont.) E failureDetectedExternal ToTheNE (from CERENT-454-mib) SNMPv2 Variable Bindings Description (7) cerent454AlarmState The alarm severity and service-affecting status. Severities are Minor, Major, and Critical. Service-affecting statuses are Service-Affecting and Non-Service Affecting.
-
Chapter 16 SNMP 16.7.2 Variable Trap Bindings Table 16-8 Group Supported ONS 15454 SNMPv2 Trap Variable Bindings (continued) Variable Trap Name(s) Associated Binding with Number E (cont.) F performanceMonitor ThresholdCrossingAlert (from CERENT-454-mib) SNMPv2 Variable Bindings Description (9) cerent454AlarmAdditionalInfo Additional information for the alarm object. In the current version of the MIB, this object contains provisioned description for alarms that are external to the NE.
-
Chapter 16 SNMP 16.7.2 Variable Trap Bindings Table 16-8 Group Supported ONS 15454 SNMPv2 Trap Variable Bindings (continued) Variable Trap Name(s) Associated Binding with Number F (cont.) G All other traps (from CERENT-454-MIB) not listed above SNMPv2 Variable Bindings Description (10) cerent454ThresholdLocation Indicates whether the event occurred at the near or far end. (11) cerent454ThresholdPeriod Indicates the sampling interval period.
-
Chapter 16 SNMP 16.8 SNMP Community Names Table 16-8 Group Supported ONS 15454 SNMPv2 Trap Variable Bindings (continued) Variable Trap Name(s) Associated Binding with Number G (cont.) SNMPv2 Variable Bindings Description (8) cerent454AlarmObjectName The TL1-style user-visible name that uniquely identifies an object in the system. (9) snmpTrapAddress The address of the SNMP trap. 16.8 SNMP Community Names Community names are used to group SNMP trap destinations.
-
Chapter 16 SNMP 16.10.1 64-Bit RMON Monitoring over DCC ONS 15454 system RMON is based on the IETF-standard MIB RFC 2819 and includes the following five groups from the standard MIB: Ethernet Statistics, History Control, Ethernet History, Alarm, and Event. Certain statistics measured on the ML card are mapped to standard MIB if one exists else mapped to a non standard MIB variable. The naming convention used by the standarad/non-standard MIB is not the same as the statistics variable used by the card.
-
Chapter 16 SNMP 16.10.2 HC-RMON-MIB Support 16.10.1.2 Row Creation in cMediaIndependentHistoryControlTable SNMP row creation and deletion for the cMediaIndependentHistoryControlTable follows the same processes as for the MediaIndependentTable; only the variables differ.
-
Chapter 16 SNMP 16.10.4 History Control RMON Group 16.10.3.2 Get Requests and GetNext Requests Get requests and getNext requests for the etherStatsMulticastPkts and etherStatsBroadcastPkts columns return a value of zero because the variables are not supported by ONS 15454 Ethernet cards. 16.10.3.3 Row Deletion in etherStatsTable To delete a row in the etherStatsTable, the SetRequest PDU should contain an etherStatsStatus “invalid” value (4). The OID marks the row for deletion.
-
Chapter 16 SNMP 16.10.
-
Chapter 16 SNMP 16.10.6 Alarm RMON Group 16.10.6.1 Alarm Table The NMS uses the alarmTable to determine and provision network performance alarmable thresholds. 16.10.6.2 Row Creation in alarmTable To create a row in the alarmTable, all OIDs in the SetRequest PDU should be type OID.0. The table has a maximum number of 256 rows.
-
Chapter 16 SNMP 16.10.6 Alarm RMON Group Table 16-10 OIDs Supported in the AlarmTable (continued) No. Column Name OID Status 14 Dot3StatsSingleCollisionFrames {1.3.6.1.2.1.10.7.2.1.4} — 15 Dot3StatsMultipleCollisionFrames {1.3.6.1.2.1.10.7.2.1.5} — 16 Dot3StatsDeferredTransmissions {1.3.6.1.2.1.10.7.2.1.7} — 17 Dot3StatsLateCollisions {1.3.6.1.2.1.10.7.2.1.8} — 18 Dot3StatsExcessiveCollisions {13.6.1.2.1.10.7.2.1.9} — 19 Dot3StatsFrameTooLong {1.3.6.1.2.1.10.7.2.1.
-
Chapter 16 SNMP 16.10.7 Event RMON Group 16.10.7 Event RMON Group The Event group controls event generation and notification. It consists of two tables: the eventTable, which is a read-only list of events to be generated, and the logTable, which is a writable set of data describing a logged event. The ONS 15454 implements the logTable as specified in RFC 2819. 16.10.7.1 Event Table The eventTable is read-only and unprovisionable. The table contains one row for rising alarms and another for falling ones.
-
Chapter 16 SNMP 16.10.7 Event RMON Group Cisco ONS 15454 Reference Manual, R8.5.
-
A P P E N D I X A 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.
-
Appendix A Hardware Specifications A.1.2 Configurations A.1.2 Configurations The ONS 15454 can be configured as follows: • Two-fiber path protection • Path protected mesh network (PPMN) • Two-fiber bidirectional line switch ring (BLSR) • Four-fiber BLSR • Add-drop multiplexer (ADM) • Terminal mode • Regenerator mode • Hubbed rings • Multihubbed rings • Point-to-point • Linear • Linear with optical add/drop multiplexing (OADM) A.1.
-
Appendix A Hardware Specifications A.1.7 Alarm Interface • Hardware flow control • TCC2/TCC2P: EIA/TIA-232 DB-9 type connector A.1.7 Alarm Interface The ONS 15454 alarm interface has the following specifications: • Visual: Critical, Major, Minor, Remote • Audible: Critical, Major, Minor, Remote • Alarm contacts: 0.045 mm, –48 V, 50 mA • Backplane access: Alarm pin fields A.1.
-
Appendix A Hardware Specifications A.1.12 Fan Tray – Nominal: –48 VDC – Input Voltage Range: –40.5 to –57.0 VDC • Power terminals: #6 Lug • ANSI shelf fusing: 100–A fuse panel (minimum 30 A fuse per shelf) HD shelf fusing: 100–A fuse panel (minimum 30 A fuse per shelf) The ONS 15454 ETSI has the following power specifications: • Nominal Input Voltage: –48 VDC • Power consumption: Configuration dependent; 53 W (fan tray only) • Power requirements: – Nominal: –48 VDC – Input Voltage Range: –40.
-
Appendix A Hardware Specifications A.2 SFP, XFP, and GBIC Specifications A.2 SFP, XFP, and GBIC Specifications Table A-2 lists the specifications for the available Small Form-factor Pluggables (SFPs), 10 Gbps Pluggables (XFPs) and GBICs.
-
Appendix A Hardware Specifications A.2 SFP, XFP, and GBIC Specifications Table A-2 SFP, XFP, and GBIC Specifications (continued) SFP/XFP Product ID Interface Transmitter Output Receiver Input Power Power Min/Max (dBm) Min/Max (dBm) ONS-SC-GE-SX= GE –9.5 to 0 –17 to 02 ONS-SC-GE-LX= GE –9.
-
Appendix A Hardware Specifications A.3 General Card Specifications Table A-2 SFP, XFP, and GBIC Specifications (continued) SFP/XFP Product ID Interface ONS-SI-622-SR-MM= OC-12, STM-4 Transmitter Output Receiver Input Power Power Min/Max (dBm) Min/Max (dBm) -20 to -14 (50 micrometer) -26 to -14 -24 to -14 (62.
-
Appendix A Hardware Specifications A.3.1 Power Table A-3 Individual Card Power Requirements Card Type Card Name Watts Amperes BTU/Hr. Control Cards TCC2 19.20 0.4 66.8 TCC2P 27.00 0.56 92.2 XCVT 34.40 0.72 117.46 XC10G 48 1 163.68 XC-VXC-10G 67 1.4 228.62 AIC-I 4.8 0.1 15.3 AEP 3 (from +5 VDC from AIC-I) 10.2 FTA3 Fan Tray –48 VDC 129.60 2.7 442.21 FTA4 Fan Tray –48 VDC 115 2.4 393 EC1-12 36.60 0.76 124.97 DS1-14 12.60 0.26 43.02 DS1N-14 12.60 0.
-
Appendix A Hardware Specifications A.3.1 Power Table A-3 Individual Card Power Requirements (continued) Card Type Card Name Watts Amperes BTU/Hr. Optical Cards OC3 IR 4 19.20 0.40 65.56 OC3 IR 4/STM1 SH 1310 19.20 0.40 65.56 OC3 IR 4/STM1SH 1310-8 26.00 0.48 78.5 OC12 IR 1310 10.90 0.23 37.22 OC12 LR 1310 9.28 0.2 31.68 OC12 LR 1550 9.28 0.2 31.68 OC12 LR/STM4 LH 1310 9.00 0.2 31.68 OC12 LR/STM4 LH 1550 9.28 0.2 31.68 OC12 IR/STM4 SH 1310-4 35.60 0.74 121.
-
Appendix A Hardware Specifications A.3.2 Temperature Table A-3 Individual Card Power Requirements (continued) Card Type Card Name Watts Amperes BTU/Hr. Storage Access Networking FC_MR-4 60 1.25 212.00 1. These cards are designated as OC192-XFP in CTC. 2. GBICs = Gigabit Interface Converters A.3.2 Temperature Table A-4 provides temperature ranges and product names for ONS 15454 cards. Note The I-Temp symbol is displayed on the faceplate of an I-Temp compliant card.
-
Appendix A Hardware Specifications A.3.
-
Appendix A Hardware Specifications A.
-
Appendix A Hardware Specifications A.4.2 TCC2P Card Specifications – Reference: External BITS, line, internal • Supply voltage monitoring – Both supply voltage inputs are monitored. – Normal operation: –40.5 to –56.7 V – Undervoltage: Major alarm – Overvoltage: Major alarm • Environmental – Operating temperature: –40 to +149 degrees Fahrenheit (–40 to +65 degrees Celsius) – Operating humidity: 5 to 95 percent, noncondensing – Power consumption: 26.00 W, 0.54 A at –48 V, 88.
-
Appendix A Hardware Specifications A.4.3 XCVT Card Specifications • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.716 in. (18.2 mm) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 1.5 lb (0.7 kg) A.4.
-
Appendix A Hardware Specifications A.4.5 XC-VXC-10G Card Specifications A.4.5 XC-VXC-10G Card Specifications The XC-VXC-10G card has the following specifications: • Environmental – Operating temperature: I-Temp (15454-XC-VXC-10G-T): –40 to 149 degrees Fahrenheit (–40 to +65 degrees Celsius) – Operating humidity: 5 to 85 percent, noncondensing – Power consumption: 67 W, 1.4 A, 228.62 BTU/hr • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.716 in. (18.2 mm) – Depth: 9.000 in. (228.
-
Appendix A Hardware Specifications A.4.7 AEP Specifications – Orderwire party line – Dual tone multifrequency (DTMF) signaling • User data channel (UDC) – Bit rate: 64 kbps, bidirectional – ITU-T G.
-
Appendix A Hardware Specifications A.5 Electrical Card Specifications – Termination: 50-pin AMP champ connector • Alarm outputs – Number of outputs: 16 – Switched by opto MOS – Triggered by definable alarm condition – Maximum allowed open circuit voltage: 60 VDC – Maximum allowed closed circuit current: 100 mA – Termination: 50-pin AMP champ connector • Environmental – Overvoltage protection: as in ITU-T G.
-
Appendix A Hardware Specifications A.5.2 DS1-14 and DS1N-14 Card Specifications – Bit rate: 51.84 Mbps +/– 20 ppm – Frame format: SONET – Line code: B3ZS – Termination: Unbalanced coaxial cable – Input impedance: 75 ohms +/–5 percent – Cable loss: Max 450 feet 734A, RG-59, 728A/Max 79 feet RG-179 – AIS: TR-TSY-000191 compliant – Power level: –1.8 +/– 5.7 dBm – Pulse shape: ANSI T1.102-1988 Figure 8 – Pulse amplitude: 0.36 to 0.
-
Appendix A Hardware Specifications A.5.3 DS1/E1-56 Card Specifications • Output – Bit rate: 1.544 Mbps +/– 32 ppm – Frame format: Off, SF (D4), ESF – Line code: AMI, B8ZS – Termination: Wire-wrap, AMP Champ – Input impedance: 100 ohms – Cable loss: Max 655 feet ABAM #22 AWG – AIS: TR-TSY-000191 compliant – Power level: 12.5 to 17.9 dBm centered at 772 KHz, –16.4 to –11.1 dBm centered at 1544 KHz – Pulse shape: Telcordia GR-499-CORE Figure 9-5 – Pulse amplitude: 2.4 to 3.
-
Appendix A Hardware Specifications A.5.4 DS3/EC1-48 Card Specifications – Termination: Balanced, twisted pair, #22/24 AWG – Input impedance: 100 ohms +/– 5 percent (DS1); 120 ohms =/–5% (E1) – Cable loss: Max 655 feet ABAM #22/24 AWG (DS1); Compliant per ITU-T G.703 (E1) – AIS: TR-TSY-000191 compliant • Output – Bit rate: 1.544 Mbps ± 32 ppm (DS-1); 2.
-
Appendix A Hardware Specifications A.5.5 DS3-12 and DS3N-12 Card Specifications – Line code: B3ZS – Termination: Unbalanced coaxial cable – Input impedance: 75 ohms +/–5 percent – Cable loss: Max 450 feet with 734A or 728A, Max 79 feet with RG-179 – AIS: TR-TSY-000191 compliant • Output – Bit rate: 44.736 Mbps +/– 20 ppm – Frame format: DS-3 ANSI T1.
-
Appendix A Hardware Specifications A.5.5 DS3-12 and DS3N-12 Card Specifications – Frame format: DS-3 ANSI T1.107-1988 – Line code: B3ZS – Termination: Unbalanced coaxial cable – Input impedance: 75 ohms +/–5 percent – Cable loss: Max 450 feet 734A, RG-59, 728A/Max 79 feet RG-179 – AIS: TR-TSY-000191 compliant • Output – Bit rate: 44.736 Mbps +/– 20 ppm – Frame format: DS-3 ANSI T1.
-
Appendix A Hardware Specifications A.5.6 DS3i-N-12 Card Specifications A.5.6 DS3i-N-12 Card Specifications The DS3i-N-12 card has the following specifications: • Input – Bit rate: 44.736 Mbps +/–20 ppm – Frame format: ITU-T G.704, ITU-T G.752/DS-3 ANSI T1.107-1988 – Line code: B3ZS – Termination: Unbalanced coaxial cable – Input impedance: 75 ohms +/– 5 percent – Cable loss: Maximum 137 m (450 ft): 734A, RG59, 728A Maximum 24 m (79 ft): RG179 – AIS: ITU-T G.704 compliant • Output – Bit rate: 44.
-
Appendix A Hardware Specifications A.5.7 DS3-12E and DS3N-12E Card Specifications – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 1.9 lb (0.8 kg) A.5.7 DS3-12E and DS3N-12E Card Specifications The DS3-12E and DS3N-12E cards have the following specifications: • Input – Bit rate: 44.736 Mbps +/– 20 ppm – Frame format: DS-3 ANSI T1.
-
Appendix A Hardware Specifications A.5.8 DS3XM-12 Card Specifications • Power consumption: 26.80 W, 0.56 A, 91.51 BTU/hr • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.716 in. (18.2 mm) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235.0 mm) – DS3-12E card weight: 1.8 lb (0.8 kg) – DS3N-12E card weight: 1.9 lb (0.8 kg) A.5.8 DS3XM-12 Card Specifications The DS3XM-12 card has the following specifications: • Input – Bit rate: 44.
-
Appendix A Hardware Specifications A.5.9 DS3XM-6 Card Specifications Note The I-Temp symbol is displayed on the faceplate of an I-Temp compliant card. A card without this symbol is C-Temp compliant. • Operating humidity: 5 to 95 percent, noncondensing • Power consumption: 34 W, 0.71A at –48 V, 116.1 BTU/hr • Dimensions – Height: 12.65 in. (321.3 mm) – Width: 0.716 in. (18.2 mm) – Depth: 9.00 in. (228.6 mm) – Card weight: 1.8 lb (0.8 kg) A.5.
-
Appendix A Hardware Specifications A.5.10 FILLER Card Specifications – C-Temp (15454-DS3XM-6): 0 to 131 degrees Fahrenheit (0 to +55 degrees Celsius) – I-Temp (15454-DS3XM-6-T): –40 to 149 degrees Fahrenheit (–40 to +65 degrees Celsius) Note The I-Temp symbol is displayed on the faceplate of an I-Temp compliant card. A card without this symbol is C-Temp compliant. • Operating humidity: 5 to 95 percent, noncondensing • Power consumption: 20 W, 0.42 A, 68 BTU/hr • Dimensions – Height: 12.650 in.
-
Appendix A Hardware Specifications A.6.1 OC3 IR 4/STM1 SH 1310 Card Specifications A.6.1 OC3 IR 4/STM1 SH 1310 Card Specifications The OC3 IR 4/STM1 SH 1310 card has the following specifications: • Line – Bit rate: 155.52 Mbps – Code: Scrambled non-return to zero (NRZ) – Fiber: 1310-nm single-mode – Loopback modes: Terminal and facility – Connector: SC – Compliance: Telcordia GR-253-CORE, ITU-T G.707, ITU-T G.
-
Appendix A Hardware Specifications A.6.2 OC3 IR/STM1SH 1310-8 Card Specifications A.6.2 OC3 IR/STM1SH 1310-8 Card Specifications The OC3 IR/STM1SH 1310-8 card has the following specifications: • Line – Bit rate: 155.52 Mbps – Code: Scrambled NRZ – Fiber: 1310-nm single-mode – Loopback modes: Terminal and facility – Connector: LC – Compliance: Telcordia GR-253-CORE, ITU-T G.707, ITU-T G.
-
Appendix A Hardware Specifications A.6.3 OC12 IR/STM4 SH 1310 Card Specifications A.6.3 OC12 IR/STM4 SH 1310 Card Specifications The OC12 IR/STM4 SH 1310 card has the following specifications: • Line – Bit rate: 622.08 Mbps – Code: Scrambled NRZ – Fiber: 1310-nm single-mode – Loopback modes: Terminal and facility – Connectors: SC – Compliance: Telcordia GR-253-CORE, ITU-T G.707, ITU-T G.
-
Appendix A Hardware Specifications A.6.4 OC12 LR/STM4 LH 1310 Card Specifications A.6.4 OC12 LR/STM4 LH 1310 Card Specifications The OC12 LR/STM4 LH 1310 card has the following specifications: • Line – Bit rate: 622.08 Mbps – Code: Scrambled NRZ – Fiber: 1310-nm single-mode – Loopback modes: Terminal and facility – Connectors: SC – Compliance: Telcordia SONET, Telcordia GR-253-CORE, ITU-T G.707, ITU-T G.
-
Appendix A Hardware Specifications A.6.5 OC12 LR/STM4 LH 1550 Card Specifications A.6.5 OC12 LR/STM4 LH 1550 Card Specifications The OC12 LR/STM4 LH 1550 card has the following specifications: • Line – Bit rate: 622.08 Mbps – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Loopback modes: Terminal and facility – Connectors: SC – Compliance: Telcordia SONET, Telcordia GR-253-CORE, ITU-T G.707, ITU-T G.
-
Appendix A Hardware Specifications A.6.6 OC12 IR/STM4 SH 1310-4 Specifications A.6.6 OC12 IR/STM4 SH 1310-4 Specifications The OC12 IR/STM4 SH 1310-4 card has the following specifications: • Line – Bit rate: 622.08 Mbps – Code: Scrambled NRZ – Fiber: 1310-nm single-mode – Loopback modes: Terminal and facility – Connector: SC – Compliance: Telcordia GR-253-CORE, ITU-T G.707, ITU-T G.
-
Appendix A Hardware Specifications A.6.7 OC48 IR 1310 Card Specifications Note Minimum transmit power, minimum receive power, and link loss budget might exceed standard specifications. A.6.7 OC48 IR 1310 Card Specifications The OC48 IR 1310 card has the following specifications: • Line – Bit rate: 2.
-
Appendix A Hardware Specifications A.6.8 OC48 LR 1550 Card Specifications A.6.8 OC48 LR 1550 Card Specifications The OC48 LR 1550 card has the following specifications: • Line – Bit rate: 2.
-
Appendix A Hardware Specifications A.6.10 OC48 LR/STM16 LH AS 1550 Card Specifications – Code: Scrambled NRZ – Fiber: 1310-nm single-mode – Loopback modes: Terminal and facility – Connectors: SC – Compliance: Telcordia GR-253-CORE, ITU-T G.707, ITU-T G.
-
Appendix A Hardware Specifications A.6.11 OC48 ELR/STM 16 EH 100 GHz Card Specifications – Connectors: SC – Compliance: Telcordia GR-253-CORE, ITU-T G.707, ITU-T G.
-
Appendix A Hardware Specifications A.6.12 OC48 ELR 200 GHz Card Specifications • Transmitter – Maximum transmitter output power: 0 dBm – Minimum transmitter output power: –2 dBm – Center wavelength accuracy: +/– 0.
-
Appendix A Hardware Specifications A.6.13 OC192 SR/STM64 IO 1310 Card Specifications – Transmitter: Electro-absorption laser – Dispersion tolerance: 3600 ps/nm • Receiver – Maximum receiver level: –8 dBm – Minimum receiver level: –28 dBm – Receiver: InGaAs APD photodetector – Link loss budget: 26 dB minimum, with 1 dB dispersion penalty – Receiver input wavelength range: 1520 to 1580 nm – Jitter tolerance: Telcordia GR-253/ITU-T G.
-
Appendix A Hardware Specifications A.6.14 OC192 IR/STM64 SH 1550 Card Specifications – Maximum receiver level: –1 dBm at BER 1 * 10 exp – 12 – Minimum receiver level: –11 dBm at BER 1 * 10 exp – 12 – Receiver: PIN diode – Link loss budget: 5 dB minimum, plus 1 dB dispersion penalty at BER = 1 * 10 exp – 12 including dispersion – Receiver input wavelength range: 1290 to 1330 nm – Dispersion tolerance: 6.
-
Appendix A Hardware Specifications A.6.
-
Appendix A Hardware Specifications A.6.16 OC192 LR/STM64 LH ITU 15xx.
-
Appendix A Hardware Specifications A.6.16 OC192 LR/STM64 LH ITU 15xx.xx Card Specifications In deployments with a dispersion compensation unit (DCU): +/– 1000 ps/nm, with optical signal-to-noise ration (OSNR) of 19 dB (0.5 nm resolution bandwidth [RBW]) In deployments without a DCU: +/– 1200 ps/nm, with OSNR of 23 dB (0.5 nm RBW) – Loopback modes: Terminal and facility Note You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the OC192 LR/STM64 LH 15xx.xx card in a loopback.
-
Appendix A Hardware Specifications A.6.17 15454_MRC-12 Card Specifications – 1535.82 +/– 0.040 nm, OC192 LR/STM64 LH ITU 1535.82 – 1536.61 +/– 0.040 nm, OC192 LR/STM64 LH ITU 1536.61 – 1538.19 +/– 0.040 nm, OC192 LR/STM64 LH ITU 1538.19 – 1538.98 +/– 0.040 nm, OC192 LR/STM64 LH ITU 1538.98 – 1539.77 +/– 0.040 nm, OC192 LR/STM64 LH ITU 1539.77 – 1540.56 +/– 0.040 nm, OC192 LR/STM64 LH ITU 1540.56 ITU grid red band: – 1550.12 +/– 0.040 nm, OC192 LR/STM64 LH ITU 1550.12 – 1550.92 +/– 0.
-
Appendix A Hardware Specifications A.6.18 MRC-2.5G-4 Card Specifications – Maximum receiver level: Depends on SFP (see A.2 SFP, XFP, and GBIC Specifications, page A-5) – Minimum receiver level: Depends on SFP (see A.
-
Appendix A Hardware Specifications A.6.18 MRC-2.5G-4 Card Specifications – Compliance: Telcordia GR-253-CORE • Transmitter – Maximum transmitter output power: Depends on SFP (see A.2 SFP, XFP, and GBIC Specifications, page A-5) – Minimum transmitter output power: Depends on SFP (see A.
-
Appendix A Hardware Specifications A.6.19 OC192SR1/STM64IO Short Reach Card Specifications A.6.19 OC192SR1/STM64IO Short Reach Card Specifications Note The OC192SR1/STM64IO Short Reach card is designated as OC192-XFP in CTC. The OC192SR1/STM64IO Short Reach card has the following specifications: • Line – Bit rate: OC-192 (9.
-
Appendix A Hardware Specifications A.7 Ethernet Card Specifications – Connectors: LC duplex connector for the XFPs – Compliance: Telcordia GR-253-CORE • Transmitter – Maximum transmitter output power: Depends on SFP (see A.2 SFP, XFP, and GBIC Specifications, page A-5) – Minimum transmitter output power: Depends on SFP (see A.2 SFP, XFP, and GBIC Specifications, page A-5) • Receiver – Maximum receiver level: Depends on SFP (see A.
-
Appendix A Hardware Specifications A.7.2 E100T-G Card Specifications – Height: 12.650 in. (321.3 mm) – Width: 0.716 in. (18.2 mm) – Depth: 9.000 in. (228.6 mm) – Card weight: 2.3 lb (1.0 kg) A.7.2 E100T-G Card Specifications The E100T-G card has the following specifications: • Environmental – Operating temperature: C-Temp (15454-E100T-G): 32 to 131 degrees Fahrenheit (0 to +55 degrees Celsius) – Operating humidity: 5 to 95 percent, noncondensing – Power consumption: 65 W, 1.35 A, 221.
-
Appendix A Hardware Specifications A.7.5 CE-1000-4 Card Specifications C-Temp (15454-E1000-2-G): 32 to 131 degrees Fahrenheit (0 to +55 degrees Celsius) – Operating humidity: 5 to 95 percent, noncondensing – Power consumption: 53.50 W, 1.11 A, 182.67 BTU/hr • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.716 in. (18.2 mm) – Depth: 9.000 in. (228.6 mm) – Card weight: 2.1 lb (0.9 kg) A.7.
-
Appendix A Hardware Specifications A.7.7 CE-MR-10 Card Specifications A.7.7 CE-MR-10 Card Specifications The CE-MR-10 card has the following specifications: • Environmental – Operating temperature C-Temp (15454-CE-MR-10): 32 to 131 degrees Fahrenheit (0 to +50 degrees Celsius) – Operating humidity: 5 to 95 percent, noncondensing – Power consumption: 95 • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.716 in. (18.2 mm) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in.
-
Appendix A Hardware Specifications A.7.10 ML1000-2 Card Specifications – Width: 0.716 in. (18.2 mm) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 2.3 lb (1.0 kg) A.7.10 ML1000-2 Card Specifications The ML1000-2 card has the following specifications: • Environmental – Operating temperature: +23 to +131 degrees Fahrenheit (–5 to +55 degrees Celsius) – Operating humidity: 5 to 95 percent, noncondensing – Power consumption: 49.00 W, 1.
-
Appendix A Hardware Specifications A.8 Storage Access Networking Card Specifications – Operating humidity: 5 to 95 percent, noncondensing – Power consumption: 100 W • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.716 in. (18.2 mm) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 0.9 kg (2.1 lb) A.8 Storage Access Networking Card Specifications This section describes the FC_MR-4 (Fibre Channel) card specifications.
-
Appendix A Hardware Specifications A.8 Storage Access Networking Card Specifications – Card weight: 2.59 lb (1.17 kg) Cisco ONS 15454 Reference Manual, R8.5.
-
A P P E N D I X B Administrative and Service States This appendix describes administrative and service states for Cisco ONS 15454 cards, ports, and cross-connects. For circuit state information, refer to Chapter 11, “Circuits and Tunnels.” Entity states in Software Release 5.0 and later are based on the generic state model defined in Telcordia GR-1093-CORE, Issue 2 and ITU-T X.731. This appendix contains the following sections: • B.1 Service States, page B-1 • B.2 Administrative States, page B-2 • B.
-
Appendix B Administrative and Service States B.2 Administrative States Table B-2 ONS 15454 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 the correction of conditions, or on a soak timer. Alarm reporting is suppressed, but traffic is carried.
-
Appendix B Administrative and Service States B.3 Service State Transitions Table B-3 ONS 15454 Administrative States Administrative State (PST,SST) Definition IS Puts the entity in service. IS,AINS Puts the entity in automatic in-service. OOS,DSBLD Removes the entity from service and disables it. OOS,MT Removes the entity from service for maintenance. OOS,OOG (VCAT circuits only) Removes a VCAT cross-connect cross-connect from service and from the group of members.
-
Appendix B Administrative and Service States B.3.1 Card Service State Transitions Table B-4 ONS 15454 Card Service State Transitions (continued) Current Service State Action Next Service State OOS-AU,AINS & SWDL Restart completed. IS-NR Remove the card. OOS-AU,AINS & UEQ Insert a valid card. OOS-AU,AINS & SWDL Insert an invalid card. OOS-AU,AINS & MEA Delete the card. OOS-AUMA,UAS & UEQ Remove the card. OOS-AU,UEQ Delete the card.
-
Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions Table B-4 ONS 15454 Card Service State Transitions (continued) Current Service State Action Next Service State OOS-AUMA,MEA & UAS Remove the card. OOS-AUMA,UAS & UEQ Provision the card. OOS-AU,MEA Restart completed. OOS-MA,MT Remove the card. OOS-AUMA,MT & UEQ Change the administrative state to IS. OOS-AU,UEQ Insert a valid card. OOS-AUMA,MT & SWDL Insert an invalid card.
-
Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions To change this behavior so that you cannot put a port in OOS-MA,DSBLD if any of these conditions exist, set the NODE.general.ForceToOosDsbldStateChange default setting to FALSE. For the procedure to change node defaults, refer to the “Maintain the Node” chapter in the Cisco ONS 15454 Procedure Guide.
-
Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions Table B-5 ONS 15454 Port and Cross-Connect Service State Transitions (continued) Current Service State Action Next Service State OOS-AU,AINS & FLT Alarm/condition is cleared. OOS-AU,AINS Put the port or cross-connect in the IS administrative state. OOS-AU,FLT Put the port or cross-connect in the OOS,DSBLD administrative state.
-
Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions Table B-5 ONS 15454 Port and Cross-Connect Service State Transitions (continued) Current Service State Action Next Service State OOS-AU,FLT & OOG Alarm/condition is cleared. IS-NR or OOS-MA,MT • If an In Group member is IS-NR or OOS-AU,AINS, the member transitions to IS-NR.
-
Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions Table B-5 ONS 15454 Port and Cross-Connect Service State Transitions (continued) Current Service State Action Next Service State OOS-AUMA,FLT & MT Alarm/condition is cleared. & OOG Put the VCAT cross-connect in the IS administrative state. Note OOS-MA,LPBK & MT OOS-AU,AINS & FLT & OOG VCAT In Group members are in the OOS-AU,AINS & FLT or IS-NR service state.
-
Appendix B Administrative and Service States B.3.3 Pluggable Equipment Service State Transitions Table B-5 ONS 15454 Port and Cross-Connect Service State Transitions (continued) Current Service State Action Next Service State OOS-MA,LPBK & MT & OOG Alarm/condition is raised. OOS-AUMA,FLT & LPBK & MT & OOG OOS-MA,MT Put the port or cross-connect in the IS administrative state. IS-NR Put the port or cross-connect in the IS,AINS administrative state.
-
Appendix B Administrative and Service States B.3.3 Pluggable Equipment Service State Transitions Table B-6 ONS 15454 Pluggable Equipment Service State Transitions (continued) Current Service State Action Next Service State OOS-AU,AINS & UEQ Insert valid pluggable equipment. IS-NR Insert pluggable equipment with the incorrect rate. OOS-AU,MEA Pluggable equipment does not work with the board configuration.
-
Appendix B Administrative and Service States B.3.3 Pluggable Equipment Service State Transitions Cisco ONS 15454 Reference Manual, R8.5.
-
A P P E N D I X C 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.
-
Appendix C Network Element Defaults C.2 Card Default Settings Changes that are made manually to most node-level default settings override the current settings, whether default or provisioned.
-
Appendix C Network Element Defaults C.2.2 Threshold Defaults Note MRC-12 and MRC-2.5G-4 line configuration defaults are defined on a per OC-N rate basis. • SONET STS—(OC-N and EC1-12 cards) SONET STS-level configuration settings. • Port—(FC_MR-4 cards only) Port line-level configuration, distance extension, and enhanced FC/FICON ISL settings.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card • Physical Layer thresholds—(OC3-8, OC-192, OC-192XFP, MRC-2.5G-4, and MRC-12 cards) Expressed in percentages; includes optics thresholds. Threshold defaults are defined for near end and/or far end, at 15-minute and one-day intervals. Thresholds are further broken down by type, such as Section, Line, STS, or VT for performance monitoring (PM) thresholds, and TCA (warning) or Alarm for physical thresholds.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-1 DS-1 Card Default Settings (continued) Default Name Default Value Default Domain DS1.pmthresholds.line.farend.1day.ES 648 (seconds) 0 - 86400 DS1.pmthresholds.line.nearend.15min.CV 13340 (BPV count) 0 - 1388700 DS1.pmthresholds.line.nearend.15min.ES 65 (seconds) 0 - 900 DS1.pmthresholds.line.nearend.15min.LOSS 10 (seconds) 0 - 900 DS1.pmthresholds.line.nearend.15min.SES 10 (seconds) 0 - 900 DS1.pmthresholds.line.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-1 DS-1 Card Default Settings (continued) Default Name Default Value Default Domain DS1.pmthresholds.path.nearend.1day.ES 648 (seconds) 0 - 86400 DS1.pmthresholds.path.nearend.1day.FC 0 (count) 0 - 8640 DS1.pmthresholds.path.nearend.1day.SAS 17 (seconds) 0 - 86400 DS1.pmthresholds.path.nearend.1day.SES 100 (seconds) 0 - 86400 DS1.pmthresholds.path.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1.pmthresholds.sts.farend.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-1 DS-1 Card Default Settings (continued) Default Name Default Value Default Domain DS1.pmthresholds.vt.nearend.15min.UAS 10 (seconds) 0 - 900 DS1.pmthresholds.vt.nearend.1day.CV 125 (BIP8 count) 0 - 207360000 DS1.pmthresholds.vt.nearend.1day.ES 100 (seconds) 0 - 86400 DS1.pmthresholds.vt.nearend.1day.SES 7 (seconds) 0 - 86400 DS1.pmthresholds.vt.nearend.1day.UAS 10 (seconds) 0 - 86400 C.2.3.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-2 DS1/E1-56 Card Default Settings (continued) Default Name Default Value Default Domain DS1-E1-56.DS1-PORT.config.sonet.AdminSSMIn STU PRS, STU, ST2, ST3, SMC, ST4, DUS, RES when //.//.//.//.NODE.timing.general.SSMMessa geSet Generation 1; PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, RES when //.//.//.//.NODE.timing.general.SSMMessa geSet Generation 2; PRS, STU, ST2, ST3, SMC, ST4, DUS, RES when //.//.//.//.NODE.timing.general.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-2 DS1/E1-56 Card Default Settings (continued) Default Name Default Value Default Domain DS1-E1-56.DS1-PORT.pmthresholds.path.farend.15min.ESN 65 (seconds) E 0 - 900 DS1-E1-56.DS1-PORT.pmthresholds.path.farend.15min.FC 0 - 72 10 (count) DS1-E1-56.DS1-PORT.pmthresholds.path.farend.15min.SEF 25 (seconds) S 0 - 900 DS1-E1-56.DS1-PORT.pmthresholds.path.farend.15min.SES 10 (seconds) 0 - 900 DS1-E1-56.DS1-PORT.pmthresholds.path.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-2 DS1/E1-56 Card Default Settings (continued) Default Name Default Value Default Domain DS1-E1-56.DS1-PORT.pmthresholds.path.nearend.15min.ES 65 (seconds) 0 - 900 DS1-E1-56.DS1-PORT.pmthresholds.path.nearend.15min.FC 10 (count) 0 - 72 DS1-E1-56.DS1-PORT.pmthresholds.path.nearend.15min.SA 2 (seconds) S 0 - 900 DS1-E1-56.DS1-PORT.pmthresholds.path.nearend.15min.SE 10 (seconds) S 0 - 900 DS1-E1-56.DS1-PORT.pmthresholds.path.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-2 DS1/E1-56 Card Default Settings (continued) Default Name Default Value Default Domain DS1-E1-56.DS1-PORT.pmthresholds.vt.farend.1day.ES 100 (seconds) 0 - 86400 DS1-E1-56.DS1-PORT.pmthresholds.vt.farend.1day.FC 40 (count) 0 - 6912 DS1-E1-56.DS1-PORT.pmthresholds.vt.farend.1day.SES 7 (seconds) 0 - 86400 DS1-E1-56.DS1-PORT.pmthresholds.vt.farend.1day.UAS 10 (seconds) 0 - 86400 DS1-E1-56.DS1-PORT.pmthresholds.vt.nearend.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-2 DS1/E1-56 Card Default Settings (continued) Default Name Default Value Default Domain DS1-E1-56.E1-PORT.config.SyncMsgIn FALSE FALSE, TRUE DS1-E1-56.E1-PORT.config.TreatLOFAsDefect TRUE FALSE, TRUE DS1-E1-56.E1-PORT.pmthresholds.line.nearend.15min.CV 9 (BPV count) 0 - 1388700 DS1-E1-56.E1-PORT.pmthresholds.line.nearend.15min.ES 65 (seconds) 0 - 900 DS1-E1-56.E1-PORT.pmthresholds.line.nearend.15min.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-2 DS1/E1-56 Card Default Settings (continued) Default Name Default Value Default Domain DS1-E1-56.E1-PORT.pmthresholds.sts.nearend.1day.FC 40 (count) 0 - 6912 DS1-E1-56.E1-PORT.pmthresholds.sts.nearend.1day.SES 7 (seconds) 0 - 86400 DS1-E1-56.E1-PORT.pmthresholds.sts.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-E1-56.E1-PORT.pmthresholds.vt.farend.15min.ES 65 (seconds) 0 - 900 DS1-E1-56.E1-PORT.pmthresholds.vt.farend.15min.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-3 DS-3 Card Default Settings (continued) Default Name Default Value Default Domain DS3.pmthresholds.line.nearend.1day.CV 3865 (BPV count) 0 - 3715200 DS3.pmthresholds.line.nearend.1day.ES 250 (seconds) 0 - 86400 DS3.pmthresholds.line.nearend.1day.LOSS 10 (seconds) 0 - 86400 DS3.pmthresholds.line.nearend.1day.SES 40 (seconds) 0 - 86400 DS3.pmthresholds.sts.farend.15min.CV 15 (G1 count) 0 - 2160000 DS3.pmthresholds.sts.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-4 DS3/EC1-48 Card Default Settings (continued) Default Name Default Value Default Domain DS3-EC1-48.DS3-PORT.config.LineType UNFRAME D UNFRAMED, M13, C BIT, AUTO PROVISION FMT DS3-EC1-48.DS3-PORT.config.SDBER 1.00E-07 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 DS3-EC1-48.DS3-PORT.config.SendAISOnFacilityLoopback TRUE TRUE, FALSE DS3-EC1-48.DS3-PORT.config.SendAISOnTerminalLoopback FALSE TRUE, FALSE DS3-EC1-48.DS3-PORT.config.SFBER 1.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-4 DS3/EC1-48 Card Default Settings (continued) Default Name Default Value Default Domain DS3-EC1-48.DS3-PORT.pmthresholds.line.nearend.1day.CV 3865 (BPV count) 0 - 3715200 DS3-EC1-48.DS3-PORT.pmthresholds.line.nearend.1day.ES 250 (seconds) 0 - 86400 DS3-EC1-48.DS3-PORT.pmthresholds.line.nearend.1day.LOSS 10 (seconds) 0 - 86400 DS3-EC1-48.DS3-PORT.pmthresholds.line.nearend.1day.SES 40 (seconds) 0 - 86400 DS3-EC1-48.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-4 DS3/EC1-48 Card Default Settings (continued) Default Name Default Value Default Domain DS3-EC1-48.DS3-PORT.pmthresholds.sts.nearend.15min.UAS 10 (seconds) 0 - 900 DS3-EC1-48.DS3-PORT.pmthresholds.sts.nearend.1day.CV 125 (B3 count) 0 - 207360000 DS3-EC1-48.DS3-PORT.pmthresholds.sts.nearend.1day.ES 100 (seconds) 0 - 86400 DS3-EC1-48.DS3-PORT.pmthresholds.sts.nearend.1day.FC 10 (count) 0 - 6912 DS3-EC1-48.DS3-PORT.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-4 DS3/EC1-48 Card Default Settings (continued) Default Name Default Value Default Domain DS3-EC1-48.EC1-PORT.pmthresholds.line.nearend.1day.CV 13120 (B2 count) 0 - 13219200 DS3-EC1-48.EC1-PORT.pmthresholds.line.nearend.1day.ES 864 (seconds) 0 - 86400 DS3-EC1-48.EC1-PORT.pmthresholds.line.nearend.1day.FC 40 (count) 0 - 6912 DS3-EC1-48.EC1-PORT.pmthresholds.line.nearend.1day.SES 4 (seconds) 0 - 86400 DS3-EC1-48.EC1-PORT.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-4 DS3/EC1-48 Card Default Settings (continued) Default Name Default Value Default Domain DS3-EC1-48.EC1-PORT.pmthresholds.sts1.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 DS3-EC1-48.EC1-PORT.pmthresholds.sts1.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 DS3-EC1-48.EC1-PORT.pmthresholds.sts1.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 DS3-EC1-48.EC1-PORT.pmthresholds.sts1.nearend.15min.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-5 DS3E Card Default Settings (continued) Default Name Default Value Default Domain DS3E.config.SDBER 1.00E-07 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 DS3E.config.SendAISOnFacilityLoopback TRUE TRUE, FALSE DS3E.config.SendAISOnTerminalLoopback FALSE FALSE DS3E.config.SFBER 1.00E-04 1E-3, 1E-4, 1E-5 DS3E.config.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS DS3E.pmthresholds.cpbitpath.farend.15min.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-5 DS3E Card Default Settings (continued) Default Name Default Value Default Domain DS3E.pmthresholds.pbitpath.nearend.15min.SAS 2 (seconds) 0 - 900 DS3E.pmthresholds.pbitpath.nearend.15min.SES 4 (seconds) 0 - 900 DS3E.pmthresholds.pbitpath.nearend.15min.UAS 10 (seconds) 0 - 900 DS3E.pmthresholds.pbitpath.nearend.1day.AISS 10 (seconds) 0 - 86400 DS3E.pmthresholds.pbitpath.nearend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-6 DS3I Card Default Settings Default Name Default Value Default Domain DS3I.config.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 DS3I.config.FeInhibitLpbk TRUE TRUE, FALSE DS3I.config.LineLength 0 - 225 ft 0 - 225 ft, 226 - 450 ft DS3I.config.LineType C BIT UNFRAMED, M13, C BIT, AUTO PROVISION FMT DS3I.config.SDBER 1.00E-07 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 DS3I.config.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-6 DS3I Card Default Settings (continued) Default Name Default Value Default Domain DS3I.pmthresholds.line.nearend.1day.ES 250 (seconds) 0 - 86400 DS3I.pmthresholds.line.nearend.1day.LOSS 10 (seconds) 0 - 86400 DS3I.pmthresholds.line.nearend.1day.SES 40 (seconds) 0 - 86400 DS3I.pmthresholds.pbitpath.nearend.15min.AISSP 10 (seconds) 0 - 900 DS3I.pmthresholds.pbitpath.nearend.15min.CVP 382 (BIP count) 0 - 38700 DS3I.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card C.2.3.7 DS3XM-6 Card Default Settings Table C-7 lists the DS3XM-6 card default settings. Table C-7 DS3XM-6 Card Default Settings Default Name Default Value Default Domain DS3XM.config.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 DS3XM.config.FeInhibitLpbk TRUE TRUE, FALSE DS3XM.config.LineLength 0 - 225 ft 0 - 225 ft, 226 - 450 ft DS3XM.config.LineType M13 M13, C BIT DS3XM.config.SDBER 1.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-7 DS3XM-6 Card Default Settings (continued) Default Name Default Value Default Domain DS3XM.pmthresholds.ds1path.nearend.15min.UAS 10 (seconds) 0 - 900 DS3XM.pmthresholds.ds1path.nearend.1day.AISS 10 (seconds) 0 - 86400 DS3XM.pmthresholds.ds1path.nearend.1day.ES 648 (seconds) 0 - 86400 DS3XM.pmthresholds.ds1path.nearend.1day.SAS 17 (seconds) 0 - 86400 DS3XM.pmthresholds.ds1path.nearend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-7 DS3XM-6 Card Default Settings (continued) Default Name Default Value Default Domain DS3XM.pmthresholds.sts.nearend.15min.CV 15 (B3 count) 0 - 2160000 DS3XM.pmthresholds.sts.nearend.15min.ES 12 (seconds) 0 - 900 DS3XM.pmthresholds.sts.nearend.15min.FC 10 (count) 0 - 72 DS3XM.pmthresholds.sts.nearend.15min.SES 3 (seconds) 0 - 900 DS3XM.pmthresholds.sts.nearend.15min.UAS 10 (seconds) 0 - 900 DS3XM.pmthresholds.sts.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-8 DS3XM-12 Card Default Settings (continued) Default Name Default Value Default Domain DS3XM12.config.SDBER 1.00E-07 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 DS3XM12.config.SendAISOnFacilityLoopback TRUE TRUE, FALSE DS3XM12.config.SendAISOnTerminalLoopback FALSE TRUE, FALSE DS3XM12.config.SFBER 1.00E-04 1E-3, 1E-4, 1E-5 DS3XM12.config.State OOS,DSBLD IS, OOS,DSBLD, OOS,MT, IS,AINS DS3XM12.ds1config.FdlMode T1.403 T1.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-8 DS3XM-12 Card Default Settings (continued) Default Name Default Value Default Domain DS3XM12.pmthresholds.ds1path.farend.15min.SEFS 25 (seconds) 0 - 900 DS3XM12.pmthresholds.ds1path.farend.15min.SES 10 (seconds) 0 - 900 DS3XM12.pmthresholds.ds1path.farend.15min.SESFE 10 (seconds) 0 - 900 DS3XM12.pmthresholds.ds1path.farend.15min.SESNE 10 (seconds) 0 - 900 DS3XM12.pmthresholds.ds1path.farend.15min.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-8 DS3XM-12 Card Default Settings (continued) Default Name Default Value Default Domain DS3XM12.pmthresholds.line.nearend.15min.CV 387 (BPV count) 0 - 38700 DS3XM12.pmthresholds.line.nearend.15min.ES 25 (seconds) 0 - 900 DS3XM12.pmthresholds.line.nearend.15min.LOSS 10 (seconds) 0 - 900 DS3XM12.pmthresholds.line.nearend.15min.SES 4 (seconds) 0 - 900 DS3XM12.pmthresholds.line.nearend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-8 DS3XM-12 Card Default Settings (continued) Default Name Default Value Default Domain DS3XM12.pmthresholds.sts.nearend.1day.ES 100 (seconds) 0 - 86400 DS3XM12.pmthresholds.sts.nearend.1day.FC 10 (count) 0 - 6912 DS3XM12.pmthresholds.sts.nearend.1day.SES 7 (seconds) 0 - 86400 DS3XM12.pmthresholds.sts.nearend.1day.UAS 10 (seconds) 0 - 86400 DS3XM12.pmthresholds.vt.farend.15min.CV 15 (BIP8 count) 0 - 2160000 DS3XM12.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-9 EC1-12 Card Default Settings (continued) Default Name Default Value Default Domain EC1.pmthresholds.line.farend.15min.ES 87 (seconds) 0 - 900 EC1.pmthresholds.line.farend.15min.FC 10 (count) 0 - 72 EC1.pmthresholds.line.farend.15min.SES 1 (seconds) 0 - 900 EC1.pmthresholds.line.farend.15min.UAS 3 (seconds) 0 - 900 EC1.pmthresholds.line.farend.1day.CV 13120 (B2 count) 0 - 8850600 EC1.pmthresholds.line.farend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-9 EC1-12 Card Default Settings (continued) Default Name Default Value Default Domain EC1.pmthresholds.sts1.farend.1day.UAS 10 (seconds) 0 - 86400 EC1.pmthresholds.sts1.nearend.15min.CV 15 (B3 count) 0 - 2160000 EC1.pmthresholds.sts1.nearend.15min.ES 12 (seconds) 0 - 900 EC1.pmthresholds.sts1.nearend.15min.FC 10 (count) 0 - 72 EC1.pmthresholds.sts1.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 EC1.pmthresholds.sts1.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-10 FC_MR-4 Card Default Settings Default Name Default Value Default Domain FC-MR.config.card.Mode Fibre Fibre Channel Line Rate, Fibre Channel/FICO Channel/FICON Enhanced when N Enhanced //.port.MediaType Undefined; Fibre Channel/FICON Enhanced when //.port.MediaType FICON 1 Gbps ISL, FICON - 2 Gbps ISL; Fibre Channel Line Rate, Fibre Channel/FICON Enhanced when //.port.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-11 Ethernet Card Default Settings Default Name Default Value Default Domain CE-1000-4.config.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 CE-1000-4.config.State OOS,DSBLD IS, OOS,DSBLD, OOS,MT, IS,AINS CE-1000-4.etherPortConfig.AutoNegotiation TRUE TRUE, FALSE CE-1000-4.etherPortConfig.FlowControl Symmetric None, Symmetric, Pass Through CE-1000-4.etherPortConfig.MTU 10004 (bytes) 1548, 10004 CE-1000-4.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card C.2.3.12 OC-3 Card Default Settings Table C-12 lists the OC-3 (OC3 IR 4/STM1 SH 1310) card default settings. Table C-12 OC-3 Card Default Settings Default Name Default Value Default Domain OC3.config.line.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 OC3.config.line.PJStsMon# 0 (STS #) 0-3 OC3.config.line.SDBER 1.00E-07 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 OC3.config.line.sdh.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-12 OC-3 Card Default Settings (continued) Default Name Default Value Default Domain OC3.pmthresholds.line.farend.1day.UAS 10 (seconds) 0 - 86400 OC3.pmthresholds.line.nearend.15min.CV 1312 (B2 count) 0 - 137700 OC3.pmthresholds.line.nearend.15min.ES 87 (seconds) 0 - 900 OC3.pmthresholds.line.nearend.15min.FC 10 (count) 0 - 72 OC3.pmthresholds.line.nearend.15min.PSC 1 (count) 0 - 600 OC3.pmthresholds.line.nearend.15min.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-12 OC-3 Card Default Settings (continued) Default Name Default Value Default Domain OC3.pmthresholds.sts1.nearend.1day.ES 100 (seconds) 0 - 86400 OC3.pmthresholds.sts1.nearend.1day.FC 10 (count) 0 - 6912 OC3.pmthresholds.sts1.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 OC3.pmthresholds.sts1.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 OC3.pmthresholds.sts1.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 OC3.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card C.2.3.13 OC3-8 Card Default Settings Table C-13 lists the eight-port OC3-8 (OC3 IR/STM1 SH 1310-8) card default settings. Table C-13 OC3-8 Card Default Settings Default Name Default Value Default Domain OC3-8.config.line.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 OC3-8.config.line.AlsMode Disabled Disabled, Auto Restart, Manual Restart, Manual Restart for Test OC3-8.config.line.AlsRecoveryPulseDuration 2.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-13 OC3-8 Card Default Settings (continued) Default Name Default Value Default Domain OC3-8.physicalthresholds.alarm.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1, OPR-LOW + 2 .. 255 OC3-8.physicalthresholds.alarm.OPR-LOW 50 (%) -1, 0, 1 .. OPR-HIGH OC3-8.physicalthresholds.alarm.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1, OPT-LOW + 2 .. 255 OC3-8.physicalthresholds.alarm.OPT-LOW 80 (%) 0, 1, 2 .. OPT-HIGH OC3-8.physicalthresholds.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-13 OC3-8 Card Default Settings (continued) Default Name Default Value Default Domain OC3-8.pmthresholds.line.nearend.15min.PSD 300 (seconds) 0 - 900 OC3-8.pmthresholds.line.nearend.15min.SES 1 (seconds) 0 - 900 OC3-8.pmthresholds.line.nearend.15min.UAS 3 (seconds) 0 - 900 OC3-8.pmthresholds.line.nearend.1day.CV 13120 (B2 count) 0 - 13219200 OC3-8.pmthresholds.line.nearend.1day.ES 864 (seconds) 0 - 86400 OC3-8.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-13 OC3-8 Card Default Settings (continued) Default Name Default Value Default Domain OC3-8.pmthresholds.sts1.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 OC3-8.pmthresholds.sts1.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 OC3-8.pmthresholds.sts1.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 OC3-8.pmthresholds.sts1.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 OC3-8.pmthresholds.sts1.nearend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-14 OC-12 Card Default Settings Default Name Default Value Default Domain OC12.config.line.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 OC12.config.line.PJStsMon# 0 (STS #) 0 - 12 OC12.config.line.SDBER 1.00E-07 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 OC12.config.line.sdh.AdminSSMIn STU G811, STU, G812T, G812L, SETS, DUS OC12.config.line.sdh.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-14 OC-12 Card Default Settings (continued) Default Name Default Value Default Domain OC12.pmthresholds.line.farend.1day.UAS 10 (seconds) 0 - 86400 OC12.pmthresholds.line.nearend.15min.CV 5315 (B2 count) 0 - 552600 OC12.pmthresholds.line.nearend.15min.ES 87 (seconds) 0 - 900 OC12.pmthresholds.line.nearend.15min.FC 10 (count) 0 - 72 OC12.pmthresholds.line.nearend.15min.PSC 1 (count) 0 - 600 OC12.pmthresholds.line.nearend.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-14 OC-12 Card Default Settings (continued) Default Name Default Value Default Domain OC12.pmthresholds.sts1.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 OC12.pmthresholds.sts1.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 OC12.pmthresholds.sts1.nearend.15min.SES 3 (seconds) 0 - 900 OC12.pmthresholds.sts1.nearend.15min.UAS 10 (seconds) 0 - 900 OC12.pmthresholds.sts1.nearend.1day.CV 125 (B3 count) 0 - 207360000 OC12.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-14 OC-12 Card Default Settings (continued) Default Name Default Value Default Domain OC12.pmthresholds.sts12c.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 OC12.pmthresholds.sts12c.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 OC12.pmthresholds.sts12c.nearend.1day.SES 7 (seconds) 0 - 86400 OC12.pmthresholds.sts12c.nearend.1day.UAS 10 (seconds) 0 - 86400 OC12.pmthresholds.sts3c-9c.nearend.15min.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-15 OC12-4 Card Default Settings (continued) Default Name Default Value Default Domain OC12-4.config.line.SDBER 1.00E-07 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 OC12-4.config.line.sdh.AdminSSMIn STU G811, STU, G812T, G812L, SETS, DUS OC12-4.config.line.sdh.SendDoNotUse FALSE FALSE when SendDoNotUse TRUE; FALSE, TRUE when SendDoNotUse FALSE OC12-4.config.line.sdh.SendDoNotUse FALSE FALSE, TRUE OC12-4.config.line.sdh.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-15 OC12-4 Card Default Settings (continued) Default Name Default Value Default Domain OC12-4.pmthresholds.line.nearend.15min.ES 87 (seconds) 0 - 900 OC12-4.pmthresholds.line.nearend.15min.FC 10 (count) 0 - 72 OC12-4.pmthresholds.line.nearend.15min.PSC 1 (count) 0 - 600 OC12-4.pmthresholds.line.nearend.15min.PSC-W 1 (count) 0 - 600 OC12-4.pmthresholds.line.nearend.15min.PSD 300 (seconds) 0 - 900 OC12-4.pmthresholds.line.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-15 OC12-4 Card Default Settings (continued) Default Name Default Value Default Domain OC12-4.pmthresholds.sts1.nearend.15min.UAS 10 (seconds) 0 - 900 OC12-4.pmthresholds.sts1.nearend.1day.CV 125 (B3 count) 0 - 207360000 OC12-4.pmthresholds.sts1.nearend.1day.ES 100 (seconds) 0 - 86400 OC12-4.pmthresholds.sts1.nearend.1day.FC 10 (count) 0 - 6912 OC12-4.pmthresholds.sts1.nearend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-15 OC12-4 Card Default Settings (continued) Default Name Default Value Default Domain OC12-4.pmthresholds.sts12c.nearend.1day.UAS 10 (seconds) 0 - 86400 OC12-4.pmthresholds.sts3c-9c.nearend.15min.CV 25 (B3 count) 0 - 2160000 OC12-4.pmthresholds.sts3c-9c.nearend.15min.ES 20 (seconds) 0 - 900 OC12-4.pmthresholds.sts3c-9c.nearend.15min.FC 10 (count) 0 - 72 OC12-4.pmthresholds.sts3c-9c.nearend.15min.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-16 OC-48 Card Default Settings (continued) Default Name Default Value Default Domain OC48.config.line.AlsRecoveryPulseDuration 2.0 (seconds) 2.0, 2.1, 2.2 .. 100.0 when AlsMode Disabled, Auto Restart, Manual Restart; 80.0, 80.1, 80.2 .. 100.0 when AlsMode Manual Restart for Test OC48.config.line.AlsRecoveryPulseInterval 100 (seconds) 60 - 300 OC48.config.line.PJStsMon# 0 (STS #) 0 - 48 OC48.config.line.SDBER 1.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-16 OC-48 Card Default Settings (continued) Default Name Default Value Default Domain OC48.pmthresholds.line.farend.1day.ES 864 (seconds) 0 - 86400 OC48.pmthresholds.line.farend.1day.FC 40 (count) 0 - 6912 OC48.pmthresholds.line.farend.1day.SES 4 (seconds) 0 - 86400 OC48.pmthresholds.line.farend.1day.UAS 10 (seconds) 0 - 86400 OC48.pmthresholds.line.nearend.15min.CV 21260 (B2 count) 0 - 2212200 OC48.pmthresholds.line.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-16 OC-48 Card Default Settings (continued) Default Name Default Value Default Domain OC48.pmthresholds.section.nearend.1day.SEFS 5000 (seconds) 0 - 86400 OC48.pmthresholds.section.nearend.1day.SES 5000 (seconds) 0 - 86400 OC48.pmthresholds.sts1.nearend.15min.CV 15 (B3 count) 0 - 2160000 OC48.pmthresholds.sts1.nearend.15min.ES 12 (seconds) 0 - 900 OC48.pmthresholds.sts1.nearend.15min.FC 10 (count) 0 - 72 OC48.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-16 OC-48 Card Default Settings (continued) Default Name Default Value Default Domain OC48.pmthresholds.sts12c-48c.nearend.15min.SES 3 (seconds) 0 - 900 OC48.pmthresholds.sts12c-48c.nearend.15min.UAS 10 (seconds) 0 - 900 OC48.pmthresholds.sts12c-48c.nearend.1day.CV 750 (B3 count) 0 - 207360000 OC48.pmthresholds.sts12c-48c.nearend.1day.ES 600 (seconds) 0 - 86400 OC48.pmthresholds.sts12c-48c.nearend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-16 OC-48 Card Default Settings (continued) Default Name Default Value Default Domain OC48.pmthresholds.sts3c-9c.nearend.1day.SES 7 (seconds) 0 - 86400 OC48.pmthresholds.sts3c-9c.nearend.1day.UAS 10 (seconds) 0 - 86400 C.2.3.17 OC-192 Card Default Settings Table C-17 lists the OC-192 (OC192 SR/STM64 IO 1310, OC192 LR/STM64 LH ITU 15xx.xx, OC192 IR/STM64 SH 1550, and OC192 LR/STM64 LH 1550) card default settings.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-17 OC-192 Card Default Settings (continued) Default Name Default Value Default Domain OC192.config.line.sonet.AdminSSMIn STU PRS, STU, ST2, ST3, SMC, ST4, DUS, RES when //.//.//.//.NODE.timing.general.SSM MessageSet Generation 1; PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, RES when //.//.//.//.NODE.timing.general.SSM MessageSet Generation 2; PRS, STU, ST2, ST3, SMC, ST4, DUS, RES when //.//.//.//.NODE.timing.general.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-17 OC-192 Card Default Settings (continued) Default Name Default Value Default Domain OC192.physicalthresholds.warning.1day.OPR-LOW 50 (%) -1, 0, 1 .. OPR-HIGH OC192.physicalthresholds.warning.1day.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1, OPT-LOW + 2 .. 255 OC192.physicalthresholds.warning.1day.OPT-LOW 80 (%) 0, 1, 2 .. OPT-HIGH OC192.pmthresholds.line.farend.15min.CV 85040 (B2 count) 0 - 8850600 OC192.pmthresholds.line.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-17 OC-192 Card Default Settings (continued) Default Name Default Value Default Domain OC192.pmthresholds.line.nearend.1day.PSD-R 600 (seconds) 0 - 86400 OC192.pmthresholds.line.nearend.1day.PSD-S 600 (seconds) 0 - 86400 OC192.pmthresholds.line.nearend.1day.PSD-W 600 (seconds) 0 - 86400 OC192.pmthresholds.line.nearend.1day.SES 4 (seconds) 0 - 86400 OC192.pmthresholds.line.nearend.1day.UAS 10 (seconds) 0 - 86400 OC192.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-17 OC-192 Card Default Settings (continued) Default Name Default Value Default Domain OC192.pmthresholds.sts1.nearend.1day.SES 7 (seconds) 0 - 86400 OC192.pmthresholds.sts1.nearend.1day.UAS 10 (seconds) 0 - 86400 OC192.pmthresholds.sts12c-192c.nearend.15min.CV 75 (B3 count) 0 - 2160000 OC192.pmthresholds.sts12c-192c.nearend.15min.ES 60 (seconds) 0 - 900 OC192.pmthresholds.sts12c-192c.nearend.15min.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-17 OC-192 Card Default Settings (continued) Default Name Default Value Default Domain OC192.pmthresholds.sts3c-9c.nearend.15min.SES 3 (seconds) 0 - 900 OC192.pmthresholds.sts3c-9c.nearend.15min.UAS 10 (seconds) 0 - 900 OC192.pmthresholds.sts3c-9c.nearend.1day.CV 250 (B3 count) 0 - 207360000 OC192.pmthresholds.sts3c-9c.nearend.1day.ES 200 (seconds) 0 - 86400 OC192.pmthresholds.sts3c-9c.nearend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-18 OC192-XFP Default Settings (continued) Default Name Default Value Default Domain OC192-XFP.config.line.sdh.SyncMsgIn TRUE FALSE, TRUE OC192-XFP.config.line.SendAISOnFacilityLoopback TRUE TRUE, FALSE OC192-XFP.config.line.SendAISOnTerminalLoopback TRUE TRUE, FALSE OC192-XFP.config.line.SFBER 1.00E-04 1E-3, 1E-4, 1E-5 OC192-XFP.config.line.sonet.AdminSSMIn STU PRS, STU, ST2, ST3, SMC, ST4, DUS, RES when //.//.//.//.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-18 OC192-XFP Default Settings (continued) Default Name Default Value Default Domain OC192-XFP.physicalthresholds.warning.1day.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1, LBC-LOW + 2 .. 255 OC192-XFP.physicalthresholds.warning.1day.LBC-LOW 20 (%) 0, 1, 2 .. LBC-HIGH OC192-XFP.physicalthresholds.warning.1day.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1, OPR-LOW + 2 .. 255 OC192-XFP.physicalthresholds.warning.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-18 OC192-XFP Default Settings (continued) Default Name Default Value Default Domain OC192-XFP.pmthresholds.line.nearend.1day.FC 40 (count) 0 - 6912 OC192-XFP.pmthresholds.line.nearend.1day.PSC 5 (count) 0 - 57600 OC192-XFP.pmthresholds.line.nearend.1day.PSC-R 5 (count) 0 - 57600 OC192-XFP.pmthresholds.line.nearend.1day.PSC-S 5 (count) 0 - 57600 OC192-XFP.pmthresholds.line.nearend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-18 OC192-XFP Default Settings (continued) Default Name Default Value Default Domain OC192-XFP.pmthresholds.sts1.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 OC192-XFP.pmthresholds.sts1.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 OC192-XFP.pmthresholds.sts1.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 OC192-XFP.pmthresholds.sts1.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 OC192-XFP.pmthresholds.sts1.nearend.15min.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-18 OC192-XFP Default Settings (continued) Default Name Default Value Default Domain OC192-XFP.pmthresholds.sts12c-192c.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 OC192-XFP.pmthresholds.sts12c-192c.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 OC192-XFP.pmthresholds.sts12c-192c.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 OC192-XFP.pmthresholds.sts12c-192c.nearend.15min.SES 3 (seconds) 0 - 900 OC192-XFP.pmthresholds.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-18 OC192-XFP Default Settings (continued) Default Name Default Value Default Domain OC192-XFP.pmthresholds.sts3c-9c.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 OC192-XFP.pmthresholds.sts3c-9c.nearend.15min.SES 3 (seconds) 0 - 900 OC192-XFP.pmthresholds.sts3c-9c.nearend.15min.UAS 10 (seconds) 0 - 900 OC192-XFP.pmthresholds.sts3c-9c.nearend.1day.CV 250 (B3 count) 0 - 207360000 OC192-XFP.pmthresholds.sts3c-9c.nearend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC12-PORT.config.line.sdh.SendDoNotUse FALSE FALSE when SendDoNotUse TRUE; FALSE, TRUE when SendDoNotUse FALSE MRC-12.OC12-PORT.config.line.sdh.SendDoNotUse FALSE FALSE, TRUE MRC-12.OC12-PORT.config.line.sdh.SyncMsgIn TRUE FALSE, TRUE MRC-12.OC12-PORT.config.line.SendAISOnFacilityLoopback TRUE TRUE, FALSE MRC-12.OC12-PORT.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC12-PORT.physicalthresholds.warning.1day.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1, OPR-LOW + 2 .. 255 MRC-12.OC12-PORT.physicalthresholds.warning.1day.OPR-LOW 50 (%) -1, 0, 1 .. OPR-HIGH MRC-12.OC12-PORT.physicalthresholds.warning.1day.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1, OPT-LOW + 2 .. 255 MRC-12.OC12-PORT.physicalthresholds.warning.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC12-PORT.pmthresholds.section.nearend.15min.CV 10000 (B1 count) 0 - 553500 MRC-12.OC12-PORT.pmthresholds.section.nearend.15min.ES 500 (seconds) 0 - 900 MRC-12.OC12-PORT.pmthresholds.section.nearend.15min.SEFS 500 (seconds) 0 - 900 MRC-12.OC12-PORT.pmthresholds.section.nearend.15min.SES 500 (seconds) 0 - 900 MRC-12.OC12-PORT.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC12-PORT.pmthresholds.sts1.nearend.1day.ES 100 (seconds) 0 - 86400 MRC-12.OC12-PORT.pmthresholds.sts1.nearend.1day.FC 40 (count) 0 - 6912 MRC-12.OC12-PORT.pmthresholds.sts1.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 MRC-12.OC12-PORT.pmthresholds.sts1.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 MRC-12.OC12-PORT.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC12-PORT.pmthresholds.sts12c.nearend.1day.CV 750 (B3 count) 0 - 207360000 MRC-12.OC12-PORT.pmthresholds.sts12c.nearend.1day.ES 600 (seconds) 0 - 86400 MRC-12.OC12-PORT.pmthresholds.sts12c.nearend.1day.FC 40 (count) 0 - 6912 MRC-12.OC12-PORT.pmthresholds.sts12c.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 MRC-12.OC12-PORT.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.UAS 10 (seconds) 0 - 900 MRC-12.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.CV 250 (B3 count) 0 - 207360000 MRC-12.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.ES 200 (seconds) 0 - 86400 MRC-12.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.FC 40 (count) 0 - 6912 MRC-12.OC12-PORT.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC3-PORT.config.line.sonet.SendDoNotUse FALSE FALSE when SendDoNotUse TRUE; FALSE, TRUE when SendDoNotUse FALSE MRC-12.OC3-PORT.config.line.sonet.SendDoNotUse FALSE FALSE, TRUE MRC-12.OC3-PORT.config.line.sonet.SyncMsgIn TRUE FALSE, TRUE MRC-12.OC3-PORT.config.line.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS MRC-12.OC3-PORT.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC3-PORT.pmthresholds.line.farend.15min.SES 1 (seconds) 0 - 900 MRC-12.OC3-PORT.pmthresholds.line.farend.15min.UAS 3 (seconds) 0 - 900 MRC-12.OC3-PORT.pmthresholds.line.farend.1day.CV 13120 (B2 count) 0 - 13219200 MRC-12.OC3-PORT.pmthresholds.line.farend.1day.ES 864 (seconds) 0 - 86400 MRC-12.OC3-PORT.pmthresholds.line.farend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC3-PORT.pmthresholds.sts1.farend.15min.ES 12 (seconds) 0 - 900 MRC-12.OC3-PORT.pmthresholds.sts1.farend.15min.FC 10 (count) 0 - 72 MRC-12.OC3-PORT.pmthresholds.sts1.farend.15min.SES 3 (seconds) 0 - 900 MRC-12.OC3-PORT.pmthresholds.sts1.farend.15min.UAS 10 (seconds) 0 - 900 MRC-12.OC3-PORT.pmthresholds.sts1.farend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC3-PORT.pmthresholds.sts3c.farend.15min.CV 25 (B3 count) 0 - 2160000 MRC-12.OC3-PORT.pmthresholds.sts3c.farend.15min.ES 20 (seconds) 0 - 900 MRC-12.OC3-PORT.pmthresholds.sts3c.farend.15min.FC 10 (count) 0 - 72 MRC-12.OC3-PORT.pmthresholds.sts3c.farend.15min.SES 3 (seconds) 0 - 900 MRC-12.OC3-PORT.pmthresholds.sts3c.farend.15min.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC3-PORT.pmthresholds.sts3c.nearend.1day.UAS 10 (seconds) 0 - 86400 MRC-12.OC48-PORT.config.line.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 MRC-12.OC48-PORT.config.line.AlsMode Disabled Disabled, Auto Restart, Manual Restart, Manual Restart for Test MRC-12.OC48-PORT.config.line.AlsRecoveryPulseDuration 2.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC48-PORT.physicalthresholds.alarm.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1, OPT-LOW + 2 .. 255 MRC-12.OC48-PORT.physicalthresholds.alarm.OPT-LOW 80 (%) 0, 1, 2 .. OPT-HIGH MRC-12.OC48-PORT.physicalthresholds.warning.15min.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1, LBC-LOW + 2 .. 255 MRC-12.OC48-PORT.physicalthresholds.warning.15min.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC48-PORT.pmthresholds.line.nearend.15min.PSC-S 1 (count) 0 - 600 MRC-12.OC48-PORT.pmthresholds.line.nearend.15min.PSC-W 1 (count) 0 - 600 MRC-12.OC48-PORT.pmthresholds.line.nearend.15min.PSD 300 (seconds) 0 - 900 MRC-12.OC48-PORT.pmthresholds.line.nearend.15min.PSD-R 300 (seconds) 0 - 900 MRC-12.OC48-PORT.pmthresholds.line.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC48-PORT.pmthresholds.sts1.farend.15min.SES 3 (seconds) 0 - 900 MRC-12.OC48-PORT.pmthresholds.sts1.farend.15min.UAS 10 (seconds) 0 - 900 MRC-12.OC48-PORT.pmthresholds.sts1.farend.1day.CV 125 (B3 count) 0 - 207360000 MRC-12.OC48-PORT.pmthresholds.sts1.farend.1day.ES 100 (seconds) 0 - 86400 MRC-12.OC48-PORT.pmthresholds.sts1.farend.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC48-PORT.pmthresholds.sts12c-48c.farend.15min.FC 10 (count) 0 - 72 MRC-12.OC48-PORT.pmthresholds.sts12c-48c.farend.15min.SES 3 (seconds) 0 - 900 MRC-12.OC48-PORT.pmthresholds.sts12c-48c.farend.15min.UAS 10 (seconds) 0 - 900 MRC-12.OC48-PORT.pmthresholds.sts12c-48c.farend.1day.CV 750 (B3 count) 0 - 207360000 MRC-12.OC48-PORT.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-19 MRC-12 Card Default Settings (continued) Default Name Default Value Default Domain MRC-12.OC48-PORT.pmthresholds.sts3c-9c.farend.15min.ES 20 (seconds) 0 - 900 MRC-12.OC48-PORT.pmthresholds.sts3c-9c.farend.15min.FC 10 (count) 0 - 72 MRC-12.OC48-PORT.pmthresholds.sts3c-9c.farend.15min.SES 3 (seconds) 0 - 900 MRC-12.OC48-PORT.pmthresholds.sts3c-9c.farend.15min.UAS 10 (seconds) 0 - 900 MRC-12.OC48-PORT.pmthresholds.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card C.2.3.20 MRC-2.5G-4 Card Default Settings Table C-20 lists the MRC-2.5G-4 card default settings. Table C-20 MRC-2.5G-4 Card Default Settings Default Name Default Value Default Domain MRC25G-4.OC12-PORT.config.line.AINSSoakTime 08:00 00:00, 00:15, 00:30 .. (hours:mins) 48:00 MRC25G-4.OC12-PORT.config.line.AlsMode Disabled MRC25G-4.OC12-PORT.config.line.AlsRecoveryPulseDuration 2.0 (seconds) 2.0, 2.1, 2.2 .. 100.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC12-PORT.physicalthresholds.warning.15min.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1, LBC-LOW + 2 .. 255 MRC25G-4.OC12-PORT.physicalthresholds.warning.15min.LBC-LOW 20 (%) 0, 1, 2 .. LBC-HIGH MRC25G-4.OC12-PORT.physicalthresholds.warning.15min.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1, OPR-LOW + 2 .. 255 MRC25G-4.OC12-PORT.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC12-PORT.pmthresholds.line.nearend.15min.PSD-W 300 (seconds) 0 - 900 MRC25G-4.OC12-PORT.pmthresholds.line.nearend.15min.SES 1 (seconds) 0 - 900 MRC25G-4.OC12-PORT.pmthresholds.line.nearend.15min.UAS 3 (seconds) 0 - 900 MRC25G-4.OC12-PORT.pmthresholds.line.nearend.1day.CV 53150 (B2 count) 0 - 53049600 MRC25G-4.OC12-PORT.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC12-PORT.pmthresholds.sts1.farend.1day.CV 125 (B3 count) 0 - 207360000 MRC25G-4.OC12-PORT.pmthresholds.sts1.farend.1day.ES 100 (seconds) 0 - 86400 MRC25G-4.OC12-PORT.pmthresholds.sts1.farend.1day.FC 40 (count) 0 - 6912 MRC25G-4.OC12-PORT.pmthresholds.sts1.farend.1day.SES 7 (seconds) 0 - 86400 MRC25G-4.OC12-PORT.pmthresholds.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC12-PORT.pmthresholds.sts12c.farend.15min.CV 75 (B3 count) 0 - 2160000 MRC25G-4.OC12-PORT.pmthresholds.sts12c.farend.15min.ES 60 (seconds) 0 - 900 MRC25G-4.OC12-PORT.pmthresholds.sts12c.farend.15min.FC 10 (count) 0 - 72 MRC25G-4.OC12-PORT.pmthresholds.sts12c.farend.15min.SES 3 (seconds) 0 - 900 MRC25G-4.OC12-PORT.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC12-PORT.pmthresholds.sts12c.nearend.1day.PJCS-PGEN 9600 (seconds) MRC25G-4.OC12-PORT.pmthresholds.sts12c.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 MRC25G-4.OC12-PORT.pmthresholds.sts12c.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 MRC25G-4.OC12-PORT.pmthresholds.sts12c.nearend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 MRC25G-4.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 MRC25G-4.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 MRC25G-4.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC3-PORT.physicalthresholds.alarm.LBC-LOW 20 (%) 0, 1, 2 .. LBC-HIGH MRC25G-4.OC3-PORT.physicalthresholds.alarm.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1, OPR-LOW + 2 .. 255 MRC25G-4.OC3-PORT.physicalthresholds.alarm.OPR-LOW 50 (%) -1, 0, 1 .. OPR-HIGH MRC25G-4.OC3-PORT.physicalthresholds.alarm.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC3-PORT.pmthresholds.line.nearend.15min.CV 1312 (B2 count) 0 - 137700 MRC25G-4.OC3-PORT.pmthresholds.line.nearend.15min.ES 87 (seconds) 0 - 900 MRC25G-4.OC3-PORT.pmthresholds.line.nearend.15min.FC 10 (count) 0 - 72 MRC25G-4.OC3-PORT.pmthresholds.line.nearend.15min.PSC 1 (count) 0 - 600 MRC25G-4.OC3-PORT.pmthresholds.line.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC3-PORT.pmthresholds.sts1.farend.15min.UAS 10 (seconds) 0 - 900 MRC25G-4.OC3-PORT.pmthresholds.sts1.farend.1day.CV 125 (B3 count) 0 - 207360000 MRC25G-4.OC3-PORT.pmthresholds.sts1.farend.1day.ES 100 (seconds) 0 - 86400 MRC25G-4.OC3-PORT.pmthresholds.sts1.farend.1day.FC 40 (count) 0 - 6912 MRC25G-4.OC3-PORT.pmthresholds.sts1.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC3-PORT.pmthresholds.sts3c.farend.15min.CV 25 (B3 count) 0 - 2160000 MRC25G-4.OC3-PORT.pmthresholds.sts3c.farend.15min.ES 20 (seconds) 0 - 900 MRC25G-4.OC3-PORT.pmthresholds.sts3c.farend.15min.FC 10 (count) 0 - 72 MRC25G-4.OC3-PORT.pmthresholds.sts3c.farend.15min.SES 3 (seconds) 0 - 900 MRC25G-4.OC3-PORT.pmthresholds.sts3c.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC3-PORT.pmthresholds.sts3c.nearend.1day.PJCS-PGEN 9600 (seconds) MRC25G-4.OC3-PORT.pmthresholds.sts3c.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 MRC25G-4.OC3-PORT.pmthresholds.sts3c.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 MRC25G-4.OC3-PORT.pmthresholds.sts3c.nearend.1day.SES 7 (seconds) 0 - 86400 MRC25G-4.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC48-PORT.physicalthresholds.alarm.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1, OPT-LOW + 2 .. 255 MRC25G-4.OC48-PORT.physicalthresholds.alarm.OPT-LOW 80 (%) 0, 1, 2 .. OPT-HIGH MRC25G-4.OC48-PORT.physicalthresholds.warning.15min.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1, LBC-LOW + 2 .. 255 MRC25G-4.OC48-PORT.physicalthresholds.warning.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC48-PORT.pmthresholds.line.nearend.15min.PSC-R 1 (count) 0 - 600 MRC25G-4.OC48-PORT.pmthresholds.line.nearend.15min.PSC-S 1 (count) 0 - 600 MRC25G-4.OC48-PORT.pmthresholds.line.nearend.15min.PSC-W 1 (count) 0 - 600 MRC25G-4.OC48-PORT.pmthresholds.line.nearend.15min.PSD 300 (seconds) 0 - 900 MRC25G-4.OC48-PORT.pmthresholds.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC48-PORT.pmthresholds.section.nearend.1day.CV 100000 (B1 count) 0 - 206582400 MRC25G-4.OC48-PORT.pmthresholds.section.nearend.1day.ES 5000 (seconds) 0 - 86400 MRC25G-4.OC48-PORT.pmthresholds.section.nearend.1day.SEFS 5000 (seconds) 0 - 86400 MRC25G-4.OC48-PORT.pmthresholds.section.nearend.1day.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC48-PORT.pmthresholds.sts1.nearend.1day.ES 100 (seconds) 0 - 86400 MRC25G-4.OC48-PORT.pmthresholds.sts1.nearend.1day.FC 40 (count) 0 - 6912 MRC25G-4.OC48-PORT.pmthresholds.sts1.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 MRC25G-4.OC48-PORT.pmthresholds.sts1.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 MRC25G-4.
-
Appendix C Network Element Defaults C.2.3 Defaults by Card Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 MRC25G-4.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.SES 3 (seconds) 0 - 900 MRC25G-4.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.UAS 10 (seconds) 0 - 900 MRC25G-4.OC48-PORT.pmthresholds.sts12c-48c.nearend.1day.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-20 MRC-2.5G-4 Card Default Settings (continued) Default Name Default Value Default Domain MRC25G-4.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 MRC25G-4.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 MRC25G-4.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 MRC25G-4.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.
-
Appendix C Network Element Defaults C.3 Node Default Settings to be disabled when they are providing services (when the default is set to FALSE users must remove or disable the services first, then put the ports out of service), and whether to report loopback conditions on Out-of-Service, Maintenance (OOS-MT) state ports. • Power Monitor settings—Set default voltage thresholds for the node.
-
Appendix C Network Element Defaults C.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.circuits.pathprotection.SwitchOnPDIP FALSE TRUE, FALSE NODE.circuits.pathprotection.VT_SDBER 1.00E-05 1E-5, 1E-6, 1E-7, 1E-8 NODE.circuits.pathprotection.VT_SFBER 1.00E-03 1E-3, 1E-4, 1E-5 NODE.general.AllowServiceAffectingPortChangeToDisabled TRUE FALSE, TRUE NODE.general.AutoPM FALSE FALSE, TRUE NODE.general.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.lmp.controlChannel.HelloInterval 500 (ms) maximum_of(30 0,MinHelloInterv al), maximum_of(30 0,MinHelloInterv al) + 1, maximum_of(30 0,MinHelloInterv al) + 2 .. minimum_of(500 0,MaxHelloInter val,quotient_of( HelloDeadInterv al,3)) NODE.lmp.controlChannel.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.lmp.controlChannel.MinHelloDeadInterval 2000 (ms) maximum_of(20 00,sum_of(MinH elloInterval,1)), maximum_of(20 00,sum_of(MinH elloInterval,1)) + 1, maximum_of(20 00,sum_of(MinH elloInterval,1)) + 2 .. minimum_of(200 00,HelloDeadInt erval) NODE.lmp.controlChannel.MinHelloInterval 300 (ms) 300, 301, 302 ..
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.network.general.GatewaySettings None LeaveAsIs, None, ENE, GNE, ProxyOnlyNode NODE.network.general.LcdSetting Allow Configuratio n Allow Configuration, Display Only, Suppress Display NODE.osi.greTunnel.OspfCost 110 110 - 65535 NODE.osi.greTunnel.SubnetMask 24 (bits) 8, 9, 10 .. 32 NODE.osi.lapd.Mode AITS AITS, UITS NODE.osi.lapd.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.osi.tarp.LDBFlush 5 (min) 0 - 1440 NODE.osi.tarp.PDUsL1Propagation TRUE FALSE, TRUE NODE.osi.tarp.PDUsL2Propagation TRUE FALSE, TRUE NODE.osi.tarp.PDUsOrigination TRUE FALSE, TRUE NODE.osi.tarp.T1Timer 15 (sec) 0 - 3600 NODE.osi.tarp.T2Timer 25 (sec) 0 - 3600 NODE.osi.tarp.T3Timer 40 (sec) 0 - 3600 NODE.osi.tarp.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.security.dataComm.CtcBackplaneIpDisplaySuppression TRUE FALSE, TRUE when isSecureModeSu pportedOnContro lCard TRUE; (NOT SUPPORTED) when isSecureModeSu pportedOnContro lCard FALSE NODE.security.dataComm.DefaultTCCEthernetIP 10.0.0.1 IP Address NODE.security.dataComm.DefaultTCCEthernetIPNetmask 24 (bits) 8, 9, 10 .. 32 NODE.security.dataComm.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.security.dataComm.SecureModeOn (May reboot node) FALSE FALSE, TRUE when isSecureModeSu pportedOnContro lCard TRUE; (NOT SUPPORTED) when isSecureModeSu pportedOnContro lCard FALSE NODE.security.emsAccess.AccessState NonSecure NonSecure, Secure NODE.security.emsAccess.IIOPListenerPort (May reboot node) 57790 (port #) 0 - 65535 NODE.security.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.security.legalDisclaimer.LoginWarningMessage WAR NING center>This system is restricted to authorized users for business purposes. Unauthorize daccess 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.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.security.passwordChange.NewPasswordMustDifferFromOldByNCharacters 1 (characters) 1-5 NODE.security.passwordChange.PreventReusingLastNPasswords 1 (times) 1 - 10 NODE.security.passwordChange.RequirePasswordChangeOnFirstLoginToNewAccount FALSE TRUE, FALSE NODE.security.passwordComplexity.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.software.DefaultDelayedUpgrades FALSE FALSE, TRUE when AllowDelayedUp grades TRUE; FALSE when AllowDelayedUp grades FALSE NODE.timing.bits-1.AdminSSMIn STU PRS, STU, ST2, ST3, SMC, ST4, DUS, RES when //.general.SSMM essageSet Generation 1; PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, RES when //.general.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.timing.bits-1.Coding B8ZS B8ZS, AMI when FacilityType DS1; HDB3, AMI when FacilityType E1; N/A when FacilityType 2MHz; AMI when FacilityType 64kHz+8kHz NODE.timing.bits-1.CodingOut B8ZS B8ZS, AMI when FacilityTypeOut DS1; HDB3, AMI when FacilityTypeOut E1; N/A when FacilityTypeOut 2MHz; AMI when FacilityTypeOut 6MHz NODE.timing.bits-1.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.timing.bits-1.Framing ESF ESF, D4 when FacilityType DS1; FAS+CRC, FAS+CAS, FAS+CAS+CRC, FAS, Unframed when FacilityType E1; N/A when FacilityType 2MHz; N/A when FacilityType 64kHz+8kHz NODE.timing.bits-1.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.timing.bits-2.AdminSSMIn STU PRS, STU, ST2, ST3, SMC, ST4, DUS, RES when //.general.SSMM essageSet Generation 1; PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, RES when //.general.SSMM essageSet Generation 2; G811, STU, G812T, G812L, SETS, DUS when //.general.SSMM essageSet N/A NODE.timing.bits-2.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.timing.bits-2.CodingOut B8ZS B8ZS, AMI when FacilityTypeOut DS1; HDB3, AMI when FacilityTypeOut E1; N/A when FacilityTypeOut 2MHz; AMI when FacilityTypeOut 6MHz NODE.timing.bits-2.FacilityType DS1 DS1, 64kHz+8kHz when //.general.Timing Standard SONET; E1, 64kHz+8kHz, 2MHz when //.general.Timing Standard SDH NODE.timing.bits-2.
-
Appendix C Network Element Defaults C.3 Node Default Settings Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.timing.bits-2.FramingOut ESF ESF, D4 when FacilityTypeOut DS1; FAS+CRC, FAS+CAS, FAS+CAS+CRC, FAS, Unframed when FacilityTypeOut E1; N/A when FacilityTypeOut 2MHz; N/A when FacilityTypeOut 6MHz NODE.timing.bits-2.LBO 0-133 0-133, 134-266, 267-399, 400-533, 534-655 NODE.timing.bits-2.
-
Appendix C Network Element Defaults C.3.1 Time Zones Table C-21 Node Default Settings (continued) Default Name Default Value Default Domain NODE.timing.general.QualityOfRES RES=DUS NODE.timing.general.ReversionTime 5.0 (minutes) 0.5, 1.0, 1.5 .. 12.0 NODE.timing.general.Revertive TRUE NODE.timing.general.SSMMessageSet Generation 1 Generation 1, Generation 2 when TimingStandard SONET; N/A when TimingStandard SDH NODE.timing.general.
-
Appendix C Network Element Defaults C.3.
-
Appendix C Network Element Defaults C.3.
-
Appendix C Network Element Defaults C.
-
Appendix C Network Element Defaults C.4 CTC Default Settings Table C-23 CTC Default Settings Default Name Default Value Default Domain CTC.circuits.CreateLikeTL1 FALSE TRUE, FALSE CTC.circuits.RouteAutomatically TRUE TRUE, FALSE CTC.circuits.RouteAutomaticallyDefaultOverridable TRUE TRUE, FALSE CTC.network.Map United States -none-, Germany, Japan, Netherlands, South Korea, United Kingdom, United States Note The CTC.network.LocalDomainCreationAndViewing NE default has been removed.
-
Appendix C Network Element Defaults C.4 CTC Default Settings Cisco ONS 15454 Reference Manual, R8.5.
-
I N D EX cross-connect card compatibility Numerics description 1+1 optical port protection creating linear ADMs description I-Temp 12-31 description specifications 7-2 7-6 example, shelf configurations by EIA type 7-9 description 3-29 2-32 A-8 software compatibility 7-6 example, shelf configurations by EIA type specifications 7-10 2-3 A-15 temperature range 1-23 A-10 See also AEP revertive switching 7-4 See also external alarms and controls 7-4 AINS secondary state, definition 15
-
Index deleting description editing log entries 14-11 automatic protection switching 14-9 XC10G card switch matrix 14-12 list by node loading XCVT card switch matrix 14-11 severity descriptions severity options 14-12 backplane connections AEP connections alarm suppressed by user 14-14 alarm suppression with OOS,MT 14-3, 14-13, B-3 AMP Champ 14-9 BNC 14-5 14-7 1-70 1-24 timing connections 14-4 1-67 1-19 MiniBNC entries in session history 1-31 LAN connections 14-4 1-58 1-69
-
Index BBE-PM parameter CAT-5 (LAN) 15-5 1-53, 8-6, 8-7 BBER-PM parameter 15-5 coaxial. See coaxial cable BBER-SM parameter 15-5 DS-1 See DS-1 cables BBE-SM parameter Ethernet 15-5 1-51 bidirectional line switched ring.
-
Index specifications SW-LCAS security policies A-50 circuits 5-31 VCAT differential delay attributes 5-32 See also Ethernet cards 11-2 automatic routing CE-100T-8 card autorange circuit types 9-6 11-27 11-2 constraint-based routing 5-28 cross-connect compatibility 5-30 exporting 11-33 11-3, 11-10 description 5-28 filtering illustration 5-29 finding circuits with alarms LEDs manual routing detail 5-30 link capacity adjustment port status 11-3 maximize resources 11-36 mer
-
Index port colors and service states port state compatibility 8-10 1-76 computer requirements 11-11 common control cards concurrent session limit See AIC-I card default settings See TCC2 card delivery methods See TCC2P card exporting data See XC10G card Launcher See XCVT card legal disclaimer See XC-VXC-10G card login common fiber routing (VCAT) comparing alarm profiles computer requirements 8-18 8-8 8-7 specifications 14-6 8-7 C-Temp ranges 14-5 connecting to LANs using static
-
Index consolidating connections icon description 8-15 pin assignments viewing connections 8-14 view non-DCC nodes 8-8 illustration 2-7 termination on TCC2P card DCC tunnels port status C-7 3-11 specifications 3-11 A-19 UBIC-H EIA J-labeling 15-6 1-36 See also electrical cards deep door kit See also UBIC-H EIA 1-7 deleting See also UBIC-V EIA alarm profiles alarms DS1-14 card 14-11 card-level LEDs 14-4 rows in RMON alarmTable description 16-19 rows in RMON historyControlTa
-
Index factory defaults illustration 15-16 slot compatibility port status A-18 3-25 15-5 card-level LEDs description 3-18 J-labeling port assignments 1-25 15-27 3-19 factory defaults 1-16, 1-17 C-21 3-20 illustration 3-16 3-21 EIA compatibility features 3-19 specifications A-24 DS3i-N-12 card 1-17 C-14 slot restrictions 3-22 DS3 CV-L parameter 3-16 performance monitoring 3-20 performance monitoring A-20 UBIC-H EIA J-labeling 1-36 port status slot compatibility See also M
-
Index factory defaults illustration XC-VXC-10G card support C-19 See also electrical cards 3-24 performance monitoring port-level LEDs 15-19 dual GNEs 3-22 DWDM backplane configurations card-level LEDs OC48 ELR 200 GHz cards 4-28 Dynamic Host Configuration Protocol.
-
Index LEDs description 5-6 port status installation overview 5-6 slot compatibility specifications 1-15 replacement 5-5 1-16 1-38 shelf assembly compatibility A-48 See also Ethernet cards specifications E100T-G card 1-16 A-3 See also AMP Champ EIA cross-connect compatibility 5-8 See also BNC EIA description 5-6 See also high-density BNC EIA illustration 5-7 See also MiniBNC EIA LEDs See also SMB EIA 5-8 port status See also UBIC-H EIA 5-8 slot compatibility specifications
-
Index proxy tunnel and firewall tunnel requirement SOCKS proxy server scenario 13-12 13-27 See also Ethernet cards Ethernet cards enterprise LAN.
-
Index four-fiber BLSRs two-fiber BLSR fiber connections 12-6 four-node path protection configuration four-shelf node (fiber-optic bus) unprotected configuration 12-15 8-17 extended fiber clips alarm contact connections 13-53 description nodes on the same subnet with secure mode enabled 13-21 See also AIC-I card 13-55, external firewalls external timing 12-31 path protection subtending from a BLSR 12-29 F path protection to BLSR traditional DRI handoff 12-26 facility data link fan-tray a
-
Index LEDs modes front door 6-3 equipment access 6-4 path trace capability ground strap 11-25 performance monitoring ports, line rates, and connectors power requirements specifications FT-TD A-10 1-10 13-41 fuse and alarm panel FX interface 15-53 1-2, 1-6 5-21 11-36 temperature range A-12 Utilization window VCAT circuits G 15-54 11-34 G1000-4 card See also VCAT circuits FC-L parameter description 15-7 FC-PFE parameter FC-PM parameter FC-P parameter 5-14 GBIC.
-
Index available types high-density BNC EIA 5-37 CE-1000-4 card card protection description 5-31 compatible cards CWDM and DWDM description description 5-39 G1000-4 card G1K-4 card card protection description 5-16 high-density shelf GNE AIP 13-14 dual GNEs on the same subnet 13-18 filtering packets for the firewall firewall configuration with SOCKS proxy server enabled 13-26 in a multivendor OSI network 1-14 EIA compatibility 1-17 fan-tray assembly 1-63 requirements 13-17 firewall
-
Index circuit display default gateway on CTC workstation 11-23 ML-Series card performance monitoring performance monitoring IEEE 802.
-
Index JRE loading alarm profiles requirement LOFC parameter 8-4 software compatibility 15-8 logging in, interoperability issues 8-5 jumper slack storage reels 14-11 login node groups 1-53 8-4 8-8, 8-12 LOSS-L parameter 15-8 lower backplane cover.
-
Index description LEDs RPR Span window 5-23 soak timer 5-24 port status slot compatibility specifications modem interface 5-25 A-2 modules ML100T-12 card See cards cross-connect compatibility 5-21 See SFPs description 5-19 monitor circuits illustration 5-20 monitoring 11-18 64-bit RMON over DCC 5-20 port status 11-34 modifying See changing A-52 See also Ethernet cards LEDs 11-9 VCAT circuits 5-25 circuits 5-21 slot compatibility specifications 5-21 A-51 See also Ether
-
Index port status network element defaults 4-49 SFP compatibility specifications topologies node view 4-53 card colors A-45 8-9 creating users 4-46 9-1 See also optical cards port colors See also SFPs security level by tab MT secondary state, definition multiple drops tabs list B-2 8-10 9-2 8-11 viewing popup information 11-18 NPJC-PDET parameter NPJC-Pdet parameter N 15-4 NE defaults.
-
Index port status slot compatibility specifications topologies OC192 LR/STM64 LH 1550 card 4-11 15454-OC192-LR2 illustration 4-10 description A-30 See also optical cards LEDs OC12 LR/STM4 LH 1310 card description illustration LEDs topologies specifications illustration 4-12 LEDs OC12 LR/STM4 LH 1550 card illustration LEDs topologies performance monitoring topologies 15-50 4-41 4-40 A-42 4-40 See also optical cards description 4-14 4-29 factory defaults A-32 illustration 4-14
-
Index J0 section trace LEDs performance monitoring 11-24 port status 4-52 performance monitoring port status 15-50 slot compatibility specifications 4-27 slot compatibility specifications 4-52 topologies 4-50 OC48 ELR 200 GHz cards 4-53 description See also XFPs factory defaults OC3 IR/STM1 SH 1310-8 card illustration LEDs 15-49 description 4-9 illustration LEDs 4-6 4-21 C-49 4-22 4-22 performance monitoring C-35 port status 4-6 performance monitoring 15-49 slot compatibil
-
Index OC48 LR/STM16 LH AS 1550 card description illustration overview C-49 specifications power requirements product names 4-24 specifications OC48 LR 1550 card timing C-49 specifications 10-1 OPT-MAX parameter 4-20 A-35 12-35 OC-N cards.
-
Index OSPF PIM service state transitions alternative to static routes common scenarios definition pin assignments. See backplane connections 13-7 ping 13-2 13-2 pinned hex key 13-10 in OSI routing scenarios B-10 to B-11 1-8 PJCDIFF-P parameter 13-50 P 15-8 PJCS-PDET-P parameter 15-9 PJCS-PGEN-P parameter 15-9 PJNEG parameter. See NPJC-PDET parameter passwords PJPOS parameter. See PPJC-PDET parameter 9-7 patch panel tool pluggable device 1-20, 1-27 path-protected mesh network.
-
Index and span upgrades provisioning PSC parameter 12-37 4-56 service state transitions B-10, B-10 to B-11 15-9 PSC-R parameter 15-9 PSC-S parameter 15-9 See also SFPs PSC-W parameter See also XFPs PSD parameter preprovisioning cards 8-11 See also provisioning printing CTC data 8-17 processing TARP 13-38 nonrevertive 1+1 revertive 7-13 15-10 B-1 B-1 rack installation bay assembly 12-8 overview CNLP 13-31 ES-IS 13-36 1-6 multiple nodes protocols rack size 1-6 1-3 single
-
Index RG-179 cable. See coaxial cable row creation in cMediaIndependentHistoryControlTable RG59 (735A) cable.
-
Index port state transitions S B-5 See also administrative states SAPI 13-31 SESCP-PFE parameter SASCP-P parameter SASP parameter 15-10 SESCP-P parameter 15-10 SASP-P parameter SES-L parameter 15-10 saving alarm profiles 15-10 15-10 SES-PFE parameter 14-11 15-10 SES-PM parameter SCSI connectors 15-10 SES-P parameter 15-10 15-10 See UBIC-H EIA SESP-P parameter See UBIC-V EIA SESR-PM parameter 15-11 SDCC.
-
Index components SST 16-2 external interfaces message types MIBs ST3 clock 16-4 RMON See administrative states See circuits, states 16-1 See service states 16-16 traps.
-
Index alarms for maintenance SWDL secondary state, definition SW-LCAS network-level LEDs 14-13 node database B-2 2-9 2-8 power requirements 11-36 A-8 synchronization status messaging.
-
Index TCP/IP node addition or removal and OSI mediation TCC2P access TDM TEI path protection to two-fiber BLSR 13-40 DCN communication 2-12 two-fiber to four-fiber BLSR 12-41 unprotected point-to-point or linear ADM to path protection 12-39 13-31 Telcordia traffic monitoring alarm severities 14-1 traffic routing performance monitoring standard racks 15-1 temperature ranges 13-31 See DS3XM-12 card See DS3XM-6 card Terminal Endpoint Identifier 13-31 traps 1-2, 11-16 content threshold
-
Index UAS-V parameter 15-12 V UBIC-H cables connector pins description VAP 1-46 definition 1-45 DS-1 pin assignments 1-41, 1-47 DS-3/EC-1 pin assignments 1-43, 1-49 card protection description connector labeling 1-35 connectors per side 7-5 description J labeling 7-12 11-46 VCAT circuits 11-34 11-34 differential delay on the CE-1000-4 1-18 in-service topology upgrade support member routing See also UBIC-H cables server trail support 1-40, 1-52, 1-53 sizes 1-40 card protection
-
Index VT1.
-
Index Cisco ONS 15454 Reference Manual, R8.5.